-
-
So on the field where this is working, is this also a validation rule?
-
I'm sorry I missed this - thanks for the bump! You can use another qRules command to insert the PI (processing instructions) that are in the mso-infoPathSolution line. That should be all you need. Look for the InsertPI command in the qRules user guide - it has an example for this. Just run that command prior to submit, and you should be on ...
-
Unfortunately, there isn't an easy out of the box way to do this - I believe if you promote the data as merged, it won't be available in your query fields in your secondary data connection. If the merged data was instead submitted separately to a SharePoint list (using code, qRules or CAML) you could then query that list - same if ...
-
So - this section is showing or hiding based on Class selection? Not Additional Class selection?
-
You need to link the tables when you create the main data connection, not create two connections. I'm assuming there is a link between your two tables?
-
Unfortunately, InfoPath has no out of the box date diff function. Here's a link to one way to do this:
http://www.bizsupportonline.net/infopath2007/calculate-date-difference-infopath-rules-formulas.htm
You can also do this using code or qRules.
-
This thread indicates that the workflow will not be terminated unless you also delete the item from the recycle bin - so that's kinda awful. Again, you can always set up a quick unit test - which is what I would probably do.
-
I'd guess setting the task to completed from the form would work - but I would test this. I'd set up a mapping to the task list, including the ID column so you can update, then I'd just dummy up a scenario - have an open task w/ workflow running, and in my form, set the ID field and the status, and use the qRules SubmitToSharePointList ...
-
You could have also used the count function, I think - but if Max works for you, that's great!