Recursive ETL issue - JOIN
Hello,
I am having trouble with a recursive ETL. When I update my data set "Record Status", the rows are not appending, the duplicates are not replaced and the card data doubles. I believe the error is related to my join but I cannot pin point the issue. I have read many support articles pertaining to recursive ETL's which have not solved my issue. I am hoping that someone can review my case and point me in the right direction.
Please see the enclosed image for a better understanding of my current ETL.
Thank you,
Comments
-
Hi @user066906 ,
It's likely not your join. With the changes in Magic ETL 2.0 NULLs are handled differently than in ETL 1.0. With 2.0 they are now handled the same way as SQL, as a special value.
ETL 1.0: NULL <> 'Delete' = TRUE
ETL 2.0: NULL <> 'Delete' = FALSE
This is because you must use an explicit NULL check instead of <> 'Delete'.
So on your filter tile, instead of saying <> 'Delete' change it to be 'IS NULL' instead of 'Not equal to'
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 302 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 104 SQL DataFlows
- 633 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 760 Beast Mode
- 62 App Studio
- 42 Variables
- 699 Automate
- 181 Apps
- 457 APIs & Domo Developer
- 51 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 401 Distribute
- 116 Domo Everywhere
- 277 Scheduled Reports
- 8 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 111 Community Announcements
- 4.8K Archive