I want to share with you some reports that are using some of the new capabilities that are available for use with RDLC reports in Microsoft Dynamics NAV 2009.
We have prepared 4 reports which uses these capabilities:
Customer - Order Summary:
Quantity Explosion of BOM:
Customer - Top 10 List:
With Bar Chart
With Pie Chart
The reports can be downloaded from the attached zip file.
Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV
Please note that I have posted a new blog for this subject here. /Claus Lundstrøm
I want to share with you also another report using some of the new capabilities in point of creating dashboards in NAV 2009.
Based on reporting services and NAV data source it is possible to create dashboards for every department. This offers a perfect extension to the default charts directly in the role center.
The report shows you one example based on the sales department to get a quick and/or deep overview about the current situation.
If you are a developer you can also use the report for learning purposes:
You can download the report from here:
Rene - Microsoft Dynamics NAV MVP (firstname.lastname@example.org)
Permissions for Sample Roles for Microsoft Dynamics NAV 2009 contains information about which objects (table data) each role can access within the database and the roles equals Role Centers (User Profiles) in the RoleTailored client. These sample permissions can be used as a starting point when setting up permissions for the specific Role Centers. Please note that the permissions will not be sufficient in all cases and should be customized to the individual instance.
The Developer's Toolkit (NDT) has also received a quick overhaul and now supports field groups. If you don't know NDT already, you should look to the NDT if you are looking for a Source Analysis tool or a Compare and Merge tool. It is recommended that you use version NDT_v3.00.400 if you are using it in connection with Microsoft Dynamics NAV 2009.
Finally we have released the Language Modules for 12 Languages (AU, NZ, DE, DK, ES, FR, GB, IE, IN, IT, NA and NL). If you are not familiar with Language Modules, they enable you to add additional language(s) to an installation. This is particular useful in multicultural companies, e.g. a German installation with German and Italian speaking employees. Please read the instructions carefully and note that the Language Modules for Microsoft Dynamics NAV 2009 require the Page ID Hotfix to be installed first.
To help us better understand your experience with implementing Microsoft Dynamics NAV, we've created a survey that is available until March 20. The survey is open to all Microsoft Dynamics partner employees directly involved in any phase of Microsoft Dynamics NAV implementation work. It should take about 10 minutes to complete. The data from the survey will not be publicized, but it will help us improve your experience with Microsoft Dynamics NAV in the future.
To begin the survey, follow this link.
- Jacob Winther, NAV UX Designer
We've released an update of the Microsoft Dynamics NAV 2009 Developer and IT Pro Help to MSDN and the Microsoft Download Center. This is the second of our periodic updates to developer and IT Pro content since NAV 2009 released in November.
This release includes:
You can download the updates and copy it into your NAV 2009 installation, updating the Help you receive from F1. If you have feedback on any of the content, please use the feedback link at the bottom of each page in the CHM, or use the Ratings and Feedback form on each MSDN page.
- Bob, Elona, Jill, and John (the NAV dev & IT Pro writers)
The virtual table 2000000046 "Automation Server" shows you the physical location of the automation servers (.dll file). But a .net component is not an automation server, so is not listed here. One of the main benefits of .net is exactly to be able to copy and paste files, keep installations simple, and maintain multiple versions. But registering .net components do a lot to hide this simplicity. Windows Explorer also hides the actual structure of the registered .net components.
To see the real structure, use a command prompt instead. Go to the folder c:\windows\assembly. Windows Explorer Will just list your .net components. But go to the same location from a command prompt, and it is different:
The folder contains sub folders like GAC, GAC_32 and GAC_MSIL. When the .net framework looks for a .net component, it goes into one of these folders - typically GAC_MSIL, but it depends on which version of .net framework is installed.
The next thing the .net framework does when locating a .net component, is to go into the folder with the same name. This folder then contains a folder for each version of this component. If .net is looking for a specific version which does not exist, then if you create a new folder here with this version, then .net will look in this folder. Finally, here you have the actual .net component (dll file) which the .net framework will use.
Lars Lohndorf-Larsen (Lohndorf)
Microsoft Dynamics UK
Microsoft Customer Service and Support (CSS) EMEA