-
You can probably do this using a filter with preceding-sibling again ... the filter would be on your drop down list entries, checking to see if the preceding sibling Rooming Table nodes have the value - but I'm not sure off-hand if you'd also need to check based on the Hotel group - you'll have to experiment a bit....
-
It looks like this may be by design - I just created a test form and submitted it via email (not including the form as an attachment) and the attachment is not included. You may need to include the form when you submit.
-
concat("Delete /xpath=my:myFields/my:Rooming/my:HotelGroup/my:HotelRepeatingSection[", count(preceding-sibling::HotelRepeatingSection) + 1, "]/my:RoomingGroup/my:RoomingTable[", count(preceding-sibling::RoomingTable) + 1, "]")
-
Yes - you'll need to move back up the tree - you are on RoomingTable, so it would be something like ../../preceding-sibling::my:HotelRepeatingSection for the XPath in your count formula (may be one more ../ in there)
-
I think you'd need to specify your HotelRepeatingSection as well - have you tried that?
-
As I said, you can use the concat function to indicate which of the repeating parent groups should have this inserted. If this is a client form, you could use the position function. If this a browser form, you could use a count of preceding-siblings (this is assuming that the rule to insert the child repeating group is on the parent).
-
Yes, GetInputParameters works in the browser - be sure to set your rule on the Qdabra Rules data source finishedLoading node (finishedLoading = true). Since rules run before code, you want to use the finishedLoading node for running qRules commands on form open.
-
There's an alternate syntax if you want to add a filter - xpathsrc.
So, your command would be something like:
Insert /parent=/my:myFields/my:Rooming/my:HotelGroup/my:HotelRepeatingSection[2]/my:RoomingGroup /xpathsrc=/my:myFields/my:Rooming/my:HotelGroup/my:HotelRepeatingSection/my:RoomingGroup/my:RoomingTable
You can use a concat formula ...
-
Hi -
The issue with submitting to a lookup is that the lookup expects a particular syntax - ID;#Display
For example:
1;#Denver
There are different ways you could do this - easiest may be to add an additional field to your form that has a default value to set it to the correct ID & Display combo.
I belive if you replace the ID with ...
-
Do you have a try/catch in your on load so you can check for errors and show a message box with the error? That may help you.
I've seen this case issue before - even though I was passing in and checking for a param with proper case, IP was getting one with all lower case - and no, it wouldn't surprise me if browser and filler behaved ...