How to make Datum field mandatory in site publisher component ?

raghu1931

Find more posts tagged with

Comments

You'd think that would be pretty basic, but you can't. The only thing you can do is have your component render an error message to the user (usually in edit/preview mode only) to indicate that a value is missing.

Tanuj

Guys anybody found a solution for this problem?

Thanks

Tanuj

nipper

Guys anybody found a solution for this problem?

Thanks

Tanuj

Since Rick posted his reply in January of this year, it is quite unlikely that the resulting answer has changed.

Add JS to the component to tell the user they did not put data in, or put that in a DCR (of course the DCR can be excluded, but that is another story).

neeraj_kumar

Guys anybody found a solution for this problem?

Thanks

Tanuj

Use attribute of Datum min="1" . It will make Datum field mandatory. Let me know if it works for you.

Rick Poulin

Use attribute of Datum min="1" . It will make Datum field mandatory. Let me know if it works for you.

That's only valid for Datums of type Number. It won't help you for Type=String or anything else.

neeraj_kumar

That's only valid for Datums of type Number. It won't help you for Type=String or anything else.

That is valid for most of the Datums. It also works for String, Textarea, Page Link, Radio Group etc.

Using min="1" attribute mandate the datum to enter atleast one value.

Tanuj

My item is a singleselect so min is not even allowed
Datum Exposed="true" ID="segment_variable" Name="Segment" Type="SelectSingle" >
Generator Method="getOptions" Object="com.****.teamsite.PropertyLoader">
Parameters>
Datum ID="propName3" Name="propertyName" Type="String">Segment
Datum ID="propFile3" Name="propertyFile" Type="String">/iwmnt/iwov-resources/properties/default.properties
/Parameters>
/Generator>
/Datum

Apply_Button_Position_Change.jpg

Migrateduser

Rick's solution should be the one to go with!

Rick Poulin

That is valid for most of the Datums. It also works for String, Textarea, Page Link, Radio Group etc.

Using min="1" attribute mandate the datum to enter atleast one value.

I meant semantically valid. While it does appear to work as a hack for some cases, it appears to be caused by a side effect both XSD validation limitations, and of implicitly casting Strings and other non-numeral objects to numbers. That doesn't exactly give me the warm and fuzzies.