Bart A. Lewin

I have recently upgraded from ART version 6.22 to 8.3. All reports seem to run fine without change with one minor exception. One report, when selected to run, displays the selection parameters. After it runs, the parameters disappear, forcing the user to use the browser's Back Button to run the report with new filter values. Other reports work properly, whereby the selection criteria reappears above the report results. Please see the screen shots. The report did work properly (selection criteria...

Brilliant. Thank you, sir.

@tanyona, I cloned the reports as you suggested and found it did not affect the report's operation at all--the Parameters button behaved the same as on the original report. I also checked your online demo, and the parameter button behaves the same way there. It looks like the save and clear parameters feature has been removed. This is fine for, my use cases. I suggest only removing the down arrow from the button label to reduce confusion. I also emptied the ART_SAVED_PARAMETERS tables, and the reports...

@tanyona, I cloned the reports as you suggested and found it did not affect the report's operation at all--the Parameter button behaved the same as on the original report. I also checked your online demo, and the parameter button behaves the same way there. It looks like the save and clear parameters feature has been removed. This is fine for, my use cases. I suggest only removing the down arrow from the button label to reduce confusion. I also emptied the ART_SAVED_PARAMETERS tables, and the reports...

I will give cloning the report a try in V6.22 and report back to you, @tanyona. In the meantime, there is a table in ART_db called ART_db.ART_SAVED_PARAMETERS; with this specification: CREATE TABLE IF NOT EXISTS `ART_SAVED_PARAMETERS` ( `USER_ID` int(11) NOT NULL, `REPORT_ID` int(11) NOT NULL, `PARAM_NAME` varchar(60) NOT NULL, `PARAM_VALUE` varchar(4000) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; It currently contains records, and for those that did save parameters at one time, the saved...

We went from Ver 5.14 to 6.22; performing the updates to 5.26, 6.0 along the way, @tanyona.

We went from Ver 5.14 to 6.22; performing updates to 5.26, 6.0 along the way, @tanyona.