You can create a new empty company and use the RapidStart file and apply it to the new company. For example:
Recently I’ve been building a lot of Power BI reports from csv and Excel files, and to make sure that scheduled refresh works I have been setting up data sources in an On Premises Data Gateway (what used to be called the Enterprise Gateway). I had assumed that if I was connecting to file-based data sources in my Power BI dataset then, in the gateway, I would need to set up one data source for each file that I’m connecting to – which is a bit of a pain.
Something I didn’t understand at all when I started writing this series was how the “None” data privacy level worked. Now, however, the ever- helpful Curt Hagenlocher of the Power Query dev team has explained it to me and in this post I’ll demonstrate how it behaves and show how data privacy levels can be inherited from other data sources.
A couple of weeks ago, I was trying to write web service examples in AL code for VS Code. Unfortunately, at that time, it was not possible to call the Base64 methods on the TempBLOB table. And because those functions on the TempBLOB table are using .Net, I figured it was going to take a while before we get Base64 support in AL code. So I decided to write Base64 encoding / decoding routines myself. Just as an excercise and at that moment I didn’t know if I would even succeed.
We all know what a difficult task can be Dynamics NAV reports upgrade if you decide to change your reporting technology from Classic to RDLC. It requires quite a bit of knowledge and experience to make your reports look and work the same way as they did before. However, once you can identify all the tricky places that might cause problems and know what are the possible solutions for these problems, it is not really that painful. I hope this article will help you to make Dynamics NAV reports upgrade more joyful experience.