-
Great! Glad to hear you got it working. Thanks for sharing your solution with the rest of us!
-
-
Ocassionally a form can become corrupted. And it's often impossible to track down why. Its good to keep occasional backups as you develop, or use a source control system.
You might be able to, if it's not an overly complex form, rebuild it and then compare all the template source files to see what is different.
-
Sure thing. Glad to help!
-
Glad to have been able to help! Let us know what you find!
-
Very strange behavior. Sounds like there's a shared resource being clobbered by some other application. Once you repaired it it worked, and then some other application saw that a file changed and overwrote it again, and then it stopped working. Just a guess--but sounds like the most likely suspect at this point.
-
Great. This should work for you. Once you have the handle to the XDocument of the other form, you can code to it just the same as you do the XDocument of your current form. So if you want to copy a value from one XDocument to the other, that's no problem.
-
The problem you are having might be coming from the xsi:nil attribute.
On non-String data type nodes (including, but not limited to: Date, Time and DateTime nodes), if you want to allow the node to have a blank value, the schema places the attribute: xsi:nil="true" on the node. While this attribute is present on the node, the node value ...
-
That's great to hear! So glad you got it working!
-
Your eval has a problem, look at the XPaths:
(lineItems, "../my:lineItems/my:Quantity * ../my:lineItems/my:Price")
lineItems is the starting point, yet your multiplication XPaths step up above that node ("../") and then come back into it to always get the first row.
It should look more like:
(lineItems, "my:Quantity * ...