Creating a record for entity with Draft & publish enabled creates a "published" record

Discord Q&A strapi-questions
1

Hey all,

I am using a REST to create an entry from my FE for an entity with Draft & publish enabled.

I have noticed that even though the request body doesn’t contain a publishedAt attribute, when the entity is created is is always created with state published. I also use GraphQL in some places and the behaviour is different in that the entity is created with the Draft status.

Is this by design or is this something that can be configured?

Any help would be great.

This topic has been created from a Discord post (1285960440802705488) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord

2

Hey all, any ideas on this?
I am wondering if I should be submitting publishedAt as null but I have many forms and that is a bit tedious.
Is there a configuration option to control this behaviour?
Thanks!