Enterprise Integration Zone is brought to you in partnership with:

Ross founded the open source Mule® project in 2003. Frustrated by integration "donkey work," he set out to create a new platform that emphasized ease of development and re-use of components. He started the Mule project to bring a modern approach, one of assembly, rather than repetitive coding, to developers worldwide. He is now the Founder and CTO of Mulesoft. Ross is a DZone MVB and is not an employee of DZone and has posted 94 posts at DZone. You can read more from them at their website. View Full User Profile

Dataloader.io Data Loading Stats for Salesforce.com

07.04.2013
| 1961 views |
  • submit to reddit

Originally authored by Katie Burton

As an avid observer of the .com data loading community, I thought it would be interesting to share some of the trends we see within our dataloader.io user base heading into the summer. How do these data loading trends compare to the activities within your organization?

is one size fits all (kind of)

Even though Salesforce.com is a SaaS based application, there is quite a bit of customization that takes place inside account, opportunity and contact records. While the majority of datalaoder.io users have standard objects, roughly ⅓ are routinely updating, upserting or inserting (importing) custom objects into their salesforce.com orgs.

Salesforce.com Data Loading Task Trends

 Salesforce.com object trends

It’s all about the data: Having a 360 view of the customer starts here

Out of all of the object types that can be imported into Salesforce.com, just over 30% (30.1%) of the operations are based on account data. Closely following the account are contact (18.9%) and opportunity records (18.3%). Making sure that you have all of the information associated with an account- information about the company, who and what opportunities are associated with it – is step 1 to creating a complete view of your customer.

Top 10 most used objects in Salesforce.com

A little data loading each day, keeps the doctor away

Depending up the size or amount of information you need to update in Salesforce, you can select one of two API modes to import, export or delete data- Batch or Bulk API mode. The Salesforce Batch API is based on SOAP principles and is optimized for real-time client applications that update small numbers of records at a time, while the Bulk API is based on REST principles and is optimized for loading or deleting large sets of data. Batch is the most popular mode used by the dataloader.io community, as many users are using the data loader for Salesforce to routinely add and update existing records, or remove bad data. On the flip side, .io users leverage the Bulk API to export large amounts of data to create repositories for backup and reporting purposes.

 Top 10 most used objects in Salesforce.com

For those of you that are loading data into Salesforce or other CRM systems such as SAP, Sugar CRM, Zoho, NetSuite and others, how do these stats compare? Get started with dataloader.io by visiting us on the AppExchange.

Happy data loading!


Published at DZone with permission of Ross Mason, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)