Data Connector Fields Refresh?
I have a question and I'm not sure if this has been asked (couldn't find it) and I'm not sure if anyone else has this issue, but:
If I set up a data connection with columns A, B, and C and then I add column D, all columns show as expected.
However, if I have columns A, B, and C and then delete C from the import, the data comes over empty for C, but the column header is still there. This is the most annoying when I've just renamed the column or if the deleted column name looks very similar to an active column.
Is there a way to refresh this without creating an entirely new connection? As an FYI, I have seen this happen with the NetSuite connector and I haven't confirmed how this affects other types of data imports.
Thanks!
Best Answer
-
If you have your Netsuite dataset, set to APPEND, and you have C in a previous run and then in the next run someone deletes C, the next run will show C as blank like you describe.
If you have the connector set to Replace, then you wouldn't see C at all because the schema will change to the new format.
What I've always recommended to my users is that you don't point cards directly back to connector datasets..you build an ETL and point them to the output of that. So for this example, maybe create a recursive ETL and use 'SELECT COLUMNS' in your ETL so you can add/remove columns as you see fit.
Attached is a guide for recursive ETL.
I hope that helps.
Matt
0
Answers
-
If you have your Netsuite dataset, set to APPEND, and you have C in a previous run and then in the next run someone deletes C, the next run will show C as blank like you describe.
If you have the connector set to Replace, then you wouldn't see C at all because the schema will change to the new format.
What I've always recommended to my users is that you don't point cards directly back to connector datasets..you build an ETL and point them to the output of that. So for this example, maybe create a recursive ETL and use 'SELECT COLUMNS' in your ETL so you can add/remove columns as you see fit.
Attached is a guide for recursive ETL.
I hope that helps.
Matt
0 -
Hi, thanks for the reply.
The datasets in question are using the replace method so I don't think the recursive ETL is necessary. I already use that for certain reports that I want to append.
I'm the only one building anything in Domo at all so it's more of an annoying cleanup issue for myself more than anything.
0 -
Ok, that was weird. I didn't make any changes to the data, but just reran it and even though the error was showing before (I had A, B, and C and then changed C to D and it showed all 4. Now it only shows the corrected A, B, and D).
I also can't find other examples where this issue existed so I'm going to mark your answer as the solution. Thanks!
0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 293 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 96 SQL DataFlows
- 607 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 705 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
- Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive