I have used the following second address placeholders in a quote template. I have (of course) filled this data in for the contact in question. However, the data is not populated into the quote when the template is used in Quote Builder.
The contact placeholders you’re trying to use (##CONTACT-xxx) is not intended for Quote templates. As noted in this guide, you may use global placeholders, however:
Placeholders allow information to be auto-populated into the quote template. Check out this guide on global placeholders to use them in quotes and throughout Jetpack CRM.
Thanks for getting back to me, but please forgive me, I don’t think I understand. Your documentation doesn’t say that at all – in fact the list of placeholders in System Assistant specifies just the opposite.
I note that the list of GLOBAL placeholders does not include any of the CONTACT-xxx. However, CONTACT-PREFIX and CONTACT-LNAME work absolutely fine.
Then, in the list of the CONTACT placeholders, a whole load of CONTACT-xxx are listed to be available for QUOTEs, including SECADDR1, SECADDR2, SECCITY, SECCOUNTY, SECPOSTCODE and more.
I’m not sure why you would go out of your way to include some but exclude other CONTACT-xxx fields from the quote section. How can you build a proper written quote that a potential client would take seriously (either by text in an email or in a PDF) without having the proper details available on the quote?
For that matter, having custom fields generally available for quotes would seem to be very sensible too. But I accept that the nature of Custom Fields and their naming could cause conflicts.
I note that the list of GLOBAL placeholders does not include any of the CONTACT-xxx. However, CONTACT-PREFIX and CONTACT-LNAME work absolutely fine.
That is correct. Unfortunately some Contact placeholders work in Quote templates and others do not (such as ##CONTACT-SECADDR1##, ##CONTACT-SECADDR2##, ##CONTACT-SECPOSTCODE##). This is a bug that our development team is aware of and it is on their roadmap to fix this. However, there is no ETA on when this fix will be released.
In which case, might I respectfully suggest that the documentation available for users is temporarily changed so that people like myself don’t spend hours banging their heads against a brick wall for no good reason?
