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:
I was recently told that our PM team was working with the QVSource team, but I do not have any information on how that conversation went. I do know that variable support for the connections is on the roadmap, but there isn't a time frame on it yet.
Currently - using Legacy mode is the work-around for this.
We have not heard anything from your PM team, could you let us know where this info came from or who we should expect to be speaking with?
I'll have the account manager QVSource contact you. I recall in an email one of our team members stating they were having a call with QVSource, I could have been mistaken.
Thanks - we have not heard from anybody yet but welcome speaking further.
In addition to that, as we know for sure that there are a lot of people which this will affect (and who are already asking us about this) could we get a response from Qlik on this thread as to the reasoning and benefits behind this change for end users with regards loading from http?
As noted earlier, the docs state:
For security reasons, Qlik Sense in standard mode does not support absolute or relative paths in the data load script or functions and variables that expose the file system.
However, since absolute and relative paths were supported in QlikView, it is possible to disable standard mode and use legacy mode in order to reuse QlikView load scripts.
Which I can understand with regards loading from the file system but what is the thinking behind locking this down by default for loads from http end points?
"Legacy mode" also sounds like something which could be discontinued in the future which is another point of concern. Can we rely on this being available in the long term?
Hi Chris - I just wanted to clarify a few things. I was just thinking about this and 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.
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.
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.
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.
That being said - if you can address any specific concerns that can help prioritize this further.
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.
The limitation of the LIB function with http end points is not a design decision its just a limitation at the moment and is on the roadmap to include extra support for LIB/http connections including variable support. Legacy mode will remain in the product to cater for these limitations and to overlap with people wishing to migrate QlikView scripts into Sense in a staged way
hope this clarifies