I think this new behaviour can break existing code and be a real pain in Document Pages for example...
I don't think the solution should be an administration setting... and less that it should be available only OnPrem...
As BC developers, I think we will need a new DelayedModify property in Pages and PageExtensions objects to revert this new behaviour to the original one when this break our existing code.
Comments
There is already a DelayedInsert- Property which should be enough, because modification is afterwards mostly done by Code, which saves records as required.
Category: Development
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team