Loading
Automate Your Business Processes
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Control What Happens When a Flow Tries to Set Values for Read-Only Fields

            You are here:

            1. Salesforce Help
            2. Docs
            3. Automate Your Business Processes

            Control What Happens When a Flow Tries to Set Values for Read-Only Fields

            When a flow tries to perform an action, such as create or update records, it uses a flow request to set values for specific fields. But what happens if the running user doesn’t have edit access to all those fields? When you use a record variable or record collection variable in Create Records and Update Records elements, that’s up to you. To control the behavior, select or deselect the Filter inaccessible fields from flow requests preference.

            Required Editions

            View supported editions.
            User Permissions Needed
            To edit process automation settings: Customize Application
            To create, update, and delete flow list views: Manage Flow
              When Filter inaccessible fields from flow requests is
              Selected Not Selected (Recommended)
            Result when the running user doesn’t have edit access to all fields

            The operation partially succeeds.

            The flow filters read-only fields out of the operation. The fields that the user can edit are updated. The fields that the user can’t edit aren’t updated. The flow doesn’t execute the fault path.

            The operation fails.

            No fields in the operation are updated. The flow executes the fault path if there’s one.

            Notification when one or more fields aren’t updated No notification is sent to the user or admin to indicate that some fields weren’t updated. The admin receives a flow error email with full details.
            Compared to a Create Records element where you chose to use separate variables, resources, and literal values Inconsistent Consistent
            Compared to an Update Records element, where you chose to set fields individually Inconsistent Consistent
            Tip
            Tip We recommend disabling this preference so that you always know when a flow doesn’t set all expected field values.
            1. From Setup, enter Automation in the Quick Find box, then select Process Automation Settings.
            2. Select or deselect Filter inaccessible fields from flow requests.
              If your org was created in Winter ’17 or earlier, the preference is enabled by default. Otherwise, the preference is disabled by default.
            Example
            Example

            A flow updates several fields on an opportunity by using a record variable in an Update Records element. At run time, the flow tries to update the Acme account on behalf of your user. The user can edit Stage and Close Date but not Amount. As a result, the flow doesn’t have permission to update Amount.

            • If Filter inaccessible fields from flow requests is selected, the flow successfully updates the account, but it only updates Stage and Close Date. The flow doesn’t notify anybody that Amount wasn’t updated.
            • If Filter inaccessible fields from flow requests isn’t selected, the flow fails to update the account. The admin receives a flow error email. The email includes this error.

              INVALID_FIELD_FOR_INSERT_UPDATE: Unable to create/update fields: Amount

              That’s API-speak for “The running user doesn’t have permission to edit the Amount field.”

            Warning
            Warning If you change your org’s selection for this preference, use a sandbox to test how the change impacts your flows. Consider following the same process as you would for a critical update.

            See Also

             
            Loading
            Salesforce Help | Article