8 posts tagged qlikview, newest first.
When relying on various Node.js services (e.g. Butler SOS, Butler, App Duplicator etc), you quickly run into the challenge to ensure all services are always up and running. A failing service might be fine, as long as it is quickly restarted in a predictable way. A concrete example
With so much cool data available online, tools like QlikView and Sense becomes real Swiss Army knives of data integration. Pull in some data from company internal databases, some data from previously created QVDs, and more and more commonly also from various online sources, both public and private. Depending on
Quick update to the previous post on this topic. There is a new version of slack_proxy available on GitHub. It adds a new endpoint for creating directories on the server where slack_proxy is running. This obviously means that the apps name – “slack_proxy” – is not really that relevant
Real data and test data – both are needed One of the great things about both QlikView (QV) and Qlik Sense is their integrations with other systems. Given the native connectivity to any ODBC source, web pages in general, Salesforce, REST APIs, BigQuery etc – combined with the dozens of connectors provided
I finally got around to start using GitHub Gists a bit more systematically for storing useful bits of code. Going forward I will post useful, reusable pieces of Qlik Sense and QlikView code there. My own experience tells me there is tons of time to be saved by reusing existing
Slack has only been around since August 2013, but I would definitively say it’s one of the better team communication services out there. The web client is great, and the OSX and IOS clients are truly awesome. It integrates with tons of other services, including Dropbox, GitHub, IFTTT, Jira,
Update: Turns out it is the “Update for Windows Server 2012 (KB3013767)” that when installed on the server in question prevents the QlikView Directory Service to start. Installing the other two updates mentioned below (KB3004365 and KB3029449) does not affect QV operation. While doing regular maintenance of a QlikView server
I am not a Javascript fan. To be honest, I find it rather abusive. There are probably lots of theoretically sound reasons for designing the Javascript (=JS) syntax the way it is – but that does not make it more readable or easy to learn. I am however a QlikView (=QV)