Save and Run vs Save As

a10hall
Member
Bad idea to change the Save options in the ETL. I've been shooting down to the bottom option "Save and Run" for years. I've already duplicated multiple datasets working fast, have to back track, delete the duplicates, and update the actual ETL.
Tagged:
5
Comments
-
Oh no! I hate it when a product updates and your muscle memory for how the product used to be is causing problems in your workflow. Based on your feedback, we're talking through ways to make the change less impactful and hopefully prevent the duplicates that you're experiencing. Thanks for taking the time to provide that feedback for us.
Domo Product Manager for Data Transformation (MagicETL)
0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 305 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 107 SQL DataFlows
- 648 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 774 Beast Mode
- 75 App Studio
- 43 Variables
- 733 Automate
- 186 Apps
- 471 APIs & Domo Developer
- 62 Workflows
- 14 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 403 Distribute
- 117 Domo Everywhere
- 277 Scheduled Reports
- 9 Software Integrations
- 137 Manage
- 134 Governance & Security
- 8 Domo Community Gallery
- 44 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive