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
- 10.5K All Categories
- 8 Connect
- 918 Connectors
- 250 Workbench
- 472 Transform
- 1.7K Magic ETL
- 69 SQL DataFlows
- 477 Datasets
- 199 Visualize
- 254 Beast Mode
- 2.1K Charting
- 11 Variables
- 17 Automate
- 354 APIs & Domo Developer
- 89 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 247 Distribute
- 63 Domo Everywhere
- 243 Scheduled Reports
- 21 Manage
- 42 Governance & Security
- 178 Product Ideas
- 1.2K Ideas Exchange
- 12 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive