When you need to load a very large amount of data into Force.com quickly, you want to ensure that each insert is as efficient as possible. With appropriate preparation and post-processing, you can disable data validation and enrichment operations while loading–without compromising your data integrity or business rules. Continue reading
You are planning a Force.com implementation with large volumes of data. Your data model is in place, all your code is written and has been tested, and now it’s time to load the objects, some of which have tens of millions of records. What is the most efficient way to get all those records into the system?
This is the second entry in the six-part series about data loading for very large enterprise deployments, covering how you can load data into a lean configuration. Continue reading
The programmatic sharing capabilities of the Force.com platform are very powerful and flexible, but you have to practice a bit of defensive coding to keep our code from undoing yours. With Apex sharing reasons or one of the strategies described in this post, you can keep the shares you create from being deleted by record owner changes and maintain the integrity of your custom sharing model. Continue reading
What is the most efficient way to get all a LOT of data into your Salesforce or Force.com org? This post is the first in a six-part series “The Force.com Extreme Data Loading Series” covering all aspects of extreme data loading. Continue reading
Do you need to share data dynamically in Salesforce based on the attributes of the data itself? This blog entry explains when and how to implement two of the most common dynamic sharing use cases: criteria-based sharing rules and triggers. Continue reading
XYZ Corp is a large technology company with a very highly customized Salesforce implementation. At the time of engagement, XYZ was just recovering from a chaotic and costly end-of-year realignment of their Sales hierarchy and account assignments. Not only did the realignment take far longer than originally planned, but Sales estimated that far from kicking the year off with a bang, the company actually lost revenue opportunities in the first month from the delays. The Salesforce Technical Enablement team was engaged to help ensure a smoother realignment for the coming year-end, providing best practice advice on both technical… Continue reading
When you have a very large number of child records associated to the same account in Salesforce, we call that “data skew”. It can seem like the obviously right thing to do – for example, when you have a whole bunch of unassigned contacts and need some place to “park” them, it’s tempting to put them all under one account name ‘Unassigned’. Unfortunately this can cause issues with record locking and sharing performance. Let’s say you are updating a large number of contacts under the same account in multiple threads. For each update the system locks both the contact being… Continue reading