A Process is not allowing save of Record when it does NOT meet the Process criteria
Last updated 2015-09-03 ·Reference W-2424865 ·Reported By 83 users
User's with a Process that has criteria referencing a foreign key field (cross object references) are running into an issue when saving a record that does NOT meet the criteria. They will get an error and will be unable to save.
The record couldn’t be saved because it failed to trigger a flow.
A flow trigger failed to execute the flow with version ID 30100000000XXXX.
Contact your administrator for help.
1. Create a Process on an object, Account for example.
2. Create criteria that reference a foreign key field, "Account.LastModifiedBy.Profile.Name = Standard User" for example.
3. As a User that has a Profile that is NOT "Standard User", modify or create an Account record (or record on whatever object is being referenced).
Even though your Profile does not match the criteria (you're not a Standard User), you are still unable to save the record because you get the above mentioned error. The Process is still trying to trigger even though the criteria is not met.
The current workaround is to create a text formula field that pulls in the value of the foreign key field you are trying to reference in the Process criteria. You can use that formula in the criteria of the Process.
In the example above, on the Account object you would create a text formula field with the syntax $Profile.Name.
Reported By (83)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.