Hello,
Situation:
- a report with cascading parameters [A], [B], [C]
- first parameter [A] loaded via non-queried values
- second parameter [B] loaded via stored procedure, taking [A] and a
constant as input (via dataset dsB)
- third parameter [C] loaded via the same stored procedure, taking [A] and
[B] as input (via dataset dsC)
When I preview this report:
- initial view ok
- modify [A] -> [B] changes accordingly
- modify [B] -> the designer starts flickering and goes into a never ending
loop.
The deployed report works just fine and as expected.
Bug ? Any work arounds ?
Thanks for any input!
TomSounds like a bug. There is another bug I have found with the preview tab
and cascading parameters. It only cascades once. I.e. if you go back a
second time and change A it does not change B. Again, deploy works fine. I
have access to the the internal bug reporting tool and when I report the
previous but I'll do this one too. I am not aware of any workaround. At
least it works in deployed mode.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Tom VdP" <unick@.hot_mail_.c-o-m> wrote in message
news:1FBF14D5-28E3-4B76-93BF-47F292BC33FE@.microsoft.com...
> Hello,
> Situation:
> - a report with cascading parameters [A], [B], [C]
> - first parameter [A] loaded via non-queried values
> - second parameter [B] loaded via stored procedure, taking [A] and a
> constant as input (via dataset dsB)
> - third parameter [C] loaded via the same stored procedure, taking [A] and
> [B] as input (via dataset dsC)
> When I preview this report:
> - initial view ok
> - modify [A] -> [B] changes accordingly
> - modify [B] -> the designer starts flickering and goes into a never
ending
> loop.
> The deployed report works just fine and as expected.
> Bug ? Any work arounds ?
> Thanks for any input!
> Tom|||Thanks for reporting it.
It is annoying as the first parameter in our reports is the choice of
language. Depending on the selection the contents of the other dropdown
boxes is changed.
So we have cascading parameters in every report.
But we can use the deployed reports luckily.
Regards,
Tom
"Bruce L-C [MVP]" wrote:
> Sounds like a bug. There is another bug I have found with the preview tab
> and cascading parameters. It only cascades once. I.e. if you go back a
> second time and change A it does not change B. Again, deploy works fine. I
> have access to the the internal bug reporting tool and when I report the
> previous but I'll do this one too. I am not aware of any workaround. At
> least it works in deployed mode.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Tom VdP" <unick@.hot_mail_.c-o-m> wrote in message
> news:1FBF14D5-28E3-4B76-93BF-47F292BC33FE@.microsoft.com...
> >
> > Hello,
> >
> > Situation:
> > - a report with cascading parameters [A], [B], [C]
> > - first parameter [A] loaded via non-queried values
> > - second parameter [B] loaded via stored procedure, taking [A] and a
> > constant as input (via dataset dsB)
> > - third parameter [C] loaded via the same stored procedure, taking [A] and
> > [B] as input (via dataset dsC)
> >
> > When I preview this report:
> > - initial view ok
> > - modify [A] -> [B] changes accordingly
> > - modify [B] -> the designer starts flickering and goes into a never
> ending
> > loop.
> >
> > The deployed report works just fine and as expected.
> >
> > Bug ? Any work arounds ?
> >
> > Thanks for any input!
> > Tom
>
>|||I am not using cascading parameters but I have experieced a similiar problems
with the Report Designer preview (loops) and I sometimes get a Processing
Error 'Specified Cast in not Valid' , If I remove the Page Header OR Footer I
do not get the error, OR if there is labels only (no ReportItems! or Globals!
in the header/footer) it works.
There are no problems when the report is deployed.
"Tom VdP" wrote:
> Thanks for reporting it.
> It is annoying as the first parameter in our reports is the choice of
> language. Depending on the selection the contents of the other dropdown
> boxes is changed.
> So we have cascading parameters in every report.
> But we can use the deployed reports luckily.
> Regards,
> Tom
>
> "Bruce L-C [MVP]" wrote:
> > Sounds like a bug. There is another bug I have found with the preview tab
> > and cascading parameters. It only cascades once. I.e. if you go back a
> > second time and change A it does not change B. Again, deploy works fine. I
> > have access to the the internal bug reporting tool and when I report the
> > previous but I'll do this one too. I am not aware of any workaround. At
> > least it works in deployed mode.
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> >
> > "Tom VdP" <unick@.hot_mail_.c-o-m> wrote in message
> > news:1FBF14D5-28E3-4B76-93BF-47F292BC33FE@.microsoft.com...
> > >
> > > Hello,
> > >
> > > Situation:
> > > - a report with cascading parameters [A], [B], [C]
> > > - first parameter [A] loaded via non-queried values
> > > - second parameter [B] loaded via stored procedure, taking [A] and a
> > > constant as input (via dataset dsB)
> > > - third parameter [C] loaded via the same stored procedure, taking [A] and
> > > [B] as input (via dataset dsC)
> > >
> > > When I preview this report:
> > > - initial view ok
> > > - modify [A] -> [B] changes accordingly
> > > - modify [B] -> the designer starts flickering and goes into a never
> > ending
> > > loop.
> > >
> > > The deployed report works just fine and as expected.
> > >
> > > Bug ? Any work arounds ?
> > >
> > > Thanks for any input!
> > > Tom
> >
> >
> >
Showing posts with label loaded. Show all posts
Showing posts with label loaded. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
Report Designer Client software
I've loaded the Report Services from Microsoft unto our server. How do I get the Client Designer tool loaded on other boxes. Does anyone know where the Install is to install the report designer into a Client machine?
Thanks
AlFound the answer already - You run the Report Services Install disk and disable the report services part of the install and only install the report designer.. dah.. Anyway it took me about a half hour to remember that SQL makes you run through the SQL Server install disk to load just the client. That was my clue to install the Designer portion of the software.
Thanks anyway.
ALsql
Subscribe to:
Posts (Atom)