Alexey Abramkin comments

Repositories
Issues
Comments

Results 3 comments of


                                            Alexey Abramkin

Import-PnPTaxonomy, Creates wrong hierarchy when term contains comma

3.26 version here and workaround that worked for me is to wrap any term with comma in it with double quotes, i.e.: term one|term two|"term, three"

Import-PnPTaxonomy, Creates wrong hierarchy when term contains comma

@jimmywim did not have ids in the import (it is non SharePoint source), did not see it as an option in [documentation ](https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/import-pnptaxonomy?view=sharepoint-ps) either - do you have string example?...

Import-PnPTaxonomy, Creates wrong hierarchy when term contains comma

@jimmywim Export-PnPTaxonomy works for export of terms and produces correct labels containing commas in the exported file. The file produced by Export-PnPTaxonomy with -IncludeID switch and then used with Import-PnPTaxonomy...