<x-zendesk-user data-user-name="Suhas Kotha">365021274968</x-zendesk-user> Looking for a follow up on this as its a big challenge for us going forward. I wrote up a better use case below. Im sure <x-zendesk-user data-user-name="Georgia Churilla">365242225527</x-zendesk-user> and others in the asset management industry have seen this problem as well.
As many in the Asset Management space are aware, the classification of 3rd part content is a big area. We have a vendor glossary where we store ALL of our vendor terms under a single asset type with the Vendor being the parent asset. The challenge is that each vendor has a different classification that we would like to attach to the vendor terms asset. I looked at using the cascading reference list and think it might work with one enhancement.
Right now for a cascading reference the parent object has to be another reference list (see below)

If this could be enhanced to allow the parent of the list be an asset type (such as vendor ) in addition to the existing ability to tie it to a reference list. This would be very powerful for us as we would be able to have dynamic classifications based on the vendor within a single asset type. Classifications in our case for Bloomberg, MSCI, LSE, Factset, TrueCost and many other data vendors
