[o ] Bug
[ ] Enhancement
[o ] Office 365 / SharePoint Online
[ ] SharePoint 2016
[ ] SharePoint 2013
If SharePoint on-premises, what's exact CU version:
Taxonomy field values to be set on uploaded files where the value is specified inthe JSON file that specifies metadata
Taxonomy field values are not populated
Use a JSON file such as this when uploading via the pnp:Files template block:
(Behaviour is seen on both single and multi valued taxonomy fields.
Deserialization code in the codebase has been tested independently, and the values in the "Category" fields below successfully deserialize to a TaxonomyFieldValue[] array object.
The "Title" field successfully is set from this file also, so the framework is definitely reading the values correctly. Any Syntax errors in the text body of the Category Value are thrown during processing, so the Category field is also definitely being read.
This sample below does not error but the Category value is not set.
{
"..\\HR_Files\\Files\\HRDocuments\\Cycling to work Scheme.pdf": {
"Title": "Cycling to Work",
"Category": "[{ \"Label\": \"Health\", \"TermGuid\": \"f070cc69-28b4-482d-9f8d-09eac34c8f41\", \"WssId\": \"-1\" }]"
},
"..\\HR_Files\\Files\\HRDocuments\\Dental Plan.pdf": {
"Title": "Dental Plan",
"Category": "[{ \"Label\": \"Health\", \"TermGuid\": \"f070cc69-28b4-482d-9f8d-09eac34c8f41\", \"WssId\": \"-1\" }]"
}
}
Hi @jimmywim , thanks for logging this issue. Quick scan of the code seems to indicate this should work, but it apparently it doesn't...more research is needed.
Having the same issue. It worked before.
This does still seem to be an issue -> addition of a publishing page in the pnp template (below sample is with hardcoded id's these are added through parameters)
The below will add the single value mms field but not the multi value field
Looking at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.ObjectFiles at the
We closed this issue as it had not activity within last 180 days. This is a generic process we have decided to perform for issues, which have not been explicitly marked still to be "work in progress" based on tags. We are performing this cleaning to make sure that old issues that have already been solved (but not closed) or are no longer relevant are cleaned out and make the issues more manageable. If this issue still valid, we would ask you to open a new issue and follow the guidance in the issue template related on the recommended location. We do apologize any inconveniences this might cause. Please do remember that issues in the issue lists are also messages for others in the community, so you can also check if you can assist on any of them. “Sharing is caring!”
Most helpful comment
Hi @jimmywim , thanks for logging this issue. Quick scan of the code seems to indicate this should work, but it apparently it doesn't...more research is needed.