DOMO importing columns from Google Sheets that don't exist.
I'm importing some data from google sheets. I occasionally edit the columns in the sheet. When I re-import the data in DOMO, it keeps importing the now deleted columns. The deleted columns also continue to show as a selection when making a card.
Any Idea how to fix this? The only success I've had was to delete the data source and re-import it as if it were brand new.
Best Answer
-
@Sweep_The_Leg You know what, I just looked at the connector and it doesn't look like it actually has the functionality to switch between append and replace. Interesting.
Have you tried creating a brand new dataset and importing the sheet, do the old columns still pull over? This could be a legitimate connector bug that should be reported. It's also concerning that changing the schema doesn't carry through to the final output dataset. Both of these things should probably be reported through Domo Support.
Let me know if you have any additional questions.
**Say 'Thanks' by clicking the thumbs up in the post that helped you.
**Please mark the post that solves your problem as 'Accepted Solution'1
Answers
-
Hey mbauer,
Do you by chance have the dataset set to append, rather than replace? The only thing I can think of is that the connector is attempting to append a new schema to the old one, so you get the old columns as well.
If that's not the case, I would recommend reporting a bug to Domo Support.
Let me know if the above is helpful!
**Say 'Thanks' by clicking the thumbs up in the post that helped you.
**Please mark the post that solves your problem as 'Accepted Solution'0 -
Sorry for the late reply. Unfortunately I don't see the settings for either Append or Replace.
0 -
@Sweep_The_Leg You know what, I just looked at the connector and it doesn't look like it actually has the functionality to switch between append and replace. Interesting.
Have you tried creating a brand new dataset and importing the sheet, do the old columns still pull over? This could be a legitimate connector bug that should be reported. It's also concerning that changing the schema doesn't carry through to the final output dataset. Both of these things should probably be reported through Domo Support.
Let me know if you have any additional questions.
**Say 'Thanks' by clicking the thumbs up in the post that helped you.
**Please mark the post that solves your problem as 'Accepted Solution'1 -
Yes, it seems the only way to correct is disconnect entirely and re-import as if it were brand new. But I'll take your suggestion and report it to the support team.
Thanks again!
0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 292 Workbench
- 4 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 95 SQL DataFlows
- 602 Datasets
- 2.1K Magic ETL
- 3.7K Visualize
- 2.4K Charting
- 691 Beast Mode
- 43 App Studio
- 39 Variables
- 658 Automate
- 170 Apps
- 441 APIs & Domo Developer
- 42 Workflows
- 5 DomoAI
- 32 Predict
- 12 Jupyter Workspaces
- 20 R & Python Tiles
- 386 Distribute
- 111 Domo Everywhere
- 269 Scheduled Reports
- 6 Software Integrations
- 112 Manage
- 109 Governance & Security
- 8 Domo University
- 30 Product Releases
- Community Forums
- 39 Getting Started
- 29 Community Member Introductions
- 98 Community Announcements
- Domo Community Gallery
- 4.8K Archive