When you run the Account Subledger job in Salesforce Nonprofit Cloud (NPC), the Data Processing Engine (DPE) definition may fail.
The system returns the following error: "This run of the Data Processing Engine definition couldn't process the data. The user doesn't have the required writeback permission. Make sure the user has the required permissions and try again. Error Code: USER_ERROR, Error Type: USER_ERROR, Definition Validate Failure."
This error occurs because the DPE writeback target requires the running user to hold both the Data Pipelines permission set license and object/field-level write access to the target object. This requirement applies even when the user has the Financial Services Cloud (FSC) or NPC feature license.
This missing access also affects a related symptom where you cannot activate a Data Processing Engine definition, including cloned out-of-the-box definitions with no changes. Affected users typically run the job manually or schedule it under a dedicated integration or admin user.
Grant the running user (the user who runs or schedules the job) the correct Data Pipelines access and writeback permissions based on the specific cause below.
Navigate to Setup.
Go to Users and select Users.
Open the record of the user who runs the Account Subledger job.
In the Permission Set License Assignments related list, click Edit Assignments.
Enable Data Pipelines and click Save.
In the Permission Set Assignments related list, click Edit Assignments.
Add the permission set that grants Data Pipelines access (the permission set containing the "Data Pipelines" and "Author Apex" / writeback system permissions).
Click Save.
Identify the writeback target object by navigating to Setup.
Go to Data Processing Engine and open the Account Subledger definition.
Note each object named in the Writeback nodes (for example, Account Financial Summary and related subledger objects).
Navigate back to Setup and go to Permission Sets.
Open the permission set assigned to the running user and click Object Settings.
Set Object Permissions to Read and Edit for each writeback target object. Set it to Create if the job inserts new records.
In the same Object Settings screen, set Field Permissions to Read Access and Edit Access for every field the definition writes to.
Click Save.
Confirm the user activating the definition has the Data Pipelines permission set license and permission set outlined in Cause 1.
Navigate to Setup and go to Data Processing Engine.
Open the definition and click Activate. Activation will succeed once the Data Pipelines access is in place, and the DPE will appear as a selectable action in Flow.
Assign the Data Pipelines permission set license and writeback permission set only to the single dedicated user who runs or schedules the job. Permission set licenses are limited and should not be assigned to every system admin.
Set that specific user as the running user on any scheduled run so the job executes with the licensed identity.
Navigate to Setup and go to Data Processing Engine.
Open the Account Subledger definition and click Run.
Verify the run completes with a Success status and writes records to the target object without the writeback permission error.
005389016

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.