Microsoft Dynamics NAV Team Blog : Reporting

Dynamics NAV RTC hangs when previewing/printing reports

peterwib — Thu, 03 Dec 2009 12:56:00 GMT

Problem:
When previewing a report you only getting a small window in upper left corner with only a text string with the name for the report and the rest blank. When I trying to close this window, you get an error message: "Errors exist. Do you want to discard changes?" (Y/N). Pressing Yes, hangs and close the RTC client.

Probably cause:
You have installed the RTC client outside the setup chainer or you have uninstalled Report Viewer 2008. It may also be that Report Viewer 2008 installation is broken.

Solution:
Run DVD\Prerequisite Components\Microsoft Report Viewer 2008\ ReportViewer2008.exe and select install or repair depending on if Report Viewer 2008 was already installed.

How to run 2 RTC on the same pc and connect it to different db (how to run pages/reports from diff db)

gediminb — Tue, 17 Nov 2009 06:52:00 GMT

Multiple RTC:
We know that Dynamics NAV classic client has very nice feature: we can start it with option ID=<zup file name>. In that way we can have many NAV shortcuts which open different db/companies.
However Role Tailored Client looks like only one shortcut in menu and always starts the same client connected to "last server, last db, last company".

But we can create shortcuts for every needed connection in similar way as in CC, just we need to use option: settings:<clientusersettings.config file>.
For example i want to have shortcut which always opens W1 db on server "a1", service "NAV W1", using port 7048 (not standard port). Then:

I search for default "clientusersettings.config" in default folder (usually it is C:\Users\...AppData\Local\Microsoft\Microsoft NAV\).
Copy it to somewhere - for example to NAV RTC folder and rename to for example "w1.config".
Modify settings file:

<add key="Server" value="a1" />
<add key="ServerInstance" value="NAV W1" />
<add key="ServerPort" value="7048" />

Create shortcut: "C:\Program Files\<path to RTC>\Microsoft.Dynamics.Nav.Client.exe" -settings:"C:\Program Files\<path to RTC>\W1.config"

Now when i will click on this shortcut, it will try to connect to service tier described in config file.
And i can create as many shortcuts as i want and at the same time to have opened many RTC connected to different db.
Before use this shortcuts i must to create service tiers, but this is not current topic problem, it is described at Freddys Blog

How to run pages/reports from CC

