topic Re: Unable to save the Script after Session's name is updated in App Development

Unable to save the Script after Session's name is updated

vlad_komarov — Sat, 16 Nov 2024 21:53:41 GMT

Since there is no "Qlik Bugs" forum on the new community anymore (??), posting it here.

Looks like there is a new bug in Sept 2018 SR1 release.

Changing the Session's name in the Script editor does not update the status of the app. QS does not recognize the file being changed and your updates will be lost unless you making changes in the script's body as well and save the changes after.

It did work before, but stopped with the latest release.

Will submit the support case, just sharing here so you can avoid the changes loss.

Regards,

Re: Unable to save the Script after Session's name is updated

Bill_Britt — Wed, 14 Nov 2018 16:07:00 GMT

Hi,

If you think this is a bug, please open a support ticket so the issue can be reviewed and a bug logged.

Bill

Re: Unable to save the Script after Session's name is updated

vlad_komarov — Wed, 14 Nov 2018 16:08:54 GMT

Already did.

Just posting here to alert the community since there is no "Qlik Bugs" forum anymore...

Re: Unable to save the Script after Session's name is updated

vlad_komarov — Thu, 15 Nov 2018 02:58:27 GMT

Sorry all.

False alarm. My browser was behaving (!@#!) earlier today, but I did not realize that it was the reason for Session's renaming issue until I've restarted my system.

The issue is no longer reproducible....