QVSource 1.6.3 Now Available

We have just released version 1.6.3 of QVSource - The QlikView & Qlik Sense API Connector!

This is quite a substantial release under the covers, as we prepare to make the first beta download of the new web edition of QVSource available we have now upgraded all of the (non deprecated) connectors to use the new UI style. This has allowed us to remove a lot of legacy code and unify all the connectors under one system.

If you are interested in being notified of the new beta download for the web edition of QVSource please go to your usual download link where you will find a new tab for the web edition.

As always, in addition to reading the following for the highlighted updates and changes to QVSource 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 brand new Survey Monkey Connector.

Updated Connectors

  • Twitter Connector:
    • Fixed bug where search query for Twitter search table(s) was not being URL encoded. This bug appears to have been introduced 09/03/15. Note that this was also fixed in the recent intermediate 1.6.1.8 release made available on 10th June.
    • Added a 'manual' authentication option which helped a user who was running a very old version of IE and could not authenticate using the default option in QVSource. The manual auth option is now available for all OAuth1 and OAuth2 based connectors.
  • Google Adwords Connector:
    • Our AdWords Developer application has been approved and this connector can now be used by everyone.
    • Upgraded to v201506 of API, please read Reporting section of migration guide for any items which may affect your report queries.
  • Text Analytics & Sentiment Analysis Connector:
    • Polish is now available as an option with the Repustate API.
    • Fixed bug in Alchemy API Sentiment table which gave an error if <mixed> element was not present in the response.
  • Facebook Insights Connector:
    • BREAKING CHANGE: Removed page_storytellers table/metric. This metric is deprecated after the deprecate_PTAT migration.
    • Fixed bug where data from requests for different object IDs was getting mixed up.
    • Insights tables (excluding application insights) now have empty tables shown (i.e. with column headers) even if no data returned for selected date range.
    • Fixed bug where real-time tables (e.g. those with * at the end of their name) were no longer working. Note that this was also fixed in the recent intermediate 1.6.1.8 release made available on 10th June.
  • JIRA Connector:
    • Added AllProjects table and optional projectIdOrKey for AllIssues table.
    • Added option to first download all data then write table to minimise issues with missing columns.
  • OData Connector:
    • Updated code to set HTTP Basic authentication which did not appear to work in some scenarios.
  • YouTube Data Connector:
    • Added duration_timespan and duration_total_seconds columns to VideoStatistics table.
    • Updated 'Include Content Details' quota info, conditionally include extra columns.
    • Added url encoded comment and comment response text.
    • Added a ChannelStatistics table.
  • YouTube Analytics Connector:
    • BREAKING CHANGE - The MyId table has been removed as it relied on the now deprecated YouTube API V2.
    • We have updated the number of API calls which can be made per second through the connector.
  • Azure Data Marketplace Connector - This has been updated to the new UI style.
  • OneDrive Connector:
    • BREAKING CHANGE: Updated to use new API. This is a breaking change as available tables and columns have changed.

Removed Connectors

V1 of the OData Connector and Salesforce Connectors have been removed. These both have new and improved V2 versions which you should use instead.

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. You can also use this link to register your interest in the new beta download for the web edition of QVSource and being notified when it's available.

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!

Urgent Fix for Twitter and Facebook Plus v1.5.6 is Now Available

We've just released v1.5.6.1 of QVSource - the QlikView and Qlik Sense API connector, which is possibly one of our most important releases as it contains a critical fix for the SSL3 issue that arose yesterday and affects all our Twitter and Facebook users. As always we strive to give the best support we can and within a few hours of the issue being identified we had a fix available. You can read more about the issue in the post that we made this morning.

Due to the nature of the issue, this may also affect other connectors, so we recommend that everyone update to the new version as soon as possible.

In addition to this fix, we also have a number of general improvements, some of the notable ones being...

Twitter Connector

  • Twitter have dropped support for SSL3 connections, which QVSource now reflects (see above).
  • The Followers and Following tables now return up to 3,000 results.
  • A max_id parameter has been added to Mentions, UserTimeline HomeTimeline, DirectMessagesReceived and DirectMessagesSent tables. The Favorite table also has this as well as a since_id parameter added

General Web Connector

  • Many tables now have a checkbox to remove invalid characters.
  • Any @ symbol occurrences in JSON key names are now handled better when converting to XML where it is normally invalid.

