QVSource 1.6.0 Now Available

We have just released version 1.6.0 of QVSource - The QlikView & Qlik Sense API Connector.

This blog posts outlines the main changes. As always, we would also recommend you read the notes on the "Change Log" tab of any connectors you are using for a comprehensive overview of changes.

New Connectors

  • We have a new connector to JIRA (hosted or locally run). Currently there are only a couple of tables, one to retrieve all issues and another to make and custom REST API request but we will add to this in the next release - please let us know what features/data you need so we can make sure you are covered.

Updated Connectors

  • IMPORTANT/BREAKING CHANGE: We have removed the MyAccounts and Messages tables (as we do not believe they are being used and would now require us getting approval from Facebook to continue using) as well as the FriendsWhoUseThisApp table which we also believe is not useful from the Facebook Fan Pages Connector.
  • V3 of the Facebook Insights Connector has been added (and V2 removed). All requests to FacebookInsightsConnectorV2 will now be automatically routed to FacebookInsightsConnectorV3 (although we would still recommend making the same change in all your load scripts to avoid confusion). BREAKING CHANGE: Unfortunately, Facebook have now changed their Insights API and application insights are no longer available in this version of the connector although we hope to resolve this soon.
  • We have a new V2 of the Salesforce Connector. This replicates the functionality of the previous version and also has additional Insert and Update tables which allow you to write data back to Salesforce from your QlikView or Qlik Sense load scripts.
  • The MongoDB Connector now scans all items in the MongoDB Collection in order to establish all possible columns before generating the table for QlikView/Qlik Sense.
  • A new TableSchema table has been added to the Google BigQuery Connector.
  • The SugarCRM Connector has new max results and order by inputs which makes it much easier to get just the data you need. We hope to add a filter input to this connector also soon.
  • The Klout Connector now makes all API calls over HTTPS instead of HTTP.
  • The Adobe Analytics (Omniture) Connector has a fix in to avoid having duplicate column names in the result tables.

Deprecated Connectors

The following connectors have been deprecated and will likely be removed from the product in a future version.

  • The DFA Connector (which was still in beta) has been deprecated as it uses an API which Google are now removing later in the year. Please contact us if you would like us to consider redeveloping this connector to use the latest DFA API.

Download Latest

Where do I find this new release? If you are a QVSource customer or have requested a trial in the past you should see this new release in the personalised download link we should have sent you via email.

If you are new to QVSource you can download a fully functional free trial from our website.

3 Videos that are Worth Watching

We wanted to draw your attention to some QVSource video demonstrations that have been independently recorded and posted to YouTube by social media expert, Fahran Qureshi.

Fahran, who takes an avid interest in web analytics, has put together 3 video tutorials with the overarching theme of getting a deeper insight into – and a better understanding of - your Twitter feed, using the QlikView and QVSource business intelligence tools in tandem.

(Note that the application showed in these posts can be downloaded from the QVSource GitHub Page).

  1. In the first 10-minute tutorial, “How to gain insight from Twitter using QlikView”, Fahran demonstrates how to use QlikView to understand the conversations taking place on Twitter, based on any criteria that you choose. In the demo, the tool he uses to carry out the Twitter analysis is our very own QVSource Twitter Connector, showing how to use it and how to set it up.
    • - Read the 1st tutorial blog here.
    • - Watch the tutorial here.
  2. In Part 2, entitled “How to use QlikView to analyse Twitter conversations”, Fahran again uses the QVSource Twitter Connector to analyse the conversation on Twitter, cutting through the noise on Twitter to uncover the valuable conversations taking place, and showing how to customise the QVSource Connector to select Twitter accounts, hashtags and other Twitter search parameters.
    • - Read the 2nd tutorial blog here.
    • - Watch the tutorial here.
  3. Part 3 is called “Gain even more insight into Twitter conversations using QlikView and QVSource”. In this final session, Fahran shows how QVSource takes the whole process of gathering business intelligence on your organisation’s Twitter performance to the next level. In this video, Fahran compares the Twitter feeds of two competing companies, changing the parameters in real-time, to demonstrate the agility and flexibility of the QVSource Connector. Fahran is able to instantaneously compare the number of tweets and retweets, and who fares better in response times, sentiment analysis, and audience growth.
    • - Read the 3rd tutorial blog here.
    • - Watch the tutorial here.

It’s really heartening to receive such a positive independent review of our technology, from a completely impartial blogger. We'd like to thank Fahran for taking the time to record the videos, and share his thoughts on one of our connectors. We found his insight really valuable, and we are sure you will too. We have over 30 connectors in our portfolio, all designed to improve web analytics (Fahran’s specialist subject!) so maybe we’ll see him again sometime!

Creating A QlikView Twitter Tracker Application In 30 Minutes