During developing pages and SSRS reports in CC objects designer, usually we want to run it. However there are few issues:
- If we run page (nice feature in Dynamics NAV SP1), it will start last RTC session connection. I mean for example i just looked how page looks in db "w1" by run it from RTC, and now opened CC and designing page in db "UK", and, if i push run button in object designer, then NAV will open RTC and run page from company "w1" (but I'm expecting "UK"). This is because NAV CC has no information about "service tier" and just starts last RTC session.
- There are no possibilities "by default" to run RTC report from CC.

With my friends help i created little trick and can run page/report from CC from current connected db.

I created table with fields:

User ID Code 20 - user id which will run page/report (for example: gediminb)
RTC Client exe Text 250 - path and name to RTC client exe file (for example: C:\NAV RTC\Microsoft.Dynamics.NAV.Client.exe)
Server Name Text 30 - NAV server name (where is service tier installed) (For example "DBServer")
NAV Server Name Text 250 - NAV service tier name (for example: NAV W1)
Settings path+name Text 250 - path and name of client user settings file (i described earlier) (for example: C:\NAV RTC\w1.config)

I created form based on "Object" table, filtered pages and reports and under button i added code:

Session.RESET;
Session.SETRANGE("My Session",TRUE);
Session.FINDFIRST;

WITH DevUserSetup DO BEGIN
RESET;
GET(LoginMgt.ShortUserID(Session."User ID"));

TESTFIELD("Server Name");
TESTFIELD("RTC Client exe");
TESTFIELD("NAV Server Name");

IF DELCHR(DevUserSetup."Settings path+name")=''
THEN txtSettings := ''
ELSE
txtSettings:='-settings:"'+DevUserSetup."Settings path+name"+'"';

ShellString := '"' + "RTC Client exe" + '"';

IF Rec.Type=Rec.Type::Page THEN
ShellParam := '"DynamicsNAV://' + "Server Name" + '/' +
                "NAV Server Name" + '/' + COMPANYNAME + '/' +
                'RunPage?Page=' + FORMAT(Rec.ID) + '" '+txtSettings;
IF Rec.Type=Type::Report THEN
ShellParam := '"DynamicsNAV://' + "Server Name" + '/' +
                "NAV Server Name" + '/' + COMPANYNAME + '/' +
                'RunReport?Report=' + FORMAT(Rec.ID) + '" '+txtSettings;

END;

SHELL(ShellString,ShellParam);

----------------------------------------------------------------------

Here "DevUserSetup" is variable type rec and point to my previous created table.

So what does this code when i push button when cursor is on report 21? It creates string like: "c:\NAV RTC\Microsoft.Dynamics.NAV.Client.exe" "DynamicsNAV://DBserver/NAV W1/CRONUS International Ltd./RunReport?Report=21" -settings:"c:\NAV RTC\W1.config" and run it from SHELL.
This will run RTC and opens report i want to see with data i want to look.
The same is if i push button when cursor is on page.

That's all
Special thanks to Martin Jordt Hansen

Gedas Busniauskas (gediminb)
Microsoft Customer Service and Support (CSS) EMEA

Printer Selections in Role Tailored client

navblog — Mon, 19 Oct 2009 13:46:00 GMT

Today Printer Selections Form 64 is not transformed to Printer Selections Page 64 since virtual table 2000000039 is not accessible from Role Tailored client.

I thought of different options for how we could get page 64 to work and decided to try the new Client Extensibility feature in NAV 2009, although this could also be done with filing a temporary table from COM.

I would like to share this option with you.

Page “70809 Printer Selections FactBox” is using a client-addin, based on C#, to read the local installed printers and offers the way to select the name and save it to NAV 2009.

Page “64 Printer selection” is enhanced with the new fact box.

You can download the files here:

You can use the file for your own risk. There is no support for it.

(Note: Before you can use the page 70809 you have to install the client extension library “printerslections.dll” on your machine. The easiest way to do this is using the Add-Importer from Christian. )

Thanks,

Rene - Microsoft Dynamics NAV MVP (navmvp@live.at)

Send email with PDF attachment in NAV 2009

navblog — Thu, 08 Oct 2009 13:44:00 GMT

In this post I would like to explore the possibilities to create an email from the Role Tailored client and attach an invoice as a PDF file to the email, unfortunately we have do not have this functional build into our Demo application, but let me show you how this can be do with little effort.

First I suggest you download the fob file which contains the 5 different options I will go through here.

When downloaded the fob file you will see that I have added 5 new actions

1. SendAsPDF(Use of codeunit to rename) recommended solution
2. SendAsPDF(Access to Server needed)
3. SendAsPDF(With Temp file name)
4. SendAsPDF(User prompted to save)
5. SaveAsPDFrecommended solution(if you just want the PDF file)

Let me go through the different options starting from the bottom, since I recommend option 1, but I would also like to share other options for doing this, since these might be valuable for you.

Option 5: SaveAsPDF
In this option you will get prompted if you want to open or save the PDF. The PDF file created will be based on the select Invoice in the Posted Sales Invoices List Place

In this option all I do is to have the server create the PDF file for me and use the new download function in NAV 2009 to retrieve the PDF file created on the server.

Option 4: SendAsPDF(User prompted to save)
In this option, you will first be prompted to save the file.
Here it is important to select to “”SAVE” the PDF file on the disk, to have the correct name of the PDF file. If you select to “OPEN” the PDF filename will be given a temp name.

After you have saved the PDF we now create the email message you will get 3 messages similar to this when this happens:

You get these message because we connect to an external component(Outlook) to the Role Tailored client. It is of course up to you if you want to set this to “Always allow”, but this would remove these messages, the next time you open the Role Tailored client.

When you have allowed these to run, email will be created with the PDF file attached.

In this option all I do is to download the PDF to the client and then use the Mail codeunit to create the email

Option 3: SendAsPDF(With Temp file name)
In this option, you will not be prompted to save the PDF file.
And the email will be created immediately. This would probably be the preferred compared to downloading this to the user disk, but we will use the PDF file created on the server, and since this file get a TEMP name, like this: “__TEMP__570eb0279b9d4b1fa837caf3a14acbf7” this option is not really good.

Let us look at the option 1 and 2 where this issue is solved.

Option 2: SendAsPDF(Access to Server needed)
In this option you will not be prompted to save the file either, but here the end user will need to have access the server folder where the PDF is stored on the server. In some situation you might want this, but for security reasons you might also not want to give this access to the all user.

Option 1: SendAsPDF(Use of codeunit to rename) recommended solution
Again in this option you will not be prompted to save the PDF file, but the PDF file will be automatically added to the email. In this option we have build a codeunit to rename the TEMP file created on the server, and end user will not need to have access to any folders on the server.

So all in all I recommend option 1 for attaching PDF file to an email. And once again I have made all the code available here, so feel to be explore how I build this. If you feel there is an option that I missed, feel free to leave a commit or use the contact form Email.

Thanks,
Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV

What's New in Reporting in Microsoft Dynamics NAV 2009 SP1

navblog — Tue, 01 Sep 2009 14:01:00 GMT

We have now released Service Pack 1 for Microsoft Dynamics NAV. So you will now all be able to use the new Reporting features in this Service Pack. Previously I have described all new reporting features in this Service Pack. Please find all these features described here: What is new in Dynamics NAV 2009 SP1 for Reporting.

Thanks,
Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV

Building a Matrix Report in Microsoft Dynamics NAV 2009 SP1

navblog — Fri, 28 Aug 2009 13:40:00 GMT

The final Service Pack 1 for Dynamics NAV 2009 is now just around the corner, so with that I would like to share with you one of the new possibilities in the reporting area, Matrix reports.
First I will go through how to build a Matrix Report in NAV 2009 SP1, then I will demo some Matrix reports done by two of our MVPs of Dynamics NAV and one of our partners. In the end of this blog I will share all the Matrix reports. So if you are not interested in how to build a Matrix Report in NAV 2009 SP1 or already know how to do this in NAV 2009 SP1, this is the time for you to scroll to the bottom of this blog, if you just want to download the objects. :-)

