Traditionally, to control the visibility of records in Salesforce, we used to start with the most restrictive setting (i.e. setting OWD to Private for an object) and then opening up the access using various features like role hierarchy, sharing rules, teams etc.
Consider the following diagram. Before Restriction rules, we started with the most restrictive setting and then opened up access using various features.
In Salesforce, it is not uncommon to mass insert, update or delete records from time to time. This may be required to onboard new business units, departments or applications, fix bugs, patch existing records with certain values, accommodate changes in data model, archive and delete data etc.
But as we process data in bulk, validation rules and automation that are defined in Salesforce kicks in. This not only slows down the DML operation but may also lead to undesired processing like triggering emails to internal and external users, sending interface messages to backend systems and cause process and/or data integrity issues.
Flow continues to take more and more centre stage in Salesforce. Every Salesforce release contains tens of enhancements to Flows. In Winter ’22 Release of Salesforce, we could find about 44 enhancements related to Salesforce Flows.
And here is our top pick from these enhancements:
Uploading Files through Screen Flow is a bit tricky. We can’t use ‘Create Record’ element like we can for creating other records. And then we can’t even make the file upload mandatory like we can make other fields mandatory in Screen Flow.
This is a question that was asked by one of our Mastering Salesforce Flows course participants and since the solution is not very straight forward, we thought of documenting the whole solution in a step-by-step guide format and share with everyone.
Implementing Salesforce or already using Salesforce? Do you have a well-defined development & release management process to ensure that you are doing it the right way, using all the proper tools & technologies, automating processes where it can and should be automated?
Do you have a proper process to ensure that you are building an optimal solution on Salesforce, leveraging on the platform’s features and capabilities, not incurring technical debt and not cutting corners on best practices?