Microsoft Dynamics AX 2012 R3 Reporting Cookbook Update: Over 90 recipes to help you resolve your new SSRS Reporting woes in Dynamics AX 2012 R3

What do you get with a Packt Subscription?

Free for first 7 days. $19.99 p/m after that. Cancel any time!

Unlimited ad-free access to the largest independent learning library in tech. Access this title and thousands more!

50+ new titles added per month, including many first-to-market concepts and exclusive early access to books as they are being written.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

Thousands of reference materials covering every tech concept you need to stay up to date.

Subscribe now

View plans & pricing

Microsoft Dynamics AX 2012 R3 Reporting Cookbook Update

Chapter 1. Understanding and Creating Simple SSRS Reports

This chapter will cover the following topics:

Using a query as a data source in a report
Creating auto designs from datasets
Grouping in reports
Adding ranges to the report
Deploying a report
Creating a menu item for a report
Creating a report using a query in Warehouse Management

Introduction

Reports are a basic necessity for any business process, as they aid in making critical decisions by analyzing all the data together in a customized manner. Reports can be fetched in many types, such as ad-hoc, analytical, transactional, general statements, and many more by using images, pie charts, and many other graphical representations. These reports help the user to undertake required actions. Microsoft SQL Reporting Services (SSRS) is the basic primary reporting tool of Dynamics AX 2012 R2 and R3.

This chapter will help you to understand the development of SSRS reports in AX 2012 R3 by developing and designing reports using simple steps. These steps have further been detailed into simpler and smaller recipes. In this chapter, you will design a report using queries with simple formatting, and then deploy the report to the reporting server to make it available for the user. This is made easily accessible inside the rich client.

Reporting overview

Microsoft SQL Server Reporting Services (SSRS) is the most important feature of Dynamics AX 2012 R2 and R3 reporting. It is the best way to generate analytical, high user scale, transactional, and cost-effective reports. SSRS reports offer ease of customization of reports so that you can get what you want to see. SSRS provides a complete reporting platform that enables the development, design, deployment, and delivery of interactive reports. SSRS reports use Visual Studio (VS) to design and customize reports. They have extensive reporting capabilities and can easily be exported to Excel, Word, and PDF formats.

Dynamics AX 2012 has extensive reporting capabilities like Excel, Word, Power Pivot, Management Reporter, and most importantly, SSRS reports. While there are many methodologies to generate reports, SSRS remains the prominent way to generate analytical and transactional reports. SSRS reports were first seen integrated in AX 2009, and today, they have replaced the legacy reporting system in AX 2012.

SSRS reports can be developed using classes and queries. In this chapter, we will discuss query-based reports. Reports using classes will be discussed in later chapters.

In query-based reports, a query is used as the data source to fetch the data from Dynamics AX 2012 R3. We add the grouping and ranges in the query to filter the data. We use the auto design reporting feature to create a report, which is then deployed to the reporting server. After deploying the report, a menu item is attached to the report in Dynamics AX R3 so that the user can display the report from AX R3.

Through the recipes in this chapter, we will build a vendor master report. This report will list all the vendors under each vendor group. It will use the query data source to fetch data from Dynamics AX and subsequently create an auto design-based report. So that this report can be accessed from a rich client, it will then be deployed to the reporting servicer and attached to a menu item in AX.

Here are some important links to get started with this chapter:

Install Reporting Services extensions from https://technet.microsoft.com/en-us/library/dd362088.aspx.
Install Visual Studio Tools from https://technet.microsoft.com/en-us/library/dd309576.aspx.
Connect Microsoft Dynamics AX to the new Reporting Services instance by visiting https://technet.microsoft.com/en-us/library/hh389773.aspx.
Note
Before you install the Reporting Services extensions see https://technet.microsoft.com/en-us/library/ee355041.aspx.

Using a query as a data source in a report

Queries offer the simplest and easiest way to retrieve data for SSRS reports in Dynamics AX R3. They are very advantageous as they are reusable, and the same query can be used as the data source of another SSRS report in Dynamics AX R3. They are also very easy to design.

We can create queries in two ways: either by using the query class, or under the Queries node in Application Object Tree (AOT). In this recipe, we will create a query under the Queries node in AOT and use it as a data source in SSRS reports. Later on, we will guide you on how to add the query as a data source through Visual Studio.

Getting ready

To work through this recipe, you will require AX 2012 R2 or AX 2012 R3 rich clients with developer permission.

How to do it...

Create a new query named PKTVendorDetails under the Queries node in AOT, and add some fields in the query. Create a new SSRS report in Visual Studio 2010 and add the PKTVendorDetails query into that report as a data source.

Open the AX Development Workspace (Ctrl + D).
Go to AOT | Queries and add a new query.
Rename the query to PKTVendorDetails.
Go to query's data source node and add the new data source.
Rename the data source to VendTable and set property table to VendTable.
There are two steps to select fields from VendTable. You can use any of these:
- Go to the Fields node under the VendTable data source and set Dynamic Property to Yes. This will automatically add all the fields in the VendTable to the query.
- Drag and drop the required field directly from the table. Drag VendGroup, AccountNum, InvoiceAccount, and Blocked from VendTable as shown in the following screenshot. This is the best way to optimize the query and, consequently, reduce the fetch time, so we will go for this option in our recipes.
Save the query.
Now open Visual Studio.
Navigate to File | New | Project.
In the new project dialog, select Microsoft Dynamics AX, and then Report Model.
Set the name as PKTVendorDetailsReport.
Now, right-click on project in Solution Explorer and Add a new Report to the PKTVendDetailReport project as shown in the following screenshot:
Rename the report as PKTVendorDetailsReport.
Now open the report by double-clicking on it in Solution Explorer.
Right-click on the Dataset node and select the New Dataset option.
Rename the dataset as VendorMaster.
Now, right-click on the VendorMaster dataset and select Properties.
Click on the ellipsis (…) button in Query.
Select the PKTVendorDetail query from the list and click on the Next button.
Select All Fields since we dropped all the unwanted fields during the creation of the query. From the All Display Methods node, select Name. Click on the OK button.

This will generate the fields list for the dataset. This completes the addition of a dataset to a report.

How it works…

In this receipe we have used queries as a datasource in SSRS report in Dynamics AX R3 as queries are reusable and can help to add the ranges in a report.

Connecting VS to AX

When creating a new report project in Visual Studio, if there is no option such as Microsoft Dynamics AX, then ensure that you have your reporting extensions installed. When you have multiple instances of Dynamics AX installed, Visual Studio identifies the instance to connect to from the client configuration. The active client configuration is used to establish the connection. The layer in which the report must be created is also fetched from the client configuration.

Retrieving metadata and data

With AX 2012, Windows Communication Foundation (WCF) based system services have been introduced. This includes the metadata service, query service, and user session service. The SSRS reporting extension uses the query and metadata services. The metadata service helps the report designer in Visual Studio to retrieve the metadata information of Queries, Tables, and Extended Data Types (EDT). The query service is used to fetch the data.

Verify the query

In the case of a complex query, a better approach would be validating the query before it is included in the report. Write a job in Dynamics AX that will use the query to retrieve the data and print the values to the infolog. This will help in identifying the problem when there is an issue with the report.

No joins

The report supports multiple datasets, but as in AX forms these datasets cannot be joined and they remain independent.

Creating auto designs from datasets

There are two ways to design an SSRS report in Visual Studio:

Precision design: This is for advanced structured design
Auto design: This is for general tabular design

In this recipe, we will create a simple auto design report by using the dataset added in the previous recipe, which will fetch the data and show it in the report.

In auto design, there are layouts that are already built in, and we can choose one in which we want to show the data, based on our preferences.

Getting ready

To develop reports in Dynamics AX 2012 R3, you need Visual Studio, through which you can design, develop, and deploy the reports. SQL Reporting Services must be properly installed and configured. You must also have access to the reporting manager to manage and see the reports present in AX 2012 R3.

How to do it...

In this recipe, we will add an auto design under the Design node of the report. We will then assign its layout properties to ReportLayoutStyleTemplate and print the report.

Note

There are some standard report templates in AX. You can choose any of them for pre-designed layouts.

Right-click on the Designs node, select Add, and then select Auto Design. This will create a new auto design under the Design node. Rename it as VendorMaster.
In the VendorMaster properties, set the LayoutTemplate property to ReportLayoutStyleTemplate and set the Name property to VendorMaster.
Under the new auto design node, right-click on VendorMaster and select Add | Table. Set the properties for this table as shown in the following screenshot:
Notice that the fields are added to the table design automatically.
Right-click on Auto design (VendorMaster) and select Preview. This will show a preview of the report.
To rearrange the fields as per the user requirement, go to the Data node under the Table node. You can move fields in two ways, by:
- Using the right-click menu options, such as Move to Top, Move Up, Move Down, Move to Bottom
- Using shortcuts, like Alt + Up/Down arrow

The new format will look like the following screenshot:

How it works…

Auto design is much easier to design and develop when compared to precision design. The default type (table/chart) for auto design is defined in the properties of the dataset. The default type determines what kind of control is added when the dataset is dragged and dropped into the auto design node.

Templates: Templates are responsible for printing the header, footer, and company name on a report. They also manage the font and colors. Currently, AX does not support printing the company image in the header through auto design.

Report preview: This accesses the default company in AX to show a report preview. So, ensure that the default company in AX has data, otherwise you may not find data in the preview.

Note

Standard SSRS reporting doesn't have the concept of auto design. This is only available in the AX SSRS implementation.

Adding ranges to the report

Ranges are very important and useful while developing an SSRS report in AX 2012 R3. They help to show only limited data, which is filtered based on given ranges, in the report.

The user can filter the data in a report on the basis of the field added as a range. The range must be specified in the query. In this recipe, we will show how we can filter the data and use a query field as a range.

How to do it...

In this recipe, we will add the field under the Ranges node in the query that we made in the previous recipe. By adding the field as a range, you can now filter the data on the basis of VendGroup and show only the limited data in the report.

Open the PKTVendorDetails query in AOT.
Drag the VendGroup and Blocked fields to the Ranges node in AOT and save your query.
In the Visual Studio project, right-click on Datasets and select Refresh.
Under the parameter node, VendorMaster_DynamicParameter collectively represents any parameter that will be added dynamically through the ranges. This parameter must be set to true to make additional ranges available during runtime. This adds a Select button to the report dialog, which the user can use to specify additional ranges other than what is added.
Right-click on the VendorMaster auto design and select Preview. The preview should display the range that was added in the query. Click on the Select button and set the VendGroup value to 10. Click on the OK button, and then select the Report tab, as shown in the following screenshot:
Save your changes and rebuild the report from Solution Explorer. Then, deploy the solution.

How it works…

The report dialog uses the query service UI builder (that we will cover in later chapters) to translate the ranges and to expose additional ranges through the query.

Dynamic parameter: The dynamic parameter unanimously represents all the parameters that are added at runtime. It adds the Select button to the dialog from where the user can invoke an advanced query filter window. From this filter window, more ranges and sorting can be added. The dynamic parameter is available per dataset and can be enabled or disabled by setting up the Dynamic Filters property to True or False.

Note

The Report Wizard in AX 2012 still uses MorphX reports to auto-create reports using the wizard. The auto report option is available on every form that uses a new AX SSRS report.

Deploying a report

SSRS, being a server side solution, needs to deploy reports in Dynamics AX 2012 R3. Until the reports are deployed, the user will not be able to see them or the changes made in them, neither from Visual Studio nor from the Dynamics AX rich client.

Reports can be deployed in multiple ways and the developer must make this decision. In this recipe, we will show you how we can deploy reports using the following:

Microsoft Dynamics AX R3
Microsoft Visual Studio
Microsoft PowerShell

Getting ready

In order to deploy reports, you must have the permission and rights to deploy them to SQL Reporting Services. You must also have the permission to access the reporting manager configuration.

Before deploying reports using Microsoft PowerShell, you must ensure that Windows PowerShell 2.0 is installed.

How to do it...

Microsoft Dynamics AX R3 supports the following ways to deploy SSRS reports.

Location of deployment

For each of the following deployment locations, let's have a look at the steps that need to be followed:

Microsoft Dynamics AX R3:
1. Reports can be deployed individually from a developer workspace in Microsoft Dynamics AX.
2. SSRS reports can be deployed by using the developer client in Microsoft Dynamics AX R3.
3. In AOT, expand the SSRS Reports node, expand the Reports node, select the particular report that needs to be deployed, expand the selected report node, right-click on the report, and then select and click on Deploy Element.
4. The developer can deploy as many reports as need to be deployed, but individually.
5. Reports can be deployed for all the translated languages.
Microsoft Visual Studio:
1. Individual reports can be deployed using Visual Studio.
2. Open Visual Studio. In Solution Explorer, right-click on the reporting project that contains the report that you want to deploy, and click on Deploy.
3. The reports are deployed for the neutral (invariant) language only.
Microsoft PowerShell:
1. This is used to deploy the default reports that exist within Microsoft Dynamics AX R3.
2. Open Windows PowerShell and by using this, you can deploy multiple reports at the same time.
3. Visit http://msdn.microsoft.com/en-us/library/dd309703.aspx for details on how to deploy reports using PowerShell.
To verify whether a report has been deployed, open the report manager in the browser and open the Dynamics AX folder. The PKTVendorDetails report should be found in the list of reports.
Note
You can find the report manager URL from System administration | Setup | Business intelligence | Reporting Services | Report servers.
The report can be previewed from Reporting Services also. Open Reporting Services and click on the name of the report to preview it.

How it works

Report deployment is the process of actually moving all the information related to a report to a central location, which is the server, from where it can be made available to the end user. The following list indicates the typical set of actions performed during deployment:

The RDL file is copied to the server.
The business logic is placed in the server location in the format of a DLL.
Deployment ensures that the RDL and business logic are cross-referenced to each other.
Note
The MorphX IDE from AX 2009 is still available. Any custom reports that are designed can be imported. This support is only for the purpose of backward compatibility. In AX 2012 R3, there is no concept of MorphX reports.

Creating a report using a query in Warehouse Management

In Dynamics AX 2012 R3, Warehouse Management is a new module. In the earlier version of AX (2012 or R2), there was a single module for Inventory and Warehouse Management. However, in AX R3, there is a separate module.

AX queries are the simplest and fastest way to create SSRS reports in Microsoft Dynamics AX R3. In this recipe, we will develop an SSRS report on Warehouse Management.

In AX R3, Warehouse Management is integrated with bar-coding devices such as RF-SMART, which supports purchase and receiving processes: picking, packing and shipping, transferring and stock counts, issuing materials for production orders, and reporting production as well. AX R3 also supports the workflow for the Warehouse Management module, which is used to optimize picking, packing, and loading of goods for delivery to customers.

Getting ready

To work through this recipe, Visual Studio must be installed on your system to design and deploy the report. You must have the permission to access all the rights of the reporting server, and reporting extensions must be installed.

How to do it...

Similar to other modules, Warehouse Management also has its tables with the "WHS" prefix. We start the recipe by creating a query, which consists of WHSRFMenuTable and WHSRFMenuLine as the data source. We will provide a range of Menus in the query. After creating a query, we will create an SSRS report in Visual Studio and use that query as the data source and will generate the report on warehouse management.

Open AOT, add a new query, and name it PKTWarehouseMobileDeviceMenuDetails.

Add a WHSRFMenuTable table.
Go to Fields and set the Dynamics property to Yes.
Add a WHSRFMenuLine table and set the Relation property to Yes. This will create an auto relation that will inherit from table relation node.
Go to Fields and set the Dynamics property to Yes.
Now open Visual Studio and add a new Dynamics AX report model project. Name it PKTWarehouseMobileDeviceMenuDetails.
Add a new report to this project and name it PKTWarehouseMobileDeviceDetails.
Add a new dataset and name it MobileDeviceDetails.
Select the PKTWarehouseMobileDeviceMenuDetails query in the Dataset property.
Select all fields from both tables. Click on OK.
Now drag and drop this dataset in the design node. It will automatically create an auto design. Rename it MobileMenuDetails.
In the properties, set the layout property to ReportLayoutStyleTemplate.
Now preview your report.

How it works

When we start creating an SSRS report, VS must be connected with Microsoft Dynamics AX R3. If the Microsoft Dynamics AX option is visible in Visual Studio while creating the new project, then the reporting extensions are installed. Otherwise, we need to install the reporting extensions properly.

What you will learn

Create and deploy reports in AX 2012 R3

Understand the SSRS report programming flow

Modify the reporting framework

Create RDPbased reports

Design tabular matrices and chartbased reports

Debug reports, the reporting framework, and business logic

Migrate reports from the legacy reporting framework

Get to grips with unit testing and troubleshooting SSRS reports

What do you get with a Packt Subscription?

