Improve the Cascade Feature - Allow option to only perform cascading updates
The out of the box Cascade feature is a useful tool but presents a liability for anyone using it due to the Cascade Delete option. If a user deletes a record, they may unintentionally cause other records to be deleted. For this reason, we typically turn the Cascade feature off in our implementations.
We recommend Archibus add options to only cascade updates and/or cascade deletes. If we can turn off the cascade delete option, the cascade updates feature will make the Archibus system more user friendly and usable -- avoiding errors when someone simply needs to change a Room Category or other background data.
Dan Miller
shared this idea
Available in 25.4 or later.
-
Dan Miller
commented
Hi Yin, thank you for making this change. It seems this update has now required the Cascade Changes feature to guarantee the Archibus system works correctly. For example, in v25.4, if you turn Cascade Changes off -- or just turn off the Delete component of Cascade Changes -- you receive errors when updating a Service Level Agreement. This was not the case in earlier versions of Archibus.
Is there any way we can have the ability to turn off the Cascade Delete option and still have Archibus work correctly? The Cascade Delete option is what presents the risk for customer data loss.