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.
Current behavior: When the Multi-Select Members option is enabled in the slicer settings, the user’s previous selections are not saved when reopening the workbook. As a result, users must reselect the slicer members each time they open the workbook. However, when the Multi-Select Members option is disabled, the previously…
In the current Anaplan UX, there is no native heatmap visualization option within pages built on spoke models. Users must rely on conditional formatting in grids, which: Is limited in visual flexibility Is not intuitive for business users Does not scale well across multiple dimensions Requires manual setup in each module…
Problem Description: When a dependent line item used to filter a dropdown is deleted or has its format changed , Anaplan's underlying dependency link for the filtered dropdown can become stale. While the UI might show a newly created line item with the same list format as the dependency, the filter itself remains…
