Today, QSE SaaS doesn’t do task chaining. Instead you have two options:
Use a scheduled reload task for every app, and try to make sure the start time for task 2 will always be later than task 1
Use Qlik SaaS REST APIs to trigger the reload
This post covers a simple approach (i.e. Qlik script only) for triggering reloads of downstream apps on completion of an app reload in a way that doesn’t require much maintenance or any external systems or integrations.
Generally, getting access to vehicle data is a pay-for-data experience – but snapshots are released each year to the public.
If you head to the Vehicle Statistics page on gov.uk you get statistics about vehicle licencing, excise duty evasion, vehicle roadworthiness testing and more. You’ll probably want to check out the index as there’s 76 files in the 2016 download alone, at various levels of granularity…
The one I’m going to look at today though, is:
Licensed Cars, Motorcycles, Light Goods Vehicles, Heavy Goods Vehicles, Buses and Other vehicles by make and model, Great Britain, annually from 1994, quarterly from 2008 Quarter 3 ; also United Kingdom from 2014 Quarter 4
AKA table VEH0120. Interestingly, Qlik Sense throws an “Unknown Error” message when trying to load “.ods” files so I converted it to Excel prior to loading.
This post looks at using Qlik Cloud (using a paid-for tier) to gather and analyse data from Google Analytics.
Qlik Cloud doesn’t allow user-added extensions, connectors or alterations (unlike the Qlik Sense Desktop and Enterprise products), but is free at the basic tier where you can load from uploaded files. As mentioned, I am using a “Plus” account which gives me access to more connectors.