You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have added several content types to the content type hub with main language set to English and with Norwegian and Swedish translations using a PnP template. These are then added to SharePoint sites.
When using the filter panel to filter on the name of these content types it works fine when doing this with a user with English language set, however filtering as a Norwegian/Swedish language user returns zero results. Filtering directly on a column works fine in all languages. What I have observed is that the available filters are in English directly on the column (where it works for all users) no matter what language the user have, but the filter panel have the translated values.
Microsoft support was unable to reproduce it on their side using the GUI and as they do not support PnP they did not investigate this further.
Anyone else that have experienced the same issue?
The text was updated successfully, but these errors were encountered:
Hi,
We have added several content types to the content type hub with main language set to English and with Norwegian and Swedish translations using a PnP template. These are then added to SharePoint sites.
When using the filter panel to filter on the name of these content types it works fine when doing this with a user with English language set, however filtering as a Norwegian/Swedish language user returns zero results. Filtering directly on a column works fine in all languages. What I have observed is that the available filters are in English directly on the column (where it works for all users) no matter what language the user have, but the filter panel have the translated values.
Microsoft support was unable to reproduce it on their side using the GUI and as they do not support PnP they did not investigate this further.
Anyone else that have experienced the same issue?
The text was updated successfully, but these errors were encountered: