|
|
I recommend reviewing the placement, accessibility and prompts to ‘Update a database’ . The onset of backwards compatibility within software versions is resulting in unintended database updates. It would be beneficial to explore ways to make the ‘Update database’ command less easy to select inadvertently, perhaps by adjusting its placement, removing auto prompts and requiring an extra step for confirmation
Thank you for your feedback and thanks to those who voted.
We understand the concerns regarding the potential for unintended database updates, particularly when working across different software versions. The Update Database command already includes a warning message that clearly explains the implications and risks of proceeding, including that the update is a one-way process and cannot be reversed (see screenshot below).
We believe this provides an appropriate safeguard, ensuring users are informed of the consequences before choosing to proceed. As such, we do not currently plan to introduce additional confirmation steps or change the command's placement or accessibility.
We appreciate you taking the time to share your feedback and will continue to consider usability and safety as part of our ongoing product development.
