Wednesday, March 28, 2012
Report Parameter Defaults not being used in deployed reports
reports, it works perfectly, in other reports, the parameters specified
in Visual Studio under Report Parameters seem to have no effect when
the report is deployed to the ReportServer. The toolbar for the
parameters displays, and that is OK, but the default values don't
appear in the toolbar like they do in the other reports, and the report
doesn't run until the parameters are selected with the dropdowns. What
is causing the parameters to behave differently from one report to the
other?I have found that although you may change 'defaults' in the Report Designer,
they sometimes do not seem to take when I 'deploy' the modified report. I
don't understand why, bu my solution thus far has been to delete the report
off the report server and then redeploy it. The new/modified default values
appear.
"Kelly Gross" wrote:
> When I set the default properties under Report Parameters in some
> reports, it works perfectly, in other reports, the parameters specified
> in Visual Studio under Report Parameters seem to have no effect when
> the report is deployed to the ReportServer. The toolbar for the
> parameters displays, and that is OK, but the default values don't
> appear in the toolbar like they do in the other reports, and the report
> doesn't run until the parameters are selected with the dropdowns. What
> is causing the parameters to behave differently from one report to the
> other?
>|||Make sure your default value is your available value, otherwise it is
not working.
Kelly Gross wrote:
> When I set the default properties under Report Parameters in some
> reports, it works perfectly, in other reports, the parameters
specified
> in Visual Studio under Report Parameters seem to have no effect when
> the report is deployed to the ReportServer. The toolbar for the
> parameters displays, and that is OK, but the default values don't
> appear in the toolbar like they do in the other reports, and the
report
> doesn't run until the parameters are selected with the dropdowns.
What
> is causing the parameters to behave differently from one report to
the
> other?
Report pagination for charts
Hi,
We have developed few reports displaying data using chart layout. In the Data tab, we have specified MDX query that will return top 10 records.
But now, instead of restricting to just top 10 records, we would like to display all records and go in for pagination.
Is there some setting in the chart properties, where in I can display the first n records in first page, and the next n records( if available) in the next page and so on?
Can I specify the value of n somewhere in the propeties?
I read through many posts regarding pagination but those couldn't help me much.
Please help me in solving this problem.
Any help would be appreciated.
Thanks in advance!
No response yet!:(|||One approach is the following:
Step 1: Add a table to the report
Step 2: Group by a number of rows
Right-click on the table and select Properties. Add a table group (with a group header, but no group footer)
Enter this for the group expression: =Ceiling(RowNumber(Nothing)/10)
This will cause the table to group on every ten rows. So you'll get a separate table group for every ten rows.
Step 3: Add a chart in the table group header
Design your chart.
Note: this approach is similar to the table inline charts approach discussed in the following whitepaper: http://msdn2.microsoft.com/en-us/library/aa964128.aspx
-- Robert
|||Thanks a lot Robert!
I got the idea from the solution provided by you and did the following:
Step 1: Add a list to the report
Step 2: Added group expression for the list to group the data
Grouping =Ceiling(RowNumber(Nothing)/10)
Set the following properties for list:
KeepTogether: False
PageBreakAtEnd: True
Step 3: Added chart to the list
Set the property, PageBreakAtEnd: True for the chart.
The above steps solved my problem of report pagination for charts.
Thanks once again!
sqlReport pagination for charts
Hi,
We have developed few reports displaying data using chart layout. In the Data tab, we have specified MDX query that will return top 10 records.
But now, instead of restricting to just top 10 records, we would like to display all records and go in for pagination.
Is there some setting in the chart properties, where in I can display the first n records in first page, and the next n records( if available) in the next page and so on?
Can I specify the value of n somewhere in the propeties?
I read through many posts regarding pagination but those couldn't help me much.
Please help me in solving this problem.
Any help would be appreciated.
Thanks in advance!
No response yet!:(|||One approach is the following:
Step 1: Add a table to the report
Step 2: Group by a number of rows
Right-click on the table and select Properties. Add a table group (with a group header, but no group footer)
Enter this for the group expression: =Ceiling(RowNumber(Nothing)/10)
This will cause the table to group on every ten rows. So you'll get a separate table group for every ten rows.
Step 3: Add a chart in the table group header
Design your chart.
Note: this approach is similar to the table inline charts approach discussed in the following whitepaper: http://msdn2.microsoft.com/en-us/library/aa964128.aspx
-- Robert
|||
Thanks a lot Robert!
I got the idea from the solution provided by you and did the following:
Step 1: Add a list to the report
Step 2: Added group expression for the list to group the data
Grouping =Ceiling(RowNumber(Nothing)/10)
Set the following properties for list:
KeepTogether: False
PageBreakAtEnd: True
Step 3: Added chart to the list
Set the property, PageBreakAtEnd: True for the chart.
The above steps solved my problem of report pagination for charts.
Thanks once again!
Monday, March 26, 2012
Report of my reports
in my SRS, including their descriptions, specified by the folders they reside
in, by pulling the data directly from the SRS? Is this possible? The data's
there. How can I get to it dynamically? Thanks.Its easy using the API:
http://odetocode.com/Articles/95.aspx
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"David" <David@.discussions.microsoft.com> schrieb im Newsbeitrag
news:C6C91A2C-A270-4C18-980C-607923E180D0@.microsoft.com...
>I would like to create a report in Reporting Services that lists the
>reports
> in my SRS, including their descriptions, specified by the folders they
> reside
> in, by pulling the data directly from the SRS? Is this possible? The
> data's
> there. How can I get to it dynamically? Thanks.|||I think you could also query the ReportServer tables directly in a strored
proc then use that as the datasource for the "report of reports"
"David" wrote:
> I would like to create a report in Reporting Services that lists the reports
> in my SRS, including their descriptions, specified by the folders they reside
> in, by pulling the data directly from the SRS? Is this possible? The data's
> there. How can I get to it dynamically? Thanks.
Wednesday, March 21, 2012
Report Model Error in WSS 3.0
The model specified must be a generated model. (rsModelNotGenerated)
This error comes up after clicking on the new report model. The report model and datasource deployed to the sharepoint server with no issues.
Hi,Did you ever find a solution to the error:
"The model specified must be a generated model (rsModelNotGenerated)."
I'm getting it after I have deployed a Report Model to Microsoft Office Sharepoint Server 2007, and when trying to create a Report Builder model in Sharepoint.
I appreciate any help you can provide.
Thanks,
Fady
|||
Hi,
Did you manage to resolve your problem, if yes could you please share your experiences.
Thanks
Mon
Report Model Error in WSS 3.0
The model specified must be a generated model. (rsModelNotGenerated)
This error comes up after clicking on the new report model. The report model and datasource deployed to the sharepoint server with no issues.
Hi,Did you ever find a solution to the error:
"The model specified must be a generated model (rsModelNotGenerated)."
I'm getting it after I have deployed a Report Model to Microsoft Office Sharepoint Server 2007, and when trying to create a Report Builder model in Sharepoint.
I appreciate any help you can provide.
Thanks,
Fady
|||
Hi,
Did you manage to resolve your problem, if yes could you please share your experiences.
Thanks
Mon
Report Model Error in WSS 3.0
The model specified must be a generated model. (rsModelNotGenerated)
This error comes up after clicking on the new report model. The report model and datasource deployed to the sharepoint server with no issues.
Hi,Did you ever find a solution to the error:
"The model specified must be a generated model (rsModelNotGenerated)."
I'm getting it after I have deployed a Report Model to Microsoft Office Sharepoint Server 2007, and when trying to create a Report Builder model in Sharepoint.
I appreciate any help you can provide.
Thanks,
Fady|||
Hi,
Did you manage to resolve your problem, if yes could you please share your experiences.
Thanks
Mon
Report Model Deployment Problem (DataSource)
I created a new Report Model project and specified folders for both the model and the datasources. For some reason, every time I deploy the model I get an error stating the datasource cannot be found. I've tried changing the project properties to no end. Here's the specific output
Deploying to http://localhost/ReportServer?%2f
Deploying data source '/Data Sources/CRM Database Conection'.
Deploying model 'CRM Filtered View Model'.
The item '/Data Sources/CRM Database Connection' cannot be found.
This seems to happen a lot when creating logical joins from tables from different datasources.Report Model Deployment Problem (DataSource)
I created a new Report Model project and specified folders for both the model and the datasources. For some reason, every time I deploy the model I get an error stating the datasource cannot be found. I've tried changing the project properties to no end. Here's the specific output
Deploying to http://localhost/ReportServer?%2f
Deploying data source '/Data Sources/CRM Database Conection'.
Deploying model 'CRM Filtered View Model'.
The item '/Data Sources/CRM Database Connection' cannot be found.This seems to happen a lot when creating logical joins from tables from different datasources.