HowTo: Map a source metadata field to a target SharePoint List field or taxonomy hierarchy field or Choice List field

Follow

There can be a requirement to map a source metadata field to a target SharePoint List field or taxonomy hierarchy field. The target SharePoint List or taxonomy could have different field values or hierarchical metadata in SharePoint or Office365 as compared to source system values of respective field. So to map and transform such metadata fields to new List or taxonomy values in SharePoint, we have to configure CSV based metadata mapping, which uses PowerShell extensions and function mapping features in the Migration Accelerator. Please refer below step by step guide to achieve the same.

            1. Taxonomy/Managed Metadata Mapping Sample CSV. Please note that hierarchical taxonomy values should be separated with Semicolon(;) as shown in below Sample CSV.
              • Taxonomy/Managed Metadata Mapping Sample CSV
                howto-mapping-1.png

              • SharePoint List Metadata Mapping Sample CSV
                howto-mapping-2.png

              • SharePoint Choice List Metadata Mapping Sample CSV. Please note that multiple choice values should be separated with SemicolonHash(;#) as shown in below Sample CSV.

                howto-mapping-3.png
            2. Close the Migration Accelerator Instance if it’s running.

            3. Locate Proventeq Migration Accelerator PowerShell Default Module file as shown below:
              image006.jpg

            4. Open above PowerShell Default Module file and add below PowerShell command to load above Metadata Mapping CSV into a global PowerShell object and save the file.

              $global:CSVCommunicationCategoryMetadata = Import-PVQCsvAsHashTable 'D:\proventeq\metadata\Communication Category.csv' 'SourceValue'

              4-psm.png

            5. Then launch Migration Accelerator application in order to map respective metadata field.

            6. Select Migration Task Settings and open Content Type mapping for respective field metadata mapping as shown below:
              image010.jpg

            7. Select respective field setting icon and then select mapping type as Function shown below:
              image011.png

            8. Click on Select button to launch a function mapping popup as shown below. Creating a function mapping type will allow to reuse this mapping function in other Content Type mappings as well.
              image013.jpg

            9. Add a new function by providing below parameters:
              1. Select Function language as PowerShell
              2. Select Group as any existing or Add a new group name.
              3. Provide Name of the function
              4. Provide Description of the function
              5. Add parameter “SourceValue” by clicking on ‘+’ button. Provide Data Type as ‘string’ or ‘integer’.
              6. Provide PowerShell script to read a source field value and return it’s matching target value from global PowerShell CSV object as shown below:

                image014.jpg

                $meta = Get-PVQMetadataRow $SourceValue $global:CSVCommunicationCategoryMetadata

                if($meta -eq $null)
                {
                throw “Matching communication category metadata not found”;
                }
                else
                {
                return $meta.TargetValue;
                }


            10. Click on Save Function and then select the newly created mapping function.

            11. After creating and selecting a new function, one need to provide necessary parameter(s) in the “List of parameters available for the function” section as shown below i.e. Select mapping type as Metadata and then select respective Source field.
              image016.jpg

            12. Click on Save button to complete the metadata mapping for this field as shown below:

              image017.png
Note: Multiple Taxonomy Metadata Mapping is not supported using CSV in Office 365 when package processing setting in enabled.

  

Was this article helpful?
0 out of 0 found this helpful

Comments