If you are still here and have not scrolled to the bottom, let us get started building a Matrix Report.

Building Matrix Report in NAV 2009 SP1

In this walkthrough we will be creating a Matrix Report sorted with Items by Location.
When you have finished this Walkthrough you will understand how to build a Matrix Report in NAV 2009 SP1.

1. Select “New” in Object Designer with Report object selected

2. Add “Location” as Table

3. Select “Create a blank report“ and click “OK”

4. Insert “Location” as the first DataItem

5. Insert “Item” as the second DataItem, make sure to indent under the “Location” DataItem.

6. Save Report and give an “ID” and a “Name”

7. Now we have created the DataItems for this report, so now we need to create the Data Source for us to be able to create the Layout of the Report in Visual Studio. For this we need to go to the Section Designer. Open Section Designer

8. For now the Section Designer is Empty, so we need to add some Fields. We would need these fields:

· Items by Location – Title

· Code – Location

· Name – Location

· No. – Item

· Description – Item

· Inventory – Item

9. Make more space to have more fields in each of the Sections.

10. Add a Label with Caption=Items by Location

11. With “Location” Section selected, open Field Menu:

12. Open Field menu and select “Code” and “Name”

13. Add these 2 fields to the “Location, Body”

14. Navigate to the “Item , Body” and select “Field Menu” and select "No.", "Description" and "Inventory"

15. Add these 3 fields to the “Item, Body”

16. We have now created the Data Source for the report. Now we need to create the layout for this report.

Select “View / Layout”. Visual Studio will open.

17. In Visual Studio you will now see these elements in Data Source we can work with:

18. Lets us now design the layout.

19. In the toolbox select the Matrix control and drag this to the Report Body

20. Drag “Items_by_LocationCaption” to the top left cell in the Matrix control

21. In the “Rows” just below I want to add 2 rows directly under “Items by Location”, so we need to add a new group. Right click the “Rows” cell and select “Insert Group”

22. “Grouping and Sorting properties” dialog box will come up.

Select to group on “=Fields!Item_Description.Value” and click “OK”

23. In the new cell to the left of “=Fields!Item_Description.Value”, right click and select “Edit Group”

24. Select to group on “=Fields!Item__No__.Value” and select “OK”

Your report should now look like this:

25. It is now time to add the column above the data, and in this report we want to see in how many items are stored in each warehouse. Add “=Fields!Location_Name.Value”

26. And at last let us add the data cell in the bottom right corner of the matrix control. Add “=Sum(Fields!Item_Inventory.Value)” to the Data cell.

27. Now before viewing the report let us already do some resizing of the layout, for this to readable on one page. I choose to narrow the columns, so the report now looks like this:

