0

we have experienced a weird error while provisioning a content-type. The content type in question had a field added to it. We had provisioned the xml to sharepoint with pnp. It had been provisioned to the dev and test-enviroments prior (quite some time prior) to being provisioned to prod.

From the time it had been provisioned to test and now to prod no changes had been made to xml nor code that applies the xml.

When the xml now is ran the connection between the hidden note field and the taxonomy field does not seem to work. And this happens when we now ran the script in the previously provisioned dev(sharepoint online) and test(2013)-enviroments.

Something to note is that the hidden note field is now for some reason visable even though the xml sets it to hidden=true.

The provisioning has somehow changed the already existing taxonomy fields. The taxonomy itself is there and working.. if you take the value of the now visable note field of an old listitem and use that to create a new listitem and set the taxonomy and add the value of the note field to the correct field it will work as intended.

However if you change the value using only the taxonomy picker it will not save the value.

Been looking high and low for a solution to this problem for a while now with no luck. Given that it spans over several enviroments and even over onprem vs online it feels like the problem has to be with the provisioning itself even though no changes has been made to the xml since the last provision where it worked with no issues.

This is an example of how the taxonomy fields was provisioned (with ids and names redacted). Any ideas?

    <?xml version="1.0" encoding="utf-8" ?>
<pnp:Provisioning xmlns:pnp="http://schemas.dev.office.com/PnP/2016/05/ProvisioningSchema"
                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xsi:schemaLocation="http://schemas.dev.office.com/PnP/2016/05/ProvisioningSchema https://raw.githubusercontent.com/OfficeDev/PnP-Provisioning-Schema/master/OfficeDevPnP.ProvisioningSchema/ProvisioningSchema-2016-05.xsd">
  <pnp:Preferences Generator="OfficeDevPnP.Core, Version=2.12.1702.0, Culture=neutral, PublicKeyToken=null"/>
  <pnp:Templates ID="">
    <pnp:ProvisioningTemplate ID="" Version="1">
      <!-- SiteFields -->
      <pnp:SiteFields>
        <Field Type="Note" ID="" DisplayName="" StaticName="" Name="" ShowInViewForms="false" Hidden="true" />
        <Field Type="TaxonomyFieldType" ID="" StaticName="" Name="" DisplayName="" ShowField="Term1033" Required="true" EnforceUniqueValues="false" Group="" >
          <Default />
          <Customization>
            <ArrayOfProperty>
              <Property>
                <Name>SspId</Name>
                <Value xmlns:q1="http://www.w3.org/2001/XMLSchema" p4:type="q1:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">{sitecollectiontermstoreid}</Value>
              </Property>
              <Property>
                <Name>TermSetId</Name>
                <Value xmlns:q2="http://www.w3.org/2001/XMLSchema" p4:type="q2:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">{GUID}</Value>
              </Property>
              <Property>
                <Name>TextField</Name>
                <Value xmlns:q6="http://www.w3.org/2001/XMLSchema" p4:type="q6:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">{GUIDofNotField}</Value>
              </Property>
              <Property>
                <Name>IsPathRendered</Name>
                <Value xmlns:q7="http://www.w3.org/2001/XMLSchema" p4:type="q7:boolean" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">false</Value>
              </Property>
              <Property>
                <Name>IsKeyword</Name>
                <Value xmlns:q8="http://www.w3.org/2001/XMLSchema" p4:type="q8:boolean" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">false</Value>
              </Property>
            </ArrayOfProperty>
          </Customization>
        </Field>
      </pnp:SiteFields>
    </pnp:ProvisioningTemplate>
  </pnp:Templates>
</pnp:Provisioning>

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.