Qdabra qRules

Re: Publishing qRules Injected Forms

Hilary Stoupa — Fri, 31 May 2013 19:49:41 GMT

Don't be embarrassed - I looked at it a half dozen times before I saw it too - but that's why I was pressing for the production mapping file and schema - logically, the reason you'd get that error is because of an XPath mismatch (which is what, in the end, you had). Glad it is all working. :)

Re: Publishing qRules Injected Forms

ccroder — Fri, 31 May 2013 19:31:36 GMT

Am I embarassed!! Thanks for your help; that did the trick.

Re: Publishing qRules Injected Forms

Hilary Stoupa — Fri, 31 May 2013 18:54:12 GMT

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.

Re: Publishing qRules Injected Forms

ccroder — Fri, 31 May 2013 17:56:13 GMT

Here is the schema.

Re: Publishing qRules Injected Forms

Hilary Stoupa — Fri, 31 May 2013 17:25:50 GMT

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

Re: Publishing qRules Injected Forms

ccroder — Fri, 31 May 2013 16:32:14 GMT

Here is the production mapping file with the URL redacted.

Re: Publishing qRules Injected Forms

Hilary Stoupa — Fri, 31 May 2013 15:42:35 GMT

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.

Re: Publishing qRules Injected Forms

ccroder — Fri, 31 May 2013 15:02:10 GMT

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.

Re: Publishing qRules Injected Forms

Hilary Stoupa — Wed, 29 May 2013 21:43:40 GMT

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?

Re: Publishing qRules Injected Forms

ccroder — Wed, 29 May 2013 20:30:12 GMT

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:

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

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

Re: Publishing qRules Injected Forms

Hilary Stoupa — Wed, 29 May 2013 19:49:04 GMT

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

Re: Publishing qRules Injected Forms

ccroder — Wed, 29 May 2013 19:11:52 GMT

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?

Re: Publishing qRules Injected Forms

Hilary Stoupa — Wed, 29 May 2013 16:46:27 GMT

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.

Re: Publishing qRules Injected Forms

ccroder — Wed, 29 May 2013 16:41:06 GMT

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

Re: Publishing qRules Injected Forms

Hilary Stoupa — Wed, 29 May 2013 16:20:14 GMT

It just needs to be injected into the form.