report->report properties, gives tabbed properties.
Includes CODE tabe - VB.Net or c# can be input here along with assembly references.
Also shows report parameters - all params and types manipulated here.
Query parameters begin with the @ symbol, whereas report parameters do not.
Most properties can be set with an 'Expression' - like SSIS. Global vars are hardwired but accessible here as well as all data fields.
SUBREPORT - control added to existing report which runs another report - this other report can be run by itself.
Table sorting is done from TABLE PROPERTIES (right click on entirely selected table -> properties).
Can sort by any of the fileds in the dataset.
GROUPS - will auto put SUM() around all fields that are added within it. May be responsible for detail data being ommited/sums being less/diff then they should be.
Group visibility should be use dinstead of individual textbox vis. Dont forget to set 'can be toggled by other report item' and choose a parent testbox or somesuch otherwise you'll have no control to expand the group.
Insert Group when right clicking on the rows area is best way to get proper nesting - notice header/detail/footer areas are all added for new groups.
The report viewer control, 'ReportViewer', ships with Visual studio 2005 and can be used in any Win or web form.
A data source can be contained within a report, or it can be shared by several. In the first case, the definition for a report-specific data source is stored within the report itself, whereas for a shared source, the definition is stored as a separate item on the report server. A report can contain one or more data sources, either report-specific or shared.
Report Builder reports are built from report models that provide a business layer on top of the underlying data source. Report models include:
* Business names for database fields and tables.
* Defined relationships between items in the data source.
* Logical groupings of model items.
Report models based on SQL Server 2005 or later Analysis Services databases are generated by using Report Manager or SharePoint Services.
SubReport control - drag it into table cell of master report and set properties to point at whole other report. Set params that need to get passed. Dont forget - create sub report as a stand a lone report first.
Troubleshooting performance - have a look in the ReportServer database. In there is the ExecutionLog Table. This shows you each report that was run, who ran it, what parameters were used and how long it took. The really cool thing is that it sub divides the time taken into the time to retrieve the data, the time to process the data and the time to render the report. - to do this you must turn on Logging in the Site Settings of the Report Manager.
Report with header and body sections (order header/order lines) is done by using 2 datasets and base them both around a report param. Top section is just text boxes where the bottom section is a table.
Text box control is good to use as a section title/header as it can be stretched and gb colour set.
To create drill-through report: right click on textbox1, select properties, go to Navigation -> Hyperlink action -> Jump to report.
Main concept of a matrix - its gonna aggregate stuff.
Reporting Services Config Manager - Tool available from start menu. Virtual dirs/sharepoint integration/db setup/credentials/server status options.
Format values:- 'n0' will be numeric wilth zero decimal places. 'n2' 2 decimal places etc...
If report server throws a security wobbly after your win password has changed then go into reporting services configuration from start menu, then delete encrypted data.
MDX wizard unformats your MDX over time but keeps the correct format in the preview page of the wizard - select all, copy and paste back into the main query window to keep formatting.