SPM - Filter performance

[Former Member]

Hello,

Does anyone have suggestions to improve the filter performance? As soon as we click on Filter on any dimension, it first lists 1000 entries before we can type-in and search. Depending on system, it takes a while to get the first 1000 entries.

Is there anyway to change this - like it should not show the first 100 entries but allows us to manually enter a search value immediately after we open the filter? This would be a big advantage for end users to filter.

Regards,

Prasanna

[Former Member]

Hi Prasanna,

The queries are configured to read posted values in the infoprovider. So therefore it will read all of the contents of your cubes before returning the list. You can change the option to read master data values directly from the master data table, but the risk here is that if your master data quality isnt so good, then users may be faced with a bewildering quantity of meaningless values.

As a work around you can create mini aggregates for some of your heaviest dimensions, that are basically tiny cubes with 1 key figure. That way when posted values are read, only the aggregate is hit.

As for stopping it reading the first 1000 this isn't a configurable option.

Thanks

Neil

[Former Member]

What dimension are you filtering on? How many values does it the dimension have in the backend?