Current state & problem
Following a recent UI update, the "Delete Import Source File" option was removed from the command bar on the Data Import list view. Users are now forced to open each individual import record to access this delete button.
While we understand that the original intent of this change was to act as a fail-safe (preventing users from accidentally deleting the source file and its associated error logs), this UI control has created a significant operational burden for end-users who frequently manage data imports.
Business impact
End-users now have to perform multiple unnecessary clicks (open record -> delete -> navigate back to list) just to clean up routine files. This drastically reduces productivity and increases the operational overhead for daily data management.
Logical evaluation of the current design:
From a system design and operational standpoint, the current implementation raises several concerns:
- Design consistency: The risk of accidental deletion is not limited to source files. The "Delete Imported Records" action carries an equal, if not greater, risk of data loss. However, that option is not restricted and is still accessible from the list view. Hiding only the source file deletion lacks consistency.
- Validity of the UI measure: Forcing users to open a record is a heavy-handed UI control. It is unclear if this is statistically more effective than standard UI fail-safes.
- Trade-off balance: The severe increase in daily operational burden (extra clicks and time spent) heavily outweighs the intended risk reduction effect.
Proposed solution:
We request that Microsoft restores the "Delete Import Source File" button to the List View command bar to ensure a smooth user experience.
To maintain the fail-safe mechanism and prevent accidental log loss, please consider another solution, for example: a clear Warning/Confirmation Dialog (e.g., "Are you sure you want to delete this source file? Doing so will also delete the associated error logs.") upon clicking the button from the list view, rather than hiding the button entirely.
Comments
This is impacting the user experience when people use the platform. It would be helpful to improve this behavior and deliver a smoother experience for users.
Category: Long Term Retention CE
wonderful idea!
Category: Long Term Retention CE
