Skip to main content

Custom sheet name in RDLC Reports


Hi Readers,

In this article we are going to discuss how to change the excel sheet name while using base Navision SAVEASEXCEL functionality.

Applicable for RDLC reports of Navision and SSRS reports.

Let’s say we have the following report that shows total sales by product category by territory:
 
When we export this report to Excel, we’d like each territory to appear in its own worksheet and each worksheet named after its territory:


How do we make this work? Easy!
1) Put every group on its own page.
2) name each page using the same field the group uses.

Step 1: Put each group on its own page

To put each group on its own page, open the group’s property window.



Then, in the Page Breaks category, put a check mark in the Between each instance of a group check box.



Click OK to complete this step.

Step 2: Name the pages of the group

With the group selected in the Row Groups panel, press F4 to open the Properties window.



Next, expand the Group property and look for the Page Name sub-property. From its dropdown, select <Expression…>.



In the Expression dialog, select the Fields category and then double-click on the same field the group uses; in this case that would be the Territory field.



A reference to the field appears in the window at the top of the Expression dialog.



Click OK and that’s it! Now, when you export the report to Excel, the worksheet names will match the group names!

Enjoy!

Comments

Popular posts from this blog

Improved performance features of Business Central 17

  In the training I’ve done to some partners last week, when talking about performances I shared an example of an extension with 3 features that I think are not so well known but that have a significant impact on how your code performs, expecially on a SaaS environment. That extension used the following features: Partial record loading Temporary Tables QueryCategory The  Partial record  capability  is a new feature available starting from Dynamics 365 Business Central 2020 Wave 2 (v17) and I think it’s one of my top personal desiderata from years. This feature permits you to load only the needed fields of a recordset (when accessing a data source) instead of loading the entire set of fields. This is particularly useful on reports and OData pages because you can avoid to do a SELECT * (plus JOINS with all the extension’s tables) and instead doing a SELECT of only the fields you need. Now you can do something like: procedure TestPartialRecord(): Decimal ...

UPGRADE CUSTOMIZATIONS TO V2 EXTENSION (Application and Data)

From Navision 2018 Onwards, Navision only support v2 Extension. Dynamic Navision Extension will make upgrade easier. If customizations are converted into V2 extension that means v2 Extension consist upgraded Data as well as customizations, also it will be easy to upgrade into new version of Navision and apply CU updates. Below are the detailed steps to upgrade customizations into Navision 2018 v2 Extensions .  1) you have Customized database in Microsoft Dynamics Navision 2018. 2) Create the new table for each table that is customized or also for customized field in standard table but while creating table for standard table, add the primary key and customized field with same ID and Name in new table. For E.g.: I have created 1 table “Person” and 2 Customized Field (Test, Doc No) in “Sales Header”. Now create 2 New tables in 2018.  · Upg Sales Header -> Two base field (PK) and customized field -> Same ID and add primary key. Refer be...