This article provides an overview of how repeating sections in the Generate Document action work in Nintex Workflow Cloud versus how they worked in Nintex for Office 365. We will look at an Expense Claim SharePoint list that uses a Nintex Form with a repeating section to capture expenses. The expenses are stored as XML in a SharePoint multiple line text column and can be used throughout the workflow.
It is assumed that you already have experience working with repeating section data saved as XML inside a Nintex for Office 365 workflow. A workflow and form will not be built from scratch to explain that concept, but you can review the Nintex Workflow Cloud articles Part 1: Work with repeating section data from SharePoint based Nintex Forms and Part 2: Work with repeating section data from SharePoint based Nintex Forms for more information on how that works.
This article also builds upon information from the article, Upgrade Document Generation action, which covers other aspects of upgrading the Document Generation action outside of repeating sections.
Click on the image below for context as to what the Nintex Form looks like for this article's example.
After the upgrade to Nintex Workflow Cloud, you will have to reconfigure the Generate Document action to account for the repeating data that was merged using the Merge Collections action. This will make the repeating data available for tagging when using the Nintex Document Tagger.
You will need to retag your document template with all new tags that represent the data in your Nintex Workflow Cloud workflow. Tagging requires opening a document template in an editor and then opening the Nintex Document Tagger from the Generate Document action. In the following steps we will focus on retagging the repeating data section inside a Word Document.