Forum Discussion
Modern List Item UI Causes Data Loss
Ideally, if it was possible. An event that when that screen closes you get a prompt to save your changes, or at least some way when you click new again the previous box showed back up where you left off.
- I've got a similar issue with one customer, where they edit a list item - changing 2 values, but the item is actually updated twice - so a SharePoint Designer workflow runs twice, resulting in a duplicate email notification. They only noticed it when they moved from Classic to Modern.
Hi Rob, you are referring updating metadata using the information panel (not the Edit All form) where each field update generate a save? Yes, this is a nonsense especially for workflow/flow and also versioning (it generates new versions on each column that is saved). They should only provide the edit form (Edit All) option… But like @Anne O'Day says, when you edit with the edit form (or newform) , you need to be carefull not clicking outside the form or you will loose your updates (form will close).
Martin.
Rob Ellis wrote:
I've got a similar issue with one customer, where they edit a list item - changing 2 values, but the item is actually updated twice - so a SharePoint Designer workflow runs twice, resulting in a duplicate email notification. They only noticed it when they moved from Classic to Modern.I think I've heard of that ... does using the "edit all" button help? It opens all the fields at once, still in the modern experience but instead of doing cell by cell updates, it behaves more like the classic form.
This issue is still going on I believe since I experience it since today that when opening the editor and touching a field to change it's value, two other colons loose their data. Funny it are always the same two colons loosing data and it are both Choice fields.
When I open the editor and immediately select edit all this is not happening.
Is there already a work around for this? It is quiet hard to make all contributors to the list use this solution with the edit all option, especially when they are only viewing the data and touching a field without purpose to change it.
The best workaround I've found is to go back to classic mode, but I have a feeling that's not going to be allowed for much longer.
I've tested again PowerApps and it caches the info (in my first test I think I've concluded to fast and only notice the panel was closing) if we click outside the panel. So using PowerApps custom forms is a potential solution.
Note: It caches info for new and edit forms.
Martin.
- It'll be around for years. They will iron this out before classic goes away.
Another alternative could be just fire up powerapp form for the list and have that input the data.- If modern experience could support the "Launch in a dialog" advanced option where if enabled, this would behave as it is right now, and if not, it would redirect to the full window form... I can't understand why this would be so hard to implement... I see this issue as a major failure for the modern experience (with the document sets still not supported in modern UI). Switching to classic make you loose some very useful features... This is a nightmare for a consultant trying to provide guidance to his customers... I hope Chris McNulty could give us some feedback on this issue.
