-
In other words, you want the button to only be enabled on the last section? If so, I believe the expression would be:
count(following-sibling::my:VenueRepeatingSection) != 0
-
You shouldn't need code to do this. Just create a Boolean field in your data source called showInfo1, and have it default to false. Create two buttons, one that says Show, and one that says Hide. Give the Show button a rule to set showInfo1 to true, and have Hide set showInfo1 to false. Then add conditional formatting ...
-
I would presume you have something similar to this in your other form as well, but the expression would be something like:
concat("Delete /xpath=/my:myFields/my:Venues/my:VenueRepeatingSection[", count(preceding-sibling::my:VenueRepeatingSection) + 1, "]")
-
Because based on the error message, it appears that the XMLs that are failing to open have a LumbarRange node directly under myFields. Would you mind placing one of these problematic XML files, and a screenshot of your current main data source, in a ZIP file and attaching it to this thread?
-
I think the likely case is that the other computers have an older version of the template and that is why they can still open the forms. You probably have a newer version that has been modified in such a way that the documents won't open in it anymore.
That is my guess anyway.
Regarding my earlier question, when you look at ...
-
Even if you have Automatic Versioning turned on, I believe that InfoPath will refuse to open a document if it contains nodes that it is not expecting in the main data source. This will happen if you have deleted or moved any nodes in the data source. Did you delete or move the LumbarRange node in the main data source?
-
Ah, sorry, I didn't notice that part. It's puzzling that that works when your original attempt (just having the field set itself) didn't, since one would think they would produce the same result. Just another one of InfoPath's quirks.
I suggest using the approach I described because it's guaranteed to present ...
-
Glad you worked it out. To which two methods are you referring?
-
It looks like you deleted and re-added the calculating field, and spelled its name wrong the second time so the rules and condition are referencing invalid field names. That's the main source of your problem. Also, as I said, you should re-open the condition dialog and set up the condition using the dropdown boxes instead of having ...
-
Hello Catherine,
You can create a repeating section or table bound to InterfacingSoftwareInformation inside the repeating section for InterfacedApplicationInformation. Then, in the Display tab of the properties dialog for the inner table or section, click Filter Data..., and set it to filter on the expression ...