InfoPath Dev

We have the "14" folder, Office 2010 and 64-bit servers & workstation setup

Hi Hilary, I did not see anything related to the publishing. No events logged when Least Level set to  warning.

A couple of notes on the case-sensitivily and Infopath:  1) I have not seen or read about anything, besides the translate function shown, which could be facilitated to achieve the non-case-sensitive filter.  I still can not believe, that for an app as Infopath a full list (there was was a typo, sorry) of the standard ...

The dynamic count of the records in the Events (top-level) repeating table: As you can see from the screenshot it is implemented as a default, recalculating value on a field bound on the Main connection (dcount). The formula is using a filter very similar to the one for hiding the non-matching rows.    - The first 2 conditions ...

The attached screenshots here are related to visually filtering the results to show only those matching the criteria selected. - The rule is implemented on the repeating node itself. The partial-match filter was intended only for the master query in this case (Events). - matching Phase & Status filters is easy as they are either populated ...

Hi All, I have run again into a problem, which I have resolved in the past, but can not find a reference this time. SP 2010 Enterprise, IP 2010. I have had successfully injected a SPD Workflow Task Form with qRules 4.3 and used to successfully submit a number of sub-tasks, actions to a separate SP List. The form was working without problems ...

Hi Patrick,  First,  I would like to apologize for the delay as a couple of unexpected projects needed my attention. Yes, the demo will pull all actual (EVENT records) entries into the form (no miracles, just presentation):  - I did not use the query fields for the master, EVENT library demo( I could, of ...

Yes, my filter is not case sensitive. I will should be able to post the rules in the next 24 hours. Unxpected projects poped up, so I apologize for the delay. 

The design: No code or qRules. Only 3 data connections used: a) Main , b) Top_Level, Event, secondary "receive" data connection bound to a SP Form Library, c) Detail-level, event-related tasks, secondary "receive" data connection. The demo is intended as report/ dashboard, thus could only be printed or saved to a ...

The main connection snapshot shows all the fields used for the demo (only Sharepoint/Infopath used, no SQL or Access databases) - SelEvent: keeps track of any selected node in the master(top-level) repating table, EVENTS. It is intended for use in the drill-down when expanding a particular node to show all tasks assigned in the other secondary ...