Export - Data Source

Hi Community,

I am thinking that would be very beneficial for model builders to have the possibility to view Data Sources for Export Definitions. For the large models with lots of external integrations and different export actions is pretty difficult to follow the source of a particular export if you can have dozens of saved view for one Module.

Found this topic from last year. Thought of bringing it back into discussion.

https://community.anaplan.com/t5/Idea-Exchange/Access-to-source-views-on-saved-exports/idi-p/37624

Comments

JaredDolich

Agree. I use the notes section for each action to document the source & saved view but that's not very reliable especially if someone forgets to update the notes when they change the source or view. Great suggestion!

Miran

Status changed to: In Review

alexpavel

There are also some similar discussions on this thread as well.

https://community.anaplan.com/t5/Idea-Exchange/Exports-linked-to-saved-view-and-user-selection/idc-p/46811#M2939

Unfortunately, currently, there is no way to understand with what filter definition was an export action created, even looking at the metatada of an export action using the API's.

Cheers

Alex

wquan

Agreed with this - it's especially useful when we are trying to debug what views we're using to export to our data warehouse or alternatively when we create extract buttons for the end user.

Documentation and naming convention of the export action always helps, but when documentation isn't updated it's always best to be able to see what the system is actually looking at to pull data from.

Gwen.pryor

Status changed to: In Review

azumbahlen

Agreed - many times I get emails from end-users asking where an exported excel file of a dashboard is available in Anaplan. This requires knowing the structure of every dashboard available or individually reviewing. If the export would include the dashboard name it would significantly cut down on navigation issues.

wwood

Great suggestion, more system generated documentation would make navigation simpler.

DavidHunter

I am very much in support of this idea. Currently troubleshooting an issue & the solve will impact downstream reporting. I can't see the original export definition, and the file is too large to export for re-creation:

Without knowing how this was set up many years ago, I'm stuck with trial and error and a high probability that our downstream reports are broken in the process.

Quick Links

New ideas

Anaplan Color Pallet
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…
Workflow: Continue Workflow after Decision Task Rejection
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…
Allow non-WSAs to view source module name in UX.
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.