I have been reading up on this and noticed that I in fact do NOT have the Upsert column enabled therefore according to the document I need to contact customer support. My question is, will I need to do this for every single current dataset and all future ones as well? Or is this a "flip the switch" kind of deal and it will be available for all?
In workbench you define the upsert key in the job configuration. Are you wanting to enable upsert on a dataset which has duplicate upsert keys already? Each new job would need to have the upsert key defined as each dataset would have different keys.**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0
No I don't even see the Upsert column in the job configuration in the schema tab to be able to select my key. In the documentation it states that if it is not there to contact CS but my concern is will I need to do this every single time I create a new dataset0
yes, you do have to contact support / your CSM to have upsert available as a feature in your instance.
by default the feature is not 'turned on.'
once enabled, you configure upsert on a case by case basis.
by default datasets are set up as REPLACE when you run a connector.
UPSERT is a variation of APPEND.
might sound tedious, but if you can imagine, domo has no way of knowing what the unique row identifier for a dataset is.
also, unless your dataset is in the hundreds of millions of rows, it typically doesn't make sense to use UPSERT. UPSERT just like normal SQL does not support soft delete, so if there's a chance that rows of data are deleted from your dataset, you'd have to make a second manual process to remove the deleted rows. (upsert by definition can only insert or update).Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1
- 7.6K All Categories
- 913 Connectors
- 241 Workbench
- 470 Transform
- 1.8K Magic ETL
- 60 SQL DataFlows
- 445 Datasets
- 24 Visualize
- 194 Beast Mode
- 2K Charting
- 6 Variables
- 14 Cards, Dashboards, Stories
- 1 Automate
- 348 APIs & Domo Developer
- 82 Apps
- 14 Predict
- 3 Jupyter Workspaces
- 11 R & Python Tiles
- 241 Distribute
- 59 Domo Everywhere
- 241 Scheduled Reports
- 14 Manage
- 35 Governance & Security
- 18 Product Ideas
- 1.1K Ideas Exchange
- Community Forums
- 15 Getting Started
- 1 Community Member Introductions
- 49 Community News
- 18 Event Recordings
- 579 日本支部