Code

Re: Putting numeric values into nodes with VB code

Greg Collins — Wed, 19 Jul 2006 17:17:23 GMT

Thanks for sharing this. Yes - you must ALWAYS remove the xsi:nil attribute before providing a value to a field. If you clear the value of a field, and it is marked as cannot be blank, then you must add back the xsi:nil attribute or else the field will show an error in InfoPath.

Re: Putting numeric values into nodes with VB code

Carolyn — Tue, 18 Jul 2006 19:10:12 GMT

quote:
There's probably a valid reason for it, but alas, I have not further insights for you on this.

It has to do with nillable content.

If I default a value, say "0", in the field, then I can easily fill the field in managed code. If there is no value in the field, then I cannot fill the field in managed code. Or, I remove the nil attribute first, then fill it.

In this particular problem, assigning 0 as the default value is no problem whatsoever, and the field is read-only to the user. Thus, the problem is solved.

Thanks for replying!

Re: Putting numeric values into nodes with VB code

Greg Collins — Tue, 18 Jul 2006 17:02:08 GMT

Its the mysteries of programming. Why something doesn't work until you try to show someone, or works one time and not another.

There's probably a valid reason for it, but alas, I have not further insights for you on this.

I'm glad its working now!

Re: Putting numeric values into nodes with VB code

Carolyn — Fri, 30 Jun 2006 23:22:53 GMT

quote:
Keep in mind that all values are stored as text in the XML file... It is the schema that determines the data type of that text value.
So, when you enter ANY value from code, you do it the same way:
thisXDocument.DOM.selectSingleNode("my:node").text = "999"

Greg, thank you very much for your reply. This subject has been driving me nuts. I set up a simple trial sandbox so I could test code snippets without messing up the main project.

I have, as I said before, several text boxes defined as doubles. When trying to use the thisXdocument.DOM.selectSingleNode().text statement, I got the PCDATA is in nil content error. I was able to get around that with the method I posted above, in the sandbox.

BUT BUT BUT

I took it out of my simple trial sandbox and put it in my main program. Suddenly, the text goes into double defined text boxes without any problem. I don't need the remove named item statement.

The code is now working just great, getting a number (as you said formatted like "11") into the double defined text box.

rant WHY DID IT NOT WORK LIKE THAT BEFORE WHEN I FIRST TRIED IT??? /rant

If you could kindly offer insight on that, I would be in your debt.

Re: Putting numeric values into nodes with VB code

Greg Collins — Fri, 30 Jun 2006 17:54:43 GMT

Keep in mind that all values are stored as text in the XML file... It is the schema that determines the data type of that text value.

So, when you enter ANY value from code, you do it the same way:

thisXDocument.DOM.selectSingleNode("my:node").text = "999"

Hope this helps.

Putting numeric values into nodes with VB code

Carolyn — Wed, 28 Jun 2006 23:22:43 GMT

I have several text boxes in my InfoPath form that are defined as double precision, as well as other text boxes that are strings (text).

In VB.net code, I can easily assign the value of a string text box:

thisXDocument.DOM.selectSingleNode("my:node").text = "Whatever"

But, what if I want to assign a numeric value to one of the double numeric text boxes? I looked for something like:

thisXDocument.DOM.selectSingleNode("my:node").Value = 999

That does not work.

What does work? I kept on getting an error like:

'#PCDATA' is in nil content

If I changed the text boxes to text (string), then everything worked great. But, I did not want them to be string data. I wanted numbers so I could calculate sums, etc.

After a great deal of search, I found the answer. You have to first remove the "nil attribute". How?

thisXDocument.DOM.selectSingleNode("my:node").attributes.removeNamedItem("xsi:nil") 'all on one line

MicroSoft has a KB article (826998) that describes this in jscript.

http://support.microsoft.com/kb/826998/en-us

Added later (7/3/2006)

After some trial and error, I discovered that if I set the decimal defined text boxes to have a default value (zero in my particular case), then I did not have to worry about the PCDATA is in nil content problem at all. I did not have to remove atribute at all. Setting a default value solved the problem for me.

If you cannot or do not wish to set a default value, or if you are concerned about the user deleting your default, then you need to check to see if there is a nil attribute, then remove it if it is there. That can be done with simple if then end if code.