Workbench 4.5 Error: Object reference not set to an instance of an object
I am running Workbench 4.5 and when I migrated my Workbench 2.0 jobs I noticed that some were left out. When try to import them into Workbench 4.5 one by one I get this error: "Object reference not set to an instance of an object."
Has anyone else experienced this error and does anyone know what's causing it?
Comments
-
Hi all,
Can anybody help out @IntelliVince?
Thanks!0 -
Hi there,
I see that this thread was put in nearly a month ago. If it is still an issue, I'd like you to contact Domo Support at 801-805-9505, support@domo.com via email, or Buzz them from your instance. Typically an error like this occurs from a null exception that is pointing to a null value. There could be multiple outlets to look at in order to fix this error.
They'd be glad to help, and they're expecting your case.
Thanks
1 -
FYI -- I am getting the same error message and was searching for a solution. I will go ahead and contact support.
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