I’ve had trouble deciding on what comes after it – and sticks around for longer than a year or two. Yes, you’ll still find the term “CRM” all over my blog. Let’s dive a bit deeper into the what, starting with a look back at what has happened in our earlier episodes of Microsoft business applications branding. Thanks for coming, have a save ride home! The actual topic of this post is about what the title says: Dynamics 365 Customer Engagement is now officially gone from the Microsoft cloud.
A slide deck created by Microsoft in 2016 for the Dynamics product offering would hardly pass the code validation today – yet you still see some partners out there just happily using these legacy materials in customer dialogue. You could think of it as a new API version that MS product marketing releases, which means you need to perform updates to your “code” to keep its API references compatible with the surrounding reality. This happens when the product branding gets updated by Microsoft as part of their evolving commercial offering, or when existing technologies are realigned to be used in a new context. Like with actual coding, sometimes there are breaking changes introduced into the concepts that are used in technical writing, too. Since I don’t write any actual computer code for a living, I guess this is my way of “debugging” the deliverables that I actually ship. Yeah, the customers reading them probably wouldn’t notice the difference, but if you let go of your standards then sooner or later the lazy writing will lead to unnecessary confusion.
Some might consider me a pedantic guy who’s always correcting some insignificant details in documents or presentations that cover Microsoft technologies but aren’t using their correct names. I always prefer to use precise terminology when talking about the technologies that are part of my trade.
0 kommentar(er)
