i have a document that i want to send as a reminder to the customers. The document has a small table with positions and amount of older unpaid invoices followed by a first sum and if the customer already paid some money, there is a second list with position and amount of the paid money and the total sum.
invoice 1 ... 100€
invoice 2 ... 150€
sum so far ... 250€
already paid1 ... 50€
already paid2 ... 35€
total .... 165€
As the design is now, i can't make one list for all positions because of the sum in the middle which is also differently formatted in word so i have two seperate repeats for the invoices and the paid amounts. The design is set!
And as long as i have items in both lists, everything is fine. But when the customer didn't pay anything yet, the second list should be deleted. So i added a condition in the repeat tag around the position and amount and added the necessary stuff in the customxmlpart. the condition works as it should . Is the value false, the table row gets deleted, is the value true, the row stays there. The problem is now: if the condition is true and there are more than one paid item like in the example above, only one item is displayed.
It seems, that the repeat mechanism breaks when the repeat comes with a condition. Normaly the tag with the repeat also changes to something like od:rptd=x7&od:RptInst=2, but also that doesn't happen. It is like the repeat is ignored after the condition is processed correctly.
Is this by design or a bug or a feature? Has anyone encountered this problem an has a workaround.
Of course i can traverse through all sdts, get the condition, follow the mappings, evaluate the value und delete the rows on my own, but i would like to avoid the work, when i can get the opendopehandler to work.