Skip to content
This repository has been archived by the owner on Jan 19, 2021. It is now read-only.

[BUG] #2793

Open
Get-SPO opened this issue Oct 19, 2020 · 1 comment
Open

[BUG] #2793

Get-SPO opened this issue Oct 19, 2020 · 1 comment

Comments

@Get-SPO
Copy link

Get-SPO commented Oct 19, 2020

Environment

[*] Office 365 / SharePoint Online
[ ] SharePoint 2016
[ ] SharePoint 2013

Expected or Desired Behavior

I am using the Import-PnPTermGroupFromXml command to create terms in the M365 Term Store. When creating the term label in an alternate language the Description field is not exposed in the schema. For the primary language the Description field in set as an attribute of the term. An alternate language label uses IsDefaultForLanguage. There is no way to set an alternate description of the term based on language. This field works as expected when done manually in the UI.
I am using "http://schemas.dev.office.com/PnP/2020/02/ProvisioningSchema"

I would suggest that either the ("Description","Term Description") needs to add "Language","103x"and allow multiple elements on a term, or preferable add the Description field to the Label creation where label ("IsDefaultForLanguage","true").

See: https://docs.microsoft.com/en-us/graph/api/resources/termstore-localizeddescription?view=graph-rest-beta

Thank you.

@ghost
Copy link

ghost commented Oct 19, 2020

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@ghost ghost added the Needs: Triage 🔍 label Oct 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant