Skip to main content

In a live environment we have a scenario to update permissions for more than 500 list items. The list has nintex workflow running when item is modified. We were planning to run pnp powershell script against the list items to update the permissions. Using the "-SystemUpdate"  flag in the script makes sure the item updates without creating a new version and ideally not triggering the workflows. On comparison we found that MS power automate works as expected (does not get triggered) but Nintex workflow gets triggered

 

Is there any way we can using the power-shell script without triggering the Nintex workflows.

 

Note: We do not want to turnoff the workflows and cause application downtime

When you made a call of Set-PnPList item (event with a SystemUpdate) you are making a update on your item, so it is normal that the WF starts.



 



I recommend you to :



Add a conditional strat on you Workflow to avoid starting when the Updator is the user who run the script. (in that way, any modification made by you user will not kick the workflow). After the script is finish don't forget to remove this conditional strat.



If you use this way, don't forget to enable the feature "Workflow can use app permission"



 



Or,



 



By script



1- Disable "start workflow on Modification"



2- Made you Updated



3- Enable the "start workflow on modification"



Run you script in the night to avoid users modifications.

Yup we have the second option currently as a plan. But that involves application downtime since workflow will have to be disabled. We were looking at an option where that can be avoided.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings