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:
It would be helpful to be able to pull the information from the Imports and Import Data Sources tabs within actions via API. It would be important to include IDs for workspace, model, files, modules, lists, saved views, etc. It could be used to then quickly identify what modules/, saved views, lists, etc. from a source model are used in the downstream model
How often is this impacting your users?
Regularly when trying to identify the saved view/ module/ list in a source model with certainty. Best practices and standard naming conventions should limit this issue, but they still do come up.
Most notably, during model cleanup it can be difficult to identify lists, saved views, or modules that are no longer used in downstream models.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
model builders, solution architects, and integration team.
What would your ideal solution be? How would it add value to your current experience?
Ideally a new transactional API call would be available to return this information. An alternative would be to include the IDs in the Import and the Import Data Sources table by default with an option to export the information within the model.
Please include any images to help illustrate your experience.
API call to pull the information from imports and import data sources tabs
