When viewing the system DB I find multiple ASSET tables and have yet been able to determine the key relationships between ASSET/ASSET_ASSOCIATION/the many ASSET_DATA_X and so on. What are the 'key' fields required or to use when building queries that will tie them together? Should I be concerned with ASSET_HIERARCHY or ASSET_FIELD_DEFINITION????
Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


It depends on the sorts of queries that you're trying to write. I have not bothered with heirarchy at all, you wouldnt unless you were using nested assets. Field definition however can help you find out what sorts of fields are where and allow you to search by text name of the field as opposed to the field type/id. Its a little messy but once you get your head around it reading it is okay.
Looking at the asset_field_definition table and its contents will help you figure out which tables relate to eachother etc.
Answered 03/22/2012 by: Roonerspism
Second Degree Brown Belt

  • If you like throw me an email for some extra info.
Please log in to comment