InfoPath Dev

I have created a user update form published to a form library. I am trying to configure it using Qrules to update a list as well for editing user information. The bottom of the form has 2 combo boxs witch retireve data from 2 lists in a cascade and below that a people picker box. The form has no issues at all and works fine in the browser until I inject it and then receive the following errors. i The filter expression is on external data and cannot be validated. It may not be supported in web browser forms. i Code events on person/group picker controls are not supported i Control sends data to server when value changes (primary cause) is there some other way to get the combo boxs populated with Qrules? it was working and passing the design checker before the injection, what changed? Any assistance greatly appreciated

Hi-

I'm sorry you've run into issues. It sounds like an issue with the sandbox.

I'm attaching a test form with code. This form has custom code, but no qRules. It will allow you to test the sandbox service.

When you get a message about code not being found, you can click Ignore. Publish the form to a temporary/test form library and let us know whether the form publishes and opens without issues.

Thank you.

Thanks for the reply, your assistance is much appreciated. I downloaded the form and publish to a new library. Publish OK and the form opens in browser with Hello there! any thoughts Thanks. Rob Wilde

So - are the warnings in the design checker actually preventing you from publishing?

It is publishing but stating it can only be opened in Info-path Filler. "he Form template has been published to the server but it can only be opened in the InFoPath Filler because it contains Features that are not compatible with Web browsers." It was working great until it was injected? I made sure the compatibility was set to browser when injecting

I think the issue is with the first error you are getting - my guess would be that if you manually added code to the template, you'd see exactly the same warnings. Mind attaching it to a reply, under the Options tab, so I can take a look?

NO real code in there just query fields, witch I guess is code :) here is the form in full working order before injection. it is over 700KB so i cant upload but here is a link https://www.dropbox.com/s/v86hge1dejb8ipn/WFC_AD_Update_3.zip

Cool, I'll take a look - what I mean is when you injected your form with qRules, you added a compiled code DLL. I think if you simply added a code event to the same form (without qRules injected) you'd have had the same issue.

Okay - so when I manually add code to your form, I get the exact same warnings. I tried to publish to a form library, and it appeared to publish successfully as browser enabled. Then I removed the code and injected w/ qRules 4.3 and republished - the form is still able to open in the browser in my environment.

Do you have access to your SharePoint logs? I'm wondering if there may be some info in there while you are trying to publish that would help us understand why the form is failing to sandbox....

Hi Hilary, I went back through the creation process again, following your excellent video tutorial, and then tested the saving and publishing after every stage. It now publishes perfectly to the site and opens in browser. Really not sure what it was but its not happening any more. I am noticing something a little odd though, I am using DBXL and ADUserInfo to retrieve the current users AD information. It was working wonderfull but now it returns the spfarm account. This only happens in browser. If I preview the form in InfoPath Designer I see my details. I have attached the latest version of the file that does publish and open without errors. You might be able to see what the difference is. https://www.dropbox.com/s/cubs6rei3yncx0x/WFC_AD_Update_4.zip So close. If you happen to know of a good guide on how to add a image selector, so users can save an image to SharePoint that would be awesome.

The form is publishing OK now but there is another issue. When I preview the form it will publish to the Form Library and update the list Publishing works OK, view the form in browser everything looks good. Complete and submit and it will only Publish to the form library not to the list?

Okay - so, can you put the Qdabra Rules error node on your form and make sure the form is not set to close after submit? Something is going awry with the command in the browser - there are several possibilities and getting the error message back would be helpful. Oh, and also - there is another field in the Qdabra Rules data source - /QdabraRules/Form/@extendedErrorMessages. Put that on your form as well, and check the box prior to executing the command.

OK so I went back to a previous version before mapping and injecting. I published to network share and tested, a OK. completed the mapping and injection and still all good. I then changed the publishing to SharePoint browser form and tested and everything is working well. The only issue I have found is the ADuserinfo data connections seem to be returning the SharePoint farm account when using GetMyInfo. I worked around setting a hidden field with userName() and using that with GetUserInfo, works OK. Just curious as what is causing the different account after injection. It was fine before adding Qrules to the form. Thanks again for all your assistance, I love your training videos and webinars. :)

I had the same issue and found the following solution: http://gordonduthie.net/2011/01/26/sharepoint-2010-claims-based-security-infopath-data-connections-and-getuserprofilebyname/ , I was able to narrow down how to get reliable user data using Secure Source Server in SharePoint and an anonymous user in the target application. Specifically, for InfoPath Forms Services, when calling a web service for user information, whether using GetUserProfileByName or Qdabra's GetUserInfo, the parameter passed must be "concat("your domain\", xdUser:get=UserName())". For my purposes, I set an onload rule for GetUserInfo, populating the username field under the queryFields node for the secondary data source. Then I query the data source, and the correct user's data displays.

Hope this helps.