Hi there,

The simplest solution would be to move your workflow over from List B to List A.

When building cross list workflows it is always best to start from the point of action, in this scenario that is an action in List A that affects List B.

To me the workflow should work like this.

Workflow on List A starts when an item is created and updated. (depending on sharepoint version) you can set start conditions to check if the responsible persons have changed.

when a change is detected then update the Sharepoint item permissions in List B.

If List A item is ever updated the workflow will run again, If you need to perform actions on the List B list item with context you could just start a workflow using the List A workflow as an action point.

An alternate and more efficient method would be to merge the lists together, take all of the fields from List A and make the columns on List B, Use the list settings to remove them from the forms or just never add them to the Nintex form, Then create a new list view that shows the fields you need and set permissions on the list view to only be available to admins, this requires more work but might make any workflows much more simple, personally I would go with the first option.

Hope this helps

Jake

Hi Jake

Thank you very much for your answer. 

The option to merge both lists together never came to my mind. I may give it a try.

Regarding option 1, I would also like to note that List A, where only the responsibles are maintained, is quite static. We rarely have changes there. List B, on the other hand, is the main list, which contains an extensive form. That means in List B new entries are constantly created and edited, which then must get the correct permissions. How can this be triggered if the workflow is running on List A, where changes are rarely made? I may not understand your approach correctly.

Thanks & best regards

Markus