WB 4.5 Lookup Transform bug/error (Not present in WB 4)
Since updating from WB 4 to 4.5 the lookup transforms not no longer work properly.
I keep getting "Object reference not set to an instance of an object." on most of the jobs that have lookup transforms.
I think I isolated the problem to jobs that have more than 1 lookup transfrom.
It worked perfectly fine on WB 4.0.
I have tested a job using the same lookups individually and they work fine, but when I setup two lookups I get the error every time.
Unless an update fixes the issue this week I will need to revert back to WB 4 and I will no longer be able to provide feedback on the matter.
I have attached the log of my test job.
Best Answer
-
The issue was fixed in the latest version after I brought it up with support.
0
Answers
-
The issue was fixed in the latest version after I brought it up with support.
0
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 311 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3.8K Transform
- 657 Datasets
- 115 SQL DataFlows
- 2.2K Magic ETL
- 815 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 81 App Studio
- 45 Variables
- 775 Automate
- 190 Apps
- 481 APIs & Domo Developer
- 81 Workflows
- 23 Code Engine
- 40 AI and Machine Learning
- 20 AI Chat
- 1 AI Playground
- 1 AI Projects and Models
- 18 Jupyter Workspaces
- 410 Distribute
- 120 Domo Everywhere
- 280 Scheduled Reports
- 10 Software Integrations
- 144 Manage
- 140 Governance & Security
- 8 Domo Community Gallery
- 48 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 114 Community Announcements
- 4.8K Archive