Salesforce tutorials for developers, admins and architects.
Founder and the owner of SF Crunch. A Salesforce enthusiast, a Salesforce Certified System Architect with over a decade of experience in the Salesforce domain.
I am working as a full-time Salesforce architect and developer. I spent my spare time writing articles related to Salesforce for you guys.
I have demonstrated experience in the full Salesforce development lifecycle, designing solutions, and implementation.
Logging errors are helpful, primarily when an error occurs in the future, background apex jobs, or flows. Especially when you want to investigate why some background jobs are not working as expected and you want to know how frequently the jobs are failing.
Using the following solutions you can find the apex error exceptions easily. You can see why the error occurred and on which line of code the error occurred. You can see the errors in a list view and can do reporting on a specific error.
A solution to upload files from the same screen from where you get the record information from the end user.
Integration between Salesforce and Stripe. Sample code to create an charge object in stripe using apex code. The apex code can be invoked from the flow.
Find the number of days between two dates excluding weekends and holidays using apex
Create weekly, bi-weekly, monthly, quarterly, yearly and bi-yearly recurring tasks using apex.
Round Robin Assignment for any user lookup field using custom object and apex code.
If an opportunity has a quote then it must be synced to the opportunity in order to make the opportunity stage to Closed Won.
Deactivate an account record if it has no “Closed Won” Opportunity for 180 days or no opportunity created in 180 days.
Send the most recent Quote PDF attached to the email alert using Salesforce Flow
