AgileApps Support Wiki Pre Release

Difference between revisions of "Common:Processing Related Records in HTML"

From AgileApps Support Wiki
imported>Aeric
 
(4 intermediate revisions by 2 users not shown)
Line 7: Line 7:
When formatting a record in the current object for printing, those related records and the fields they contain can be processed in a loop.  
When formatting a record in the current object for printing, those related records and the fields they contain can be processed in a loop.  


===Finding and Using Related Record Variables===
===Finding Related-Record Variables===
{{:Common:Finding Related-Record Variables}}


====Finding Related-Record Variables====
===Using Related Record Variables===
Related Object variables are found using the [[Template Variable Tool]].
 
Here, in the Email Template for Claims, the related ClaimItems object is being chosen from the category list:
:[[File:TemplateVariableToolRelatedObjects.png]]
 
Within that group, the Item Name field is listed, along with other fields in the ClaimITems object. Once selected, the variable name appears in the Variable area, along with the loop it needs to be surrounded by for processing:
:<tt>#foreach( $ClaimItems_record in $ClaimItems ) $ClaimItems_record.item_name #end </tt>
 
If a loop already exists, you would use only the variable name part:
:<tt>$ClaimItems_record.item_name</tt>
 
{{Note|<br>For a ''many-to-many'' relationship like one between Claims and Tags, the variable looks like this:
:<tt>$Claims_Tags_record.related_to_Tags.tag_name</tt>
where:
:* <tt>$Claims_Tags</tt> is the [[Junction Object]] that produces the many-to-many relationship
:* <tt>related_to_Tags</tt> is the name of the Lookup field in the Junction Object that references a Tags record
:* <tt>tag_name</tt> is the field to display
:* The "dot" separator (<tt>.</tt>) joins each of the segments in the variable name}}


====Processing Related Records in a Loop====
====Processing Related Records in a Loop====
Line 63: Line 46:


:* The Velocity <tt>#foreach</tt> directive does the looping.
:* The Velocity <tt>#foreach</tt> directive does the looping.
:: ''Learn more:'' http://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html
:: ''Learn more:'' http://velocity.apache.org/engine/releases/velocity-{{VelocityVersion}}/user-guide.html
:* The looping construct defines <tt>$OrderItems_record</tt> as a loop variable.
:* The looping construct defines <tt>$OrderItems_record</tt> as a loop variable.
:* The loop variable iterates over the <tt>$OrderItems</tt> array.
:* The loop variable iterates over the <tt>$OrderItems</tt> array.
Line 207: Line 190:
:[[File:OrderInvoiceSampleSegment.png]]
:[[File:OrderInvoiceSampleSegment.png]]


