-
Hello Ben,
The problem here is with the design of your data source. For the Insert command to work properly, the repeating node being modified needs to have its own parent, whereas ExpenseItems and Mileage both have sibling nodes that share the same parent nodes as themselves (ExpenseSubTotal, FuelType, etc.). Giving repeating ...
-
I'm not really clear on what the problem is. Could you describea little more succinctly what's currently stopping you from doing what you want?
-
The way to accomplish this is to apply conditional formatting to the repeating table, with the condition to Hide if the data for that row is not selected in the other views.
-
Hi Ben,
Could you send a copy of your form to our support alias "support AT qdabra DOT com" so we can have a look?
-
The only way around the lack of the AddDays function is to write code that does something similar. It would be some fairly simple code that calculates the number of days between today and the specified date, place that value in a field somewhere, and then use that number for your conditional formatting. It's our general policy not ...
-
Could you attach a screenshot of how you want it to look? I'm having trouble picturing what you're describing.
-
What color do you want it to be if it's in the past?
-
That's not a bug. There are actually two rows each for apple and banana and that's why two appear for each.
-
Is this what you're trying to accomplish?
-
Something like this should work:
Condition
translate(field, ":-T", "") <= translate(xdDate:AddDays(xdDate:Today(), 7), ":-T", "")
Shade green
Condition
translate(field, ":-T", "") > translate(xdDate:AddDays(xdDate:Today(), 7), ":-T", "") ...