Every Friday at Bitmetric we’re posting a new Qlik certification practice question to our LinkedIn company page. Last Friday we asked the following Qlik Business Analyst certification practice question:
There was a little catch to this question, which fooled exactly no one đ
Recently I made a QlikView application with multiple languages. I came across a blog post by Charles Bannon: âHandling multiple languagesâ. Charles describes two scenarios for the use of multiple languages. The first scenario, âtranslate labels and textboxes within the application and not the actual dataâ, solved my problem. Charles uses a translation table with an index. He uses set analysis to reference the index number and the language. The expression used is:
=Only({<Index={5}>} [$(=vDataLanguage)])
A good solution, but not very user-friendly. Do you know which translation belongs to index 5?
In this blog post I will rewrite the expression to a more user-friendly and readable formula, and will also explore some other ways of dealing with translations in QlikView.
A little while ago, I was asked to change an existing QlikView Application. While scanning the application, I found that it used Alternate States. I had already heard about Alternate States, and that they could store different user selections, but didnât have any hands-on experience yet. I decided to dig a bit deeper into the subject before continuing. I wrote down what I learned in this post