Skip to main content

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.


Let's break down each piece of this:


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.


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 the cat command.


This is a command line utility to extract parts of a file. It can be used with csv files by setting the delimiter to a comma. In the example above, I am redirecting the output to a new file so we can maintain a clean backup file.

This command has many capabilities and this post talks about many of them. My most common usage follows this pattern:

cat file.csv | cut -d "," -f 1 > newFile.csv


This is a command line utility to perform find and replace operations on files. In our example, we are appending the OwnerId to the end of each row because our file only contains the Id of each Account. We are using the $ symbol, which tells sed to find the end of the line.

This command has a lot of options and this post covers a lot of them. I commonly use it like this:

sed -e '1 s/$/,Field_To_Append__c/' -e '2,$ s/$/,NewValue/' > outputFile.csv

sfdx force:data:bulk:upsert

This command allows us to upsert data via the Bulk API. It is a very flexible command and I have been using it for most of my data loads ever since I discovered it. In our example we are updating the Accounts in our file by their Ids.

Continued Learning

Here are a few links that will help further your knowledge of manipulating Salesforce data from the command line:


  1. Thanks for sharing this article here about modify data using the very basic linux commands. Your article is very informative and useful to know more about the process of modify sales force data from the Command Line. Keep sharing this type of articles here.


Post a Comment

Popular posts from this blog

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

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