This document provides steps for publishing reports in DBIS, including:
1. Developing and testing queries in Query Depot before building reports.
2. Creating standard reports by selecting a category, naming the report, and bringing in the query.
3. Setting dependencies by selecting applicable tables used in the report's query.
4. Enabling export to Excel functionality so users can run and export reports.
The steps outline best practices for validating queries, building reports from queries, and ensuring dependencies are set up for any tables affected by packages.
This presentation is about -
Working Under Change Management,
What is change management? ,
repository types using change management
For more details Visit :-
http://vibranttechnologies.co.in/sas-classes-in-mumbai.html
This presentation is about -
Working Under Change Management,
What is change management? ,
repository types using change management
For more details Visit :-
http://vibranttechnologies.co.in/sas-classes-in-mumbai.html
Power bi slide share pdf it is a very importantSatyabratarath5
It is first pdf I am Satyabrata rath my 1st pdf in power bi it is most wonderful pdf .A basic knowledge in power bi
Power bi most wonderful pdf.power bi is business purposes tool
Power bi slide share pdf it is a very importantSatyabratarath5
It is first pdf I am Satyabrata rath my 1st pdf in power bi it is most wonderful pdf .A basic knowledge in power bi
Power bi most wonderful pdf.power bi is business purposes tool
2. DBIS Standard Report Publishing
Steps
1. After developing query in SSMS, have T-SQL code ready to copy,
and list of tables used in query.*
2. Open DBIS – open Query Depot, create folder for report, and run
query. This serves as validation for query, and possibly can be
used in the future for testing modifications.
3. Create report
4. Test report – run report in Reports to Go
* Only need list of tables that are the result of package runs – loads and
appends – the first part of this presentation deals with simple report
creation
4. DBIS Report Publishing
Query Depot
Give report meaningful name, similar to your report name – you will
go back later and rename with the report name once it’s assigned
Locate your object; right-click, select New > Query
5. DBIS Report Publishing
Query Depot
Give it a meaningful name that works for you – just be consistent –
this is your place to test and document your queries.
7. DBIS Report Publishing
Query Depot
Drop your T-SQL in the code window to the right, and run your query – the results
will display in the window at the bottom, similar to SSRS
8. DBIS Report Publishing
Query Depot
The results will display in the window at the bottom, similar to SSRS – you’re ready to
develop your report
9. DBIS Standard Report Publishing
Report creation
• First, determine what category you are going
to replace the report in
10. DBIS Standard Report Publishing
Report creation
• Determine what category you are going to replace the report in; Say, for example, you
want to put it in Customer Activity / Completed Jobs in Reports/ Residential / Texas
• Right-click on category folder, and get ready to name your report
15. DBIS Report Publishing
Report creation
Next: Name query – for every separate query you have, that will represent
one tab in Reports To Go. Reports are often, for example, broken down
between Residential and Commerical, with separate tabs and separate
underlying queries. Or with 3 tabs, by region (NTX, CTX, STX)
23. Export to Excel functionality
• You will most likely want to set up the ability for the user to export to excel
• Right-click on object name; New > Export
24. Export to Excel functionality
• User will be able to run reports on their own, and export to excel
25. Export to Excel functionality
• Right click on export object; define properties; enable if so desired.
• Save changes
26. DBIS Report Publishing
Report creation
Next: Check Excel; Enabled; Save changes*
* Note: You may want to wait until process is fully tested before enabling
package, especially if there is a related pacakage table append
27. Dependencies
• Need to set up dependencies – any report that
uses tables that are the result of packages
with table loads/appends need to be set up.
Should have list of applicable tables ready.
32. End of Standard Report Publishing
• With no load / append packages
33. REMINDER
• Remember to include that all reports need to
have dependencies set up, whether there is a
package for a table load/append involved or
not
• Discuss timing issues, such as monthly reports
run on the 19th if low usage