Can't have blank properties in Document Blueprints

[Eaglef90]

Which Umbraco version are you using?

15.4.1

Bug summary

If a property is marked "required" and you try to leave it blank when saving a Document Blueprint the blueprint will not be saved.

Specifics

In the new Document Blueprint system you can not leave "required" properties blank. I believe you could do this with templates in v13. Not being able to leave a property blank is a bit annoying as some properties might always have to have a unique value and having a pre-defined one in a blue print means a document type could be created and published with those properties being forgotten to be updated. For example, if the property is a meta description it should be blank so when the editor goes to publish they can't until they remember to update the field.

Steps to reproduce

Create a document blueprint based off an existing content node which has a required property in it's document type.
Leave the required property blank and try to save the blueprint

Expected result / actual result

Expected: I can save a blueprint with empty properties even if the are deemed "required"

Actual: All "required" properties must have a value in them

[github-actions]

Hi there @Eaglef90!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[AndyButland]

Thanks for reporting @Eaglef90 - I can reproduce. It's looks like this issue is client rather than server-side here. We are treating documents and blueprints differently on the server, where only the former are validated. But the client-side validation is operating for both documents and blueprints, preventing you saving a blueprint with, for example, a required field.

[Eaglef90]

When v16 comes out I will be upgrading. Will this be addressed in v16 or is there something I could do on my end to bypass this problem? I need to create about a dozen blueprints and it would be really nice to have blank fields on the data points that are unique to each page.

[AndyButland]

Fixed via #19748 and due in 16.2.