Suggest an Idea

[Andrea_Bertazzo]

In Qlik Sense and in SaaS it is possible to create two or more Master Measures with the same name. Sense does no show any errors or warning but, if you use that Measure name in a formula, you get a generic error in the formula editor and incorrect results. This happens because Sense cannot understand what of the Master Measure to use.

I would suggest to introduce a warning that prevents the use of Master Measures with the same name.

[deasy_sn]

Is it possible to have a priority when we use [Measure Name] in the expression also?

Example, if there is a [Measure Name] it will checked first the chart/table, so this will be the first priority.

If there is no same name in chart/table then it will search and use the master Item.

[millerhm]

Turns out this is also a problem if you have a field and Master Item with the same name, so this feels a bit more like a bug/missed scenario rather than an idea. Given the features of Master Items, i.e., assigning colors, labels, formatting, etc, there are definitely going to be duplicates between fields and Master Items (i.e., replicate the existing field as a MI to gain the additional features). The issue here is slightly different but with a similar result where it seems to be that the Master Item starts to refer to itself as it interprets the field in the MI definition as a MI and creates a circular reference.

[deasy_sn]

Hi,

Yes, it's effecting all expression including the color formatting. All color using the field Name (measure label in chart/table) all not working properly. 

Creating master item for all formula also not a very good solution as most of the measure expression is based on KPI  of the dashboard and might not the same between the sheets but it might have the same measure label/column name, example: CY and LY and %Growth.  Where this is very common in every sheet but the formula inside might be differ between the sheet as it's depend on the KPI of the sheet presentation.

[Patric_Nordstrom]

Thank you all for your feedback on ways to improve our product. While this is something we understand would be useful, it's not on the short-term roadmap. Please continue to show your support for this idea by commenting and liking.

Thanks, 

Patric

[Digvijay_Singh]

I feel its a bug and should be handled differently and promptly.

[philipdoyne]

Isnt this very simple?  :

- I cannot see any good reason for two master items having the same name (very bad idea!)

- I cannot see any good reason for a master item having the same name as a field (also very bad idea!)

@Patrik:    Can you not just add some validation to stop these situations when a master item is being  being created in the future - if people have already done it that can stay and they can fix it as required so this change would not stop anything working in the way it did before the addition of the validation (and of course would not fix the problems seen above which will require the names to be changed).

Philip

[mgranillo]

Each master item needs a unique identifier to call it correctly in an expression. How is this not a bug?

[RoryMcHugh-Catalyst]

This bug tripped me up the other day, when I inadvertently added a master measure with the same name as a dimension. It took me a while to understand why my charts were broken.

This should be prevented from happening with a validation check, as suggested above.

[MartW]

can there be a general warning/pop-up that if a masteritem got the same name (capitals and all) as a field, because that will be very helpful

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.