Asset fields allow you to insert information about a WorkGuru Asset into supported document templates.
These fields can be used to display information such as:
Document Compatibility
Asset fields are designed for Asset document templates. When an asset is linked to a quote or project, you can then also print asset fields on the following document templates:
- Quotes - see Quote Document Templates.
- Projects - see Project Document Templates.
- Invoices - see Invoice Document Templates.
Asset fields are Universal Fields, which means they can be placed directly within supported document templates and do not need to be inside a repeating table. Merge fields are case sensitive and must be entered exactly as displayed below.
Asset Information
Use these fields to display the primary information recorded against the Asset.
| Description | Merge Field |
|---|---|
| Asset Name | [AssetName] |
| Asset Serial Number | [AssetSerialNumber] |
| Asset Type | [AssetType] |
Asset Custom Fields
Custom Fields can be included in Asset document templates. Use Custom followed by the custom field name.
For example, if an Asset has a custom field name called:
WarrantyExpiry
the merge field would be:
[CustomWarrantyExpiry]
Custom field availability depends on how the custom field has been configured in WorkGuru. For more information, see the Custom Fields Guide.
Troubleshooting
Asset Fields Are Blank
Any Asset field without a corresponding value may return blank as it is correctly printing nothing. Check that:
- The source transaction has an asset assigned to it.
- The required information has been entered against the field in the Asset.
Merge Fields Appear Instead of Values
If fields such as [AssetName] or [AssetSerialNumber] appear in the generated document instead of their values, check:
- Merge field spelling
- Capitalisation
- Document compatibility
- That both square brackets are present
Merge fields are case sensitive.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article