There is a point in the documentation for Flow Triggers (no indication that this is applicable to a standard Flow) which I'm thinking MAY be relevant). It states "Flows that are launched from workflow rules are governed by the per-transaction limits already enforced by Apex.". There is a large, highlighted warning with giant red exclamation point indicating "You must configure at least one filter, or you will update all the records for the object." - so SF documentation essentially indicates that it's possible to update ALL records in an object, regardless of how many records there are. There are two interesting points in the online documentation. I am unable to find documentation that definitively indicates that there is a limit for Record Updates in a Flow. It is launched from a custom button because it requires a variable assignment for the first step:ġ) Record Lookup - take the variable from the launch URL and get the record NameĢ) Screen - display the record Name and ask for input of a date fieldģ) Record Update - update all child records of the variable with the date entered in step 2 But I can't find documentation to support that guess, and besides, doesn't a 200 limit on record updates seem VERY low? My first guess was that there is a limit for Record Updates in a Flow. My Flow with a "Record Update" is only updating 200 records.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |