-
Why not do something even more simple:
In the schema, combine all 4 into a single repeating group with an additional Status field. Then have each of the 4 repeating sections in the view bind to the single repeating schema node, and filter them based on the status.
Then when you want to move a row from one table to the other, simply change its ...
-
Hi Tobias,
Welcome to the InfoPath Dev Forums!
You can use a button with code behind it that calls:
XDocument.UI.ShowSignatureDialog();
But this doesn't specify a particular section.
-
You cannot create a new one. But you can modify an existing one by extracting your form files and editing the XSL for each view. Then just don't touch the color schemes again after that or you'll lose your changes.
-
Double-click your check box control and then click Rules.
You can add rules to copy the value of one field to another. Set up as many copy actions as you need to in your rule.
-
Your row.selectSingleNode() XPath is the problem. You are giving it an absolute XPath from the top of your schema instead of a relative XPath staring from the node itself.
It should probably be something like row.selectSingleNode(''my:field1'').text = ...
-
Right-click the field in your secondary data source in the Data Source task pane, and then choose More | Optional Section.
-
Calculated fields can (under certain circumstances) slow things down... but typically not substantially. How many rows are there of this 6 column table?
-
It sounds as though your field is not even present in the XML. Can you even type into the field? If not, then the field is not present for some reason.
-
Since your two trigger fields are field1 and field2, you need a duplicate set of rules on both of those fields. A better way would be to write one code function which does all this, and then use the OnAfterChange event on field1 and field2 to call that function.
But if you are determined to do this via rules, you still can. Its just more work. ...
-
Great! Glad you were able to get it working!