We’ve had several experiences where layout configurations were changed in an app using the new record layout, but those edits were not saved properly.
It seems that some field labels/config changes are intermittently not sticking,
The most common issue is with field names and field labels changing.
Sometimes it’s odd because the changes appear to work temporarily. We’ve even built automations and we could see the updated field names in the automation choices. But then later on (hours or days later) the changes had reverted back and multiple toggle fields showed the same cloned field name making it impossible to differentiate one from the others.
Recently we saw this error message pop up:
This short video details some examples of what we have seen:
https://www.loom.com/share/65201cb5b249418db8ddc9a051151778
We have tried to be extra careful to not have more than one user in an unlocked edit mode for any given app at a time.
@Leo can you share any details on what is an expected outcome if two people have an app unlocked at the same time?
Lets say that two users both have the same app opened in an unlocked state at the same time.
Imagine that user one makes edits, locks it, but then user two makes different changes and locks their instance of that app shortly after. Would we expect changes from user one to be overwritten or reverted back when user two hits the lock button?
Is there a way to see or know if another user has an app in an unlocked state?