-
Thanks for posting back - I hadn't remembered that they were ordered alphabetically - glad starting them w/ 1, 2 and so on did the trick. :)
-
I would change all the multi-selects to regular string or number data types. Then I'd start the form design from InfoPath designer, and use the "manage multiple items" option so you can create multiple rows in your list from one form. If there were pieces of data that are consistent across all the list items created in a single form, ...
-
Let's see - is there a value in those repeating tables that is generally filled out? Like Patient Name? You could add a filter to the sum formula so that only rows where that field is filled out count. Try this for the gains total: sum(../my:group3/my:group4/my:GainsNumberCount[../my:GainsPatienName != ""]) and this for the losses ...
-
If you set your template to *not* upgrade existing forms, then previewed with existing XML, you sometimes get a better message - did you try that? I know for sure that Browser upgrades don't handle deleted nodes at all well, while Filler has no trouble w/ them... any chance you'd deleted (or moved) a node?
-
Use single quotes for your concat, then you can have doubles inside. concat('this is my text "', fieldhere, '" here is some more text')
-
Yeah, that should be - is this a multi-select list box? Save the attached sample locally, right click, select design, preview. Note the date is only required if you pick "orange" as an option in the multi-select.
-
I think you'd either have to save the form as source files and check out the order in the manifest, or re-add the views in the order you want, copying / pasting from your original views (which you'll need to rename) to the new views. I think the default view generally shows at the top of the menu, and then after that the order they were ...
-
So, yeah, the data set is updated each time. But you can set more query fields, as long as you are using equivalence (i.e. Status = Submitted and CurrentApprover = userName()). What helped me understand query fields better was dragging the query and data fields onto the form canvas, and adding a button to run the query. Then I could try various ...
-
I've seen forms before with multiple submit rules that submit "copies" with new names to the same library - I anticipate you could add a number of different submit data connections and just use a bunch of submit rules to handle this. You'd need to have a field in the form's schema (doesn't have to show on the form) to use ...
-
Looks like you have OvercapcityBeds with a default, and then you also have rules on that field, setting that same field. I would definitely do something different there. Get rid of the default and the rules on that field, just put rules on UnoccupiedRule with conditions to set it correctly. Your first rule on UnoccupiedRule could be to set ...