sp-dev-docs
sp-dev-docs copied to clipboard
Migration API CreateMigrationJob failed reading a manifest file generated with the Export API CreateSPAsyncReadJob
Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
SharePoint CSOM
Developer environment
Windows
What browser(s) / client(s) have you tested
- [ ] 💥 Internet Explorer
- [ ] 💥 Microsoft Edge
- [ ] 💥 Google Chrome
- [ ] 💥 FireFox
- [ ] 💥 Safari
- [ ] mobile (iOS/iPadOS)
- [ ] mobile (Android)
- [X] not applicable
- [ ] other (enter in the "Additional environment details" area below)
Additional environment details
No response
Describe the bug / error
Following the MSDN documentation for SharePoint Migration, I am doing an Export of a site library :
ClientResult<AsyncReadJobInfo> output = clientContext.Site.CreateSPAsyncReadJob(
"https://contoso1.sharepoint.com/sites/ThePerspective/Shared Documents",
new AsyncReadOptions {
IncludeDirectDescendantsOnly = true,
IncludeSecurity = true,
IncludeVersions = false,
IncludeExtendedMetadata = true
},
null,
azManifestContainerUrl,
azReportQueueUrl);
The export is successful and generate a folder (named with a GUID) containing all XML files expected (such as Manifest.XML). I then copy all xml files at the root of the container and create the snapshot for each file (since it may not be possible to directly link the folder generated).
I then try to use that manifest to Import it on another existing site "https://contoso2.sharepoint.com/sites/ThePerspective/Shared Documents" :
clientContext.Site.CreateMigrationJob(clientContext.Web.Id, sourceFileContainerUrl, manifestContainerUrl, azureQueueReportUrl);
The job is created and queued and leads to this error :
JobFatalError, message The 'Description' attribute is not declared.
By removing the Description in the DocumentLibrary node in the Manifest.XML, the error is getting moved to the following attribute Direction then ImageUrl and so on.
Steps to reproduce
- Create the manifest file using the CreateSPAsyncReadJob method
- Copy and create snapshot for all xml files at the root of the container
- Create the Import job using CreateMigrationJob method
- The migration job is queud, runs and always fail with error
Expected behavior
Import a manifest file generated by export should leads to a successful migration job
Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.
Was this ever resolved? I am encountering this issue at the moment as well.
Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.
If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.
We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.