Personalized Community is here!
Quickly customize your community to find the content you seek.
Learn about installation, licenses and upgradesGuides overview | FAQ
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Okay Guides community before I write a big long Linkedin article about why I don't recommend using and implementing D365 Guides in your organization yet...(you can test it), I figured I would reach out and see your thoughts.
Here is the issue: when you create a Guide for use on your factor floor, or service bay or where ever how do you document that is Guide XYZ ver 1.xxx., for example?
In my job I create specific, technical documentation all the time. This year alone I have already worked on more than 30+ technical documents that gets released out to service reps and factor workers. Some of our equipment can cause serious harm if not properly built, serviced or installed. Changes to how that is done gets documented and pushed for CYA for everybody.
D365 Guides is part of the new world of "Technical Publications". Which is really important...have you seen the news of the Boeing 737 Max and its bad sensor causing plane crashes? Which means you need to be able to document, in the Guides what version your of "build a widget instructions v.1.x" is using.
I've looked through the documentation and am working on a new Guide this week and have yet to find a place to put version control on the Guide. Hello, Microsoft, you bought GitHub for software version control...D365 Guides specifically needs version control as well.
Imagine the scenario: (Tom) "Hey Bill you putting those new nose vA sensors on the Boeing 737 Max?" (Bill) "Yes Tom, I am, I love this new D365 Guides helping me." Mean while engineering had pushed a change to nose sensor vB but lack of version control meant Bill didn't know he was using an old version.
As i put in a previous linked in post, the current work around in to create a Guide slide with the version control listed on that slide. The issue from a security stand point is that while you can't currently delete guides, you can delete individual slides thus adding/removing a "version control" slide after the fact.
Hi Ken – This is a feature we are currently working on. In the meantime, we recommend creating a copy of your guide and putting a version number in the guide name (as you would with a powerpoint or word doc) when you make substantial changes. Is it ok if we reach out to you to get feedback and input on how we are designing versioning?
Authors can copy a guide on the PC app from the left nav here:
Business Applications communities