Salesforce Platform dev 1 Debugging and deployment
Debug logs in Salesforce are very handy to troubleshot issues. Debug logs are useful specially for background process where you cant display error to Graphical user interface. You can activate debug logs by going to setup- Debug Mode

You need to pay special attention to debug log generation. If you activate logs every day it will generate a lot of logs in the system which can take a lot of space. So please make sure to clear those logs which are not required.
At times you do get a message under dev console that you have exceeded the log limit. In that scenario, you do need to clear a few logs from dev console. You can use following apex code
"select id from Apexlog" to fetch the log id and select the logs and press delete row. Please enable Use tool API before you run the Soql code.

You need to pay special attention to debug log generation. If you activate logs every day it will generate a lot of logs in the system which can take a lot of space. So please make sure to clear those logs which are not required.
At times you do get a message under dev console that you have exceeded the log limit. In that scenario, you do need to clear a few logs from dev console. You can use following apex code
"select id from Apexlog" to fetch the log id and select the logs and press delete row. Please enable Use tool API before you run the Soql code.
Deployment is another area you should be fairly confident with. You can deploy your code using
Change set
Packages
If you are after commercial product, please have a look at gearset
Please do note before you deploy Apex code to production, you need to ensure your apex test class should cover at least 75 percent of the code. Otherwise, you won't be able to deploy your code to production.
It's a good practice to have at least 80 percent code coverage in your sandbox
Comments
Post a Comment