Improve Error Reporting for missing fields


If a field name is changed in a data flow on a card that I'm editing all it tells me is "An invalid column was specified in your request (the column does not exist on the dataset)". When I have a data set with over 100 columns and all of the beast mode calculations on top of it it'd save a bunch of time and frustration if it could tell me exactly which beast mode calculation is erroring so I can quickly fix it.
**Did this solve your problem? Accept it as a solution!**
Comments
-
Up vote! I am experiencing a problem right now where I had to adjust a categorical beast mode after adding new columns ot the dataset powering the card, and once I made the updates to the best mode the same error popped up. However, after validating the formula and confirming it works, the error persists. If the message had more detail, I might be able to determine if this was a glitch or if I'm still missing something. It doesn't appear to be the case becasue I can make an identical card that works fine but I cannot make the error go away in the original one.
0
Categories
- 7.7K All Categories
- 12 Connect
- 925 Connectors
- 247 Workbench
- 441 Transform
- 1.7K Magic ETL
- 61 SQL DataFlows
- 456 Datasets
- 88 Visualize
- 222 Beast Mode
- 2.1K Charting
- 8 Variables
- 5 Automate
- 349 APIs & Domo Developer
- 85 Apps
- Workflows
- 17 Predict
- 3 Jupyter Workspaces
- 14 R & Python Tiles
- 242 Distribute
- 60 Domo Everywhere
- 241 Scheduled Reports
- 18 Manage
- 39 Governance & Security
- 46 Product Ideas
- 1.1K Ideas Exchange
- 6 Community Forums
- 19 Getting Started
- 6 Community Member Introductions
- 50 Community News
- 18 Event Recordings
- 577 日本支部