Our developer Zoia has been using the Covid-19 lockdown to tidy up a bit – namely in files like AX-D365/Documents/BP (Best Practice). Doing this, she discovered that the older documents stored were consistently shorter than documents of more recent date. She checked checked various documents and found out that the guidelines supporting developers in adapting MS solutions to customer-specific requirements had become increasingly detailed. However, this turns out to be an advantage for our customers as more detailed customizing rules significantly improve the quality of software development.

Countless documents had accumulated over a period of 14 years in the AX-D365/Documents/BP folder accessible to every Microsoft Dynamics user. It contains a collection of best practice descriptions and guidelines for various development projects in the Microsoft Dynamics environment.

When Zoia started sorting them by creation date, it turned out that the older the document was, the shorter it was. Searching for the cause of this quickly Zoia quickly discovered that the rules that Microsoft sets up for development work or customizing in connection with its products had become increasingly complex over time – solution approaches were consequently described in increasing detail.

Example: User Guide for Microsoft Dynamics 365 for Finance and Operations

A good example is the User Guide Microsoft Dynamics 365 for Finance and Operations – a comprehensive Microsoft ERP solution. First shock when opening: The document comprises a full 52 pages with 17 chapters. But this is exactly what the developer benefits from, because thanks to the deep level of detail he now knows exactly what he has to do.

Here comes a brief overview of the most important contents:

1. Everything about Task Tracker: standard workflows, diagrams with roles and status, etc.

2. Development environment: links, setup, how to’s, etc.

3. Development rules: Naming (all objects), labels, version control. Notes for non-standard cases, etc.

4. Information on all environments and standard release and deployment processes (code/models/databases/etc.)

5. Debugging in another development environment.

6. How-to guidelines for less experienced developers: recommendations, important lifehacks, possible bugs, etc.

Conclusion: The User Guide for  Microsoft Dynamics 365 for Finance and Operations is an extremely useful document that covers almost all possible scenarios – and thus prevents development team leaders from being kept from more important tasks by easy to solve questions from less experienced team members.

Good to know: xalution customers can be sure that our development team is always working according to the latest best practices – that’s how we ensure maximum quality. A BP Guide is part of the standard repertoire in each one of our projects.

Posts by 

Enter your keyword: