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 on All Ancestors to fails to stop Remove action

edited Aug 30, 2024 3:19PM in Enterprise Data Management 1 comment

Summary: Have Validation that checks a base account node is in two key Hier, by counting hits in AllAncestors where "name starts with"… "Global Accounts (" = 1, and equals "Cash Accounting" = 1 - All ancestors does not seem to update on a Remove action in request (even if 'visualized' rather than 'committed' state checked). Note "Global Accounts " is split into (P&L) and (BS) suffixed top nodes.

Content: I had assumed that a Validation could be used to deny someone using request to remove a shared node from under either of Two key TopNodes, and use AND() of AllAncestors with a Count=1 for each would work… and it does work when Validating static viewpoint (as long as "Visualised" is not set)… but neither works within Request context, if I do a Remove Action and have a Text derived field showing AllAncestors>toTextList>Joined it does not change until after submitted & committed.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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