MongoDB Connector

  • If server value begins with mongodb:// it will now be used as a standard connection string (i.e. port, username/password and database inputs will be ignored). This allows more flexibility in connection options.
  • We have fixed bug where document fields seen in a given batch of documents are not properly remembered on subsequent batches which can break QlikView load.

Sentiment & Text Analytics Connector

  • The Repustate engine now supports Russian.
  • Breaking Change - with Repustate you must now register for your own API key and use this instead of the built-in one, which is no longer available.

New Helper Connector

This is a new connector in development, which currently has a single Encrypt table. This can be used for encrypting a password before sending to, for example, the General Web Connector.

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.

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 can't find this, please get in touch.

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

QVSource 1.5.3 Now Available

We have just released version 1.5.3 of QVSource - The QlikView 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

  • Dropbox Connector: We have a brand new connector (beta) for Dropbox which allows you to list your files and folders, download file contents directly to QlikView as well as upload files to Dropbox via your QlikView load script.
  • Google BigQuery Connector: We have a brand new (beta) connector for Google BigQuery.
  • Sentiment Analysis & Text Analytics Connector:  We have added a new Regular Expression option to this Connector which allows you to perform RegEx analysis on any textual data in your QlikView application - you can see some examples here. Note that this is implemented locally in QVSource (it doesn't go via a Web API) so is very fast.

Updated Connectors

  • Twingly (Blog Search) Connector: We have an updated version of our Twingly Connector which allows searching for results from millions of blogs from around the world. With the new version you now get a small number of free API calls whilst trialling the connector and a larger number as a commercial user and there is no longer any need to contact Twingly separately for an API key.
  • Google Drive Connector: This now has a new table to return the contents of a file as XML (useful for example if you are hosting a QVD file on Google Drive).
  • Twitter Connector:  The Tweet Lookup table uses a new feature of the Twitter REST API which means it can now lookup up the data for up to 100 comma separated Tweet IDs per request (and 60 of these requests can be made per 15 minutes meaning ). We have also added the following trend related tables: TrendingLocations, TrendsForPlace, LocationsWithTrends. Finally, we have fixed a bug in the UserSearch table which was returning duplicated rows in some instances.
  • File Transfer (FTP/SFTP) Connector: FTPDownloadAndList and SFTPDownloadAndList tables have been added which list which files were downloaded and a FileCount column has been added to the simpler FTPDownloadFile/SFTPDownloadFile tables.
  • Sentiment Analysis & Text Analytics Connector:  We have added tables to support the new semantic API features from Repustate (Themes, Entities and Expansions). Please note also the old V1 of this connector is now deprecated and all users should move to the new version.
  • POP3/IMAP Mailbox Connector: We have added a new ImapMessageHeaders to allow you to access the emails headers.

Connector Fixes

Connectors Out Of Beta 

We've a few connectors that are moving out of beta, as such, if you're a customer and using these, please get in touch as they are now on our price list. 

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 at 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.

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!

QVSource 1.5.2 Now Available

We have just released a new version of QVSource - The QlikView API Connector. This blog posts outlines the main changes

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

New Connectors

  • SugarCRM: We have a brand new connector for SugarCRM, one of the most widely used CRM systems on the market. This connector allows QlikView users to load Accounts, Contacts, Leads, Opportunities, Forecasts, Meetings and Calls.

Updated Connectors

  • Facebook Insights V2: We have a completely revised V2 of our Facebook Insights Connector which uses the new UI style. This offers huge performance and usability improvements over the previous version (which is now deprecated and marked for removal) and we would recommend all users to upgrade. We have instructions here on upgrading from the previous version. Please note that the previous V1 of this Connector will be removed from QVSource in June 2014 so all users should upgrade no later than this.
  • MongoDB: We have a new version of our MongoDB Connector which uses the new UI style and the latest MongoDB Driver. The previous version of this Connector is now deprecated and although this Connector is still in beta would encourage all users to start using this new version and providing feedback or comments.
  • Google Calendars: We have a new version of our Google Calendar which uses the new UI style. This has a small but breaking change which is that the default data format is now QVX - we would recommend you regenerate your load scripts.
  • Google AdSense: We have a new version of our Google AdSense Connector which uses the new UI style and the latest API (v1.4) version. Please note that the previous V1 of this Connector will be removed from QVSource in June 2014 so all users should upgrade no later than this.

Removed/Deprecated Connectors

Of particular importance are the four removed Connectors listed below. If you are using these you must upgrade to start using the new versions.

  • The following Connectors have been removed as they have been replace/superseded with new improved versions:
  • Salesforce Connector: We have also deprecated our Salesforce Connector for QlikView. This is because Qlik have their own Connector to this already. We are not currently planning to remove the QVSource version from the product but are no longer actively maintaining or developing it. If you find the Qlik Salesforce Connector does not meet your requirements please get in touch.

Connector Updates

  • Google AdWords Connector: We have upgraded this by two AdWords API versions to the latest v201403. Please check the Report related updates here and here for changes and new features which you may be able to use in your reports.
  • Google Analytics Connector: We have fixed a minor bug where the WebProfiles table did not page correctly. This would only have affected users who had more than 1000 Web Profiles.
  • Google DFP Connector:
    • We have upgraded to the latest DFP API version v201403.
    • We have reduced memory utilisation and improved performance.
    • The Connector now makes more intelligent usage of the API quota limits.
    • The parameter input area should now scroll vertically.
  • Google Drive & Spreadsheets Connector: We have added the ability to specify a folder ID to move a newly created spreadsheet to.
  • Google Plus Connector:
    • The Person table has been renamed ObjectDetails (as it can return data for a Person or Page). For script generated using previous versions, the table People should be automatically mapped to this name. This table also has the following new fields: occupation, plusOneCount, circledByCount and primary_placesLived.
    • We have added a new ObjectDetailsAsXML table which returns all the details returned by the API as XML (ObjectDetails selects a subset of these to a structured table). This can then be natively parsed/loaded in QlikView.
  • Twitter Connector: We have added Post_UserLookup_Info and Post_UserLookupById_Info tables and an associated example application on GitHub here illustrating how they can be used. The purpose of these tables is to support the use case of loading information on a large number of followers or friends. Because the API only allows a limited number of calls per 15 minutes, if the account you are interested in has above a certain number of followers/friends then you need to accumulate this data over a number of reloads over a number of 15 minute windows.
  • Sentiment Analysis & Text Analytics Connector:  The ChatterBox option has been renamed to Sentimental. The Excitement table has been removed and an Anger table has been added for Chinese. These are changes based on the underlying API and not due to QVSource.
  • Facebook Fan Pages & Groups Connector:
    • The User and Person tables now always return a row, a new status column indicates any errors returned if there was an issue retrieving the data.
    • We have fixed a bug in the 'Don't return items before' feature which was sometimes not going back as far as it should.
    • We have fixed bug where the has_at_least_this_many_likes and has_at_least_this_many_comments fields always had a value one larger than the actual.
    • We have added comment_link and like_link columns to FeedItems and Posts tables. This contains a link which allows you to open the post in a browser from your QlikView application.
  • Blue Yonder Connector: We have upgraded this in line with the latest v1.14.0 and also changed the parameter input for the API version so the user can enter their own version number (rather than picking from a drop down).
  • General XML/JSON/SOAP Web Connector: We have added a new User Agent input field to allow this to be overridden.
  • You Tube Analytics Connector: This Connector has now been taken out of beta.
  • HEIDI Connector: The parameter input area should now scroll vertically.

QVSource On GitHub

You will now find most of our example and 'starter' applications over on our GitHub page here.

You don't need to know anything about GitHub to use them (just look for the 'Download ZIP' button for any applications you are interested in). However if you do have a free GitHub account you can use it to receive alerts for changes to the applications and also as a way of exploring the load scripts and their changes on the GitHub site itself (look for the LoadScript.txt file in the sub folder of the application you are interested in).

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 at the personalised download link we should have sent you via email.

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.

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.7) - The QlikView API Connector - Now Available

