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