28. Also to make this report more readable friendly, let us add a Solid Border style. Select all cells in the Matrix control, and select “Solid” for the “BorderStyle” property

29. Now let us view the report, save, import, compile and run the report. We now get this output.

Hmm, something is wrong. I.e. we have 32 bicycles on stock in each of the warehouses. Let us fix this issue.

30. Go to the DataItem “Item” and set the property “DataItemLink” to “Location Filter=FIELD(Code)”

31. Now let’s run the report again, but now we set the following filter on the Request Page: Inventory is >0

We do this to avoid all entries with 0.

32. Now select “Preview” to see the report.

33. We now have a working Matrix Report which is sorting Items by Location.

34. Now let us imagine you would like to know the Inventory Availability on the 52 “PARIS Guest Chair, black” in the “Blue Warehouse” or on the 55 “AMSTERDAM Lamp” in the “Red Warehouse”. So let use the Drill Through to Report feature in Dynamics NAV SP1 to drill through to our existing “Inventory Availability” report 705. Open Visual Studio again by selecting “View / Layout”

35. Right click the Data field in the Matrix control and select “Properties”

36. Navigate to the “Navigation” tab

37. Select “Jump to URL” and add the following expression:

="DynamicsNAV:////runreport?Report=705&Filter=Item.%22Location Filter%22:"+Fields!Location_Code.Value+"&Filter=Item.%22No.%22:"+Fields!Item__No__.Value

What we are doing here is that we open Report 705(Inventory Availability) filtered on Location and Item No., when we click data field in the Matrix report.

38. Before we save the report, let us make it visible in the report that we have a link to another report.

With the Data field selected set these properties:

Color=Blue

TextDecoration=Underline

39. Save, Import and Compile the report. Note you might this error:

Set the EnableHyperlinks=TRUE, and compile again

40. Run the report. It will now look like this:

41. Now when we click on the 52 “PARIS Guest Chair, black” in the “Blue Warehouse”, Inventory Availability report will now open based on the our Blue Warehouse and our Paris Guest chair.

And when we click on the 55 “AMSTERDAM Lamp” in the “Red Warehouse”, Inventory Availability report will now open based on the our Red Warehouse and our Amsterdam Lamp.

Now let us look at some other Matrix Reports

1. Items by Location done by Andrey Panko, MVP for Dynamics NAV. This report is very similar to the above walkthrough, it has extra logic on the data part and more advanced coloring and a Totaling to the very right. It does not contain any Drill Through to report 705, but this could easily be added following the above steps(35-37) on how to that.

2. Items by Location done by Rene Gayer, MVP for Dynamics NAV. This report is also similar to the above reports but here Rene is using the new Drill Through to report, so if click on the Item, left most column, you open a Item Dashboard, with Key Performance Indicators, Stock level illustrated and Sales History.

3. GL Entries per Account per Month, done by GAC Business Solutions. This report gives a overview of the entries in GL Account pr month. Notice when clicking the GL Account you will Drill Through to GL Account card, and when clicking the amount in the Matrix you will Drill Through to the Detail Trial Balance Report filtered on month and GL Account

Please find all the mentioned reports here:

Thanks, to Andrey Panko, Rene Gayer and GAC Business Solutions for sharing their Matrix Reports.

Thanks,
Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV

What is new in Dynamics NAV 2009 SP1 for Reporting

navblog — Tue, 07 Jul 2009 13:38:00 GMT

With our Microsoft Dynamics NAV 2009 SP1 Community Technical Preview released it is now time to drill into the new features we have been for working on for reporting in NAV 2009 SP1.

1. Drill Through to a report from a report

In NAV 2009 it was possible to Drill Through from a Report to a Page, see how this is done here.
With the possibility to Drill Through from a report to Page, we had a strong request from partners and customers to add the possibility to Drill Trough from a Report. So in NAV 2009 SP1 it is now possible to Drill Through from a Report to a Report. So how is this done? Well this is not done the way we Drill Through to Pages, but with the use of filters.
A Drill Through to a report could look something like this:

="DynamicsNAV:////runreport?Report=104&Filter=Customer.%22No.%22:"+Fields!Customer__No__.Value

The first part “DynamicsNAV:////runreport?Report=104” is our well know way to link to reports and pages. If you are new to this linking in NAV 2009 read more here.

