Expose SPContentTypeEntityData so we can use ParentContentTypeId

[patrick-rodgers]

Category

• Question
• Typo
• Bug
• Additional article idea

Expected or Desired Behavior

When creating a new content type via REST we do a post to the collection with a set of data. These parameters are defined by the SPContentTypeEntityData in the source code, however this type cannot be resolved (see observed behavior). It is expected that we could call the method with the defined type using all the properties.

Ideally we could create a new content type and specify the entire new content type id, but that is a bigger change.

Observed Behavior

If you make the POST request with a plain object with a metadata type of "SP.ContentTypeEntityData", "SPContentTypeEntityData", or "ContentTypeEntityData" you get an error below:

{"odata.error":{"code":"-1, Microsoft.SharePoint.Client.InvalidClientQueryException","message":{"lang":"en-US","value":"A type named 'ContentTypeEntityData' could not be resolved by the model. When a model is available, each type name must resolve to a valid type."}}}

Steps to Reproduce

Craft a POST request to the rest API and try to specify ParentContentTypeId in that data.

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[AlNoes]

Is there any update to this? Unfortunately, this results in not being able to create a content type and define a parent content type. With this bug, the new content type always is a child of Item.
See also here: https://stackoverflow.com/questions/55529315/how-to-create-site-content-type-with-id-using-rest-api

[facujuarez]

Hello guys! It's a pleasure to greet you.
Is there any news about this error?

[fridrichovsky]

Hi guys! I would like to know if you have any news.

[ValerasNarbutas]

Good day @patrick-rodgers ,
i see this attached to bug about id. Does this also apply for issue when cannot assign parent to created content type?
Checked today still not working and defaulting to Item as parent.

[fridrichovsky]

I raised question to Microsoft Support and they don't plan fix this bug. I had to use workaround through Azure Functions where I use CSOM for this particular part.

[fs366e2spm]

Is there an update on this topic?
This won't be fixed? Really? Is there a known reason?

Face the same issue and can confirm it's always using the root "item" as content type.

[vzzdaniel]

Any update on this?

[CallumCrowley]

Is there an update on this?

[klioqc]

Let's keep it open. Any updates?