Trigger bundle should be visualized

[ta-aoki]

If you had this trigger action working fine in your App

and if you added this middle action,

now your App will not work correctly anymore (the current record is written to the “previously_updated_ID” field), because you have separated the trigger bundle into two pieces.

Triggers

This would be difficult to find out and trouble shoot.
Please could you visualize the bundle in the trigger editor so that we can see adding something there will break the bundle.

Significant Updates to Knowledge Base article on App Triggers

If I understand/guessing correctly, if I see an action storing aggregation value to a record place holder the value stored will be … If the actions are bundled, the value is taken before the the create/load action If the actions are not bundles, the value is taken just before the store action. I think this is counter intuitive. To make this intuitive, I think the trigger editor should at least visually show which actions are going to be bundled, and warn the app builders by highlighting the …

[ta-aoki]

For those who might be interested, I used this Table Query

and this Table Aggregation

to get the ID of latest updated ID. (I did not know we could use “Mode” for a Text type field)