Dimension limitations offer a quick and easy way to measure performance of your metrics by assigning user defined limitations, that respect fixed, exact, relative and calculated values. As a result, your visualization will display a reduced set of values according to the definition of the limitation.Regards,Mike TaralloQlik ...View More

The Qlik Community currently has 97,142 register members from around the world. In which over 2,000 could be online almost at any time! We are seeking answers to questions, helping others find solutions, informing the Qlik team of product issues, or simply browsing the extensive library in search of valuable content. Qlik Community members have varying skills that range from newbies to “Jedi Masters” 😀 . BUT – our members are not just limited to posting questions and providing answers to one another, they also post solutions and helpful tutorials about various Qlik products, deployment scenarios and situations.Which brings me to introducing@rohitk1609 (Rohit Kumar). Rohit has reached out to me in an effort to highlight and share some of the fantastic information he has created when working with the Qlik Analytics Platform.Rohit is a Sr. Business Intelligence Administrator in New Delhi, India and is ranked as a Contributor III in the Qlik Community. His 8+ years of experience with Qlik products, consulting and implementing BI solutions has prompted him to create and share what he has learned when deploying many instances of Qlik Sense. Currently, his primary role is to deploy and manage Qlik multi-node sites - which are robust, scalable and highly reliable. Rohit did not find a particular document that explained everything he needed to know when it came to deploying a Mulit-node Qlik Sense site and thus made an effort to publish the steps he followed, including consolidating many of the Qlik Help materials to help guide you towards a successful multi-node deployment. He also has answered many questions posted to his document thread and will be happy to answer any of yours.• Best Practices of Qlik Sense Multi-Node Setup, Load Balancing & MaintenanceI'd like to thank Rohit for his contribution and I encourage all of you to share what you have learned when working with Qlik so others may also benefit from it.The Qlik Community – works together to achieve successful outcomes through conversation and collaboration.Do you have a valuable Qlik product contribution or solution? Contact me and I will share it on the Qlik Design Blog.RegardsMike Tarallo - followSenior Product Marketing ManagerQlik ...View More

A colleague of mine had translated two demos from the Demo Site to Japanese and wanted to know if we could post them on the Demo Site alongside the English versions. We decided that it would be best to combine the English and Japanese versions into one multilingual Qlik Sense app making it easier for us to add additional languages to the app as needed. It was an easy process and required only a few steps:Create a translation sheet with all the languages that will be available in the appUpdate the script to add a table of the translations and a list of the languages available in the appAdd a Language filter pane to every sheet in the app that allows only one selected valueUpdate sheet names, chart titles, subtitles and labels with an expression that will display the text in the selected languageCreate Translation SheetTo begin the process of making a demo multilingual, I created an Excel file with all the languages that are to be included in the app. Below is a snippet of the worksheet. The first column, Index, has a unique value which will be used in the charts and expressions to indicate what data should be displayed. The second and third columns are the languages to be used in the app. An additional column can be added for additional languages that need to be added to the app. In this scenario, I entered all the English text (sheet names, chart titles and subtitles, labels and text) and then using the Japanese version of the app, I entered the respective Japanese text. If I did not have the Japanese version of the app, I would have shared the Excel file with someone who could enter the Japanese translations for me. Preparing the Excel file in this format makes it easy to add additional languages to the app without having to update the QVF.Snippet of Excel translation sheetUpdate the ScriptOnce the translation sheet was created, it needed to be loaded into the data model. The script below is what I added to the demo.On line 1, the HidePrefix system variable is used to hide all fields that begin with “#.” Starting on line 3, the Excel file is loaded. Once it is loaded, the vLanguage variable is set to the expression “=Minstring(#LANGUAGE).” This is an important step and we will take a closer look at this when we update the front-end. On line 13, the languages from the Excel file are loaded - users can select the language they would like to view from this list. These languages are then stored in the #LANGUAGE field which will be hidden from the user (since it starts with “#”).Add Language FilterOne each sheet in the app, I added a Language filter pane using the dimension #LANGUAGE that was created in the script. Once the script is reloaded with the HidePrefix variable, the #LANGUAGE field will not be visible, but you can still use it as the dimension in the Language filter pane. I needed to see the field temporarily so I commented out the HidePrefix line in the script and reloaded so I could change a setting on the field. I only want the user to be able to select one Language at a time, so I needed to check the “Always one selected value” checkbox in the Field settings of the #LANGUAGE field. (Right click on the #LANGUAGE field and select Field settings to see the window below).Field settings dialog windowOnce my settings are saved, I uncommented the HidePrefix line and reloaded the app to hide the #LANGUAGE field again. The filter pane will look like this (image below) and only one language can be selected at any given time. When a language is selected, the vLanguage variable (that was created in the script) will store the language. This variable is used later when updating the text in the UI.Language filter paneUpdate Front-EndNow the last step is to update everything in the app that should be translated. In this scenario, I updated sheet names, chart titles and subtitles, chart labels, KPI text and text on the sheets. Here is an example of how I updated the title of the Language filter pane. In the title field, I entered:In the snippet below from the Excel translation sheet, the Index is 64 for the text “Language” which is why I used it in the expression above for the title of the Language filter pane. This expression will return either the English or Japanese translation for Language depending on the value of the variable vLanguage.Snippet from Excel translation sheetAnother piece of information I would like to share is how I handled Text & image objects that needed to be translated. In the screenshot below, there is heading text and body text that have 2 different formats (font size and font color).To handle this, I created two variables, one for the heading and one for the body and in the variables, I stored the translation expression.This way, I was able to not only translate the text but format the text in a single Text & image chart two different ways.As you can see, it is easy to make a Qlik Sense app multilingual and it is easy to update the app with additional languages as needed. Sales, Customer Experience & Churn and Supply Chain – Inventory & Product Availability are the two demos that were made multilingual. Check them out and switch between the languages to see the final results. If you are interested in doing this in QlikView, check out Chuck Bannon’s blog on this topic as well as making the data multilingual in a QlikView app.Thanks,Jennell ...View More

Hi Guys - A little feature that sometimes can be overlooked, can make a world of difference. Many know that the Master Items Library is a great way to store your reusable data visualizations, as well as expressions defined for your measures and dimensions. BUT did you know that you can quickly add your already defined expression to the Master Item Library without having to cut and paste and switch screens? Since the September 2019 release we have made it even easier to develop and encourage reuse - you can now quickly add those expressions to the Master Items Library with a click of a button. Check out this 60 second video to learn how. Learn more in 60:https://www.youtube.com/watch?v=DruqV98s_xk&list=PLW1uf5CQ_gSpuFutN7IbRfzWeI1kgGZrH Regards, Mike TaralloQlik ...View More

...View More

With the design work to introduce Spaces, available in Qlik Sense cloud-based editions and discussed in Part 1 of this series....todayFredrik Lautrup is back with Part 2 - sharinghow his team wants to evolve the life-cycle for content in Qlik. Observing and talking to our customers we have seen that there are often two needs that the customer wants to cater for with their Qlik platform. The ad-hoc flow where you develop concepts and explore data. Here it is important that you can be agile and collaborate on content quickly. The governed flow where quality and control are important to create trust with the users who want to make decisions based on the data. So, we set out to create the two flows. In the ad-hoc flow we have personal spaces as a starting point where you can do experimentation and exploration of your data and the shared spaces where you can continue your collaboration around with others on the data. Both these space types are targeted for self-management allowing users to quickly and in an agile/collaborative way work to author content. But once we have content that we want to move into production for consumers and self-service users to explore and make decisions on we have a different set of requirements targeted at creating trust. Here we have the managed spaces which introduce a more controlled release process allowing users to trust the quality of content. With two flows, ad-hoc and governed, we need a way to bridge them. This is publishing. The publish workflow allow developers to continue developing while consumers and self-service users can start using the content to make data driven decisions. This is achieved by the publish workflow by creating a copy and move one of the items to the managed space locking it for changes. While maintaining a linked copy in the ad-hoc flow to continue building on. When a new version of the app is ready the content can be moved in a controlled manner into the managed space again. With the publishing as a bridge we have been able to evolve the content life-cycle to both support an ad-hoc flow for the agile/collaborative work and bridge this with the managed flow to maintain the trust in the data. But even if this default life-cycle has evolved there are always more advanced use cases that we would like to support, so in the next post I will walk through some of the more advanced capabilities that will be built out to support things like data movement and release management of content. If you have questions or ideas, please do not hesitate to put a comment below. For more information on spaces and our cloud editions of Qlik Sense check out this 2 part videos series plus bonus video on Spaces. Take a Tour of our cloud editions of Qlik Sense Spaces ...View More

