-
Again - before you try again, that error is usually because of invalid data submitted to the list. Here's another thread with this error.
-
Already did that, before posting anything on this forum. Her example is with a much more complicated data, but I did follow the steps in spirit.
I will still give it another try.
-
Sorry to waste your time. It seems like it's working now. I can't seem to figure out what could have changed. Thank you for your time.
-
Hi
Hilary has published a thorough walk thru for qRules v4.2, which I would recommend checking out:
http://www.infopathdev.com/blogs/hilary/archive/2012/05/30/qrules-submittosharepointlist-walkthrough-for-v4-2.aspx
I'm not sure what could be going on in your case - I haven't looked at the v2.0 steps in a long time. Anyway, please check ...
-
Here's a link to the 4.2 walkthrough, just so you have it. What are the data types of the fields you are submitting to? Are they just text? Lookups, perhaps?
-
Thanks again,
I tried following an example with qrules 2.0 for submitting to an existing sharepoint list.
Everything goes well, until the test. Then I get an error: "The operation failed because an unexpected error occurred. (Result Code:
0x80020005)"
The infopath form is set to compatible with Infopath Filler. The error appears for ...
-
-
Glad that's resolved. Just to be clear, reinstalling is not necessary. The steps I provided should resolve the issue.
The InfoPath to SharePoint list tool is an installable template. Have you installed the template?
In the tool's folder (for example C:\Program Files (x86)\Qdabra Software\Qdabra Rules Library) , you'll find a folder ...
-
What's the data source look like for your form?
I am guessing the issue is that in IP we can't use rules to insert a new instance in a field in our data source. There are a couple ways to deal with this limitation.
Custom Code - write code to insert a new instance of the target field and set the value
qRules - use rules to insert ...
-
Never mind - answered my own question. Turns out the option buttons on View 8 were actually unbound. Once I bound them to optEnvironment, they worked when I would set a value for optEnvironment on View 3. D'oh!
nkstrou