Publishing app studio app and dashboard with same dataset creates duplicate datasets in subscriber

Since you can only choose either app studio app or a dashboard to be published they can't be in the same publish job. This means that even if there is only one dataset is powering both the app studio app and the dashboard, duplicate datasets are made in the subscriber after publishing. It gets even more complicated if you have more publish jobs being powered by the same dataset. Causing chaos and confusion for the end user (a little dramatic, but true).
It would be great if we could have both dashboards and app studio apps in one publish job.
Or even better… if multiple publish jobs could recognize the datasets being used in other jobs and you have the choice whether to link them in the subscriber (so they're the same ID) or create a new dataset.
Comments
-
@user088745 - You'll be glad to know we are planning to address this in 2025, the "multi-asset type" way specifically. However the point you make about multiple jobs recognizing that there is already the dataset in another job is also a good point - will likely look to pick that up as part of the effort too.
Thanks!Cadell Falconer
Principal Product Manager0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 307 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 112 SQL DataFlows
- 649 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 790 Beast Mode
- 78 App Studio
- 43 Variables
- 745 Automate
- 187 Apps
- 475 APIs & Domo Developer
- 67 Workflows
- 16 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 406 Distribute
- 117 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 139 Manage
- 136 Governance & Security
- 8 Domo Community Gallery
- 47 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive