Showing posts with label views. Show all posts
Showing posts with label views. Show all posts

Friday, March 23, 2012

Report Builder, Stored Procedures and Views

How can I access recordsets from Stored Procedures and/or views instead of
tables from the database. I need to limit the amount of data a user can
access but the only entities showing up in the Explorer are tables.Hi,
You can access from tables and views, what ever filter criteria you can give
it in views. Go to "Data Source Views" in the Report model project and click
on add existing items from your datasource you should see tables and views.
Amarnath
"SYoung" wrote:
> How can I access recordsets from Stored Procedures and/or views instead of
> tables from the database. I need to limit the amount of data a user can
> access but the only entities showing up in the Explorer are tables.|||You're talking about a Report Project in VS. What I'm talking about is an
add on client development tool accessible via the
http://YourReportServer/Reports page called "Report Builder". This tool
allowes the user to create adhoc reports without having to write 1 line of
SQL.
"Amarnath" wrote:
> Hi,
> You can access from tables and views, what ever filter criteria you can give
> it in views. Go to "Data Source Views" in the Report model project and click
> on add existing items from your datasource you should see tables and views.
> Amarnath
>
> "SYoung" wrote:
> > How can I access recordsets from Stored Procedures and/or views instead of
> > tables from the database. I need to limit the amount of data a user can
> > access but the only entities showing up in the Explorer are tables.

Monday, March 12, 2012

Report Builder Dialog (Filter)

Anyone know what conditions cause the dialog box that says "A filter must be specified." to come up? I am joining two underlying views and cannot figure out why sometimes this comes up and other times it does not.

I also have this problem; it appears when the result of running the report is large. If this error message is triggered, you can still get the report to run by putting on a filter which does not actually filter out anything (!?). I experimented with a moderately large table of 9951 rows. If I select a filter that doesn't filter out any rows, I will still be able to produce a 199 page report containing 9951 rows.

But I still do not know what is the maximum amount of data that causes this error message to be triggered. Also, this error message is a little vague.|||Has anyone got a clue for the reason of above behaviour? Its pretty annoying to see the filter pop-up coming up when you don't want to filter any data. One workaround is to create a dummy filter which won't actually filter any rows from the output.|||

well !

Got it! The Instance Selection property of an entity in the model determines whether filter must be specified.

Report Builder Dialog (Filter)

Anyone know what conditions cause the dialog box that says "A filter must be specified." to come up? I am joining two underlying views and cannot figure out why sometimes this comes up and other times it does not.

I also have this problem; it appears when the result of running the report is large. If this error message is triggered, you can still get the report to run by putting on a filter which does not actually filter out anything (!?). I experimented with a moderately large table of 9951 rows. If I select a filter that doesn't filter out any rows, I will still be able to produce a 199 page report containing 9951 rows.

But I still do not know what is the maximum amount of data that causes this error message to be triggered. Also, this error message is a little vague.
|||Has anyone got a clue for the reason of above behaviour? Its pretty annoying to see the filter pop-up coming up when you don't want to filter any data. One workaround is to create a dummy filter which won't actually filter any rows from the output.|||

well !

Got it! The Instance Selection property of an entity in the model determines whether filter must be specified.

Report Builder Dialog (Filter)

Anyone know what conditions cause the dialog box that says "A filter must be specified." to come up? I am joining two underlying views and cannot figure out why sometimes this comes up and other times it does not.

I also have this problem; it appears when the result of running the report is large. If this error message is triggered, you can still get the report to run by putting on a filter which does not actually filter out anything (!?). I experimented with a moderately large table of 9951 rows. If I select a filter that doesn't filter out any rows, I will still be able to produce a 199 page report containing 9951 rows.

But I still do not know what is the maximum amount of data that causes this error message to be triggered. Also, this error message is a little vague.|||Has anyone got a clue for the reason of above behaviour? Its pretty annoying to see the filter pop-up coming up when you don't want to filter any data. One workaround is to create a dummy filter which won't actually filter any rows from the output.|||

well !

Got it! The Instance Selection property of an entity in the model determines whether filter must be specified.

report builder cant join views?

Hi friends
i have quick question with report builder utility .am using VS2005 and Sql 2005.
When creating report model solution ,when adding field names from a table it loads fields names as it is ,right ? so to make end users life easier i created
Views with lengthy field names.

the issue is ,i'll start with an example ,i've 2 views (ParentView and ChildView) and the tables used by these views have foreign key relation ship .when i use these 2 entities in report builder as soon as i add a column from one view (say ParentView) the other view disappears from list !! I assume Report builder looks FKey to link 2 entities and since am using views which will not have any fkeys on them it removes other entities from list.
is there any way to link these 2 views so that users can add few columns from ParentView and few more from ChildView.
Yes, If i use tables directly everything works fine .
Thanks for your help.
i finally figured out .if any one interested
when we double click on data source view (in report model project you created) it gives graphical representation of objects where we can drag & drop to create relationships just like diagrams in Enterprise Managers

report builder cant join views?

Hi friends
i have quick question with report builder utility .am using VS2005 and Sql 2005.
When creating report model solution ,when adding field names from a table it loads fields names as it is ,right ? so to make end users life easier i created
Views with lengthy field names.

the issue is ,i'll start with an example ,i've 2 views (ParentView and ChildView) and the tables used by these views have foreign key relation ship .when i use these 2 entities in report builder as soon as i add a column from one view (say ParentView) the other view disappears from list !! I assume Report builder looks FKey to link 2 entities and since am using views which will not have any fkeys on them it removes other entities from list.
is there any way to link these 2 views so that users can add few columns from ParentView and few more from ChildView.
Yes, If i use tables directly everything works fine .
Thanks for your help.
i finally figured out .if any one interested
when we double click on data source view (in report model project you created) it gives graphical representation of objects where we can drag & drop to create relationships just like diagrams in Enterprise Managers