Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
abbieharrison1
Contributor III
Contributor III

Keep getting "An error occurred. Invalid parameters" Qlik Sense

Hi,

We are currently using  Qlik Sense enterprise on windows May 2023 patch 1 (14.129.7) and are getting "An error occurred. Invalid parameters" messages daily while developing our apps. This is happening to multiple developers on different apps when amending tables and pivot tables e.g. amending existing measures, adding measures

Does anyone have any ideas of why this is happening and how we prevent it? We have looked at the patch 2 release notes and they don't seem to mention a bug fix for this.
It seems to go away when we stop editing and refresh the page but then happens again later in the day

Edit: We now have tables that are unusable. We cannot remove measures from them without getting the error message so are having to create our tables from scratch

abbieharrison1_0-1689175643787.png

Thanks,

Abbie

Labels (1)
24 Replies
salshute
Partner - Contributor III
Partner - Contributor III

We are on February 2024 Patch 7 and have the same issue with a master visualisation that is used in a tabbed container.

ADRANGI
Contributor
Contributor

Can you please tell how you have identified that the issue is with that specific master visualization used in a tabbed container.

BTW we are also facing the same issue and are currently running on May 2023 Patch4

kleeone
Contributor
Contributor

Is there a solution for this? Is this only an issue in development or does it affect end users who are in the published app?

salshute
Partner - Contributor III
Partner - Contributor III

It doesn't seem to affect end users. I have found a workaround within tables. You have to add another dimension to the table (you can then immediately remove it), and that will allow you to work and make changes. If you don't do this, no changes you make will take effect. It is incredibly frustrating.

 

howdash
Creator II
Creator II

This seems like a legitimate bug. I would think it should be reported to Qlik for them to be aware of it, take a look at it, and fix it. But I don't actually know if there's a dedicated channel where we can report Qlik Sense bugs.

Does anyone know if there's a team at Qlik that can be contacted to officially report bugs like these along with steps to reproduce them?