InfoPath Dev

I don't know if it's our dev environment setup, or my form, or what, but the qRules commands aren't working in  the browser. 

• Injected with qRules 7.1
• Administrator-approved
• Claims based site
• useWebServices set on finishedLoading
• SPListSubmit is converted to udc

I have a button that sets Command to SubmitToSharePointList /submit=SPListSubmit /mapping=mapping.  When I click the button, nothing.  No Result errors, it just sits there.  Fiddler shows nothing happened.  It's like it just sets the field but doesn't run the command. 

This form of course works in InfoPath.  ARGH!  Am I missing something, or is the environment not set up right? ARGH!

Did you set postback on the button to Always under the button's properties in the browser tab?

DOH!  I know you have told me to do that before!  It is now done, and one of my buttons works, but not the one with the submit.   There are 5 rules on the submit button, and it does them all except for the actual submit.  ='(

What is the "actual submit"? Is that the qRules SubmitToSharePointList command? Anything in the error node?

Sorry.  Yes, it is the SubmitToSharePointList command:  SubmitToSharePointList /submit=SPListSubmit /mapping=mapping

Nothing in the error node.  =( 

If the button is a "submit" button (so the rules are under the submit rules) maybe try changing to Rules instead. Or add another button with the same rules & see what happens. Any rules with a "don't run the rest of the rules if this condition is met" checkbox selected?

The button is not a "submit" button.

I tried adding another button with just the submit rule.  Nothing, although Fiddler now recognizes that I clicked the button.  I even created a new mapping and tried that.

I am going to email you the .xsn.  If you have the time, please take a look to see if you see anything wrong. 

 

I'm confused again - I thought you said it was working in preview / filler? Is that the case? Any rate, I got your XSNs and I'll try to take a look later today. :-)

Just updating this thread per our email conversation - turns out there was an error on a date time and resolving that allowed your form to submit correctly to the list. :-)