by site-publisher | Sep 18, 2026 | Microsoft Dynamics 365 CRM
Before rebuilding the lead process so that sales steps can only be recorded by completing a task, four assumptions about the platform had to be tested rather than believed. All four held. The tests themselves turned out to be the fragile part. One assumption is that...
by site-publisher | Sep 18, 2026 | Microsoft Dynamics 365 CRM
The lead process rebuild depends on automation writing to records under its own name rather than under a person’s. That needed a separate identity with a narrow role, and a test of whether the platform will let such an identity do the work. It will do most of...
by site-publisher | Sep 9, 2026 | Microsoft Dynamics 365 CRM
The mutual action plan agreed with a customer now records what was promised and what actually happened. The third piece, how far each step slipped, turned out to be unable to hold a negative number, so a step finished ahead of its date and a step finished exactly on...
by site-publisher | Sep 9, 2026 | Microsoft Dynamics 365 CRM
Ten automations in the CRM were switched off, and the system’s own dependency check said nothing pointed at any of them. On that evidence all ten looked equally disposable. Half of them still could not be deleted. Five were removed and five were kept, for...
by site-publisher | Sep 9, 2026 | Microsoft Dynamics 365 CRM
The sales process keeps a plan of the steps to a first commitment, with a target date, a baseline and a slippage figure on each row. A question about the slippage field turned out to have an awkward answer: nothing computes it, nothing writes it, and every row in the...
by site-publisher | Sep 3, 2026 | Microsoft Dynamics 365 CRM
A CRM product catalogue is usually typed in once and then quietly drifts from whatever document is supposed to govern it. This one is generated, and the drift it replaced had been sitting there unnoticed. The catalogue is built by a script that parses the canonical...
