Have you ever felt that Dynamics NAV is sooo slow especially after having restarted the Server Tier?
Every time you are going to Demo Dynamics NAV to a customer or a group of potential new users, you always have to make excuses that Dynamics NAV is always slow just after having been restarted.
Do you want to connect to hundreds of data sources, simplify data prep, and drive ad hoc analysis, produce beautiful reports, then publish them for your organization to consume on the web and across mobile devices. Well, then you can use the Power BI suite of business analytics tools that deliver insights throughout your organization.
A Single Sign-on (SSO) user experience is achieved between Microsoft Dynamics NAV and the Office 365 Web Applications where the User is authenticated using Office 356 credentials to access NAV Windows client and Webclient.
I’ve just wrote a post about Image Analyzer in NAV as Cognitive Service and recognizing attributes for Item, but now I’ll write about second part of using cognitive services in NAV and D365 for Financials. Now I’ll show you how it works with people photos. This feature works on the Contact Card.
It really sounds amazing. But if you were been at Microsoft Ignite and attended NAV/D365FOBE sessions, you already seen this service as something what we will have in the future. When I say future, I think on the future NAV version, but if we speak about D365 for Financials, you can test in now.
You may notice that the Location Filter might not be effective when you run the report 5807 “Item Age Composition – Qty.” on NAV 2013 R2 to NAV 2016. On NAV 2009 Classic, NAV 2009 R2 and NAV 2017, you may not have that issue because they write the code in different ways. On NAV 2017, they use a function called FilterLinesWithItemToPlan rather than writing the code directly under Item-OnAfterGetRecord trigger. This blog will walk through the steps to correct this issue.
Just to set the right expectations – this blog is intended for Extensions Version 1. In other words, extensions that are:
– developed completely in the well known classic C/SIDE development environment (C/AL).
– created, installed and published with PowerShell
– NOT created in VSCode