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
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: The Anaplan Color pallet should be consistent across all forms. Text Pallet is different Action Icon Default Colors, and different…
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: Currently a workflow ends if a decision task is rejected and it is not possible to add workflow steps after the rejection. I want to…
When a user clicks the ellipsis in a grid card they should be able to see the name of the source module. This empowers end users with the ability to connect to the source data they see in the UX to the module in the backend. It also enables end users to pull the data into Google Sheets or Excel.
