Let’s first take a simple example of setting up end user-specific filters within Anaplan. During setup of end user-specific filters for reports, both the filter selection module and the module with filter check will be dimensioned by the Users list as shown below
用户列表不需要将必须过滤的报告/必须过滤的模块,因为过滤器将查看当前用户。
Since the user selection modules and the filter modules do not normally house a lot of dimensions or logic, the size impact of adding the full user list is less, and most of the time unavoidable, as most of the users will be viewing the report. 但是,在某些方案中(例如差异报告与用户选择要由有限数量的用户使用)非常突出。但是,Anaplan并不能使您能够创建用户列表的子集。这样做的解决方法是创建自己的清单。 让我们以版本之间的差异报告为例。我创建了一个自定义版本列表,并使用了一个订单项子集来创建一个报告模块,该模块显示了用户选择的两个版本(版本A和版本B)之间的差异。当您必须执行“计算计算”时,订单项子集很方便。简而言之,如果您必须在订单项上执行其他计算,例如在差异报告或货币转换的情况下,使用订单项子集管理比进入复杂公式更容易管理。有关行项目子集的更多信息,请参阅订单项目脱颖而出。 I went with a custom version list as it can be given as a dropdown for user selection, as shown below.
The first module is a user selection module given for the users to select the version of their choice for comparison, dimensioned by the user subset list and line items formatted by the custom version list (“Planning Versions”). 由于订单项子集用于构建方差报告,因此使用Collect()函数来构建基本报告中间分阶段模块。
The final variance reporting module makes use of the intermediate module and looks up the version selected by the user to build the variance report For such a report where multiple users can change the selection, we would have to dimension both the selection and the report module by users for proper functioning.
When the report module is already having quite a few line items and major lists as dimensions, the additional Users list will have a big impact on the cell count. If the report is to be used by a limited number of users, then the space occupied by adding the rest of the users into the report is, in effect, sparsity. 在这些情况下,一种方法是在Anaplan中创建单独的用户列表,并启用了选择性访问。
Each user will be given write access to their own ID/name, and we would be able to use this list as a“自定义用户子集。”
The content in this article has not been evaluated for all Anaplan implementations and may not be recommended for your specific situation. 在应用本文中的任何想法或步骤之前,请咨询您的内部管理员。
Nice approach. Unfortunately it puts a serious limitation on the model: selective access can be given only用户的ID /名称自定义的用户名列表中。如果纬度er some other task requires to provide user with Read selective access to someone else in Custom Users List (for example, users from one department need to see each others scenarios) - this would not be possible. So you'll need to keep this in mind while making choice between sparsity reduction and limitation of Custom Users List applicability.