InfoPath Dev

Hello,  The rule cannot be entered via the user interface. You need to extract the source files and edit the manifest. This is explained in detail in this video of a webinar held by Patrick Halstead on May 24. http://www.youtube.com/watch?v=9rtXm5oOEhI&feature=plcp The Qdabra Youtube channel has lots of really cool InfoPath ...

Hello, I have created a dropdown field that uses a SharePoint list as the source. When I created the data connection to the list, I selected to sort by ID. I then converted the data connection to a udcx file and stored it in a connection library. Now it turns out that sorting by ID was not a good idea. The users want to sort by title ...

Success. Setting @useWebServices to FALSE did the trick. Problem solved. Thanks Hilary and Jim!!

Explanation for the grayed out check boxes: The view that I added the qRules fields to was set to read only. Duhh. I'll try to set the @useWebServices to FALSE, since so far it was always set to TRUE by the action on the finishedLoading field.

Thanks, Hilary. While trying to give that a go, I see the following: - When I drag the @useWebServices field onto the form and preview the form, the check box is ticked. But when I inspect the field, its default value is FALSE. How can that be? - I can use the FormLoad rule to change the value, but I cannot tick the box on the form. That also ...

Bump. Any ideas, Jim?

Hello Jim, yes, the same urls work internally and externally. I have tried to change the url to use https before I posted here, but the error returns exactly the same message, just shows https in the url. Yes, if I enter 'http://restore.testworld.co.nz/sites/general/dispatch/_vti_bin/lists.asmx' as the url, it redirects to https when it ...

Hi, thanks for the quick reply. It's a browser form. Injected with qRules 4.2 and admin approved. The form itself behaves fine. Just writing to the SharePoint list on the sibling site is the problem.

Hello, we have the following scenario: A form with qRules gets filled in and saved on Site A. When it is saved, it also uses SubmitToSharePointList to write data into a list on site B. Both sites are in the same site collection. It works fine when we run it on our in-house network. We have extended the web application and remote users can access ...

After some more testing I find that this weird behaviour shows just on two farms. The setup may be dodgy and they have not had any service packs installed. The date fields work fine on a newly built farm with service packs in place.