I have a form with several fields and there is the possibility of times where 2 people can be reviewing the same record at the same time. For example, if I have a date field set to today's date and user 1 changes that date to tomorrow and saves the record, the field behaves as intended and updates to tomorrow. If user 2 updates another field and saves the form after user 1, that date change is overwritten with today's date as that was the initial value and what is current on the record (as per the view on user 2's screen)
Is there a way to code an IFTTT macro to only update fields that have changed? This would help us avoid collision.
This is the normal behaviour, as users work with data snapshot and send their version of data for submission. This happens everywhere.
Last submission wins
The solution might be to use individual edits (enabled via "view" macro) or add a "version" field type (definition) to enable the form to be versionable which makes the second submit fail, telling the data has been updated in between and needs to be refreshed first
Thanks for the quick reply and sorry for the late response.
Sounds like the version field type would be my best bet to prevent collision, however, I've never used that field before (we recently updated our Confiforms version finally) and am wondering if it's as simple as injecting that field into my form? Tried looking for some detailed documentation of a version field type and how to use it but was unsuccessful.
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events