Nishant's Blog

AX7/Dynamics 365 for finance & operation: How to avoid user interaction while printing multiple cheques(Mass cheque printing) You all might be aware of the ‘Generate Payment’ functionality available in Dynamics AX. This function we use to generate/print cheques. The process is to create one payment journal, add few transactions with mode of payment as ‘Cheque’ then go for ‘Generate Payment’ option available in the drop down of ‘Function’ menu item button. Process is specific to print one cheque at a time for a single journal. Recently I came across a requirement where I had a customized form which contains multiple journal records and I have to add the ‘Generate Payment’ button on the form to allow user to print the checks for journals, and also allow user to select multiple journal records at the same time to print cheques and avoid user interaction with the system for each cheque. The major challenge here was, how to handle user interactions everytime to print multiple

Dynamics 365 for finance & operation/AX 7- Chain of command In past couple of releases and updates from Microsoft, Dynamics 365 for finance & operation aka AX7 came up with a lot more new Extension feature. Current version came with a lot of hard sealed version and few are soft sealed. Hard seal packages will not allow a developer to make any changes in the existing code but still this flexibility is there with the soft sealed packages. But it's best practices to avoid changes or modifications in the existing piece of code because you never know the next version will come with all hard sealed packages. So there are multiple extension features that we are already aware of like delegates, events and pre & post event handlers. As part of update 9, Microsoft has given one more extension possibility which is Chain of command. Now Pre & Post functionality can be used in Extensions in more easier way. And it also provides developers flexibility to work with Prot

Scrum Meetings and it's importance A large part of the SCRUM process revolves around the SCRUM Meetings and also User stories. User Stories are short description in non-technical language of how a system is expected to behave. There are 4 meetings or ceremonies defined in the SCRUM framework. Each meetings happens at a specific time in each sprint and each has a set purpose and defines what participants are required and what artifacts are produced. 1.      Sprint Planning This meeting happens before the sprint begins to define what will be delivered in the Sprint. Product owner, SCRUM Master and Scrum team, all are required in the sprint planning meeting. In this meeting the top priority items are added to the product backlog and the priority of these items will be decided be Product Owner. Team breaks each backlog items into smaller tasks and estimates the work for each task. Once the team is filled with capacity for the sprint they stop taking new items and commi