(The [{{DOCHOST}}/files/OrderInvoiceTemplate.html Order Invoice template] and the [{{DOCHOST}}/files/OrderInvoiceSample.html Order Invoice sample] file are both available in the downloads area.)
(The [https://agileappscloud.info/aadev-src/images/c/c6/Order_Invoice_Template.zip Order Invoice Template file] is available in the downloads area.)

Latest revision as of 08:07, 11 July 2023

About Related Record Variables

In a Custom Object, fields from related records can be added to a Document Template. (That is, records from an Object that has a Lookup to the current object.)

For example, OrderItems has a lookup to Orders, so in a Document Template for Orders, related OrderItems records can be accessed. (In an object Form, related records are typically displayed in a Subform, although they need not be.)

When formatting a record in the current object for printing, those related records and the fields they contain can be processed in a loop.

Finding Related-Record Variables

Related Object variables are found using the Template Variable Tool.

Here, in the Email Template for Claims, the related ClaimItems object is being chosen from the category list:

TemplateVariableToolRelatedObjects.png

Within that group, the Item Name field is listed, along with other fields in the ClaimITems object. Once selected, the variable name appears in the Variable area, along with the loop it needs to be surrounded by for processing:

#foreach( $ClaimItems_record in $ClaimItems ) $ClaimItems_record.item_name #end

If a loop already exists, you would use only the variable name part:

$ClaimItems_record.item_name

Notepad.png

Note:
For a many-to-many relationship like one between Claims and Tags, the variable looks like this:

$Claims_Tags_record.related_to_Tags.tag_name

where:

  • $Claims_Tags is the Junction Object that produces the many-to-many relationship
  • related_to_Tags is the name of the Lookup field in the Junction Object that references a Tags record
  • tag_name is the field to display
  • The "dot" separator (.) joins each of the segments in the variable name

Using Related Record Variables

Processing Related Records in a Loop

Typically, you'll create a table for the related records, define its headings, and then create a row for a single record, putting the related-record variables into the cells of the row. You then enclose that row in a loop, using the #foreach instruction defined by the Velocity templating engine.

Related records are returned in an array, so the loop creates a new table row for each record in the array.

Here is an example that processes OrderItems for an Order (with formatting attributes removed for simplicity):

<syntaxhighlight lang="xml" enclose="div">
<tbody> </tbody>
  1. foreach( $OrderItems_record in $OrderItems )
  1. end
...
Quantity Product Unit Price Amount
$OrderItems_record.item_quantity $OrderItems_record.related_to_ProductInventory.product_name $OrderItems_record.item_price $OrderItems_record.total

</syntaxhighlight>

where:

  • The <tbody> element is required around the header row.
  • The Velocity #foreach directive does the looping.
Learn more: http://velocity.apache.org/engine/releases/velocity-1.7/user-guide.html
  • The looping construct defines $OrderItems_record as a loop variable.
  • The loop variable iterates over the $OrderItems array.
  • The $OrderItems array is automatically available in the template, because OrderItems is a Related Object. (All related objects are available. Each is an array.)

Special Considerations for Subform Variables

Totals and additional computation fields defined for a Subform are also available in the Template Variable Tool. To find them, you access the main object (not the object displayed in the Subform), because those fields are added to the object that contains the Subform.

For example, the Subform for OrderItems totals the $Amount column, and then does additional computations on it to add a surcharge. Those values are shown in the $Orders Fields category as Total $Amount and Shipping for $Amount, respectively. (The final total is shown as Net Total $Amount.)

Sample Template for an Order Invoice

This sample:

  • Creates an invoice for an order, showing all items in it
  • Gets the name and price of order items from the ProductInventory object
  • Uses Velocity #foreach processing to process OrderItems records for an Order
  • Uses Velocity #if conditionals to display surcharge and discount rows only if those values are present
<syntaxhighlight lang="xml" enclose="div">

<html><head> <title></title> <style>

div {  
     padding-top: 5px;  
     padding-bottom: 5px;  
     padding-right: 5px;  
     padding-left: 30px;  
     border: 3px;  

margin-top: 5%; margin-right: 40%; margin-bottom: 5%; margin-left: 5%;

   }

</style>

</head><body bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">

<img width="100" height="100" src="http://justanothermobilemonday.com/Wordpress/wp-content/uploads/2009/10/android-robot-logo2.jpg" alt="Company logo" />    <---- Company Logo Here
$company.name

$company.street  
$company.city, $company.state,
$company.country - $company.zip

 
 (Phone): $user.phone



Order Invoice

Invoice Date: $Orders.date_created



Bill To:
$Orders.account.name - $Orders.account.number

$Orders.account.street
$Orders.account.city, $Orders.account.state,
$Orders.account.country - $Orders.account.zip

(Phone): $Orders.account.phone


Invoice #: $Orders.order_number
 

<tbody> </tbody>
  1. foreach( $OrderItems_record in $OrderItems )
  1. end
  1. if( $Orders.grid_surcharge_031f67dd4b3946949df2da276e5c82a6 > 0 )
  1. end
  1. if( $Orders.grid_discount_031f67dd4b3946949df2da276e5c82a6 > 0 )
  1. end
Quantity Product Unit Price Amount
$OrderItems_record.item_quantity $OrderItems_record.related_to_ProductInventory.product_name $OrderItems_record.item_price $OrderItems_record.total
  Sub Total $Order.grid_comptn_f5631e34b39f4ba39a98559c7215a3b4
  Surcharge $Orders.grid_surcharge_f5631e34b39f4ba39a98559c7215a3b4
  Discount $Orders.grid_discount_f5631e34b39f4ba39a98559c7215a3b4
  Tax $Orders.grid_tax_f5631e34b39f4ba39a98559c7215a3b4
  Shipping $Orders.grid_shipping_f5631e34b39f4ba39a98559c7215a3b4
  TOTAL AMOUNT DUE $Orders.grid_net_total_f5631e34b39f4ba39a98559c7215a3b4



Payment Due upon reciept
Thank you for your business!

</body> </html> </syntaxhighlight>

The Subform part of the resulting invoice then looks something like this:

OrderInvoiceSampleSegment.png

(The Order Invoice Template file is available in the downloads area.)