I had my Assisted Setup wizard up and running on NAV 2017. Everything looked fine but when the extension was being validated nothing worked. So, there is a difference between NAV 2017 and Dynamics 365 for Financials.
This will be the last part of this little miniseries, unless you bring up so many questions that I might combine them into another blog – challenge me. I am going to explain this time the packaging process and what comes after. While it is fairly simple, it is still important that you pay attention to it.
This time, I am going through the development of an app, explain the important steps to remember, and different suggestions to create a well-rounded App for Dynamics 365 for Financials. I am not going into the fundamentals of creating an extension, since this is well documented already, but I am going to look into the actual issues that can arise when you are trying to develop an app and what should be added to an app to make it well rounded.
After spending quite some time to go through the App publishing process for extensions for Dynamics 365 for Financials, I thought it would be a good idea to share my findings, thoughts, and experiences. It will be a multi-part series in which I will walk you through the process of getting an App published, look at the do’s and don’ts in development, and the packaging process.
When we sign up for Dynamics 365 for Financials, we get access to a demonstration company (called Cronus). The demonstration company contains sample data like sample orders, invoices, ledger entries etc., which lets us explore the application, view charts and reports with sample data.