MicroStrategy Filter setup Sample Size

OK how about defining 2 new metrics:

One with a filter condition handling all outliers, one with a filter condition handling all values within scale.

Then you can use both metrics in your report.

so you basically define two new metrics on the original metric with a custom filter respectively

With Thresholds you can only format the data which is outside a specific range. Is this example outside -100 and 100. But it's not an option to exclude the values from the report/view to be shown. I don't want to show them - but count them in any way.

As said use 2 metrics.

Hi Tolomir,

I've tried what you suggested. I've created two metrics:
1. One with filter for values within the range of -100 to 100
2. One with filter for values outside range of -100 to 100

Result: Report return no data.
Seems like the metrics exclude each other and nothing is displayed in the report.

I found something different where I thought it could work but is does not. I have only one attribute within my report and normally one metric. When defining a metric there is level and grouping information within the editor which you can set to absolute, ignore none for a certain attribute. In case I set the level to "absolute" for the attribute I use it does not calculate the unfiltered or not displayed value like it should. Within the tutorial they use two attributes where one is a child of the other. That's currently not what I have in my report. My attribute is "valueRange" for values between -1000 and 1000 e.g. and a metric which counts how many values are within each "valueRange bucket".

Could you test if one metric with a filter does work. I'm at a MicroStrategy course tomorrow anyway,maybe the teacher can help.

There's one report in the tutorial which is doing nearly what I want to do: Reports->MicroStrategy Platform Capabilities -> Advanced Metrics -> Level Metrics -> Report: Revenue by Geography

The difference to my report: Instead of 2 attributes I have 3 attributes in my report. Two I use as page-by, the other attribute as a column. The hierarchy is like in the Tutorial report: page-by attribute1 is parent of page-by attribute2 and attribute2 is parent of column attribute3. The current failures in my report: All columns are filled with the total value and the report filter is not applied to the view. I have two metrics: One should just apply the filter for attribute3 where the values are between -100 and 100 and the other one should ignore the filter and deliver a sum of attribute3 values between -1000 and 1000. The page by function should be applied as well. I'm working on it. Step by step I get closer but the result is still not ok.