Auto Save (or some other measure) to prevent table errors.

We have a big organization within VIP and we are seeing issues with "Table issues"... Errors that happen when one person is updating a voyage and someone else is also trying to update something else connected with that same voyage.

When table errors occur, they prevent updates from saving, damage the user experience, and trigger re-work. While we tell our folks to refresh and save often, it's not enough. Our users regularly see these errors.

Suggesting that Veson look into auto saving or other techniques to minimize the number times that users run into table errors and/or eliminate them altogether.