I'd like the ability to allow users to fill out a Form in the new UX and create a code for the new item (automatically) based on the inputs - as well as flag the inputs as not possible if the item has been created before.
I agree, this would be good.I'm just building a module now for personnel planning where user can add new employees to the list. Since names can be same, we're using numbered lists. I don't want to have to ask the unit to input next available code, nor do I want to maintain the code list for them.
For now, I made different modules to return the next available code, but to get it to the new list item is still manually done.
Regards
Kinga
Business Problem & Current Limitation Current State: In our current Polaris implementation, the cumulative dimension index across just five core business dimensions has reached 55. The Constraint: With a hard ceiling at 64, this leaves a headroom of only 9 remaining indexes across the entire workspace/model scope. Direct…
Dear all, Some times your system refuses us to log in. It seems it is because the password is no longer valid and has to be renewed. However absolutely no information is given to the user. Therefore he/she tries to connect again and again, until he/she thinks "oh, that should be the password that has expired". This is…
I've come across this need more than once now so I figured I'd post it here for the Anaplan product team! We have a client who utilizes a primary hierarchy for a core list but developed the need to see the lowest level in that primary hierarchy rolling up to an alternate hierarchy of parent list members. In their Polaris…
