Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Tool_Tip
Creator III
Creator III

Slowness issue

Dear all,

 

We have data as below : 

ID PRODUCT PRODUCT_CODE
1 MOBILE A1
1 MOBILE A2
2 WATCH P3
2 LAPTOP P4
3 LAPTOP L1

 

We are displaying data in straight table as below :

ID PRODUCT
1 MOBILE / MOBILE
2 WATCH / LAPTOP
3 LAPTOP

 

We are are able to achieve resulting table using below expression in table object by creating PRODUCT column by writing expression as below:

= Concat( PRODUCT, ' / ' )

 

But the issue is we have almost 90K ID and for all them this expression is taking so much time to load in the table object also we have seen hub also responding slow due to this. We need to know if there is any alternative for this or it is the bug. We are using later version November 2024 patch 5 Qliksense enterprise.

We are not doing anything in data model as we have other many more columns in table objects too.

Labels (1)
2 Replies
Chanty4u
MVP
MVP

Try to create that expression in script and use directly in table 

FinalData:

LOAD

    ID,

    Concat(DISTINCT PRODUCT, ' / ') AS PRODUCT

RESIDENT FACT

GROUP BY ID;

marcus_sommer

I don't think that there is a bug else it's a rather heavy computation to show a string-concatenation against 90 k of distinct dimension-values. Like already hinted you should consider to transfer this part into the data-model or maybe to do the entire job per script and storing the result as csv (because if no outsourcing of the data is wanted it wouldn't be necessary to run the logic against so many rows - else appropriate selections should reducing the response-times significantly).

If it should remain within the UI you might split the object into n objects and/or using specialized print/export objects (simplifying each sub-part). Further important would be to optimize the data-model (star-scheme) and the chart itself (no calculated dimension and/or aggr() and/or (nested) if-loops and/or interrecord-functions).