Works On My OrgUNABLE TO REPRODUCE.
Menu

Changelog

What changed here.

Pages carry a last-verified date. This is the record that those dates mean something: what was added, what was corrected, and what changed about how any of it is checked.

    • Version guide for Dynamics 365 Customer Engagement 9.x on-premises, written from Microsoft's current on-premises documentation: where the SDK went, the state of each endpoint, the Xrm.Page deprecation, plug-in rules that only apply on-premises, and virtual entities.
    • Version guide for Microsoft Dataverse, written from Microsoft's current documentation: continuous updates and release waves, the state of the 2011 SOAP and OData v2 endpoints, service protection limits, sandbox-only plug-ins and plug-in packages, custom APIs, and deprecated automation features.
    • Version guides for CRM 3.0 and CRM 4.0, written from Microsoft's install media (readmes, application Help and the 3.0 workflow tool Help): crmForm scripting, customization export and import, Workflow Manager, the 4.0 relationship and privilege model, and the traps in upgrading 1.2 to 3.0 and 3.0 to 4.0. Every version now has a guide.
    • The first tool: an error decoder. Paste a Dataverse or Dynamics CRM error, such as a SecLib::CheckPrivilege failure, a service protection limit or a sandbox crash, and get a plain-English explanation, what to do, and Microsoft sources. It runs in your browser and sends nothing.
    • CRM 3.0 callouts and the CRM 3.0 web services, written from the 3.0 SDK: callout events, pre-callout return values, callout.config.xml, error handling and loops, and CrmService, MetadataService, impersonation, DynamicEntity and the two query styles.
    • CRM 4.0 plug-in registration and the 2007 endpoint, sourced from the 4.0 install media and the CRM 2011 SDK: steps registered with the Plug-in Registration tool, parent and child pipelines, and what broke on upgrade. The callout and CRM 3.0 web service pages now say what came next.
    • CRM 4.0 plug-ins, written from the CRM 4.0 SDK: IPlugin and its context, the five-stage pipeline with parent and child pipelines, registration with the sample tools and its permissions, impersonation and offline plug-ins. The CRM 4.0, callout and CRM 3.0 web service pages now reflect the 4.0 SDK, including how 4.0 still ran 3.0 callouts and the 2006 endpoint.
    • Callouts to plug-ins: CRM 3.0 callouts, CRM 4.0 plug-ins, CRM 2011 and Dataverse compared side by side, with the upgrade breaks between each and a table for porting an old callout.
    • crmForm to Xrm.Page to formContext: form scripting across CRM 3.0, 4.0, 2011, 2013 and Dataverse, with the same tasks written each way and the upgrade breaks between them.
    • CrmService to the Web API: every CRM web service endpoint from the 2006 services to Dataverse, with what each era changed and a table for recognising old endpoints in code.
    • What should my classic workflow become? A decision table from Microsoft's comparisons of flows, classic workflows, custom process actions and custom APIs, plus how workflow evolved from CRM 3.0 to Power Automate.
    • Customization XML to solutions to pipelines: how each era packaged customizations, which layer wins, update versus upgrade versus patch, and why a field can’t be removed while something depends on it.
    • Solution component type decoder: look up componenttype numbers or names against Microsoft's published list, with a full reference table that works without JavaScript.
    • Plug-in stage and mode explorer: pick a stage, mode and message to see timing, transaction, rollback and image rules, with a comparison table that works without JavaScript.
    • On-premises upgrade paths: the first On-prem page. The supported path into every release from CRM 3.0 to 9.x, interim upgrades with trial keys, the three upgrade methods, pre-upgrade checks, and supported Windows Server and SQL Server versions.
    • Dropped the planned Plugin to Solution Finder, the one tool that would have signed you in to your own environment. Every tool on the site runs in your browser with no sign-in.
    • CRM 4.0: a new section on web service authentication, from the 4.0 SDK. Active Directory, Internet-facing deployment (IFD) tickets and CRM Online Passport tickets, and what claims-based authentication replaced them with in CRM 2011.
    • CRM 4.0: Internet-facing deployment setup from the 4.0 Implementation Guide (sign-in by IP address, configuration settings, DNS, wildcard SSL, hardening), and 4.0’s supported Windows Server and SQL Server on the upgrade paths page.
    • CRM 2011: upgrading from CRM 4.0 and claims-based Internet-facing deployment, from the 2011 Implementation Guide, plus CRM 2011’s supported Windows Server and SQL Server on the upgrade paths page, which now has a row for every release.
    • Pre-launch corrections: the privacy page now says up front that Ask and page feedback send data too, the terms describe the reference material and tools, and empty sections and product pages are out of the navigation until they have something in them.
    • worksonmyorg.com leads with the Works On My Org company site again: products and services come first, and this reference has its own home at /reference/. Every reference page keeps its address.

    • The site becomes a version-aware Dynamics CRM and Dataverse reference, covering CRM 3.0 through current Dataverse.
    • Version landing pages for all eight releases, with CRM 3.0 treated as a first-class page rather than hidden under a legacy menu.
    • Search that keeps error text and identifiers intact, so a pasted exception finds the page.
    • Every technical page now shows which versions it applies to, what evidence sits behind it, and when that was last checked.
    • Added a feedback control on technical pages and an Ask page for questions the site cannot answer yet.
    • Published the sourcing method, this changelog, and what is planned next.
    • Version guides for CRM 2011, 2013, 2015 and 2016 / 8.x, written from Microsoft's SDKs and archived developer documentation, with lifecycle dates checked against Microsoft's lifecycle pages.