On a on prem 2013 environment, I have backed up and restored a site collection containing Nintex Workflows.
Now I'm checking the workflows on the restored site collection and have to change a groupname in the Set Item Permission action.
It can find the groups, using the picker function but when I save the action it shows any attention mark. Hoovering the action, it shows the message:
Error validating configuration
I've already deleted the permission rows in the action, leaving one and then it saves correct
When I add a second or third permission, the attention mark shows and removing the last added permission doesn't solve the problem. Even with only the first added permission, the attention mark stays.
It doesn't seem to happen on Current Item, but only on items within another library.
I've also removed the entire action, published the workflow and added the action back in, but htat only worked once.
Any idea what causes this issue and how to solve it?
Thanks in advance for your support!
I think I have the same problem. I also tried to create a new workflow with a new Set item permission (as a site workflow). First time saving and Publishing works. When I open the workflow again and edit the "set item permission Action" the error: An item with the same key has already been added - occurs. Which version do you use on prem? Our version is 18.104.22.168-International.
I ran in same issue when creating item level security for items and documents. Both of them, list item and document, are in different libraries. Item has an "lookup" to particular one document from doc lib. Now when in Nintex I try to assign for document in another lib same permissions (multiple user groups depending on case) as current item permissions are set, i run at error "key has already added".
I couldn't find any particular procedure to replicate this. I couldn't though copy and re-use these through snippets, copy and re-use already existing action on the workflow that changes (adds more) document (non current item) permissions, nor couldn't manually create each of doc lib (non current item) permission actions. But, I could re-use current item permission actions and only change the target from current item into document lib item. This didn't give errors for some reasons.
There seems to be something wrong in permission granting. I was wondering if it was possible somehow to use current item permissions and replicate them as a whole to another list or library?
In the actual Version 3.1.8 they resolved an issue that sounds like the issue discribed before:
Resolved an issue when editing a Set Item Permission for a second time gave the error message "An Item with the same Key has already been added" (38672)
So far we have not tested the new Version.