users dimension for filtering

BlessyDube

In my model user dimension is used across the model for filtering so that the users do not overlap their data. If my understanding is correct this is the standard practice. I searched community for best practices related to usage of users dimension i could not find anything. So my question is i have a model which is almost 120gb with a clean users list only the active users are in. And in the UX page there are multiple filters used so for that in the model the filter line items have users as a dimension. In this scenario is there some best practices that can be done in the model for better size optimization or is it mandatory that where filters are there users dimension mandatorily needs to be included and there is no way out.

AjayM

Hi @BlessyDube ,

A couple of suggestions with user dimensioned filtering:

1. Assess where you really need user dimension and where you don't. You might be able to define filtering in a central module and apply it to the module where 'users' is not a dimension. It still respects the user based filtering
2. As already covered in above point, prefer to centralise the filtering logic, similar to sys modules, since certain filtering rules could be used across multiple modules/pages
3. Revisit UX requirement, and check if certain UX pages are role specific or smaller user base specific, so that you can leverage user subsets. Consider subset maintenance as additional admin step in this case
4. Besides model size, considering model performance, please avoid unnecessary dimensionality and unnecessary repeatability of filtering logic as much as possible
5. Wherever possible, maintain fewer number of filtering conditions on each of rows/columns on UX, rather than splitting the code into multiple filters

Cheers!