Hello Qlik Users!Happy Featured Content Friday!This week we are featuring a partner from Vancouver, Canada!Martin of GINQO Consulting Ltd!Martin has been using Qlik products for 7 years. His current role is Senior Qlik Solutions Consultant and he specializes in Public Safety.When asked what his favorite thing about Qlik is, Martin said:"The current pace of development, innovation and expansion is blowing my mind! Amazing set of tools now and more to come." - MartinMartin shared a video showing how he created a keyboard using QlikView and Qlik GeoAnalytics within a Qlik Sense app. QlikView was used to create the shapes of the keyboard and a macro was used to find the coordinates of the buttons. The coordinates were brought into Qlik Sense as an inline table and then the Qlik GeoAnalytics polygon layer was used to "map" the keyboard. Check out Martin's video*:Creating novel shapes for Qlik Sense GeoAnalytics (using QlikView)Martin’s mind might be blown away by Qlik’s innovation but we are blown away by his ingenuity and application of our products!*The information in this post is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support may not be provided by Qlik Support.Do you want to be spotlighted in a future post? See our previous post, Introducing Featured Content Friday!, for more information on submitting your dashboards, workarounds, how-to’s or anything else you would like to share!Thank you for being a part of the Qlik Community and for choosing Qlik!Kind regards,Qlik Digital Support
...View More
Hello Qlik Users!Happy Friday! Did this week fly by for anyone else?It’s Featured Content Friday and I’m so excited to share a writer with you all today!He is an Enterprise Architect and has been working as the global lead architect for the past 6 years.Armand of Tata Consultancy Services!Armand is a former Qlikkie (he worked on the UK presales team for 3 years) and is currently a Qlik Luminary! Total, he has been using Qlik for 11 years. Armand’s favorite thing about Qlik:Armand wrote a great piece on scalability and performance optimization, particularly with how Qlik Sense apps are rendered. He takes you on his journey to discover ways to bypass the no-cache policy for static content. Please check out his article* onStatic Content Cache Policy*The information in this document is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support may not be provided by Qlik Support.Would you like to be spotlighted in a future post? SeeIntroducing Featured Content Friday!for more information on submitting your dashboards, workarounds, how-to’s, and articles.Thank you for being a part of the Qlik Community and for choosing Qlik!Kind regards,Qlik Digital Support
...View More
Hello Qlik Users!Not only is it Friday but it is also Featured Content Friday!Today we are featuring another long-time Qlik user (12 years to be exact) and Qlik Luminary:Radovan of EMARK!When asked what his favorite thing about Qlik is, he said:“Very fast answers (because in-memory) to complex business questions (because data is associated, not queried) on top of large amounts of data (because 10s of millions on data records can be handled on anotebook).”Using the REST connector and API’s, Radovan created a Qlik Sense app that monitors current performance and availability of his Qlik Sense environment*. Check out Radovan’s post on Qlik Community for more information as well the QVF file and steps to implement.Qlik Engine Health-Check AnalysisThank you for sharing what you created,@RadovanOresky! It's amazing to see what you can do with the power of Qlik.Do you want to be spotlighted in a future post? See our previous post, Introducing Featured Content Friday!, for more information on submitting your dashboards, workarounds, how-to’s, etc.Thank you for being a part of the Qlik Community and for choosing Qlik!Kind regards,Qlik Digital Support*The information in this document is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support may not be provided by Qlik Support.
...View More
Hello Qlik Users!Today is very exciting! Not just because it’s Friday but it is our very FIRST Featured Content Friday! We are so excited about this new series to get to know all of you, see how you are using Qlik and for the opportunity to showcase what you all are creating!Thank you to everyone for all the great submissions! Our first creator has been working with Qlik products for 15 years! Congratulations to:Adam Barrie-Smith of Pomerol Insight!Adam submitted a great video showcasing his use of calendar measureswithin Qlik Sense. Calendar measures allow you to easily compare current YTD to the same period for the previous year, for example. Adam also demonstrated the use of variables to easily adjust the timeframe being analyzed and to create titles so users know exactly what they are looking at.Check out Adam’s YouTube video where he explains his use case for calendar measures and variables to create an easy-to-use dashboard that offers his users flexibility in their Sales analysis.Let us know in the comments below if you have used calendar measures before.Do you want to be spotlighted in a future blog? See our previous post, Introducing Featured Content Friday!, for more information on submitting your dashboards, workarounds, how-to’s, etc. We can't wait to see!Thank you for being a part of the Qlik Community and for choosing Qlik!Kind regards,Qlik Digital Support
...View More
Hello Qlik Users,I hope you are doing well!A couple weeks ago, I blogged about the new App Analyzer. The App Analyzer is a new application that was developed for SaaS clients. The application provides a holistic picture of what is happening in your tenant by providing insights on memory footprints, development analysis, threshold analysis, and RAM utilization.I’ve seen a few issues pop up with configuring the app so I figured I would create a quick blog with the errors and troubleshooting tips.Error: HTTP protocol error 405 (Method Not Allowed):Troubleshooting tip: Check the request URL that the connection is pointing to. Verify it is correct and there is not a forward slash (/) at the end of the URL.Example: https://tenantname.us.qlikcloud.com/api/v1/items/ vs https://tenantname.us.qlikcloud.com/api/v1/itemsError: HTTP protocol error 401 (Unauthorized): Requested resource requires authentication.Troubleshooting tips:Authorization is spelled correctly and there is not a space after the wordBearer is spelled correctly and there is one space between the word and the API keyAngle brackets are not being used for the keyThis information is under Query headers and not Query parametersError: (Connector error: Invalid URI: The hostname could not be parsed.)Troubleshooting tip: Verify the vu_tenant_fqdn variable is set to the correct tenant name on the **Configuration** tab of the script.Personally, I found that creating the connection can be a little finicky. If you think that you have fixed the issue but it’s still erroring, try creating a new connection from scratch.Remember that the development team is keeping an eye on the App Analyzer blog for any issues or suggestions so please comment on that blog so the developers can assist.If you found this post useful please give it a ‘like’ and make sure to subscribe to the Qlik Support Updates Blog.Kind regards,Qlik Digital Support
...View More
Hello Qlik Users!With the recent change to Qlik Sense Desktop, we have seen some users facing issues with authentication. Users are reporting the following error message:Failed to authenticate against the selected server. Please make sure your internet connection is working and try again.There are a few reasons why this error could occur.ReasonSolutionThe firewall is blocking the required ports.Contact your local IT/network administrator and ensure that the following URLs can be reached using https (port 443):*qlik.com, *.auth0.comand*qlikcloud.com.Version of Qlik Sense Desktop.Verify that you have the most up to date version of Qlik Sense Desktop installed.A proxy is being used to access the internet.It may be necessary to bypass the Proxy to log on and authenticate or to contact your local/IT network administrator to ensure the appropriate ports are opened.A VPN is being used.Disconnect from the VPN or contact your l local/IT network administrator to ensure the appropriate ports are opened.The incorrect license was granted in Qlik Sense Enterprise.A professional or user access license is required to authenticate against Qlik Sense Enterprise.For more information on these solutions, please see this article. If you have any questions about authenticating against SaaS editions, please see How to authenticate Qlik Sense Desktop against SaaS editions.Please let us know if you have any questions. If you found this blog useful, please give it a like! Also, subscribe to theQlik Support Updates Blogby clicking the green Subscribe button.Kind regards,Qlik Digital Support
...View More
Inline load is a type of data load that can be used when you do not have a data source. The data can be entered manually or by using the wizard within QlikView or Qlik Sense.Here are a couple of key things to remember:Data entered through aninlineclause must be enclosed by square brackets [ ]The columns of the table are defined in the first line of the inline load statement, separated by comas.A semi colon (;) is required after the closing square bracketHere is an example of a simple table using inline load:Load * Inline [ID, Name, Age, Title1, Wladimir, 31, Team Lead2, Paul, 22, Technical Support Engineer3, Mark, 40, Customer Support Engineer4, Janne, 27, IT Specialist];In the example inline load above, the columns for the table are:IDNameAgeTitleThe values starting with 1, are all data values that will populate the table. After loading the data, and looking at the data model, it will look like a normal table:As with any other dataset, two inline load tables can be created and be connected as can be seen below. You can also connect your inline table to an already existing table:Inline load using the QlikView wizard:You can accomplish the same result using the QlikView Inline load wizard.In the edit script window, go to Insert > Load Statement > Load Inline. A window with a structure of a table will appear. Select the top cell indicated by F1 and change its value to the name of your first column. Repeat for the other columns of your inline table. Insert the data to create the table. At the end, your table should look like this:Inline load using the Qlik Sense wizard:In the Data Manager, select the ‘Manual Entry’ option located at the top left corner of the screen.Add the table name and double click on Field_1 cell to insert your first column name. Repeat this for the other columns. After naming all the columns, you should have something like in the image below.Note that at the bottom right you can see the column count = 4 and number of rows = 0. If you Insert data, you see that the number of rows is no longer 0.For more detail information on using the Qlik Sense Wizard, please see the following resources:Manual Entry - Qlik SenseInline load DelimiterPlease give this post a like if you found it helpful! Also please let us know if you have any questions or leave your feedback in the comments.
...View More
Security rules are a very powerful tool intended to assist Qlik Sense administrators in managing access to Qlik Sense features. Using these rules administrators can manage not just the ability to access or create applications, but almost all features of the product including data connections, streams and even individual components of the Qlik Management Console.This allows administrators to define user and administration roles that closely match unique organization needs rather than merely rely on an out of the box user model. Unfortunately, this comes at a cost, when a user logs in and access the system all the relevant security rules need to be evaluated to determine the correct access rights for the current screen. This can potentially lead to long load times and poor performance in especially in large systems.This blog post will cover a summary of the default user model Qlik Sense ships with, along with a closer examination of how security rules are evaluated and cached and in doing so will provide a framework for administrators to ensure that they can get the most out of their system and where possible reduce unintentional performance impacts on users.The Default Security RulesQlik Sense ships with a set of default security rules that provide a set of administration roles and user roles for organisations to use and modify to meet their own needs.When you first log in to a fresh installation of Qlik Sense September 2019, you will be greeted with a set of 63 rules which all work together to create that initial user model.Broadly speaking the model works as follows (Items in bold are unchangeable rules and are always true):In the Hub:Users can create appsOwners of items can see those itemsIf you can read a stream, you can read all apps published to the streamIf you can read an app, you can read the content of that appIf you can update an app, you can update the contents of that appIf you can read an unpublished app, you can create objects that are part of that appIf you can read a published app, you can create some objects on that appEveryone has access to the Everyone StreamAdministrators have access to the Monitoring Apps streamIn the QMC:The Service Account has access to everythingThe Root Administrator has access to everythingAudit Administrators have access to audit sections and entitiesContent Administrators have access to content section, entities and connection related security rulesDeployment Administrators have access to deployment sections and entities, apps (to manage load balancing) and license rulesSecurity Administrators have access to security sections and entitiesAs you can see there are two separate contexts for rules and that, for the most part administrator roles only impact the Qlik Management Console. This is because all administration activity is expected to happen in the QMC and not the hub. It is possible, and in some cases desirable, for your root administrator to operate entirely without an assigned license, though this does prevent them from using the monitoring applications.One final note about Security rules in Qlik Sense. Rules can only ever add privileges, they can never take them away. This is very important when trying to design your access model, try to think in terms of what users can do, rather than in terms of what they cannot do and the structure of your rules will flow much more easily.Security Rule EvaluationLet’s go a little deeper and focus on how the system evaluates security rules.Every rule has a set of attributes that are used during evaluations:Context (Does this rule apply in the QMC, the Hub or both)Resource Filter (The parts of the system the rule covers)Actions (The privileges the rule grants)Conditions (The set of conditions that ultimately determine who is granted the actions)A Score (A dynamically generated metric indicating how useful the rule is, the moreWhen a user accesses Qlik Sense, the system pulls only rules relevant to the current context and resources (for example, when accessing the hub, we need to evaluate the rules for a user’s apps, as well as the rules for streams).The system also will retrieve the relevant resources (in this case all published applications, applications the user owns, and all streams) to evaluate the combination of rules, user and resources.It runs through these rules in score order, these scores are stored in the Security Rule Evaluation Cache, which means the values are lost every time the system restarts.Once it has finished evaluating the rules, the results are stored in the Security Rule Evaluation Cache so that the next time this user accesses the same page the system can simply retrieve the result of the calculation from the cache and if necessary only evaluate the rules on new apps.The system will exit the evaluation early if the user has already been granted all the requested rights to a resource. For example: the Root Administrator will generally find most of the QMC will load very quickly because the rule evaluation is very simple. One of the oldest rules in any given system grants them all privileges on everything in the QMC, that rule will generally score very highly and so be evaluated very early and then there is no need to perform any further checking as rules can only add and not take away.On the other hand, a limited user who has been granted access to only the Apps Section of the QMC and a small handful of applications may find that interface takes a very long time to load as the system will first need to evaluate enough rules to give access to the requested resource (i.e. in a system that has no previous evaluation, the less access the user has the longer the evaluation will take.Finally, security rule evaluation takes place on a mixture of different nodes, some evaluations will take place on the node with the proxy you are connecting to, some will take place on the node with the engine, and some will take place on the central node.In the case of QMC activity, all evaluations will take place on the central node, and in the case of very limited users, those evaluations will be relatively lengthy and complex. On larger systems this can lead to a rather slow user experience on the QMC. In extreme cases this can lead to the system becoming effectively unavailable on all nodes. In Qlik Sense September 2019 we have implemented 2 feature flags to increase the scalability of the QMC at the cost of reduced functionality.See How to enable QMC Limits in Qlik Sense (KB 000086580) for details.The Security Rule Evaluation CacheIn the previous section I mentioned the Security Rule Evaluation Cache Cache, which stores the results of security rule evaluations in order to speed up future access. Why then does your system seem to slow down as more users and apps are added? After all the cache should eventually cover all common system activities.The cache is deliberately designed to be short lived, there are many circumstances under which it is either partially or wholly invalidated or discarded, meaning that a full rules evaluation needs to be completed once more. This is broadly because we need to know that the cache is correct, anytime something changes (or could have changed) we cannot rely on the cache and must revert to the slower approach.There are basically 3 types of cache invalidation:Complete invalidation (The entire cache is discarded)User based invalidationEntity based invalidation1. Complete InvalidationAny change to security rules, load balancing or license rulesAny change to custom properties values (i.e. the potential possible values a custom property can be assigned)When the system is restarted (the cache is never written to disk, and rules may have changed since the service last started)If the connection to the database is disruptedAs these changes could have a wide ranging impact, the entire cache is discarded and must be rebuilt by user behavior.When this cache is invalidated, the scores for every rule are also reset to 0, meaning that we also lose any optimizations gained since the session started.2. User based invalidationAny change to a user attribute (e.g. the user is added or removed from a group)A user’s custom properties are changedRules are often based on user attributes, changes to that user mean we cannot ensure the cached results still apply, so we discard the cached results linked to that user.3. Entity based invalidationAlmost any change to a single entity. (e.g. changing an app’s name or owner, approving a community sheet, renaming a data connection)Much like with users, changing any aspect an entity or resource that can be addressed in a rule means that we cannot ensure the cached results still apply for that entity, so we discard the cached results linked to it.In Qlik Sense February 2019, additional logging was implemented to record when a cache invalidation occurs along with its type (Complete, User, Entity)Recommendations/Best Practices:If you want to provide the best performance for your users try to make rule changes near scheduled downtime, when the cache is already going to be invalidated due to a service restart.To reduce the number of evaluations that need to take place, try to ensure you have a regular clean up process where you export and delete old apps that are no longer in use.Limited users in the QMC should also have a very limited scope, i.e. only get access to one or two sections. Where possible try to centralise QMC activities to a smaller number of administrators rather than expand access to the entire user base. In a large organization it is better to have a small number of administrators and a ticket system than to grant every developer access to the QMC for small scale task management.
...View More
.png "Former Employee"){kind=icon}
