topic Re: Cannot change name of Data Connection in Connectivity & Data Prep

Cannot change name of Data Connection

pwagner — Thu, 23 Dec 2021 14:59:21 GMT

Hello community,

I am facing a strange behaviour of Qlik Sense November 2019 P1:

We have a data connection 'WAG' but for any reason in the data editor the data connection has the name 'WAG (be-terna/wag)'

I have saved the data connection several times. Refreshed, closed and opened the browser several times.

Do you have any idea how to solve this issue? Is it a bug from November 2019?

Thank you. Best regards, Patrick

Re: Cannot change name of Data Connection

Anil_Babu_Samineni — Mon, 30 Dec 2019 08:33:24 GMT

once you edited the proper name in QMC you need to refresh hub to effect that.

Re: Cannot change name of Data Connection

pwagner — Mon, 30 Dec 2019 08:40:50 GMT

I have done this several time, unfortunately without an effect.

Re: Cannot change name of Data Connection

Anil_Babu_Samineni — Mon, 30 Dec 2019 08:43:57 GMT

Where did you tried? Is that the public URL or any other RIM or central Nodes? Try to refresh the QMC first and check again If that refreshed to normal from your name indexing. Off course, Sometimes in QMC may fails as well.

Clear the Cache in browser if QMC is good and then retry the URL of connection?

Re: Cannot change name of Data Connection

pwagner — Mon, 30 Dec 2019 09:13:05 GMT

I figured out if I work directly on the Qlik Sense server (central node) via Remotedesktopconnection, the data connection has in the QMC and the hub the same name.

Re: Cannot change name of Data Connection

Anil_Babu_Samineni — Mon, 30 Dec 2019 09:22:51 GMT

Could you please check other RIM nodes as well the same way

Re: Cannot change name of Data Connection

cjgorrin — Fri, 22 Mar 2024 11:14:22 GMT

We had experienced this issue for ages, never knowing why it happened. We inspected the traffic and it could not be a proxy cache because the information about data connections in the Data Load Editor are passed via Websocket.

After trying many things, we finally managed to reproduce the issue. It is due to having two data load editors open at the same time in different tabs and then changing the name in the QMC. The issue has been reported to Qlik with support ticket 00147307.