Switch from Context Selector to Boolean - Scope of view
I'm trying to optimize a module for space.
At current the module alone occupies 33 GB of space.
The module is a cross dimension of 4 lists as seen in the picture above. with time month granularity.
The idea is to reduce the dimension count to 3 by removing one list.
The 9LE List shown in the applies to above. It has two members cases & 9 Litre equivalent. Both are essentially a reporting metric unit.
To give some context all the calculation in the formula happens in terms of case units and to convert it into 9 litre equivalent the case value is multiplied by a factor depending on the product.
A line item formula from this module for example:
This is the current ux page setup.
The idea is to remove the 9LE list. by introducing a boolean selection and IF ELSE clause as a work around in the formula.
The boolean when ticked shows value in 9LE if unchecked shows Cases
so formula would change something to :
If Boolean = true then <the formula>* Conversion factor[LOOKUP:9LE] else <theformula>[LOOKUP:Cases]
This would actually eliminate the need of 9LE dimension from this module reducing the module size to half since the cell count reduces to half.
However the problem with this is since the change happens in the formula depending on the if condition the change in values is global and it would not allow parallel users to see values they wish. In the use of context selector the scope of values displayed are local I guess.
This particiular page will have multiple users at a given time. Is there a way to achieve this by giving individual users their view of choice either cases or 9le without affecting the view of another user.
Just to note use of user dimension will not work as it would defeat the purpose of this change which is space saving. User dimension would further **** up the module size.
Thoughts and solutions appreciated :)
Answers
-
Hi, @Yehya123 .
I do not think there is another solution for this concern, unless the Boolean line item replaces a more layered list within 9le. Not sure if you already did this, but in terms of optimization, if the conversion is preferred as one time change across all periods in the reporting, setting the period / Model Calendar to "Not Applicable" saves space.
For individual user preference is also considered, that is more volume.
Hope this helps.
0 -
Identify how many users are supposed to use the report. Try using user subsets?
However the problem with this is since the change happens in the formula depending on the if condition the change in values is global and it would not allow parallel users to see values they wish. In the use of context selector the scope of values displayed are local I guess.In order to achieve this, we need to have user dimension. Since our main focus is to reduce the cell count so the module size is relatively lesser. Try to reduce members of 3 dimensions or using user subsets.
0
