Asset Object Attribute Dependencies

[Rob Terakedis]

I'm building out a Schema to track knowledge assets (videos, documents, labs, etc).   In the schema, I have 3 sibling Objects -> Knowledge Domain (related product), Use Case, and Knowledge Asset.  The "Use Case" object also has a child object called "Related use cases" (i.e. sub use-cases of the parent).

The way I've set these up is as follows:

• Use Cases have an object reference to Knowledge Domain
• Sub Use Cases have object reference to Knowledge Domain and Use Case
• Knowledge Assets have object reference to Knowledge Domain, Use Case, and Sub Use Case.

I'm trying to figure out how I can tier the 3 object references on the Knowledge Asset configuration -> Choose the knowledge domain, then show only the Use-Cases that refer to that specific Knowledge Domain. Then if sub-use cases are tied to that specific core use case, those would only be possible to select.

Do I need an AQL query in the "Filter Objects" for the Object Reference that will limit the available options?   Or have I possibly not done the object references correctly?

Thank you for a point in the right direction!

[Steve Y]

Rob,

Do you have your attribute reference set to Dependency, or Reference? Dependency will enable your fields to present the cascade effect you're looking for. At least they did for me.