-
I think you can workaround this by adding an temp field on your form. Set the default value of your temp field to AccountID and then create your action rules off this temp field. This should work for the single person case. You'll have to play around with it if you need this to work for the multiple selection case.
-
You can create a rule on the Submit button by adding your own button to the form and then adding your own rules as well as the submit rule. You'll probably have to remove the ribbon ribbon from the options menu.
I'm not sure if there is a PreSaveAction() equivalent in InfoPath.
-
I've attached an XSN that hopefully has the behaviour you are looking for. If you have any questions or if I misunderstood your scenario, let me know.
-
It depends on what kind of data connection you are using. For example, the list data connection in 2010 has support for query fields so you can filter you data that way. Web service connections can be set up to allow querying as well.
-
The filter option is located in the control properties -> Display Tab -> Filter Data
-
Hi there,
You can create a secondar data connection to your list/library and then drag the repeating node form that schema to your form as a repeating table. In the repeating table, you can either set up filters in the properties or conditional formatting to hide the rows based on the criteria you specified.
-
It's not there. You'll have to type it yourself.
-
You can use the format-number function like this: format-number(field1, "$###,###"). Then you can just append the additional text that you want. Just to warn you this function only works on the client and will not work in the server. I'm not sure if there is an easy solution for the server.
-
Sounds doable, but you'll likely need some qRules functionality that isn't offered out of the box to accomplish this. I'm thinking you can do some logic to calculate the sum and then use the insert and delete commands to manage the second repeating table.
-
Have you tried using preceding sibling? Here is a blog post that may help: http://www.infopathdev.com/blogs/greg/archive/2005/06/13/Using-XPath_2700_s-_2700_preceding_2D00_sibling_2700_-Axis-Correctly.aspx