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 was trying to identify which models consume our Data Hub as a source in a model-to-model setup. Anaplan supports using one model as a central Data Hub for multiple target models, but the visibility I found is mainly target-side, not source-side.
Today, the workaround is to go into each spoke model and check Source Models / Import Data Sources / Actions one by one. I also found a community answer saying they were not aware of a direct report or process to see this from the Data Hub side.
This makes impact analysis, cleanup, troubleshooting, and governance harder than it should be.
How often is this impacting your users?
Whenever we need to change, clean up, remap, or troubleshoot Data Hub integrations across multiple models.
Who is this impacting?
- Workspace admins
- Model builders
- Solution architects
- Integration teams
- Support teams
What would your ideal solution be? How would it add value to your current experience?
A source-side dependency / lineage view for model-to-model imports.
From a Data Hub, I want to see:
- all target models using it (at the very least, basic view)
- which saved views/modules/lists they consume
- which import/process uses them
- last run / status
- exportable results
This would make impact analysis, support, cleanup, and governance much easier. The existing Source Models information already exposes some relationship metadata, so extending that into a reverse-lineage view would be a logical improvement.
