Setting the scene ...
Here, I am going to share my experience with implementing data governance in QlikSense, please note that this can be readily applied to QlikView as well because the architecture is the same.
I will run the DG articles in a series over the coming weeks as it is a fairly large topic, but so far has been well received on site.
Getting down to it, essentially with both QlikSense and QlikView a developer will construct expressions to calculate some aggregation of facts contained in the model, a simple example is an average over sales avg(SalesAmount) and indeed expressions can become very complex, we won't cover that here (I feel a blog entry on Set Analysis forming).
Lets for a moment assume the above expression is used in more than one App or Document.
So what ? you say ! But just imagine this expression is in 20 QlikView documents and or 30 QlikSense apps.
Then the business get's in touch with the team or person tasked the overseeing of these apps and documents and informs them that the average sales needs to be calculated as avg(SalesAmount - SalesCost), well now things get a little labour intensive as you need to change 20 docs and or 30 apps.
The workflow would entail Dev to UAT to Prod, and hopefully you did'nt forget an app that the CEO looks at on their mobile device.
Now the developer (Data Analyst) has a bunch of work to do , taking them away from other work in the work flow.
Is there a better way ? Yes with some initial effort and setup of the methodology a boost to QlikSense and QlikView data governance will be sustainably achieved.
Stay tuned for the next post.