23 results found

1. Map properties depending on the source content type

   On our scenario, we want to map two properties from the source, not one.
   However, we do not want to merge them into one because it's not the case that two existing properties will map to one property; they will still be a one-to-one mapping.

   We would like to do something like this,

   $propMappings = Set-PropertyMapping -MappingSettings $propMappings -Source "prop1" -Destination "prop3"

   $propMappings = Set-PropertyMapping -MappingSettings $propMappings -Source "prop2" -Destination "prop3"

   However, by doing this ShareGate overwrites the first mapping with the second one.

   The reason for doing this is simple: each content type will only have one of the fields.
   If we use single mapping, one of them is ignored.
   If we use multiple mapping, ShareGate will try to merge the two properties that exist at the list level, even though they do not exist on both content types.
   This creates a series of problems from default values to forcing the destination property to allow multiple values when none of the 3 properties (2 source, 1 destination) are multi value.

   A potential solution for this would be something like,

   $propMappings = Set-PropertyMapping -MappingSettings $propMappings -Source "prop1" -Destination "prop3" -ContentType "admin"

   $propMappings = Set-PropertyMapping -MappingSettings $propMappings -Source "prop2" -Destination "prop3" -ContentType "meet"

   In this alternative, we could specify property mappings that are content-type specific, which would allow a one-to-one mapping in a scenario where multiple content types exist and we want to control what field goes into the destination field depending on the document's source content type

   On our scenario, we want to map two properties from the source, not one.
   However, we do not want to merge them into one because it's not the case that two existing properties will map to one property; they will still be a one-to-one mapping.

   We would like to do something like this,

   $propMappings = Set-PropertyMapping -MappingSettings $propMappings -Source "prop1" -Destination "prop3"

   $propMappings = Set-PropertyMapping -MappingSettings $propMappings -Source "prop2" -Destination "prop3"

   However, by doing this ShareGate overwrites the first mapping with the second one.

   The reason for doing this is simple: each content type will only have one of the… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  10- Manage with PowerShell  ·  Delete…  ·  Admin →

2. Map/concatenate multiple text properties into a single property

   We would like that, in PowerShell, we could have the ability to map multiple properties to a single property.
   At the moment, it seems that this is possible only with certain types of fields.

   "3) Advanced scenario – Multiple columns to a single column
   Since Sharegate 2.9, any destination column that supports the ‘multi-values’ (Lookup, Choice, People, Managed Metadata) option will allow more than one column to be mapped to it"
   https://sharegate.com/blog/sharepoint-merge-remap-multiple-columns-to-a-single-column

   So if we have a simple scenario such as:
   Property A (text)
   Property B (text)

   We cannot map them to a
   Property C (text)

   this is only allowed if Property C is an MMS column or other supported type.
   it would be interesting to be able to perform such a mapping , for example:

   Property A value: "dog"
   Property B value: "cat"

   examples:
   Property C value: "dog, cat", "dog; cat", "dog cat", "dog [newline] cat".

   in short, we would have the ability to pick a delimiter and concatenate the values of multiple text properties into a single text property.

   thank you

   We would like that, in PowerShell, we could have the ability to map multiple properties to a single property.
   At the moment, it seems that this is possible only with certain types of fields.

   "3) Advanced scenario – Multiple columns to a single column
   Since Sharegate 2.9, any destination column that supports the ‘multi-values’ (Lookup, Choice, People, Managed Metadata) option will allow more than one column to be mapped to it"
   https://sharegate.com/blog/sharepoint-merge-remap-multiple-columns-to-a-single-column

   So if we have a simple scenario such as:
   Property A (text)
   Property B (text)

   We cannot map them to a
   Property C (text)

   this is only allowed… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  10- Manage with PowerShell  ·  Delete…  ·  Admin →

3. Provide ability to output errors only

   When using PowerShell to perform a content migration, ShareGate outputs successes, errors, warnings, etc.. Please provide a way to output errors only so we can check for errors > 0, and if true, do something (like use native PowerShell functionality to email the admin, for example). This way, multiple migrations can be run without the need to scan all the results for errors.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  10- Manage with PowerShell  ·  Delete…  ·  Admin →