HI There,
i have 15K items in the list and have a Site workflow to run against themt o change some metadata. I would like this to run in btaches, so say 100 at one time? how can i approach this?
please advise?
Run Site workflow in batches
+3
+23- Nintex Partner
Hi,
It sounds like you are looping through your 15K items.
You could add the following to your workflow to pause every 100 items.
Math operation looks at the loop count and divides it by 100.
If the calculation has zero remainder then the run If will run.
+3thanks for your message, i am new to nintex so can you please advise where to place these actions, before query list or after and what will be the type of loopcount and calculation variables? please advise?
my workflow screenshots are attached.
thanks
+3It would also be better to target id 1-100 at one time as this workflow will run for ages?
If user can direct the workflow to pick up id 1-100 at one time and than the next lot and than next.
What do you recommend? Thanks
If user can direct the workflow to pick up id 1-100 at one time and than the next lot and than next.
What do you recommend? Thanks
+23- Nintex Partner
Hi,
Hard to point you in the right direction based on a bunch of random pictures of your screen. Basically the actions I suggest would go at the end of your for each loop. The variables would be of type number as they will be holding a number.
Hard to point you in the right direction based on a bunch of random pictures of your screen. Basically the actions I suggest would go at the end of your for each loop. The variables would be of type number as they will be holding a number.
+3great thanks. i will give this a try but will that mean the workflow will be running until all the item have been updated?
+23- Nintex Partner
Yes the workflow will run until all will be updated.
If this is not desired you could record the last item id that was processed and then start the workflow again quering from the next item ID. This may not work as it will look like a recursive workflow to SharePoint.
You could maybe use a parent child workflow to avoid the recursive workflow issue.
If this is not desired you could record the last item id that was processed and then start the workflow again quering from the next item ID. This may not work as it will look like a recursive workflow to SharePoint.
You could maybe use a parent child workflow to avoid the recursive workflow issue.
+3Thanks, i am trying to get start IDs and end id in the start of the workflow but it runs find for smaller chunks not for larger number.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.