Can not move data connections to data space

[Thomas23]

Hi,

I've created a new data connection to a Microsoft SQL Server via data gateway in QLik Cloud.
In the dropdown list where I can select the space where I want to create the connection doesn't show me the data spaces we have. I can see my personal space, all shared spaces and all managed spaces, but there are no data spaces.

When I create a new data connection in one these spaces I can move it from a shared space to another shared space and also to managed spaces.

But I can't move it to a Data Space. I get the error message:
"The data connections move could not be completed. Check if you and the data connection owner have edit privileges on the spaces related to the move action. The move was denied for the following data connections:"

We set up data connections a few weeks ago, and it was possible then.

I am the owner of the data connection and the data space. I have all admin roles also.

Was there an updated that causes this behaviour?
Or is it a bug?

Thank you and many regards
Thomas

[marksouzacosta]

Hi @Thomas23,

I don't think you can create Analytics Data Connections inside Data Spaces.
Those Data Spaces are reserved to store files (datasets in general) and Data Integration Projects/Connections. If you have a Data Integration Connection, you can move it from one Data Space to another - but not to Shared/Managed Spaces.

Regards,

Mark Costa

[kevin456london]

---

@Thomas23 myaarpmedicare wrote:

Hi,

I've created a new data connection to a Microsoft SQL Server via data gateway in QLik Cloud.
In the dropdown list where I can select the space where I want to create the connection doesn't show me the data spaces we have. I can see my personal space, all shared spaces and all managed spaces, but there are no data spaces.

When I create a new data connection in one these spaces I can move it from a shared space to another shared space and also to managed spaces.

But I can't move it to a Data Space. I get the error message:
"The data connections move could not be completed. Check if you and the data connection owner have edit privileges on the spaces related to the move action. The move was denied for the following data connections:"

We set up data connections a few weeks ago, and it was possible then.

I am the owner of the data connection and the data space. I have all admin roles also.

Was there an updated that causes this behaviour?
Or is it a bug?

Thank you and many regards
Thomas

---

Hello @Thomas23,
Yes — this behavior aligns with recent changes in Qlik Cloud. As of the October 2025 update, stricter permission checks were introduced for moving data connections into Data Spaces. Even with admin roles, both the connection owner and the target space must have explicit edit rights. If everything looks correct on your end, it may be a bug or a backend sync issue. Best to log it with Qlik support for confirmation.

Best Regards,
Kevin London

[lmcsedyz]

Identical issue here, we have a lot of tenants and everywhere we have have connections moved from personal to data space. But today, new tenant, even if you are tenant admin, with all rights and have all rights for space and even you are space owner, it does not work, can not move connections anymore. Reported as an issue with level 2 severity 2 hours ago. No info yet.

In our case - we are dead - we can not work anymore... entire release process, updates, backups is dead. When you have common data on AWS S3 and global configs with same connection rules for each tenant...

[Thomas23]

This is what the Qlik bot returned:

"Thank you for reaching out about the issue with the data spaces not appearing in the dropdown list when creating a new data connection in Qlik Cloud. It seems that this is a known situation where only personal, shared, and managed spaces are visible, but not data spaces. This is because data spaces are part of the Qlik Talend Data Integration offering and are not meant for storing Qlik Cloud Analytics data. For Qlik Cloud Analytics, datasets should be stored in managed and shared spaces. If you have been using data spaces previously, it is recommended to plan a migration of your datasets and connections to managed or shared spaces...

...The behavior you're experiencing, where data spaces are not visible in the dropdown list for creating a new data connection, is not due to a recent update or a bug. Instead, it is related to the way Qlik Cloud Analytics is designed to handle data spaces. Data spaces are part of the Qlik Talend Data Integration offering and are not intended for storing Qlik Cloud Analytics data. Therefore, they do not appear in the dropdown list for creating connections...

...It seems that the ability to use data spaces for data connections might have been part of a temporary workaround that Qlik allowed for analytics customers. However, this workaround is subject to change, and Qlik has advised analytics-only customers to plan for migrating their datasets and connections to managed or shared spaces. This is not a bug but rather a design decision related to how Qlik Cloud Analytics handles data spaces. "

[lmcsedyz]

This is an epic fail. We’ve been using Qlik long before any Talend acquisition, and data spaces have always been used for data sources — data and data connections.

Changing such a fundamental behavior without any communication to clients or partners is unbelievably arrogant and has no place in this century.

Qlik has all the capabilities to analyze how features are being used by customers and to plan changes — and communication — accordingly.

This is simply unacceptable.

[Daniele_Purrone]

To everyone that is experiencing the issue, I am investigating this with the dev team.
I'm gathering some data about this: if you are affected, can you please answer these questions?

1. Does your Qlik Subscription include both Analytics and Integrations?
2. Is it Analytics connections that you are trying to move, or is it Integrations ones?
3. if it's Analytics, are they used in conjunction with some integration pipelines?

[Daniele_Purrone]

Hi @lmcsedyz 
I understand your frustration, but I would like to point out that it's been clarified since a long way back that data spaces are meant for Integrations-use only.
Please check the disclaimers here: https://community.qlik.com/t5/Official-Support-Articles/Not-able-to-create-data-spaces-with-Qlik-Clo... (this article replaced a previous one from early 2024 that mentioned the same thing).

However, I'm trying to determine if this was just an oversight in the communication, and if it's something that can be reverted while we wait for a reassessment. I agree that this should have been communicated.

I would still point, however, that the disclaimers from the article I linked still stand:

IMPORTANT

• The decision to allow this workaround might be reverted at any time, preceded by a timely communication.
• Analytics-only customers who never made use of data spaces should refrain from starting now.
• Analytics-only customers who are already working with data spaces should consider planning to move away from them, migrating their datasets and connections and should not start implementing new workflows involving data spaces.
• Additional Qlik Talend Data Integration-only features, like the possibility to work with pipelines or the Qlik Data Movement Gateway, are not available to Analytics-only customers.

[lmcsedyz]

I’m not aware of any workaround — creating a connection in a personal space and testing it before moving it to a “production” destination is a perfectly normal workflow.

Posting an article on a community page is hardly a professional way to communicate with customers or OEM partners. You might as well pin it on a bulletin board in the basement, in the tiger cage, and claim the information was publicly accessible.

Yes, this kind of change should be communicated through proper and more appropriate channels. When your administration is fully automated, such a change can cause serious issues.

Furthermore, Qlik’s behavior in this case is misleading — instead of a clear message announcing that the functionality is no longer supported, users just get an error about insufficient rights.

[lmcsedyz]

1) Yes

2) both - AWS S3 acts the same like integrations (even if it was created as analytics), Google drive as analytics only - but id does not make sense to me to have main sources (connections) on different spaces

3) we do not use integration pipelines (there are no benefits for us in our scenario)