-
Hi - can we see your form? You can attach it to the options tab here, or you can email it to Support AT Qdabra DOT com - if you email it to us, would you include a reference to this thread?
-
You want this:
xdXDocument:GetDOM("STATES")/items/item/value[../name = xdXDocument:get-DOM()/my:myFields/my:State]
-
You could modify your XML file to include the correct number for each state and use a default value for GL. I've attached a simple sample - save it locally and then you right click the file to open in design mode and preview it. Under Data --> Resource Files you can export the XML (if IP 2007, Tools --> Resource Files) so you can see how ...
-
Can you also post a screenshot showing what you are describing? I'm having a little trouble following your description. Just attach a picture file under the options tab.
Thanks!
-
Mind attaching your template under the Options tab in a reply? That would give me a better idea of what you are trying to do.
-
Hey, fantastic, glad it is working for you - here's a little blog post that may help with the syntax.
-
I think it would be:
../preceding-sibling::my:SharePointListItem_RW[1]/my:Description
-
I asked Jim to chime in, because I thought we had seen this before - as you saw with testing, the issue is with resources for the Sandbox being exceeded when the form is published, whether with qRules or with code.
You may want to try admin approving the form. If that isn't possible in your environment, Jim has also posted a script that will ...
-
I think this will do what you want:
../preceding-sibling::my:SharePointListItem_RW/my:Description
Save the form linked in this reply locally, right click the file and select Design to open in design mode.
-
So, was the "yes" answer to both of my questions? You can sandbox other forms with code or qRules, but you can't sandbox large forms with qRules / code.
I think it would be good to take a copy of a form that won't sandbox with qRules in it and add custom code - see if it will sandbox then. Just go to the Developer tab and ...