Facebook Fan Page Connector (v1.4.6) Bug Fix

We just noticed a bug which appeared in our new release a week ago which means that for the Facebook Fan Page Connector, the has_at_least_this_many_likes column was always returning same value as has_at_least_this_many_comments.

This column is typically used to make a decision as to whether to call one of the other tables in the Connector to get more detailed and accurate information about the likes if the has_at_least_this_many_likes value is greater than zero.

We have released version 1.5.2.3 which addresses this and can be downloaded from the usual location you go to which will vary depending on whether you are a partner, customer or currently evaluating the software.

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.

Tracking The 2013 Argentine Legislative Election On Twitter With QlikView And QVSource

Just a quick heads up on a great application built by Ignacio Albano (@nachoalbano) and a QlikView partner in Argentina to track Twitter activity related to the upcoming Argentine legislative election.

The application is built using QlikView with QVSource providing data from Twitter. We have included a couple of screen shots below, but if you are quick (the elections fall at the end of October 2013), you can try the live application online here.

QVSource - The QlikView API Connector - contains connectors to a large number of web APIs, including Facebook, Twitter, YouTube, Google Analytics, Multiple Sentiment Analysis & Text Analytics APIs and many many more. You can request a free, fully functional trial, over on our website.

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.

Upates to the QVSource Facebook Fan Pages Starter App For QlikView

A quick note to say that we have just updated our Facebook Fan Page Starter App for QlikView to stay in line with the recent changes to the QVSource Facebook Fan Pages & Groups Connector for QlikView here.

As a reminder this application lets you make a couple of minor edits to a config file and then very easily start loading data for a number of Facebook Fan Pages (or Groups) into QlikView. The application also uses the QVSource Sentiment Analysis and Text Analytics Connector for QlikView to score the posts and comments for sentiment.

You will need the latest version of QVSource (1.4.7.5) to use this application.

The config file for the application now has two new variables:

// If the has_at_least_this_many_likes value is less than or equal to this we assume this is
// the actual like count. If it is greater than this we make extra table requests (and therefore
// API calls) to establish correct number.
let vLikeCountThreshold = 25;

// Same as above but for comments.
let vCommentCountThreshold = 25;

This means that if the following variables are both set to 1:

let vLoadCommentCountForFeedItems = 1;
let vLoadLikeCountForFeedItems = 1;

And the connector can establish that the comment or like count is at least as big as the threshold values set, then the QlikView load script will now make additional requests to other tables (and therefore API requests in the background) to retrieve the exact value.

Note that turning on these vLoadXXXXXXCountForFeedItems variables will slow the load script down so if you don't need these more accurate like and comment counts we would recommend that you leave the values set to 0.

Almost all the changes to this application have been made on the "Facebook Feed" tab of the QlikView application's load script.

The full change log for the application can be found on the GitHub page, on the first tab of the QlikView application and is also duplicated below.

1.9.2.0 - 30/08/13
------------------
* BREAKING CHANGES - This new version will not be compatible with QVDs from a previous version.
* IMPORTANT - This version requires QVSource 1.4.7.5 or later.
* Added columns to feed table:
from_id as FeedItem_from_id,
status_type as FeedItem_status_type,
to_id as FeedItem_to_id,
to_name as FeedItem_to_name,
to_category as FeedItem_to_category,
story as FeedItem_story,
application_name as FeedItem_application_name,
application_namespace as FeedItem_application_namespace,
application_id as FeedItem_application_id,
has_at_least_this_many_likes as FeedItem_has_at_least_this_many_likes,
has_at_least_this_many_comments as FeedItem_has_at_least_this_many_comments,
* Added new vLikeCountThreshold and vCommentCountThreshold to config file and associated logic/loadscript. See notes in config file for more detail.
* vIgnoreCache moved to config file.
* Added warning notes on intro tab when vLoadCommentCountForFeedItems or vLoadLikeCountForFeedItems are not set to 1.
* App is now set to require QVSource 1.4.7.5.

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

New QVSource Release (1.4.4) Available

It's been six weeks since we released 1.4.3.0 and as usual we've been working hard to make QVSource even better to give QlikView users even more power and flexibility in connecting to Web APIs and other data sources.

We are pleased to announce that a new version is now available with quite a few interesting enhancements and also a couple of fixes which may have affected some users:

  • We have fixed a couple of important stability issues:
    • Some users were finding that the connectors were not loaded/showing until the 'Include Beta' checkbox had been toggled at least once.
    • The main settings file was occasionally getting reset and losing, for example, the fact that the EULA had been accepted. This was causing issues especially for server based deployments.
  • We have added a new ListFileRevisions table to the Google Drive Connector.
  • The MongoDB Connector has had some massive performance boosts and can now be queried using JSON.
  • The Twitter Connector Search is no longer limited to a maximum of 15 pages of result (i.e. 15 x 100 = 1500 Tweets).
  • Three new tables (GroupMembers, Files and Events) have been added to the Facebook Pages & Groups Connector. We will be working on support for the new comment replies soon.
  • We have updated the DoubleClick for Publishers (DFP) Connector to use the new API (v201302).
  • BREAKING CHANGE: The Accounts table has been removed from the Facebook Insights connector (this is dues to removal of this feature from the API itself).
  • A new 'Include Depreciated Connectors' checkbox has been added and deprecated connectors are no longer shown by default.

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 Twitter, Facebook and Google+.

Page List