General

Re: Error with xsi:nil attribute

Greg Collins — Tue, 11 Dec 2007 17:56:22 GMT

Changing the data type in your schema should not affect the values stored in the field in your forms (except for possibly marking them as invalid values).

XPath calculations work against strings as well as numbers. Normally, XPath doesn't care about the data type. However, if you want to be sure a values is treated as a number, use the number(field) function.

Re: Error with xsi:nil attribute

shaun.nieves — Fri, 07 Dec 2007 19:36:38 GMT

There's about 1500 existing forms. I changed it back to double and it they haven't errored out yet. Will that blow the values in the saved forms? I was doing a calculation on the node which was why it bombed out. I'm going to try and do the calculation using managed code. Hopefully it works.

Re: Error with xsi:nil attribute

Greg Collins — Fri, 07 Dec 2007 17:36:09 GMT

When you converted the node from Text to Double, you left it as not required, which is why the xsi:nil attribte was placed on the fields. If you have a Double that your mark as required, there will be no xsi:nil.

Now, can you use that information to create a fix? Perhaps. It depends on the process you went through the first time and how many forms were affected.

Error with xsi:nil attribute

shaun.nieves — Fri, 07 Dec 2007 16:48:50 GMT

I have a broken node. This node was originally a text field that stored prices. I know I know... Well I converted it to double and published the form. I thought everything was ok but it started erroring out on prices that had parenthesis (.90) so I changed it back to text. Now, new forms can open just fine but old forms error out on load with this error:

xsi:nil attribute on element '{http://schemas.microsoft.com/office/infopath/2003/myXSD/2006-12-12T22-07-01}PROFPRICE' is invalid.

I thought for now I could loop through the nodes and remove the nil attribute but that doesn't seem to be working. Anyone have any ideas? Anything would be greatly appreciated!