Also a very annoying :ladybug: when entities are r...
# gooddata-cloud
a
Also a very annoying 🐞 when entities are removed from the LDM there are inconsistent behaviours. 1. its hard to track down all the different attributes that are affected to mitigate/migrate 2. breaks Vizs completely making it hard to recover them 3. when being used in the dashboard level filter it does not allow you to save a dashboard ☝️ ☝️ ☝️ This one is particularly annoying to resolve - STEPS 1. Go to the affected viz (you have to download the dashboard JSON to reverse engineer it) 2. click on the affected viz filters 3. toggle them all on off - then 🙏 and save
m
Hi Ashley, thank you for bringing this to our attention. When removing entities from the LDM, you will get a list of entities that are dependent on the object as a warning message; the entities in the list will get broken and will have a cascading effect on any related objects, e.g., in your case, the dashboard that contained it could not be opened. I am afraid that it would be hard or unpractical to list every single entity that will be affected indirectly, if too many, you may reconsider its removal or even redoing the workspace. But I understand that there could be corner case in which a complete list would be helpful. Just so you are aware the issue has been brought up a few times, e.g.: https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1702919910308869, and this is not a bug in general.
I will be glad to share this as product feedback on your behalf. Could you please share a bit more about your use case or what you are trying to achieve? For example, why you need to remove entities that have many relationships with other entities, how often, or how reverting the changes by restoring the workspace is or is not feasible? Thank you for any details.