Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Copying SharePoint Objects as a Separate Action Self-Service Migration Incremental Migration Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering Metalogix Command DLL Files Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed and Self-Service Migration Frequently Asked Questions
DB_Owner Permission Migrating with the Fabulous 40 Templates Item Count Discrepancies Keyboard Shortcuts License Key Troubleshooting Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Using Proxies, Load Balancing or Alternate Access Mappings Troubleshooting the Extensions Web Service Installing the Extensions Web Service on Specific Systems Extensions Web Service Installation Files Using Older Versions of the Extensions Web Service Preserving IDs when Migrating a Custom List as a Folder Migrating JavaScript Migrating Site Variations Migrating with SharePoint 2010/2013/2016 Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations SharePoint 2013 and 2016 Site Collection Creation Issue Job List Database fails to Load After Upgrade Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs with a CSOM Connection Type Retrying Failed Document Copies to O365 CSOM Connections Migrating Content When the Source Custom List Template is Missing Are SharePoint Online Migrations Throttled? What to Expect when Migrating with StoragePoint on the Target Migration Error Message 'There was an Error Reading from the Pipe: The Pipe has been Ended (109, 0xd6)' How do I Remove Items from My Azure Blob Storage Account? Azure Batches Getting Stuck Supported Nintex Actions for SPO Migration "Insufficient Credentials" Message Connecting to Modern Team Site Using Web Browser Authentication Error Making a Browser-Based Connection with PowerShell Console Open
About Us

Linking Source Columns to SharePoint External Data (BCS) Columns

Metalogix Content Matrix allows you to create special columns that are linked to a SharePoint External Data (BCS) source. With these columns users can attribute external items to documents prior to migration. At migration time, these terms will be applied to the migrated documents.

Overview of Business Connectivity Services (BCS) in SharePoint 2010 and Later

Business Connectivity Services (also referred to as External Data) is a feature introduced in SharePoint 2010 that enables the use of content from external data sources in SharePoint. Metalogix Content Matrix supports retrieving External Items from a SharePoint BCS data source, attributing those items to source documents, then applying those terms in an existing External Data Column when content is migrated.

Connection icon

Currently, only connections over the SharePoint Object Model (OM) are supported. This includes connections using the Local OM (by installing locally on the SharePoint server), or connections using the Extensions Web Service (remote OM connections).

Applying external items to migrated documents involves the following tasks:

A.Create a new SharePoint External Data (BCS) column to your source Metabase project. This column will be associated with a pre-defined SharePoint External Content Type.

B.Use the external data column to attribute terms to your documents.

C.When pasting your documents to your target, map the source Taxonomy column to an existing External Data column on SharePoint.

Related Documents