Free for first 7 days. $19.99 p/m after that. Cancel any time!

Unlimited ad-free access to the largest independent learning library in tech. Access this title and thousands more!

50+ new titles added per month, including many first-to-market concepts and exclusive early access to books as they are being written.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

Thousands of reference materials covering every tech concept you need to stay up to date.

Subscribe now

View plans & pricing

Frequently bought together

Microsoft Dynamics AX 2012 R3 Reporting Cookbook Update

R$367.99

Microsoft Dynamics AX 2012 R3 Financial Management

R$306.99

Total R$ 674.98

Filter reviews by

All

Amazon verified reviews

adnan baloch May 19, 2015

Businesses depending on ERP to make their decisions have a great need to generate their own customized reports. In Microsoft Dynamics AX 2012 R3, the reporting component is powered by SQL Server Reporting Services (SSRS). This book demystifies the generation of reports using SSRS through easy to understand code samples. However, a sound understanding of object oriented concepts is a prerequisite. The book starts off by showing how to create a simple report using a query as a data source. The formatting of the report is made quick and easy with the help of the auto design feature. Ranges are utilized to help the users filter the data according to their needs. Finally, the report is deployed so it is visible as a menu item in AX. The second chapter tackles sprucing up the report through charts and custom images based on the evaluation of user defined expressions. The next chapter delves into the Report Programming Model in AX and explains how the Model-View-Controller pattern is used in the reporting framework of AX to generate data based on specified parameters and display the report. A particularly useful recipe in this chapter deals with using the same controller for calling multiple reports simulataneously while also handling their security. When reports are dependent on the analysis and consolidation of data provided by the business logic, the Report Data Provider(RDP) comes into play. Creating a report with multiple data sources in a single table as well as displaying company images in the report is made possible thanks to RDP. Connecting SSRS reports with external data sources like XML feeds, SQL server and OLAP are discussed in the next chapter. Adding a map sub report as well as using precision design to create a flexible sub report are also explained clearly. Using charts and gauges and adding validation in reports is made possible with AX 2012. The recipe showing how to upgrade from previous reports is very reassuring to longtime users of Dynamics AX. Surrogate fields introduced in AX 2012 can prove to be quite powerful. However, their proper use is shrouded in mystery for the uninitiated. Two practical examples demonstrate how to leverage surrogate fields in query-based as well as RDP-based reports. A chapter on troubleshooting provides a good deal of solutions for common issues encountered in deployment, rendering and data in reports. Tips are also provided for dealing with barcode generation and improving the performance of language-specific reports like Sales Invoice. Readers plagued by performance problems will particularly appreciate the section showing how to troubleshoot the cause of slowdown by using the free Report Log Viewer tool. The final chapter deals with creating unit classes for contract, controller and RDP classes to aid in testing the feature logic. The book bids adieu to the readers with some great time-saving and productivity-enhancing best practices for report development.

Amazon Verified review

Brian Apr 05, 2015

Deepak gives you the easy route to become an AX report expert. Great reference book for recall and patterns too!

gcc Spain May 20, 2015

This book drives you, in a very practical way, from the basics of Ax reporting to the most complex scenarios. Troubleshooting and performance tips are also really helpful. In my opinion it is a must for Ax technical community

Filippo Gallocchio Apr 23, 2015

Great book!Deepak has huge experience and that's make all easier

Pradeep May 06, 2015

Microsoft Dynamics AX 2012 R3 Reporting Cookbook is really a very useful to develop the SSRS report for a beginner level to an expert level. This book is explained in detail of developing a report with detailed screen shots and step by step explanation of development of a report. This book is very useful to me, so suggest to all technical consultants .....

Microsoft Dynamics AX 2012 R3 Reporting Cookbook Update: Over 90 recipes to help you resolve your new SSRS Reporting woes in Dynamics AX 2012 R3

What do you get with a Packt Subscription?

Reporting overview

Note

Connecting VS to AX

Retrieving metadata and data

Verify the query

No joins

Location of deployment

Note

Note

Description

Who is this book for?

What you will learn

Product Details

What do you get with a Packt Subscription?

Product Details

Packt Subscriptions

Frequently bought together

Table of Contents

Recommendations for you

Customer reviews

Filter reviews by

People who bought this also bought

About the 3 authors

FAQs