Reporting provides consolidated, factual, and up-to date information about any area of business in an organization. This will help the organization member to take the right decision for their business. It acts as a treasure trove of reliable information for long-term planning and decision making.
In Microsoft Dynamics R2, AX provides the tool to build the SSRS reports but in Microsoft Dynamics R3, the tool to build the SSRS reports in a more simple and efficient way. This book will give over 90 more recipes for beginners to understand the SSRS reports in Microsoft Dynamics AX R3 faster and in a simplified manner.
Chapter 1, Understanding and Creating Simple SSRS Reports, helps you to walk through the basis of SSRS reports and create a simple report using queries. This chapter will also help you understand the basic characteristics of reports.
Chapter 2, Enhancing Your Report – Visualization and Interaction, covers how to enhance the visualization and interaction of reports through parameters, creating data regions and charts, and formatting the reports.
Chapter 3, A Report Programming Model, helps you build the SSRS reports programmatically inside Dynamics AX and add the validations programmatically.
Chapter 4, Report Programming Model – RDP, helps you to develop the advanced reports using the data provider framework. In this chapter, we will create a report using RDP classes.
Chapter 5, Integrating External Datasources, covers how the SSRS reports can be extended to include other data sources or through the integration framework.
Chapter 6, Beyond Tabular Reports, helps you understand the other formats of reports such as using matrices and charts. This book also covers the interesting components of reports such as gauges, rectangles, and lists.
Chapter 7, Upgrading and Analyzing Reports, discusses the approaches for moving the MorphX-based reports into SSRS reports and also covers the patterns of reports.
Chapter 8, Troubleshooting and Other Advanced Recipes, dives into the performance and troubleshooting of SSRS reports. This will also introduce the log viewer through which you can analyze the report usage and its log.
Chapter 9, Developing Reports with Complex Databases, discusses developing the SSRS reports that have complex data and how to drive that data into reports using maps, views, and queries.
Chapter 10, Unit Test Class and Best Practices Used for Reports, helps you create the unit test classes for a report, which will help you test the business logic being written to develop reports. It will also tell you best practices to be followed when developing the reports.
To practice the content in this book, you need the following software:
Microsoft Dynamics AX 2012 R3
SQL Server Reporting Services
SQL Server Analysis Services
Microsoft Visual Studio 2010
Microsoft Visual Studio 2013 in case of CU8
Alternatively, you can use the Virtual Image available for Microsoft Dynamics AX 2012 R3 through the Microsoft Learning download center.
This book is aimed at IT administrators looking to develop their own reports for their internal demands and for X++ developers who want to deepen their understanding of SSRS reports.
This book requires some basic knowledge of the SQL server reporting system, Microsoft Dynamics AX 2012, X++, and MorphX. Some examples are based on C#.NET; however, it is not a must to read this book.
In this book, you will find several headings that appear frequently (Getting ready, How to do it, How it works, There's more, and See also).
To give clear instructions on how to complete a recipe, we use these sections as follows:
This section tells you what to expect in the recipe, and describes how to set up any software or preliminary settings required for the recipe.
This section usually consists of a detailed explanation of what happened in the previous section.
This section consists of additional information about the recipe in order to make the reader more knowledgeable about the recipe.
In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "Add a new report to this project and name it PKTWarehouseMobileDeviceDetails."
A block of code is set as follows:
=drillVoucher(!Parameters.AX_ReportContext.Value,
!Fields.ItemTrans.VoucherNum.value,
!Fields.ItemTrans.TrandDate.value,
!Parameters.AX_CompanyName.Value);Any command-line input or output is written as follows:
$>rs.exe -i C:\timeout.rss -s http://[SSSRSServerName]:80/Reports -v timeout="72000" –l 0
New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Right-click on the Dataset node and select the New Dataset option."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of.
To send us general feedback, simply e-mail <[email protected]>, and mention the book's title in the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you could report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website or added to any list of existing errata under the Errata section of that title.
To view the previously submitted errata, go to https://www.packtpub.com/books/content/support and enter the name of the book in the search field. The required information will appear under the Errata section.
Piracy of copyrighted material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors and our ability to bring you valuable content.
If you have a problem with any aspect of this book, you can contact us at <[email protected]>, and we will do our best to address the problem.