Difference between filter and slice in selectors

Hello there!

Today let’s talk about the difference between Filter and Slice when filtering in documents.

You can see the option to in Selector tab in Properties of the selector.


If you check Apply selection as filter all targets are going to be filtered using Filter, if you uncheck, all targets will use Slice.

You can also click on “Manual Targets” button and choose for each target, which kind of filter use.



Let’s keep it simple. If you select Slice, the aggregation is made when opening the document. If you select Filter, the aggregation is made when you change the filter. So…

When using Slice:

1. You have everything preprocessed and you won’t have delays when changing an element in a selector;

2. Your document runs slower than using Filter, because it creates all aggregations when the document is been processed. It stores all the content within the document, so it doesn’t need to create new aggregations when changing the selector element.

3. The aggregation is made using all the attributes of the source dataset instead of the attributes included in the grid/graph. So, if you have Region, Year and Cost in source dataset and in your grid you only have Region and Cost, MicroStrategy will aggregate it using Region, Year and Cost.

Here is an example:

Using Slice:


As you can see, I have Year and Cost in Grid and Region in the selector. MicroStrategy will not summarize all Regions by Year, it will repeat the years for every Region selected, because as I told before, the aggregation uses Region and Year. Think that you have an invisible Region in the grid template.

Using Filter:


Here MicroStrategy will aggregate the Cost metric only using Year and filter using Region. So, you will see a sum of all Regions by Year.


4. It’s good for caching and exporting. Because all data is included in your document. So, if you export a document in Flash, you will be able to change the selector without receiving an error message.

When using Filter:

1. Your document runs much faster because it only aggregates the data using the selected elements in the selectors. But, every time that you change a single element in a selector, MicroStrategy has to aggregate the data at runtime, so it can delay much more time to change element than using slice, that is already aggregated and runs instantly*;

2.  The size of your exported document is lighter than using slice, but it only stores data of the selected elements of the selectors;

3. It aggregates using the attributes of your grid/graph. So, if you have Region, Year and Cost in the source dataset and create a grid with Year and Cost, it will summarize Cost only by Year, as the image above shows;

4. It’s not so good for caching and exporting.  If you export to a Flash file, you won’t be able to change the selectors elements;


That’s it.

Hope it heps.


God bless you!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.