I need some help understanding what I've done and hopefully some direction on a better way.
I have a straight table with a drill down group as the dimension. The fields in the drill down are Country - Segment - Business Name. (In our CRM, Segment is equivalent to Territory) I need to count the covered business and used:
to count businesses with a Segment assigned. It works like a charm until I drill down to the actual segment. At that point, it doesn't filter to the actual segment. So, If I filter to Australia - 'Australia Segment 1', all of the Australia businesses are still returned in the table. (Instead of only Austrailia Segment 1, I get all segmented businesses in Australia)
everything works as expected and I only get business from the segment that I've filtered to.
I guess my question is with the {"**"} ... I thought that meant count [Business.Key] if it has a segment. But I expected that it would still filter without the intersection set analysis. Any help would be much appreciated!
The default behaviour with Set Analysis is that you provide a selection to override the selection that is made in the UI. This can be really useful - but can lead to results that can be counter intuitive to users. By using the intersection code (*=) you don't override the selections made by the user - you further limit what they have selected to what the Set Analysis dictates. Generally this is a much better thing to be doing.
*= is a not particularly well documented feature of Set Analysis - but it is often the most useful way of doing things. Unfortunately, syntax highlighting is not properly aware of the syntax - and often highlights expressions in red when you try to use it.
The default behaviour with Set Analysis is that you provide a selection to override the selection that is made in the UI. This can be really useful - but can lead to results that can be counter intuitive to users. By using the intersection code (*=) you don't override the selections made by the user - you further limit what they have selected to what the Set Analysis dictates. Generally this is a much better thing to be doing.
*= is a not particularly well documented feature of Set Analysis - but it is often the most useful way of doing things. Unfortunately, syntax highlighting is not properly aware of the syntax - and often highlights expressions in red when you try to use it.
It is indeed, except you should only need the one *. If this is a field you use for selections a lot you might want to consider replacing the nulls out in the load script, eg:
if(isnull([Segment.Name]), 'No Segment', [Segment.Name]) as [Segment.Name],
That means you can code for it and select it (or exclude it) more easily.
