Current behavior makes some sense if you want to allow self-service creation of new connections, but still need to distinguish between user-made data connections, and the governed ones.
we are looking at it in a slightly different way within our Qlik Sense Enterprise on Cloud Services & Qlik Sense Enterprise on Kubernetes deployment options. First of all, Data Connections are no longer created via the MC within those deployment types. You can create them via the App as you already do it today. But what we are about to add here is the ability to create / manage Data Files & Data Connections right out of the Hub. And here it is important to have a look into our new concept which is Working in spaces as part of the Qlik Sense Hub. As part of those Spaces and especially as part of Shared Spaces, you are able to store connections in Spaces and share them across your deployment. The main goal here is to deliver a more governed and maintainable way of managing Data Connections across the whole platform.
We recently delivered a new capability as part of our QSEoCS offering. As part of our SaaS offering (QSEoK to follow with that capability in May) we are now allowing you to create & manage data connections as part of the Hub and you can do the same with Data Files. This is currently available as part of Shared Spaces within your QSEoCS Tenant and allows you do manage all of it outside of your Apps but then using those Data Files & Connections across your environment (Relative Path and Fixed Path is supported)
On the screenshot below, you can see how the UI looks like as part of your Hub experience. A similar functionality is currently not planned for the QSEoW composition.
Please let me know if you want to talk more in detail about the possibilities and supported use cases.
@Thomas_Hopp it is good to see the feedback on cloud, but really disappointing to hear that the features being asked for are not planned for QSEoW.
Stopping the "inane" behaviour of tagging data connections with user names must be so easy to implement ?
And although there is another idea thread for QMC data connection creation, it was mentioned again above by someone else.
In my opinion the QSEoW product ( the main one we and our customers use ) is crying out for some investment in the app management space. No pun intended !
There must literally be one line of code that constructs the data connection name in the QMC app out of the user-provided value and their id, e.g. "Oracle JDE (Andrew)". Drop the id from the save ? Yes maybe there are two API calls under the covers ? It really must be that simple to implement ? So much angst would be solved for QSEoW users who do not have the benefits of shared spaces on SaaS.