We just set up a Twitter tracker application (link at end) for the upcoming Qlik Qonnections Global Partner Summit in Orlando (which by the way we will be attending and sponsoring!) and I thought I would remind users how easy it is to do this using QlikView and QVSource.

Assuming you already are a QlikView user and have QlikView desktop up and running, the next thing of course is to make sure you also have QVSource. If not, you can grab a free fully functional trial here and find instructions on getting up and running here.

(Setting up QVSource is really easy - the application is delivered simply as a zipped folder, no installer, no components to register. Typically you will simply need to unzip the QVSource folder to somewhere on your local disk and double click the QVSource.exe then simply install your licence file.)

The next step is to make sure you are authenticated with the Twitter Connecotor - to do this first locate and double click the Twitter Connector in the list of Connectors:

Then on the Connector's config screen - click on the 'Authenticate' button:

You will then be redirected to Twitter's authentication screen where you can enter your account name and password. After completing this you should find a token has appeared next to the 'Authenticate' button.

If you like you can do a quick test here - enter a search term and click the 'Run Table / Generate Script' button and you should see matching Tweets returned:

This is all we need to do in QVSource now - we just need to make sure that it is left running in the background:

Wherever the QlikView reload is taking place.

Next we go to our GitHub site, specifically the QVSource-Twitter-Starter-App-For-QlikView and click the 'Download ZIP' button:

Unzip this file somewhere on your local machine, you should see something like this: 

For this post, we are only interested in config.txt and Twitter-Starter-App-Load-Script-And-Data-Model.qvw. Below are some notes on these and some of the other files and folders:

  • config.txt is simply a QlikView load script fragment referenced by the main QVW file. Having your config data here (such as search terms, timezone, sentiment API configuration etc.) means that you can often simply overwrite the QVW file with updated versions and continue your reloads without interruption (as long as the data model has not been updated between versions).
  • Twitter-Starter-App-Load-Script-And-Data-Model.qvw reads the contents of config.txt (which tells it, amongst other things, which Twitter search terms to monitor) and creates a set of QVD files containing all the data for the application. It is designed to be reloaded regularly (e.g. every 5 minutes) and only query Twitter for the newest results since the last reload.
  • Twitter-Starter-App-Load-Script-And-Data-Model-Alternative-UI.qvw is an alternative front end to the same set of QVDs. Once you have run Twitter-Starter-App-Load-Script-And-Data-Model.qvw.qvw once and generated the first set of QVDs you should be able to simply hit reload on this application to see a different view of the data.
  • The two sub folders contain the files which make up the two QVW applications and represent one way QlikView can be used with a source control system. If you were to open the QVW files and save them to an alternative location then these files would all be combined into the newly saved QVW application.

Open config.txt in your favourite text editor. We will now discuss the few minor changes we will make to get the application ready to reload.

First, locate the following section:

let vLocalTimeZone = 'UTC+01:00';
let vLocalReloadTime = date(ConvertToLocalTime(gmt(), '$(vLocalTimeZone)'), 'DD/MM/YYYY hh:mm');


From this site we can see that since the 9th March the timezone in Orlando is UTC - 4 hours so let's update our config file accordingly: 

let vLocalTimeZone = 'UTC-04:00';
let vLocalReloadTime = date(ConvertToLocalTime(gmt(), '$(vLocalTimeZone)'), 'DD/MM/YYYY hh:mm');

 
Next, find this section:

//
// A folder which QlikView has write access to and QVSource has read access 
// to. See http://www.qvsource.com/wiki/Synchronous-Asynchronous-And-Batch-Requests-Explained.ashx 
// for more info.
//
let vWorkingFolder = 'c:\QVSource\Temp\';


For certain operations, QVSource needs a folder where it can read and write temporary files. We generally recommend running QVSource from the folder c:\QVSource and having the above Temp subdirectory. However you are set up, you should make sure that the above variable points to a folder location which exists and which the QVSource.exe has read/write access to.

Now locate the TwitterSearchTerms inline table. We will edit this to be:

TwitterSearchTerms:
LOAD * INLINE [
Grouping, SearchTerm
Qonnections, Qonnections,
Qlik, from:QlikView,
Qlik, QlikView,
Qlik, Qlik,
QVSource, qvsource
QVSource, from:QVSource ];


The application allows you to configure an arbitrary 'Grouping' field as well as a number of Twitter search terms for each.

As a minimum we want to track the official #Qonnections tag. As Qonnections is such a unique word we have excluded the hashtag so that we pick up any Tweets where the user has simply referred to it without the # too.

We are also interested in picking up some related Tweets so have included a number of other search terms. QlikView, Qlik and QVSource should be self explanatory.

The from:QlikView and from:QVSource search terms are added additionally to pick up any Tweets sent from these two accounts - this is because they might not actually contain any of the other search terms but might still be interesting to our analysis.

You should make sure that the following setting is 0. By default random Klout scores are generated as this greatly speeds up the load time during development and testing of the application.

