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.
The created XLSX file contains an index of template report names that quick link to the related report tab. Since templates may be used to create multiple different reports based on passthrough parameters, I believe it makes more sense for the index to reference the Description given in the report book rather than the Name.
In multiple Anaplan implementations across FP&A, S&OP, and operational planning use cases, a recurring design challenge is the overuse of hierarchical lists with Top Levels, especially on large transactional or operational lists. In many projects, hierarchies are introduced early with the intention of providing “future…
Phenomenon: When the page is opened after launching the browser, FY25 is selected in the selector, but the year displayed in the grid is FY24. Current Workaround and Impact: The grid will display FY25 if the user first changes the selector in the page header to FY24, and then changes it back to FY25. Currently, end-users…
