Generate document has nothing to offer: no published template for this record type
Documents are generated only from published document templates of the record's type; the starter templates (cost sheet, allotment letter, offer letter and others) ship as drafts, so until someone publishes one, Generate document has nothing to pick, offers issue without a letter and workflow rules that generate the template fail.
Messages this explains
- “No published template for this record type”
- “Only published templates can be used. Publish one for this record type under Settings › Documents › Templates.”
- “Template <CODE> is not published”
- “Template <CODE> renders a <x>, not <y>”
- “No published template renders an offer, so this offer will be issued without a letter. To send one, publish a template under Settings > Documents > Templates (the starter "Offer letter (standard)" ships as a draft) and generate it from the offer afterwards.”
- “Drafts cannot be used yet. Publish the template to offer it on <record type> records and in workflows.”
Generate document has nothing to offer: no published template for this record type
You want to print a cost sheet, an allotment letter or an offer letter, but the template list is empty, the offer issues without a letter, or a workflow rule that generates the document fails.
What you see
- In the Generate document dialog on a record's Documents card (the estimate page, the booking's Documents tab, the opportunity, an offer, a demand): the Template list reads "No published template for this record type", with the help text "Only published templates can be used. Publish one for this record type under Settings › Documents › Templates."
- In the Issue the offer dialog on an allottee's offer (Society & Tenants or the allottee's page): "No published template renders an offer, so this offer will be issued without a letter. To send one, publish a template under Settings > Documents > Templates (the starter "Offer letter (standard)" ships as a draft) and generate it from the offer afterwards."
- On a template in the template designer that is still a Draft: "Drafts cannot be used yet. Publish the template to offer it on <record type> records and in workflows."
- On an errored run in Runs whose rule generates or attaches a document: "Template <CODE> is not published". The same text answers a generate request for a template that is a Draft or has been retired.
- When a document is requested (for example through the AI assistant) with a template made for another kind of record: "Template <CODE> renders a <x>, not <y>", for example "Template STD_ALLOTMENT_LETTER renders a booking, not estimate".
Why it happens
A template is written against one record type (for example estimate, booking, offer, opportunity, demand or payment) and kept as a draft while it is being designed. Only a published version is used to produce documents, so that every letter a buyer or member receives comes from wording someone has approved, and every generated document records the exact version it was made with. A draft, or a template that has been Retired, is left out of every picker and refused by workflow rules.
The starter templates are seeded as drafts for you to review before use: "Cost estimate sheet (standard)" for estimates, "Allotment letter (standard)" for bookings, "Offer letter (standard)" and "Term sheet (standard)" for offers, "Demand letter (standard)" for demands and "Receipt (standard)" for payments. Until one of them (or your own) is published, the matching records have nothing to generate.
A template also only fits the record type it was written for, because its merge fields read that record; a booking template cannot fill in an estimate.
How to fix it
- Go to Settings > Documents > Templates (Document templates) and find a template whose record type matches (Estimate for a cost sheet, Booking for an allotment letter, Termsheet for an offer letter). You need the View permission on Document Templates.
- Open it, check the wording in the preview against a real record, and click Publish. This needs the Publish permission on Document Templates; in the default roles the Administrator, the Sales Manager and Legal & Documentation hold it. A Retired template is brought back with Reopen (same permission).
- If no template of that record type exists, create one with New template (the Create permission on Document Templates), choosing the right record type, then publish it.
- Go back to the record and use Generate document again (the Create permission on Generated Documents). For an offer already issued without a letter, generate the letter from the offer's Documents card.
- For a workflow rule that failed, open the run on Runs and click Retry once the template is published (the Edit permission on Workflow Runs). If the rule points at a template of another record type, change the rule's action to a template made for the rule's record.
- For "renders a <x>, not <y>", pick a template of the record's own type.
Related
Related
- EstimateScreen
One estimate version: its charges by group, payment plan, approvals, unit and parking hold and validity, with the lifecycle actions to send, finalize, request approval, approve or reject, extend, cancel, version and book.
- Booking documentsScreen
The letters and agreements generated for one booking, such as the allotment letter, together with the receipts of its payments and the letters of its demands, with the button to generate another from a published template and the icons to preview, download, email, void or delete each one.
- Opportunity (Overview tab)Screen
One buyer's enquiry on one project: who they are, what they want, the current estimate, the latest activity, documents and tasks, with the pipeline actions (estimate, assign, book, mark lost, reopen) in the header.
- Society & TenantsScreen
On a redevelopment project, link the society being redeveloped, keep its members and the project's landowners and PAP tenants, and give each of them an offer that allots new units and sets the benefits the developer pays.
- AllotteeScreen
One society member, landowner or PAP tenant on a page: who they are, what they hold today, their co-owners, their offers on each project, the letters and files filed for them, their bank accounts and parking.
- Document templatesScreen
The list of your organization's document templates (demand letters, offer letters, termsheets, agreements, allotment letters, receipts, cost sheets), with filters and the actions to create, duplicate, open or delete one.
- Document templateScreen
The template designer: write a template's wording with merge fields, set its letterhead, title and page layout, preview it against a real record, and publish, retire or restore its versions.
- Generated documentsScreen
The organization-wide log of every document generated from a template or uploaded against a record, where you preview, download, email, void or delete them.
- RunsScreen
Every time a rule ran: what started it, which record it worked on, how each action went, and the panel from which an errored run is retried.
- Document templates, published versions and letterheadsConcept
A document template is an HTML letter with merge fields written for one record type; publishing it freezes a numbered version that generation uses while the draft stays editable, and a letterhead (the template's own, else the project's, else the organization's default) supplies the logo, header, footer and page layout around it.
- Generated documents: offer letters, cost sheets, void and supersededConcept
A generated document is a numbered, filed rendering of a published template against one record, kept with its merged text, template version and file; offer letters are generated when an offer is issued and supersede the earlier ones, cost sheets print an estimate for the buyer, and a void or superseded document keeps its number and shows a watermark saying what replaced it.
- Issue an offer with its letterHow-to
Publish the offer letter template once, then issue a draft offer so the letter is generated and filed with it and the offer moves to Issued.
- Template will not save, publish or render: a tag, expression or the HTML is wrongTroubleshooting
A document template, message template or rule action that carries a broken merge tag is refused when saved or published, names the field and the line; a template that parses but fails while filling in a record, or whose HTML the PDF or Word engine cannot lay out, fails at preview, generation or sending; the editor's own dialogs and fields have their own checks.