Identifying unused properties on object for cost reduction on indexing post write-back?

[rovshify]

I have some objects that have 100+ properties mapped to them from the backing datasets. Whoever worked on them earlier mapped all of the properties on the objects from the data.

These objects also support edits and thus post any edit, the whole object indexes, and this increases the cost for me. I’m trying to get rid of the unused properties in the downstream resources/functions.

I intend to delete these properties from the object (let me know of any other suitable actions), but don’t want to break anything.

But as these objects are used in 20+ workshops and have many functions associated with them, I was wondering if there is an easy way so that I could know which properties are being used in downstream workshops.

[tmiskow]

Hey @rovshify !

This is supported in Ontology Manager and Workflow Lineage applications.

In the properties view in Ontology Manager, you can show a “Dependents” column to check the count of dependent resources or open the “Dependents” tab in the sidebar to show the list.

In Workflow Lineage, you can see the count of dependents in the properties list and hover to see the count

Keep in mind, though, that we do not yet support all types of resources as “property dependents”, so some usage (e.g. Slate dashboards) may not be reported. Workshop reporting should be fully reliable, though.