Handle Postbacks

RS2000
If a report have several parameter dropdowns, the data for each populated
dropdown is fetched again when data for non populated drop down is fetched.
Is there a way to handle postbacks events/viewstate more effective?
Regards Martin BringHave you created your own asp.net dropdowns to feed the parameters into the
report url address?
You can use the Atlas framework from Microsoft (see http://atlas.asp.net).
This allows partial postbacks of an asp.net 2.0 page, perfect for dependent
dropdowns...
"Maran" wrote:
> RS2000
> If a report have several parameter dropdowns, the data for each populated
> dropdown is fetched again when data for non populated drop down is fetched.
> Is there a way to handle postbacks events/viewstate more effective?
> Regards Martin Bring|||Thank you for replying.
No, I am just using the "out-of-the-box" functionality and so will it stay
for some time. In the future we might use our own code for paramters and
h´just call RS web service.
Regards Martin
************
"NH" wrote:
> Have you created your own asp.net dropdowns to feed the parameters into the
> report url address?
> You can use the Atlas framework from Microsoft (see http://atlas.asp.net).
> This allows partial postbacks of an asp.net 2.0 page, perfect for dependent
> dropdowns...
> "Maran" wrote:
> > RS2000
> >
> > If a report have several parameter dropdowns, the data for each populated
> > dropdown is fetched again when data for non populated drop down is fetched.
> >
> > Is there a way to handle postbacks events/viewstate more effective?
> >
> > Regards Martin Bring|||I am not sure I fully understand what problem you have. Are you trying to
have dependent dropdowns in the report viewer ?
"Maran" wrote:
> Thank you for replying.
> No, I am just using the "out-of-the-box" functionality and so will it stay
> for some time. In the future we might use our own code for paramters and
> h´just call RS web service.
> Regards Martin
> ************
> "NH" wrote:
> > Have you created your own asp.net dropdowns to feed the parameters into the
> > report url address?
> >
> > You can use the Atlas framework from Microsoft (see http://atlas.asp.net).
> > This allows partial postbacks of an asp.net 2.0 page, perfect for dependent
> > dropdowns...
> >
> > "Maran" wrote:
> >
> > > RS2000
> > >
> > > If a report have several parameter dropdowns, the data for each populated
> > > dropdown is fetched again when data for non populated drop down is fetched.
> > >
> > > Is there a way to handle postbacks events/viewstate more effective?
> > >
> > > Regards Martin Bring|||Yes, our parameter dropdowns is dependent on each other.
For example: If the user choose a country in one dropdown, regions will show
in another dropdown.
When running the report from the report server the data for the dropdowns
will be fetched each time (for the populated ones). Relating to ASP.Net I
would like the report to have som "ViewState" to remember the data it have
already fetched.
I just found out today that running the report in Visual Studio will not
fetch the data twice.
Regards
Martin Bring
"NH" wrote:
> I am not sure I fully understand what problem you have. Are you trying to
> have dependent dropdowns in the report viewer ?
> "Maran" wrote:
> > Thank you for replying.
> >
> > No, I am just using the "out-of-the-box" functionality and so will it stay
> > for some time. In the future we might use our own code for paramters and
> > h´just call RS web service.
> >
> > Regards Martin
> >
> > ************
> >
> > "NH" wrote:
> >
> > > Have you created your own asp.net dropdowns to feed the parameters into the
> > > report url address?
> > >
> > > You can use the Atlas framework from Microsoft (see http://atlas.asp.net).
> > > This allows partial postbacks of an asp.net 2.0 page, perfect for dependent
> > > dropdowns...
> > >
> > > "Maran" wrote:
> > >
> > > > RS2000
> > > >
> > > > If a report have several parameter dropdowns, the data for each populated
> > > > dropdown is fetched again when data for non populated drop down is fetched.
> > > >
> > > > Is there a way to handle postbacks events/viewstate more effective?
> > > >
> > > > Regards Martin Bring