-
So - here is the difficulty with that - Out of the box, InfoPath doesn't have any rule actions that can be used to add rows to a table. This leaves writing custom code, or possibly an add-in like qRules (not sure if we have tested qRules much with DB bound forms).
-
Well, in my sample form, the tables are bound to the same data source. So, I'm not sure that this is going to be applicable to your situation - when you say "add the filtered record to a different database" I think you may be dealing with a database bound form - is that correct?
-
Maybe try setting the postback settings on the drop down to always (under the control's properties). I won't have a chance to try it in the browser this week, but can look next week if postback doesn't fix it.
-
-
So, this version uses a default value. The general idea can be found here: http://blogs.msdn.com/b/infopath/archive/2006/11/27/conditional-default-values.aspx
-
Oh Browser Forms can be so pesky. Give me 5 mins and I'll update your sample with a different approach.
-
Rules fire when a field changes. In your sample, status is not the field that changes, so a rule will not fire. Here's your sample back w/ the rules on the repeating field instead and a custom condition.
-
Might be worth a try - you could use a formula to return the year, month and day - you'll want it formatted like:
yyyy-MM-dd
You can also import a schema for Excel to use for the XML that will indicate a date field - but the above may be a simpler approach....
-
As far as qRules in general - it adds a ton of functionality to InfoPath forms - but, like I said, we can't add code to SharePoint List forms. Your form would need to be created from one of the new blank templates. What are you trying to do in your SharePoint List form that you were hoping to do with qRules?
-
Want to attach your test form under the Options tab in a reply? I can try to take a quick look. :)