Hi Pete

I sometimes do this by :

1. creating a column called "Dummy"

2. updating my workflow to conditional start on modification when Dummy = x

3. publish workflow

4. Add "Dummy" to view and edit in datasheet view

5. Put "x" in Dummy column on all items I want workflow to run on

6. Wait for workflow to complete

7. Edit workflow and remove the conditional start

8. Publish workflow

9. Delete column "Dummy"

Alternatively you can do this for each item by choosing item menu > workflows > workflow name > start.

If you don't see your workflow then you need to allow your workflow to start manually (checkbox) on your workflow settings and publish.

Hi Peter Scott‌,

I want to add some extra info to point (5) of what Cassy mentioned:

Nintex workflows, just like workflows made with SharePoint Designer, are meant to be triggered by human inter-action and not by a batch. In step (5), you can create a batch and potentially 'hurt' your farm performance.

The company I work for has dealt with unhappy companies that contacted us, saying their workflows were very very slow and their farm was under performing. Investigation showed that every day, at the start of the day, a SAP export was dumped into a SharePoint list kicking of a Nintex Workflow for each item.

My personal experience is that small batches often is not a real problem. So please take care with (5).

Cheers,

Rick