A simple addition to help us with users adding/modifying features via an Experience Builder web app would be to add a SAVE option that forces the commit to our database. I've seen an idea to auto save as well (which also would be a great addition) but we are having issues with losing features during edit sessions in Experience Builder web apps. We are not sure where the disconnect is between the edit session in the web app and the commit to the enterprise geodatabase. Having a SAVE option that would then bring up the saved records in the edit form when a user is finished for final review would be helpful. At present users are losing some of their edits and we have phantom features that seem to cache in a user's session, but no data is pushed to the backend enterprise geodatabase. After a refresh of the app - the feature disappears and frustrates our users.