The last part “&Filter=Customer.%22No.%22:"+Fields!Customer__No__.Value” is what is new for NAV 2009 SP1. The first part will open Report 104, and with the last part, report 104 will be filtered on the “Customer__No__.Value”. If we add this code to a Customer Top 10 List report, we can Drill Through to report 104 both from the List and the Pie Chart. I have made a small video how that is done:

2. Paging

In NAV 2009 the dataset creation was done on server, before it was sent to the requesting client. With this approach, the memory consumption on the server could potentially be very large with multiple user requesting reports at the same time. For this reason we have implemented paging in SP1. With paging the memory footprint on the server is minimal. When the dataset for a report is generated, we are now sending small chunks of the dataset to the client, and thereby building up the dataset on the client. With this approach the client is now taking the memory hit and not the server. I have made small video that illustrates how the dataset was build up in NAV 2009 and in NAV 2009 SP1:

3. About this Report

In NAV 2009 we had the possibility to zoom into the dataset of a report. We also had a very short short as well SHIFT+CTRL+ALT+F12 :-) but in SP1 we have reintroduced the zoom feature for Pages as well. We decided to call this “About this Page”. “About this Page” and can be found in the help menu on all pages. For reporting we aligned this, so in Report Preview we now have a menu called “About this Report”. Also the shortcut is aligned, so this is now CTRL+ALT+F1.

4. Progress Indicator

With paging introduced in SP1, it gave us the possibility to add a Progress Indicator, while the dataset is being created and sent in chunks to the client.

You will now be able to see how long the dataset generation has taken
You will be able to see how many rows has been received from the server
And at last you will be able to cancel a report, something which was not possible in NAV 2009

Note: When dataset has been sent to the client Progress Indicator will disappear and Report Viewer will starter rendering the report. Based on the logic in your layout this can take more time than the actual dataset generation. You will be able to stop this generation by clicking the stop button in the Report Viewer while the report is being generated.

5. Matrix reports

We now also supports Matrix reports, so we can do things like this:

6. Visual Web Developer 2008

We now have full support for Visual Web Developer 2008, so it is no longer needed for you to do the “hack” I described here. Note: As of April 1st. Visual Web Developer 2005 has reached EOL, which means it can no longer be downloaded from Microsoft.com

7. External Images

In NAV 2009 it was possible to add both embedded images and images from the NAV database. With NAV 2009 SP1, it will now also be possible to add external images to your report.

I hope you appreciate the new reporting features which will be available in NAV 2009 SP1. And as always I’m happy to get feedback for reporting features you would like for us to implement in future releases. So use the Contact Form to write directly to the core reporting team in Navision(Dynamics NAV) :-).

Thanks,
Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV

Report Design in Microsoft Dynamics NAV 2009

navblog — Fri, 03 Jul 2009 13:37:00 GMT

We have now released training material for designing reports in NAV 2009.

This training will teach the learners about the concepts of Report Design in NAV 2009 using VS Report Designer along with the limitations and workarounds in Report Design. It covers the new options with practical examples on creating reports in report design, creating and defining data set within NAV 2009 to be used in Visual Studio. In addition, it covers how to implement dynamics features like interactive sorting, conditional formatting, visualizing data using graphs, document maps, creating expressions. Furthermore the training contains information on best practices and recommendations for creating interactive dashboard reports containing KPI’s.

At Training Material Completion
After reviewing this training, individuals will be able to:

Understand the new architecture and reporting features in Microsoft Dynamics NAV 2009.
Create table and matrix reports for the Microsoft Dynamics NAV RoleTailored client in Microsoft Visual Studio.
Add interactive features, such as Visibility Options, Interactive Sort, Document Maps, and Pictures to the report.
Use expressions and custom code in RoleTailored client reports.
Integrate reports in the RoleTailored client user experience.
Run RoleTailored client reports in various ways.

You will find the training material at CustomerSource here:
https://mbs.microsoft.com/customersource/training/trainingmaterials/student/course80146.htm

Thanks,
Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV

Strange errors come during change SourceExpr value in NAV report designer...

navblog — Thu, 02 Jul 2009 13:27:00 GMT

Our colleague raised problem: why he receives strange error during report compile, after he changed SourceExpr value for some control in report designer in NAV 2009.

Error message was:

Error while validating RDL content:
The Value expression for textbox “CompanyInfo” refers to the field ‘PricesInclVAT_YesNo’. Report Item expressions can only refers to fields within the current data set scope or, if inside an aggregate, the specified data set scope.

