Mainpac 2011 Reporting Writing Hints

Transcription

1 Mainpac 2011 Reporting Writing Hints

2 Intended Audience This a technical document that assumes the following skills: Exposure to creating reports in Microsoft Access or other third-party reporting products, such as Crystal Reports. Conceptual understanding of the push and pull distribution/subscription paradigm. Experience navigating the Microsoft Windows Server environment. Experience with Windows services (starting and stopping) Experience creating service accounts and permissions Experience with Microsoft SQL Server, including: SQL Server Agent. SQL Server query language (SELECT, UPDATE, INSERT, and DELETE). SQL Server System tables. SQL Server accounts (users and permissions). Mainpac recommends that all staff nominated to write Mainpac 2011 Reports attend Microsoft Learning Course 6236A Implementing and Maintaining Microsoft SQL Server 2008 Reporting Services

3 Mainpac 2011 System Design Runs on SQL Server.NET Application Code Layered Architecture Logically Separated Mainpac 2011 User Data and Reporting Server Database Can be physically separated on different physical machines Can be physically separated on different virtual machines

4 Uses Standard SSRS Infrastructure We assume: That your SSRS Infrastructure is configured Mainpac 2011 is running You have sufficient permissions to access to the SQL Database You have installed the Report Writing tools Mainpac 2011 Database SQL D A T A Data Source Query & Query Parameters Result Set Fields Data Set Filters Web Front End IIS (SSRS 2005) HTTP.SYS (SSRS 2008) Reporting Services Security Data Processing Rendering Delivery SQL Server Database Engine SQL Server Service Account Encryption Key /Reports /ReportServer Report Manager Web Application For humans Web Services for programs to access via SOAP Or URL Access Reporting Services on the Front End Connects to it s SQL Server on the Back End Virtual Directories Web Browsers BIDS Report Builder, rs.exe, URL Access, Custom apps, Or 3 rd Party Apps ReportServer Folder Structure Reports (RDL) Resources (Logos) Data Sources Encrypted Credentials Security Snapshots Histories ReportServerTempDB Temporarily Cached Intermediate Reports An Intermediate Report is all the information that is needed to render the report. That includes Data and Layout information

5 And Standard SSRS Design Tools Tool Details How to Access Power View Report Designer Report Builder An interactive data exploration and visual presentation experience designed to let you create and interact with reports based on Analysis Services tabular models. NOTE: Requires Reporting Services in SharePoint mode. Design reports and deploy to a native mode or SharePoint mode report server. Hosted in SQL Server Data Tools (SSDT) Report Data pane to organize data used in your report Tabbed views for Design and Preview for interactive report design Query designers to help specify which data to retrieve from data sources and that are associated with data source types in the RSReportDesigner Configuration File Expression editor with IntelliSense to build Visual Basic expressions that customize report content and appearance Supports custom report items and custom query designers For more information, see Reporting Services in SQL Server Data Tools (SSRS). Design reports and deploy to a native mode or SharePoint mode report server. Microsoft Office-like authoring environment Ability to save report items as report parts A wizard for creating maps Aggregates of aggregates Enhanced support for expressions Query designers to help specify which data to retrieve from a selection of built-in data sources types For more information, see Report Builder (SSRS). Browser with Silverlight. SQL Server Data Tools (SSDT) Download MSI or open from Report Manager/SharePoint

6 Important Note Mainpac always recommends that you use your TEST instance of Mainpac 2011 for Report Development When your users confirm the Report(s) are working correctly from your TEST instance of Mainpac 2011, then you can migrate them to the Mainpac 2011 PROD database Once installed on PROD, you should again ask your users to confirm that the Report(s) are working correctly

7 Using Visual Studio for a New Report 1. Create your Query Write and test in MS SQL Server Management Studio 2. Put Query into Visual Studio Setup a project Define datasource Select fields and play with report output Add graphics and logos Add Parameters 3. Publish the Report 4. Use within Mainpac 2011

8 Create a New Project File > New Project Type is Report Server Project

9 Add a Data Source Right Click Data Sources then add new Data Source Enter the correct server details and select the Mainpac Database Be sure to select production or training depending on your needs You can use the same name for TEST and PROD to save time

10 Add a New Report Right Click reports and select Add New Report Select the shared datasource from the previous add datasource example

11 Enter the SQL Query Enter the SQL Query Example: Select * from WorkOrderDetail Write the Query in Management Studio (see next slide for example)

12 Creating the SQL Query

13 Visual Studio Reports Select fields for the report Mainly into details Try a report with one field in the group category E.g. Operational Asset Name NEXT Select Stepped, or Block (try each) Include subtotals Include drilldown Next then Finish SAVE THE CORRECT NAME (NO Spaces)

14 Use Preview to quickly test your Report

15 Components of Report Data Parameters Images Query and fields

16 Parameters in Visual Studio Pass Parameter to subreport In Query parameter format ROUND brackets! In Subreport format SQUARE brackets!

17 Add the Report in Visual Studio Open Solution explorer Right click on reports. Add -> existing item Browse to report, select and then add Can add multiple items at once

18 Reports must be in folders Save the reports in one of the main category folders Administration Financial Assets Inventory Maintenance Organisational Resources Purchasing. No spaces in the names for Report Builder OR Visual Studio Reporting Options How many records to be shown/printed Output formats such as width.

19 The GUID Error It is common when developing reports on a different SQL Reporting Services server (SRS) than the deployed reports to generate the GUID error

20 Resolving the GUID issue 1. Go to the Properties Tab the issue is highlighted in red

21 Resolving the GUID issue 2. Click Browse, expand the Data Sources tree, select the correct data source and click OK

22 Resolving the GUID issue 3. Click Apply to confirm the change

23 Adding Reports The list only shows Unallocated Reports

24 Visual Studio add an Embedded Image Reports/Embedded Images Click New Select IMG Open Added to list

25 Visual Studio Embed Image Reports/Embedded Images View/Toolbox Report Items/Image - double click or drag to report area Select image in report area Press F4 to bring up properties Change Source to Embedded Change Value to Image name.

26 Visual Studio Embed Image

27 Add a Mainpac 2011 Report to the Dashboard via Administration -> Dashboard Manager

28 And Dashboard -> Manage to select the actual report

29 Conclusion Mainpac 2011 reporting makes use of Standard Microsoft Infrastructure Multiple tools are available to design reports Mainpac R&D has embedded views within the Mainpac 2011 database to simplify joins for common tables Operational Assets Work Orders Purchasing Inventory