Slide
notes: This is an example of an Invoice. On this Invoice, we use a UNIT to
display the Line Items on the Invoice, and in the Unit, we use the 'Line
Iteration Count' Template to display the number for each Line Item.
Slide 2
Slide
notes:
Slide 3
Slide
notes: Our example is based on a Retail Invoice Report.
Slide 4
Slide
notes:
Slide 5
Slide
notes: Here we see the Tag in the main Document that calls the Unit.
Slide 6
Slide
notes:
Slide 7
Slide
notes:
Slide 8
Slide
notes: We note also that this type of Unit Call is based on a Data Source,
and for this type of Unit the Data Source is often ‘docwritespre’, i.e.
with a pre-prepared record specifically for the Report.
Slide 9
Slide
notes:
Slide 10
Slide
notes: Here we can see the Data Source listed.
Slide 11
Slide
notes:
Slide 12
Slide
notes:
Slide 13
Slide
notes:
Slide 14
Slide
notes:
Slide 15
Slide
notes: From the Metadata, we can retrieve the Data Source Layout.
Slide 16
Slide
notes: Our Unit, in this case, will display the Transaction lines, and the
Line Count in column 1 on the Invoice is based on the number of Transaction
Lines that will appear.
Slide 17
Slide
notes:
Slide 18
Slide
notes:
Slide 19
Slide
notes:
Slide 20
Slide
notes:
Slide 21
Slide
notes: The 1st Tag is the Item Line Count.
Slide 22
Slide
notes:
Slide 23
Slide
notes: And it uses the Template for 'Iteration Line Count'.
Slide 24
Slide
notes:
Slide 25
Slide notes: This Template is ALWAYS used with
a Data Source Record where the Unit is based on an included Data Set where
a number of Fields have correlated multi or iterative Values.
