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 'Alpha-Numeric Iteration' Template for some of
the Values.
Slide 2
Slide
notes: The Description & Document columns both use this kind of
Template.
Slide 3
Slide
notes:
Slide 4
Slide
notes: Our example is based on a Retail Invoice Report.
Slide 5
Slide
notes:
Slide 6
Slide
notes: Here we see the Tag in the main Document that calls the Unit.
Slide 7
Slide
notes:
Slide 8
Slide
notes:
Slide 9
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 10
Slide
notes:
Slide 11
Slide
notes: Here we can see the Data Source listed.
Slide 12
Slide
notes:
Slide 13
Slide
notes:
Slide 14
Slide
notes:
Slide 15
Slide
notes:
Slide 16
Slide
notes: From the Metadata, we can retrieve the Data Source Layout.
Slide 17
Slide
notes: We will connect the Tags back to this Layout, to understand where we
get the answers from.
Slide 18
Slide
notes:
Slide 19
Slide
notes:
Slide 20
Slide
notes:
Slide 21
Slide
notes:
Slide 22
Slide
notes: This is our Unit example for this Report, and the 'Description' Tag
uses the Template for Alpha-Numeric Iteration.
Slide 23
Slide
notes:
Slide 24
Slide
notes: The answer comes from Data Field number 2, which we can also see on
the Data Layout.
Slide 25
Slide
notes:
Slide 26
Slide
notes:
Slide 27
Slide
notes:
Slide 28
Slide
notes: Likewise for the 'Doc' Tag.
Slide 29
Slide
notes:
Slide 30
Slide
notes: The answer is from Data Field number 3.
Slide 31
Slide
notes:
Slide 32
Slide
notes:
Slide 33
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.