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
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 620 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 742 Beast Mode
- 58 App Studio
- 41 Variables
- 686 Automate
- 176 Apps
- 453 APIs & Domo Developer
- 47 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 395 Distribute
- 113 Domo Everywhere
- 276 Scheduled Reports
- 6 Software Integrations
- 124 Manage
- 121 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive