I have created a Report Parameter, and set the type of this to "Boolean".
This is displayed as a RadioButton with the options of True or False.
Is there anyway to change this to be displayed as a CheckBox?
Thanks,
Kate
See this thread:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=562091&SiteID=1
Hi,
Anyone can help me?
I created a store proc with @.startdate and @.enddate
in query analyser - I run it as Exec SP_Admission '2006/01/01','2006/01/25' and it is ok.
Then I created a report in VS2005 and set the parameter as datetime in report parameter.
if I manually force to fill startdate and enddate with ‘yyyy/mm/dd’ format in preview, it works.
However if I choose the date from the given calendar(Date Time Picker), it doesn’t work
it is said that "The value provided the report parameter 'enddate' is not valid for its type.
Of course it not valid because it always comes with ‘dd/mm/yyyy’ format
I didn't setup the date time picker, it will automatically when I choose datetime as datatype.
any idea what should I do?
thanks,
Susan
Hi Susan,
not exactly brilliant, but
Exec SP_Admission convert(datetime,'12/10/2006',103),convert(datetime,'12/11/2006',103)
should work in your case, so put your parameter instead of '12/10/2006'
|||
Thanks...
someone suggested that in my SP -
I declare as varchar then in where statement I convert it as you mention.
however in report para - I can't set it as datetime but set to string.
it works ok but I can't use the date time picker .
well at least works that way...
Thanks so much
Good day everyone...
I created a simple report in SQL Server 2005 Reporting Services. Its about getting the sales from specific date and store. My parameters are date and storename, the report works fine as I view it in the reportserver. But, when we incorporate the report in a custom webpage using a reportviewer, the parameter toolbar occupies half the space, now that's my problem. Is there anyway I can create a custom Toolbar in Visual Studio so I can just set the parameter property to hidden so the default parameter toolbar wont show?
Thanks in advance guys... c",)
Yes. There's nothing extra (like controls) supplied to allow this. Just create the parameters using standard controls (dropdowns, dat pickers, whatever you like) and then in code pass those parameters to the report viewer control.sqlHello,
I need to create a MyPar parameter dropdown list, that is why I created a new dataset that gets data through a stored procedure. I also add @.MyPar into the query string of MyMainDataSet . I defined this parameter in Parameter screen for both available and default values.
When I run the report, I get the following error.
Query execution failed for data set MyMainDataSet.
Must declare the variable @.MyPar
What is problem?
Hello:
If I understand correctly:
The first stored procedure that displays the parameters for MyPar is a straight SQL Select Statement - So this SQL Select just gets the data for the available parameters to display in the dropdown list.
The next step the user selects one value from all of the available parameters in the dropdown list - so once this parameter is selected you need to pass this selected parameter to your next SQL Select statement so you only get the data based on the parameter the user selected!
Include the following in the Stored Procedure (if your are using one for the selection of data based on the parameter the user selected)
CREATE PROCEDURE "Whatever the Procedure name is"
@.MyPar nvarchar(10) or whatever length the parameter is
-- SETUP RUNTIME OPTIONS / DECLARE VARIABLES --
set nocount on
Hope this helps!
Best Regards - Joe
Try to print parameters in the report.
Be carefull with case sensitive of your database, mine is case sensitive.|||Hello ykagoma.
I've made several reports that need a situation similar tou the one you're handling. What I do is to create a more awful query, so it is composed by IF statements. I mean, IF the parameter has certain value I use a query with certain WHERE clauses. IF the parameter has another value then I use a query with another WHERE clauses and so on.
For example:
IF @.param = -5
BEGIN
SELECT *
FROM tbl_employee
END
ELSE
BEGIN
SELECT *
FROM tbl_employee
WHERE id_boss = @.param
END
I hope it helps.|||
Hi,
the solustion is actually in help books of Reporting Services.
For example you have query: select name from emplyees where name like 'ro%'
and You want to have parameter instead ro%. The modified query into Visual Studio type into by having parameter @.NAME is:
="select name from emplyees where name like '" & Parameters!NAME.Value & "%'"
so you are not writing query directly but puzzling query text by syntax usage of visual studio, which can include everything.
Try to print parameters in the report.
Be carefull with case sensitive of your database, mine is case sensitive.|||Hello ykagoma.
I've made several reports that need a situation similar tou the one you're handling. What I do is to create a more awful query, so it is composed by IF statements. I mean, IF the parameter has certain value I use a query with certain WHERE clauses. IF the parameter has another value then I use a query with another WHERE clauses and so on.
For example:
IF @.param = -5
BEGIN
SELECT *
FROM tbl_employee
END
ELSE
BEGIN
SELECT *
FROM tbl_employee
WHERE id_boss = @.param
END
I hope it helps.|||
Hi,
the solustion is actually in help books of Reporting Services.
For example you have query: select name from emplyees where name like 'ro%'
and You want to have parameter instead ro%. The modified query into Visual Studio type into by having parameter @.NAME is:
="select name from emplyees where name like '" & Parameters!NAME.Value & "%'"
so you are not writing query directly but puzzling query text by syntax usage of visual studio, which can include everything.
sqlI have created an asp.net application in which i have a textbox and botton.T
he textbox value is passed as parameter to a report and the corresponding report is generated on button click.The problem is that once i add a report to any application the same report is displayed each time i.e. the report is not updating whenever there is a change in the database values.
Iam refreshing the datasource in the original report and change is reflected there in original report but in the dotnet application always the old report is maintained......
Can anybody help me out......
I had the same problem reportviewer1.reset nd I sovled it by added a line code before refreshing the report:
reportviewer1.reset
|||
I had the same problem and I sovled it by added a line of code before refreshing the report:
reportviewer1.reset
|||
Thanx Frankmeng for your suggestion but it is not working....
It is giving me build error.
Error 1 'Microsoft.Reporting.WebForms.ReportViewer' does not contain a definition for 'Reset'
Can u help me with this?
I would also like to know whether we can set the paging property of the report so that only desired number of records are displayed in a page and the user doesn't have to scroll up and down.
Thanx.
|||Thanks a lot Arun its working...
Arun:
It is sovled by added a line of code in the Button click event.
reportviewer1.localreport.refresh()
I have a datasource view DSV1. It points to a datasource DS1 that is considered the "primary".
I have created a Report Model that uses DSV1 (and thus uses DS1)
I created a new datasource, DS2 that I would like to use instead of DS1. (I can't just modify DS1 because if I modify it, it will overwrite it when we go to our Production environment and break that datasource)
So, I can go into DSV1 and change all the references from DS1 to DS2.
But that's where the problem lies.
When I try to build, I get the following error:
"The Table property of the Entity "E1" refers to the Table "dbo_View", which is not in the primary data source."
Somehow, the entity is tied to the "primary" datasource. When I change it back to DS1, everything works fine. Any thoughts? What can I do?
Here is what I've noticed:
If I look at the code for the Data Source DS1, the XML shows an <ID> tag and a <NAME> tag.
In SSRS, it is requiring that the ID be named "DS1", but the name can be whatever I want.
So if I change the name, it looks like I can deploy no problem without overwriting my old Datasource, but I just wish I could have these two pieces updated without a problem.
Any idea why this is?
Did you ever figure this out? I'm having the same problem.|||Cross-database report models are not supported in Model Designer. You can get around this by creating a view on top of the second table. We should probably give you a more informative error (or add support for it
).|||Thank you for the reply.. I'm not sure I understand the workaround though. I am trying to do a proof of concept for my department and we have several data sources that I need to report from. Any help I can get is truly appreciated. I've been reading up on the different BI tools available with SQL server 2005 and it seems that maybe my best bet is to work on a data integration project... not sure which route to go. I do have a very good understanding of our database schema, its just a matter of how I can simplify it for end users to be able to write their own reports.|||I think I might have misread your original question. Are the two databases on the same server? If not, you will need to use the Linked Server feature of SQL to make this work. There are some performance implications with cross-server joins that may mean that you should pull the two sources into a single database using Integration Services,|||I actually have both cases
... But I can't even get the view to work for two databases on the same server
.. can you shed some light on that scenario?|||Yudi,
If the databases are on one instance on one server, you can use the full name of the table to access the data in a named query. For instance,
SELECT col1, col2, col3 FROM table1
would be the first named query in the original database. In another named query you could use
SELECT col1, col2, col3 FROM DB1.dbo.table2
Provided you have the correct permissions on that database, you will be able to see the data in both databases. I use that technique and it works fairly well.
R
sqlDid you ever figure this out? I'm having the same problem.|||Cross-database report models are not supported in Model Designer. You can get around this by creating a view on top of the second table. We should probably give you a more informative error (or add support for it).|||Thank you for the reply.. I'm not sure I understand the workaround though. I am trying to do a proof of concept for my department and we have several data sources that I need to report from. Any help I can get is truly appreciated. I've been reading up on the different BI tools available with SQL server 2005 and it seems that maybe my best bet is to work on a data integration project... not sure which route to go. I do have a very good understanding of our database schema, its just a matter of how I can simplify it for end users to be able to write their own reports.|||I think I might have misread your original question. Are the two databases on the same server? If not, you will need to use the Linked Server feature of SQL to make this work. There are some performance implications with cross-server joins that may mean that you should pull the two sources into a single database using Integration Services,|||I actually have both cases... But I can't even get the view to work for two databases on the same server.. can you shed some light on that scenario?|||Yudi,
If the databases are on one instance on one server, you can use the full name of the table to access the data in a named query. For instance,
SELECT col1, col2, col3 FROM table1
would be the first named query in the original database. In another named query you could use
SELECT col1, col2, col3 FROM DB1.dbo.table2
Provided you have the correct permissions on that database, you will be able to see the data in both databases. I use that technique and it works fairly well.
R
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.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.
The model ID of the submitted model must match that of the current model
I have searched all over for the cause and solution but, have had no luck.Can someone please help me?
Thanks,
Roy
The SemanticModel ID of the submitted model must match the semantic model id of the existing model, otherwise you'll get this error.
The solution is to delete model from server (using Report Manager or Management Studio)before deploying.|||Yes, I had the same problem. Surely a deploy would be able to deal with this automatically?|||Deploy tries not to override existing model with completely different model.
The model ID of the submitted model must match that of the current model
I have searched all over for the cause and solution but, have had no luck.Can someone please help me?
Thanks,
Roy
The SemanticModel ID of the submitted model must match the semantic model id of the existing model, otherwise you'll get this error.
The solution is to delete model from server (using Report Manager or Management Studio)before deploying.|||Yes, I had the same problem. Surely a deploy would be able to deal with this automatically?|||Deploy tries not to override existing model with completely different model.sql
