Qlik Community

Ask a Question

Suggest an Idea

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
Join us at the Cloud Data and Analytics Tour! REGISTER TODAY

Data Selections should surface Master Dimension Names

AndrewMcIlwrick
Luminary Alumni
Luminary Alumni

Data Selections should surface Master Dimension Names

The data selections that appear in the selections bar are those of the underlying field-level data model.

However a business analyst may often not always have the time ( whether via Data Manager or Script Editor ) to alias poorly named fields, often inherited from database tables or spreadsheet cell headers.

It is frustrating that when time is taken to create a library of master dimensions, and they are used in filter panes, the selection still surfaces the field names. It is even worse if the field names have been qualified ( manually or using qualify * ).

Can the selections bar be improved so that if a master dimension value is selected it is that which is shown ?

The same behaviour is exhibited in the selections tool - where the default list of only master dimensions results in a selected value of the field.

mcilwricka_0-1605002754733.png

 

10 Comments
AndrewMcIlwrick
Luminary Alumni
Luminary Alumni

Thanks for the like votes. I should have also added .... my hope is that this can be implement as a visual UI change with no requirements to modify associative engine behaviour !

Basically, in the selections bar and tool, identify if a master dimension was used to select 1+ of fields values. If so show its title rather than the field name. Else show field name as is done now.

BillyBirdIBT
Partner
Partner

Seems so obvious, an oversight that needs addressing.

pablolabbe
Luminary Alumni
Luminary Alumni

On more recent versions, creating a a calculated dimensions as master items, creates a field on the fly in memory and the field name show in the data selection panel is the name of the master item , not the expression. Not sure if forcing a calulated dimension could be a workaround, but it could have a potential side effect on performance and memory consumption. 

Meghann_MacDonald

I find this a lot. In drill downs as well I think.

pablolabbe
Luminary Alumni
Luminary Alumni

Yes, in drill downs is the same behavior.

Carl_Hunter
Luminary Alumni
Luminary Alumni

This is a great idea. It's confusing to see the data model name when using master dimensions

There are a few issues with this... 

1) You can have multiple master dimensions for the same column from the data model.

2) You can also have multiple master dimensions with the same name.

This would need some careful thought

AndrewMcIlwrick
Luminary Alumni
Luminary Alumni

Carl - my thoughts that this could just be a simple UI change rather than anything for the underlying data model / associations.

Patric_Nordstrom
Employee
Employee

Master dimensions are trickier than they first appear to be. In order to get a proper name and avoid formulas in the selection bar here some suggestions:

1. Put the dimension in the load script, that is always performs better.

Or.

1. Create master dimension.

For master dimensions Qlik Sense uses Fields-on-the-fly or Calculated dimensions depending on the complexity on the expression:

  • Fields-on-the-fly : master dimension name is used in the selection bar.
  • Calculated fields : underlying fields in the selection bar.


2. Meet Fields-on-the-fly requirements

  • The expression must be based on one single field only, or on multiple non-key fields from the same table in the data model
  • The expression cannot depend on the selection state, e.g. through the GetSelectedCount() function
  • The expression cannot contain an Aggr() function
  • Must be a calculation, simply =CategoryName is not, write at least =trim(CategoryName)


3. Don't have several master dimension with the same expression. Sense picks the first.

But "Put as much as possible in the script. In most cases, it is far better to have these calculations pre-made, so that they do not have to be calculated at run-time, i.e. when the user clicks."

More details on Calculated fields and Fields-on-the-fly in HICs post:
https://community.qlik.com/t5/Qlik-Design-Blog/Calculated-Fields/ba-p/1694383

For an example of the above see the sheet "Avoid formulas in selection bar"

https://community.qlik.com/t5/Qlik-Sense-Documents/Top-10-Viz-tips-2020-part-IV/ta-p/1769697

Thanks,
Patric

Status changed to: Open - Collecting Feedback
AndrewMcIlwrick
Luminary Alumni
Luminary Alumni

Thanks Patric I agree with many of your suggestions but in my opinion they are focused at the more experienced user. For a business analyst using only the Data Manager to often load data from sources that they have no control over, the scripting option is a non-starter.

Aside from more votes, hopefully others will be able to add implementation ideas.

simonaubert
Partner
Partner

Hello,
Some feedbacks :
1/ like stated by @Patric_Nordstrom , the best practice is to calculate most things in the script. It's also faster.
2/ However, the issue I had is the field in my data model has technical name and I want a business friendly name to appear everywhere on the front application.
Example :

item_id in database/etl/qlik script, specifications, etc...
Item Id as a master item

But when I filter on Item Id, it's item_id that appears in the filter panel, which is quite ugly and confusing.

@AndrewMcIlwrickCan you please change the title to clarify the idea? It's a really good and it deserves more vote.

Best regards,

Simon