Table Field Setup in WorkGuru Document Templates

When setting up tables to display recurring information in WorkGuru, they have a couple of pre-requisites to be completed so they are able to display the information correctly. These tables should have two rows, the header row, and the row that will be duplicated.

Headers

The table must have a header row, even if it is blank. WorkGuru won't display table rows without a header, even if the row fields have been correctly added. Note that the header (E.g. Products) must be entered directly above the lines that will be auto populated.

Table Properties

The table's alt text description field needs to be filled in so WorkGuru knows which data it needs to populate the rows with.  If you are setting up a table from scratch.  To access the table's alt text description field, right click the table and open the Table Properties.

Select the Alt Text tab:

Enter the following text in the Description field depending on the type of table it is:

• Products/Costs - Products
• Product/Cost options - ProductOptions
• Tasks/Labour - Tasks
• Tasks/Labour options - TaskOptions
• Timesheets - Timesheets
• Purchase orders - Purchases
• Purchase order line detail- PurchaseLines
• Purchase orders grouped by supplier or PO - AltPurchases
• Invoice payments - Payments
• Lead activities - LeadActivities
• Project/Quote phase summary - PhaseSummary
• Project/Quote phase details - PhaseDetails (note: The PDF converter we use can sometimes have difficulty handling nested tables. In circumstances where the printed PhaseDetails table is formatted incorrectly when printed to pdf, we recommend instead printing to docx and converting to pdf from MS Word )
• Invoice summary - InvoiceSummaries
• Purchase order summary - POSummaries
• Stock usage summary - StockUsageSummaries
• Production job output - Output
• Project notes - Notes

Note: you can only have ONE of each table type (e.g. you cannot have 2 tables with the Alt Text of "Products" on the same template.

A general rule when using tables is to make sure that the columns line up with the rows, as failing to do so can result in the document not printing correctly or at all. Below you will find an example of a correctly set up table and an incorrectly set up table.

Correct set up:

note how all cells are mirrored on the top and bottom rows - all columns are balancing with the rows

Incorrect set up:

note how the cell with [PhaseName] in it is the length of both the cells underneath which is not balancing the columns and rows

Nested Tables

A nested table in it's most basic form is a table with another table sitting inside of it, the only table type that WorkGuru has which supports nested tables is the PhaseDetails table for quotes/projects that have phases applied. Nested tables follow the same rules/requirements as the tables that sit within (E.g. ensuring that "PhaseDetails" sits within the alt text of the table properties, making sure the table has a header row, etc). An example of a PhaseDetails nested table set up with both Task and Product tables inside of it can be seen below:

Once your tables have been set up correctly, ensure you have entered the correct merge fields to populate your document accordingly. Please note that WorkGuru reads these and matches them to pre-defined fields, so they must match exactly to work. See here for available merge fields.