cannot be blank

[deronburba]

I have a form based on an existing schema. From my take on the schema, the
element should not be required. When implementing the element as a drop down
list on the form, the "Cannot be blank" is checked and cannot be changed.
Why can't this be unchecked given the way the element is defined in the
schema?

Thanks.


<element minOccurs="0" ref="omb:ESPCFunding"/>

<element name="ESPCFunding" type="omb:yesNoString"/>

<simpleType name="yesNoString">
<restriction base="string">
<enumeration value="yes"/>
<enumeration value="no"/>
</restriction>

 

[Adam Harding]

Hi

If your form is connected to a main data source such as a Database or
Sharepoint Site and THAT specifies the field cannot be blank or cannot be
NULL.

Hoep this helps

Adam

 

[Greg Collins [InfoPath MVP]]

Those kinds of settings are only available on schema built fully within the InfoPath designer. You need to manually modify your external schema to resolve this issue.

It looks to me like what you need to do is add an additional enumeration to allow for value="".