Feedback on Qlik Reporting Experience

[_JFKDW_]

I’ve been using Qlik Reporting recently and often find myself struggling in several areas:

• Locating images I’ve added to the image library.
• Debugging deployments to identify where images have been used.
• Understanding error messages, which often lack clarity.

The most frustrating part isn’t just finding the right images—it’s even harder to delete unwanted ones. Before removing an image from the library, I must first delete every instance where it’s deployed. However, templates don’t display image icons, so I have to click into properties and check image sources manually. Imagine doing this for 50+ images in a template—it feels like one step forward, ten steps back.

When I used NPrinting, the process was much simpler. If Storytelling had the 'LEVEL' similar functionality, it would save us significant time and effort.

Challenges and Suggestions

Below are the issues I’ve encountered. I hope these are not inherent limitations but rather gaps in my understanding or missing guidelines.

Problem	Challenges	Better Alternative Suggestion by Qlik or Other Qlik Reporting Expert from Community
Adding Images – One by One	Adding multiple images from a sheet is cumbersome: Navigate to the sheet, wait for rendering. Find the image, add it, wait for rendering again. Repeat for every image. As a leading BI tool, I’d expect multi-select functionality for adding images—this should be a basic feature.
Images Entity Sorting	Images entity in the library aren’t sorted by the time they were added. They appear randomly, possibly by name, and there’s no sorting option. For example, the last image I added might appear near the top instead of at the end.
Finding Images - Image Naming	Image names vary: (see diagram No. 2) Sometimes long alphanumeric codes. Sometimes titles. Sometimes short random strings (especially when added as Master Items). Although there’s an optional field for naming images under properties, these names don’t appear in the library, making identification harder.
Tracking Image Entity Deployment	The above error message is caused by an object has been deleted in a sheet.  But what object is that? In which sheet? There is probably no way I could find out, I would like to know if there is a method to do so. I thought to remove the entire Image entity at least get the preview working, then the next error pop up. Now, I have to first remove all instances first where I used this images in the template.  To find this out, the only way I know is to click on each object property and then click on Image Source to compare the image long id. So, is there a way we can see where all images are deployed in the reporting section or band or subband?
Trouble shooting – Vague Error Message	Error messages are vague and provide no clues about the root cause. For example: “Bad Request”  - what request? Patch ‘value’ – what is Patch value?  Why ‘value’ has this quotation ‘ ‘?. I ended up recreate the whole template after deleting all my objects and this message still popping up.
Troubleshooting – Error Message without much Context	When adding a KPI as an image, I sometimes get errors despite the KPI having valid data. Could conditional visibility be the issue? Possibly—but the error messages make troubleshooting extremely difficult, especially for new users.

[Daniele_Purrone]

Hi @_JFKDW_ ,

this is very valuable. What I recommend is that you suggest an idea for each of these challenges, so that they can go straight to the product management team.

[_JFKDW_]

The thing is all this shouldnt need anyone to say or propose to Qlik.  I always said Qlik Sense is a people tools that design by PEOPLE for PEOPLE, so easy to use and so good in many ways.  This reporting tool is the total opposite.  It's time consuming, the challenges here is not about how to use the tools, is the tool design logic are so unfriendly and so inhuman (yes, because it tortures people with small thing that can be taken care of by design easily - e.g. Object in app deleted but used in template - house keeping - instead of the tool delete all the object that no longer found for us, it has to keep thouse object in the image library.  There is no indication or what so ever to identify the object has been deleted, not even a ! sign next to the object)..  The tool is so chunky, so inefficient and so time consuming to use. In my view, this Qlik Reporting is only gonna bring down the goods wills Qlik Sense has built till date.   I'm sorry, but it's true.

[Lech_Miszkiewicz]

Hi @_JFKDW_ 

1. I agree with you on some points and on others to some extend. I also see that you made it little bit hard for yourself in your templates. I normally create objects for reporting and I include meaningful chart titles for reporting authoring purpose (such as: "Sheet xyz | Image 1"). You dont need to show those when image is used on sheet but they will appear when you add them in add-in and can be used to identify what object has been used and where.

2. Your point re-"Finding Images - Image Naming" - this is very simple. If you dont have chart title in Qlik Sense then Qlik Sense object Id is used instead. No matter if that object is master visualisation or not and as mentioned before if you are not showing titles in your report you can still populate them and toggle of "show titles" which will hide them from the view but actual title will be still used to identify object.  

3. Error troubleshooting - when using tool I would expect someone to go through training or existing tutorials. I agree that some errors are vague but on the other hand you need to make sure you are running supported configuration: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Reporting/Reporting-serv... . Here is an example of known limitations. I am not saying that your example was caused by known limitation but given that you said "Could conditional visibility be the issue" I would straight away say: a - Yes, b - KPI object does not have conditional visibility so are you talking about 3rd party KPI object or did you mean "Calculation condition"? or did you nest it in a container maybe? Each of those typically cause issues long term so I would just stick to simple solutions.

Other than above I dont have any other comments. I agree with you with the remaining points so lets see what Qlik will do regarding them and as @Daniele_Purrone mentioned we may as well suggest ideas as that is best way to provide feedback and do exactly what you said: that Qlik is peoples tool. 

cheers