let vUseRandomKloutScore = 0;


Finally, note the following section:

//
// Configure this table with one or more of the following sentiment APIs:
//
// Repustate
// Sentiment140
// AlchemyAPI
// Random
//
// NOTE:
// - You may need to ensure you have API keys configured in QVSource for the selections you make here with 
// enough quota to be able to score all the content.
// - The QVSource Sentiment Analysis & Text Analytics Connector also connects to other APIs which you can 
// of course also use however you would need to modify the load script accordingly.
//
SentimentEngines:
LOAD * INLINE [
Engine
Sentiment140
];


You can see that the application is, by default, set to use the Sentiment140 API in the QVSource Sentiment Analysis & Text Analytics Connector which supports English and Spanish. You will see from the notes above this section of load script that you may also easily select some of the other APIs the connector supports.

That should be all we need to do - save config.txt and then open the Twitter-Starter-App-Load-Script-And-Data-Model.qvw and hit reload. When we first did this we ended up with the following:


This application has quite a rich data model, not only does each Tweet captured have a great deal of information but we also now have data on the Klout score for each user and a sentiment score for each Tweet. Additionally the application creates fields which indicate whether the Tweet is an original Tweet, a Retweet of a Tweet or a reply to a Tweet as well as extracting entities such as hashtags, links, pictures and stock ticker sumbols into separate tables.

The screen shot below (click to enlarge) shows the most important parts of the data model for this QlikView application:

Looking back at the application, if we select just the 'Qonnections' search term we can see that in fact the application only has 47 Tweets.

(Click to Enlarge)

But you can already see who the top Tweeters are, what the top hash tags are etc.

The reason there are only a small number of Tweets is that the Twitter Search REST API which QVSource uses only allows you to go back up to approx 1500 Tweets or 1 week for a given search term. Here we can see that we have hit the 1 week back limit.

However, we will now deploy this to our QlikView Server and set it up to reload regularly and over the coming weeks we should see all new Tweets accumulate into the QVD files and the application.

You can see this here!

And we look forward to meeting many of our partners in Orlando in a few weeks!

New QVSource Release (1.4.9) Available

We have just pushed out a major new release of QVSource with a large number of updates including four exciting new connectors for QlikView.

If you are currently evaluating QVSource or using it commercially we would definitely recommend you start using this new version (after reading the notes below carefully).

In particular, if you are a commercial user, please see if any of the MailChimp, Klout, Twitter or Facebook related fixes below affect you - if they do you should test your apps with the new version and upgrade.

In addition to the highlighted changes below, please check the change logs on our wiki for any connectors you are using as there have been a number of other minor updates and improvements.

New Connectors

