-
Hi -
So you know, if the form does not have code in it when you publish it, it won't be going into the Sandbox. No need, since there is no code.
Do you have other forms with qRules published as Sandboxed browser forms? If you take a new, blank form and inject with qRules does it Sandbox?
-
So, you are using that in your default values? And when you enter a new row, it gets the value of the row before? I'm sorry, I don't quite understand - if you could give a bit more detail / attach your temlate to the Options tab, that would help.
-
Is the ClientID field also in your main data source?
-
Hi -
I think the part that may be a little tricky is the pulling the relevant questions in to the main data source - there are a few commands you could use for this. If the schemas match, just use CopyTable - it is the simplest route. If they are more complex, you can use some other approaches, like Insert with additional logic to populate ...
-
Oh, wonderful, glad you got it resolved.
I always try to narrow the issue down to form, machine or user - generally it seems to be one of those categories. From there you can start figuring out the issue, but until I do that I find myself just sort of thrashing about, which isn't terribly efficient. :-)
-
Well, a lookup column is going to always have the ID of the "looked up" item. If you look at the Data Connections dialog (Data tab on ribbon, click the Data Connections button) you'll see a number of data connections that say in the Details section (just click on the name of a data connection and there will be details about it ...
-
Then you'll not want to use managed code. :-) XPathNavigator is used in IP 2007 and IP 2010 managed code - you can either change the programming language for your form, or use the appropriate syntax.
http://www.infopathdev.com/tags/vbscript/default.aspx
-
You had a lot of default values - drag the main data source onto your form so you can see what fields are actually being set to (change the data source task pane to the advance view to make it easier for yourself). Again, the error is occurring (most likely) because you have set one of these lookup fields to a text string instead of a list item ID.
-
Well, it is baffling. I guess what I'm wondering is if it is a machine issue or a form issue. It seems to be machine, right? Since only you are having the issue. But what if the problem is with the latest template, and the other users have the template cached....? You may want to try removing the template from the cache on another machine to ...
-
You bet - glad that was what you needed! :-)