Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Is there a way to create and edit data connections directly instead of doing it from with the data load editor?
What I need to do is create some standard data connections for all applications to use and remove all the developer-created connections that have userids in the name. Also we need to troublshoot the connections sometimes and typically it is necessary to recreate them because they are not easily edited from the QMC to test.
It seems this approach is not the standard workflow for Qlik, so please point me to any resources that would explain why I am thinking about this wrong...what I want to do is lock down our servers so that developers are not able to create their own data connections and then I will manage the data connections centrally. It is a mess on the server when you have hundreds of poorly-named, ambiguous data connections which then get incorporated into various apps depending on who found what connection when and used it by trial and error. Further confusion results when some people use ODBC vs OLEDB or native Azure...When we promote the apps into production environment, we end up having to re-write developer code or recreate these connections for them.
Hi,
Below link to get start with your requirment
There's probably a way to create data connections via API, but what we do is create it normally through the data editor, then use QMC to change the name to a standardized name (without the developer name, for example). This is the Data Connections section of the QMC. Unfortunately, this won't help you clean up whatever mess already exists...
Locking down the ability to create additional new connections would be handled through security rules, as per the linked section in a previous response.
thanks...but that doesn't talk about editing the data connections
What I don't understand is why Qlik makes this so difficult. Creating a data connection is a task for a server admin, not a developer. On a production server, no one should be opening development tools like the data load editor. It seems odd to have the admin have to make their own app just so they can get to the screen where they can create a connection...then pop over to the qmc to rename it.
I am not in any way affiliated with Qlik (I'm just a customer), but I assume this is intended to facilitate self-service by allowing users to create connections to their own data rather than having to contact an administrator to get data from a source. I can't say I'm in love with the ensuing mess, but to be fair, it is reasonably manageable at least from the developer side by setting up standardized connections (ones with no username) and instructing all developers to use these and only these.
You can manage connections programmatically using the QRS API. For example
You can also do the same using the Engine API.
You can use the Qlik Sense Data Connections Analyzer app to analyze what connections are currently in use and what is not.
-Rob
http://masterssummit.com
http://qlikviewcookbook.com
http://www.easyqlik.com