February 2012 - Posts - Hilary Stoupa
in

InfoPath Dev

Hilary Stoupa

February 2012 - Posts

  • And yet another qRules video!

    There is a form available here for download that demos the techniques in the video - the video outlines using qRules to copy complex repeating data between two data sources. CopyTable works well in simple scenarios, but if your data structures don't match, or have nested groups, you may find the video and sample form helpful.

  • More qRules Video Goodness

    So, I've got 3 recent qRules videos up on YouTube:

    Hope they help with your qRules forms!

    PS - the sample form used in the Submit To Multiple InfoPath Lists is available here for download. It points to my dev SharePoint, and has a trial version of qRules installed, but you'll be able to get a good idea of the logic used from the sample.

  • IPFS & qRules - the saga continues

    I wanted to note a few things I've run into using qRules in Browser forms, along with some troubleshooting ideas.

    • Postback - if your form works in client (preview) but not when opened in the browser, check postback on your controls that are setting commands first. Set postback to "Always" on controls that execute qRules commands.
    • Errors - put the error node from the QdabraRules data source onto your form, and admin approve (or sandbox) the form again. See if an error is being returned.
    • Data Connections - Permissions can be different. If your data connection works in client, it may not in IPFS. Try converting to UDCX (and be sure to approve the UDCX files). If it is a data connection that qRules is using for something, try executing the data connection outside of the qRules command, see if your form shows and IPFS error with a correlation ID you can use to track down the issue in the logs.
    • Bubbling - I've had instances where rules on nodes in secondary data sources will fire when an attribute of the node changes, or where rules on a group fire when a new instance of the group is inserted - these can be hard to track down. Try disabling rules on attributes / child nodes and see if your outcome changes. Then you can start planning a work-around.
    • Spaces - I saw an instance where a SubmitToSharePointList command failed in the browser because of an extra space at the end of the name of the mapping data connection. In client, the space was trimmed. In IPFS, it was considered to be part of the data connection name, and we had an error about the data connection not existing.

    It can be hard to track some of these things down in IPFS - you can't just set a rule on the Command field to pop up a dialog. What I do is add another field, temporarily, and each time the Command (or Error, or whatever field I want to track) changes, set the trouble-shooting field to its current value concatenated with the new value. This can give me a list of commands that have run (or errors that have occurred) and allows me to track back through the logic to find inconsistencies between browser and client.

     

Copyright © 2003-2017 Qdabra Software. All rights reserved.
View our Terms of Use.