pnp / pnp/pnpframework

Applying pnp template breaks multilingual managed metadata field

Open
#641 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
259
Forks
161
Avg merge
10h 33m
Merged PRs (30d)
1

Description

I have a managed metadata site column attached to the term set with terms with labels in many different languages. When I use this column on a list it works correctly - users see values in their own languages. But if I export this column and the apply pnp site template with this column - it displays the 1033 (English) term name for each user. I can then open the edit page for this column and - without changing anything - click OK. This fixes the column. Once again it is multilingual. Unitl the next pnp run.... In the pnp there is this ShowField value
ShowField="Term1033"
I can set it for example to Term1045 - then all users see the term in Polish but if I export the field, the ShowField attribute has there 1033 just like it was not changed at all (but it was and it is visible as the column always display polish name of the term).
Removing the ShowField attribute from the PnP template does not help. Assigning there an empty string makes the column to display nothing (empty space in the column for all rows on the list)
I guess that when the field is working fine, then this ShowField attribute is not there but the SharePoint somehow returns it always equal to Term1033 when you try to get the field schema. But assigning it to any value makes this value the only possible one.... And then saving the column through the SP UI fixes it for example by removing this attribute? I have no idea... I suppose this is an issue in the SharePoint itself but as I do not know then I am reporting this here...

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with a multilingual managed metadata site column, then export and apply a PnP template containing ShowField="Term1033". Compare the field before and after applying the template, including values such as Term1045; done means the applied column preserves each user's language rather than forcing English.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.