Prev: RB Report Model Warnings and Errors
Next: Deployment of reports error
From: Patrice on 7 Oct 2009 13:23
Hi all,

Just wanted to know if someone saw the following situation. I have a report
that uses dependent parameters and works fine in Visual Studio.
When deployed on a dev server, one of the hidden parameter is shown.
When the same report is deployed on another server that is at the same
product level, one of the parameter that should be shown is hidden (perhaps
in addition to the problem above).

My layout is :
- the user enters a date
- a parameters is defined as a reference to the previous parameters to feed
a query that lists projects active at the previous date
- the user selects an employee category
- an parameter is defined as a reference to the first parameter (so same
expression as param #2) so that both the date and the category feeds a query
that lists the users active at this date and belonging to the selected
categories

And I've got the problem listed in the first paragraph. I tried also another
setup (where date A is user entered and then I have an hidden B parameter
set to date A and then another hidden C parameter set to date B, it works
fine also in VS, but has the same problem on the RS 2005 servers).

This report is used in the context of Dynamics AX (but I don't think this is
the issue, its only contribution being to feed yet another parameter (which
is hidden) with the current company name used for the AX session).

So :
- is there another way to have the user entering a date and then having
other parameters showing values depending on this date ?
- if this is the right way to do this, do you have seen this behavior and
how have you fixed it ?

For now I've been able to workaround the problem by reading the parameters
using RS web services. I see that the parameter that references the user
entered parameter has true for the value "PromtUser" (which is not what I
expect). I then change this value to fix the problem. I would be still
curious though to find out what goes wrong and if possible avoid having to
use a custom tool to "fix" this issue.

TIA
--
Patrice





From: Patrice on 8 Oct 2009 05:40
> For now I've been able to workaround the problem by reading the parameters
> using RS web services. I see that the parameter that references the user
> entered parameter has true for the value "PromtUser" (which is not what I
> expect). I then change this value to fix the problem. I would be still
> curious though to find out what goes wrong and if possible avoid having to
> use a custom tool to "fix" this issue.

It seems it has definitely fix the issue. If I upload an updated version I
don't have this problem any more. For now it seems that something gone wrong
on the fist load and that when a new RDL file is uploaded there is a logic
that udpates the current report definition rather than replacing it entirely
(keeping the bad setting until it is fixed)...

One thing I didn't thought I could try would have been to delete the report
and to upload it again (my assumption was that it basically replaces the
report definition, it seems it rather updates the existing definition).
Really strange...

--
Patrice


 | 
Pages: 1
Prev: RB Report Model Warnings and Errors
Next: Deployment of reports error