I am receiving an error with one of the numbered lists - "You are not authorised to move this entity".
ONLY non- workspace admins are getting this error.
They are able to add items to the list but they cannot put the Parent against the Parent field.
I have checked the action and the Parent field is being correctly mapped in the action - as mentioned in this thread.
The user has access to the source module view and is able to see the data that is being used for Parent mapping. The user also has access to the list in Roles -> List section and the Roles-> Actions section for the action being run.
Also, this numbered list has a parent/child relationship and the top ancestor list in this chain has selective access. The user has Total Company access WRITE access to this ancestor (Top level element) list.
Can anyone identify the issue if they have seen this before?
@shreyak.garg We too are facing the same issue. Just to further shortlist the two differences between you and the user - in our case both the user and the WA have SSO enabled. So, essentially, everything else being equal - being WA seems to resolve this issue.
Please do update this thread in case you happen to find the cause/solution.
We have a situation where we ended up in the same point as in your last comment - after going through all the steps mentioned above, everything seems to be mapped correctly and the only difference between users getting the error or not is the workspace admin selection.
Is there another reason that you were able to identify in your process?
@shreyak.gargIf I'm understanding you correctly; you have a numbered list with selective access enabled. There are also orphans in the numbered list. The action which is causing errors is mapping parents to these orphans.
Anaplan correctly denies access to orphans in a list with selective access enabled to non-WSA users. This is why the action is causing the error.
I suggest either mapping the parent in the same action that is currently creating the orphans. Or alternatively, the orphans being created currently should be mapped to a temporary dummy parent. This will allow all users access to the orphans and the last action should successfully remap the 'orphan' to the desired parent
Is it possible that the user running the action does not have access to the parent that the child is currently at.
The user I'm testing with does not have access to P3, the parent of C6 and is also not a WSA
When this user runs an action to update the parent of C6 as below he will receive the "Unauthorized to move this entity" error
The difference between my original answer and this is that the problem child is not because it is an orphan but because it is currently mapped to a parent which the user cannot access. When the user tries to remap any child to any other parent, irrespective of whether he has access to the destination parent, he will be unauthorized to make the change.