Error itself looks very strange because:
1. It comes from validating RDL content, but we changed nothing in it.
2. Changed was SourceExpr in NAV classic client report designer>sections>control property, and it has no relations to field mentioned in error. Actually what was changed: report 204 – Sales-Quote; control 116; SourceExpr had value "Sales Header"."Prices Including VAT" and now it has value FORMAT("Sales Header"."Prices Including VAT").

If we change back value – error disappears.

After deeper analyze we found that RDL dataset has field ‘PricesInclVAT-YesNo’, but after report designer change SourceExpr value by adding FORMAT – this field disappears from dataset. So problem really is in the SourceExpr value, however value itself is correct. And after few more research we found there is control 167 – name PriceIncVAT_YesNo which has exactly the same SourceExpr value - FORMAT("Sales Header"."Prices Including VAT").

Conclusion: only one source expression is pushed to RDL, if there are few controls with the same SourceExpr, only first will be in RDL, other will not appears there.

I asked NAV architects about this issue and they answered:

The field names that we show in the RDL dataset do NOT come from the SourceExpr property "directly". Each control on a report has a DatasetFieldName property, which is what we use to build the field names in the RDL dataset.

The DatasetFieldName property is then derived from the SourceExpr property the first time you open Visual Studio for a report using the View --> Layout menu item. After this, if you change the SourceExpr, the DatasetFieldName does not get changed. (The whole purpose of this property is to fix the dataset field name so even if you change your SourceExpr, you won’t need to redesign your RDL). This should cover most of the user scenarios.

In a few scenarios, you are not covered though: one is, if you move sections or controls in the layout, and if two controls have the same SourceExpr value, the control we choose to export to the report dataset may change with another one with the same SourceExpr. Since they have different DatasetFieldName properties, your RDL will break. We don’t cover this scenario and we don’t believe that we could fix this easily.

In another scenario: if you change the SourceExpr, and the data type of the new field is different than the old one, RDL compilation may fail due to the expressions used on that field - as these are data type dependent.

So, during report design be very careful with modifying 2 properties: SourceExpr and DataSetFieldName. Changes could impact RDL very much and result could be not you are expecting. Of course this is important if you already have RDL report prepared, if you will create new layout by using "Laoyout suggestion", problems will not come, because new RDl laoyout will be created regarding earlier described rules.

These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.

Special thanks to John Vestergaard from Logica Danmark A/S for pointing us to this feature.

Gedas Busniauskas (gediminb)

Microsoft Lithuania
Microsoft Customer Service and Support (CSS) EMEA

Filtering out blank fields

navblog — Tue, 12 May 2009 13:35:00 GMT

Some of you have noticed that the Chart displayed in “Customer Order - Summary” contained a series label called Series 1.

Well the reason for that being shown is because we have missed to filter out all customer with have no data in the field: Chart_SalesOrderAmountLCY.Value

So how is that actually done? Well let me show you:

1. Design Report 70000

2. Select “View / Layout”

3. Right click the chart in the bottom of the report

4. Select “Filters” tab

5. Type the follow:

Expression:
=System.String.IsNullOrEmpty(Fields!Chart_SalesOrderAmountLCY.Value)

Operator:
=

Value:
=False

6. With this filter we now filter out where "Chart_SalesOrderAmountLCY.Value” is equal blank.

7. Now save and compile the report and display in RoleTailored client. Now only customers with outstanding orders are shown in the chart.

I have updated the demo reports package to reflect this change.

The reports can be downloaded from here.

Thanks,

Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV

Creating Dashboards in NAV 2009

navblog — Mon, 30 Mar 2009 13:34:00 GMT

Hi!

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:

Use charts
Use coding in expressions
Use DrillDown
Use own color palette in charts

You can download the report from here:

Thanks,

Rene - Microsoft Dynamics NAV MVP (navmvp@live.at)

Demo Reports

navblog — Mon, 30 Mar 2009 13:31:00 GMT

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:

Use of Conditional Formatting (Table colors)
Use of Conditional Formatting (Colors in cells)
Use of Charts
Use of Hyperlink External(Click the Dynamics Logo in the bottom)
Use of Embedding picture into report

Sales Pipeline:

Use of Conditional Formatting (Icons, expand to see the icons)
Use of Conditional Formatting (Table colors)
Use of Visibility toggle
Use of Hyperlink (Click the Dynamics Logo in the bottom)
Use of Embedding picture into report

