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.
Backgrounds We have a question regarding Logs > Session Log. Currently, system activity logs are only available for a limited number of functions, such as Journal operations and metadata updates. As a result, some system administrators on the customer side have found the current audit capabilities insufficient and have…
To maintain efficiency and performance, model builders must periodically remove unused or irrelevant line items. At present, the [Referenced By] column in the blueprint provides visibility into dependencies between line items. However, for line items that are not referenced by other calculations, builders must manually…
When we use "Anaplan Extensions", we can check "Filters used in Pages" now. But we cannot check "Filters used in Saved Views" and "Filters used in Context Selector". We want to have a function that allows us to check "Filters used in Saved Views" and "Filters used in Context Selector" in "Anaplan Extensions".
