Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 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
I've a project that has been running for a while and the focus has been on implementation. Meanwhile, the documents have become out of date. The design document doesn't have all the functionality that has been added and so is the case with requirements document.
Going through the customizations and code to update the documents is a solution but am looking for options here...
Appreciate your suggestions
I don’t see enough room for any sort of automation to finish your jobs quickly.
I can feel, it’s hard to go object by object for each customized object and looking into code. Have a look at developer comments in code (if there are) and then add those in documentation, that why and how that customization was done.
This is exhausting practice going object by object, but there does not seems a ‘very quick way’.
There is a better solution - document changes during implementation, because that's when you have all information available. Analyzing code retrospectively and trying to figure out what requirements you have to build your code is much more expensive and the result is usually much worse.
You made a debt and now you have to pay it with interest.
That doesn't even sound better.
Guess reengineering is the only one way out
Except running through the code, there can be other sources of the information:
- one option is to check the time-sheets, made by the team, to figure out the list of additional functionality they have been working with
- I suppose you had some approval process of those functionalities with the customer, are there any approval documents left, or protocols of testing?
- If current documents are out of date, there might be evidence from customer's side for change requests or additional requests
- also you can interview existing consultants/developers for their recent achievements in this project
Is your project already live or yet to go live?
Better you start preparing the User Manuals, Change Request documents, Issue Log Registers etc. as updating requirement document or design document may not help to an extent.
Business Applications communities