Quantity Explosion of BOM:

Use of Visibility toggle. Notice that this is Visibility toggle for “Expand All” replaces the previous table shown. Look for Table 1 and Table 2 in Visual Studio to see how that is done.
Use of Conditional Formatting (Table colors)
Use of Drill Through to Page(Click “Where used?”)
Use of Hyperlink (Click the Dynamics Logo in the bottom)
Use of Embedding picture into report

Customer - Top 10 List:

With Bar Chart

With Pie Chart

Use of Visibility toggle. Now you can switch between Bar chart and Pie Chart in the Report Viewer and are not required to run the Request Page to make this change.
Use of Percent
Use of Point Labels
Use of Hyperlink (Client the Dynamics Logo in the bottom)
Use of Embedding picture into report

The reports can be downloaded from here.

Thanks,

Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV

Report Headers

navblog — Tue, 24 Feb 2009 13:16:00 GMT

In classic reports, adding a header to your report is as easy as just copying the Header section from an existing one.

With reports for RTC you need to do a bit of manual work to get your report header. A standard header contains the following information:

Report Name

Company Name

Time and date (=Globals!ExecutionTime)

Page Caption and Number (=Globals!PageNumber)

User ID (=User!UserID)

Time and Date, Page Number and User ID are automatically defined as global variables in Visual Studio report designer. All you need to do, is: Add a TextBox, right click on it and select "Expression...", then select from the Globals-Menu:

The other fields (Report Name, Company Name and Page Caption) are labels, and have to be added following the steps described here:

Labels in NAV2009 Report Design

So these are the two ways (Globals and Labels) that you have to add information to your report headers as illustrated here:

Lars Lohndorf-Larsen (Lohndorf )

Microsoft Dynamics UK

Microsoft Customer Service and Support (CSS) EMEA

Labels in NAV2009 Report Design

navblog — Tue, 24 Feb 2009 13:14:00 GMT

When adding fields to a report, the caption is typically added automatically or with a bit of drag and drop from the DataSet in VS Report Layout. But if you want to add additional labels, for example Report Name in the header, then there are a few more steps you must follow.

Of course, you can just add a new TextBox in VS Layout, and type in the value you want to show. This is simple but will not give you Multi Language. Using a label from the classic report design gives you Multi language, but is a bit more complicated. This is what you need to do:

As usual, before you can use it in the layout you must add the label to the report sections, and then specify the caption you want to display. In this case, make sure to also specify a name in the DataSetFieldName-property of the label. For this example, let’s call it Report_Label.
To get the label value (Caption) into the layout, you must first add it to the Table on the Body-part of the layout. Note: It must be part of the table, and not in a TextBox outside of the table. The name of the cell will default to the DataSetFieldName you specified (Report_Label). And the value must be =Fields!Report_Label.Value. You get this value automatically if you drag it from the Data Set into a detail-section of the table. The caption is only here to be available from the header part of the report, so you can set the Visible-property to No.

Finally you can get the label from the table and add it to a header-section in the report layout: Add a new TextBox, then name it something unique, for example Report_Label1, and set Expression = =ReportItems!Report_Label.Value. Note that "Report_Label" refers to the cell you added above, not directly to the label on the sections.

This picture shows the steps needed to get the label to show in the header:

Lars Lohndorf-Larsen (Lohndorf)

Microsoft Dynamics UK

Microsoft Customer Service and Support (CSS) EMEA

How to enable Document Map in a Report

navblog — Thu, 05 Feb 2009 14:22:00 GMT

Here are the steps to leverage the use of “Document Map” in a Report.

1. Design Report 113 Customer/Item Sales

2. Select View / Layout

3. Right click on Table top left corner

4. Select Properties

5. Navigate to “Groups” tab

6. Select Table1_Group

7. Select “Edit…”

8. Select “=Fields!Customer_Name.Value” in “Document map label”

9. Select “OK”

10. Navigate to “Navigation” Tab

11. Enter “Customer” or what you want the title to be in the Document List

12. Select “OK”

13. Save and import RDLC changes, and then compile report in Classic client.

14. Run Report 113, it now looks like this:

Notice the expand in the top left corner. Unfortunately this does not display anything in NAV 2009 RTM, this will be fixed in SP1.

16. Click the expand button to see the Document Map

17. Now click the customer “Klubben” and notice that the report in to the right navigates to the area where info about the customer “Klubben” is displayed.

Thanks,

Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV