Microsoft Dynamics AX 2012 SSRS Reports Considerations

Things we must remember while working with SSRS reports whether it is customized or new reports from scratch.

  • All servers must be using Microsoft Windows authentication. Depending on the functionality that you implement, Microsoft Dynamics AX may also require that you use domain accounts with specific permissions.
  • 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
    • 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 accessing data from the Microsoft Dynamics AX database
    • use the predefined Microsoft Dynamics AX data sources to ensure that appropriate security is enforced
    • 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.
  • Try to put static debugger (write breakpoint) in DP Class processReport() method.
  • Run the report from visual studio
    • Open Microsoft dynamics AX Configuration Utility -> select developer tab,
      • Select check boxes provided) and debug it.
  • Stress (While Debugging) on query in processReport() methods
    • Because that could also be one of the reason for your problem.
  • Put static debugger in insertIntoTempTable() as well to check whether data is populating in temp table or not, change TableType as regular.
  • Refresh Report, Report Server in Tools-> Caches ->Refresh report server
  • Delete the Report from report Server and redeploy it.
  • Generate Incremental CIL.
    • Full CIl generation (Recommended)
  • Do not build third-party reporting projects from the command line. Build from the command line only in trusted scenarios
    • 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

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s