Starting off this massive debate: (144) Yammer : Dynamics 365 Business Central Development : View Conversation

I have another solution for this problem.

The Problem: we need to show the information that was Saved accurately without interfering with the existing customers experience.

At the same time we want to expand on the functionality of the system to assist users not losing any data they input.

The question we need to ask ourselves is Why? Is this because we don't want users to lose work in progress if we get an error? If so, read ahead:

One solution I imagine could be (and I can come with others as well if you'd ask me - open to discussion):

• Would the (Edit in progress) not be sufficient and getting it reset to Saved when a commit in the database happens? If not, this could be further extended as follows:
• keeping the BC v20 record behaviour the same (no modify execution after each field changed)
• Saving the edited fields (before the v20 onmodify is triggered - user leaving the record, etc) in a generic table (that has a user/sessionid/record ID/FieldID as Primary Key plus timestamp/unsaved field values and a Currently Editing flag for every table and field). This can be kept outside the actual database (another helper azure db tied up to each BC database, with a retention policy driving the clearing of old data after x months). When the record modify is executed, this data would be removed automatically.
• when anyone goes back to the record, a factbox could show the data in this table and users can apply these previous InProgress changes to the record, or remove them entirely, or the will simply be removed when the record is deleted (ex: sales header/line transformed into a posted document).
• This would allow users to continue working with the same experience until v20, while at the same time accurately having a status displayed at the top screen and with the added benefit of having collaborative work with the other users.

Further to this (the collaboration value of this approach):

• a click on the userID could open up a Teams window with the context and this would allow the current editor of the record quickly chat to their peer about the correct value in the record