break inheritance for custom field location
J
Joseph Plaizier
If a custom field is shared at a space or folder level it shows up for everything under it in the hierarchy, which is great. A big problem that we have is that if we want to remove it from a single location that's under this inheritance / flow down effect we have to remove it from the location at the higher level. This creates big problems for other locations, automations, dashboards, views, filters, etc. that may rely on that field still.
It would be wonderful if we could remove a custom field from a lower hierarchy level without impacting other locations at or even below it.
I have attempted to try to show what I mean by diagraming an arbitrary hierarchy structure. If I remove the custom field from My Space or even move it to Folder 1 or 2 I break the other locations that are using it. I would like to be able to just remove it from List 4 without breaking the other locations that still use it.
My Space (custom field applied here)
---- Folder 1 (filters and automations use the field here)
---- ---- List 1 (formula field uses the field here)
---- ---- List 2 (form uses the field here)
---- Folder 2 (dashboards use the field here)
---- ---- List 3 (automations use the field here)
---- ---- List 4 (need to remove it from here)
Log In