Migration Error: 'ERROR, the batch will be resubmitted to the import pipeline'
Question
What does it mean when the message ERROR, the batch will be resubmitted to the import pipeline displays in the Information section of the Log Item Details dialog when a migration is performed using the Import Pipeline?
Answer
You may see this message (which will begin with either ERROR or FATAL ERROR) during a migration when a batch fails to migrate in its entirety. To address this issue, increase the value of the environmentsettings.xml key MaxAzureBatchRetryCount. This key controls the maximum number of times Content Matrix will resubmit the batch until it is successfully migrated. (The default value is 5.)
The batch retry mechanism will also be triggered for the following errors:
·Please try again. CallStack -- at Microsoft.SharePoint messages
·Access denied
·Save Conflict The system cannot find the path specified. (Exception from HRESULT: 0x80070003)
·Updates to system roles is not allowed.
·List does not exist
For any error not listed above (such as Item Does Not Exist, which is different than List does not Exist), a batch will be resubmitted only if the error message is added to the environmentalsettings.xml key ErrorMessagesForRetryAzureBatch.
IMPORTANT: If adjusting this setting does not resolve the issue, the error may be with the CSOM connection. See Retrying Failed Document Copies to SharePoint Online CSOM Connections for details.
Item Count at Target is Increased When Migrating Using the Import Pipeline
Question
Why is it that, after migrating a list with versioning enabled using the Import Pipeline, there are more items on the target than on the source?
Answer
If you are migrating a batch that includes a list with a base type of CustomList (such as Announcements), versioning is enabled, and Content Matrix has had to resubmit the batch that includes the list, duplicate items may be migrated to the target. By default, these types of lists are excluded from resubmissions, but can be included via the environmentsettings.xml key RetryBatchForCustomListWithVersions.
NOTE: If custom lists are excluded from batch resubmissions and all items are not successfully migrated, you can migrate any outstanding items using incremental migration.
Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline
Question
Why is it that, after a migration using the Import Pipeline, some lists with versioning enabled do not appear on the target?
Answer
By default, lists with a base type of CustomList (such as Announcements) are excluded when Content Matrix must resubmit a batch that initially failed to migrate in its entirety (because if they are included, duplicate items may be migrated to the target). These types of lists can be included via the environmentsettings.xml key RetryBatchForCustomListWithVersions)
NOTE: If custom lists are excluded from batch resubmissions and all items are not successfully migrated, you can migrate any outstanding items using incremental migration.
Supported Nintex Actions for SPO Migration
Question
What are the supported Nintex actions that are available when migrating from SharePoint on premises to SharePoint Online?
Answer
The following table lists the supported Nintex actions that are available when migrating from SharePoint on premises to SharePoint Online.
NOTE: The following actions are supported, but not all their parameters will necessarily have a SharePoint Online equivalent. Make sure to review migrated Nintex workflows to ensure that they migrated as expected. Also ensure that actions requiring user interaction (such as Assign Flexi Task, Send Notification, etc.) have user mappings properly configured during migration.
|
On-Premises Actions |
Online Actions |
|---|---|
|
Assign Flexi Task |
Start a task process |
|
Build String |
Build String |
|
Calculate Date |
Add Time to Date |
|
Change State |
Set Next State |
|
Check Out Item |
Check Out Item |
|
Convert Value |
Convert Value |
|
Create Item |
Create List Item |
|
Delete Item |
Delete Item |
|
Discard Check Out |
Discard Check Out Item |
|
End Workflow |
Terminate Current Workflow |
|
Filter |
Filter |
|
Log in History List |
Log to History List |
|
Loop |
Loop with Condition |
|
Math Operation |
Do Calculation |
|
Pause for... |
Pause for Duration |
|
Pause Until |
Pause until Date |
|
Query list |
Query list |
|
Regular Expression |
Regular Expression |
|
Run If |
Run If |
|
Run Parallel Actions |
Parallel Block |
|
Send Notification |
Send an Email |
|
Set a Condition |
Conditional Branch |
|
Set Field Value |
Set Field in Current Item |
|
Set Variable |
Set Workflow Variable |
|
Set Workflow Status |
Set Workflow Status |
|
State Machine |
State Machine |
|
Switch |
Switch |
|
Update Item |
Update List Item |
|
Wait for item update |
Wait for Field Change in Current Item |
Refer to Quest® Essentials for Office 365 documentation for an idea of the requirements and caveats involved in the migration to SPO.
NOTE: If the workflow contains an action that is not supported, this unsupported action will be created as a comment in the migrated workflow. The comment will contain the name of this unsupported action.