Clearing Salesforce Logs Manually - UI Delete not working

Sometimes clearing the logs via the UI does not always work...but what to do now?

 Here are some steps to solve your problem:

• Open your Developer Console
• Select query editor

• Enter the following query 
• select id from Apexlog 
• This will display all the logs by id

• Highlight (select) all the lines you wish to delete (Shift + down arrow)
• Then select Delete Row

This will start deleting your logs per id.

Happy Trails!

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

If Nginx wont start and is pushing back the following error:

[emerg]: bind() to 0.0.0.0:80 failed (98: Address already in use)

Then it means nginx or some other process is already using port 80.

You can kill it using:

sudo fuser -k 80/tcp

And then try restarting nginx again:

service nginx start 

 sudo /opt/bitnami/ctlscript.sh start

Salesforce : 22 Ways to Share Records

 

Code Coverage

Hey TrailBlazers!


One interesting area within any Salesforce org is code coverage.Inhereting an environment with low code coverage is never easy.

So the official statement : 

Code coverage indicates how many executable lines of code in your classes and triggers have been exercised by test methods. ... To deploy Apex or package it for the Salesforce AppExchange, unit tests must cover at least 75% of your Apex code, and those tests must pass.

...but how do you identify the root causes for your low coverage?



Select the Gear Icon >>Select Developer console




Once your developer console is open >>Select Query Editor >>




Paste the query below in the query editor  :

SELECT ApexClassorTrigger.Name, NumLinesCovered, NumLinesUncovered FROM ApexCodeCoverageAggregate ORDER BY NumLinesUncovered DESC LIMIT 10

Please ensure that you tick "Use Tooling API" and the execute:




This will give you a list of the top 10 classes lowering your code coverage.


Once identified its time to create the test classes.

Happy Trails!

This organization isn't authorized to upload change sets to other organizations. For authorization, contact the deployment connections administrators on the organizations where you want to upload changes.

Soooo..... I refreshed my sandbox environment to create a partial copy of production.

Added my new components and merrily attempted to deploy them to production.

All of a sudden I was posed with :

This organization isn't authorized to upload change sets to other organizations. For authorization, contact the deployment connections administrators on the organizations where you want to upload changes.

There is a simple fix for this.

• Logon to your production environment
• Launch Set Up
• Enter Deployment in the quick find box.

• Select Edit next to the environment (e.g. Sandbox) where you received the error
• Now tick the box that allows connections

• Once done with ticking the radio button, hit save.

You should now be able to go back to your Sandbox and deploy.

Happy Trails

Jerome Slinger