You are here:
Considerations for Processes That Update Records
Understand what happens when you change a record owner, update the same field multiple times, or update currency fields in a multiple currency org.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
Understand what happens when you change a record owner, update the same field multiple times, or update currency fields in a multiple currency org.
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your switch to Flow Builder and use the Migrate to Flow tool. For new automations, create flows in Flow Builder.
Processes that update owners don’t automatically transfer the associated items. Use an Update Records action for each type of child record that you want to transfer.
For example, you want to transfer an account to a new owner. Add four Update Records actions to your process. The first updates the account. The second updates the child contacts. The third updates the child opportunities. And the fourth updates the child contracts.
If multiple Update Records actions apply different values to the same field, the last action’s value is used.
If your org uses multiple currencies, the currency fields are updated using the record’s currency code. If you use a formula to update a field, the formula values use the record’s currency code.
Processes can't update records that inactive users own. When you deactivate a user, also transfer that user's records to an active user to avoid failed processes.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.