In the Global Update function, "File" > "Save (Server)" should prompt the user to confirm if they attempt to overwrite an existing search.

Write-protection of specific saved global updates on the sever would provide additional assurance against data loss for very important/complex items.

Idea Value
This would mitigate the risk of accidental data loss due to user error. Sophisticated searches may be saved to the server, the loss of which may require substantial work to recreate accurately.

As of Sierra 5.4, if a user working with an unsaved session accidentally selects "Save (Sever)" rather than "Load (Sever)", the "Save as..." dialog appears. If an existing update file is selected, it will be overwritten without a confirmation prompt.

This behaviour makes sense after a set of saved parameters have been loaded but appears to be problematic at the start of a global update session.

In particular, if the user makes this error immediately after accessing Global Update, the saved search is overwritten with a blank search (ask me how I know!); and in general, because Sierra does not prompt to confirm overwrite of a saved global update with an empty one having no parameters, it is easy to wipe out existing saves.

The SDA UI could also potentially be tweaked to mitigate risk of this error by changing the order of entries in the "File" menu.

Current state (grouped by Local/Sever, with "Save (Server)" and "Load (Server)" adjacent):Save (Local)Load (Local)Save (Sever)Load (Sever)Save as (Sever)

Proposed state (grouped by Load/Save with separator between them):Load (Local)Load (Sever)-----------------Save (Local)Save (Sever)Save as (Sever)