I hope that you are doing well!
I have a problem with my flow, when I try to run it as an user not administrator. I got this:
Error element Update_initial_individual_Risk (FlowRecordUpdate).
The flow tried to update these records: null. This error occurred: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY: insufficient access rights on cross-reference id.
I found here a lot of similar questions and made a lot of changes, but it's still not working.
- I added permission to all fields
- all picklists are available for this record type
- related objects can be edited and viewed
Do you have an idea what else I need to do?
Resolution for INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY Error in Flow
While working with an Autolaunched Flow to create a Case record, I encountered the following error when executing the flow as an Einstein Service Agent:
> Error:
INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY: insufficient access rights on cross-reference id
This issue did not occur when running as an Admin, which indicated a permission or access issue specific to the profile or permission set of the non-admin user.
🛠️ What Helped Resolve the Issue:
1️⃣ Provided Access to Record Types in Permission Set
The Case object has multiple record types, and the flow was attempting to create a record with a default or specific record type.
The Einstein Service Agent's permission set did not have access to the required record type.
✅ Fix:
Navigate to Permission Sets > Object Settings > Case > Record Types
Ensure all necessary record types are enabled for the permission set.
2️⃣ Granted Edit Access to All Fields Used in the Flow
In the Create Records element of the flow, several fields (including standard and custom fields) were being populated.
Some of those fields (like WorkId, etc.) were not editable by the Einstein Service Agent.
✅ Fix:
In the permission set, go to Object Settings > Case > Field Permissions
Ensure all fields used in the flow have Read and Edit access.
3️⃣ Removed the 'Work ID' Field from the Create Element
The WorkId field is already included in the case record, without knowing this, i was explicitly using work id field while creating the record.
So, I removed it since it's already there by default.
✅ Fix:
Simply removed the WorkId field from the Case record creation mapping.
After this change, the flow executed successfully.
