[Closed] Prompt page - previous choice retention

[JoeBass]

When we upgraded from MR1 to MR2, our reports lost the ability to retain the prompt value lists and selections that were generated and picked when the report was last run.Ã, 

Strangely, this is not always the case.Ã,  Sometimes, the lists and previous user choices appear to be stored, as the list boxes appear re-populated, with highlighted choices.Ã,  When this happens and the user submits the report without re-cascading prompt values, default value prompts are presented as the parameters don't seem to respect the highlighted choices.

Has anyone developed a work-around for this "enhancement"?

[raro]

Hi  JoeBass,

we also expierenced this feature and decided to accept it as is, because:

as it is now (after MR2 update) users just clicking around can't actually
destroy a valuable selection made by someone else before. (if you
didn't set the write protection)
=> now we have a write protection (almost) as default
=> now we modify values we need more frequently to be
     changed with the properties page of the report.

hopefully our arguments may lead your customers back to the
satisfaction trail  ;)

have fun,
ralf

[JoeBass]

Hi Raro,
Ã,  I'm not sure what you mean by "as it is now (after MR2 update) users just clicking around can't actually
destroy a valuable selection made by someone else before. (if you didn't set the write protection)" or "now we modify values we need more frequently to be changed with the properties page of the report."?  Can you explain it to me another way?

Ã,  I miss MR1's ability to cache lookup-type, prompt-filling data.Ã,  It is confusing to the user when it appears as if the prompts are filled and selected with the choices from their last run but, then they are prompted with the ugly, default prompts after hitting the run button because the parameters actually have not been set.Ã, 

Ã,  I'm glad you've found a silver lining for your application though.

[raro]

  I'm not sure what you mean by "as it is now (after MR2 update) users just clicking around can't actually
destroy a valuable selection made by someone else before. (if you didn't set the write protection)" or "now we modify values we need more frequently to be changed with the properties page of the report."?  Can you explain it to me another way?

Of course :-)

If you have a long list of items in your selectionbox, the
users have to scroll to see the last items. A not so expierenced
user might as well click into the selectionbox (by accident instead of scrolling)
... this way he changes the parameters without actually wanting to
and then runs the report by pressing "OK".

Or the users just runs the report for testing - changes the
parameters and the parameters are saved.

The next user running the report will see parameters "selected
by accident" or "just for testing".

With MR1 - the user changed the parameters each time running the report.

With MR2 this will not happen.

With MR2 you can only "preset" the parameters with your "first run" or
by selecting the properties of your report - but not "by accident".

Hope this helps.

regards,
RaRo

P.S. although I would have prefered to not learn
from Users about this "feature" ;-)