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?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?
Showing posts with label visual. Show all posts
Showing posts with label visual. Show all posts
Wednesday, March 28, 2012
Report Parameter Calendar Formatting PLEASE HELP
If anyone can help me with this, I would be really grateful. I am using
Reporting Services 2005 and Visual Studio 2005 for this problem.
A while back, I had a formatting problem with my reports that was fixed by
use of the Language property on the report. Although this fixed all
formatting within the report. However, there is still a problem with the
calendar controls that collect DateTime report parameters.
To check that this was not some kind of obscure problem with my particular
report, I put together a very simple example from the AdventureWorks
database.
The dataset was provided by the text query of:
SELECT Title, BirthDate
FROM HumanResources.Employee
WHERE (BirthDate BETWEEN @.StartDate AND @.EndDate)
The @.StartDate and @.EndDate parameters were set to type DateTime with
default value of null. I put a two column table on the report, displaying
Title and BirthDate. The Language of the report is set to English(United
Kingdom). The international setting under options in Visual Studio is set
to 'Same as Microsoft Windows'. My windows setting is English - United
Kingdom.
Once the parameters have been entered on the default calendar controls,
their values are converted to US date format (MM/dd/yyyy). Where the UK
date format will not convert, the following error displays:
"An error occurred during local report processing. The report parameter
'StartDate' is not valid for its type."
If anyone has any ideas of how to fix this, then I would be really grateful.
Virtually every report I run has the start and end date parameters, so
unless I fix this, the default method of collecting these parameters is
effectively useless to me.
Thanks in advance,
Ed AllisonInterestingly, this problem does not seem to occur when reports are deployed
to the report server.
Ed Allison
"Ed Allison" <ed@.optix.co.uk> wrote in message
news:O8B4xJlLGHA.3012@.TK2MSFTNGP14.phx.gbl...
> If anyone can help me with this, I would be really grateful. I am using
> Reporting Services 2005 and Visual Studio 2005 for this problem.
> A while back, I had a formatting problem with my reports that was fixed by
> use of the Language property on the report. Although this fixed all
> formatting within the report. However, there is still a problem with the
> calendar controls that collect DateTime report parameters.
> To check that this was not some kind of obscure problem with my particular
> report, I put together a very simple example from the AdventureWorks
> database.
> The dataset was provided by the text query of:
> SELECT Title, BirthDate
> FROM HumanResources.Employee
> WHERE (BirthDate BETWEEN @.StartDate AND @.EndDate)
> The @.StartDate and @.EndDate parameters were set to type DateTime with
> default value of null. I put a two column table on the report, displaying
> Title and BirthDate. The Language of the report is set to English(United
> Kingdom). The international setting under options in Visual Studio is set
> to 'Same as Microsoft Windows'. My windows setting is English - United
> Kingdom.
> Once the parameters have been entered on the default calendar controls,
> their values are converted to US date format (MM/dd/yyyy). Where the UK
> date format will not convert, the following error displays:
> "An error occurred during local report processing. The report parameter
> 'StartDate' is not valid for its type."
> If anyone has any ideas of how to fix this, then I would be really
> grateful. Virtually every report I run has the start and end date
> parameters, so unless I fix this, the default method of collecting these
> parameters is effectively useless to me.
> Thanks in advance,
> Ed Allison
>|||I have this question as well
"Ed Allison" wrote:
> Interestingly, this problem does not seem to occur when reports are deployed
> to the report server.
> Ed Allison
> "Ed Allison" <ed@.optix.co.uk> wrote in message
> news:O8B4xJlLGHA.3012@.TK2MSFTNGP14.phx.gbl...
> > If anyone can help me with this, I would be really grateful. I am using
> > Reporting Services 2005 and Visual Studio 2005 for this problem.
> >
> > A while back, I had a formatting problem with my reports that was fixed by
> > use of the Language property on the report. Although this fixed all
> > formatting within the report. However, there is still a problem with the
> > calendar controls that collect DateTime report parameters.
> >
> > To check that this was not some kind of obscure problem with my particular
> > report, I put together a very simple example from the AdventureWorks
> > database.
> >
> > The dataset was provided by the text query of:
> >
> > SELECT Title, BirthDate
> > FROM HumanResources.Employee
> > WHERE (BirthDate BETWEEN @.StartDate AND @.EndDate)
> >
> > The @.StartDate and @.EndDate parameters were set to type DateTime with
> > default value of null. I put a two column table on the report, displaying
> > Title and BirthDate. The Language of the report is set to English(United
> > Kingdom). The international setting under options in Visual Studio is set
> > to 'Same as Microsoft Windows'. My windows setting is English - United
> > Kingdom.
> >
> > Once the parameters have been entered on the default calendar controls,
> > their values are converted to US date format (MM/dd/yyyy). Where the UK
> > date format will not convert, the following error displays:
> >
> > "An error occurred during local report processing. The report parameter
> > 'StartDate' is not valid for its type."
> >
> > If anyone has any ideas of how to fix this, then I would be really
> > grateful. Virtually every report I run has the start and end date
> > parameters, so unless I fix this, the default method of collecting these
> > parameters is effectively useless to me.
> >
> > Thanks in advance,
> >
> > Ed Allison
> >
>
>|||I have found no solution to this, I am afraid. Since the problem does not
occur when reports are deployed, I just work around it when developing
reports.
Ed Allison
"Tango" <Tango@.discussions.microsoft.com> wrote in message
news:628FB199-1E9A-4723-8748-0C649E3683EA@.microsoft.com...
>I have this question as well
> "Ed Allison" wrote:
>> Interestingly, this problem does not seem to occur when reports are
>> deployed
>> to the report server.
>> Ed Allison
>> "Ed Allison" <ed@.optix.co.uk> wrote in message
>> news:O8B4xJlLGHA.3012@.TK2MSFTNGP14.phx.gbl...
>> > If anyone can help me with this, I would be really grateful. I am
>> > using
>> > Reporting Services 2005 and Visual Studio 2005 for this problem.
>> >
>> > A while back, I had a formatting problem with my reports that was fixed
>> > by
>> > use of the Language property on the report. Although this fixed all
>> > formatting within the report. However, there is still a problem with
>> > the
>> > calendar controls that collect DateTime report parameters.
>> >
>> > To check that this was not some kind of obscure problem with my
>> > particular
>> > report, I put together a very simple example from the AdventureWorks
>> > database.
>> >
>> > The dataset was provided by the text query of:
>> >
>> > SELECT Title, BirthDate
>> > FROM HumanResources.Employee
>> > WHERE (BirthDate BETWEEN @.StartDate AND @.EndDate)
>> >
>> > The @.StartDate and @.EndDate parameters were set to type DateTime with
>> > default value of null. I put a two column table on the report,
>> > displaying
>> > Title and BirthDate. The Language of the report is set to
>> > English(United
>> > Kingdom). The international setting under options in Visual Studio is
>> > set
>> > to 'Same as Microsoft Windows'. My windows setting is English - United
>> > Kingdom.
>> >
>> > Once the parameters have been entered on the default calendar controls,
>> > their values are converted to US date format (MM/dd/yyyy). Where the
>> > UK
>> > date format will not convert, the following error displays:
>> >
>> > "An error occurred during local report processing. The report
>> > parameter
>> > 'StartDate' is not valid for its type."
>> >
>> > If anyone has any ideas of how to fix this, then I would be really
>> > grateful. Virtually every report I run has the start and end date
>> > parameters, so unless I fix this, the default method of collecting
>> > these
>> > parameters is effectively useless to me.
>> >
>> > Thanks in advance,
>> >
>> > Ed Allison
>> >
>>|||Hi Ed,
I have the same problem and strangely - setting language property on
the report to "default" with international setting under options in
Visual Studio set to "English" sorted out the problem.
If for you this is not acceptable - the way arround (at least it works
for me) is not to press "View report" button - but the small green
refresh button on the toolbar on the preview report tab...
Hope this helps
Ivan
Reporting Services 2005 and Visual Studio 2005 for this problem.
A while back, I had a formatting problem with my reports that was fixed by
use of the Language property on the report. Although this fixed all
formatting within the report. However, there is still a problem with the
calendar controls that collect DateTime report parameters.
To check that this was not some kind of obscure problem with my particular
report, I put together a very simple example from the AdventureWorks
database.
The dataset was provided by the text query of:
SELECT Title, BirthDate
FROM HumanResources.Employee
WHERE (BirthDate BETWEEN @.StartDate AND @.EndDate)
The @.StartDate and @.EndDate parameters were set to type DateTime with
default value of null. I put a two column table on the report, displaying
Title and BirthDate. The Language of the report is set to English(United
Kingdom). The international setting under options in Visual Studio is set
to 'Same as Microsoft Windows'. My windows setting is English - United
Kingdom.
Once the parameters have been entered on the default calendar controls,
their values are converted to US date format (MM/dd/yyyy). Where the UK
date format will not convert, the following error displays:
"An error occurred during local report processing. The report parameter
'StartDate' is not valid for its type."
If anyone has any ideas of how to fix this, then I would be really grateful.
Virtually every report I run has the start and end date parameters, so
unless I fix this, the default method of collecting these parameters is
effectively useless to me.
Thanks in advance,
Ed AllisonInterestingly, this problem does not seem to occur when reports are deployed
to the report server.
Ed Allison
"Ed Allison" <ed@.optix.co.uk> wrote in message
news:O8B4xJlLGHA.3012@.TK2MSFTNGP14.phx.gbl...
> If anyone can help me with this, I would be really grateful. I am using
> Reporting Services 2005 and Visual Studio 2005 for this problem.
> A while back, I had a formatting problem with my reports that was fixed by
> use of the Language property on the report. Although this fixed all
> formatting within the report. However, there is still a problem with the
> calendar controls that collect DateTime report parameters.
> To check that this was not some kind of obscure problem with my particular
> report, I put together a very simple example from the AdventureWorks
> database.
> The dataset was provided by the text query of:
> SELECT Title, BirthDate
> FROM HumanResources.Employee
> WHERE (BirthDate BETWEEN @.StartDate AND @.EndDate)
> The @.StartDate and @.EndDate parameters were set to type DateTime with
> default value of null. I put a two column table on the report, displaying
> Title and BirthDate. The Language of the report is set to English(United
> Kingdom). The international setting under options in Visual Studio is set
> to 'Same as Microsoft Windows'. My windows setting is English - United
> Kingdom.
> Once the parameters have been entered on the default calendar controls,
> their values are converted to US date format (MM/dd/yyyy). Where the UK
> date format will not convert, the following error displays:
> "An error occurred during local report processing. The report parameter
> 'StartDate' is not valid for its type."
> If anyone has any ideas of how to fix this, then I would be really
> grateful. Virtually every report I run has the start and end date
> parameters, so unless I fix this, the default method of collecting these
> parameters is effectively useless to me.
> Thanks in advance,
> Ed Allison
>|||I have this question as well
"Ed Allison" wrote:
> Interestingly, this problem does not seem to occur when reports are deployed
> to the report server.
> Ed Allison
> "Ed Allison" <ed@.optix.co.uk> wrote in message
> news:O8B4xJlLGHA.3012@.TK2MSFTNGP14.phx.gbl...
> > If anyone can help me with this, I would be really grateful. I am using
> > Reporting Services 2005 and Visual Studio 2005 for this problem.
> >
> > A while back, I had a formatting problem with my reports that was fixed by
> > use of the Language property on the report. Although this fixed all
> > formatting within the report. However, there is still a problem with the
> > calendar controls that collect DateTime report parameters.
> >
> > To check that this was not some kind of obscure problem with my particular
> > report, I put together a very simple example from the AdventureWorks
> > database.
> >
> > The dataset was provided by the text query of:
> >
> > SELECT Title, BirthDate
> > FROM HumanResources.Employee
> > WHERE (BirthDate BETWEEN @.StartDate AND @.EndDate)
> >
> > The @.StartDate and @.EndDate parameters were set to type DateTime with
> > default value of null. I put a two column table on the report, displaying
> > Title and BirthDate. The Language of the report is set to English(United
> > Kingdom). The international setting under options in Visual Studio is set
> > to 'Same as Microsoft Windows'. My windows setting is English - United
> > Kingdom.
> >
> > Once the parameters have been entered on the default calendar controls,
> > their values are converted to US date format (MM/dd/yyyy). Where the UK
> > date format will not convert, the following error displays:
> >
> > "An error occurred during local report processing. The report parameter
> > 'StartDate' is not valid for its type."
> >
> > If anyone has any ideas of how to fix this, then I would be really
> > grateful. Virtually every report I run has the start and end date
> > parameters, so unless I fix this, the default method of collecting these
> > parameters is effectively useless to me.
> >
> > Thanks in advance,
> >
> > Ed Allison
> >
>
>|||I have found no solution to this, I am afraid. Since the problem does not
occur when reports are deployed, I just work around it when developing
reports.
Ed Allison
"Tango" <Tango@.discussions.microsoft.com> wrote in message
news:628FB199-1E9A-4723-8748-0C649E3683EA@.microsoft.com...
>I have this question as well
> "Ed Allison" wrote:
>> Interestingly, this problem does not seem to occur when reports are
>> deployed
>> to the report server.
>> Ed Allison
>> "Ed Allison" <ed@.optix.co.uk> wrote in message
>> news:O8B4xJlLGHA.3012@.TK2MSFTNGP14.phx.gbl...
>> > If anyone can help me with this, I would be really grateful. I am
>> > using
>> > Reporting Services 2005 and Visual Studio 2005 for this problem.
>> >
>> > A while back, I had a formatting problem with my reports that was fixed
>> > by
>> > use of the Language property on the report. Although this fixed all
>> > formatting within the report. However, there is still a problem with
>> > the
>> > calendar controls that collect DateTime report parameters.
>> >
>> > To check that this was not some kind of obscure problem with my
>> > particular
>> > report, I put together a very simple example from the AdventureWorks
>> > database.
>> >
>> > The dataset was provided by the text query of:
>> >
>> > SELECT Title, BirthDate
>> > FROM HumanResources.Employee
>> > WHERE (BirthDate BETWEEN @.StartDate AND @.EndDate)
>> >
>> > The @.StartDate and @.EndDate parameters were set to type DateTime with
>> > default value of null. I put a two column table on the report,
>> > displaying
>> > Title and BirthDate. The Language of the report is set to
>> > English(United
>> > Kingdom). The international setting under options in Visual Studio is
>> > set
>> > to 'Same as Microsoft Windows'. My windows setting is English - United
>> > Kingdom.
>> >
>> > Once the parameters have been entered on the default calendar controls,
>> > their values are converted to US date format (MM/dd/yyyy). Where the
>> > UK
>> > date format will not convert, the following error displays:
>> >
>> > "An error occurred during local report processing. The report
>> > parameter
>> > 'StartDate' is not valid for its type."
>> >
>> > If anyone has any ideas of how to fix this, then I would be really
>> > grateful. Virtually every report I run has the start and end date
>> > parameters, so unless I fix this, the default method of collecting
>> > these
>> > parameters is effectively useless to me.
>> >
>> > Thanks in advance,
>> >
>> > Ed Allison
>> >
>>|||Hi Ed,
I have the same problem and strangely - setting language property on
the report to "default" with international setting under options in
Visual Studio set to "English" sorted out the problem.
If for you this is not acceptable - the way arround (at least it works
for me) is not to press "View report" button - but the small green
refresh button on the toolbar on the preview report tab...
Hope this helps
Ivan
Wednesday, March 7, 2012
Report Jump in Page Header
I tried to add a report jump to a page header - visual studio mentions that this is not supported by all renders, but I did not find any information which renderers support this. It seems the default html renderer does not support it, because i receive the following error
"The path of the item "(null)" is not valid. The path must be less than 260 characters long and must start with slash. Other restrictions apply. (rsInvalidItemPath)"
while I only specify the report name.
"The path of the item "(null)" is not valid. The path must be less than 260 characters long and must start with slash. Other restrictions apply. (rsInvalidItemPath)"
while I only specify the report name.
Is there a way to add a report jump to the page header ? with parameters ?
I have an startpage with links to each report - and in the header of the reports a want to support a back to the table of content link. Is there a othere way so switch back to the origninal report (after some parameter switches) ?
Thanks
HANNES
As indicated by the publishing warning message in report designer preview, drillthrough actions are currently not supported in page headers/footers in RS 2005.
The closest you can get for the page header/footer is to use a hyperlink action and build a url that points back to the report server and uses URL access to run a report with certain parameter settings. The Globals collection in the report object model exposes properties such as ReportServerUrl that you will need to build the URL - see also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rscreate/htm/rcr_creating_expressions_v1_7ilv.asp
-- Robert
report item not linked to a dataset
Hi,
I'm using SQLServer 2000 and Visual Studio 2003.
Today all the sudden in Visual Studio the field list pane is empty for all
reports I have created. When I try to ad a field using Expressions, I receive
the message "report item not linked to a dataset". As a source for the
dataset I use a storede procedure.
The reports can still be used. I just cannot properly edit them anymore.
When l look at the xml code, the fields are in the report.
--
JanHi Jan
Have you tried right-clicking on the table in the report, going to properties,
then linking it to a dataset manually?
I've never had reports suddenly lose their datasets like that, but there are
often times when I add a table to a report and it isn't automatically linked
to a dataset.
Jan Hussaarts wrote:
>Hi,
>I'm using SQLServer 2000 and Visual Studio 2003.
>Today all the sudden in Visual Studio the field list pane is empty for all
>reports I have created. When I try to ad a field using Expressions, I receive
>the message "report item not linked to a dataset". As a source for the
>dataset I use a storede procedure.
>The reports can still be used. I just cannot properly edit them anymore.
>When l look at the xml code, the fields are in the report.|||The point is that normally there is a Fields pane on the left of the screen.
Add a table and you can drop a Field from the Fields pane on a cell in the
table. The field pane remains empty after manually linking the table to the
dataset.|||Have you checked your dataset to make sure it can still access the data?
If there is no dataset, or if you don't have access to the data for whatever
reason (maybe your user account doesn't have authority to view the data) then
the fields pane will remain empty, since RS can't actually see the fields
returned by the dataset query.
Jan Hussaarts wrote:
>The point is that normally there is a Fields pane on the left of the screen.
>Add a table and you can drop a Field from the Fields pane on a cell in the
>table. The field pane remains empty after manually linking the table to the
>dataset.
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200509/1|||When I look at de rdl version of the report, under < Datasets> the dataset
and all the fields that are output of the stored procedure are there. So,
access rights are ok. It is just the Fields pane that remains empty.
I'm thinking of uninstalling and installing RS. I think that might solve the
problem. It has taken a lot of my time up till now.|||unable to add a field in report viewer which is not selected in datase
From http://www.developmentnow.com/g/115_2005_9_0_0_598578/report-item-not-linked-to-a-dataset.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||unable to add a field in report viewer which is not selected in datase
From http://www.developmentnow.com/g/115_2005_9_0_0_598578/report-item-not-linked-to-a-dataset.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||In the future post your problem. Don't expect us to follow a link. I almost
just ignored this.
Go into the dataset that is no longer showing the field list and click on
the refresh fields button (it is to the right of the ...). See if that
brings back the field list.
This sometimes occurs with stored procedures. If it does not bring back the
list then it is possible that somebody has modified that stored procedure in
such a way that it causes a problem.
First see if this fixes your problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sunil tripathi" <sunil137_bpl@.yahoo.com> wrote in message
news:cbbcde3f-6750-4e12-bc8c-9a0d62474c18@.developmentnow.com...
> unable to add a field in report viewer which is not selected in dataset
> From
> http://www.developmentnow.com/g/115_2005_9_0_0_598578/report-item-not-linked-to-a-dataset.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
I'm using SQLServer 2000 and Visual Studio 2003.
Today all the sudden in Visual Studio the field list pane is empty for all
reports I have created. When I try to ad a field using Expressions, I receive
the message "report item not linked to a dataset". As a source for the
dataset I use a storede procedure.
The reports can still be used. I just cannot properly edit them anymore.
When l look at the xml code, the fields are in the report.
--
JanHi Jan
Have you tried right-clicking on the table in the report, going to properties,
then linking it to a dataset manually?
I've never had reports suddenly lose their datasets like that, but there are
often times when I add a table to a report and it isn't automatically linked
to a dataset.
Jan Hussaarts wrote:
>Hi,
>I'm using SQLServer 2000 and Visual Studio 2003.
>Today all the sudden in Visual Studio the field list pane is empty for all
>reports I have created. When I try to ad a field using Expressions, I receive
>the message "report item not linked to a dataset". As a source for the
>dataset I use a storede procedure.
>The reports can still be used. I just cannot properly edit them anymore.
>When l look at the xml code, the fields are in the report.|||The point is that normally there is a Fields pane on the left of the screen.
Add a table and you can drop a Field from the Fields pane on a cell in the
table. The field pane remains empty after manually linking the table to the
dataset.|||Have you checked your dataset to make sure it can still access the data?
If there is no dataset, or if you don't have access to the data for whatever
reason (maybe your user account doesn't have authority to view the data) then
the fields pane will remain empty, since RS can't actually see the fields
returned by the dataset query.
Jan Hussaarts wrote:
>The point is that normally there is a Fields pane on the left of the screen.
>Add a table and you can drop a Field from the Fields pane on a cell in the
>table. The field pane remains empty after manually linking the table to the
>dataset.
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200509/1|||When I look at de rdl version of the report, under < Datasets> the dataset
and all the fields that are output of the stored procedure are there. So,
access rights are ok. It is just the Fields pane that remains empty.
I'm thinking of uninstalling and installing RS. I think that might solve the
problem. It has taken a lot of my time up till now.|||unable to add a field in report viewer which is not selected in datase
From http://www.developmentnow.com/g/115_2005_9_0_0_598578/report-item-not-linked-to-a-dataset.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||unable to add a field in report viewer which is not selected in datase
From http://www.developmentnow.com/g/115_2005_9_0_0_598578/report-item-not-linked-to-a-dataset.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||In the future post your problem. Don't expect us to follow a link. I almost
just ignored this.
Go into the dataset that is no longer showing the field list and click on
the refresh fields button (it is to the right of the ...). See if that
brings back the field list.
This sometimes occurs with stored procedures. If it does not bring back the
list then it is possible that somebody has modified that stored procedure in
such a way that it causes a problem.
First see if this fixes your problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sunil tripathi" <sunil137_bpl@.yahoo.com> wrote in message
news:cbbcde3f-6750-4e12-bc8c-9a0d62474c18@.developmentnow.com...
> unable to add a field in report viewer which is not selected in dataset
> From
> http://www.developmentnow.com/g/115_2005_9_0_0_598578/report-item-not-linked-to-a-dataset.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
Saturday, February 25, 2012
Report in Report Manager (server) does not look the same way that it looks in the Visual Studio
I am using SSRS 2005 and my server is a Microsoft Windows Server 2003 Enterprise Edition Service Pack 1.
Most of the differences between VS and Report Manager are formatting differences. Borders won't show up, scrolling does not work etc. Is there something i need to upgrade on the server.
Last thing but not the least. Everytime i change something in regards to the parameters i need to delete the report from the report manager and deploy in order for the change to appear on the Report Manager. Is there a fix for this?
Could somebody please help me with these?
1. differences in rendering between design-time and run-time -- the renderer used in Report Designer is quite different than the renderer used in Report Manager. The Designer renderer is GDI-based, whereas the Report Manager renderer is HTML-based. There are many differences between these renderers, including handling of overlapping items, borders, and pagination.
2. changes to parameters made at design-time require deletion and republishing -- this is an artifact of our "server wins" philosophy. Since you can change parameter characteristics in the Report Server after a report has been published 9and therefore which may conflict with the characteristics stored in the RDL), it is indeterminate which version of the parameters a user expects to be persisted -- do you expect customizations made after publishing to dominate, or does republishing dominate? We chose to go with the server's version of parameters. Note that if we chose the other way, you would lose server-based parameter customizations everytime you republished an RDL. Admittedly it it would be nice to give users control over this, like with an RDL-based design-time option to choose which parameter collection dominates, or a publish-time option so you could choose one or the other at publish time.
|||You mean there is no way i can reproduce my params changes in the report manager with out deleting the report itself. Everytime i do that it deletes all the subscriptions on my report. Isn't there any work around?|||Go ahead and republish the RDL, but don't bother making changes to the parameter properties in Report Designer -- just make them directly in the Report Manager or Management Studio UI.
If you need to change the # or name of the parameters, that will have to be done in Report Designer.
Report in Report Manager (server) does not look the same way that it looks in the Visual Stu
I am using SSRS 2005 and my server is a Microsoft Windows Server 2003 Enterprise Edition Service Pack 1.
Most of the differences between VS and Report Manager are formatting differences. Borders won't show up, scrolling does not work etc. Is there something i need to upgrade on the server.
Last thing but not the least. Everytime i change something in regards to the parameters i need to delete the report from the report manager and deploy in order for the change to appear on the Report Manager. Is there a fix for this?
Could somebody please help me with these?
1. differences in rendering between design-time and run-time -- the renderer used in Report Designer is quite different than the renderer used in Report Manager. The Designer renderer is GDI-based, whereas the Report Manager renderer is HTML-based. There are many differences between these renderers, including handling of overlapping items, borders, and pagination.
2. changes to parameters made at design-time require deletion and republishing -- this is an artifact of our "server wins" philosophy. Since you can change parameter characteristics in the Report Server after a report has been published 9and therefore which may conflict with the characteristics stored in the RDL), it is indeterminate which version of the parameters a user expects to be persisted -- do you expect customizations made after publishing to dominate, or does republishing dominate? We chose to go with the server's version of parameters. Note that if we chose the other way, you would lose server-based parameter customizations everytime you republished an RDL. Admittedly it it would be nice to give users control over this, like with an RDL-based design-time option to choose which parameter collection dominates, or a publish-time option so you could choose one or the other at publish time.
|||You mean there is no way i can reproduce my params changes in the report manager with out deleting the report itself. Everytime i do that it deletes all the subscriptions on my report. Isn't there any work around?|||Go ahead and republish the RDL, but don't bother making changes to the parameter properties in Report Designer -- just make them directly in the Report Manager or Management Studio UI.
If you need to change the # or name of the parameters, that will have to be done in Report Designer.
Subscribe to:
Posts (Atom)