Systematic Updating of View Name/ID used in Import

This may be obvious to others, but I have found that when I rename a view in a source model, it breaks the Import in the destination. Unlike lists/modules do views not have corresponding IDs to represent them? I think most if not all elements in Anaplan should be linked by a unique identifier that should not be broken when something is renamed.

My idea is then to make sure views have corresponding IDs that do not break when their name is changed/updated.

Comments

david.savarin

Agreed, but isnt it more like a bug to fix rather than a feature ?

This is one of the few things that makes anaplan integration features weak (like easily breakable and prone to generate regressions) while they are completely key to the whole experience

I can confirm btw that saved views have their own ids so changing the name shouldnt break the underlying actions.

Quick Links

New ideas

Default Show Scroll Bars
Description Currently, scroll bars in Anaplan UX grids and cards only appear when content exceeds the visible area and when you hover over a card and the scroll bars appear. While this behavior is standard, it can create usability challenges for end users, especially when: Users are unsure if additional data exists beyond…
Read/write security rights simplification for AnaplanXL
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: I have a small improvement request for assigning security rights to different security groups in AnaplanXL - it makes sense having…
Default value for Booleans or other types
I would like to pre setup input Booleans by default to true in the blueprint view //GP