Today we've released a new version of QVSource, which has a large number of exciting enhancements, updates and fixes across a number of the connectors.

Of particular importance are a number or changes to the Facebook Fan Pages & Groups Connector - some of them breaking changes. So if you are using this connector please take note and upgrade and test your application scripts appropriately.

In a follow up to the last post, some more connectors have also been removed, but we've also added some new ones!

A New Way to Contact us for Support

If you've read any reviews about us (like the 36 5-star reviews on QlikMarket), you'll quickly see that we take supporting you very seriously and strive to give the very best service. To help us improve our customer service even further we've started to use Zendesk, (if, like us, you want to get Zendesk data into QlikView with QVSource, see below!) So if you do need to get in touch for support, if having read our documentation you're still stuck, please contact us at support[at]qvsource.com or qvsource.zendesk.com. That way you can be confident the right person will respond to you as quickly as possible.

Updates to Connectors

  • Sentiment & Text Analytics V2 Connector
    • Chatterbox has now been added to the connector.
    • The Repustate option now supports Italian.
  • General Web Connector
    • A comma separated list of http Headers can now be specified for requests as well as the accept type.
    • We often get asked if our General Web Connector can work with certain APIs, which in many cases it can. So, we've put together a few examples on how to use this connector with ZendeskRome2Rio (an API that gives routing between 2 points), desk.com and how to use it with a SOAP web service
  • Mashape Connector
    • The authentication process for Mashape has changed and the connector has been updated to reflect this.
  • Facebook Pages & Groups Connector
    • BREAKING CHANGE: Due to API changes, the FeedItems and Posts tables can no longer show the like count. We have added a new table LikeCountForItem table to retrieve this. If you are using the Facebook Pages Application, then you will now see zero for the count. An updated application with the new table will be released soon. If you are using this connector we would strongly recommend you test your QlikView applications against this new version and adjust your load scripts as necessary before deploying to production.
    • A new Albums table has been added.
    • A new PromotablePosts table has been added. This is similar to Posts except it includes 'the Page's own posts, including unpublished and scheduled posts' and has an additional is_published column.
    • The cache is now cleared when the user re-authenticates.
    • We have tidied up some labels and other minor issues.
  • Twitter Connector
    • We have fixed the info labels on UserLookup table.
    • A new FollowersId table has been added.
    • There is now better handling when the quota limit is reached on the Follower and Following tables.
  • Mailbox Connector
    • Fixed issue where exceptions requesting table would sometimes crash QVSource due to invalid XML characters in the stack trace.
    • Better checking of nullable values when downloading Imap mails (this could have caused an incomplete download in some instances).
    • The Imap download should no longer fail completely if a single email fails.
    • For Imap, it now handles case where To field is a MailGroup and shows the group name.
  • iTunes Connector
    • BREAKING CHANGES: There have been a number of updates and improvements to this connector which will mean any load scripts using the connector will need to be re-generated. Please see the change log for details.
  • MongoDB Connector
    • Added a new input for Database name (this can also take a comma separated list). This is useful in scenarios where the user does not have permission to enumerate the Database names.
  • General updates

