This content has been marked as final. Show 6 replies
Use the validation class "UniqueProp" and give it the Description property as a parameter.
Thanks Richard. I actually do have that validation in place as well to validate that the description is unique among all nodes in the hierarchy. What I need now is slightly different - I want the node name to also be unique among all description.
Here are the 4 validations that I must implement. #3 is in question.
1.Check if descr matches with an existing node name (Custom Validation) - Done
2.Check if descr is unique among descr of other nodes (Unique Prop Validation) - Done
3.Check if node name matches with an existing descr - ???
4.Check if node name is duplicate (system default) - Done
Tricky, not sure the possibilities with in DRM, checking further,
just few thoughts below,
1. May be mainatain all descriptions in a Table and run a query before a node gets created ( external process to DRM)
2. Why dont we maintain a unique prefix for the node name?
You can use this validation class with Name(Abbrev) and Description as the parameters: Unique 2 properties within a version, but it checks the entire version and not just the hierarchy you are currently in. In general that's even better but it may not match your use case...
Hi Try this formula :
hiername will be name of hier from where u want to check desc ,if abbrev and description gets mattched will return node name.
Sandeep, that's not how HierNodePropValue works. It returns a single value and is not a search function that will evaluate multiple nodes.
Your sample formula will only check the description of the current node [abbrev()] in the other hierarchy, and since Description is a global property this will always be a match.