Skip to main content

Key Take Away : Sequencing Load Operations

Here some highlight after I have done reading on
Extreme Data Loading, Part 4: Sequencing Load Operations

Configuring Your Organization for the Data Load

1) To consider enable the parallel recalculation

To enable this feature contact Salesforce Support

2) Create Role Hierarchy
3) Load users, assigning them to appropriate roles
4) Configure Public Read/Write organization-wide sharing defaults on the objects you plan to load. Note : some org may have so much data that changing sharing rules from Public to Private takes very long time, therefore just load the data with sharing model that you will use in Production.

Preparing to Load Data

1) Ensure clean data especially foreign key relationship, note that parallel loads switchs to single execution mode, slowing down the load considerably.
2) Suspend events that fire on insert
3) Perform advance testing to tune batch size for throughput.For both the Bulk API and the SOAP API, look for the largest batch size that is possible without generating network timeouts from large records, or from additional processing on inserts or updates that can’t be deferred until after the load completes.

Executing the Data Load

1) Use fastest operation possible : insert is faster than upsert. insert + update can be faster than upsert
2) When Update only load field that have changed for existing record
3) Group child records by Parent Id , if you use separate batched don't reference the same Parent Id. Why? This can reduce risk of record-locking errors.If this cannot be done, you can choose option of using the Bulk API in serial execution mode to avoid locking from parallel updates.

Configuring Organization for Production

1) Defer sharing calculation before performing some or all of the operations below ; depending on the results of your sandbox.
2) Change Public Read/Write OWD to Public Read Or Private appropriately
3) Create or configure public groups / queue [todo configure to what?]
4) Configure sharing rules
5) If Sharing Calculation is not deferred, create public groups, queues, and sharing rules one at a time, and allow sharing calculations to complete before moving on to the next one.
Note :That this will consume long time when resume sharing calculation for large data.
6) Resume events such insert trigger so validation/data enhancement process (Flow,Workflow etc) can run properly in Production


Popular posts from this blog

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {