Hello,
I wonder if there is any chance to require that metafields (of any type) have a value, like in a SQL database?
I know that I can force kind of a “required” validation for text fields with min length, but I’m looking for a generic solution for any type of metafield. (You cannot require dates, for example.)
If a design or a function in a store relies on such metafields, it is absolutely necessary to guarantee not only the validity of a value (if one is entered) but the existence of such values.
Maybe there is a trick or a third-party solution – but if this option is really missing, it’s kind of a metafield design flaw, I think.
Thanks for any tipps! ![]()