Pre-Migration Check Results
Within the Power BI Report you can find a number of tabs detailing the results of various classes of pre-migration checks. The "Has Issues" indicates the total number of issues found, by selecting the "True" bar the results can be filtered to only show those items which have failed.
Do be aware that these checks run against the data as it was present in the source and before any transformation occurs, therefore issues such as overly long folder paths and duplicate file names can be resolved through transformation rules, structure mappings and options.
The "General" section covers the following checks:
- Content referenced by multiple folders - items that are referenced (filed/linked) in multiple different folders. Positives on this test suggest that you may want to enable Shortcut Link Resolution.
- Deleted or marked for deletion - items that have been removed from the source system via a deletion operation or are in a deletion queue and pending removal by an administrator.
- Too many child items - items that have more child items within them than is permitted on the target system. Positives suggest that re-structuring should take place on the source system or through structure mapping.
Paths and Names
The "Paths and Names" section covers all of the generalised checks for the names and paths of items, these checks run against the source representation of the names and paths therefore they do not take account of structure mapping, item name transformation rules or duplicate file handling.
- Long Item URL - The item's path would be too long for the target system. This would lead to a load failure if not corrected.
- Long Parent URL - The parent folder component of the path (everything before the item name) would be too long for the target system. This would lead to a load failure if not corrected.
- Blocked Characters - The item has characters in its name that the target system does not support, the "General > Replace all invalid characters" option should be enabled or the name should be rectified to prevent load failures.
- Items with the same name as another item in a folder - two or more items have the same name and reside in the same folder. If the target system does not allow this you should consider changing the "File and Folder Settings > Duplicate File Handling" setting to "Create a new file with a unique name", restructuring the source system and rediscovering or resolving the conflict with structure mapping.
The "Files" section covers all of the checks that are specific to files.
- Empty (zero byte) content - items that appear to have either missing or empty (0 byte) files. This could indicate an issue with the integrity of the source data, positives should be examined by a record officer/system administrator to determine whether the files truly are missing: if so the issue can be worked around by loading placeholders with the "LoadPlaceholdersForMissingOrEmptyFiles" advanced setting.
- Max Size (MB) - items that are too large to load into the target system.
- Disallowed extensions - items that have a file-extension/format that is not permitted on the target system, a common example is ".exe" executable files.
The "Version Continuity" section focuses on flagging up any potentially unwanted/undiagnosed property divergence across version sets. A number of systems to do not allow core properties such as content types, file types and names to differ between different versions of a document.
- Content type mismatch across versions - items for which all versions of a group (normally a document) do not share the same Content Type/Category/Classification.
- Name mismatch across versions - items for which all versions of a group (normally a document) do not share the same name.
- Differing extensions across versions - items for which all versions of a group (normally a document) do not share the same file extension/format.