In alphabetical order:

  • We have a new connector to Blue Yonder who provide a service and API for forward demanding prediction and planning. See our sample app which shows how to use this Connector. 
  • We have a new File Transfer Connector which allows you to both download and upload files from FTP and Secure FTP (SFTP) locations into/from QlikView. 
  • We have a new connector to the Google Prediction API which lets you 'train' your own categorization or regression prediction models based on your own training data set. The Prediction API uses patterns it finds in your training data to either find the closest category for the submitted example (if this is a categorical model) or estimate a value for the example (if this is a regression model) and returns the category or value. One potential use of this QlikView connector is to create your own sentiment API (we give an example here) but Google also give a few other examples on their website:
    • Document and Email Classification
    • Recommendation Systems
    • Spam Detection
    • Language Detection
    • Upsell Opportunity Analysis
    • Diagnostics
    • Suspicious Activity Detection
    • Churn Analysis 
  • We have added a new connector to HEIDI (the Higher Education Information Database for Institutions) for QlikView which should be of interest to a number of UK universities and other higher education institutions.

 Connector Updates

  • Version 3 of the Google Analytics Connector for QlikView has been added. This new version has all the features of the previous version, plus new support for real-time data and Multi-Channel Funnel Reporting! The other main change is that we have upgraded it to the new UI and workflow style (as we plan to do to all connectors in due course). The previous version (V2) of this connector should now be considered deprecated and will be removed in March 2014 giving existing users several months to make the (simple) upgrade.
  • Similarly, we have also upgraded the Google AdWords and General Web (JSON/XML/SOAP) Connectors for QlikView to use the new UI and workflow and the previous versions should be considered deprecated.
  • The General Web (JSON/XML/SOAP) Connector now supports:
    • Saving the response to a local file. This has been found useful for example, for downloading image files which can then be loaded into the actual QlikView application for usage offline and also better performance.
    • Loading local files - this is useful for example if you have a file with JSON formatted data and wish to load it into QlikView.
  • We have improved and moved the Google Spreadsheet Connector functionality into the Google Drive Connector for QlikView where we feel it makes more logical sense. The dedicated Google Spreadsheet Connector should now be considered deprecated and will be removed in March 2014 giving existing users several months to make the (simple) upgrade. Note that users who have purchased a commercial licence for the Google Spreadsheet Connector will be automatically transferred over to the Google Drive Connector.
    • We have also added a new DownloadRawFile table to the Google Drive Connector.
  • We have added a number of new tables to the LinkedIn Connector for accessing a person's companies and company statistics. The Skills table has also been renamed MySkills and only returns skills for the authenticated user.
    • Note that we are aware of a number of issues with this connector which appear to be due to changes in the underlying API. We are currently considering working on a new V2 of this Connector.
  • We have fixed a bug in the Facebook Fan Pages Connector for QlikView which caused the has_likes and has_comments columns to be swapped in some cases.
  • Twitter Connector for QlikView
    • BREAKING CHANGE: We have also made a very minor breaking change in the Twitter Connector for QlikView by removing the cursor column from the FollowerIds table. We are investigating a new way to properly support paging through some of the Twitter tables and currently you will see a new 'Post_FollowerIds_Info (Beta)' table and you will find some notes here regarding this (although this still isn't working how we would like).
    • We have also added a new Favorites table to this Connector and fixed an issue with the CustomRequest table.
  • Google DoubleClick For Publishers (DFP) Connector for QlikView
    • This is now out of beta.
    • It will also now wait up to 20 minutes for the report generation to complete and also has a few more progress update messages (when running in the UI) so you can get a better idea of how long each phase of the report request is taking.
    • We have also upgraded it to use the very latest DFP API (201311).
  • We have fixed a bug in the CampaignEmailStats table of the MailChimp Connector (it looks like a minor change in the API response started causing an issue in the connector) and the email address parameter should now be correctly URL encoded.
  • We have fixed a bug with the monthChange column showing true/false instead of numeric value in the Klout Connector and also added a new column for the score bucket.
  • We have upgraded the Google Plus Connector for QlikView to use the new UI layout and also made a couple of improvements to the Connector.
  • The MailBox Connector has been upgraded to use the new UI style and also has new tables to list and download email attachments. 
  • The Repustate option in the Text Analytics & Sentiment Analysis Connector for QlikView now supports Chinese and sentiment by topic.
  • The Google AdSense, Google DFPGoogle CalendarGoogle AdWords, Google DriveGeneral JSON/XML/SOAP and OData Connectors are now out of beta. If you have been using any of these connectors and wish to continue to do so when upgrading QVSource please contact us or your QVSource partner for licensing details.

Removed Connectors

Other Updates

  • You will probably notice we have a new product logo on our website, wiki, blog and other online locations. This is also now used in the product.
  • We have moved most of our demo QlikView applications over to our site on GitHub. Using GitHub makes it much easier to track changes that are made between versions. Note that you do not need to know how to use GitHub - if you want to download an application just look for the 'Download ZIP' button.

NOTE: You can access this latest version from the link you received when signing up for QVSource.

We really hope you are enjoying the updates!

If you like using QVSource, please take 30 seconds to help us by rating us on QlikMarket.

New Nightly Build Of QVSource (1.4.8.2) Available

We have just pushed out a new nightly build of QVSource with a large number of updates including two exciting new connectors for QlikView.

If you are currently evaluating QVSource, we would definitely recommend you start using this new version.

If you are a commercial user, please see if any of the MailChimp, Klout, Twitter or Facebook related fixes below affect you - if they do you should test your apps with the new version and upgrade.

Otherwise, if any of the updates below are interesting or applicable to you we would recommend you start testing your QlikView applications on a test server against the new version.

In addition to the highlighted changes below, please check the change logs on our wiki for any connectors you are using as there have been a number of other minor updates and improvements.

New Connectors

  • We have a brand new connector to the Google Prediction API which we are particularly excited about. This connector lets you 'train' your own categorization or regression prediction models based on your own training data set. The Prediction API uses patterns it finds in your training data to either find the closest category for the submitted example (if this is a categorical model) or estimate a value for the example (if this is a regression model) and returns the category or value. One potential use of this QlikView connector is to create your own sentiment API (we give an example here) but Google also give a few other examples on their website:
    • Document and Email Classification
    • Recommendation Systems
    • Spam Detection
    • Language Detection
    • Upsell Opportunity Analysis
    • Diagnostics
    • Suspicious Activity Detection
    • Churn Analysis
  • We have added a new connector to HEIDI (the Higher Education Information Database for Institutions) for QlikView which should be of interest to a number of UK universities and other higher education institutions.

 Connector Updates

  • Version 3 of the Google Analytics Connector for QlikView has been added. This new version has all the features of the previous version, plus new support for real-time data and Mult-Channel Funnel Reporting!. The other main change is that we have upgraded it to the new UI and workflow style (as we plan to do to all connectors in due course). The previous version (V2) of this connector should now be considered deprecated and will be removed in March 2014 giving existing users 6 months to make the (simple) upgrade.
  • Similarly, we have also upgraded the Google AdWords and General Web (JSON/XML/SOAP) Connectors for QlikView to use the new UI and workflow and the previous versions should be considered deprecated.
    • The new General Web (JSON/XML/SOAP) Connector now supports saving the response to a local file. This has been found useful for example, for downloading image files which can then be loaded into the actual QlikView application for usage offline and also better performance.
  • We have improved and moved the Google Spreadsheet Connector functionality into the Google Drive Connector for QlikView where we feel it makes more logical sense. The dedicated Google Spreadsheet Connector should now be considered deprecated and will be removed in March 2014 giving existing users 6 months to make the (simple) upgrade. Note that users who have purchased a commercial licence for the Google Spreadsheet Connector will be automatically transferred over to the Google Drive Connector.
  • We have added a number of new tables to the LinkedIn Connector for accessing a person's companies and company statistics.
  • We have fixed a bug in the Facebook Fan Pages Connector for QlikView which caused the has_likes and has_comments columns to be swapped in some cases.
  • BREAKING CHANGE: We have made a very minor breaking change in the Twitter Connector for QlikView by removing the cursor column from the FollowerIds table. We are investigating a new way to properly support paging through some of the Twitter tables and currently you will see a new 'Post_FollowerIds_Info (Beta)' table and you will find some notes here regarding this (although this still isn't working how we would like).
  • The Google DoubleClick For Publishers (DFP) Connector for QlikView will now wait up to 20 minutes for the report generation to complete and also has a few more progress update messages (when running in the UI) so you can get a better idea of how long each phase of the report request is taking.
  • We have fixed a bug in the CampaignEmailStats table of the MailChimp Connector (it looks like a minor change in the API response started causing an issue in the connector) and the email address parameter should now be correctly URL encoded.
  • We have fixed a bug with the monthChange column showing true/false instead of numeric value in the Klout Connector and also added a new column for the score bucket.
  • We have upgraded the Google Plus Connector for QlikView to use the new UI layout and also made a couple of improvements to the Connector.

Removed Connectors

NOTE: You can access this latest version from the link you received when signing up for QVSource. We really hope you are enjoying the updates and are particularly interested in talking to any users working with the new Google Prediction Connector so we can make sure it's working well for you.

If you like using QVSource, please take 30 seconds to help us by rating us on QlikMarket.

New Release Of QVSource (1.4.5) The QlikView API Connector Now Available

We have a new release of QVSource (The QlikView API Connector) available with a lot of small updates, improvements and fixes across a broad range of connectors.

If you are currently using QVSource commercially or evaluating it please read the following, particularly for any connectors you are using, as you will probably want to update your installation.

  • Facebook InsightsWe fixed a major issue with this which was affecting some users when the name of a subvalue field returned from the Facebook API was an empty "" string resulting in an XmlNodeConverter error in QVSource. We have also improved some of the UI labels and messages that are shown in the case where an error does occur.
  • Text Analytics Connector (V2)
    • Fixed an issue which caused this to crash the first time it was shown.
    • Fixed bug with batch sentiment analysis in connection to Repustate.
    • Fixed bug where Sentiment140 language parameter was being ignored.
    • The Random sentiment generator now always returns scores with a decimal point (e.g. 1.5 instead of 1,5) as in countries which use a comma as a decimal this was breaking compatibility with our demo applications.
  • Twitter Connector
    • New TweetLookup table added.
    • New favorite_count column now available for Tweets.
    • New symbols columns added which pulls out a CSV list of any stock symbols in the Tweet (e.g. $QLIK).
    • UserTimeline now returns up to 3200 Tweets.
    • HomeTimeline now returns up to 800 Tweets.
    • The behaviour of the maxCacheAgeInHours parameter has changed - now -1 means cache indefinitely. Set to 0 to not use the cache at all. This is used on the UserLookup and TweetLookup tables.
    • We have fixed an issue with the Grouping column in the template demo application for Twitter.
  • Facebook Fan Page Connector (INCLUDING BREAKING CHANGES)
    • BREAKING CHANGE: Facebook have changed their API which means the comments_count on the FeedItems table is no longer available (we now return 'DEPRECATED - Please use CommentCountForItem Table.' for this column). You can either use the new CommentCountForItem table (see below) or the new has_comments column which has been added to this table.
    • BREAKING CHANGE: The feeditem_id column from the CommentsForItem table has been removed. This is because this table also now works for Comments on Comments and therefore the feeditem_id would actually be a comment id. As this is passed in anyway as a parameter to the table it is not needed here.
    • New CommentCountForItem table added which can be used for any feed item or top level comment id (as comments now also allow replies which are effectively comments on comments).
    • New CommentsAndRepliesForItem table added which lists comments and comment replies in chronological order (including details on the parent comment where applicable).
    • We have added a new Person table. The existing User table can be used with the ID of a person, fan page or any Facebook object and it will attempt to extract as much information as possible. The new Person table can only be used with the object ID of a person and it specifically requests only data which applies to a person, including some data not available in the User table.
    • When requesting things like feed items and comments, the connector now requests data in batches of 100 items instead of 250 which has resolved some bugs certain users were experiencing with the FeedItems table for specific Facebook Fan Pages.
    • Added end_date to Events table.
    • The template demo application has been updated to accommodate the breaking issues above and also now uses V2 of the Text Analyser Connector
  • Google Analytics Connector
    • Fixed issue where Accounts, WebProperties, WebProfiles, Goals and Segments tables would only show up to 1000 rows.
    • Fixed issue with progress bar for Data table.
  • General Web Connector - We have added a feature which converts any JSON element names beginning with a number (e.g. 2013-01-01) to have an N_ prefix (e.g. N_2013-01-01). Previously these elements were causing an error on translating them to XML (which QVSource uses internally). With this fix we have had users able to connect to new APIs including appFigures and App Annie.
  • YouTube Connector
    • Version 1 of this Connector has now been marked as 'Deprecated' and will be removed from QVSource in the near future. Please upgrade to V2 of this Connector. The updates below apply to V2 not V1.
    • Fixed issue with Insights data for Video not working.
    • Improved error messages when Insights data not found or invalid date inputs are made for Insights.
    • Now embeds encrypted refresh token in script when this option is selected.
    • Removed MostViewed table. This has been deprecated by the API and is the same as MostPopular.
  • Klout Connector
    • The Random data generator option for this (used for development purposes to avoid hitting the API) now always returns numbers with a decimal point (e.g. 1.5 instead of 1,5) as in countries which use a comma as a decimal this was breaking compatibility with our demo applications.
  • Google Plus Connector - We have fixed a bug where a change in the API was causing endless looping on some of the tables.
  • Notifier Connector - This contains a new CC input to include email addresses to be copied to.
  • Google Drive Connector - Oops - we accidentally removed this recently from the build by accident. It's back!
  • Removed Connectors
    • We have removed V1 of the Google Analytics and Google Spreadsheets Connectors as these now have V2 versions which should be used in preference. We have run both versions in parallel for a long time and it is time now to sunset the previous versions.
    • We have removed the following connectors - as far as we are aware these are not being used and we want to focus our efforts on connectors which are more popular. Please note, if you are using these and feel we have made a mistake do get in touch and let us know.
      • Viadeo
      • InfoChimps
      • Factual
      • World Bank
      • Omniture (note: We have heard of users using a built in Omniture feature to export report data to an FTP location and access this natively from QlikView so it is not clear that a connector to the API is necassary).

If you are a customer or trialling QVSource and would like to get these enhancements as well as some other general bug fixes and performance improvements, simply go to the download link that you would have received in your QVSource download email.

Or, if you've never tried QVSource and would like to, then you can get a free trial by completing this form.

If you like what we do with QVSource then we'd really appreciate it if you could take a few moments to either rate us on QlikMarket or recommend us on our LinkedIn page. If you've already done this, then thank you!

Don't forget you can always keep up to date with what we're doing by following us on TwitterFacebook and Google+.

Major New Official QVSource Release (1.4.2) Now Available for QlikView

We just published our latest official QVSource release (1.4.2) and it was a big one - in addition to the usual updates and improvements to the connectors we have also added a number of stability, performance and logging enhancements which should be of interest to enterprise users of QlikView.

If you are currently evaluating QVSource and especially if you are a commercial user we would strongly recommend you read this post as it almost certainly contains information which will affect you.

Much of this information was also discussed in our recent blog posts here, here, here and here, but there are also some new updates specific to this latest build.

Last Beta Version Of Certain Connectors

We are planning to take the following Connectors out of beta in the next official build of QVSource (probably in about 6 - 8 weeks time). This is particularly important to commercial users of QVSource who might currently be using these as when they are taken out of beta you will need a commercial licence to continue to use them:

Deprecated Connectors

This will be the last official build of QVSource which contains V1 of the Google Spreadsheet and Google Analytics connectors. Both of these have now been superseded by much improved 'V2' versions which we would recommend you migrate to.

Synchronous, Asynchronous and Batch Request Modes Added

This is a significant new capability in QVSource which was explained in detail in the previous blog post and so will not be covered again here. This update has the potential to give major performance improvements and also change and improve the way QVSource related QlikView script is constructed.

One thing to note is that we have now removed the previous mechanism for running asynchronous requests as the new functionality improves and supersedes this.

QVSource Windows Service

QVSource now has a dedicated Windows Service available and documented here. We have always had a well documented and stable way of configuring QVSource to run on a server environment however the new Windows Service represents an improvement over this technique and in time will likely become the recommended and only supported method.

Related to this, we have also now made it so if QVSource is running in server mode you can run QVSource desktop in order to manage connector and other settings without having to then restart the QVSource server instance for changes to be picked up.

First Version Of New Twitter Connector (V2)

This build has the first version of the new Twitter Connector V2 in which also illustrates the new UI style we are working towards as discussed here. Unfortunately Twitter will start shutting down version 1.0 of their API in early march so all users should start upgrading to this new version ASAP.

First Version of New Sentiment Analysis and Text Analytics Connector (V2)

This build has the first version of the new Sentiment Analysis and Text Analytics Connector in. This also illustrates the new UI style we are working towards as discussed here. We would also recommend users start working with this new version and reporting any issues as it will soon replace V1 of this Connector.

Checking the Status of QVSource

It has always been possible to browse to http://localhost:5555/QVSource to get a html page with various pieces of information about QVSource (e.g. the licence state, version, which Connectors were running). We have now tidied this up and added additional information. More importantly, we have added a new XML option at http://localhost:5555/QVSource?format=xml which allows you to check the exact QVSource status from your QlikView load script as explained here.

Log File & Error Page Updates

QVSource now has a much more structured XML file format with additional information added. As before, logging needs to be enabled for these to be generated as explained here. It should now be possible to load these files into QlikView directly for structured reporting.

Related to this, the HTML error page which QVSource sends back has also been enhanced and tidied.

appID Load Script Parameter

QVSource now adds an appID= parameter to the generated QlikView load script. We recommend setting a variable at the start of your load script, e.g.:

let vQVSourceAppId = 'my_app_identifier';

And then adding this variable to all of your QVSource requests, e.g:

....&appID=$(vQVSourceAppId)&....

This provides an identifier to QVSource to be used in error logging and tracing. This is explained in more detail here.

Note that in a recent 'nightly build' we actually generated the full appID=$(vQVSourceAppId) in the QVSource generated load script. Unfortunately it was pointed out that this actually breaks the QlikView 'Web File' Wizard (used for example in the General XML/JSON Connector and certain tables in other Connectors) - so now we just include an empty appID= parameter in the URL leaving it to the user to insert a value or variable in the final QlikView script as recommended above. This isn't mandatory or required and it can be left blank.

Other Connector Changes & Updates

  • The Google AdSense Connector for QlikView has been upgraded to use the latest API (version 1.2).
  • The Google Analytics Connector For QlikView has had a number of minor tweaks and fixes. These are only likely to affect you if you were using the MaxNumberOfPages parameter (i.e. not bringing back all the data for a particular query url).
  • Empty \Temp folder has been added to the distribution - this is currently the recommended location to store the parameters CSV files used by the new processParams[Sync|Async|Batch] feature.
  • The General JSON/XML API Connector now has a better preview of XML and HTML and also a new checkbox to encrypt the request URL before including in your QlikView script to help secure any sensitive credentials it might contain.
  • The Facebook Fan Pages and Insights Connectors now have buttons to 'Deauthorise' the Connectors (i.e. detach them from your Facebook account).
  • The Facebook Fan Pages Connector has a new QuestionVotes table listing the users who selected each option.
  • The Klout Connector has been tweaked to work more efficiently with the new new async feature. Note that the Klout V1 Connector for QlikView has been removed from QVSource.
  • The FreeAgent Connector has two new tables related to the Trial Balance. We have also removed V1 of this connector and recommend upgrading to the latest V2 version.
  • The first version of the Google DoubleClick For Publishers (DFP) Connector is now included. We hope to add more functionality to this soon. Please get in touch if you are interested.
  • The Semiocast Connector for QlikView now supports new languages and has some performance improvements.
  • We have upgraded the MongoDB Connector for QlikView to use the latest c# driver and also fixed a couple of minor issues.

All these recent features further enhance the speed and ease at which you can load your QlikView applications with data from a large number of web APIs.

We hope you like the updates and we are looking forward to continuing to innovate and improve QVSource - The QlikView API Connector in 2013!

New QVSource Nightly Build (1.4.0.8) Available

We have just pushed out a new nightly build of QVSource which has all of the updates noted here plus the following:

All these recent features further enhance the speed and ease at which you can load your QlikView applications with data from a large number of web APIs. We expect this will be the basis of the new official release coming in the next two weeks.

Major New QVSource Nightly Build (1.4.0.4)

Good news - We have just made a major new QVSource release available.

As there have been many significant changes and improvements this is currently only available as a 'nightly build' - this means it's not yet recommended (or supported) for critical production environments but we would recommend all QVSource users to try out this new release on their QVSource powered QlikView applications and report back any feedback or issues you are experiencing.

Where do I find this new release? If you are a QVSource customer or have requested a trial in the past you should see this new release at the personalised download link we should have sent you via email.

Note that it's possible that in the week(s) after this blog post and release is published, we will upload new nightly builds with incremental changes and fixes based on the feedback so please check the download page regularly for further updates.

Once this new release has been out for a few days to a week we will probably push out a dedicated email newsletter so that users who might not necessarily follow this blog or our Twitter, Facebook or other social media accounts, are aware of the new release.

We would then expect this to be released as the new official release some time in February.

The rest of this blog posts outlines the main changes in this latest version.

Before that - If you like what we are doing with QVSource and haven't already, please take a minute to rate us on QlikMarket or leave a recommendation on our LinkedIn product page.

Synchronous, Asynchronous and Batch Request Modes Added

This was explained in detail in the previous blog post and so will not be covered here. However this update has the potential to give major performance improvements and also change and improve the way QVSource related QlikView script is constructed. One thing to note is that we have now removed the previous mechanism for running asynchronous requests as the new functionality improves and supercedes this.

(Note: Version 1.4.0.7 released as a nightly build 26/01/13 fixes an issue in the Async feature of this).

QVSource Windows Service

QVSource now has a dedicated Windows Service available and documented here. We have always had a well documented and stable way of configuring QVSource to run on a server environment however the new Windows Service represents an improvement over this technique and in time will likely become the recommended and only supported method.

Related to this, we have also now made it so if QVSource is running in server mode you can run QVSource desktop in order to manage connector and other settings without having to then restart the QVSource server instance for changes to be picked up.

Checking the Status of QVSource

It has always been possible to browse to http://localhost:5555/QVSource to get a html page with various pieces of information about QVSource (e.g. the licence state, version, which Connectors were running). We have now tidied this up and added additional information. More importantly, we have added a new XML option at http://localhost:5555/QVSource?format=xml which allows you to check the exact QVSource status from your QlikView load script as explained here.

Log File & Error Page Updates

QVSource now has a much more structured XML file format with additional information added. As before, logging needs to be enabled for these to be generated as explained here. It should now be possible to load these files into QlikView directly for structured reporting.

Related to this, the HTML error page which QVSource sends back has also been enhanced and tidied.

appID Load Script Parameter

QVSource now adds an appID=$(vQVSourceAppId) parameter to the generated QlikView load script. We recommend setting this variable at the start of your load script (although it is not mandatory) to help provide an identifier to QVSource to be used in error logging and tracing. This is explained in more detail here.

Note that it was pointed out that appID=$(vQVSourceAppId) actually breaks the QlikView 'Web File' Wizard (used for example in the General XML/JSON Connector) - so in 1.4.0.8 and later we actually just include appID= in the URL leaving it to the user to insert a value or variable in the final QlikView script).

Connector Changes & Updates

  • The Klout V1 Connector for QlikView has been removed from QVSource, please upgrade to the new version. We have also made a couple of fixes and improvements to this new Klout Connector.
  • We have upgraded the MongoDB Connector for QlikView to use the latest c# driver and also fixed a couple of minor issues.
  • The Google AdSense Connector for QlikView has been upgraded to use the latest API (version 1.2).
  • The Semiocast Connector for QlikView now supports new languages and has some performance improvements.
  • We have removed V1 of the FreeAgent Connector for QlikView, please upgrade to the latest V2 version.
  • Added option to encrypt the request url in the General JSON/XML Web API Connector (version 1.4.0.7 released as a nightly build 26/01/13).
  • Deauthorise buttons have been added to the Facebook Fan Pages and Insights Connectors to remove the app from your Facebook profile (version 1.4.0.8 and later).
  • Empty \Temp folder has been added to the distribution - this is currently the recommended location to store the parameters CSV files used by the new processParams[Sync|Async|Batch] feature(version 1.4.0.8 and later).
  • The Web Preview window in the General JSON/XML Web API Connector should now format XML and HTML properly (version 1.4.0.8 and later).

Script Updates In New Twitter Demo Application For QlikView

In our last post we discussed the front end changes in our template QlikView application for Twitter analysis. We have also made a number of changes and improvements to the load script which I wanted to briefly outline.

  • The sentiment analysis can now be run asynchronously which can give huge performance boosts (up to a 90% reduction in load time of the sentiment in some of our tests as discussed here). This is turned on using the vAsyncSentiment variable in the config file.
  • New variables have been added to the config file to turn off sentiment analysis (vGetSentiment) and Klout scoring (vGetKloutScores) as we have seen some use cases where the user only wishes to load matching Tweets into the application.

As usual the full list of changes to the application can be seen on the first tab of the load script:

This latest version of this template application (version 1.0.5.1) is available for download on our wiki here. We would also recommend reading the contents of config.txt which is fully documented and explains some of the other advanced options which this application provides.

You will need QVSource to be able to reload it with your own data and you can register for a free fully functional trial on our website.

Page List