How many times in real world projects a customer asked you to create custom exports in Excel in order to fill a pre-defined and pre-formatted Excel report (with formulas, charts, macros and more) or to create an Excel report exactly like in a given model? Personally, I’ve lost the count…
Now with the new Excel Layout feature, this is possible directly at customer’s fingertips.
This post continues exploring the topic of Dimensions in Dynamics NAV (further, “NAV”) and Dynamics 365 Business Central (further, “D365BC”). Other posts have already discussed what Dimensions and Dimensions Values are; how to create; and assign them to Master Data and GL Accounts as well as how to block Dimension Combinations. This post focuses on how to use Dimensions in reporting in particular.
For the reporting year 2016, minor adjustments have been made to the Vendor 1099 Information reports in Dynamics NAV. The only change identified is the addition of a field for reporting of Bond Premium in Treasury Obligations on the Form 1099-INT report. No changes have been identified on Form 1099-MISC and Form 1099-DIV.
Somewhere in mid 2017 Microsoft will release a new version of SQL Server in which we will have an integration with Power BI. This means we will (I hope) be able to use SSRS as an on premise solution to host Power BI reports, as you can read here on the SQL Server Reporting Services Team Blog.
Recently I noticed a new Reporting tab in the Service Tier options, in Dynamics NAV: It has the following options: Enable Save as Excel on Request Pages of RDLC-layout Reports Specifies whether users can open or save a report that is based on an RDLC layout as Microsoft Excel document from the report request page.
Learn how to use the reporting data setup tool in Microsoft Dynamics NAV 2017. The demonstration covers the following steps:
creating a data set
editing a data set
copying a data set
I have seen several reports about the Microsoft Dynamics NAV RDLC reports dropping symbols out of decimals when printing out a report. One of the most common occurrences, that I have seen, is when the de-CH locale is being used by the end user. After some investigation, it appears that this problem is due to some changes between Windows 7 and Windows 8 (and Windows 2012).