-
Consequences when field is deleted
Currently, when a field is deleted from an environment, the system appropriately checks for dependencies, including system views (savedquery). However, it appears that personal views (userquery) are not being accounted for in the same manner.
When a field that is referenced in a personal view is deleted, the system does not handle this scenario gracefully. To improve the user experience and maintain data integrity, I recommend the following enhancements:
- Error Notification: Implement a feature that triggers an error dialog box when a user attempts to access or utilize a personal view containing a deleted column. The dialog box should clearly state that the specified column no longer exists in the entity, providing users with immediate feedback on the issue.
- Automated Cleanup: Develop a mechanism to automatically update the fetchXml in the userquery entity. This process should detect and remove instances of the deleted column, thereby preventing the creation of 'zombie' columns that no longer have valid references. This will help in maintaining the accuracy of personal views and reduce manual intervention.