Skip to main content

Salesforce Data Loads from the Command Line

Whether it's creating, updating or deleting records, it seems like we're constantly being asked to do data loads. Trouble is, that this takes away from our core project tasks. There must be a faster way...

Use Case: Move all accounts owned by one user to another user.

Export Data from the Command Line

The first step in loading data is to prepare the import file. Sometimes we are given a nicely formatted import file, but let's pretend you need to pull the data out of Salesforce first.

In our scenario, we need to export the accounts that need to be moved. To do this, we need to get the Id of the user who currently owns the accounts.

You'll notice that this command starts with soql instead of sfdx force:data:soql:query --query. That is because I have set soql as an alias for the sfdx query command. Check out my other post on SOQL from the Command Line for more details on this technique.

Now that we have the Id of the user who currently owns the accounts, let's get the accounts we need to move over.

Notice that I've added -r csv > chatty_accounts_to_move.csv to the end of this command. This will output the query as a csv and the > symbol will direct the output to a file named chatty_accounts_to_move.csv

This file does not need to exist yet. If it does not exist, the command will create it for you. Be careful though because if it does exist, this command will overwrite the file.

Import Data from the Command Line

After you have exported your data and updated the csv to have the new owner's Id, you're ready to upload it to Salesforce. You can do that by running: 

The force:data:bulk:upsert command is a favorite of mine because it's so easy to use. In this example we are upserting accounts and using the Id column to identify the records. It is possible to use an External Id field here and upsert records based on a field that is not Id!

We are also passing the csv file into this command along with the alias of the org we want to import the data to. The --wait parameter allows you to define the number of minutes the CLI should wait for the upsert to complete. I typically just use 10 each time because the CLI will respond as soon as the upsert finishes.

Continued Learning

While exporting and importing data from the command line is faster than having to open up another application each time, there is a way to do this even faster. Check out Manipulate Salesforce Data from the Command Line to learn how you could do this in a single command.

If you're still getting used to the Salesforce CLI, I recommend checking out some of these links:


Popular posts from this blog

Salesforce Lighting Migration: Plan for Success

In April 2018, I led the Salesforce Lightning Migration at Postmates . This is how I would do it over again if I could. Define Goals The goals of a Lightning Migration are: Enable Lightning Experience Configure Lightning Experience Document all Salesforce processes Create training and support materials Lightning Experience is adopted Easy enough right? Let's go though the plan to see how we accomplish each one. Enable Lightning Experience Just turn it on right? Well, kinda. Although it may be controversial, I recommend turning it on and hiding the option from all users. This can be done by removing the Lightning Experience User permission from your custom profiles.  And yes, turn it on in production .  Why? You're going to turn it on anyway. Salesforce has declared this as the path forward, so you either turn it on now or wait until they flip the switch for you. Plus, turning this on ahead of time will make deploying from a sandbox much  e

Joins in SOQL

If you are familiar with SQL, the biggest gotcha when writing SOQL is how joins are done. You'll see the term  Sub-Query  used instead of  JOIN  because of how queries are done on the Salesforce platform. You can still do joins; it's just done a little differently than you're used to. Sub-Query (Outer Join) In SQL, a join is when rows are selected from multiple tables and joined together on common columns. Thinking about your tables like a Venn Diagram is a great analogy for this. Let's say you want to query all Accounts and also include their related Opportunities. This is an example of an Outer Join because it selects all Accounts and will include their related Opportunities via the sub-query. If an Account does not have an Opportunity, it will still be returned here. An Outer Join is similar to selecting one whole circle in a Venn Diagram, including the area that overlaps with the other circle. Sub-Query (Inner Join) An inner join can seem a little m

Modify Salesforce Data from the Command Line

When doing Salesforce data loads, how often are you putting the same value in an entire column? I find this happening when I need to: Move all accounts from one user to another Assign a set of leads to a specific user Set a field to a specific value Let's use the example from my other post: Salesforce Data Loads from the Command Line - Move all accounts owned by one user to another user. Magic Let's break down each piece of this: soql This is an alias I set for sfdx force:data:soql:query --query . It saves me from having to type this out each time and let's me query from the command line by just typing soql  and my query. This is a popular StackExchange post  that talks about how to set an alias. cat This command outputs the contents of a file. It is common to use this command with other commands by piping the output into another command. In our example, we are piping the output into the cut command. This post gives more examples of how to use t