Filing a generated document to the record automatically

Microsoft Dynamics 365 CRM

A document the system generates had to be handed over for a person to upload by hand, because sending the file through the tooling cost too much. That turned out to be a fact about typefaces rather than about documents. The skill builds a one page executive summary from what the customer said on the […]

In this series · Part 19 of 27

1Dynamics 365 CRM: API integration + change-control repo2Dynamics 365 CRM: Last Contact Engagement tracking on Accounts3Turning a sales-intelligence export into a clean CRM data model4Dynamics 365 CRM: contacts inherit their company’s website, and emails timestamp by send time5Your SEO health now lives as a dashboard inside the CRM6Contact form duplicate detection now reads the request, not just the address7Marketing list members now show engagement and account fit8Campaign responses now create leads behind a confirmation step9Three CRM automations passed their tests without running the code that had just changed10A signature defect that three mailboxes agreed was not there11Why a corrected email signature kept sending the old one12A read-only CRM endpoint for scoring outside the desktop13Choosing what runs the AI layer in the CRM sales process14Asking whether a partner is involved, instead of inferring it15An email step in the sales process can now be excused, not only sent16The rehearsal that guards every process change had been failing silently17A one to one email from a lead left the engagement record blank18Two local dependencies, and only one was obvious19Filing a generated document to the record automatically20One meeting that served two process steps, recorded as two21A setting that stored correctly, read back correctly, and was never in force22Generating a product catalogue from one canonical file23Three date fields that existed on every row, and had never once been written24Unused, unreferenced, and still not safe to delete25A measure that could not record early26A sales automation that runs as itself, not as an administrator27A stage change that was refused, and reported as a success

On this page

Free Revenue Lifecycle Assessment

Connect with Marissa Wright to receive a free Revenue Lifecycle Assessment Report on your own business.

Book a consult →

A document the system generates had to be handed over for a person to upload by hand, because sending the file through the tooling cost too much. That turned out to be a fact about typefaces rather than about documents.

  • The skill builds a one page executive summary from what the customer said on the discovery call, quoting them rather than summarising, and files the PDF onto their record itself.
  • The earlier measurement put a single page at roughly 178,000 tokens, which is what ruled this out. Re-measuring showed the cost is driven by how many typefaces are embedded, not by length. One page using a single family came in at 232 kilobytes against 521 for one using eleven.
  • The size check now runs at the moment of upload rather than sitting in the documentation as a claim. Over the limit, the file is handed over and the number reported.
  • The generator can refuse. The field holding the customer's own cost figure accepts anything, and on one record it held a number identical to that company's revenue. Reading that field and printing it produces a confident wrong document, so an implausible value stops the run.

Other Posts