It would be nice to setup Anaplan Connect Scripts using Process/Action IDs vs. the name in case naming convention needs to be changed.
Hi @mooreta,
This is supported by Anaplan Connect since (at least) 1.4.4, so few years ago. Process, action, export, import, file, workspace, model - any of them can be specified either by name or ID. And as you pointed out, in most cases it's usually better to use IDs, as it will be persistent and later change of name won't impact the execution of the script.
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…
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…
I would like to pre setup input Booleans by default to true in the blueprint view //GP
