Hi Jon,
We've found that hierarchy node details are actually stored as code sets in the database tables and will query those on occasion. So you can use the Hierarchy Name to search the table B_CODE_SET and join the CODE_SET_ID to the B_CODE_SET_DETAIL table. Each node in the hierarchy is stored in the CODE column and you can see the parent info in the PARENT_CODE column.
I'm questioning if you need to write a special validation rule for this scenario you're describing though. I've noticed for us that when a user uploads a node value via spreadsheet, if the value doesn't match exactly, the system will automatically raise a "code set" type error without us needing to make a special validation rule. For example, in the screenshot, the Hierarchy Node value should be "Outdoor Table + Shade" and when the user uploaded "Outdoor + Shade", the system already recognized that value isn't in the hierarchy.
But maybe if you have some additional logic that needs to be included along with the hierarchy node, then it would require a special validation rule.
Hope this helps!
Josh
------------------------------
Joshua Swett
Steelcase, Inc
MI
------------------------------
Original Message:
Sent: 05-03-2023 12:49
From: Jon Varo
Subject: Creating A Validation Error If A Hierarchy Catalog Record Node Value Doesn't Exist In The Hierarchy Itself
Hi!
How can I find the hierarchy information within SQL so that I can compare Node Values in Hierarchy Catalog and trigger an error if the Node Value doesn't match what is in the hierarchy itself?
Thanks,
-Jon
------------------------------
Jon Varo
Fender Musical Instruments Corporation
AZ
------------------------------