Discussion board where members can learn more about Qlik Sense Data Connectivity.
For load a web file in Qlik Sense is mandatory to define the connection with the specific link?
I need to load a web file that the source is made by variables like that:
Thanks for your message - have tried to address all your points below:
...wanted you to make sure you understand that Qlik Sense is NOT a replacement for QlikView. QlikView will continue to be improved upon as well going into next year, so QVSource will continue to work with QlikView new releases.
Yes - we fully understand this and we are keen to work with both products and preferably with a single version of QVSource.
Qlik Sense specifically addresses the need for self-service data visualization first with the added capabilities to create mash-ups using its extensive APIs for both connectivity, visualizations, integration and automation.
Agreed, and I feel these are the types of scenarios where users will want to load interesting data from external web APIs which is where QVSource adds a lot of support and value.
Are there specific use cases pertaining to self-service data visualization where you are using or plan to use QVSource data sources with Qlik Sense over using QlikView?
This really comes down to our (and Qlik's) customers and how they wish to use QlikView and Qlik Sense. We want to continue to make it easy for both sets of users to access the growing list of APIs we support.
We are already in conversations prospects making purchase decisions on Qlik Sense and we are keen to be able to give them a clear message about the interoperability with QVSource. Saying we are only able to run in Legacy mode is not reassuring unfortunately.
Did you / your customers think you needed to migrate or move over QlikView Apps to Qlik Sense (which is not the case)
No - we didn't think this.
Now, Qlik Sense uses newer API technology and protocols and is being improved upon with each release to add new capabilities. From my understanding, QVSource had developed connectors to originally work with QlikView utilizing the http endpoints and APIs. My assumption is that QVSource will look into the new Qlik Sense connector APIs and start to develop Qlik Sense specific connectors gradually. "Legacy mode" will support QlikView 11 connectors, and will not go away until we know that we have addressed prioritized issues.
We are not currently planning to change the way QVSource works - our user base appears to be currently very satisfied with the usability, flexibility and performance. If there is a compelling reason to change and.or our users/partners show an interest in us changing then we will of course look into it.
I have been informed that that variable support for the LIB connectivity is on the list, however it is not at the top of the list.
This is good to hear (well, not that it's not top of the list ).
That being said - if you can address any specific concerns that can help prioritize this further.
I think I have done this now - specifically something like my post Oct 15, 2014 8:55 AM is what I currently feel we would like to see possible.
I have contacted the Product Manager and your QVSource account rep to inform of them of your needs and I intend for them to contact you.
This is much appreciated and I believe we now have a call scheduled.
Thanks again Mike.
It's not a replacement, but some customers like the natural UI/analytics and are serious thinking about using Sense for some replacement dashboards. I would not like to see another specific version of QVSource for Sense. Sense makes it possible to import existing QVW's (script 99% Compatible). So it would be nice that Qlik could solve the problem regarding the LIB Connections (Variables), i think it really needs your serious attention (priority) for the future (for now we can enable the legacy support).
Would also just like to keep the interest up on this thread as we just saw this create a problem for another user, this time bought to our attention on the Qlik Community:
Re: Unable to load data from QVSource MongoDBConnector to Qlik Sense
Again, the docs suggest:
Disabling standard mode can create a security risk by exposing the file system.
But the user is not trying to access the file system but a http URL.
It seems to me that calling the mode 'Legacy' mode is slightly off-putting, and then placing warnings about its use is likely to really worry users. I have a number of users who use QVSource, and they will be put off migrating to Sense if they are unable to use the product in a way that feels 'correct'.
I like the lib:\\ functionality, particularly when it is set up to a folder with a bunch of files in, as it simplifies things for the users. It seems counter-productive to go backwards on things though and not allow previously perfectly legitimate code.
With the move with QlikView across to the Sense engine, I presume this is not going to make these statements start to fail when people upgrade their QlikView servers?
Just to clarify all of the QlikView scripts you may have which use QVSource will continue to work with the common QIX layer in the future.
The restriction around passing variables into a http connection in the LIB function is on the priority list to be enhanced in future Sense versions (no ETA yet)
I am trying to connect to salesforce in Qliksense . I know that to use Custom Connect, we need to enable Legacy Mode in Qlik Sense Desktop. However, when I open settings.ini in a notepad it is empty.
How do I change StandardReload=1 to StandardReload=0?
Hi Chandni, there is actually a Salesforce Connector for Qlik Sense now - it is available here:
Let us know how you do.