InfoPath Dev

Is it necessary for qRules to be installed on the workstation that publishes InfoPath forms to the SharePoint server, or is it sufficient that qRules be injected into the form?  We have a closed development environment on which all form development and testing is performed.  To publish a completed form to the separate production environment, the qRules-injected form is moved to a different workstation connected to the production environment.  The publish appears to run as expected, the form operates as designed in the production environment, but the qRules command (SubmitToSharePointList) does not work.  The development environment has the full version of qRules installed on the workstation, is developing with InfoPath 2010, and saving the form in InfoPath 2007 format.  The production environment does not have qRules installed and is publishing the form from InfoPath 2007 to a SharePoint 2010 site.

 It just needs to be injected into the form.

Given the environment I described, why is the qRules command not functioning in production like it does in development?

 Sorry - I didn't notice that in your post. I'd put the qRules Error node on your form someplace (maybe a hidden debug view) and then try the command in production to see if you are getting any errors.

I added the error field, and the form returned "Failed to select node for SharePoint List Id:my:ActivityID." ActivityID is the form field set up to capture the list ID that is returned.  In moving the form from development to production, I updated all of the data connections and the publishing directions to point to the new environment.  I also modified the mapping file to change the target list GUID at the top of the file and the site URL at the bottom of the file.

Any other suggestions?

 The field in your form is still named my:ActivityID? Can I take a peek at the form? You can attach it under options.

The field is still named my:ActivityID.  The file from the development system is attached; I can't send you the one from production.  Both development and production are SharePoint 2010.  The differences from development to production other than site URLs are:

1. Development is http:// and production is https://
2. Development is using InfoPath 2010 and production uses InfoPath 2007

Could there be a problem not publishing from InfoPath 2007 as an administrator?

 Can I see the copy of the mapping file from the production form? You can remove the SharePoint URL in the mapping file if that will make you more comfortable?

Here is the mapping file from our development environment; I can't send the production version.  The only difference between the development and production mapping files is the GUID at the top of the file and the site URL at the bottom of the file.  The GUID is that of the target list "Report Activities" and the URL is that of the site.

 The reason I asked for the production one was because you are not having this error in your dev template, but are in your production template. If I have the template, or even just the mapping, I can run it with qRules in debug and get a better idea of what is going wrong. Since your dev form works, there is nothing here that I can test against.

Here is the production mapping file with the URL redacted.

 May I also see a screenshot of the schema in your production form for my:myFields/my:Activities/my:ActivityGroup?

Here is the schema.

 The mapping has ActivtyID for the ID - it is misspelled - missing an "i" between "v" and "t" - I didn't see it till I ran the code in debug and even then had to walk through it twice to catch that missing "i". Update your mapping file and try your production form again.