It was back in 2015 when I first published the original Qlik Sense Search Cheat Sheet. Since then, and thanks to lots of individual contributors here in the Community, the Search Cheat Sheet has suffered several transformations to make it more complete and truthful.@afurtadowrote me an email a few weeks ago because he was interested in getting the document localized for the Brazilian folks out there. In addition to thank him for his contribution and sending him the file I decided that it was about the time to get the Search Cheat Sheet an update.Today I want to introduce a new version of the document. I added the compound search section to it (@jayanttibhe thanks for the tip), and I redesigned and rationalized the position of each element for better comprehension.As an extra, I made the document multilanguage ready. So, if someone wants to translate the Cheat Sheet to other language (currently available in English, Spanish and Portuguese) please let me know in the comments section and I'll gladly tell you how to help us.LanguageURLContributor(s)English - USAhttps://webapps.qlik.com/search-cheat-sheet/Qlik+Sense+Search+Cheat+Sheet+en-US.pdfPortuguese - Brazilhttps://webapps.qlik.com/search-cheat-sheet/Qlik+Sense+Search+Cheat+Sheet+pt-BR.pdf@afurtadoSpanish - Spainhttps://webapps.qlik.com/search-cheat-sheet/Qlik+Sense+Search+Cheat+Sheet+es-ES.pdfGermanhttps://webapps.qlik.com/search-cheat-sheet/Qlik+Sense+Search+Cheat+Sheet+de-DE.pdf@g_mitschkeRussianhttps://webapps.qlik.com/search-cheat-sheet/Qlik+Sense+Search+Cheat+Sheet+ru-RU.pdf@martynovaItalianhttps://webapps.qlik.com/search-cheat-sheet/Qlik+Sense+Search+Cheat+Sheet+it-IT.pdf@AntonioCostantinoFrenchhttp://webapps.qlik.com/search-cheat-sheet/Qlik+Sense+Search+Cheat+Sheet+fr-FR.pdf@arychenerHope you like it, and please share it.ArturoUpdates:Feb 28: French version thanks to@arychenerFeb 25: Italian added thanks to@AntonioCostantino. Russian translation updatedFeb 13, 2020: Cheat sheet includes now the ^ Wildcard to be consistent with Qlik Help. Russian language added thanks to the contribution of@martynovaJan 29, 2020: German language added thanks to the contribution of@g_mitschke ...View More

Hi guys – I have some great news to share in preparation for our annual customer and partner conference, Qlik World, formerly known as Qonnections. For the first time, you will now be able to immediately join the discussion with those attending QlikWorld - including Qlik’s team of experts - on event-related content and events – all via our Qlik Community forum. We have created a new forum in the Qlik Community where you can post questions, view Qlik World documents and learn more about the informative sessions you may want to attend. You will have inside access to many of the Qlik World key topics and themes to be presented, giving insight into our 2020 direction. There will be a selection of Qlik employees available to “Qonnect” with – whether they are product specific or event related, who will have the answers for you! . You can also subscribe to boards in the Qlik World forum to be notified of content that is published. Areas available: • Data Analytics Platform • Data Integration Platform • Data Literacy • Customer Success & Use Cases • Customer Success & Data Literacy • Technical Training & Certifications • Event Info • Panel & Round Table Sessions • Partner Success & Integration So get connected, be involved and share your ideas with your peers and Qlik’s data and analytics experts who are passionate about Qlik's platform, transforming business processes and driving data-driven insights. This forum will get you energized and ready for Qlik’s largest customer and partner event of the year. Let’s start a discussion. Join me in the QlikWorld forum today. Check it out! Register for QlikWorld here. BTW - here is a shameless plug - check out what I'll be up to at QlikWorld- have a question? Let us know, we'll do our best to answer. Hope to see you there!Regards,Mike Tarallo - TwitterQlik ...View More

Hi Guys Recently, we've had some communication in regards to the registration process for a Qlik Sense Business tenant. Though, it is fairly simple and straightforward, some people prefer to see it in action first before actually attempting to do it. So I decided to show you the steps needed to register the tenant both with or without a Qlik Account. I have also created a quick video showing how quickly you can create your first Qlik Sense app and add data to it. (Sample data file attached below). Note these videos can be quickly used in situations where you just need to get started as quickly as possible and don't necessarily have the time to watch a longer product tour (also available). Please see link below for other detailed resources and let me know if you have any comments or question. Also - don't forget to enter the #QlikHighlights2019 $100 Amazon Giveaway for your chance to win a $100 Amazon gift card. Official rules and more information available here:https://community.qlik.com/t5/Qlik-Design-Blog/The-QlikHighlights-100-Gift-Card-Giveaway-Starts-Today/ba-p/1663495 Regards, Mike TaralloQlik Register Your Qlik Sense Business Tenant Create Your First App Resources Topics You Need to Knowhttps://community.qlik.com/t5/Qlik-Sense-Documents-Videos/New-to-Qlik-Sense-Topics-You-Need-to-Know/ta-p/1530582 ...View More

