The rehearsal that guards every process change had been failing silently

Microsoft Dynamics 365 CRM

Before any change to how the sales process behaves, a rehearsal runs the whole twenty step chain against a test record and reports what broke. It had been stopping at the second step for three days, and nothing said so, because a rehearsal nobody runs looks exactly like one that passes. The rehearsal did not […]

In this series · Part 16 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 →

Before any change to how the sales process behaves, a rehearsal runs the whole twenty step chain against a test record and reports what broke. It had been stopping at the second step for three days, and nothing said so, because a rehearsal nobody runs looks exactly like one that passes.

  • The rehearsal did not know about a question added to the process the day before, so it never cleared that answer between runs. The test record carried a stale answer from an earlier run, which made the first step pass for the wrong reason.
  • It also never attached the document that the process has required since the end of August before it will close a review step. That is what stopped the run at step two, so steps three to twenty had not actually run in three days.
  • Both were repaired. The full chain now passes twenty one of twenty one steps, the count of records created comes out exact, and the test record is left clean.
  • It was found only because a separate change needed proving. Nothing reports a rehearsal that is not being run.

Other Posts