Recently I’ve been doing some more investigations into how data privacy settings work in Power BI. This is a subject I’ve blogged about in great detail already in a series of posts last year, but this functionality is so complex that there is always more to learn. I don’t have any profound new insights to offer; instead this blog post is a write up of a series of experiments whose results shed light onto how the process of setting data privacy levels works end-to-end.
Microsoft Dynamics NAV 2017 introduces another way to get your work done faster with the ability to save settings for reports. This means that if you run a report with different filter settings in it, you can save those settings and retrieve them when you print the report. No more having to fill in the settings you want on the report every time you run the report.
This short, instructional video will show how to save time and improve efficiency with a new feature of Dynamics NAV 2017, Report Settings.This short, instructional video will show how to save time and improve efficiency with a new feature of Dynamics NAV 2017, Report Settings.
Back in April 2015 I wrote an article about reading server settings with C/AL code. Unfortunately, that code didn’t work in NAV 2015 and above. However, the question pops up now and then, and I decided to give it another try. Being curious myself, of course…
And I found a solution that works on NAV 2016. Didn’t test it with NAV 2015, but I’m sure one of you will.
In this example I will show how to read the server settings directly from NAV code. Without the need to know the location of the config file or to create an external .Net dll. Also PowerShell isn’t needed, and you don’t need any information about the running environment. Only the tenant ID is important in case you are running in a multitenant environment, but the tenant ID is already available in C/AL code with the TENANTID key word.
At Ifacto, we are (still) working on our product for NAV2013 using PRS. One of the things we also try to accomplish, is ease of setup for the functional consultant during an implementation process. We try to manage this by supplying an “Initialize Setup” button on every place that has some distinct setup.