Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have a measure created as so
Sum({<SALES_UNIT_MEAS = {'l'}>} INVOICED_QTY)
it calculates the values correctly, but if I filter the SALES_UNIT_MEAS on a different unit of measure that is not l, the values remain static in the table. it should turn blank and say "undefined values". it does i have several copies of the same app and it seems to work on one copy but not others.
why is it not filtering down when others criteria are selected?
Hi, the value used in set analysis will overwrite selections on that fields. If some chart is working diferently it should have something different.
To apply slection to that field it should be something as:
Sum({<SALES_UNIT_MEAS *= {'l'}>} INVOICED_QTY)
Or maybe it's using altern states in some ways, or fields are renamed, or something, but the bahaviour described in your initial post is the expected behaviour.
the expression seems working as intended. there shouldnt be any effect on the summation when other values are selected from SALES_UNIT_MEAS. could you share a picture of the selections your making in other copies and theri expressions? if possible, share some same data.
it's from the same table, just a different field selection basically for different units of measure for different regions.
but you can see how it fails where I pick a Unit of Measure that is neither Liters nor Each and the table does not remove them
If I do something similar in a different version of the app, I get a blank chart which is the intent
i cant really say anything just by looking the pictures, try copying the object thats good from the app to another and see how it behaves.
Hi, the value used in set analysis will overwrite selections on that fields. If some chart is working diferently it should have something different.
To apply slection to that field it should be something as:
Sum({<SALES_UNIT_MEAS *= {'l'}>} INVOICED_QTY)
Or maybe it's using altern states in some ways, or fields are renamed, or something, but the bahaviour described in your initial post is the expected behaviour.
that was it thank you!
I think I had that previously somewhere but when I came back to it I was asking myself why that * was there and probably removed it...
I'm still not sure what that syntax means or does but it seems to be working how I want.
The * in set analysis is the operator for intersections, if 'I' is not in the selections the result would be an empty set.
Superb !!! Neat Solution.