Super excited about User Subsets. However, we will need the ability to import into the user subset to make it useful. Another potential workaround would be the ability to use roles to auto populate the subset.
Agreed, getting role via formula, or a default property which shows roles by default, would be great along with populate subsets via import action. This would help us automate a lot of stuff.
@smeeki : You can already populate subsets with import actions.
Is this disabled for the new users list / subsets feature ?
Subsets in general would greatly benefit from being managed through formulas though !
Please consider upvoting the ideas around dynamic formulas subsets
@david.savarin - There is no import option in the new user list, so subsets can only maintained manually for now.
@Dikshant Whoa. That is disappointing to say the least :/
So users subsets management is for manual interventions from eworkspace admins only.
Cannot see how it can be used at enterprise level scale.
All the more reason to have the subsets managements with formulas feature
@david.savarin - Yep, agreed.
For short term, having an import option in list would make it scalable.
And for long term, it's better we have roles in the list property, where role comes up automatically, makes it fully automated.
Selective access via formula is cherry on top, but we can't expect too much, so above two things will do most of the work π
agreed, having to manually update user subsets is a frustrating limitation of this useful functionality. please do at the very least give us the ability to import into this subset
Do we have any progress/updates on this? The import option would really help with a peculiar use case we're having.
Giving users the ability to add subsets to users is useful for a variety of use cases, not giving the ability for developers to treat user subsets in the same manner as subsets for Anaplan lists to manage via import(s) is a big miss.
To maintain efficiency and performance, model builders must periodically remove unused or irrelevant line items. At present, the [Referenced By] column in the blueprint provides visibility into dependencies between line items. However, for line items that are not referenced by other calculations, builders must manuallyβ¦
When we use "Anaplan Extensions", we can check "Filters used in Pages" now. But we cannot check "Filters used in Saved Views" and "Filters used in Context Selector". We want to have a function that allows us to check "Filters used in Saved Views" and "Filters used in Context Selector" in "Anaplan Extensions".
When we access a model that belongs to a different Tenant that the one we are currently viewing, the Tenant does not switch automatically. Example: Tenant A: Model 1 Tenant B: Model 2 β We view Model 1 (Tenant A) β‘ We try to access Model 2 (Tenant B) β Tenant does not switch automatically