Almost two years ago, in February of 2018, the Qlik Demo Team (Qdt) publicly released qdt-components (GitHub, npm). We originally built Qdt-components as an internal library designed to help us create demos to showcase Qlik Sense Enterprise. We opened up the library to help others use the new Qlik APIs and create interesting mashups with their data. Since that initial release, we've written over a dozen blog posts to the Qlik Community Design Blogdetailing how to use the various Qlik Sense and Picasso.js charts available via Qdt-components. In 2019, we hit 50 stars on GitHub, putting us in the top 1% of all open-source projects on GitHub. We've recently made some updates to our documentation and we wanted to re-introduce Qdt-components, show off our new logo, and highlight this powerful library's practical uses and recently added features.Qdt-components is designed to be a library-agnostic method of connecting to Qlik Sense and displaying visualizations. Whether that is bringing in entire Qlik Sense charts and objects or building your own visualizations, Qdt-components is an easy-to-setup wrapper that can be used in a number of different ways. We've written in the past on this blog about the pros and cons of using the various APIs to connect to Qlik Sense (Getting Started with Qlik APIs, Integrating Qlik Sense into your Web App), an area that developers can easily get tripped up on. With Qdt-components, the question of whether to use the Capability API or incorporating Enigma.js has already been handled. You just need to answer one simple question: do I want to use charts and objects directly from my Qlik Sense app? If so, then you want access to the Visualization API; otherwise, the Engine API is sufficient.Bringing in Qlik objects with the Visualization API means that it'll have the appearance you'd see in a Qlik Sense app. If you don't need to customize the look of your objects for your web app, then you can just build the charts / toolbars / etc. in Qlik Sense and bring them into your mashup using their object id's. If you want to skip all that, you can use our pre-built components by simply specifying the dimensions, measures, columns, etc. you need. Here are the available components as of 01/01/2020, the appropriate Qlik API required for the configuration object, and links to documentation to get you started:QdtVizThese are used to bring in Qlik Sense objects exactly as they are in Qlik Sense. QdtViz components require the Visualization API (vizApi: true) and are one of the easiest to implement; you just need the object's id.Visualization API: yesEngine API: noBlog Posts:qdt-components - A Components Library that can be used in simple Html, Angular 5 and ReactDocumentationQdtCurrentSelectionsLike QdtViz, QdtCurrentSelections requires the Visualization API and appears as it is from Qlik Sense. It can be used to show your user's current selections in the familiar, Qlik-styling. The only property you need to specify is its height.Visualization API: yesEngine API: noDocumentationQdtFilterUsing the Engine API, QdtFilter is a simple dropdown based on a column from your data.Visualization API: noEngine API: yesDocumentationQdtSelectionToolbarThis component displays a toolbar with the current app selections.Visualization API: noEngine API: yesDocumentationQdtPicassoThe QdtPicasso component actually comprises several Picasso.js charts; fifteen (15) as of January 10, 2020. Picasso.jsis a charting library streamlined for building interactive visualizations for the Qlik product suites. With Qdt-components, connecting to and using Picasso.js is super easy because it's already built in...no need to import Picasso.js yourself.Visualization API: noEngine API: yesBlog Posts: qdt-components - Horizontal Barchart by Picasso.js & Selection Toolbar,Qdt-components & Picasso.js - More Charts!,Qdt-components - custom charts with Qlik's Open Source picasso.js,Creating custom charts with qdt-components,DocumentationQdtSearchThe QdtSearch component is a simple text input field that can be used to search a dimension of your data.Visualization API: noEngine API: yesDocumentationQdtMapBoxWe've recently added our MapBox integration with the QdtMapBox component. You'll just need a MapBox API key and desired styling to create a map showcasing your data.Visualization API: noEngine API: yesBlog Posts:Creating a Geo Map with qdt-components and MapBoxDocumentationQdtTableBuild a sortable table of your data using QdtTable.Visualization API: noEngine API: yesDocumentationGetting started with Qdt-components is easy but we've created several templates to make it even easier:HTML / Vanilla JavaScript Template,HTML Documentation, DemoReact Template,React Documentation, DemoAngular Template,Angular Documentation, DemoAnd lastly, do you have an idea for a feature, bug fix, or chart to add? You can open an issue on GitHub or contribute! ...View More