End users have to populate Code manually when using Form. This can generate manual errors.
It would be very helpful if we can generate codes automatically based on name or other properties of the list.
This would be incredibly useful. The ability to add a form to a process would allow even more flexibility here.
Exception handling - where the user is permitted to enter a code, but where the requested code is already taken - would also be incredibly useful (link below).
https://community.anaplan.com/t5/Idea-Exchange/NUX-Forms-Exception-handling-when-duplicate-code-entered/idi-p/115271
There's no warning to tell the user there's a potential issue, then on "create" the model is timed out for n seconds/minutes, and when the error had processed, the error doesn't give an appropriate response (i.e. "you ave attempted to create a line item with a code that already exists").
Forms are a fantastic new release, the above mentioned would help take them to the next level.
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…
