Reporting in Microsoft Dynamics AX [AX 2012]

Lasă un comentariu

3 Ianuarie 2014 de liviustoica55


Reporting in Microsoft Dynamics AX [AX 2012]    1

Reporting in Microsoft Dynamics AX [AX 2012]    5

Getting started with reporting [AX 2012]    6

What’s New: Reporting for IT Professionals in Microsoft Dynamics AX 2012 [AX 2012]    7

Support for data partitions    7

Support for report servers that run in SharePoint integrated mode    7

Simplified installation    8

Improvements to the report deployment process    8

Upgrade information    8

Security changes    8

Parity with the legacy X++ reporting framework    9

What’s New: Reporting for Developers in Microsoft Dynamics AX 2012 [AX 2012]    10

Reporting Improvements    11

Parity with Existing Functionality    18

Overview of Reporting Services [AX 2012]    20

Native mode    20

SharePoint integrated mode    21

Types of reports [AX 2012]    28

Planning and architecture of reporting [AX 2012]    30

Reporting architecture [AX 2012]    30

Planning considerations for reporting [AX 2012]    35

Is native mode supported?    35

Is SharePoint integrated mode supported?    35

Can multiple instances of Reporting Services be installed on the same computer?    35

Is an AOS scale-out deployment supported with Reporting Services?    37

Is a Reporting Services scale-out deployment supported?    38

Is failover clustering supported?    38

Is AlwaysOn supported?    39

How can I create new, custom reports?    39

How can I generate reports on a recurring basis?    39

Deployment of reporting [AX 2012]    40

Install Reporting Services extensions for Microsoft Dynamics AX [AX 2012]    40

Checklist: Install the Reporting Services extensions and deploy reports [AX 2012]    41

Before you install the Reporting Services extensions [AX 2012]    42

Configure the Reporting Services instance by using the Reporting Services Configuration Manager tool    43

Configure the Reporting Services instance for local administration    45

Configure Reporting Services 2008 in SharePoint integrated mode    46

Configure Reporting Services 2012 in SharePoint integrated mode    47

Install the Reporting Services extensions [AX 2012]    48

Complete the Reporting Services integration [AX 2012]    50

Create a document library to store reports [AX 2012]    51

Deploy the default reports [AX 2012]    53

Grant users access to reports [AX 2012]    56

Deploy language-specific versions of a report [AX 2012]    57

How to: Deploy Reports to a Report Server [AX 2012]    60

To deploy reports from Microsoft Dynamics AX    61

To deploy reports from Microsoft Visual Studio    61

Install multiple instances of Reporting Services on the same computer (for use with Microsoft Dynamics AX) [AX 2012]    62

Install the new Reporting Services instance [AX 2012]    64

Configure the new Reporting Services instance [AX 2012]    71

Modify Reporting Services configuration files [AX 2012]    73

Restart the new Reporting Services instance [AX 2012]    77

Create a new Microsoft Dynamics AX configuration [AX 2012]    78

Connect Microsoft Dynamics AX to the new Reporting Services instance [AX 2012]    78

Deploy reports for the new Reporting Services instance [AX 2012]    81

Revert to the original Microsoft Dynamics AX configuration    84

Upgrading Reports [AX 2012]    84

Report Upgrade [AX 2012]    84

X++ reports    85

Microsoft Visual Studio tools for Microsoft Dynamics AX reports    86

Report Project Upgrade [AX 2012]    88

Using the Report Upgrade Tool    88

Examples    89

Guidance when Upgrading Reports [AX 2012]    90

Define a New Reporting Services Report    91

Convert the Report to a Reporting Services Report    92

Mapping Microsoft Dynamics AX 2009 Reports to the Microsoft Dynamics AX 2012 Version [AX 2012]    94

Report Mapping to a Non-Reporting Services Implementation    134

Deprecated Microsoft Dynamics AX 2009 Reports in Microsoft Dynamics AX 2012 [AX 2012]    136

Security and protection for reporting [AX 2012]    147

Security Considerations Creating a Report [AX 2012]    147

Security settings for reports [AX 2012]    150

Assign users and groups to the DynamicsAXBrowser role    150

Restrict access to report folders and reports    151

Operation of reporting [AX 2012]    152

How to work with the reports that are provided by Microsoft Dynamics AX [AX 2012]    152

Print a report [AX 2012]    153

Print a report on a recurring basis [AX 2012]    155

Print a report during off-peak hours [AX 2012]    158

Print a report from the archive [AX 2012]    161

Filter the data on a report [AX 2012]    161

Sort the data on a report [AX 2012]    162

How to create a custom report [AX 2012]    163

Create a report by using the Microsoft Dynamics AX auto-report wizard [AX 2012]    165

Create a report by using the Excel data connection wizard to connect to a cube [AX 2012]    167

Create a report by using SQL Server Report Builder to connect to a cube [AX 2012]    168

Create a report by using SQL Server Power View to connect to a cube [AX 2012]    171

 

 

 

Reporting in Microsoft Dynamics AX [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: January 15, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

The focus for this section is on Reporting Services reports.

Tip

To apply advanced criteria to your search for Help about Microsoft Dynamics AX, use the WebSearchAx tool.

In This Section


Getting started with reporting

Planning and architecture of reporting

Deployment of reporting

Security and protection for reporting

Operation of reporting

Developing Reports for Microsoft Dynamics AX in Visual Studio

Troubleshoot reporting

Technical reference for reporting

 

 

 

Getting started with reporting [AX 2012]

0 out of 1 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

The following topics provide an overview of the reporting features of Microsoft Dynamics AX.

What’s New: Reporting for IT Professionals in Microsoft Dynamics AX 2012

What’s New: Reporting for Developers in Microsoft Dynamics AX 2012

Overview of Reporting Services

Types of reports

 

What’s New: Reporting for IT Professionals in Microsoft Dynamics AX 2012 [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Microsoft SQL Server Reporting Services is now the primary reporting platform for Microsoft Dynamics AX. The default, predefined reports that are provided with Microsoft Dynamics AX run on the Reporting Services platform.

This topic describes the new reporting features of Microsoft Dynamics AX.

New features in Microsoft Dynamics AX 2012 R2


The following reporting features have been added in Microsoft Dynamics AX 2012 R2.

Support for data partitions

A Microsoft Dynamics AX 2012 R2 installation may consist of multiple data partitions. One report server can support all the data partitions in a Microsoft Dynamics AX 2012 R2 installation. For more information about data partitions, see Data partitioning architecture.

Support for report servers that run in SharePoint integrated mode

Reporting Services can be installed in native mode or SharePoint integrated mode. Report servers that run in SharePoint integrated mode are supported by Microsoft Dynamics AX 2012 R2.

In SharePoint integrated mode, a report server runs within a SharePoint server farm. Reports are managed and viewed from SharePoint document libraries. For more information, see Overview of Reporting Services.

New features in Microsoft Dynamics AX 2012


The following reporting features have been added in Microsoft Dynamics AX 2012.

Simplified installation

In Microsoft Dynamics AX 2012, the Setup wizard has been updated to simplify the process of installing the Reporting Services extensions. When you install the Reporting Services extensions, the Setup wizard will:

  • Verify that prerequisite software has been installed on the server that runs Reporting Services. For more information about the prerequisite software, see the system requirements web page.
  • Prompt you to select an instance of Reporting Services. The extensions that you are installing will be configured to use this instance. For more information, see Install Reporting Services extensions for Microsoft Dynamics AX.
  • Enable you to deploy the default reports that are included with Microsoft Dynamics AX.

Improvements to the report deployment process

The process of deploying reports has changed in the following ways.

Feature

Description

Deploy reports using Windows PowerShell

In Microsoft Dynamics AX 2009, the Microsoft Dynamics AX Reporting Project Deployment form is used to deploy reports. In Microsoft Dynamics AX 2012, Windows PowerShell commands are used to deploy reports. For more information about how to use Windows PowerShell commands to deploy reports, see Deploy the default reports.

Improved support for multiple languages

In Microsoft Dynamics AX 2009, when you deploy a report, 42 versions of the report are deployed. One version of the report is deployed for every language that is supported by Microsoft Dynamics AX. For example, when you deploy the Sales Order report, 42 versions of that report are deployed: one for English, one for French, one for German, and so on.

In Microsoft Dynamics AX 2012, when you deploy a report, one version of the report is deployed. That version renders in every language that is supported by Microsoft Dynamics AX.

Upgrade information

When you upgrade from Microsoft Dynamics AX 2009, existing reports are copied to the Microsoft Dynamics AX 2012 system, but they are not upgraded. Microsoft Dynamics AX 2012 provides hundreds of default, predefined reports that you can deploy and customize. We recommend that you use these reports as templates, and customize them to meet your needs. For more information, see Upgrading Reports.

Security changes

The following changes that pertain to security have been made.

Feature

Description

Kerberos authentication is no longer required

In Microsoft Dynamics AX 2009, Kerberos authentication is required for environments where:

  • Enterprise Portal for Microsoft Dynamics AX is installed on a server other than the server that is running Reporting Services and/or Analysis Services.
  • The Reporting Services database exists on a server other than the server that is running the Windows service for Reporting Services.

In Microsoft Dynamics AX 2012, Kerberos authentication is not required.

Integration with the new security model

Reports are fully integrated into the new Microsoft Dynamics AX security model. When you help secure data by using duties and privileges, reports automatically respect that security. For more information about how to set up security for reports, see Security settings for reports.

Parity with the legacy X++ reporting framework

The following features have been added so that Reporting Services reports have the same capabilities as the legacy X++ reports.

Feature

Description

Filter and sort the data on Reporting Services reports

You can now filter and sort the data that is displayed on Reporting Services reports. For more information, see Filter the data on a report and Sort the data on a report.

Create auto-reports

Auto-reports are preconfigured reports that you can generate by clicking File > Print > Print in a Microsoft Dynamics AX form. You can quickly generate an auto-report for a single use. Alternatively, you can create a custom auto-report, and then save the report so that it can be reused later. For more information, see Create a report by using the Microsoft Dynamics AX auto-report wizard.

Print Reporting Services reports as part of a batch

In Microsoft Dynamics AX 2012, you can print Reporting Services reports as part of a batch. This capability lets you perform the following tasks:

Manage print settings for reports

In Microsoft Dynamics AX 2012, you can manage the print settings for reports. This capability lets you perform the following tasks:

  • Modify the print settings of a report based on the contents of the data being printed. For example, you can print sales orders that total less than USD 1,000 to printer A, and sales orders that total USD 1,000 or more to printer B.
  • Specify print settings at various levels of the application. For example, you can set up module-level print settings to apply to all documents in a specific module, and customer-level print settings to apply to documents for specific customers.

For more information about how to use the print management features of Microsoft Dynamics AX, see the Print Management Integration Guide

 

What’s New: Reporting for Developers in Microsoft Dynamics AX 2012 [AX 2012]

2 out of 2 rated this helpful – Rate this topic

Updated: November 15, 2011

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

SQL Server Reporting Services is now the primary reporting platform for Microsoft Dynamics AX. The default, out-of-the-box reports that are provided with Microsoft Dynamics AX now run on the Reporting Services platform.

What is new or changed?


Reporting Services is a server-based reporting platform that provides comprehensive reporting functionality for a variety of data sources. Reporting Services includes a complete set of tools for you to create, manage, and deliver reports, as well as APIs that enable you to integrate or extend data and report processing in custom applications. The new report development environment takes advantage of extended SQL Server tools and components. The report development environment is fully integrated into Microsoft Visual Studio. For more information, see Reporting in Microsoft Dynamics AX.

Reporting Improvements

The following table describes the improvements that have been made to the Microsoft Dynamics AX reporting framework.

What can you do?

Microsoft Dynamics AX 2009

Microsoft Dynamics AX 2012

Why is this important?

Where can I find more information?

Access data for a report.

Used Microsoft Dynamics AX queries, data from analysis cubes, external SQL Server databases, data methods that access data from Microsoft Dynamics AX or other sources, and managed code for data access.

Uses the data access methods available in Microsoft Dynamics AX 2012 and the report data provider (RDP) framework to define business logic for a report.

When you use Microsoft Dynamics AX queries, the reporting framework was enhanced to support display methods, field groups, and dimensions. When you add a field to a field group, the field is automatically reflected throughout the application. This means that reports automatically add the field. Display methods are treated like fields in the query, even though the display method is retrieving the data from a different table. Support for dimensions means that you can create a report design using dimension attributes in the data set and dimension attributes can be used as report parameters.

A report data provider class lets you write X++ code to define your report business logic.

Report Data Overview

Report Programming Guide

Use labels in a report.

Each language locale required a .resx file to store localized strings.

Use AX labels in your reports that can be dynamically resolved at runtime.

Using AX labels in reports, you no longer have to create a .resx file for each language which improves the time to deploy reports. Only one report definition per report is needed.

How to: Use a Label in a Report

Use data on your report that is based on specific time periods.

Feature not available.

Create a report that has data that is based on specific time periods. The reporting framework supports date effective data.

You do not have to handle date effective data explicitly for Microsoft Dynamics AX query based datasets.

Walkthrough: Creating a Report Bound to Date Effective Data

Use an improved set of developer tools.

Used X++ Reporting Framework and Visual Studio 2008.

Use Visual Studio 2010 integration, take advantage of enhancements to auto-design reports, and create precision design reports that use the chart features in Reporting Services 2008.

In line with the long term goal to align with the Microsoft technology stack.

Brings Reporting Services features to Microsoft Dynamics AX developers like rich charting and interactive reports. The following list describes additional improvements in the reporting tools:

  • The Preview option is now enabled for all nodes under the design node.
  • A drop-down was added to display the possible parameter types.
  • Microsoft PowerPivot and other Open Data Protocol (OData) Clients are now supported.
  • SQL Server Reporting Services sub reports in precision design are now supported.
  • Report Data Customization Extension (RDCE) uses Windows event viewer logging.
  • New expressive charting capabilities for precision design reports.

Creating Reports Overview

Process business logic for data on a report.

Used a report data method and managed code.

Use the report data provider (RDP) framework that supports complex business logic in X++ code.

The report data provider framework can support logic to handle data on a report like calculating an amount based on a specific field.

How to: Use a Report Data Provider Class in a Report

Report Programming Guide

Use services to access data and business logic for a report.

Used .NET Business Connecter, which has a weakly-typed programming model.

Create a custom service and access the service from a report.

Queries and RDP use services to access data for a report.

Standards-based service interfaces enable you to integrate with many platforms.

Services are strongly typed meaning that issues are found at design time instead of run time.

A service was added by the reporting framework to consume a report data provider class from an external application. Services enable you to quickly expose existing X++ business logic without additional coding.

Services and Application Integration Framework (AIF)

How to: Reference a Service from a Data Method

Work with large datasets for a report.

Used a report data method to return a data table.

Create reports that use large datasets. Added functionality now binds to data methods that return data in a page or stream of data.

Only the first row of a dataset must be executed in order to determine the report schema. This makes it easier to work with large datasets. Now you can write business logic that returns data in a page or a stream of data. You no longer need to fill the data table before you return it which was using memory and resources on the Reporting Server.

Report Data Method Overview

Use Microsoft Dynamics AX metadata to auto-format a report.

Defined the report format explicitly.

Create reports where the auto-formatting of the report is based on the formatting specified for the extended data types.

Display width, date/time and numeric formatting are automatically set. All style and colors were updated to be correct.

You can use metadata to handle whether a field or table should be visible on a report.

Report Data Overview

Define secure reports based on the role of the user.

Reports were secured using security keys.

Secure your reports by using role-based security and extensible data security (XDS) policies.

When you save a report to the AOT, the securable objects will be added to the base permission set under the report design node. When a menu item is created and linked to a report design, the minimum permissions to execute the report are derived from the base permission set.

XDS policies can be created to limit records that a user in a particular role can access.

Report security is based on the user role and you can specify with more precision which data is displayed on a report.

Security Considerations Creating a Report

Create an unlimited number of dimensions attributes.

Limited to three default dimensions and seven user-definable dimension attributes.

Use the query picker, report model, and report generation that were updated to reflect improvements to the dimension framework.

Create an unlimited number of dimension attributes using the dimension framework. Additional flexibility is enabled by the ability to combine dimension attributes.

Walkthrough: Creating a Report Bound to a Dimension Data Source

Reap the benefits of queries using a surrogate foreign key (SFK).

Report queries sourced data from tables that sometimes contain natural keys and the text for the fields was not always understandable.

Use queries that are using SFKs instead of natural keys.

Some of the benefits include improved readability, reduced database size, decreased time to upgrade, and fewer data integrity issues.

A lookup was added to the ReportRunUI control for SFK parameters to let you filter on a SFK relationship in a report.

Walkthrough: Leveraging Foreign Keys in Query Relations

Access cross-reference information for a Reporting Services report.

Feature not available.

Use the cross-reference tool with Reporting Services reports.

You can see what data the report is using and what AOT objects are using the report.

Walkthrough: Using the Cross-Reference Tool with Visual Studio Projects

Define a report that can be flipped from right to left based on the language that is set for the report.

Right to left flip of a report design was not supported.

A new precision design was needed where all the report items were flipped manually which resulted in two designs for the same report.

Create a report that will flip right to left at runtime, based on the language that is set and properties set on the report.

You no longer need to maintain two report designs for reports that require a right to left flip.

Localizing Reports

AX_CompanyNamereport parameter has been updated to reflect changes in Microsoft Dynamics AX 2012.

At report design time, the company name report parameter was added to each report.

TheAX_CompanyNamereport parameter was unique because it could not be deleted and it was not required to be initialized.

The AX_CompanyNameparameter is only added when the query is company specific.

You can initialize theAX_CompanyNameparameter using built-in methods.

You can add organization parameters to your report such as Operating Unit or Department.

The AX_CompanyName parameter was created by the Microsoft Dynamics AX framework for queries that are company specific.

This change reflects the organization hierarchy product wide feature.

How to: Create a Company Parameter in a Report

Organizations and organizational hierarchies

Use the improved drill-through functionality on reports.

Feature not available.

The following list describes the changes that were made to improve the drill-through functionality on reports.

  • The client no longer uses table IDs, instead it uses table and field names to determine which menu item the report link should use.
  • The link style is no longer underlined and the color was changed.
  • The drill-through now opens in a new client window.

Using table and field names reduces ambiguity and errors.

The updated link style is consistent with expected link style. This improves the look and usability of reports that have links.

Launching a new window for a linked report is consistent with expected behavior and improves the usability of reports that have links.

Walkthrough: Creating a Drillthrough Report

Parity with Existing Functionality

The following table describes the features that were added so that the Reporting Services reports have the same capabilities as the legacy X++ reports.

Feature

Description

Link to more information

Modify queries used by reports

Allows you to filter and sort data on reports.

How to: Define a Report with Dynamic Filters

Control report destination settings

The PrintDestinationSettings class was added to allow you to programmatically change print settings such as printing a report.

Managing Reporting Services Reports using X++

Report Programming Guide

Create auto-reports

An auto-report is a report that is generated by clicking Print on a form. The data on the form is displayed on the report. Auto-reports are generated by using the Reporting Services framework for Microsoft Dynamics AX.

Create a Report by Using the Microsoft Dynamics AX Auto-Report Wizard

Print reports in a batch

You can use the Reporting Services framework to print a batch of reports, print a report on a recurring basis, and schedule a report to be printed during off peak hours.

How to work with the reports that are provided by Microsoft Dynamics AX

Are there any special considerations?


Reports will not be upgraded from Microsoft Dynamics AX 2009 to Microsoft Dynamics AX 2012. Microsoft Dynamics AX 2012 provides hundreds of default, out-of-the-box reports that you can deploy and customize.

When upgrading, existing Reporting Services and X++ reports will be copied to the Microsoft Dynamics AX 2012 system, but they will not be upgraded. We recommend that you use a Reporting Services report that is provided with Microsoft Dynamics AX 2012 as a template and customize it to meet your needs.

See also


Reporting in Microsoft Dynamics AX

 

Overview of Reporting Services [AX 2012]

2 out of 2 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Microsoft SQL Server Reporting Services is now the primary reporting platform for Microsoft Dynamics AX. The default, preconfigured reports that are included with Microsoft Dynamics AX run on the Reporting Services platform.

Before you integrate Microsoft Dynamics AX and Reporting Services, review this topic to better understand the concepts and components of Reporting Services.

Reporting Services modes


When you install Reporting Services, you must select a mode in which to run Reporting Services. Two modes are available: native mode and SharePoint integrated mode.

Native mode

In native mode, a report server is a stand-alone application server. Native mode is the default mode for Reporting Services.

If the report server is running in native mode, the reports that are included with Microsoft Dynamics AX are deployed to the Report Manager website. You can manage and view the reports from this website. The following picture shows the Report Manager website that contains Microsoft Dynamics AX reports.


For instructions about how to configure Reporting Services in native mode, see Before you install the Reporting Services extensions.

SharePoint integrated mode

In SharePoint integrated mode, a report server runs in a SharePoint server farm.

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.

If the report server is running in SharePoint integrated mode, the reports that are included with Microsoft Dynamics AX are deployed to a document library on a SharePoint website. You can manage and view the reports from this document library. The following picture shows a document library that contains Microsoft Dynamics AX reports.


For instructions about how to configure Reporting Services in SharePoint integrated mode, see Before you install the Reporting Services extensions.

Reporting Services Configuration Manager


After you install a Reporting Services instance, you can use Reporting Services Configuration Manager. This tool helps you configure settings and specify which accounts are used by the Reporting Services instance. For more information about how to use Reporting Services Configuration Manager, see Before you install the Reporting Services extensions.

Note

Reporting Services Configuration Manager is not used to configure and administer an instance of Reporting Services 2012 that is running in SharePoint integrated mode.

The following picture shows the Reporting Services Configuration Manager that is included with Reporting Services 2012.


Report Manager


When you configure a Reporting Services instance that is running in native mode, a website that is named Report Manager is created. As the Microsoft Dynamics AX administrator, you deploy the reports that are included with Microsoft Dynamics AX to this site.

By default, the URL of the Report Manager site is http://%5BSSRSServerName%5D:80/Reports. The following picture shows the Report Manager website.


Reporting Services web service


When you configure a Reporting Services instance, a web service is created. Users cannot access reports unless this service is running.

The URL of the web service is typically http://%5BSSRSServerName%5D:80/ReportServer. However, if you are using Reporting Services 2012 in SharePoint integrated mode, the URL is typically http://%5BSharePointServerName%5D/_vti_bin/ReportServer or http:[SharePointServerName]/sites/[SiteName]/_vti_bin/ReportServer.

The following picture shows the web service for an instance of Reporting Services that is running in native mode.


Report Builder


Report Builder is an ad hoc reporting tool that lets users create their own reports. For more information about how to use Report Builder to create a report that accesses Microsoft Dynamics AX data, see Create a report by using SQL Server Report Builder to connect to a cube.

The following picture shows Report Builder in design mode.


Top of Form

Types of reports [AX 2012]

1 out of 1 rated this helpful – Rate this topic

Updated: January 29, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

The following table describes the types of reports that you can create by using the reporting and analytical features of Microsoft Dynamics AX.

Category

Tool that is used to create the report

Format of the report

Type of user who typically creates this kind of report

For more information

Transactional reports

Transactional reports retrieve data from the transaction processing database for Microsoft Dynamics AX.

Visual Studio

Reporting Services report

Developer

Developing Reports for Microsoft Dynamics AX in Visual Studio

Microsoft Dynamics AX list page

Excel worksheet

System administrator

Application user

Use a list page

Microsoft Dynamics AX auto-report wizard

Reporting Services report

System administrator

Application user

Create a report by using the Microsoft Dynamics AX auto-report wizard

Microsoft Dynamics AX add-in for Excel

Excel worksheet

System administrator

Application user

Using the Microsoft Dynamics AX Add-in for Excel

Management Reporter for Microsoft Dynamics ERP

Management Reporter report

System administrator

Application user

Microsoft Management Reporter: Installation, Migration, and Configuration Guides

Analytical reports

Analytical reports retrieve data from Microsoft SQL Server Analysis Services cubes.

Visual Studio

Reporting Services report

Developer

Walkthrough: Displaying Cube Data in a Report

SQL Server Business Intelligence Development Studio or SQL Server Data Tools

Key performance indicator (KPI)

Developer

Walkthrough: Defining KPIs for a Cube

Walkthrough: Displaying KPIs in a Role Center

SQL Server Report Builder

Reporting Services report

Developer

System administrator

Create a report by using SQL Server Report Builder to connect to a cube

Excel

Excel worksheet

System administrator

Application user

Create a report by using the Excel data connection wizard to connect to a cube

SQL Server Power View

Reporting Services report

System administrator

Application user

Create a report by using SQL Server Power View to connect to a cube

 

 

Planning and architecture of reporting [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Planning is required to successfully implement the reporting features of Microsoft Dynamics AX. The following topics explain the architecture of the reporting features and help you plan an implementation.

Reporting architecture

Planning considerations for reporting

Reporting architecture [AX 2012]

4 out of 5 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

This topic describes the architecture of the reporting functionality in Microsoft Dynamics AX.

Architecture for typical installations


The following diagram illustrates how a report is rendered in Microsoft Dynamics AX. This diagram represents the reporting architecture when one of the following versions of Microsoft SQL Server Reporting Services is installed:

  • Reporting Services 2008 in native mode
  • Reporting Services 2008 in SharePoint integrated mode
  • Reporting Services 2008 R2 in native mode
  • Reporting Services 2008 R2 in SharePoint integrated mode
  • Reporting Services 2012 in native mode

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.

 


To better understand how a report is rendered, review the following steps:

  1. A user requests a report.

    A menu item in the Microsoft Dynamics AX client may be bound to a report for Reporting Services. After a user clicks the menu item, a parameters form is displayed to the user. The user enters parameters to filter the data that is displayed on the report.

    The Microsoft Dynamics AX client then requests the report from an instance of Reporting Services. The request includes the parameters that the user entered.

  2. Reporting Services receives the request and requests the report data from the Microsoft Dynamics AX server.

    Reporting Services receives the request and examines the report. The report is stored as an .rdl file. The .rdl file indicates the report’s data source. The data source may be a Microsoft Dynamics AX query, a report data provider class, or an external data source that is accessed through report data methods.

    If a Microsoft Dynamics AX data source is used for the report, Reporting Services uses the Microsoft Dynamics AX data extension to retrieve the data.

    Reporting Services then requests metadata about the data source from Microsoft Dynamics AX. Then Reporting Services requests the data for the report.

  3. The Microsoft Dynamics AX server receives the request and sends the report data back to Reporting Services.

    The Microsoft Dynamics AX services examine the query in the Application Object Tree (AOT) to return the requested metadata. The services also run the query to generate the data for the report.

    Microsoft Dynamics AX then returns the metadata and data to Reporting Services.

Note

Microsoft Dynamics AX enforces security on all data that it returns. If the user who is running the report is not allowed to see a specific field, the data for that field is not returned.

  1. Reporting Services renders the report and sends it to the Microsoft Dynamics AX client.

    The Microsoft Dynamics AX customization extension formats the report. The customization extension uses metadata to provide automatic formatting of data and can affect the positioning and layout of elements on the report.

    Reporting Services then renders the report into a visual representation and sends that representation to the Microsoft Dynamics AX client.

  2. The report is displayed to the user.

    The Microsoft Dynamics AX client displays the report to the user in the report viewer control.

Architecture for Reporting Services 2012 installations in SharePoint integrated mode


The following diagram illustrates how a report is rendered in Microsoft Dynamics AX. This diagram represents the reporting architecture when Reporting Services 2012 is installed in SharePoint integrated mode.

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.


To better understand how a report is rendered, review the following steps:

  1. A user requests a report.

    A menu item in the Microsoft Dynamics AX client may be bound to a report for Reporting Services. After a user clicks the menu item, a parameters form is displayed to the user. The user enters parameters to filter the data that is displayed on the report.

    The Microsoft Dynamics AX client then requests the report from the Reporting Services service application in SharePoint. The request includes the parameters that the user entered.

  2. The Reporting Services service application receives the request and requests the report data from the Microsoft Dynamics AX server.

    The Reporting Services service application receives the request and examines the report. The report is stored as an .rdl file. The .rdl file indicates the report’s data source. The data source may be a Microsoft Dynamics AX query, a report data provider class, or an external data source that is accessed through report data methods.

    If a Microsoft Dynamics AX data source is used for the report, the Reporting Services service application uses the Microsoft Dynamics AX data extension to retrieve the data.

    The Reporting Services service application then requests metadata about the data source from Microsoft Dynamics AX. Then the Reporting Services service application requests the data for the report.

  3. The Microsoft Dynamics AX server receives the request and sends the report data back to the Reporting Services service application.

    The Microsoft Dynamics AX services examine the query in the Application Object Tree (AOT) to return the requested metadata. The services also run the query to generate the data for the report.

    Microsoft Dynamics AX then returns the metadata and data to the Reporting Services service application.

Note

Microsoft Dynamics AX enforces security on all data that it returns. If the user who is running the report is not allowed to see a specific field, the data for that field is not returned.

  1. The Reporting Services service application renders the report and sends it to the Microsoft Dynamics AX client.

    The Microsoft Dynamics AX customization extension formats the report. The customization extension uses metadata to provide automatic formatting of data and can affect the positioning and layout of elements on the report.

    The Reporting Services service application then renders the report into a visual representation and sends that representation to the Microsoft Dynamics AX client.

  2. The report is displayed to the user.

    The Microsoft Dynamics AX client displays the report to the user in the report viewer control.

 

 

Planning considerations for reporting [AX 2012]

1 out of 1 rated this helpful – Rate this topic

Updated: February 4, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Consider the following information before you implement the reporting features of Microsoft Dynamics AX.

Reporting Services modes


To integrate Microsoft SQL Server Reporting Services for use with Microsoft Dynamics AX, consider the following information.

Is native mode supported?

Microsoft Dynamics AX can be integrated with Reporting Services servers that are running in native mode. For instructions about how to configure Reporting Services in native mode, see Before you install the Reporting Services extensions.

Is SharePoint integrated mode supported?

Reporting Services servers that are running in SharePoint integrated mode are supported only if you are using Microsoft Dynamics AX 2012 R2. For instructions about how to configure Reporting Services in SharePoint integrated mode, see Before you install the Reporting Services extensions.

Topology


To help plan your Microsoft Dynamics AX implementation, consider the following information.

Can multiple instances of Reporting Services be installed on the same computer?

You can install multiple instances of Reporting Services on the same computer. In this kind of deployment environment, each instance of Reporting Services is connected to an independent Microsoft Dynamics AX installation. You may want to install multiple instances of Reporting Services on the same computer for the following reasons:

  • To support development and production installations of Microsoft Dynamics AX

    For example, in the following sample diagram, assume that AOS instance 1 is a development installation of Microsoft Dynamics AX, and AOS instance 2 is the production installation of Microsoft Dynamics AX.

  • To support multiple production installations of Microsoft Dynamics AX

    For example, if you are a Microsoft Dynamics AX solution provider, you may have to support multiple production installations of Microsoft Dynamics AX. For this scenario, assume that AOS instance 1 (in the sample diagram) is a production installation of Microsoft Dynamics AX for one client, Northwind Traders. Assume that AOS instance 2 is a production installation of Microsoft Dynamics AX for another client, Contoso Pharmaceuticals.


Note

You cannot install multiple instances of Reporting Services 2012—that run in SharePoint integrated mode—on the same computer.

For more information, see Install multiple instances of Reporting Services on the same computer (for use with Microsoft Dynamics AX).

Is an AOS scale-out deployment supported with Reporting Services?

You can distribute the user load in Microsoft Dynamics AX across multiple instances of the Application Object Server (AOS) by creating a load balancing cluster. The cluster may or may not include a dedicated load balancer.

In an environment that contains an AOS load balancing cluster, you must point each AOS instance to the same Reporting Services instance. For example, your environment may resemble the following illustration.


To integrate an AOS load balancing cluster with Reporting Services, complete the following tasks.

  1. Install the Reporting Services extensions on the server running Reporting Services. For more information, see Install the Reporting Services extensions.

    When you install the Reporting Services extensions, the Setup wizard requires you to connect to an AOS instance. Connect to an AOS instance in the cluster. However, if the cluster includes a dedicated load balancer, do not connect to the AOS instance that serves as the dedicated load balancer.

    When the installation is complete, the AOS instance that you selected is connected to the Reporting Services instance. You can view the properties of this connection in the Report servers form in Microsoft Dynamics AX.

  2. Connect the other AOS instances in the cluster to the Reporting Services instance. To connect an AOS instance to the Reporting Services instance, complete these steps:
    1. Open the Microsoft Dynamics AX client.
    2. Click System administration > Setup > Business intelligence > Reporting Services > Report servers.
    3. Connect the AOS instance to the Reporting Services instance by creating a new record in the Report servers form. For more information about how to use this form, see Report servers (form).

Is a Reporting Services scale-out deployment supported?

A report server scale-out deployment includes two or more report server instances that share a single report server database. By using a Reporting Services scale-out deployment, you can increase the number of users who can access reports at the same time. You can also improve the availability of the report server.

Microsoft Dynamics AX supports scale-out deployments of Reporting Services in an environment that has the following configuration:

  • The Reporting Services instances are installed on separate computers.
  • The Reporting Services instances share a single database.
  • A Network Load Balancing (NLB) cluster is used.
  • The Reporting Services extensions that are provided by Microsoft Dynamics AX are installed on each computer where Reporting Services is installed.

An environment of this kind may resemble the following illustration.


For more information about how to configure a scale-out deployment, see the Configuring a SQL Server Reporting Services scale-out deployment to run on a Network Load Balancing cluster white paper. For more information about Reporting Services scale-out deployments, see Planning for scale-out deployment in the SQL Server documentation.

Is failover clustering supported?

Reporting Services cannot be installed on a failover cluster because you cannot run the Reporting Services service as part of a failover cluster. However, you can install the report server database on a computer that has a failover cluster installed. For more information, see Host a Report Server Database in a SQL Server Failover Cluster.

Is AlwaysOn supported?

SQL Server AlwaysOn is the new high availability and disaster recovery solution in SQL Server 2012. AlwaysOn is not supported for the report server database. This is because report data is accessed through the Microsoft Dynamics AX AOS server, which does not support read-only databases.

Security


To grant users access to reports, you must complete the following tasks:

  • Configure security settings in Microsoft Dynamics AX.
  • If you are running Reporting Services in native mode, assign users to the DynamicsAXBrowser role on the Report Manager website.
  • If you are running Reporting Services in SharePoint integrated mode, grant users Read permission to the document library that stores the reports.
  • Assign users to roles in Microsoft SQL Server Analysis Services.

For more information about how to complete these tasks, see Security settings for reports.

Customizations


To help plan any customizations that you must implement, consider the following information.

How can I create new, custom reports?

If you or anyone in your organization has to create a new, custom report, several tools are available. For example, you can use the auto-report wizard in Microsoft Dynamics AX to create a report that lists the customers who receive a 5 percent discount. Alternatively, you can use the data connection wizard in Microsoft Excel to create a PivotChart report that displays the total sales, by product, for each salesperson in all regions over all recorded years.

For more information about the tools that you can use to create a customized report, see Types of reports.

How can I generate reports on a recurring basis?

You can configure Microsoft Dynamics AX to automatically print reports on a recurring basis. For example, Microsoft Dynamics AX can automatically send a specific report to you and your team members by email every Monday morning. For more information, see Print a report on a recurring basis.

Note

Microsoft Dynamics AX reports do not support the subscription functionality that is available on the Report Manager site of Reporting Services.

 

 

 

 

 

Deployment of reporting [AX 2012]

1 out of 1 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

The following topics explain how to install the Microsoft SQL Server Reporting Services extensions and deploy the reports that are included with Microsoft Dynamics AX. Information about how to upgrade reports from Microsoft Dynamics AX 2009 to Microsoft Dynamics AX 2012 is also included.

Install Reporting Services extensions for Microsoft Dynamics AX

Install multiple instances of Reporting Services on the same computer (for use with Microsoft Dynamics AX)

Upgrading Reports

 

Install Reporting Services extensions for Microsoft Dynamics AX [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Microsoft SQL Server Reporting Services is the primary reporting platform for Microsoft Dynamics AX. The reports that are included with Microsoft Dynamics AX run on the Reporting Services platform.

To integrate Microsoft Dynamics AX and Reporting Services, you must complete several procedures. You must first install the Reporting Services extensions by running the Microsoft Dynamics AX Setup Wizard and selecting the Reporting Services extensions option. This option installs the extensions and enables you to deploy the reports that are included with Microsoft Dynamics AX.

The following topics provide step-by-step instructions.

Checklist: Install the Reporting Services extensions and deploy reports

Before you install the Reporting Services extensions

Install the Reporting Services extensions

Complete the Reporting Services integration

 

Checklist: Install the Reporting Services extensions and deploy reports [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

To install the Microsoft SQL Server Reporting Services extensions and deploy reports, complete the tasks in the following checklist.

Task

More information

Complete the preinstallation tasks:

  1. Verify that you have the permissions that are required to install the Reporting Services extensions.
  2. Install prerequisites.
  3. Configure the Reporting Services instance.

Before you install the Reporting Services extensions

Install the Reporting Services extensions.

Install the Reporting Services extensions

Complete the Reporting Services integration. The directions vary, depending on whether you are running Reporting Services in native mode or SharePoint integrated mode.

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.

If you are running Reporting Services in native mode, complete the following procedures:

  1. Deploy the default reports that are included with Microsoft Dynamics AX, if you did not already deploy the reports when you installed the Reporting Services extensions.
  2. Assign users to the DynamicsAXBrowser role on the Report Manager site.

If you are running Reporting Services in SharePoint integrated mode, complete the following procedures:

  1. Create a document library to store reports.
  2. Deploy the default reports that are included with Microsoft Dynamics AX.
  3. Grant users permission to view reports in SharePoint.

Complete the Reporting Services integration

Top of Form

 

Before you install the Reporting Services extensions [AX 2012]

4 out of 4 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Before you install the Microsoft SQL Server Reporting Services extensions, you must complete the following procedures.

Verify that you have the required permissions to install the Reporting Services extensions


To install the Reporting Services extensions, you must have the required permissions. For more information, see Verify that you have the required permissions for installation.

Assign system service accounts to the appropriate Active Directory groups


Identify which accounts are used for the following purposes:

  • The account used to run the Microsoft Dynamics AX Application Object Server (AOS)
  • The account used as the Business Connector proxy

Assign the accounts listed above to the following Active Directory groups on the domain server:

  • Windows Authorization Access group
  • Pre-Windows 2000 Compatibility Access group

Install prerequisites


On the computer where Reporting Services is installed, or where you plan to install Reporting Services, run the prerequisite validation utility to verify that system requirements have been met. For information about how to run the prerequisite validation utility, see Check prerequisites.

For more information about the hardware and software requirements for Microsoft Dynamics AX, see the system requirements.

Configure Reporting Services in native mode


If you installed Reporting Services in native mode, you must complete the following procedures to configure the Reporting Services instance.

Configure the Reporting Services instance by using the Reporting Services Configuration Manager tool

Use the following procedure to configure the Reporting Services instance.

Note

If you installed the Reporting Services instance in its default configuration, Reporting Services is already configured for you. However, we recommend that you complete this procedure to verify that the options are configured correctly.

  • Click Start > All Programs > Microsoft SQL Server > Configuration Tools > Reporting Services Configuration Manager to open Reporting Services Configuration Manager.
  • Connect to your Reporting Services instance.
  • Configure the options that are described in the following table. For detailed information about each option, see the SQL Server documentation.

Click this option…

To do this…

[ServerName]\[InstanceName]

Verify that the Reporting Services instance is running. If it is not running, click Start.

Service Account

The action that you should take depends on the configuration mode that you selected when you installed the Reporting Services instance.

  • If you installed the default configuration for native mode, no action is required. The service account is set to the account that you specified when you installed the Reporting Services instance.
  • If you installed but did not configure the report server, select the Network Service built-in account.

Note

When you install the Reporting Services extensions, the Business Connector proxy account is automatically assigned as the service account for the Reporting Services instance.

Web Service URL

Create a virtual directory for the Reporting Services web service. By default, the virtual directory is namedReportServer, and the URL is http://%5BSSRSServerName%5D:80/ReportServer.

Database

Create a database for the Reporting Services instance. By default, the database is named ReportServer.

Report Manager URL

Create a virtual directory for Report Manager. Report Manager is the website that reports are published to. By default, the virtual directory is named Reports, and the URL is http://%5BSSRSServerName%5D:80/Reports.

E-mail Settings

This option is not required. For more information, see the SQL Server documentation.

Execution Account

Take no action.

Note

When you install the Reporting Services extensions, the Business Connector proxy account is automatically assigned as the execution account for the Reporting Services instance.

Encryption Keys

This option is not required. For more information, see the SQL Server documentation.

Scale-out Deployment

This option is not required. For more information, see the SQL Server documentation.

  • Click Exit to close Reporting Services Configuration Manager.

Configure the Reporting Services instance for local administration

To administer an instance of the report server locally, you must complete additional configuration steps when you deploy Reporting Services on Windows Server 2008. Windows Server 2008 limits the overuse of elevated permissions by removing administrator permissions when you access applications. If you are a member of the local Administrators group, you run most applications as if you are using the Standard User account because the operating system removes permissions.

Although this practice improves the overall security of your system, it prevents you from using the predefined, built-in role assignments that Reporting Services creates for local administrators. However, by completing additional configuration steps, you can manage the report server’s content and operations by using standard user permissions. For instructions, see How to: Configure a Report Server for Local Administration on Windows Vista and Windows Server 2008 on TechNet.

After you have configured the Reporting Services instance for local administration, verify that you can access the websites that are listed in the following table.

Website

Default URL

Reporting Services web service

http://%5BSSRSServerName%5D:80/ReportServer

Report Manager

http://%5BSSRSServerName%5D:80/Reports

Configure Reporting Services in SharePoint integrated mode


If you installed Reporting Services in SharePoint integrated mode, use one of the following procedures to configure the Reporting Services instance. The procedure that you should use depends on the version of SQL Server that you are using.

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.

Configure Reporting Services 2008 in SharePoint integrated mode

If you are using Reporting Services 2008 or Reporting Services 2008 R2, follow these steps to configure Reporting Services in SharePoint integrated mode.

Note

When you configure Reporting Services, set the Reporting Services service account and execution account to the Business Connector proxy account.

Website

Default URL

Reporting Services web service

http://%5BSSRSServerName%5D:80/ReportServer

SharePoint site

The URL of the SharePoint site varies based on the URL that you provided when you created the site collection. The URL of the SharePoint site may be:

http://%5BSharePointServerName%5D:%5BPortNumber%5D

-or-

http:[SharePointServerName]:[PortNumber]/sites/[SiteName]

Configure Reporting Services 2012 in SharePoint integrated mode

If you are using Reporting Services 2012, follow these steps to configure Reporting Services in SharePoint integrated mode.

Important

When installing Reporting Services 2012 in SharePoint integrated mode, be sure that you do not mark the Reporting Services – Native option on the Feature Selection page of the SQL Server Setup Wizard.

  • If you did not create a site collection when installing and configuring SharePoint, create one now by following the instructions in Create a site collection in SharePoint.
  • Verify that you can access the websites that are listed in the following table.

Website

Default URL

Reporting Services web service

The URL of the Reporting Services web service varies based on the URL that you provided when you created the site collection. The URL of the Reporting Services web service may be:

http://%5BSharePointServerName%5D:%5BPortNumber%5D/_vti_bin/ReportServer

-or-

http:[SharePointServerName]:[PortNumber]/sites/[SiteName]/_vti_bin/ReportServer

SharePoint site

The URL of the SharePoint site varies based on the URL that you provided when you created the site collection. The URL of the SharePoint site may be:

http://%5BSharePointServerName%5D:%5BPortNumber%5D

-or-

http:[SharePointServerName]:[PortNumber]/sites/[SiteName]

 

 

Install the Reporting Services extensions [AX 2012]

0 out of 1 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Use this procedure to install the Microsoft SQL Server Reporting Services extensions. You must complete this procedure on the computer that is running Reporting Services.

This procedure assumes that you are installing the Reporting Services extensions on a dedicated server where no other Microsoft Dynamics AX components are installed. If you are installing other Microsoft Dynamics AX components at the same time, the installation pages vary, depending on the components that you are installing.

  1. Start Microsoft Dynamics AX Setup. Under Install, select Microsoft Dynamics AX components.
  2. Advance through the initial wizard pages.
  3. If the Setup Support files have not yet been installed on this computer, the Select a file location page is displayed. The Setup Support files are required for installation. Provide a file location or accept the default location, and then click Next. On the Ready to install page, click Install.
  4. On the Select installation type page, select Custom installation. Click Next.
  5. On the Select components page, follow these steps:
    1. Select the Reporting Services extensions check box.

      When you select the option to install the Reporting Services extensions, the management utilities are automatically selected for installation, also.

    2. A message is displayed that states that you must complete the code upgrade checklist if you are upgrading. Click OK.
    3. Click Next.
  6. On the Prerequisite Validation page, resolve any errors. For more information about how to resolve prerequisite errors, see Check prerequisites. When no errors remain, click Next.
  7. On the Select a file location page, select the location in which to install 32-bit versions of Microsoft Dynamics AX files, and then click Next.
  8. On the Specify a location for configuration settings page, specify whether you want the Reporting Services extensions to access configuration information from the registry on the local computer or from a shared configuration file. If you select to use a shared configuration file, you must enter the network location of the file. Click Next.
  9. On the Connect to an AOS instance page, enter the name of the computer that is running the Application Object Server (AOS) instance that you want to connect to. You can optionally specify the name of the AOS instance, the TCP/IP port number, and the WSDL port for services. ClickNext.

Note

You can connect to an AOS instance that is part of an AOS cluster. However, do not connect to an AOS instance that serves as the dedicated load balancer for a cluster. For more information about how to integrate Reporting Services with an AOS scale-out deployment, seePlanning considerations for reporting.

  1. On the Specify Business Connector proxy account information page, enter the password for the proxy account that is used by Business Connector. Click Next.
  2. On the Specify a Reporting Services instance page, complete the action listed in the following table.

Field

Action you should take

Notes

Instance name

Select the name of the Reporting Services instance.

If you are using Reporting Services 2012 in SharePoint integrated mode, select@Sharepoint.

SharePoint integrated mode is supported only if you are using Microsoft Dynamics AX 2012 R2.

Site URL

Select the URL of the SharePoint site that has been integrated with Reporting Services.

This field is displayed only when Reporting Services 2012 is running in SharePoint integrated mode.

Deploy reports

Select the check box to deploy the default reports that are included with Microsoft Dynamics AX.

If you do not deploy the reports now, you can deploy them later by using Windows PowerShell commands. For more information, see Deploy the default reports.

This check box is displayed only when Reporting Services is running in native mode.

If Reporting Services is running in SharePoint integrated mode, you must deploy the reports after you complete this wizard. Deploy the reports by using Windows PowerShell commands. For more information, see Deploy the default reports.

  1. Click Next.
  2. On the Prerequisite Validation page, resolve any errors. When no errors remain, click Next.
  3. On the Ready to install page, click Install.

    If you selected to deploy the reports in step 11, a Windows PowerShell window is displayed. This window shows the progress of the deployment, which may take several minutes. Do not close this window. When the reports are deployed, the window closes automatically.

  4. Click Finish to close the Setup wizard.

    If you selected to deploy the reports in step 11, you can close the Setup wizard before the reports have finished being deployed. The deployment of the reports is not affected.

  5. The Microsoft Dynamics AX 2012 Setup Summary Report is displayed. This report lists additional procedures that you must complete to integrate Microsoft Dynamics AX and Reporting Services. For more information about the procedures, see Complete the Reporting Services integration.

 

 

Complete the Reporting Services integration [AX 2012]

1 out of 1 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

To fully integrate Microsoft Dynamics AX and Microsoft SQL Server Reporting Services, you must complete additional configuration procedures. The procedures vary, depending on whether you are running Reporting Services in native mode or SharePoint integrated mode.

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.

If you are running Reporting Services in native mode, complete the following procedures:

  1. Deploy the default reports
  2. Grant users access to reports

If you are running Reporting Services in SharePoint integrated mode, complete the following procedures:

  1. Create a document library to store reports
  2. Deploy the default reports
  3. Grant users access to reports

 

Create a document library to store reports [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: October 8, 2012

Applies To: Microsoft Dynamics AX 2012 R2

If you are using Microsoft Dynamics AX 2012 R2, and if Microsoft SQL Server Reporting Services is running in SharePoint integrated mode, create a document library in SharePoint to store your reports. Complete this procedure before you deploy the default reports that are included with Microsoft Dynamics AX.

Note

This procedure does not apply to you if you are running Reporting Services in native mode.

Create a document library


Create a document library on your SharePoint site to store reports. For information about how to create a document library, see the SharePoint documentation.

After you create the document library, add Reporting Services content types to the library. For more information, see Add Report Server Content Types to a Library (Reporting Services in SharePoint Integrated Mode) in the SQL Server documentation.

Specify the URL of the document library


After you have created the document library, complete the following procedure to specify the URL of the document library in the Report serversform in Microsoft Dynamics AX.

  • Open Microsoft Dynamics AX.
  • Click System administration > Setup > Business intelligence > Reporting Services > Report servers.
  • In the Configuration ID field, enter a name that identifies the Reporting Services instance and the Application Object Server (AOS) instance that you are connecting.
  • In the Description field, enter a brief description to help you identify the Reporting Services instance and the AOS instance that you are connecting.
  • Select the Default configuration check box to make the Reporting Services and AOS instances that are specified in this record the active connection.
  • On the Reporting Server information tab, enter the following information:
    • In the Server name field, enter the name of the server that is running Reporting Services.
    • In the Server instance name field, enter the name of the Reporting Services instance.

Note

If you are using Reporting Services 2012, enter @Sharepoint.

  • Leave the Report Manager URL field blank. This field becomes unavailable when you select the SharePoint integrated mode check box in a later step.
  • In the Web service URL field, enter the URL of the Reporting Services web service.
  • Select the SharePoint integrated mode check box.
  • In the Microsoft Dynamics AX report folder field, enter the URL of the document library that you created to store reports.

    For example, suppose that you have created a document library that is named Reports on a SharePoint site that is named Contoso. In this example, the URL is as follows:

    http://%5BSharePointServerName%5D/sites/Contoso/Reports

  • On the Application Object Server information tab, select the name of the AOS instance.

 

 

 

 

 

Deploy the default reports [AX 2012]

2 out of 2 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Microsoft Dynamics AX includes many default reports that you must deploy. If you did not deploy the reports when you installed the Microsoft SQL Server Reporting Services extensions, you can deploy them by using Windows PowerShell. The following procedures can help you deploy the reports.

Before you begin


Before you can deploy the reports by using Windows PowerShell, you must complete the following tasks:

  • Verify that Windows PowerShell 2.0 is installed on the computer that you are using.
  • Verify that your Windows domain account is a member of the Administrators group on the server that is running Reporting Services.

Note

If your Windows domain account is assigned to a group that is a member of the Administrators group, it may take some time to validate that you are a member of the Administrators group. If you experience a delay when you deploy reports, consider adding your Windows domain account directly to the Administrators group.

  • If Reporting Services is running in native mode, verify that you are assigned to the System Administrator role on the Report Manager website.
  • If Reporting Services is running in SharePoint integrated mode, verify that you have been granted Contribute permission to the document library where you plan to deploy the reports.

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.

Open Windows PowerShell and view a list of reports


Complete the following procedure to open Windows PowerShell and view a list of the reports that are included with Microsoft Dynamics AX.

  1. Open Windows PowerShell as an administrator by following these steps:
    1. Click Start > Administrative Tools.
    2. Right-click the Microsoft Dynamics AX 2012 Management Shell option.
    3. Click Run as administrator.
  2. Retrieve a list of the reports that are included with Microsoft Dynamics AX, and store the list in a local variable by entering the following command:

    PowerShell

    $reports
    = GetAXReport ReportName *

    For more information about the Get-AXReport command, see Get-AXReport.

  3. View the list of reports by entering the following command:

    PowerShell

    $reports

Filter the list of reports


In the previous procedure, you displayed a list of all the reports that are included with Microsoft Dynamics AX. To modify and filter the list, you can use the following commands:

  • To modify the list so that only the Name and ChangedDate fields are displayed, enter the following command:

    PowerShell

    $reports | SelectObject Name,ChangedDate

  • To filter the list so that only specific reports are listed, enter keywords or report names. For example, to filter the list so that only reports that contain the word CustTrans are listed, enter the following command:

    PowerShell

    $reports | SelectObject Name,ChangedDate | Where { $_.Name -like
    „CustTrans*” }

Deploy the reports


After you have retrieved a list of reports, you can deploy the reports. The Publish-AXReport command is used to deploy the reports. The following examples show how to use this command. For more information, see Publish-AXReport.

  • To deploy a specific report, enter the name of the report. For example, to deploy the CustTransList report, enter the following command:

    PowerShell

    PublishAXReport ReportName CustTransList

  • To deploy two or more specific reports, enter the names of the reports. For example, to deploy the CustTransList and CustTransOpenPerDate reports, enter the following command:

    PowerShell

    PublishAXReport ReportName CustTransList, CustTransOpenPerDate

  • To deploy all reports, enter the following command:

    PowerShell

    PublishAXReport –ReportName *

     

     

     

     

     

Grant users access to reports [AX 2012]

Other Versions


This topic has not yet been rated – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

This topic explains how to give users access to reports. Two procedures are described in this topic. The procedure that you should use depends on whether you are running Microsoft SQL Server Reporting Services in native mode or SharePoint integrated mode.

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.

Assign users to the DynamicsAXBrowser role on the Report Manager site


If you are running Reporting Services in native mode, you must assign users or groups to the DynamicsAXBrowser role on the Report Manager site. The following procedure explains how to complete this task.

  1. Open the Report Manager website for the Reporting Services instance. By default, the URL is http://%5BSSRSServerName%5D:80/Reports.
  2. Click the DynamicsAX folder.
  3. Click Folder Settings.
  4. Click Security.
  5. Click New Role Assignment.
  6. Enter the Active Directory user name or group to assign to the DynamicsAXBrowser role.
  7. Select the DynamicsAXBrowser role.
  8. Click OK.

Grant users permission to view reports in SharePoint


If you are running Reporting Services in SharePoint integrated mode, you must grant users permission to view reports in SharePoint. To grant this permission, grant users Read permission to the document library that stores the reports. Alternatively, if the document library inherits permissions from the site, you can grant users Read permission to the site. The following procedure describes how to grant users Read permission to the site.

Important

If the SharePoint site is configured for claims-based authentication, you must also grant the following accounts Read permission to the document library or site:

  • The account that is used as the Business Connector proxy
  • The account that is used to run the Microsoft Dynamics AX Application Object Server (AOS) service.
  1. Open your browser and navigate to the SharePoint site that contains the document library that stores the reports.
  2. Click Site Actions > Site Permissions.
  3. Click Grant Permissions. The Grant Permissions window is displayed.
  4. In the Users/Groups field, enter the Active Directory names of the users or groups that you want to view reports.
  5. In the Grant Permissions area, select the Grant users permission directly option.
  6. Select the Read check box.

Note

If you want users of Enterprise Portal for Microsoft Dynamics AX to be able to filter reports by using a custom parameter value, select theDesign check box. For more information about the permissions that are required to use Enterprise Portal, see Enable users to access Enterprise Portal.

  1. Click OK.

Deploy language-specific versions of a report [AX 2012]

0 out of 1 rated this helpful – Rate this topic

Updated: September 5, 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Typically, when you deploy a report, one version of the report is deployed. This version can then be rendered automatically in every language that is supported by Microsoft Dynamics AX. However, you can configure Microsoft Dynamics AX so that language-specific versions of a report are deployed. A language-specific version of a report is sometimes referred to as a static version.

A language-specific version of a report is rendered more quickly for the following reasons:

  • Labels are not resolved at run time.

Note

Labels are resolved when you deploy the report. Therefore, if you deploy a report and later change a label, the updated label is not displayed on the report. In this scenario, you must redeploy the report to view the updated label.

  • Columns are not collapsed at run time.

Note

A language-specific version of a report is designed to render quickly. If you are a developer designing a language-specific version of a report, we recommend that you do not include drill-through links to other reports on the report that you are designing.

When language-specific versions of reports are deployed


The following table explains when and how language-specific versions of reports are deployed.

Event

Are language-specific versions deployed?

You select the Deploy reports check box when you run the Microsoft Dynamics AX Setup wizard.

No.

While you are completing the Initialization Checklist or the Partition Initialization Checklist, you set up system parameters in the System parameters form.

Note

If you are using Microsoft Dynamics AX 2012 or Microsoft Dynamics AX 2012 Feature Pack, you set up system parameters when you are completing theInitialization Checklist. If you are using Microsoft Dynamics AX 2012 R2, you set up system parameters when you are completing the Partition Initialization Checklist.

No.

However, at this point, the Report deployment settings form is populated with a list of reports for which we recommend that you deploy language-specific versions. This list includes the following reports:

  • FreeTextInvoice
  • ProdPickList
  • ProdRouteCard
  • PurchPackingSlip
  • PurchPurchaseOrder
  • PurchReceiptsList
  • SalesConfirm
  • SalesInvoice
  • SalesPackingSlip
  • SalesQuotation
  • SalesQuotationConfirmation
  • VendInvoiceDocument
  • WMSBillOfLading
  • WMSPickingList_OrderPick

The next time that you deploy or redeploy these reports, language-specific versions are deployed.

You redeploy all reports by using Windows PowerShell.

Yes.

Language-specific versions are deployed for each report for which the Use static report design check box is selected in the Report deployment settingsform.

Deploy language-specific versions of a report


To deploy language-specific versions of a report, complete the following procedure.

  1. Open Microsoft Dynamics AX.
  2. Click System administration > Setup > Business intelligence > Reporting Services > Report deployment settings.
  3. Click New.
  4. In the Report name field, select the report for which you want to deploy language-specific versions.
  5. In the Report design name field, select a report design.
  6. Select the Use static report design check box.
  7. Close the Report deployment settings form.
  8. Deploy the report by following the instructions in Deploy the default reports. A language-specific version of the report is deployed for each language that is enabled in your Microsoft Dynamics AX installation.

    If Reporting Services is running in native mode, the language-specific versions are deployed to the DynamicsAX\StaticReports folder on the Report Manager website.

    If Reporting Services is running in SharePoint integrated mode, the language-specific versions are deployed to the StaticReports folder in the document library that stores all of your Microsoft Dynamics AX reports.

How to: Deploy Reports to a Report Server [AX 2012]

 

 

0 out of 2 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

This topic describes how to deploy reports to a report server from Microsoft Dynamics AX and from Microsoft Visual Studio.

SQL Server Reporting Services is the reporting platform for Microsoft Dynamics AX. Reporting Services enables developers to create and publish traditional, paper-based reports, and interactive Web-based reports. When you deploy a report, the report design, data sources, and associated business logic assemblies are deployed to the SQL Server Reporting Services server.

Deploying reports to Reporting Services does the following:

  • Uploads the Report Definition Language (RDL) file, which is the report, to the Reporting Services server
  • Copies the business logic assemblies to the Reporting Services server
  • Ensures that the cross referenced report and business logic assemblies are present to have a valid report deployed

To deploy an Microsoft Dynamics AX reporting project in Visual Studio, you must start Visual Studio with administrative privileges or start Microsoft Dynamics AX and the Developer Workspace with administrative privileges. To do this, you must right-click on the icon for Visual Studio or Microsoft Dynamics AX and then choose Run as administrator. The following table describes the options to deploy reports:

Deploy option

Description

Microsoft Dynamics AX

Reports can be deployed individually from a developer workspace in Microsoft Dynamics AX.

In the AOT, expand the SSRS Reports node, expand the Reports node, right-click the report, and then click Deploy Element.

The reports are deployed for all the translated languages.

Microsoft Visual Studio

Reports can be deployed individually from Visual Studio.

In Solution Explorer, right-click the reporting project that contains the reports that you want to deploy, and then clickDeploy.

The reports are deployed for the neutral (invariant) language only.

Microsoft PowerShell

Used to deploy the default reports that are provided with Microsoft Dynamics AX.

For information about how to deploy from PowerShell, see Deploy the default reports.

For more information about deployment, see Report Integration and Customization Overview. For information about the reporting install, see Install business intelligence components.

To deploy reports from Microsoft Dynamics AX

  1. In the AOT, expand the SSRS Reports node.
  2. Expand the Reports node.
  3. Right-click the report that you want to deploy, and then click Deploy Element.

To deploy reports from Microsoft Visual Studio

  • In Solution Explorer, right-click the reporting project that contains the reports that you want to deploy, and then click Deploy. Reports are deployed for the neutral (invariant) language only.

 

Install multiple instances of Reporting Services on the same computer (for use with Microsoft Dynamics AX) [AX 2012]

2 out of 2 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

You can install multiple instances of Microsoft SQL Server Reporting Services on the same computer. In this kind of deployment environment, each instance of Reporting Services is connected to an independent Microsoft Dynamics AX installation. You may want to install multiple instances of Reporting Services on the same computer for the following reasons:

  • To support development and production installations of Microsoft Dynamics AX

    For example, in the following sample diagram, assume that AOS instance 1 is a development installation of Microsoft Dynamics AX, and AOS instance 2 is the production installation of Microsoft Dynamics AX.

  • To support multiple production installations of Microsoft Dynamics AX

    For example, if you are a Microsoft Dynamics AX solution provider, you may have to support multiple production installations of Microsoft Dynamics AX. For this scenario, assume that AOS instance 1 (in the sample diagram) is a production installation of Microsoft Dynamics AX for one client, Northwind Traders. Assume that AOS instance 2 is a production installation of Microsoft Dynamics AX for another client, Contoso Pharmaceuticals.


Supported versions of Reporting Services


To install multiple instances of Reporting Services on the same computer, you must use one of the following versions of Reporting Services:

  • Reporting Services 2008 in native mode
  • Reporting Services 2008 in SharePoint integrated mode
  • Reporting Services 2008 R2 in native mode
  • Reporting Services 2008 R2 in SharePoint integrated mode
  • Reporting Services 2012 in native mode

Note

You cannot install multiple instances of Reporting Services 2012—that run in SharePoint integrated mode—on the same computer.

For more information about the service packs and updates that must be installed with each version of Reporting Services, see the Microsoft Dynamics AX system requirements.

How to install multiple instances of Reporting Services on the same computer


To set up an environment that has multiple Reporting Services instances on the same computer, follow these steps.

  1. Configure the initial instance of Reporting Services and integrate it with Microsoft Dynamics AX. For information about the tasks that you must complete, see Checklist: Install the Reporting Services extensions and deploy reports.
  2. Configure the next instance of Reporting Services and integrate it with Microsoft Dynamics AX. For information about the tasks that you must complete, see the following topics:

    Install the new Reporting Services instance

    Configure the new Reporting Services instance

    Modify Reporting Services configuration files

    Restart the new Reporting Services instance

    Create a new Microsoft Dynamics AX configuration

    Connect Microsoft Dynamics AX to the new Reporting Services instance

    Deploy reports for the new Reporting Services instance

    Revert to the original Microsoft Dynamics AX configuration

  3. Repeat step 2 for each additional instance of Reporting Services.

Install the new Reporting Services instance [AX 2012]

3 out of 15 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

You can install multiple instances of Microsoft SQL Server Reporting Services on the same computer. Each instance will have its own report server database, configuration files, and virtual directories. One instance can be the default instance. All other instances must be named instances. A server can run multiple instances of Reporting Services at the same time, and each instance runs independently of the other instances.

Install an additional Reporting Services instance on the computer that is running Reporting Services. To install additional instances, you must run the SQL Server Setup Wizard one time for each report server instance that you want to install. You cannot install multiple instances at the same time.

This topic assumes that the new instance of Reporting Services that you install meets the version requirements that are listed in Install multiple instances of Reporting Services on the same computer (for use with Microsoft Dynamics AX).

Installing a default instance


The first time that you run the SQL Server Setup Wizard, you have the option of installing the first report server instance as a default installation if the computer meets the requirements. A default installation is one that uses all default values. This results in a report server that is ready to use when Setup is completed. You can have only one default instance of Reporting Services on a single SQL Server installation.

Installing a named instance


When you install multiple report server instances on the same computer, each additional instance must be installed as a named instance. To install an additional, named instance, you must run the SQL Server Setup Wizard again. When you run Setup, keep the following points in mind:

  • On the Installation Type page, select the option to perform a new installation. This option lets you install an additional instance of Reporting Services.

    The name of the option varies, depending on the version of SQL Server that you are using. The following picture shows the Installation Type page of the SQL Server 2012 Setup Wizard. In this version, the option is named Perform a new installation of SQL Server 2012.


  • On the Instance Configuration page, enter a name for the new instance of Reporting Services.

    The following picture shows the Instance Configuration page of the SQL Server 2012 Setup Wizard.


  • On the Reporting Services Configuration page, select the option to install—but not configure—the report server.

    The name of the option varies, depending on the version of SQL Server that you are using. The following picture shows the Reporting Services Configuration page of the SQL Server 2012 Setup Wizard. In this example, Reporting Services is running in native mode, and the option is named Install only.


For more information about how to run the SQL Server Setup Wizard, see the SQL Server documentation on TechNet or MSDN for the version that you are using.

Configure the new Reporting Services instance [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Complete the following procedures to configure the new instance of Microsoft SQL Server Reporting Services. This topic assumes that the new instance of Reporting Services meets the version requirements that are listed in Install multiple instances of Reporting Services on the same computer (for use with Microsoft Dynamics AX).

Configure the Reporting Services instance by using the Reporting Services Configuration Manager tool


Use the following procedure to configure the new Reporting Services instance.

  • Click Start > All Programs > Microsoft SQL Server > Configuration Tools > Reporting Services Configuration Manager to open Reporting Services Configuration Manager.
  • Connect to the new Reporting Services instance.
  • Configure the options that are described in the following table. For detailed information about each option, see the SQL Server documentation.

Click this option…

To do this…

[ServerName]\[InstanceName]

Verify that the Reporting Services instance is running. If it is not running, click Start.

Service Account

Enter the name and password of the account that is used as the Business Connector proxy.

Note

To view the account that is used as the Business Connector proxy, open Microsoft Dynamics AX and then clickSystem administration > Setup > System > System service accounts.

Web Service URL

Create a virtual directory for the Reporting Services web service. By default, the virtual directory is namedReportServer, and the URL is http://%5BSSRSServerName%5D:80/ReportServer_%5BSSRSInstanceName%5D.

Database

Create a database for the Reporting Services instance.

Report Manager URL

  • If Reporting Services is running in native mode, create a virtual directory for Report Manager. Report Manager is the website that reports are published to. By default, the virtual directory is named Reports, and the URL is http://%5BSSRSServerName%5D:80/Reports_%5BSSRSInstanceName%5D.
  • If Reporting Services is running in SharePoint integrated mode, skip this page. Report Manager is not used when Reporting Services is running in SharePoint integrated mode.

E-mail Settings

This option is not required. For more information, see the SQL Server documentation.

Execution Account

Enter the name and password of the account that is used as the Business Connector proxy.

Encryption Keys

This option is not required. For more information, see the SQL Server documentation.

Scale-out Deployment

This option is not required. For more information, see the SQL Server documentation.

  • Click Exit to close Reporting Services Configuration Manager.

Configure the Reporting Services instance for local administration


To administer an instance of the report server locally, you must complete additional configuration steps when you deploy Reporting Services on Windows Server 2008. Windows Server 2008 limits the overuse of elevated permissions by removing administrator permissions when you access applications. If you are a member of the local Administrators group, you run most applications as if you are using the Standard User account because the operating system removes permissions.

Although this practice improves the overall security of your system, it prevents you from using the predefined, built-in role assignments that Reporting Services creates for local administrators. However, by completing additional configuration steps, you can manage the report server’s content and operations by using standard user permissions. For instructions, see How to: Configure a Report Server for Local Administration on Windows Vista and Windows Server 2008 on TechNet.

After you have configured the Reporting Services instance for local administration, verify that you can access the sites that are listed in the following table.

Website

Default URL

Reporting Services web service

http://%5BSSRSServerName%5D:80/ReportServer_%5BSSRSInstanceName%5D

Report Manager

Note

If Reporting Services is running in SharePoint integrated mode, you do not have to verify that you can access this website. Report Manager is not used when Reporting Services is running in SharePoint integrated mode.

http://%5BSSRSServerName%5D:80/Reports_%5BSSRSInstanceName%5D

Modify Reporting Services configuration files [AX 2012]

6 out of 7 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Complete the following procedures to modify the configuration files that are used by the new instance of Microsoft SQL Server Reporting Services.

Tip

We recommend that you make a backup of each configuration file before you modify it.

Modify the Report Manager Web.config file


Complete the following procedure to modify the Web.config file that is used by Report Manager.

  • Open the Web.config file.
    • If you are using SQL Server 2008, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS10.[SSRSInstanceName]\Reporting Services\ReportManager.
    • If you are using SQL Server 2008 R2, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS10_50.[SSRSInstanceName]\Reporting Services\ReportManager.
    • If you are using SQL Server 2012, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS11.[SSRSInstanceName]\Reporting Services\ReportManager.
  • Search for httpRuntime.
  • Add maxRequestLength=”100000″ to the line of code so that the line looks like this:
  • <httpRuntime maxRequestLength=”100000″ executionTimeout=”90000″ />

Modify the report server RsReportServer.config file


Complete the following procedure to modify the RsReportServer.config file.

  • Open the RsReportServer.config file.
    • If you are using SQL Server 2008, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS10.[SSRSInstanceName]\Reporting Services\ReportServer.
    • If you are using SQL Server 2008 R2, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS10_50.[SSRSInstanceName]\Reporting Services\ReportServer.
    • If you are using SQL Server 2012, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS11.[SSRSInstanceName]\Reporting Services\ReportServer.
  • Find the <AuthenticationTypes> element.
  • In the <AuthenticationTypes> element, remove the following line of code if it is present:
  • <RSWindowsNegotiate>
  • Find the <Service> element.
  • In the <Service> element, add the following line of code:
  • <IsRdceEnabled>True</IsRdceEnabled>
  • Find the <Data> element.
  • In the <Data> element, add the following lines of code. If you are using Microsoft Dynamics AX 2012, use 6.0.0.0 as the version number. If you are using Microsoft Dynamics AX 2012 R2, use 6.2.0.0 as the version number.
  • <Extension Name=”AXQUERY” Type=”Microsoft.Dynamics.Framework.Reports.AxQueryConnection,Microsoft.Dynamics.Framework.ReportsExtensions, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″/>
  • <Extension Name=”AXDATAMETHOD” Type=”Microsoft.Dynamics.Framework.Reports.AxDataMethodConnection,Microsoft.Dynamics.Framework.ReportsExtensions, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″/>
  • <Extension Name=”AXREPORTDATAPROVIDER” Type=”Microsoft.Dynamics.Framework.Reports.AxReportProviderConnection,Microsoft.Dynamics.Framework.ReportsExtensions, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″/>
  • <Extension Name=”AXADOMD” Type=”Microsoft.Dynamics.Framework.Reports.AxAdomdConnection,Microsoft.Dynamics.Framework.ReportsExtensions, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″/>
  • <Extension Name=”AXENUMDATAPROVIDER” Type=”Microsoft.Dynamics.Framework.Reports.EnumProviderConnection,Microsoft.Dynamics.Framework.ReportsExtensions, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″/>
  • Find the <Extensions> element.
  • In the <Extensions> element, add the following lines of code. If you are using Microsoft Dynamics AX 2012, use 6.0.0.0 as the version number. If you are using Microsoft Dynamics AX 2012 R2, use 6.2.0.0 as the version number.
  • <ReportDefinitionCustomization>
  • <Extension Name=”AXRDCE” Type=”Microsoft.Dynamics.Framework.Reports.AxRdce.CustomizationExtension,Microsoft.Dynamics.Framework.ReportsExtensions, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″/>
  • </ReportDefinitionCustomization>

Modify the report server RsSrvPolicy.config file


Complete the following procedure to modify the RsSrvPolicy.config file.

  • Open the RsSrvPolicy.config file.
    • If you are using SQL Server 2008, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS10.[SSRSInstanceName]\Reporting Services\ReportServer.
    • If you are using SQL Server 2008 R2, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS10_50.[SSRSInstanceName]\Reporting Services\ReportServer.
    • If you are using SQL Server 2012, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS11.[SSRSInstanceName]\Reporting Services\ReportServer.
  • Find the <SecurityClasses> element.
  • In the <SecurityClasses> element, add the following line of code. If you are using Microsoft Dynamics AX 2012, use 6.0.0.0 as the version number. If you are using Microsoft Dynamics AX 2012 R2, use 6.2.0.0 as the version number.
  • <SecurityClass Name=”AxSessionPermission” Description=”Microsoft.Dynamics.Framework.Reports.AxSessionPermission, Microsoft.Dynamics.Framework.Reports, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ />
  • Find the <NamedPermissionSets> element.
  • In the <NamedPermissionSets> element, add the following lines of code:
  • <PermissionSet class=”NamedPermissionSet” version=”1″ Name=”AxSessionPermissionSet”>
  • <IPermission class=”AxSessionPermission” version=”1″ Unrestricted=”true” />
  • <IPermission class=”SecurityPermission” version=”1″ Flags=”Assertion” />
  • </PermissionSet>
  • Find the <CodeGroup class=”FirstMatchCodeGroup” version=”1″ PermissionSetName=”Execution” Description=”This code group grants MyComputer code Execution permission. „> element.
  • Directly after the <CodeGroup class=”FirstMatchCodeGroup” version=”1″ PermissionSetName=”Execution” Description=”This code group grants MyComputer code Execution permission. „> element, you’ll find the <IMembershipCondition> element. Add the following lines of code after the <IMembershipCondition> element:
  • <CodeGroup class=”UnionCodeGroup” version=”1″ PermissionSetName=”FullTrust” Name=”AX_Reports_Strong_Name” Description=”This code group grants Dynamics AX Reports code full trust. „>
  • <IMembershipCondition class=”StrongNameMembershipCondition” version=”1″ PublicKeyBlob=”0024000004800000940000000602000000240000525341310004000001000100B5FC90E7027F67871E773A8FDE8938C81DD402BA65B9201D60593E96C492651E889CC13F1415EBB53FAC1131AE0BD333C5EE6021672D9718EA31A8AEBD0DA0072F25D87DBA6FC90FFD598ED4DA35E44C398C454307E8E33B8426143DAEC9F596836F97C8F74750E5975C64E2189F45DEF46B2A2B1247ADC3652BF5C308055DA9″ />
  • </CodeGroup>

Modify the report server Web.config file


Complete the following procedure to modify the Web.config file that is used by the report server instance.

  • Open the Web.config file.
    • If you are using SQL Server 2008, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS10.[SSRSInstanceName]\Reporting Services\ReportServer.
    • If you are using SQL Server 2008 R2, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS10_50.[SSRSInstanceName]\Reporting Services\ReportServer.
    • If you are using SQL Server 2012, the default location of this file is: \Program Files\Microsoft SQL Server\MSRS11.[SSRSInstanceName]\Reporting Services\ReportServer.
  • Find the <httpModules> element.
  • In the <httpModules> element, add the following line of code. If you are using Microsoft Dynamics AX 2012, use 6.0.0.0 as the version number. If you are using Microsoft Dynamics AX 2012 R2, use 6.2.0.0 as the version number.
  • <add name=”AxReportsHttpModule” type=”Microsoft.Dynamics.Framework.Reports.AxReportsHttpModule,Microsoft.Dynamics.Framework.ReportsExtensions, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ />
  • Search for httpRuntime.
  • Add maxRequestLength=”100000″ to the line of code so that the line looks like this:
  • <httpRuntime maxRequestLength=”100000″ executionTimeout=”90000″ />
  • Find the <system.web> element.
  • In the <system.web> element, add the following line of code if it does not already exist:

    <hostingEnvironment shadowCopyBinAssemblies=”true” />

Restart the new Reporting Services instance [AX 2012]

0 out of 1 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Complete the following procedure to restart the new instance of Microsoft SQL Server Reporting Services.

  1. Click Start > Administrative Tools > Services to open the Services management console.
  2. Right-click the SQL Server Reporting Services ([InstanceName]) service, and then click Restart.

Create a new Microsoft Dynamics AX configuration [AX 2012]

1 out of 1 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Complete the following procedure to create a new configuration of Microsoft Dynamics AX and to export the configuration settings to a file.

  • Click Start > Administrative Tools > Microsoft Dynamics AX 2012 Configuration to open the Microsoft Dynamics AX Configuration Utility.
  • Click Manage > Create configuration. The Create Configuration window is displayed.
  • Enter a name for the configuration, and then click OK. The configuration is created.
  • Click the Connection tab.
  • Verify that the server name, instance name, and port information for the Application Object Server (AOS) are correct.
  • Click Refresh to update the configuration.
  • Click Manage > Export configuration to file. The Export Configuration window is displayed.
  • Save the configuration to a file by following these steps:
    • Name the file Microsoft.Dynamics.AX.ReportConfiguration.axc.
    • Save the file to the appropriate location, depending on the version of SQL Server that you are using.
      • If you are using SQL Server 2008, save the file to: \Program Files\Microsoft SQL Server\MSRS10.[SSRSInstanceName]\Reporting Services\ReportServer\bin.
      • If you are using SQL Server 2008 R2, save the file to: \Program Files\Microsoft SQL Server\MSRS10_50.[SSRSInstanceName]\Reporting Services\ReportServer\bin.
      • If you are using SQL Server 2012, save the file to: \Program Files\Microsoft SQL Server\MSRS11.[SSRSInstanceName]\Reporting Services\ReportServer\bin.

Connect Microsoft Dynamics AX to the new Reporting Services instance [AX 2012]

1 out of 1 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Complete the following procedure to connect an instance of Microsoft Dynamics AX Application Object Server (AOS) to the new instance of Microsoft SQL Server Reporting Services. This topic assumes that the new instance of Reporting Services meets the version requirements that are listed in Install multiple instances of Reporting Services on the same computer (for use with Microsoft Dynamics AX).

  • Open Microsoft Dynamics AX.
  • Click System administration > Setup > Business intelligence > Reporting Services > Report servers.
  • In the Configuration ID field, enter a name that identifies the Reporting Services instance and the AOS instance that you are connecting.
  • In the Description field, enter a brief description to help you identify the Reporting Services instance and the AOS instance that you are connecting.
  • Select the Default configuration check box.
  • On the Reporting Server information tab, complete the actions that are listed in the following table.

Field

Action you should take

Server name

Enter the name of the server that is running Reporting Services.

Server instance name

Enter the name of the new Reporting Services instance.

Report Manager URL

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.

Web service URL

Enter the URL of the Reporting Services web service. The URL is typically http://%5BSSRSServerName%5D/ReportServer_%5BSSRSInstanceName%5D.

SharePoint integrated mode

Select this check box if Reporting Services is running in SharePoint integrated mode.

Note

This control is available only if Microsoft Dynamics AX 2012 R2 is installed.

Microsoft Dynamics AX report folder

  • If Reporting Services is running in native mode, enter a name for a report folder. The report folder will be created for you on the Report Manager website.
  • If Reporting Services is running in SharePoint integrated mode, enter the URL of a document library. The document library will be created for you on the SharePoint site that is integrated with Reporting Services. For example, suppose you want to create a document library that is named Reports on a SharePoint site that is named Contoso. In this case, you would enter the following URL:

    http://%5BSharePointServerName%5D/sites/Contoso/Reports

  • On the Application Object Server information tab, select the name of the AOS instance.
  • Click Create report folder to create the report folder or document library that is specified in the Microsoft Dynamics AX report folder field.
  • Click Validate settings to verify that the information that you entered in this form is correct, and to verify that the report folder or document library has been created.

 

 

 

 

Deploy reports for the new Reporting Services instance [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Microsoft Dynamics AX includes many default reports that you must deploy. You can deploy these reports by using Windows PowerShell. The following procedures can help you deploy the reports.

Before you begin


Before you can deploy the reports by using Windows PowerShell, you must complete the following tasks:

  • Verify that Windows PowerShell 2.0 is installed on the computer that you are using.
  • Verify that your Windows domain account is a member of the Administrators group on the server that is running Microsoft SQL Server Reporting Services.

Note

If your Windows domain account is assigned to a group that is a member of the Administrators group, it may take some time to validate that you are a member of the Administrators group. If you experience a delay when you deploy reports, consider adding your Windows domain account directly to the Administrators group.

  • If Reporting Services is running in native mode, verify that you are assigned to the System Administrator role on the Report Manager website.
  • If Reporting Services is running in SharePoint integrated mode, verify that you have been granted Contribute permission to the document library where you plan to deploy the reports.

Note

SharePoint integrated mode is supported if you are using Microsoft Dynamics AX 2012 R2.

Open Windows PowerShell and view a list of reports


Complete the following procedure to open Windows PowerShell and view a list of the reports that are included with Microsoft Dynamics AX.

  1. Open Windows PowerShell as an administrator by following these steps.
    1. Click Start > Administrative Tools.
    2. Right-click the Microsoft Dynamics AX 2012 Management Shell option.
    3. Click Run as administrator.
  2. Retrieve a list of the reports that are included with Microsoft Dynamics AX, and store the list in a local variable by entering the following command:

    PowerShell

    $reports
    = GetAXReport ReportName *

    For more information about the Get-AXReport command, see Get-AXReport.

  3. View the list of reports by entering the following command:

    PowerShell

    $reports

Filter the list of reports


In the previous procedure, you displayed a list of all the reports that are included with Microsoft Dynamics AX. To modify and filter the list, you can use the following commands.

  • To modify the list so that only the Name and ChangedDate fields are displayed, enter the following command:

    PowerShell

    $reports | SelectObject Name,ChangedDate

  • To filter the list so that only specific reports are listed, enter keywords or report names. For example, to filter the list so that only reports that contain the word CustTrans are listed, enter the following command:

    PowerShell

    $reports | SelectObject Name,ChangedDate | Where { $_.Name -like
    „CustTrans*” }

Deploy the reports


After you have retrieved a list of reports, you can deploy the reports. The Publish-AXReport command is used to deploy the reports. The following examples show how to use this command. For more information, see Publish-AXReport.

Note

In the following examples, SSRSConfigID refers to a configuration ID that was defined in Microsoft Dynamics AX. To view these configuration IDs, open Microsoft Dynamics AX and then open the Report servers form. (Click System administration > Setup > Business intelligence >Reporting Services > Report servers.) To deploy reports to the new Reporting Services instance, enter the configuration ID that is associated with that instance.

  • To deploy a specific report, enter the name of the report. For example, to deploy the CustTransList report, enter the following command:

    PowerShell

    PublishAXReport –Id SSRSConfigID ReportName CustTransList

  • To deploy two or more specific reports, enter the names of the reports. For example, to deploy the CustTransList and CustTransOpenPerDate reports, enter the following command:

    PowerShell

    PublishAXReport –Id SSRSConfigID ReportName CustTransList, CustTransOpenPerDate

  • To deploy all reports, enter the following command:

    PowerShell

    PublishAXReport –Id SSRSConfigID –ReportName *

     

Revert to the original Microsoft Dynamics AX configuration

2 out of 2 rated this helpful – Rate this topic

Updated: November 1, 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Delete the Microsoft Dynamics AX configuration that you created earlier (in the Create a new Microsoft Dynamics AX configuration procedure) and revert to the original configuration. Complete the following procedure to delete the configuration.

  1. Click Start > Administrative Tools > Microsoft Dynamics AX 2012 Configuration to open the Microsoft Dynamics AX Configuration Utility.
  2. In the Configuration field, make sure that the configuration that you created earlier (in the Create a new Microsoft Dynamics AX configurationprocedure) is selected.
  3. Click Manage > Delete configuration.
  4. In the Configuration field, make sure that the original configuration that you used is selected.
  5. Click OK to close the Microsoft Dynamics AX Configuration Utility.

Upgrading Reports [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: November 7, 2011

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

The following topics provide guidance to upgrade reports in Microsoft Dynamics AX.

Report Upgrade

Report Project Upgrade

Guidance when Upgrading Reports

Mapping Microsoft Dynamics AX 2009 Reports to the Microsoft Dynamics AX 2012 Version

Deprecated Microsoft Dynamics AX 2009 Reports in Microsoft Dynamics AX 2012

Report Upgrade [AX 2012]

1 out of 1 rated this helpful – Rate this topic

Updated: August 2, 2011

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic provides guidance to convert X++ reports, Microsoft Visual Studio tools for Microsoft Dynamics AX reports, and troubleshooting tips for converted reports. To use the reports you created or customized in Microsoft Dynamics AX 2009, they must be converted for Microsoft Dynamics AX 2012. The upgrade readiness checklist checks the reports that will need to be upgraded for the current release. For more information, see Upgrade overview and preparation.

Converting reports


The following sections provide the suggested options to upgrade reports from Microsoft Dynamics AX 2009 to Microsoft Dynamics AX 2012. The options are provided for reports that were originally created with:

  • Morphx Reporting tool
  • Visual Studio tools for Microsoft Dynamics AX 2009

X++ reports

The X++ reporting framework is being deprecated in Microsoft Dynamics AX 2012. Reports that you created or customized using the Morphx Reporting tool will be copied to the Microsoft Dynamics AX system, but they will not be upgraded. The following table describes the options to upgrade an X++ report.

Option

Tool

Define a new Reporting Services report.

Visual Studio Reporting Tools for Microsoft Dynamics AX

For more information, see Developing Reports for Microsoft Dynamics AX in Visual Studio.

Customize an existing production report to meet the same reporting purposes that the original X++ report served.

Visual Studio Reporting Tools for Microsoft Dynamics AX

For more information, see Integrating and Customizing Reports.

Fix the report. This is not the recommended approach as the MorphX Reporting tool is being deprecated.

Morphx Reporting Tools

For more information, see MorphX Reporting Tools.

Note

The End user settings for report print and parameter settings for X++ reports must be reset after the upgrade.

You will no longer set security explicitly on X++ report objects. For example, you previously secured a field on the report using a security key. Role and task security on report data sources like tables and fields will be enforced by X++ reports. For information, see Setting up and maintaining security.

Microsoft Visual Studio tools for Microsoft Dynamics AX reports

Due to framework changes that affect report formats and queries, you must convert reports that were created using Visual Studio tools for Microsoft Dynamics AX 2009. The following table describes the options for a Reporting Services report that was created or customized using the Visual Studio tools for Microsoft Dynamics AX 2009.

Tool

Task

Report Upgrade Tool

Convert the Reporting Services report format to the current report format. For more information, seeReport Project Upgrade.

Visual Studio tools for Microsoft Dynamics AX

Define a new report.

Or

Customize an existing production report to meet the same reporting purposes.

Troubleshooting converted reports


After an Microsoft Dynamics AX 2009 report is converted, there may be additional troubleshooting steps required in Visual Studio tools for Microsoft Dynamics AX. The following table describes additional details for specific kinds of Reporting Services reports.

Report issue

How to resolve

Report data source is SQL and you are receiving the error:

An SqlParameter with ParameterName ‘AX_CompanyName’ is not contained by this SqlParameterCollection.

Refresh the dataset for the report to clear out legacy parameters. In Model Editor, right-click the dataset for the report and then click Refresh.

Report data source is SQL and you are receiving the error:

The ‘AX_CompanyName’ parameter is missing a value.

Remove the AX_CompanyName parameter. To do this, in Model Editor, select the AX_CompanyNameparameter. In the Properties window, set the Default Value to=Microsoft.Dynamics.Framework.Reports.BuiltInMethods.GetUserComany(Nothing).

Report has data methods and you receive an error that the application requires Full Trust permissions to run correctly.

Data methods must run with the FullTrust named permission set. For more information, see Code Access Security.

The report parameter values no longer display in the report header.

The RenderParameter property is intended to debug report parameter values. It displays the parameter values in the header of the report. The default value in Microsoft Dynamics AX 2009 for theRenderParameter property was True. In Microsoft Dynamics AX 2012, the default value is False. During upgrade, the value is not explicitly set.

To show the parameter values in the report header, in Model Editor, select the auto design for the report and set the RenderParameter property to True.

 

Report Project Upgrade [AX 2012]

2 out of 2 rated this helpful – Rate this topic

Updated: February 1, 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

The report upgrade tool is a command line tool that helps you prepare Microsoft Dynamics AX 2009 SQL Server Reporting Services report libraries for the Microsoft Dynamics AX 2012 AOT environment. This is a required step for Microsoft Dynamics AX 2009Reporting Services reports that you want to upgrade to Microsoft Dynamics AX 2012 Reporting Services reports because metadata is now accessed in the AOT nodes instead of .moxl files.

Report Upgrade Tools Tasks


The report upgrade tool locates the Microsoft Dynamics AX 2009 report projects for the location you specify. The following list describes the tasks that the report upgrade tool performs for each report project:

  1. Creates a Dynamics AX Model Project with the same name. The project is created in the AOT in Visual Studio Projects > Dynamics AX Model Projects. Nested business logic is saved but it is not nested.
  2. Identifies the concepts for each Microsoft Dynamics AX model file and creates the appropriate node under the SSRS Reports node in the AOT. The SSRS Reports node is used to store metadata for the top level element and sub-elements. The SSRS Reports node that is created does not contain project files.
  3. Displays the completion status of the upgrade and any errors that occurred.

Using the Report Upgrade Tool

The default install location of the report upgrade tool is C:\Program Files\Microsoft Dynamics AX\60\tools. The syntax for the tool is as follows:

UpgradeReports [command] –t [target directory] <options>

Important

The files in the target directory will be deleted.

You can access Help at the command line from the upgrade tool location, by running UpgradeReports -?.

The following table describes the report upgrade tool parameters:

Command

Description

-p

The project to upgrade. The extension of the project is .dynamicsproj.

-d

The directory that contains projects to upgrade. Subdirectory projects are also upgraded.

-l

The report library from the AOT to upgrade. The library is first extracted to a temporary location.

-list

A list of the report libraries from the AOT to upgrade. Each report library should be listed on a separate line.

-t

The target directory where the upgraded project is created.

The following table describes the report upgrade tool options:

Option

Description

-stop

Stop the upgrade when there is an error. By default, the upgrade continues to run if you do not use the –stop option.

-overwritenodes

Overwrite the nodes in the AOT. By default, the nodes are not overwritten if you do not use the –overwritenodes option.

-createlabels

Create labels in Microsoft Dynamics AX for strings that are in the .resx files. By default, labels are not created unless you use the –createlabels option.

-savetoaod

Save the project to a report library in Microsoft Dynamics AX.

Examples

The following table provides examples and descriptions of command line uses of the report upgrade tool:

Example

Description

UpgradeReports -l CRMReports -t d:\temp

Upgrades the report from the CRMReports library in the AOT.

UpgradeReports -p reportsDir\CRMReports.dynamicsproj -t d:\temp

Upgrades the CRMReports project from disk.

UpgradeReports -d reportsDir -t d:\temp

Upgrades all reports in the reportsDir directory and its subdirectories.

UpgradeReports -list d:\reports.txt -t d:\temp

Upgrades the libraries that are specified in the reports.txt file. The contents of the file d:\reports.txt are the following:

AssetAcquisitionReport

AssetAdditionReport

AssetBalanceReportColumnsReport

 

 

Guidance when Upgrading Reports [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: July 25, 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Reports are not upgraded automatically during the upgrade process. Microsoft Dynamics AX provides hundreds of default, out-of-the-box reports that you can deploy and customize. To upgrade MorphX reports, we recommend that you customize a default report. The default reports run on SQL Server Reporting Services. Reporting Services is a server-based reporting platform that provides comprehensive reporting functionality for a variety of data sources.

When upgrading to Microsoft Dynamics AX 2012, existing Reporting Services reports and reports based on the MorphX reporting framework are copied to the Microsoft Dynamics AX 2012system. However, they will not be upgraded.

This topic describes additional options to determine the best approach to upgrade a MorphX report when you need to customize a default report.

Determining the Best Upgrade Approach


For each report, there are considerations to determine the best upgrade approach. If, after you customize a default report, it does not meet your needs, the following list contains other options for upgrading a MorphX report.

  • Define a new Reporting Services report
  • Convert the report to a Reporting Services report

This section provides the steps for each of these options to understand the best approach to upgrade your MorphX reports.

Define a New Reporting Services Report

Reporting Services is the primary reporting platform for Microsoft Dynamics AX. The following list provides the steps to define a report when using the Visual Studio tools for Microsoft Dynamics AX.

Note

There is no need to reference another reporting project. You can access all model elements in the AOT without using a reference.

Convert the Report to a Reporting Services Report

To convert a report from MorphX to Reporting Services you must migrate business logic to development concepts used for Reporting Services reports. Determine which advanced Reporting Services development concepts are required to define the same reporting solution as the MorphX report.

Use the following steps to convert a MorphX report to Reporting Services.

  • Examine the MorphX report.
    • In the AOT, expand the Reports node, and then expand the node for the MorphX report that you want to convert.
    • Determine the data source used for the report. This includes the relationships between tables and the fields that are used to display data for the report.
    • Apply Microsoft Dynamics AX database schema changes.

      Fix compilation issues in the MorphX report related to database schema changes. The following list describes some of the schema changes that affect legacy reports.

    • In the AOT, expand the MenuItems node, expand the Output node, and then double-click the report name with Old appended to it, for example, AXSalesReportOld.

      This opens the parameter dialog.

    • Enter data in the parameter dialog form and then click OK to print the report.
  • Define the report data source.

    Determine which type of data source is appropriate for your Reporting Services report. To do this you must understand the structure of the report data source. The following table describes when to use a query or a Report Data Provider (RDP) class.

Data source

Description

Query based report

Data for a report can be fulfilled by using a combination of table relations and table display methods.

RDP based report

Data for a report requires custom X++ business logic.

Take into account items in the following list when you review the report dataset.

  • Source of the data contained in the report dataset.
  • Elements of the report that are from report business logic.
  • Calculated columns based on Microsoft Dynamics AX data.
  • Extended Data Types (EDTs) that are used to format data.
  • Data that does not display on the report but which is used to navigate to Microsoft Dynamics AX forms.
  • When custom business logic is needed, create a Report Data Provider (RDP) class.

    An RDP class is the data access layer that contains the X++ custom business logic used to produce the report dataset. Refactor the existing X++ code into an RDP class and then separate the business logic from the report that renders logic.

  • TempDB temporary tables are used to store the report dataset generated by the RDP class.
  • In the AOT, create a temporary table to store the report dataset and then define the table schema based on the dataset that is needed to generate the report.
  • Consider if you should use the report execution sequence. Create a report controller class that extends the SysOperationController class for MorphX report execution. The following list describes the reasons to override the controller class.
    • Change the query based on input parameters.
    • React to form control events.
    • Add contextual input validation that is not part of the contract.
    • Select the report design based on the user input.
    • Modify organization or culture information.
  • Define a report in Visual Studio and bind it to the RDP class.
  • If necessary, convert the basic design into a precision design to achieve the desired report layout.
  • Deploy the report to the Reporting Server. In Visual Studio, from the Build menu, click Deploy Solution to Deploy the report.
  • From the File menu, click Save All and close Visual Studio. You are prompted to add the local project to the AOT.
  • View the report in Report Manager by using the URL: http://%5BMachineName%5D/reports
  • View the report in Microsoft Dynamics AX by creating a menu item for the report.
  • After you convert the report you must manually delete the old report. For more information, see How to Delete a SQL Reporting Services Report

Note

There is no need to reference another reporting project. You can access all model elements in the AOT without using a reference.

 

 

 

Mapping Microsoft Dynamics AX 2009 Reports to the Microsoft Dynamics AX 2012 Version [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: July 25, 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic provides a mapping of the reports from Microsoft Dynamics AX 2009 to a similar representation of data in Microsoft Dynamics AX 2012. The following implementations were used to show similar data:

Some reports will not be provided in this release. For more information, see Deprecated Microsoft Dynamics AX 2009 Reports in Microsoft Dynamics AX 2012. For information about the reports that will be provided, see Report catalog for Microsoft Dynamics AX. For a Microsoft Excel version of the report list, see Microsoft Dynamics AX 2012 and 2009 Report List.

Report Mapping to Reporting Services Reports


The following table provides the mapping of a Microsoft Dynamics AX 2009 report to the report in Microsoft Dynamics AX 2012.

Microsoft Dynamics AX 2009 Report Name

Microsoft Dynamics AX 2012 Report Name

SysCompanySize

SysCompanySize

SysDataAreaPrintCollections

SysDataAreaPrintCollections

SysDatabaseLog

SysDatabaseLog

SysSqlSyncInfo

SysSqlSyncInfo

SysTableDefinition

SysTableDefinition

SysUsersOnline

SysUsersOnline

BankPaymAdviceVend

BankPaymAdviceVend

PurchEUVatInvoice

PurchEUVATInvoice

PurchInvoice

PurchInvoice

VendAccountStatementInt

VendAccountStatementInt

VendCheckSettlement

VendCheckSettlement

VendExchRateAdjSimulation

VendExchRateAdjSimulation

VendExchRateAdjustment

VendExchRateAdjustment

VendInvoice

VendInvoice

VendInvoicePoolNotposted

VendInvoicePoolNotposted

VendInvoiceSpec

VendInvoiceSpec

VendInvoiceVolume

VendInvoiceVolume

VendLedgerTrans

VendLedgerTrans

VendOutAttendingNote_PNRemittance

VendOutAttendingNote_PNRemittance

VendPromissoryNoteReport

VendPromissoryNoteReport

VendProvisionalBalance

VendProvisionalBalance

VendReportApproveCollection

VendReportApproveCollection

VendAgingreport

VendAgingreport (detail or summary version)

VendBalanceList

VendBalanceList

VendDueReportDetail_NA

VendDueReportDetail_NA

VendLedgerReconciliation

VendLedgerReconciliation

VendPurchOpenOrders_NA

VendPurchOpenOrders_NA

VendTransList

VendTransListReport

VendInvoiceJour

VendInvoiceJour

BankPaymAdviceCust

BankPaymAdviceCust

CustAccountStatementInt

CustAccountStatementInt

CustAuditor

CustAuditor

CustBillOfExchangeReport

CustBillOfExchangeReport

CustCheckSettlement

CustCheckSettlement

CustCOD

CustCOD

CustCollectionJour

CustCollectionJour

CustCollectionLetterOverview

CustCollectionLetterOverview

CustExchRateAdjSimulation

CustExchRateAdjSimulation

CustExchRateAdjustment

CustExchRateAdjustment

CustInvoice

CustInvoice

CustInvoiceSpec

CustInvoiceSpec

CustInvoiceVolume

CustInvoiceVolume

CustLedgerTrans

CustLedgerTrans

CustOutAttendingNote_BillRemittance

CustOutAttendingNote_BillRemittance

CustPaymManFeeHist

CustPaymManFeeHist

CustPaymManOutputReport

CustPaymManOutputReport

CustPaymManStepPosting

CustPaymManStepPosting

CustPaymManUnpaid

CustPaymManUnpaid

CustProvisionalBalance

CustProvisionalBalance

CustReimbursement

CustReimbursement

CustTransOpenPerDate

CustTransOpenPerDate

CustTransTaxTrans

CustTransTaxTrans

CustVendAgingStaticticsAutoReport

CustVendAgingStaticticsAutoReport

CustVendPaymJournal

CustVendPaymJournal

CustVendPaymProposal

CustVendPaymProposal

FreeTextInvoice

FreeTextInvoice

SalesInvoice

SalesInvoice

CustAccountStatementExt

CustAccountStatementExt

CustAgingReport

CustAgingReport

CustBalanceList

CustBalanceList

CustLedgerReconciliation

CustLedgerReconciliation

CustSalesOpenOrders_NA

CustSalesOpenOrders_NA

CustTransList

CustTransList

CustInvoiceJour

CustInvoiceJour

CustDueReportDetail

CustDueReportDetail

BankAccountStatement

BankAccountStatement

BankBillOfExchange

BankBillOfExchange

BankDepositByCustomer

BankDepositbyCustomer

BankDepositByDate

BankDepositByDate

BankDepositSlip

BankDepositSlip

BankPaymAdviceCheque

BankPaymAdviceCheque

BankPaymentByDate

BankPaymentByDate

BankPaymentByVendor

BankPaymentbyVendor

BankReconciliation

BankReconciliation

BankReconciliationSummary

BankReconciliationSummary

BankAccountReconciliation

BankAccountReconciliation

BankLedgerReconciliation

BankLedgerReconciliation

AssetAcquisition

AssetAcquisition

AssetAddition

AssetAddition

AssetBalanceReportColumns

AssetBalanceReportColumns

AssetBalancesPeriod

AssetBalancesPeriod

AssetBarcode

AssetBarcode

AssetBasis

AssetBasis

AssetBookCompare

AssetBookCompare

AssetConsumptionProposal

AssetConsumptionProposal

AssetDepBookMassUpdate

AssetDepBookMassUpdate

AssetDisposal

AssetDisposal

AssetFutureValue

AssetFutureValue

AssetInsurance

AssetInsurance

AssetLending

AssetLending

AssetLendingHistory

AssetLendingHistory

AssetListing

AssetListing

AssetMidQuarter

AssetMidQuarter

AssetReserveTransactions

AssetReserveTransactions

AssetsInAssetStatement

AssetsInAssetStatement

AssetStatement

AssetStatement

AssetStatementRowSetup

AssetStatementRowSetup

AssetTaxStatistic

AssetTaxStatistic

AssetTransactionListing

AssetTransactionListing

AssetBalances

AssetBalances

IntrastatFormLetter

IntrastatFormLetter

IntrastatList

IntrastatList

LedgerAccountSched

LedgerAccountSched

LedgerAllocationRules

LedgerAllocationRules

LedgerBalanceControl

LedgerBalanceControl

LedgerCheckTrans

LedgerCheckTrans

LedgerCheckVoucher

LedgerCheckVoucher

LedgerClosing

LedgerClosing

LedgerEliminationRules

LedgerEliminationRules

LedgerJournalAccountMovement

LedgerJournalAccountMovement

LedgerJournalCashReport

LedgerJournalCashReport

LedgerJournalizeReport

LedgerJournalizeReport

LedgerJournalizeReport2

LedgerJournalizeReportTransLog

LedgerJournalPostControlByJournalType

LedgerJournalPostControlByJournalType

LedgerJournalPostControlByUser

LedgerJournalPostControlByUser

LedgerRowDefinitionPrint

LedgerRowDefinitionPrint

LedgerRowStructureWhereUsed

LedgerRowStructureWhereUsed

LedgerTotalAndBalanceList

LedgerTotalAndBalanceList

LedgerTransferOpening

LedgerTransferOpening

LedgerTransListAccount

LedgerTransListAccount

LedgerTransListDate

LedgerTransListDate

LedgerTransOpen

LedgerTransOpen

LedgerTransPerJournal

LedgerTransPerJournal

LedgerTransStatement

LedgerTransStatement

TaxAmountByCustomer

TaxAmountByCustomer

TaxAmountByVendor

TaxAmountByVendor

TaxCodeReportSetup

TaxCodeReportSetup

TaxDeviation

TaxDeviation

TaxLedgerReconciliation

TaxLedgerReconciliation

TaxList

TaxList

TaxPackagingTaxItem

TaxPackagingTaxItem

TaxReportById

TaxReportById

TaxReportInclAdjustment

TaxReportInclAdjustment

TaxReporting

TaxReporting

TaxSpecPerLedgerTrans

TaxSpecPerLedgerTrans

TaxTable

TaxTable

TaxTrans

TaxTrans

TaxTransCode

TaxTransCode

TaxTransDetail

TaxTransDetail

TaxWithholdTrans

TaxWithholdTrans

LedgerAccountStatementPerCurrency

LedgerAccountStatementPerCurrency

LedgerOpenTransactions

LedgerOpenTransactions

LedgerProvisionalBalance

LedgerTrialBalance

LedgerTransBase

LedgerTransBase

LedgerJournal

LedgerJournal

LedgerTrialBalance

LedgerTrialBalance

LedgerAuditTrail

LedgerAuditTrail

BankReconciliation

BankReconciliation

VendAccountStatement_FR

VendAccountStatement_FR

VendAccruedPurchases_NA

VendAccruedPurchases_NA

VendInvoiceSettled_TransDate_ES

VendInvoiceSettled_TransDate_ES

VendOpenPaymDocu_ES

VendOpenPaymDocu_ES

VendOutAttendingNote_ATEDIFACT

VendOutAttendingNote_ATEDIFACT

VendOutAttendingNote_DEDTAUS

VendOutAttendingNoteDE_DTAUS

VendOutAttendingNote_DEDTAZV

VendOutAttendingNote_DEDTAZV

VendOutCoveringLetter_DEDTAUS

VendOutCoveringLetter_DEDTAUS

VendOutCoveringLetter_DEDTAZV

VendOutCoveringLetter_DEDTAZV

VendOutPaymAdvice_ATEDIFACT

VendOutPaymAdvice_ATEDIFACT

VendOutPaymAdvice_CHDTA

VendOutPaymAdvice_CHDTA

VendOutPaymAdvice_CHEZAG

VendOutPaymAdvice_CHEZAG

VendOutPaymControl

VendOutPaymControl

VendOutPaymControl_DEDTAZV

VendOutPaymControl_DEDTAZV

VendOutPaymControl_ES

VendOutPaymControl_ES

VendOutPaymControl_FI_FOR

VendOutPaymControl_FI_FOR

VendOutPaymControl_FI_LM

VendOutPaymControl_FI_LM

VendOutPaymControl_FR

VendOutPaymControl_FR

VendOutPaymControl_IT

VendOutPaymControl_IT

VendOutPaymControl_SE

VendOutPaymControl_SE

VendOutPaymOrder_CHDTA

VendOutPaymOrder_CHDTA

VendOutPaymOrder_CHEZAG

VendOutPaymOrder_CHEZAG

VendPaymentJournal_NA

VendPaymentJournal_NA

VendPaymRefReport_BE

VendPaymRefReport_BE

VendPostPaymJournal_NA

VendPostPaymJournal_NA

VendPromissoryNoteOpenTrans_ES

VendPromissoryNoteOpenTrans_ES

VendPromissoryNoteOpenTrans_FR

VendPromissoryNoteOpenTrans_FR

VendPurchaseDistribution_NA

VendPurchaseDistribution_NA

VendPurchOpenLinesByDelvDate_NA

VendPurchOpenLinesByDelvDate_NA

VendPurchOpenLinesByItem_NA

VendPurchOpenLinesByItem_NA

VendPurchOpenLinesByVend_NA

VendPurchOpenLines_NA with three designs:i)ByVend ii) ByItem iii) ByDelvDate

VendPurchReceivingLog_NA

VendPurchReceivingLog_NA

VendTransOpen_PaymMode_ES

VendTransOpen_PaymMode_ES

VendOutPaymAdvice_FRAFB

VendOutPaymAdvice_FRAFB

CustAccountStatement_FR

CustAccountStatement_FR

CustBalanceList_MY

CustBalanceList_MY

CustBillOfExchangeOpenTrans_ES

CustBillOfExchangeOpenTrans_ES

CustBillOpenTrans_FR

CustBillOpenTrans_FR

CustDomStatement_BE

CustDomStatement_BE

CustGrossMarginbyAccount_NA

CustGrossMarginbyAccount_NA

CustGrossMarginbyItem_NA

CustGrossMarginbyItem_NA

CustInPaymentCH

CustInPaymentCH

CustInPaymSE

CustInPaymSE

CustInvoiceSettled_TransDate_ES

CustInvoiceSettled_TransDate_ES

CustInvoiceVolume_BE

CustInvoiceVolume_BE

CustOpenBillId_ES

CustOpenBillId_ES

CustOutAttendingNoteAT_EDIFACT

CustOutAttendingNoteAT_EDIFACT

CustOutAttendingNoteDE_DTAUS

CustOutAttendingNoteDE_DTAUS

CustOutCoveringLetterDE_DTAUS

CustOutCoveringLetterDE_DTAUS

CustOutPaymAdviceAT_EDIFACT

CustOutPaymAdviceAT_EDIFACT

CustOutPaymAdviceCH_DebitDirect

CustOutPaymAdviceCH_DebitDirect

CustOutPaymAdviceCH_LSV

CustOutPaymAdviceCH_LSV

CustOutPaymControl

CustOutPaymControl

CustOutPaymControl_ES

CustOutPaymControl_ES

CustOutPaymControl_FR

CustOutPaymControl_FR

CustOutPaymControl_FR_LCR

CustOutPaymControl_FR_LCR

CustOutPaymControl_IT

CustOutPaymControl_IT

CustOutPaymLetterFR

CustOutPaymLetter_FR

CustOutPaymOrderCH_DebitDirect

TaxWithholdCertificationIT

CustOutPaymOrderCH_LSV

TaxWithholdYearlyReportIT

CustPaymentJournal_NA

TaxWithholdMonthlyReportIT

CustPaymReconciliationPrint_DK_BS

CustPaymReconciliationPrint_DK_BS

CustPostPaymJournal_NA

CustPostPaymJournal_NA

CustSalesAnalysisByInvoice_NA

CustSalesAnalysisByInvoice_NA

CustSalesDistribution_NA

CustSalesDistribution_NA

CustSalesItemGroupStatistics_NA

CustSalesItemGroupStatistics_NA

CustSalesOpenLinesByCust_NA

CustSalesOpenLines_NA with ByCust design

CustSalesOpenLinesByDelvDate_NA

CustSalesOpenLines_NA with ByDelvDate design

CustSalesOpenLinesByItem_NA

CustSalesOpenLines_NA with ByItem design

CustShippedNotInvoiced_NA

CustShippedNotInvoiced_NA

CustTransOpen_ES

CustTransOpen_ES

RCSalesList_UK

RCSalesList_UK

CustInPaymNO

CustInPaymNO

FreeTextInvoice

FreeTextInvoice

SalesInvoice

SalesInvoice

SalesPackingSlip

SalesPackingSlip

BankReconciliation

BankReconciliation

BankBillOfExchange_FR

BankBillOfExchange_FR

BankCashflowReport

BankCashflowReport

BankCodaDetails

BankCodaDetails

BankPaymIdTypesSetup_NO

BankPaymIdTypesSetup_NO

BankPromissoryNote_ES

BankPromissoryNote_ES

BankPromissoryNote_FR

BankPromissoryNote_FR

Cheque_CA

Cheque_CA

Cheque_DE

Cheque_DE

Cheque_DK

Cheque_DK

Cheque_ES

Cheque_ES

Cheque_FR

Cheque_FR

Cheque_UK

Cheque_UK

Cheque_US

Cheque_US

BankReconciliationSummary

BankReconciliationSummary

BankReconciliationSummary

BankReconciliationSummary

EUSalesListAT

EUSalesListAT

EUSalesListDE

EUSalesListDE

EUSalesListDK

EUSalesListDK

EUSalesListFI

EUSalesListFI

EUSalesListNL

EUSalesListNL

EUSalesListSE

EUSalesListSE

EUSalesListUK

EUSalesListUK

LedgerJournal

LedgerJournal

LedgerAccountSched

LedgerAccountSched

LedgerTotalAndBalanceList

LedgerTotalAndBalanceList

TaxWithholdReport_TH

TaxWithholdReport_TH

TaxWithholdReportPND_TH

TaxWithholdReportPND_TH

TaxWithholdSlip_TH

TaxWithholdSlip_TH

AssetDepreciationLedger_IT

AssetDepreciationLedger_IT

AssetOverviewBE

AssetOverviewBE

AssetStatementLowValuePool_AU

AssetStatementLowValuePool_AU

LedgerCentralisationJournalReportBE

LedgerCentralisationJournalReportBE

LedgerFinancialJournalReportBE

LedgerFinancialJournalReportBE

LedgerFiscalJournal_IT

LedgerFiscalJournal_IT

LedgerInAccountStatementDE_DTAUS

LedgerInAccountStatementDE_DTAUS

LedgerInAccountStatementDE_MT940

LedgerInAccountStatementDE_MT940

LedgerJournalizeReport_DE

LedgerJournalizeReport_DE

LedgerJournalizeReport_ES

LedgerJournalizeReport_ES

LedgerPeriodSum_FR

LedgerPeriodSum_FR

LedgerPurchaseJournalReportBE

LedgerPurchaseJournalReportBE

LedgerTransDateVoucher_FR

LedgerTransDateVoucher_FR

LedgerXBorderActivityAT

LedgerXBorderActivityAT

Tax1099Detail

Tax1099Detail

Tax1099DupTIN

Tax1099DupTIN

Tax1099Report

Tax1099Report

Tax1099Summary

Tax1099Summary

TaxAmountByCustomer_BE

TaxAmountByCustomer_BE

TaxAmountByVendor_BE

TaxAmountByVendor_BE

TaxBookReport_ES

TaxBookReport_ES

TaxBookReportSum_ES

TaxBookReportSum_ES

TaxList_BE

TaxList_BE

TaxPurchaseTaxReport

TaxPurchaseTaxReport

TaxPurchLedger

TaxPurchLedger

TaxReport_AU

TaxReport_AU

TaxReport_BE

TaxReport_BE

TaxReport_DE

TaxReport_DE

TaxReport_IT

TaxReport_IT

TaxReport_NL

TaxReport_NL

TaxReport_NO

TaxReport_NO

TaxReport_SE

TaxReport_SE

TaxReport_SG

TaxReport_SG

TaxReport_US

TaxReport_US

TaxReport349

TaxReport349

TaxReportAlandImport_FI

TaxReportAlandImport_FI

TaxReportCorrectionBE

TaxReportCorrectionBE

TaxReportIntervat

TaxReportIntervat

TaxReportUnrealizedInputOutput

TaxReportUnrealizedInputOutput

TaxSalesLedger

TaxSalesLedger

TaxTrans_BE

TaxTrans_BE

TaxTransDetail_BE

TaxTransDetail_BE

TaxWithholdCertificationIT

TaxWithholdCertification_IT

TaxWithholdYearlyReportIT

TaxWithholdYearlyReport_IT

LedgerPostingJournalList

LedgerPostingJournalList

LedgerPostingJournalTotal

LedgerPostingJournalTotal

TaxReconciliationReport

TaxReconciliationReport

TaxReport_FI

TaxReport_FI

TaxYearlyComReport_IT

TaxYearlyComReport_IT

LedgerTransAccountVoucher_FR

LedgerTransAccountVoucher_FR

LedgerAccountSum_FR

LedgerAccountSum_FR

TaxWithholdMonthlyReportIT

TaxWithholdMonthlyReport_IT

VendConsultationFees_SA

VendConsultationFees_SA

VendSubContractor_SA

VendSubcontractor_SA

LedgerMainReportZakat_SA

LedgerMainReportZakat_SA

InventMovement_TH

InventMovement_TH

InventPhysicalPerWarehouseTrans_IT

InventPhysicalPerWarehouseTrans_IT

InventProdComGeneral

InventProdComGeneral

InventFiscalLIFOValuation

InventFiscalLIFOValuation

IntrastatFormLetterAT

IntrastatFormLetterAT

IntrastatFormLetterDE

IntrastatFormLetterDE

IntrastatFormLetterES

IntrastatFormLetterES

IntrastatFormLetterFI

IntrastatFormLetterFI

IntrastatFormLetterFR

IntrastatFormLetterFR

IntrastatFormLetterIT

IntrastatFormLetterIT

IntrastatFormLetterSE

IntrastatFormLetterSE

IntrastatFormLetterUK

IntrastatFormLetterUK

IntrastatListES

IntrastatListES

IntrastatListNL

IntrastatListNL

IntrastatListUK

IntrastatListUK

IntrastatPeriodReport_IT

IntrastatPeriodReport_IT

IntrastatListFI

IntrastatListFI

HRMEPAbsenceTransList

HcmEPAbsenceTransListThisYear

HRMEPBirthday

HcmEPBirthdays

HRMEPJubilee

HcmEPAnniversaries

HRMAbsenceAdministration

HcmAbsenceAdministration

HRMAbsenceEmplDue

HcmAbsenceJournalMissingReport

HRMAbsenceSetup

HcmAbsenceSetup

HRMAbsenceStatusListPrint

HcmAbsenceStatus 

HRMAccommodationtList

HCMAccommodationtList

HRMADARequirement

HcmADARequirement

HRMApplicantStatus

HcmApplicantStatusReport

HRMBirthday

HcmBirthday

HRMCourseAgenda

HcmCourseAgenda

HRMCourseAttendeeLine

HcmCourseAttendeeLine

HRMCourseAttendeeStatusList

HcmCourseAttendeeStatusList

HRMCourseConfirmation

HcmCourseConfirmation

HRMCourseDesign

HcmCourseDesign

HRMCourseSkills

HcmCourseSkills

HRMCourseTableInstructor

HcmCourseTableInstructor

HRMEmplLeave

HcmEmployeeLeave

HRMEmployeeBenefit

HcmWorkerBenefits 

HRMGoalAlarm

HcmGoalAlarm

HRMi9Document

Hcmi9Document

HRMi9DocumentExpireList

Hcmi9DocumentExpireList

HRMi9DocumentTypeExpireList

Hcmi9DocumentTypeExpireList

HRMi9InspectionList

Hcmi9InspectionList

HRMJobByOrganization

HcmPositionsByDepartment 

HRMJobInformation

HcmJobInformation

HRMJubilee

HcmAnniversary

HRMMassHireProject

HcmMassHireProject

HRMOrganizationTotal

HcmNumberOfWorkersReport

HRMRecruiting

HcmRecruiting

HRMRecruitingApplicationStatus

HcmRecruitingApplicationStatus

HRMSeniority

HcmSeniorityReport

HRMSkillBySkillType

HcmSkillBySkillType

HRMSkillBySkillTypeCount

HcmSkillBySkillTypeCount

HRMSkillGapJob

HcmSkillGapJob

HRMSkillProfile

HcmSkillProfile

HRMSkillType

HcmSkillType

HRMVirtualNetworkCV

HcmWorkerResume & HcmApplicantResume

HRMVirtualNetworkDueCertificate

HcmDueCertificate

HRMVirtualNetworkIdByOrganization

HcmPeopleDepartmentReport

HRMVirtualNetworkSkill

HcmWorkerSkill

HRMJobTemplateInformation

HcmJobTemplateInformation

OrganizationUnit

HcmDepartmentReport

HRMCourseAttendeeCollectionResult

HcmCourseAttendeeCollectionResult

KMKnowledgeCollector

KMKnowledgeCollector

KMKnowledgeCollectorByCollection

KMAnswersByQuestionnaire

KMKnowledgeCollectorByVirtualNetworkId

KMAnswersByPerson

KMQuestionAnalyze

KMQuestionAnalyze

KMQuestionAndAnswer

KMQuestionandAnswer

Cust

Cust

CustBasedata

CustBaseData

CustRevenue

smmCustRevenue

SalesItemCustStatistics

smmSlaesCustStatistics

SalesRanking

smmSalesRanking

smmActivityAnalyses

smmActivityAnalyses

smmCampaignResponseFrequency

smmCampaignResponseFrequency

smmPhoneAverage

smmPhoneAverage

smmSalesTargets

smmSalesTarget

smmTMCallListTelemarketingSummary

smmTMCallListTelemarketingSummary

EPProjHourStatement

EPProjHourStatement

TrvAllowance

TrvAllowance

TrvCost

TrvCost

TrvCostStatistics

TrvCostStatistics

TrvExpense

TrvExpense

TrvExpenseSettlementReport

TrvExpenseSettlementReport

TrvMileage

TrvMileage

TrvPersonalExpenses

TrvPersonalExpenses

ProjCashFlowCategoryReport

ProjCashFlowCategory

ProjCashFlowEmplItemReport

ProjCashFlowEmplItem

ProjCashFlowProjectReport

ProjCashFlowProject

ProjListClosingProfile

ProjClosingProfile

ProjEstimateList

ProjEstimateList

ProjInvoice

ProjInvoice

ProjInvoiceJournal

ProjInvoiceJournal

ProjJournalEmpl

ProjJournalEmpl

ProjJournalRevenue

ProjJournalRevenue

ProjListBudget

ProjListBudget

ProjListEstimateHourRate

ProjListEstimateHourRate

ProjListEstimateProdBacklogConsumption

ProjListEstimate

ProjListEstimateProdBacklogOnAcc

ProjListEstimate

ProjListEstimateProdBacklogPL

ProjListEstimate

ProjListEstimateReadyForElimination

ProjListEstimate

ProjListEstimateWonFixedPriceProjPL

ProjListEstimate

ProjListInvoiceTable

ProjListInvoiceTable

ProjListLedgerReconPayRoll

ProjListLedgerRecon

ProjListLedgerReconProfitLoss

ProjListLedgerRecon

ProjListLedgerReconWIP

ProjListLedgerRecon

ProjListLedgerReconWIPAccount

ProjListLedgerReconWIPAccount

ProjListLedgerUpdatesConsumption

ProjListLedgerUpdates

ProjListLedgerUpdatesOnAccount

ProjListLedgerUpdates

ProjListLedgerUpdatesPayroll

ProjListLedgerUpdates

ProjListLedgerUpdatesProfitLoss

ProjListLedgerUpdatesProfitLoss

ProjListLedgerUpdatesWIP

ProjListLedgerUpdates

ProjListLineProperty

ProjListLineProperty

ProjListPostingReady

ProjListPostingReady

ProjListProjConsumptionCategory

ProjConsumCateg

ProjListProjConsumptionCategory2Column

ProjConsumCateg2Column

ProjListProjConsumptionCategory2CoPeriod

ProjConsumCateg2Prd

ProjListProjConsumptionEmplItem

ProjConsumEmpl

ProjListProjConsumptionEmplItem2Column

ProjConsumEmpl2Column

ProjListProjConsumptionEmplItem2CoPeriod

ProjConsumeEmpl2Prd

ProjListProjConsumptionProj

ProjConsumProj

ProjListProjConsumptionProj2Column

ProjConsumProj2Column

ProjListProjConsumptionProj2ColumnPeriod

ProjConsumProj2Prd

ProjListProjHourRateCategory

ProjHourRateCateg

ProjListProjHourRateEmplItem

ProjHourRateEmpl

ProjListProjHourRateProj

ProjHourRateProj

ProjListProjOnAccountProj

ProjOnAccProj

ProjListProjOnAccountProj2Column

ProjOnAccProj2Column

ProjListProjOnAccountProj2ColumnPeriod

ProjOnAccProj2Prd

ProjListProjPayRollCategory

ProjPayrollCateg

ProjListProjPayRollCategory2Column

ProjPayrollCateg2Column

ProjListProjPayRollCategory2ColumnPeriod

ProjPayrollCateg2Prd

ProjListProjPayRollEmplItem

ProjPayrollEmpl

ProjListProjPayRollEmplItem2Column

ProjPayrollEmpl2Column

ProjListProjPayRollEmplItem2ColumnPeriod

ProjPayrollEmpl2Prd

ProjListProjPayRollProj

ProjPayrollProj

ProjListProjPayRollProj2Column

ProjPayrollProj2Column

ProjListProjPayRollProj2ColumnPeriod

ProjPayrollProj2Prd

ProjListProjPosting

ProjListProjPosting

ProjListProjProfitLossCategory

ProjProfitLossCateg

ProjListProjProfitLossCategory2ColPeriod

ProjProfitLossCateg2Prd

ProjListProjProfitLossCategory2Column

ProjProfitLossCateg2Column

ProjListProjProfitLossEmplItem

ProjProfitLossEmpl

ProjListProjProfitLossEmplItem2ColPeriod

ProjProfitLossEmpl2Prd

ProjListProjProfitLossEmplItem2Column

ProjProfitLossEmpl2Column

ProjListProjProfitLossProj

ProjProfitLossProj

ProjListProjProfitLossProj2Column

ProjProfitLossProj2Column

ProjListProjProfitLossProj2ColumnPeriod

ProfitLossProj2Prd

ProjListProjTable

ProjListProjTable

ProjListProjWIPCategory

ProjWIPCateg

ProjListProjWIPCategory2Column

ProjWIPCateg2Column

ProjListProjWIPCategory2ColumnPeriod

ProjWIPCateg2Prd

ProjListProjWIPCustTable

ProjListProjWIPCustTable

ProjListProjWIPEmplItem

ProjWIPEmpl

ProjListProjWIPEmplItem2Column

ProjWIPEmpl2Column

ProjListProjWIPEmplItem2ColumnPeriod

ProjWIPEmpl2Prd

ProjListProjWIPProj

ProjWIPProj

ProjListProjWIPProj2Column

ProjWIPProj2Column

ProjListProjWIPProj2ColumnPeriod

ProjWIPProj2Prd

ProjListTrans

ProjListTrans

ProjListTransCommittedCost

ProjListTransCommittedCost

ProjListTransProj

ProjListTransProj

ProjMissingHourReg

ProjMissingHourReg

ProjOnAccountInvoicePlan

ProjOnAccountInvoicePlan

ProjPeriodPosting

ProjPeriodPosting

ProjPriceGroupList

ProjPriceGroupList

ProjUtilCategory

ProjUtilCategory

ProjUtilEmpl

ProjUtilEmpl

ProjUtilProject

ProjUtilProject

ProjValCategory

ProjValCategory

ProjValEmplCategory

ProjValEmplCategory

ProjValEmployee

ProjValEmployee

ProjValEmployeeProj

ProjValEmployeeProj

ProjValProjCategory

ProjValProjCategory

ProjValProject

ProjValProject

PurchPackingSlip

PurchPackingSlip

PurchPurchaseOrder

PurchPurchaseOrder

PurchRanking

PurchRanking

PurchReceiptsList

PurchReceiptsList

PurchVariencesCostPrice

PurchVariencesCostPrice

ReqItemJournalSafetyStock

ReqItemJournalSafetyStock

ReqTransAction

ReqTransAction

ReqTransFutures

ReqTransFutures

CommissionTrans

CommissionTrans

ReturnAcknowledgment

ReturnAcknowledgmentAndDocument

ReturnDocument

ReturnAcknowledgmentAndDocument

SalesCODLabel

SalesCODLabel

SalesConfirm

SalesConfirm

SalesHeading

SalesHeading

SalesLinesExtended

SalesLinesExtended

SalesNotInvoiced

SalesNotInvoiced

SalesPackingSlip

SalesPackingSlip

SalesQuotation

SalesQuotation

SalesQuotationConfirmation

SalesQuotationConfirmation

SalesShippingLabel

SalesShippingLabel

InventCheckSettlement

InventCheckSettlement

InventSiteDimensionLinkValidation

InventSiteDimensionLinkValidation

WrkCtrCapRes

WrkCtrCapRes

WrkCtrJobs

WrkCtrJobs

COSCostRatesPrint

COSCostRatesPrint

COSDiffAccount

COSDiffAccount

COSDiffLedger

COSDiffLedger

COSDiffProd

COSDiffProd

COSJournalReport

COSJournalReport

COSPeriodCalculationUniversal

COSPeriodCalculationUniversal

COSReportPrint

COSReportPrint

COSTrans

COSTrans

COSTransPreview

COSTransPreview

EPSalesByCustomer

EPSalesByCustomer

EPSalesByRegion

EPSalesByRegion

InventBalanceAccount

InventBalanceAccount

InventLedgerConciliation

InventLedgerConciliation

BOMCalcTrans

BOMCalcTrans

BOMConsistOf

BOMConsistOf

BOMPartOf

BOMPartOf

ConvInventPriceIsZero

ConvInventPriceIsZero

ForecastSalesItem

ForecastSalesItem

InventABC

InventABC

InventAdjOnHand

InventAdjOnHand

InventAdjTransaction

InventAdjTransaction

InventAgeDim

InventAgeDim

InventAgeGroup

InventAgeGroup

InventBalanceAccountService

InventBalanceAccountService

InventCheckReceiptCostPricePcs

InventCheckReceiptCostPricePcs

InventCostValue

InventCostValue

InventCostVariances

InventCostVariances

InventCountingList

InventCountingList

InventCountStatistics

InventCountStatistics

InventDimPhys

InventDimPhys

InventJournalTrans

InventJournalTrans

InventJournalTrans_Tag

InventJournalTrans_Tag

InventJournalTransTransfer

InventJournalTransTransfer

InventNonConformanceTable

InventNonConformanceTable

InventNonConformanceTag

InventNonConformanceTag

InventOnhand

InventOnhand

InventOpenQtyCritical

InventOpenQtyCritical

InventPriceOverview

InventPriceOverview

InventQuarantineOrder

InventQuarantineOrder

InventSettlementAdjustment

InventSettlementAdjustment

InventStdCostConvCheck

InventStdCostConvCheck

InventStdCostVariance

InventStdCostVariance

InventSumCritical

InventSumCritical

InventTableOverview

InventTableOverview

InventTablePriceDiscount

InventTablePriceDiscount

InventTableQuantity

InventTableQuantity

InventTestCertOfAnalysis

InventTestCertOfAnalysis

InventTestCorrection

InventTestCorrection

InventTransferOrderOverview

InventTransferOrderOverview

InventTransferReceive

InventTransferReceive

InventTransferShip

InventTransferShip

WMSBillOfLading

WMSBillOfLading

WMSCheckABCZones

WMSCheckABCZones

WMSJournalTrans

WMSJournalTrans

WMSLocationLabel

WMSLocationLabel

WMSPalletList

WMSPalletList

WMSPalletNumber

WMSPalletNumber

WMSPickingList

WMSPickingList

WMSPickingList_OrderPick

WMSPickingList_OrderPick

WMSPickingLocations

WMSPickingLocations

WMSShipmentList

WMSShipmentList

IndirectCostOverview

IndirectCostOverview

PBAConfiguratedItem

PBAConfiguratedItem

PBAConsistOf

PBAConsistOf

ProdCalcTrans

ProdCalcTrans

ProdFinishGoodsInProgress

ProdFinishGoodsInProgress

ProdIndirectCostInProgress

ProdIndirectCostInProgress

ProdOverview

ProdOverview

ProdPicklist

ProdPicklist

ProdRawmaterialInProgress

ProdRawmaterialInProgress

ProdReport

ProdReport

ProdResourcesInProgress

ProdResourcesInProgress

ProdRouteCard

ProdRouteCard

ProdRouteJob

ProdRouteJob

SMAServiceOrderMargin

SMAServiceOrderMargin

SMAWorkNote

SMAWorkNote

JmgAbsenceCalendar

JmgPlannedAbsence

JmgAbsenceColumn

JmgAbsence

JmgEmplCard

JmgWorkerCard

JmgEmployeeReport

JmgEmployee

JmgEmployeeTimeSpec

Jmgpayspec

JmgEmplSignedIn

JmgEmplSignedIn

JmgFlexBalance

JmgFlexBalance

JmgFlexCheck

JmgFlexCheck

JmgIndirectActivity

JmgIndirectActivity

JmgIpcBarcode

JmgIpcBarcode

JmgIpcStat

JmgAbsenceStatistics

JmgPayAgreement

JmgPayAggreement

JmgPayStatTrans

JmgPayStatTrans

JmgProfile

JmgProfileDaily and JmgProfileWeek

JmgProjBarcode

JmgProjBarcode

JmgWorkPlanner_Employee

JmgWorkPlanner_Employee

JmgWorkPlanner_Profile

JmgWorkPlanner_Profile

Report Mapping to a Non-Reporting Services Implementation

The following table provides a mapping of reports from Microsoft Dynamics AX 2009 to a similar representation of data in Microsoft Dynamics AX 2012 in the form of list pages or export to Excel functionality from a form.

Microsoft Dynamics AX 2009 Report Name

Microsoft Dynamics AX 2012 Implementation Type

SysUtilElementsLog

Export to Excel

SysUpgradeEstimate

Export to Excel

EmplReportAdvance_RU

Export to Excel

RLedgerSheetEngine_ActAdjustVend

Export to Excel

PurchInvoice4Paym_RU, PurchInvoice4PaymOriginal_RU, PurchInvoice4PaymCopy_RU

Export to Excel

CustVendFacture_RU

Export to Excel

CustVendOutPaym_RU

Export to Excel

SalesInvoice4Paym_RU, SalesInvoice4PaymOriginal_RU, SalesInvoice4PaymCopy_RU

Export to Excel

PurchInvoice_RU

Export to Excel

RCashBook

Export to Excel

RCashDocJournal

Export to Excel

RCashOrder_RU

Export to Excel

RAssetCollationStatement

Export to Excel

RTax25Registers

Export to Excel

RTax25RegisterTrans

Export to Excel

LedgerBalanceSheetDimPrint6111_IL

Export to Excel

RPayAlimonySheetReport

Export to Excel

RPayDepositJournalReport

Export to Excel

RPaySheetListReport

Export to Excel

RPaySheetReport

Export to Excel

RPaySickListReport

Export to Excel

SalesSupplyCapacity

ListPage

 

 

Deprecated Microsoft Dynamics AX 2009 Reports in Microsoft Dynamics AX 2012 [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: November 22, 2011

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

SQL Server Reporting Services is now the primary reporting platform for Microsoft Dynamics AX. The out-of-the-box reports that are provided with Microsoft Dynamics AX have been converted to run on the Reporting Services platform. All reports were evaluated and in some cases a report will not be provided in this release. For example, multiple reports were consolidated into a single Reporting Services report or the same data could be printed from a form. For information about the Microsoft Dynamics AX 2009 mapping to Microsoft Dynamics AX 2012 reports, see Mapping Microsoft Dynamics AX 2009 Reports to the Microsoft Dynamics AX 2012 Version. For more information about the reports that will be provided, see Report catalog for Microsoft Dynamics AX. For a Microsoft Excel version of the report list, see Microsoft Dynamics AX 2012 and 2009 Report List.

Microsoft Dynamics AX 2012 and future releases will not provide the following reports:

Deprecated Reports List


  • SysRecordLevelSecurity
  • SysSecurity
  • SysSQLCheckSetup
  • SysSqlStatus
  • SysUserLogin
  • AxdGenerateAxdQueryHelper
  • NumberSequenceReference
  • XRefNamesReference
  • xRefPathCount
  • SysHelpIndexBrokenLinks
  • SysHelpIndexNoPages
  • SysHelpIndexPagesWithoutKeywords
  • SysTestJobTable
  • SysPrintCode
  • CustInPaymNO
  • CustInterestNote
  • Cheque
  • DimensionSetRulePerCollection
  • DimensionSetRulePerHierarchy
  • LedgerBalanceSheetDimPrint
  • LedgerBalanceSheetPrint
  • LedgerBudgetReport
  • LedgerBudgetReportWithRevisions
  • TaxPackagingTaxCust
  • TaxReconciliationReport
  • LedgerBudgetTrans
  • LedgerBalanceSheetDimPrint
  • LedgerBalanceSheetPrint
  • PurchInvoiceNF_BR
  • VendReportTransferPrice_BR
  • PurchPackingSlip
  • PurchPurchaseOrder
  • VENDORINDReport26
  • CustReportTransferPrice_BR
  • INDTDSCustTrans
  • INDTDSCustTransSum
  • SalesPackingSlip
  • CustVendCommunicationReport_IT ReplaceThisText
  • CustVendOutPaymNL_DisketteLabels
  • FreeTextInvoice_BR
  • SalesDeliverySlip_BR
  • Chequelayoutreport_BR
  • BankStatement11
  • BankReconciliation
  • ACOWrkCenterCapacity_BR
  • EUSalesListBE
  • RAssetReportInventoryCard
  • LedgerBalanceSheetDimPrint_CN
  • INDExciseCENVATCredit
  • INDExciseER
  • INDPLARegister
  • INDReceipt
  • INDReport26
  • INDReport27E
  • INDRG23APartI
  • INDRG23APartII
  • INDRG23APartIIReport
  • INDRG23APartIIReportN
  • INDRG23APartINew
  • INDRG23APartIReportN
  • INDRG23CPartI
  • INDRG23CPartII
  • INDRG23CPartIIReportN
  • INDRG23CPartIReportN
  • INDRG23D
  • NewINDRG23APartI
  • NewINDRG23APartII
  • NonSalaryReturn
  • RG23APartI
  • RG23CPartI
  • TDSReport27_IN
  • LedgerAccountSum_FR
  • LedgerInAccountStatementAT_EDIFACT
  • LedgerTransAccountVoucher_FR
  • ReplaceThisText
  • ReplaceThisText
  • TaxDeviation_BE
  • TaxListDiskReportBE
  • TaxPurchaseTaxDetails
  • TaxReport_UK
  • TaxReportEdivat
  • TaxReporting_TH
  • TaxWithholdMonthlyReportIT
  • AssetTaxStatistic
  • AssetBalanceReportColumns
  • AssetBookCompare
  • InventoryLedger
  • InventProdComR2
  • InventProdComR3
  • InventProdComR4
  • InventProdComR5
  • InventProdComR6
  • DispatchDocuement
  • WarrantyCreditNote
  • WarrantyDebitNote
  • TradeBLWIReport
  • ProjInvoice
  • IT_InventFiscalLIFOInternal
  • KMActionAlarm
  • KMActionPlan
  • KMBSCOverview
  • KMCollection
  • KMConnectionType
  • KMAction
  • KMGamePlan
  • KMGameplanLastNews
  • KMKnowledgeAccountSched
  • KMKnowledgeAccountStatement
  • KMKnowledgeJournal
  • KMKnowledgeOpenTransaction
  • KMKnowledgeTableIndicator
  • EPEmplTableList
  • HRMEPAbsenceEmplDue
  • HRMEPCourseCalendar
  • HRMEPCourseSessionTrack
  • HRMEPCourseType
  • HRMEPCourseType
  • HRMEPCourseTypeGroup
  • HRMEPDueLoan
  • ReplaceThisText
  • HRMEPEmployeeCV
  • HRMEPGoalAlarm
  • HRMEPVirtualNetworkDueCertificate
  • HRMEPVirtualNetworkIdByOrganization
  • HRMCourseCertificate
  • HRMDueLoan
  • HRMEducationGroup
  • HRMEmployeeEmploymentDismiss
  • HRMEmplResponsibility
  • HRMTeamsByOrganization
  • HRMVirtualNetworkDevelopmentPlan
  • HRMVirtualNetworkGroup
  • HRMVirtualNetworkIdByJob
  • Job
  • Position
  • KMEPQuestionnaireResultGroupGraph
  • KMEPQuestionnaireResultReport
  • KMEPQuestionnaireStatisticsLineList
  • KMQuestionnaireStatisticsResultPrint
  • CCStatReport
  • tutorial_ColourLines
  • tutorial_CustomizedSumDescription
  • tutorial_Date
  • tutorial_FontInfo
  • tutorial_HelloWorld
  • tutorial_Joins
  • tutorial_JoinsExtended
  • tutorial_NotesSpanningPages
  • tutorial_Positioning
  • tutorial_Prompt
  • tutorial_Properties
  • tutorial_Reset
  • tutorial_Resources
  • tutorial_RunbaseReport
  • tutorial_RunbaseReportStd
  • tutorial_SectionTemplateCust
  • tutorial_SectionTemplateVend
  • tutorial_SumPerSubField
  • tutorial_SumPerSubFieldDate
  • CompositeTestReport
  • LoTestResult
  • LoTestRLS
  • CustPhoneList
  • SalesCustItemStatistics
  • EPCustRevenue
  • smmActivityListDate
  • smmActivityNone
  • smmActivityPerQuotation
  • smmActivityTurnover
  • smmBusRel
  • smmBusRelActivities
  • smmBusRelActivityLast
  • smmBusRelContacts
  • smmBusRelTurnover
  • smmCampaignTarget
  • smmCampaignTargetResponse
  • smmPhoneInboundCalls
  • smmPhoneOutboundCalls
  • smmQuotationPrognosisLostCause
  • smmQuotationPrognosisWonCause
  • smmQuotationPrognosisSales
  • smmQuotationPrognosisProd
  • smmSalesUnitMembers
  • smmTMCallList
  • smmTMCallListStatus
  • smmTMCallListTelemarketingResponse
  • EPCustRevenue
  • EPProjJournalTransEmpl
  • TrvAdvanceReturn
  • TrvEmplAdvance
  • TrvEmplBalance
  • TrvRequisition
  • TrvExpenseList
  • ProjListPriceCost
  • ProjListPriceHourCost
  • ProjListPriceHourSales
  • ProjListPriceRevenueSales
  • ProjListProjConsumptionProjActivity
  • ProjListProjCustTable
  • ProjListProjProfitLossProjActivity
  • ProjListProjWIPProjActivity
  • ProjListTransHour
  • ProjPriceList
  • ProjListProjTransLayout
  • PurchBlanket
  • PurchCollectionLetterList
  • PurchHeading
  • PurchLinesExtended
  • PurchSupplyCapacity
  • PurchVariencesVendor
  • ReqExplosion
  • ReqPO
  • ReqTransOverview
  • PriceDiscCustExtern
  • PriceDiscTable
  • PriceList
  • PriceListAll
  • ReturnCycleTime
  • ReturnStatRanking
  • ReturnVolume
  • SalesBlanket
  • SalesByState
  • SalesContractShipment
  • SalesFreightSlip
  • InventSiteDimensionLinkAccountValidation
  • WorkCalendar
  • WorkTime
  • WrkCtrGroups
  • WrkCtrGroupsLedger
  • WrkCtrPartOfOperation
  • WrkCtrPartOfProdRoute
  • WrkCtrPartOfTaskGroup
  • WrkCtrProperty
  • WrkCtrTaskGroup
  • COSEDSStructure
  • COSHierarchy
  • COSLedgerReference_LT_CLT_Rep
  • COSLineStructure
  • COSVersion
  • EPInventTableByQty
  • EPInventTableBySales
  • EPInventTableByTime
  • EPSalesByPerson
  • InventDimAXReportAdapterTest
  • InventDimPhys
  • InventJournalTrans
  • InventJournalTransTransfer
  • InventStdCostVariance
  • InventTransList
  • BOMCostGroupSource
  • ForecastPurch
  • ForecastPurchActual
  • ForecastPurchItem
  • ForecastSales
  • ForecastSalesActual
  • InventBatchExpired
  • InventDimPosted
  • InventFiscalLIFOValuation
  • InventGroupPhys
  • InventGroupPosted
  • InventPackagingMaterialFeeCalc
  • InventPackagingMaterialWeights
  • InventPackagingMaterialWeightsPurch
  • InventSiteActivate
  • InventSpecPhys
  • InventSpecPosted
  • InventTransList
  • InventTransOnOrder
  • InventTransOrdered
  • RFIDInventSerialLabels
  • RFIDPalletLabels
  • SuppItemTable
  • WMSShipmentAddresses
  • WMSShipmentAddressesTransferOrders
  • PBAPartOf
  • PBAPrintGraphic
  • PBAPrintGraphicSalesQuotationTable
  • PBAPrintGraphicSalesTable
  • PBAUserProfiles
  • ProdLedgerConciliation
  • ProdBalanceAccount
  • ProdCalcVarianceTrans
  • ProdDelay
  • ProdEfficiencyProcess
  • ProdGroup
  • ProdInProcessCosting_NA
  • ProdJobCard
  • ProdJournalBOM
  • ProdJournalJob
  • ProdJournalProd
  • ProdJournalRoute
  • ProdParmCostEstimation
  • ProdParmHistoricalCost
  • ProdParmJobScheduling
  • ProdParmOprScheduling
  • ProdParmRelease
  • ProdParmReportFinished
  • ProdParmStartUp
  • ProdTableJour
  • ProdTablePostingCosting
  • ProdVariance
  • RouteCostCategory
  • RouteCostCategoryOverview
  • RouteOpr
  • RouteOprPartOfRoute
  • RouteOprTable
  • RouteTable
  • RouteVersion
  • SMAAccrueperiodLineReport
  • SMACustomerSchedule
  • SMAHourConsumption
  • SMARepairByTechnician
  • SMARepairObjectHistory
  • SMAResolutionByDiagnosis
  • SMAResolutionBySymptom
  • SMASalesPriceSubscription
  • SMAServiceAgreement
  • SMAServiceBOMHistory
  • SMAServiceBOMLines
  • SMAServiceContract
  • SMAServiceLevelAgreement
  • SMAServiceObjects
  • SMAServiceOrder
  • SMAServiceOrderCounters
  • SMAServiceStageProgress
  • SMAServiceTasks
  • SMASubscriptionCreateReport
  • SMASubscriptionReport
  • SMATemplateBOMLines
  • SysFilePrintout
  • SysReportAuto
  • ObjectPermissionsReport

Security and protection for reporting [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: October 10, 2011

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

The following topics explain how to help secure reports.

Security Considerations Creating a Report

Security settings for reports

 

Security Considerations Creating a Report [AX 2012]

Other Versions


This topic has not yet been rated – Rate this topic

Updated: September 30, 2011

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic describes security considerations for creating Reporting Services reports using the Microsoft Dynamics AX reporting tools.

Data Access


  • When accessing data from the Microsoft Dynamics AX database, it is recommended that you use the predefined Microsoft Dynamics AX data sources to ensure that appropriate security is enforced. For more information about the predefined Dynamics AX data source, seeReport Data Overview. When you use the query and report data provider data source types, all data access requests go through the Role and Task security system. When you use an external SQL or OLAP data source, security settings from the Role and Task security system are not applied when accessing data. In this case, you can use the role-based security features that are available from Microsoft SQL Server to secure the data. For more information about the security features from Microsoft SQL Server, see Securing Reports and Resources andSecuring Reporting Services in SQL Server 2008 Books Online.

Extensible Data Security


The extensible data security framework enables you to secure data in shared tables such that users have access to only the part of the table that is allowed by the enforced policy. Extensible data security policies, when deployed, are enforced on Microsoft Dynamics AX reports. For more information, see the Extensible Data Security white paper.

Note

When you bind a report to a report data provider class that writes data to a temp table, apply the XDS policy to the table that contains the source data for the report, not the temp table.

Projects and Build


  • When building from the command line, Microsoft Dynamics AX reporting tools does not perform any checks for unsafe entries in the project file. The project file entries are not analyzed by Microsoft Dynamics AX reporting tools from a security perspective. Therefore, it is strongly recommended that you do not build third-party reporting projects from the command line. Build from the command line only in trusted scenarios.
  • Microsoft Visual Studio, with the help of MSBuild, analyzes unsafe entries in a project file when it is loaded and warns you about them. An example of an unsafe entry is the redirection of the project output path to a system folder. For example, the output path could be redirected to C:\Windows, which could overwrite a system file. Or, the output path could be redirected so as to overwrite a default MSBuild property for Microsoft Dynamics AX reporting tools projects. When attempting to open a reporting project that contains unsafe entries, a dialog box displays that prompts you not to open the project. If you experience this, you should inspect the unsafe entries as you decide whether to open the project.
  • Project files, model files, code files, and referenced assemblies should always be placed in a safe location whether it is a local folder, network share, or source code control database. The default project location for Microsoft Visual Studio projects is \My Documents\Visual Studio 2010\Projects, which is protected by the administrator and current user access control lists.
  • Threat detection in a business logic project is limited to the functionality provided by standard C# and Visual Basic project systems in Microsoft Visual Studio. The current implementation of the C# and Visual Basic project systems displays only the first detected threat in the project file. Therefore, if you skip the threat and load the project file, all other threats that exist in the project file will be skipped.
  • The build cache file has an internal binary structure. The first violation of this structure that is discovered will force the compilation to regenerate the file. If the file is modified without violating the structure, the issue will not be mitigated, but you can invoke a clean build to regenerate the build cache file to eliminate the threat.

Assembly Access on a Report Server


  • If an administrator grants an assembly access to the SessionManager API (which wraps .NET Business Connector), then the assembly must be given the AxSessionPermissionSet in the rssrvpolicy.config file on the report server.

Note

This is the recommended setting for business logic assemblies (depending on the main report project name length, either .BusinessLogic.dll or .BL.dll), and it is added by default for the business logic assemblies that are created for a deployed reporting project. This includes the business logic assemblies from referenced reporting projects.

  • Giving a custom assembly full trust in the report server security policy file allows the assembly to directly access .NET Business Connector running under the Business Connector proxy account. This is an account that has elevated privileges that allows for access to the LogonAsfunctionality. In this case, the assembly could impersonate any user and access their records.
  • Granting a custom assembly ReflectionPermission with MemberAccess could allow the assembly to retrieve cached sessions from the session cache. Those sessions are logged in for a specific user, and the custom assembly could have access to that user’s data.
  • The following code must be present in the custom code section of the RDL file if the report is expected to make use of the SessionManagerAPI:

    VB

    Protected
    Overrides
    Sub OnInit()

    Microsoft.Dynamics.Framework.Reports.SessionManager.BeginRequest(Report)

    End
    Sub

  • Entries in the security policy file will not be created for any assemblies referenced by business logic assemblies.

Security settings for reports [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: November 20, 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

To grant users access to reports, you must configure security settings in Microsoft Dynamics AX, Microsoft SQL Server Reporting Services or Microsoft SharePoint, and Microsoft SQL Server Analysis Services. This topic describes the tasks that you must complete in each product.

Configure security settings in Microsoft Dynamics AX


To configure security settings in Microsoft Dynamics AX, complete the following tasks:

  • Verify that each Microsoft Dynamics AX role is assigned the correct duties and privileges, so that users (who are assigned to the roles) can access the appropriate reports. For more information, see Create or modify a security role.
  • Assign users to Microsoft Dynamics AX roles. For more information, see Assign users to security roles.
  • Help secure the data that is displayed on reports. For more information, see Set up data security.

Configure security settings in Reporting Services


If you are running Reporting Services in native mode, complete the following tasks to configure security settings in Reporting Services.

Assign users and groups to the DynamicsAXBrowser role

Follow these steps to assign users and groups to the DynamicsAXBrowser role on the Report Manager website.

  1. Open the Report Manager website for the Reporting Services instance. By default, the URL is http://%5BSSRSServerName%5D:80/Reports_%5BSSRSInstanceName%5D.
  2. Click the DynamicsAX folder.
  3. Click Folder Settings.
  4. Click Security.
  5. Click New Role Assignment.
  6. Enter the Active Directory user name or group to assign to the DynamicsAXBrowser role.
  7. Select the DynamicsAXBrowser role.
  8. Click OK.

Restrict access to report folders and reports

We recommend that you use the security features and tools that are included in Reporting Services to help control access to report folders and published reports. For detailed conceptual information and step-by-step tutorials that can help you administer security in Reporting Services, see the SQL Server documentation.

Configure security settings in SharePoint


If you are running Reporting Services in SharePoint integrated mode, you must grant users permission to view reports in SharePoint. To grant this permission, grant users Read permission to the document library that stores the reports. Alternatively, if the document library inherits permissions from the site, you can grant users Read permission to the site. The following procedure describes how to grant users Read permission to the site.

Important

If the SharePoint site is configured for claims-based authentication, you must also grant the following accounts Read permission to the document library or site:

  • The account that is used as the Business Connector proxy
  • The account that is used to run the Microsoft Dynamics AX Application Object Server (AOS) service.
  1. Open your browser and navigate to the SharePoint site that contains the document library that stores the reports.
  2. Click Site Actions > Site Permissions.
  3. Click Grant Permissions. The Grant Permissions window is displayed.
  4. In the Users/Groups field, enter the Active Directory names of the users or groups that you want to view reports.
  5. In the Grant Permissions area, select the Grant users permission directly option.
  6. Select the Read check box.

Note

If you want Enterprise Portal users to be able to filter reports using a custom parameter value, select the Design check box. For more information about the permissions required to use Enterprise Portal, see Enable users to access Enterprise Portal.

  1. Click OK.

Configure security settings in Analysis Services


Some reports use Analysis Services cubes to access data. Before users can view data on these reports, you must assign the users to roles in Analysis Services. For more information, see Grant users access to cubes.

Operation of reporting [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: October 12, 2011

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

The following topics explain how to use the default reports that are included with Microsoft Dynamics AX. The topics also explain how to create your own custom reports.

How to work with the reports that are provided by Microsoft Dynamics AX

How to create a custom report

How to work with the reports that are provided by Microsoft Dynamics AX [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: October 11, 2011

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Microsoft Dynamics AX provides hundreds of preconfigured reports that you can use to view and analyze business data. The following topics explain how you can work with these reports.

Print a report

Print a report on a recurring basis

Print a report during off-peak hours

Print a report from the archive

Filter the data on a report

Sort the data on a report

 

Print a report [AX 2012]

1 out of 3 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Microsoft Dynamics AX includes hundreds of preconfigured reports that you can use to view and analyze business data. The following procedure explains how to print a report.

  • Open the module that contains the data to print.
  • On the module’s area page, in the Reports section, click the report to print.
  • A form is displayed, where you can enter parameters to filter the data that is displayed on the report. Enter any parameters that you require. For more information about how to enter parameters to filter the data, see Filter the data on a report.
  • Click Destinations …. The Print destination settings form is displayed.
  • Select the destination to print the report to. The following table lists the options and describes the additional steps that you must follow for each option.

Print destination

Additional steps

Print archive

  • In the Page range area, specify the pages of the report to print.
  • Click OK to close the Print destination settings form.

For information about how to print a report from the archive, see Print a report from the archive.

Screen

  • If you want to save a copy of the report in the print archive, select the Save in print archive? check box.
  • In the Page range area, specify the pages of the report to print.
  • Click OK to close the Print destination settings form.

Note

When you print a report to the screen, you may not be able to view all the data on the report if the text size on your computer is set to Larger – 150% in the Control Panel (Start > Control Panel > Appearance and Personalization >Display).

Printer

  • If you want to save a copy of the report in the print archive, select the Save in print archive? check box.
  • In the Name field, select the printer to print to.
  • Click Properties to configure options for the printer. Note the following points:
    • For those using Microsoft Dynamics AX 2012 or Microsoft Dynamics AX 2012 Feature Pack: If you change the page layout orientation or the paper size, your change will not be honored when the report is printed.
    • For those using Microsoft Dynamics AX 2012 R2: If you change the page layout orientation or the paper size, you must select the Override default settings check box in order for your changes to take effect.
  • In the Page range area, specify the pages of the report to print.
  • In the Copies area, enter the number of copies to print.
  • Click OK to close the Print destination settings form.

File

  • If you want to save a copy of the report in the print archive, select the Save in print archive? check box.
  • In the File name field, enter the name and location of the file to save the report to.
  • In the File format field, select the format of the file that the report is saved to.
  • In the Page range area, specify the pages of the report to print.
  • Click OK to close the Print destination settings form.

E-mail

  • If you want to save a copy of the report in the print archive, select the Save in print archive? check box.
  • In the To and Cc fields, specify who receives the email message by entering email addresses.
  • In the Subject field, enter the subject of the email message.
  • In the File format field, select the format of the file that the report is saved to. This file is attached to the email message that is sent.
  • In the Page range area, specify the pages of the report to print.
  • Click OK to close the Print destination settings form.
  • Click OK to print the report to the selected destination.

 

 

Print a report on a recurring basis [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: August 14, 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Microsoft Dynamics AX includes hundreds of preconfigured reports that you can use to view and analyze business data. The following procedure explains how to configure Microsoft Dynamics AX to automatically print a report for you on a recurring basis. For example, Microsoft Dynamics AX can send a specific report to you and your team members every Monday morning by email.

  • Open the module that contains the data to print.
  • On the module’s area page, in the Reports section, click the report to print.
  • A form is displayed, where you can enter parameters to filter the data that is displayed on the report. Enter any parameters that you require. For more information about how to enter parameters to filter the data, see Filter the data on a report.
  • Click Destinations …. The Print destination settings form is displayed.
  • Select the destination to print the report to. The following table lists the options and describes the additional steps that you must follow for each option.

Print destination

Additional steps

Print archive

  • In the Page range area, specify the pages of the report to print.
  • Click OK to close the Print destination settings form.

For information about how to print a report from the archive, see Print a report from the archive.

Screen

Do not select this option. Because this report is printed as part of a batch, you should not print this report to the screen.

Printer

  • If you want to save a copy of the report in the print archive, select the Save in print archive? check box.
  • In the Name field, select the printer to print to.
  • Click Properties to configure options for the printer. Note the following points:
    • For those using Microsoft Dynamics AX 2012 or Microsoft Dynamics AX 2012 Feature Pack: If you change the page layout orientation or the paper size, your change will not be honored when the report is printed.
    • For those using Microsoft Dynamics AX 2012 R2: If you change the page layout orientation or the paper size, you must select the Override default settings check box in order for your changes to take effect.
  • In the Page range area, specify the pages of the report to print.
  • In the Copies area, enter the number of copies to print.
  • Click OK to close the Print destination settings form.

File

  • Create the destination file.

    For example, assume that you want to save the Customers report as a PDF file. In this case, you would create a file that is named Customers.pdf.

    You can save a report as a CSV, Microsoft Excel, HTML, image, MTHML, PDF, or XML file.

  • If you want to save a copy of the report in the print archive, select the Save in print archive? check box.
  • In the File name field, enter the path to the destination file. The path must be entered in the following format:\\Server\Volume\Directory\File.

Note

The AOS service account for the Microsoft Dynamics AX batch server must have access to the destination file.

  • In the File format field, select the format of the destination file.
  • In the Page range area, specify the pages of the report to print.
  • Click OK to close the Print destination settings form.

E-mail

  • If you want to save a copy of the report in the print archive, select the Save in print archive? check box.
  • In the To and Cc fields, specify who receives the email message by entering email addresses.
  • In the Subject field, enter the subject of the email message.
  • In the File format field, select the format of the file that the report is saved to. This file is attached to the email message that is sent.
  • In the Page range area, specify the pages of the report to print.
  • Click OK to close the Print destination settings form.
  • Click the Batch tab.

    On this tab, you configure a batch job. A batch job is a task that is submitted to the instance of the Microsoft Dynamics AX server for automatic processing.

  • Select the Batch processing check box.
  • In the Task description field, accept the default description of this batch job or enter a new description.
  • From the Batch group list, select the batch group that this batch job will be a part of.
  • Click Recurrence. The Recurrence form is displayed.
  • Specify how often the report is printed. Then click OK to close the Recurrence form.
  • Click Alerts. The Set up alerts for batch jobs form is displayed.
  • Specify how and when you want to receive alerts for the batch job. Then click OK to close the Set up alerts for batch jobs form.
  • Click OK to print the report to the selected destination on a recurring basis.

 

 

 

Print a report during off-peak hours [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: August 14, 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Occasionally, you may have to print an especially long report, such as a report that contains hundreds of rows of data. In this case, it may be best to print the report during off-peak hours, when few users are logged on to Microsoft Dynamics AX. The following procedure explains how to schedule a report to be printed during off-peak hours.

  • Open the module that contains the data to print.
  • On the module’s area page, in the Reports section, click the report to print.
  • A form is displayed, where you can enter parameters to filter the data that is displayed on the report. Enter the parameters that you require. For more information about how to enter parameters to filter the data, see Filter the data on a report.
  • Click Destinations …. The Print destination settings form is displayed.
  • Select the destination to print the report to. The following table lists the options and the additional steps that you must follow for each option.

Print destination

Additional steps

Print archive

  • In the Page range area, specify which pages of the report to print.
  • Click OK to close the Print destination settings form.

For information about how to print a report from the archive, see Print a report from the archive.

Screen

Do not select this option. Because this report is printed as part of a batch, do not print the report to the screen.

Printer

  • If you want to save a copy of the report in the print archive, select the Save in print archive? check box.
  • In the Name field, select the printer to print to.
  • Click Properties to configure options for the printer. Note the following points:
    • For those using Microsoft Dynamics AX 2012 or Microsoft Dynamics AX 2012 Feature Pack: If you change the page layout orientation or the paper size, your change will not be honored when the report is printed.
    • For those using Microsoft Dynamics AX 2012 R2: If you change the page layout orientation or the paper size, you must select the Override default settings check box in order for your changes to take effect.
  • In the Page range area, specify the pages of the report to print.
  • In the Copies area, enter the number of copies to print.
  • Click OK to close the Print destination settings form.

File

  • Create the destination file.

    For example, assume that you want to save the Customers report as a PDF file. In this case, you would create a file that is named Customers.pdf.

    You can save a report as a CSV, Microsoft Excel, HTML, image, MTHML, PDF, or XML file.

  • If you want to save a copy of the report in the print archive, select the Save in print archive? check box.
  • In the File name field, enter the path to the destination file. The path must be entered in the following format:\\Server\Volume\Directory\File.

Note

The AOS service account for the Microsoft Dynamics AX batch server must have access to the destination file.

  • In the File format field, select the format of the destination file.
  • In the Page range area, specify the pages of the report to print.
  • Click OK to close the Print destination settings form.

E-mail

  • If you want to save a copy of the report in the print archive, select the Save in print archive? check box.
  • In the To and Cc fields, specify who receives the email message by entering email addresses.
  • In the Subject field, enter the subject of the email message.
  • In the File format field, select the format of the file to save the report to. This file is attached to the email message that is sent.
  • In the Page range area, specify which pages of the report to print.
  • Click OK to close the Print destination settings form.
  • Click the Batch tab.

    On this tab, you configure a batch job. A batch job is a task that is submitted to the instance of the Microsoft Dynamics AX server for automatic processing.

  • Select the Batch processing check box.
  • In the Task description field, accept the default description of this batch job or enter a new description.
  • From the Batch group list, select the batch group that this batch job will be a part of.
  • Click Recurrence. The Recurrence form is displayed.
  • Schedule the date and time that the report is printed by following these steps:
    • From the Time zone list, select your time zone.
    • In the Starting time field, enter the time to print the report. For example, to print the report during off-peak hours, you may want to enter 2:00 A.M.
    • In the Starting date field, select the day to print the report.
    • If you want to print this report on a recurring basis, specify a recurrence pattern by entering a count or a date range. Then select the days on which the report is printed.
    • Click OK to close the Recurrence form.
  • Click Alerts. The Set up alerts for batch jobs form is displayed.
  • Specify how and when you want to receive alerts for the batch job. Then click OK to close the Set up alerts for batch jobs form.
  • Click OK to print the report to the selected destination on a recurring basis.

 

 

 

Print a report from the archive [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: October 11, 2011

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

If you saved a report to the print archive, you can use the following steps to print the report from the archive.

  1. Click Organization administration > Inquiries > Print archive.
  2. On the Overview tab, select the report to print.
  3. Click Print preview. The report is displayed in a PDF viewer, such as Adobe Acrobat.

Note

To print the report, you must open the report in a PDF viewer. You cannot print the report from the print archive by clicking the Printbutton.

  1. Print the report from the PDF viewer.

 

 

Filter the data on a report [AX 2012]

0 out of 3 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

By filtering the data that is displayed on a report, you can view only the data that is important to you. The following procedure shows how to filter the data on the Customers report. You can modify this procedure to filter the data on the report that you are working with.

  1. Open the module that contains the data that you want to print. For example, to print the Customers report, open the Accounts receivablemodule.
  2. On the module’s area page, in the Reports section, click the report that you want to print. For example, to print the Customers report, clickCustomer > Customers.

    A form is displayed that lists the fields that the data on the report is filtered by. The form also displays the destination that the report is printed to.

  3. Click Select. An inquiry form is displayed. This form is used to filter the data on the report.
  4. Click the Range tab. The Range tab displays the fields that you can filter the data on the report by.
  5. To add a field, click Add. Then follow these steps:
    1. In the Table field, select the table that contains the field that you want to filter data by.
    2. In the Field field, select the field that you want to filter data by.
    3. In the Criteria field, select the data that you want to display on the report.

    For example, suppose you want to filter the Customers report so that it displays only those customers who receive a discount of 5 percent when they pay their bill in 30 days. In this scenario, you would follow these steps:

    1. In the Table field, select Customers.
    2. In the Field field, select Customers.
    3. In the Criteria field, select 0.5%D30.
  6. To remove a field, select the row that contain the field and then click Remove.
  7. Click OK to close the inquiry form.
  8. Click Destinations … to specify how you want to print the report.
  9. Click OK to print the report.

 

Sort the data on a report [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: October 11, 2011

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

You can sort the data that is displayed on a report. The following procedure shows how to sort the data on the Customers report. You can modify this procedure to sort the data on the report that you are working with.

  1. Open the module that contains the data to print. For example, to print the Customers report, open the Accounts receivable module.
  2. On the module’s area page, in the Reports section, click the report to print. For example, to print the Customers report, click Customer >Customers.

    A form is displayed that lists the fields that the data on the report is filtered by. The form also displays the destination that the report is printed to.

  3. Click Select. An inquiry form is displayed. This form is used to sort the data on the report.
  4. Click the Sorting tab. The Sorting tab displays the fields that you can sort the data on the report by.
  5. To add a field, click Add. Then follow these steps:
    1. In the Table field, select the table that contains the field that you want to sort the data by.
    2. In the Field field, select the field that you want to sort the data by.
    3. In the Search direction field, select whether you want to sort the data in ascending or descending order.

    For example, suppose you want to sort the Customers report by the customer’s credit limit. In this scenario, you would follow these steps:

    1. In the Table field, select Customers.
    2. In the Field field, select Customers.
    3. In the Criteria field, select Credit limit.
    4. In the Search direction, select Ascending or Descending.
  6. To remove a field, select the row that contain the field and then click Remove.
  7. Click OK to close the inquiry form.
  8. Click Destinations … to specify how you want to print the report.
  9. Click OK to print the report.

 

 

How to create a custom report [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: December 3, 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

There are several ways to create a custom report. The following table lists the tools that you can use to create a custom report if you are a system administrator or an application user.

Category

Tool that is used to create the report

Format of the report

For more information

Transactional reports

Transactional reports retrieve data from the transaction processing database for Microsoft Dynamics AX.

Microsoft Dynamics AX list page

Excel worksheet

Use a list page

Microsoft Dynamics AX auto-report wizard

Reporting Services report

Create a report by using the Microsoft Dynamics AX auto-report wizard

Microsoft Dynamics AX add-in for Excel

Excel worksheet

Using the Microsoft Dynamics AX Add-in for Excel

Management Reporter for Microsoft Dynamics ERP

Management Reporter report

Microsoft Management Reporter: Installation, Migration, and Configuration Guides

Analytical reports

Analytical reports retrieve data from Microsoft SQL Server Analysis Services cubes.

Excel

Excel worksheet

Create a report by using the Excel data connection wizard to connect to a cube

SQL Server Report Builder

Reporting Services report

Create a report by using SQL Server Report Builder to connect to a cube

SQL Server Power View

Reporting Services report

Create a report by using SQL Server Power View to connect to a cube

 

Create a report by using the Microsoft Dynamics AX auto-report wizard [AX 2012]

3 out of 5 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

Auto-reports are preconfigured reports that you can generate by clicking File > Print > Print in a Microsoft Dynamics AX form. You can quickly generate an auto-report for use once, or you can create and save a custom auto-report that can be reused later. This topic describes both of these scenarios.

Scenario: Quickly print a report for one-time use


You can use the auto-report functionality to quickly generate a report that displays the data that you are currently viewing in a Microsoft Dynamics AX form. The following procedure explains how to do so.

  • Open the Microsoft Dynamics AX form that contains the data to print.
  • Click File > Print > Print.

    The Autoreport form is displayed.

  • To filter or sort the data on the report, click Select.

    An inquiry form is displayed. In this form, you can complete the following tasks:

    • Filter the data – To filter the data that is displayed on the report, click the Range tab. For information about how to filter the data, see Filter the data on a report.
    • Sort the data – To sort the data that is displayed on the report, click the Sorting tab. For information about how to sort the data, see Sort the data on a report.
    • Specify date options – To filter the data that is displayed on the report based on date information, click the Date options tab. Specify whether you want the report to display all active records, records that are active as of a specific date, or records that are active in a specific date range.
  • Click OK to return to the Autoreport form.
  • Click OK to print the report to the screen.

Scenario: Create a custom report for reuse


You can use the auto-report functionality to create a custom report that is saved so that it can be reused later. The following procedure explains how to do so.

  • Open the Microsoft Dynamics AX form that contains the data to print.
  • Click File > Print > Print.

    The Autoreport form is displayed.

  • Click Modify… > New.

    The Autoreport Wizard is displayed.

  • The wizard displays the names of tables, fields, and methods. If you are more familiar with the system names of tables, fields, and methods (for example, CustTable), than the names that appear in the user interface (for example, Customer), select the Show system names of tables, fields, and methods check box.

    Click Next.

  • The Report name page is displayed. Enter a name for the report. Click Next.
  • The Select fields page is displayed. Use the arrows to specify which fields should be included on the report. Use the Up and Down buttons to indicate the order in which they should appear. Click Next.

Note

If a field does not contain any data, it will not be included in the report.

  • If the report includes a field that contains real numbers or integers, the Summation on fields page is displayed. Specify which fields should contain sum values. Click Next.
  • The Report layout page is displayed. Select a template to specify the layout of the report, and a template to specify the layout of tables. Click Next.
  • Click Finish to complete the wizard. The Autoreport form is redisplayed.
  • To filter or sort the data on the report, click Select.

    An inquiry form is displayed. In this form, you can complete the following tasks:

    • Filter the data – To filter the data that is displayed on the report, click the Range tab. For information about how to filter the data, see Filter the data on a report.
    • Sort the data – To sort the data that is displayed on the report, click the Sorting tab. For information about how to sort the data, see Sort the data on a report.
    • Specify date options – To filter the data that is displayed on the report based on date information, click the Date options tab. Specify whether you want the report to display all active records, records that are active as of a specific date, or records that are active in a specific date range.
  • Click OK to return to the Autoreport form.
  • Click OK to print the report to the screen.

    The report settings are automatically saved. The next time that you open the form that you opened in step 1, you can generate and print this report by clicking File > Print > Print.

 

 

Create a report by using the Excel data connection wizard to connect to a cube [AX 2012]

0 out of 1 rated this helpful – Rate this topic

Updated: January 16, 2013

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

 Your opinion counts! We are working to improve Microsoft Dynamics AX documentation. Take our survey.

The following procedure explains how to use Microsoft Excel to create a custom report that uses a Microsoft SQL Server Analysis Services cube as a data source.

  1. Open Excel.
  2. Click the Data tab.
  3. Click From Other Sources > From Analysis Services. The Data Connection Wizard is displayed.
  4. On the Connect to Database Server page, enter the name of the server that is running Analysis Services and then enter credentials to access that server. Click Next.
  5. On the Select Database and Table page, follow these steps:
    1. Select the Analysis Services database that contains the cubes. By default, the database name is Dynamics AX of Dynamics AX initial.
    2. Select the cube that contains the data to include on the report.
    3. Click Next.
  6. On the Save Data Connection File and Finish page, follow these steps:
    1. In the File Name field, enter a name for the data connection file that is created. This file can be used to connect to the cube in the future.
    2. Click Browse to specify where to save the data connection file.
    3. In the Description field, enter a description to help identify the type of data that this file connects to.
    4. In the Friendly Name field, enter a user-friendly name for the data connection file.
    5. Click Finish to close this wizard.
  7. The Import Data dialog box is displayed. Select whether you want to view the cube data in a PivotTable report, or in a PivotChart and PivotTable report. For more information about these options, see the Excel Help. Click OK.
  8. To add fields to the report, select the fields in the PivotTable Field List pane.

    For more information about how to create PivotTable and PivotChart reports, see the Excel documentation. To see an example of this procedure that uses the Microsoft Dynamics AX General ledger cube, see Walkthrough: Analyzing Cube Data in Excel.

Create a report by using SQL Server Report Builder to connect to a cube [AX 2012]

3 out of 4 rated this helpful – Rate this topic

Updated: November 1, 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic helps you create a custom report that uses an online analytical processing (OLAP) cube as a data source. To complete the procedures in this topic, you must have access to Report Builder, which is a component of Microsoft SQL Server Reporting Services.

For more information about Report Builder and how to access it, see the SQL Server documentation.

Open Report Builder


If Reporting Services is running in native mode, follow these steps to open Report Builder from the Report Manager website.

  1. Go to the Report Manager website. By default, the URL is http://%5BSSRSServerName%5D:80/Reports.
  2. Click the Report Builder button.

    Report Builder opens and displays the Getting Started wizard to help you design the report. For information about how to design a report by using the Getting Started wizard, see the next section of this topic.

If Reporting Services is running in SharePoint integrated mode, follow these steps to open Report Builder from the SharePoint website.

  1. Go to the SharePoint website.
  2. Go to the document library that contains the Microsoft Dynamics AX reports.
  3. Click the Documents tab.
  4. Click New Document > Report Builder Report.

Note

If the Report Builder Report option is not available, your system administrator may need to add the Report Builder content type to the document library. This process is described in Add Report Server Content Types to a Library (Reporting Services in SharePoint Integrated Mode) in the SQL Server documentation.

  1. Report Builder opens and displays the Getting Started wizard to help you design the report. For information about how to design a report by using the Getting Started wizard, see the next section on this topic.

Design a report


When you open Report Builder, the Getting Started wizard is displayed. This wizard helps you design a report. Follow these steps to complete the wizard.

  1. On the first page of the Getting Started wizard, click New Report, and then select the type of report to design. This procedure explains how to create a table or matrix report.
  2. On the Choose a dataset page, click Create a dataset. Click Next.
  3. On the Choose a connection to a data source page, click New.
  4. In the Data Source Properties window, follow these steps:
    1. In the Name field, enter a name for the data source.
    2. From the Select connection type list, select Microsoft SQL Server Analysis Services.
    3. Click Build.
  5. In the Connection Properties window, follow these steps:
    1. In the Server name field, enter the name of the server that runs Analysis Services.
    2. From the Select or enter a database name list, select the database that contains the Microsoft Dynamics AX cubes. By default, the name of this database is Dynamics AX or Dynamics AX initial.
    3. Click OK.
  6. In the Data Source Properties window, click Test Connection to verify that the data source is configured correctly. After the test is successful, click OK to close the window.
  7. The Choose a connection to a data source page is redisplayed. Click Next.
  8. On the Design a query page, select the cube that contains the data to include on the report. Then select the dimensions, measures, or key performance indicators (KPIs) to include on the report.

    For example, to create a report that shows the balance of each General ledger account, you would follow these steps:

    1. Select General ledger cube.
    2. Expand the Measures > Ledger transactions node. Then drag the General ledger amount – accounting currency measure onto the design surface.
    3. Expand the Chart of accounts node. Then drag the Account type and number dimension onto the design surface.

    Click Next.

  9. On the Arrange fields page, specify whether the fields should be formatted as rows, columns, or values by dragging each field to the appropriate box.

    For example, to continue the example that was described in the previous step, you would follow these steps:

    1. Drag the Account_type field to the Row groups box.
    2. Drag the Main_account_name field to the Row groups box.
    3. Drag the General_ledger_amount_accounting_currency field to the Values box.

    Click Next.

  10. On the Choose the layout page, select layout options for the report. Click Next.
  11. On the Choose a style page, select a style to specify how the report will be formatted. Click Finish.

    The design for the report is displayed in Report Builder. For information about how to generate, or run, the report, see the next procedure.

Generate a report


When you have finished designing a report, you can generate, or run, the report. Click the Run button in the Report Builder toolbar. The report will be displayed.

Create a report by using SQL Server Power View to connect to a cube [AX 2012]

This topic has not yet been rated – Rate this topic

Updated: February 20, 2013

Applies To: Microsoft Dynamics AX 2012 R2

Power View, a feature of Microsoft SQL Server 2012, is a tool that you can use to create highly-interactive, ad-hoc reports. This topic helps you create a Power View report that displays data from a Microsoft SQL Server Analysis Services cube. To create the report, you must first select the cube that you want to use, and create a data source to connect to that cube. Then, you can create the Power View report by selecting the fields that you want to display on the report. Finally, you can display the report in a web part on a Role Center page in Microsoft Dynamics AX.

Prerequisites


This topic assumes that the following software has been installed:

  • SQL Server 2012 – A version of SQL Server 2012 that supports Power View for multidimensional models must be installed in your environment. For more information about supported versions, see the disclaimer at the end of this topic.
  • Role Centers – Role Centers are deployed when you install Enterprise Portal. For more information about how to install and configure Enterprise Portal, see Checklists for deploying Enterprise Portal sites.

Note

Role Centers must be deployed to an environment that supports Power View for multidimensional models.

  • Analysis Services cubes – The cubes that are included with Microsoft Dynamics AX must be deployed to your Analysis Services server. For more information about how to deploy the cubes and assign users to them, see Checklist: Configure Analysis Services and deploy cubes.

Create a data source to connect to a cube


The first step is to determine which cube contains the data that you want to display on the report. To view the data that is contained in each cube, see Cube and KPI reference for Microsoft Dynamics AX 2012 R2.

After you determine which cube you want to use, you may need to create a data source to connect to that cube. By default, data sources that connect to the Accounts payable, Accounts receivable, General ledger, and Sales cubes have been created for you. If you want to display data from any other cube, you must use the following procedure to create the data source.

  1. Open your browser and go to the Enterprise Portal site. The URL for the Enterprise Portal site is typically http://%5BSharePointServerName%5D/sites/DynamicsAX.
  2. Go to the Power View Reports folder. The URL for this folder is typically http://%5BSharePointServerName%5D/sites/DynamicsAX/Power%20View%20Reports.
  3. Click Documents > New Document > Report Data Source. The Data Source Properties page is displayed.
  4. In the Name field, enter a name for the data source. For example, if the data source will connect to the Retail cube, you may want to name the data source Retail cube.
  5. In the Data Source Type area, select Microsoft BI Semantic Model for Power View.
  6. In the Connection string area, enter the following connection string:

    Provider=MSOLAP.4;Integrated Security=SSPI;Persist Security Info=True;Data Source=[ServerName];Initial Catalog=[DatabaseName];Locale identifier=[LocaleID];Cube=[CubeName]

    The following table lists the documentation conventions that are used in the connection string.

Value

Description

[ServerName]

The name of the server on which Analysis Services is installed.

[DatabaseName]

The name of the Analysis Services database that contains the cube that you want to connect to.

[LocaleID]

The identifier that designates the language of the labels to display on the report. For example, if you want measures and dimensions to be shown in German, you must add German translations to the cube and specify the locale identifier for German.

For more information about how to add translations to a cube, see How to: Update an Existing SQL Server Analysis Services Project. For a list of the locales that are supported by both Enterprise Portal and SharePoint, see Install Enterprise Portal on a stand-alone server.

[CubeName]

The name of the cube that contains the data that you want to display on the report.

For example, if you want to connect to the Retail cube that is provided with Microsoft Dynamics AX, the default connection string is:

Provider=MSOLAP.4;Integrated Security=SSPI;Persist Security Info=True;Data Source=[ServerName];Initial Catalog=Dynamics AX initial;Locale identifier=1033;Cube=Retail cube

  1. In the Credentials area, select Windows authentication (integrated) or SharePoint user.
  2. Click Test Connection to verify the connection to the cube.
  3. In the Availability area, select the Enable this data source check box.
  4. Click OK. The data source is created.

Create the report


To create and design the Power View report, complete the following procedure.

  1. Go to the Power View Reports folder. The URL for this folder is typically http://%5BSharePointServerName%5D/sites/DynamicsAX/Power%20View%20Reports.
  2. Click the data source that you created in the previous procedure. A blank, untitled Power View report is displayed in your browser.
  3. To add fields to the report, select the fields in the Field List pane, or drag the fields onto the report.

    For example, suppose that you want to create a report that shows sales amounts for your retail stores. In this scenario, you would:

    1. Expand the Retail channel node and select Retail channel – Name.
    2. Expand the Customer invoice lines node, and select Customer invoice line amount – accounting currency.
    3. Expand the Date node and drag Month to the Filters area of the report.
  4. Enter a name for the report in the title area.
  5. Use the options on the StylesDesign, and Layout tabs to format the report as necessary. For more information about how to use the Power View options to format the report, see Power View Design Experience in the SQL Server documentation.
  6. Save the report.

Display the report on a Role Center page


To display the report in a web part on a Role Center page, complete the following procedure.

  1. Open the Microsoft Dynamics AX client.
  2. Click System administration > Common > Users > User profiles. The User profiles form is displayed.
  3. Select the Role Center that will display the report.
  4. Click View role center. Your browser opens and displays that Role Center page.
  5. Click Site Actions > Edit Page. The page is displayed in design mode.
  6. Find the location where you want to display the report, and click Add a Web Part in that area. The top of the page now displays an area where you can select the web part that you want to add.
  7. To select the web part that you want to add, do the following:
    1. In the Categories area, select Microsoft Dynamics AX.
    2. In the Web Parts area, select SQL Server Power View.
    3. In the About the Web Part area, click Add.

    The SQL Server Power View web part is displayed on the page.

  8. In the web part’s menu, click Edit Web Part. The web part’s properties pane, where you can configure the web part, is displayed on the right side of the page.
  9. To configure the web part, do the following:
    1. In the Select a report area, click the Browse icon to select the Power View report that you created.
    2. In the Title field, enter an appropriate name for the web part.
    3. Set the Height and Width properties so that the web part is displayed optimally on the page.
    4. Click OK to save your changes.

Disclaimer


Important

Power View is an ad-hoc data exploration and visualization experience in Microsoft SQL Server 2012 Reporting Services. To use Power View reports with Microsoft Dynamics AX 2012 R2 data stored in Business Intelligence Semantic Model multidimensional mode, you must have a generally available release of Microsoft SQL Server 2012 that supports Power View for multidimensional models installed on your system. As of December 1, 2012, Microsoft SQL Server 2012 that supports Power View for multidimensional models is not generally available. However, the Microsoft SQL Server 2012 that supports Power View for Multidimensional Models Community Technology Preview (CTP) release is available for download if you want to test the Power View reporting capability. You should not test or use this CTP in a live operating environment unless Microsoft permits you to do so under another agreement. Click here (http://www.microsoft.com/en-us/download/details.aspx?id=35822) for more information on the CTP release. All features and dates are preliminary based on current expectations and are subject to change without notice. The information herein is for informational purpose only and represents Microsoft’s current view as of the date of this release. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft.

 


 

Lasă un răspuns

Completează mai jos detaliile despre tine sau dă clic pe un icon pentru autentificare:

Logo WordPress.com

Comentezi folosind contul tău WordPress.com. Dezautentificare / Schimbă )

Poză Twitter

Comentezi folosind contul tău Twitter. Dezautentificare / Schimbă )

Fotografie Facebook

Comentezi folosind contul tău Facebook. Dezautentificare / Schimbă )

Fotografie Google+

Comentezi folosind contul tău Google+. Dezautentificare / Schimbă )

Conectare la %s

%d blogeri au apreciat asta: