All Line Items Table Fields Reference

The All Line Items table prints every line type (tasks, products and phases) in one table, in the same row order as displayed in a WorkGuru quote, project or invoice. This table can be used in place of the separate Tasks, Products and Purchases tables, or alongside them.  

• Row Visibility - Line types included in the table are only printed if they are on the source document. For example, the table has a task and product lines, and the quote you are printing has no tasks, the quote will print products only. 
• Display Order: If task and product lines are NOT ordered by phase in the source document, tasks will print before products. On invoices, purchase lines print after the tasks and products, and unphased purchase lines print at the end.
• Phases - The All Line Items table replaces the existing Phase Table fields. When phases are present the lines are printed in the folllowing order:
  • Unphased lines come first.
  • Each phase follows, with an optional heading row, its tasks and products, and on invoices its purchase lines.
  • An optional subtotal row can close each phase.

Document Compatibility

The All Line Items table fields are supported on the documents that support phase line items:

• Quotes - see Quote Document Templates
  

• Projects - see Project Document Templates

• Invoices - see Invoice Document Templates

All Line Items fields are table fields, meaning they must be placed inside a correctly configured table in your Word document template. Merge fields and table Alt Text are case sensitive and must be entered exactly as shown below. 

Setting Up All Line Items Tables

All Line Items fields are table fields and must be placed inside a correctly configured table in your Word document template.

The table requires:

• A header row
• A repetition line row of each type of line (Phase, Task, Product and/or Purchase) containing your merge fields. You can only use one row per type and each row can only contain that particular type's merge fields.
• The correct Alt Text Description: 
  • AllLineItems

Phase fields must be placed inside a table in your document template. WorkGuru uses the table to automatically repeat the row for each applicable product line on the transaction. For detailed instructions, see Table Field Setup in WorkGuru Document Templates.

Phase Headers

Phase fields replace the current dedicated Phase Tables. Nested tables are no longer required. Phase header rows are optional. Without a header row, phased lines still group together but have no heading. If the table has a phase header row and contains only un-phased lines, the header row is not displayed.

Note: [LinesPhaseQuantity] is the phase quantity set in the editor. A phase with none set prints 1.

Phase SubTotals

Phase subtotals can be used as a standalone row to display logically. Amounts Are the total of the phase lines sell price. Phase subtotal rows are optional. Without a subtitle row, phased lines still group together but have no subtotal. If the table has a phase subtotal row and contains only un-phased lines, the subtotal row is not displayed.

Task Lines

If you want to include task information in the All Line Items table, add a row and add any Task Table fields as required. Ensure all task fields are added on the one row.

Product Lines

If you want to include product information in the All Line Items table, add a row and add any Product Table fields as required. Ensure all product fields are added on the one row.

Purchase Lines (Invoices Only)

If you want to include billable purchase information in the All Line Items table, add a row and add any Purchase Table fields as required. Ensure all purchase fields are added on the one row.

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 [LinesPhaseName] 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.