InfoPath Dev

Hi,

If I put a field or an attribute as an integer type in infopath that make this field or attibute "cannot be blank"!!!

Why this ? Is there anyway to disable this? I have a lot of field in my schema who is integer but he dosen't is required!

It's a very strange feature!

Thanks for your help!

++

Thierry

Every moment hesitated is a moment gone for life!!! Think about it

any non-String attribute automatically "cannot be blank" by schema validation rules. If you want a non String type attribute to be blank, you must change it to type String.

As for nodes (i.e. fields), you can manually modify your schema to add the nilable="true" attribute to it. This is the only way to allow it to be blank.

Greg Collins [InfoPath MVP]
InfoPath Dev

Hi,

Thanks a lot for your answer!

I will try this !


++

Thierry

Every moment hesitated is a moment gone for life!!! Think about it

Hi,

quote:

---

If you want a non String type attribute to be blank, you must change it to type String.

---

It's the worst things on infopath this probleme We have developp all the schema and now we have all to change!!!

It's so good! Thanks infopath if you hear me ;-)

If you know the reason can you explain me why? because for me it's ...

Thanks for your feedbacks

++

Thierry

Every moment hesitated is a moment gone for life!!! Think about it

Well, it's a sharp knife and if you don't do your schema design up front, then ... yes ... you run the risk of getting cut later .... ;)

The reason is XML Schema validation. Check out the XSD spec online. Should be Google-able.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Hi Greg and Patrick, Thanks for your help!

I have understand why now!

The problem is that infopath can not have an optionnal attribute so when the attribute is an integer(for example) he always send this attribute and if it is empty he make an error of validation (like all other xml parser)!

So a good challenge for the next version of infopath is :

that infopath can remove (or ignore) before validate the empty optionnal attribute.

Thanks one more time for your good explanation!

++

Thierry

Every moment hesitated is a moment gone for life!!! Think about it

Are you sure you always want to remove it? The date has this issue today with xsi:nil and it requires that you write code to add/remove it. I think it's a semantic issue and that we can't expect InfoPath to automatically remove and add the xsi:nil attribute as well as others. This is something you need to do in code.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Ok I understand your point of view! I'm agree with you!

Thanks!

Thierry

Every moment hesitated is a moment gone for life!!! Think about it