This post is part of a series on creating a module within a Microsoft Dynamics 365 for Finance and Operations application. Links to the other parts are available in the first post: Creating a Module in Microsoft Dynamics 365: Laying the Foundation.
A module in Microsoft Dynamics 365 for Finance and Operations is a grouping of similar business processes and functions that allow users to conduct business. Examples include General Ledger, Accounts Receivable, Accounts Payable, and many others. Developers create new modules to group new functionality in an equivalent manner or to produce third-party solutions.
In this series, I am creating a fictitious module called Generic Application Solution (GAS). The assumption will be that the reader has an intermediate knowledge of development in Dynamics 365 as well as best practices. This post will wrap up this series by adding the module to the module list and discussing other considerations.
Adding the Module to the Module List
A module should have a menu so that end users can access its forms, actions, and reports. This menu is a standard menu and should be structured in a manner that is consistent with the application. To add the module to the Modules tab on the navigation pane of the dashboard, developers add a menu reference to the module’s menu from the MainMenu menu.
Security
Even though it was not discussed in this series, security development is very important and the module’s features should have some form of security. Due to varying business requirements and other considerations, security is best served as a separate topic.
Dashboard
New to Dynamics 365 is the dashboard that includes a navigation pane. In the center of this dashboard, end users will find tiles that open workspaces for a more granular business process approach. These workspaces provide links to actions related to a business process along with other key performance indicators. While not really a requirement for a module, developers should learn to leverage these new features as to improve the user experience.
That concludes the series. Thank you for reading and good luck with your projects.
Dauvis' Dev Musings 