Would like to see additional enhancements to the API, things like retrieving line item blueprints, list/module editing, list properties, etc.
This would enable customers to control their Anaplan environments with various automations.
I agree that this would be a nice API enhancement, however, as a workaround, General Lists, Line Items, and Modules can all be exported via Actions and then those actions can be called from the API. This needs to be setup model-by-model initially, but then can be automated/scheduled to harvest the metadata once the actions are in place.
Hi @ablack / @EarlC - We have launched a whole new set of REST APIs (Transactional APIs) over the last 2 years for similar use cases. I would like your feedback on the Transactional APIs, fitment to your use cases and need for additional APIs or enhancements to existing ones. Please type here or email me at chanaveer.kadapatti@anaplan.com.
Thanks,
Chanaveer Kadapatti
Principal Product Manager - Anaplan
Anaplan currently provides the ability to create versions via an Import action, and update Version settings via an Import action. Ability to use an action (of any type, Import or otherwise) to do the following: - Rename Versions - Delete Versions Business Need: As we seek to continuously improve our planning process…
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: When presenting visualizations in Anaplan, users often try to hover over lines/bars/points in the chart with their cursor to point…
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…
