Collision radar

When a form opens, see whether someone else is changing the same record in another update set.

A Pro tool. Two developers changing the same business rule in two update sets is a collision the platform only reports at preview time, after both have moved on. Whichever set is committed second quietly wins.

The radar says it when the form opens, before anything is saved:

Abel Tuter is also changing this record, in update set STRY0042 · 2 hours ago

The names link to the user and to the update set. /radar in the palette asks again on demand.

What counts

• Only sets still in progress. A completed set has already shipped or been abandoned.
• Not the set you are in now. That is where your own save goes, and a set you share is collaboration, not a collision.
• Your own work elsewhere is said apart. A set where you were the last to touch the record gets a quieter note: it is not a clash with someone else, but it is still worth knowing before you save the same record into a second set.

What it costs the instance

One read per form you open, of the update records for that record. A record no set has ever captured, which is every incident, comes back empty and nothing more is asked. Only when something is found does it read two more things: your current set, and the people's names.

On Free and Plus the radar stays silent.