cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
adiu
Nintex Newbie

Nintex and SharePoint Batch vs Commit pending changes

Jump to solution

According to a topic under Designing your Workflow - Commit Pending Changes Action NW2010 & NW2013 there are two batches - one for Nintex and one for SharePoint.

I have something like this (in SP2013):

Query list returns the old value. This is ok as Set field value is batched in SharePoint batch. But when I have something like this:

Query list returns a new value. Doesn't this mean that Commit pending changes committed SharePoint batch?? And according to the document I mentioned earlier this shouldn't commit SharePoint batch. How is that possible?

Labels: (1)
0 Kudos
Reply
3 Replies
murphybp2
Nintex Newbie

Re: Nintex and SharePoint Batch vs Commit pending changes

Jump to solution

As the document states

The "Commit pending changes" action is another point where a workflow will execute all its batch operations.

So when you add "Commit Pending Change" to your workflow, the workflow is going to execute all it's batches up to that point. Regardless if they are Nintex batches, SharePoint batches, or some other batch.  So the behavior you are seeing is expected. 

View solution in original post

Reply
adiu
Nintex Newbie

Re: Nintex and SharePoint Batch vs Commit pending changes

Jump to solution

Ah ok, I did not fully understand this until now... Thank you.

Reply
murphybp2
Nintex Newbie

Re: Nintex and SharePoint Batch vs Commit pending changes

Jump to solution

You’re welcome. If that resolved your question, please mark the question as answered. Thanks.

Reply