Connectors Removed

  • The Solve360, Freshbooks and FreeAgent Connectors have now been removed, which as far as we are aware were not being used and, as we mentioned in our last blog post, we want to focus our efforts on connectors which are more popular. As before, if you are using these and feel we have made a mistake do get in touch and let us know.

Starter Applications & Examples

In a recent Facebook update comments can have replies against them, which was quickly added to the Facebook Page & Groups Connector. We have now incorporated this into our Facebook Pages Starter QlikView Application. There have also been some other breaking changes to the Facebook API (see above) which we are working on incorporating into the demo application.

The Google Analytics Starter Application has also had a few minor fixes.

Moving Starter/Demo QlikView Applications to GitHub

We have also thought about how we can improve the delivery and maintenance of these Starter/Demo applications to you as it's not always clear what changes we make, so we are starting to trial GitHub as a place to do this. For most users you won't really notice much change in how you get the starter applications, but for those who want to understand the changes and improvements we make, it'll become much more transparent, which we think is a good thing.

You can read a wiki page with more information on how this works here.

New YouTube Analytics Connector

In addition to the YouTube Data Connector where you can get largely public-based data on videos, we now have a YouTube Analytics Connector for those of you that need a much greater insight into your videos.

Try QVSource

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. You can find upgrade instructions here.

If you are new to QVSource but are a QlikView user interested in getting data from Web APIs into your applications, why not get your free trial of QVSource? It's quick to do and in a few minutes you can get your data into QlikView with one of our starter applications.

If you've already trialled QVSource and would like an extension, please get in touch via support[at]qvsource.com (attaching your current licence file) and we'll happily extend it for you.

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+.

Page List