AddFieldToContentType is case sensitive about pnp-sites-core HOT 6 CLOSED

Hi Pieter,

Thanks for reporting this. However, in the example you post, the Id property is a Guid, not a string. E.g. we are comparing 2 Guids there and casing doesn't apply then.

Which version of the engine are you running? Are you compiling the latest branch (we've been making many updates to it the last days)?

from pnp-sites-core.

Hi Erwin,

I didn't investigate the exact line things failed in but the easy way to reproduce this is by adding an existing field to a content type definition. And replace the GUIDs of this field with some capitals.

I'll have a quick look where the exact line is where things go wrong.

I've got the code as it was at the beginning of the week.

Thanks,

Pieter

from pnp-sites-core.

I just did exactly as you described, but couldn't reproduce the error here...

        <pnp:ContentType ID="0x0100B5EAF2F41E01254D8D78342FD9EF8764" Name="TestPnP" Description="" Group="PnP" NewFormUrl="" EditFormUrl="" DisplayFormUrl="">
          <pnp:FieldRefs>
            <pnp:FieldRef ID="c042a256-787d-4a6f-8a8a-cf6ab767f12d" Name="ContentType" />
            <pnp:FieldRef ID="fa564e0f-0c70-4ab9-b863-0177e6ddd247" Name="Title" Required="true" />
            <pnp:FieldRef ID="A9E51afe-1c8b-4c51-9413-b630a82b660f" Name="Test_x0020_PnP_x0020_Column" />
          </pnp:FieldRefs>
        </pnp:ContentType>

Notice the case different in the last FieldRef entry. It just worked here. I also tried with different casings in the content type ID, but also had no problems.

from pnp-sites-core.

What can help, if you still encounter the issue with the latest build (we made changes to the engine today even), is if you could provide us with the template you're trying to provision?

from pnp-sites-core.

Hi Erwin,

I just tried it with the latest code and it now worked. Whatever you did over the last few days must have fixed the issue.

from pnp-sites-core.

Glad to hear!

from pnp-sites-core.