-
I don't know when exactly this happens (maybe upon saving?), but my filter formulas (lots of them) lose their current() function at random times. It's really irritating to go through and re-enter the current() on multiple filters every now and then.
-
Thanks. I got it to work. My users will love that.
-
Thanks, Patrick, that's exactly what I ended up doing.
I added a row number field to both of my tables and had one populate a count(preceding-sibling::Group1) +1 on one of them and count(preceding-sibling::Group2) +100 on the second one. That way I have reference to the list items in case a user needs to delete them. Then I ...
-
You were right about all of that. Thanks.
-
I'm getting a wierd error when trying to delete a row from a table based on a value from another table.
My command is - concat("Delete /xpath=/my:myFields/my:Labor/my:MasterLaborCall/my:MasterLaborRepeating[../my:MasterLaborPerson=", Employee, "]")
The error I get is -
Action: Delete. ...
-
Hi guys. It's me again.
I have a labor order form that has two repeating tables that pull data from 2 sepearate SharePoint lists. One to order internal employees, and one to order freelancers.
In another view of the form, we have a repeating table set up for rooming and travel info. I would like to just have one ...
-
Yes! That's great! I'm learning a lot about the siblings these days.
-
Thanks,
I got it to work with - count(../my:VenueRepeatingSection) = 1
Now I have to figure out how to disable a button if a following section is present.
-
That disables it permanently, no matter how many sections are added.
-
The formula just consists of the delete command with the xpath to the repeating table. Wierd.
Another question. Now that the delete works (thanks), how do I format that button to be disabled if there is no second section present? IE, I don't want users to delete the only section existing in the form.