Learn about Redwood and be one of the first to join the conversation

Visit Redwood Community
Validation Rules for alternate hierarchies to not insert / update node — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Validation Rules for alternate hierarchies to not insert / update node

Question
15
Views
0
Comments
edited Dec 5, 2020 3:24PM in Enterprise Data Management

Summary

Validation Rules for alternate hierarchies

Content

Hi All,

we have 4 top nodes out of 4 , 2 are main/ primary  Hierarchy which should have unique members and rest 2 hierarchy can have / repeated nodes or parents more than one time. we want to build validation rule to the primary Hierarchies to prevent the user to stop add, insert or move the node if that is already exist in Hierarchical

i have create a validation at Hierarchy set level but its not working efficiently .

 

{
if (node.ancestors.any(ancestor Node => ancestor Node.name.matches("(T)|(R)"))) 
{
if (node.locations.count(location => location.name.matches("..*")).equals(1)) 

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!