Skip to main content

I'm preparing for migration of an SharePoint list from on-premises to SharePoint 365.  The list includes a Nintex form with a repeating section.  The repeating section includes a Person column.

In a test migration, the internal format of the person field changes (which makes sense since it's switching from the intranet to Microsoft's servers).  The IDs are update to any standalone Person fields in the list, but not the Person column within the repeating section, which from SharePoint's perspective is just a long text field that happens to hold XML data.

When attempting to view any migrated list item that includes a person in the repeating section, the form fails to load and gives the error message:
 

Index was outside the bounds of the array.
If the problem persists, contact your support team with the following information:
 

 

Followed by Correlation ID, Tenant ID, and timestamp.

 

This error doesn't happen with newly-created People in the repeating section, since they are created with the new Microsoft user IDs.

Is there a known way to get all these user IDs updated?

[Just now seeing the original post is 3 years old]

I am experiencing this problem too as we are in the middle of migrating to O365… not quite sure how to resolve this just yet.  My work-around for a standalone Form was to rename the control so that it cannot map the XML data to avoid errors with the values used by SharePoint/Nintex On-Prem.

However, this work-around will not work for another solution we built which utilizes a Form linked to a Workflow.

 

Nintex On-Prem:

<?xml version="1.0" encoding="utf-8"?><RepeaterData><Version /><Items><Item><dtCommentCreatedDate type="System.DateTime">12/19/2018 00:00:00</dtCommentCreatedDate><pplCommentCreatedBy type="System.String">i:0#.w|adsyf\5550003321</pplCommentCreatedBy><mltComment type="System.String"></mltComment></Item></Items></RepeaterData>

 

Nintex Online:

<?xml version="1.0" encoding="utf-8"?><RepeaterData><Version /><Items><Item><dtCommentCreatedDate type="System.DateTime">12/19/2018 00:00:00</dtCommentCreatedDate><pplCommentCreatedBy type="System.String">16;#i:0#.f|membership|first.lastname@company.com</pplCommentCreatedBy><mltComment type="System.String"></mltComment></Item></Items></RepeaterData>

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings