Adrenaline dataflows should not re-evaluate the schema of an inbound dataset.


I have discovered that a dataset being brought into an adrenaline dataflow, will have its schema re-evaluated based on the first x number of rows coming in.
In my case, this resulted in a google sheet dataset coming into the dataflow with an important text field being reassigned as a number. all the text values were then set to NaN. This, of course, rendered the dataflow useless as the text values were required for the needed processing.
Rather than re-evaluating a schema, adrenaline dataflows should take the schema from the dataset itself. That schema has been established and accepted prior to processing. I was told that it is working as designed but that is insanity. You should never assume you know better what the schema of a dataset should be and override the datatypes defined in that dataset.
Categories
- All Categories
- Product Ideas
- 2.1K Ideas Exchange
- Connect
- 1.3K Connectors
- 309 Workbench
- 7 Cloud Amplifier
- 10 Federated
- Transform
- 663 Datasets
- 119 SQL DataFlows
- 2.3K Magic ETL
- 823 Beast Mode
- Visualize
- 2.6K Charting
- 86 App Studio
- 46 Variables
- Automate
- 193 Apps
- 483 APIs & Domo Developer
- 87 Workflows
- 23 Code Engine
- AI and Machine Learning
- 23 AI Chat
- 4 AI Projects and Models
- 18 Jupyter Workspaces
- Distribute
- 117 Domo Everywhere
- 283 Scheduled Reports
- 11 Software Integrations
- Manage
- 143 Governance & Security
- 11 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 116 Community Announcements
- 5K Archive