Magic ETL Conditional Column
Hello,
I am brand new to Domo and looking for the equivalent data transformation in Power BI that is called "Add Conditional Column" which basically allows you to write a case statement based on values in existing columns in your data set. Ex. If [Sales Rep] = "Dan" and [Order Type] = "1" then "Exclude" else "Include".
Is there a way to achieve this without filtering, adding a constant, then appending that back to the data set? (this was how a co-worker instructed me)
Or would this be a situation where just writing it in SQL would be better?
Thank you!
RS
Best Answer
-
@remember_Sagan Your co-worker was right on the filter/constant for Magic ETL. But being better than SQL is hard to say. I say that because yes it may be more complex to set up this situation in MagicETL, but the performance of the execution of this ETL will most likely always be much better than whatever you did in SQL. This may not apply so you'd have to decide that, but if you went from 1k rows of data to 1M rows of data in SQL, you're most likely going to tell a difference in the execution of that SQL statement, but you would probably never notice it in Magic ETL.
Hope that helps.
Matt
1
Answers
-
@remember_Sagan Your co-worker was right on the filter/constant for Magic ETL. But being better than SQL is hard to say. I say that because yes it may be more complex to set up this situation in MagicETL, but the performance of the execution of this ETL will most likely always be much better than whatever you did in SQL. This may not apply so you'd have to decide that, but if you went from 1k rows of data to 1M rows of data in SQL, you're most likely going to tell a difference in the execution of that SQL statement, but you would probably never notice it in Magic ETL.
Hope that helps.
Matt
1 -
I am more comfortable using MySQL, so I agree with your statement that I think this is easier using a MySQL dataflow
SELECT
CASE WHEN `Sales Rep`='Dan' AND `Order Type`='1' THEN 'Exclude' ELSE 'Include' END AS `Conditional Column`However, if the dataflow is already built in ETL, then I would recommend just using three steps mentioned.
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 295 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 608 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 710 Beast Mode
- 49 App Studio
- 39 Variables
- 667 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 44 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 115 Manage
- 112 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive