All Ideas

Idea Details

Post an Idea
This idea has been delivered and can no longer be voted or commented on. If you’d like to add to this conversation, please post a new idea.
590  Points voting closed
Delivered in Summer 18
Delivered in Summer 18

Process Builder - All OR None

Process Builders & Workflow

We have a Process builder  triggered on creation of some object and then it invokes the auto launched flow which itself is creating some related records.Whenever a single record is created it either creates the related records or gives necessary error why it doesn't create the related record.
But when we are inserting mass reccords lets say more than 100 the bulkified process builder will be triggered ( bulkification is done in recent release which is not a problem now) and it started creating the related records if any of the related record fails all the related records will not be inserted and we are getting error msg like this  : INSERT --- INSERT FAILED --- ERRORS : (ALL_OR_NONE_OPERATION_ROLLED_BACK) Record rolled back because not all records were valid and the request was using AllOrNone header,

We need the ability to update the AllOrNone header in case of process builder as this is much required. As we can perform our exceptional handling for the records which are not created.

It is much required for the admins so that they can fully rely on the process builder to create their own business process without writing even a single line of code.


Thanks,

· Flag

  • Upvotes
  • Downvotes

Ideas

Apps

from AppExchange

Questions

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



 

 

Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


 

Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.