Purchase Line Table Fields Reference

The PurchaseLines table displays individual Purchase Order line information associated with a Project. Use this table when you need to show the individual items ordered rather than summary-level Purchase Order information.

• Purchase Line Information
• Purchase Line Quantities
• Purchase Line Financials

Purchase Lines vs Purchase Order Summaries:

• Use PurchaseLines when you want to display individual Purchase Order line items associated with a Project.
• Use POSummaries when you want to display one summary row for each Purchase Order associated with a Project or Production Job.

For the complete list of Purchase Order Summary fields, see the Purchase Order Summary Table Fields Reference.

Document Compatibility

Purchase Line tables are supported on the following documents:

• Projects - see Project Document Templates
• Production Jobs - see Production Job Document Templates

Unlike Universal Fields, these fields must be placed inside a correctly configured table. WorkGuru uses the table to automatically repeat the applicable row for each line. Merge fields and Table Alt Text are case sensitive and must be entered exactly as displayed below.

Setting Up a Purchase Lines Table

Purchase merge fields must be placed inside a correctly configured table. The table requires:

• A header row
• A repetition row containing your merge fields
• The correct Alt Text Description. Set the table’s Alt Text Description to:
  • PurchaseLines

When WorkGuru generates the document, the purchases line row is repeated for each applicable purchase order on the transaction. For detailed instructions, see Table Field Setup in WorkGuru Document Templates.

Purchase Line Information

Purchase Line Quantities

Purchase Line Financials

Troubleshooting

Table Does Not Populate

Check that:

• The Alt Text Description is correct.
• Capitalisation matches the required table name - alt text descriptions are case sensitive.
• There is only one table of the same type on the document.
• The table is supported by the document type.
• There is applicable data to display.
• The table has a header

Merge Fields Appear in the Generated Document

If fields such as [PoName] appear instead of actual values, check:

• The spelling of the merge field. 
• Check capitalisation - merge fields are case sensitive.
• Confirm the field belongs to the table type being used.
• Confirm the field is supported by the document type.

Table Formatting Is Incorrect

Check that:

• Header and repetition row columns align.
• Cells have not been incorrectly merged.
• Nested tables are configured correctly.
• Each table has the correct Alt Text Description.