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.
The Color Palette under Assets only applies to charts, but it’d be awesome if we could use it for font and text colors in NUX. It’s a bit tricky to remember or copy hex codes every time, and this would make pages so much easier to style and keep on-brand. A small change with a big visual impact!
While the Model Map functionality already exists in Anaplan, it becomes difficult to navigate when working with large models. I would like to see enhanced support for full export capabilities of the model schema (DISCO). This would greatly streamline documentation efforts and save time when capturing model status across…
I'd like to request implementing a formal notification system for upcoming platform changes and updates. This would be incredibly valuable for the Anaplan community for several reasons: Real Impact Example:Recently (Sept 2025), an unannounced Cloudworks change restricted .csv000 file imports. This resulted in: Failed…
