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
- 310 Workbench
- 7 Cloud Amplifier
- 9 Federated
- 3K Transform
- 113 SQL DataFlows
- 654 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 796 Beast Mode
- 78 App Studio
- 44 Variables
- 757 Automate
- 188 Apps
- 480 APIs & Domo Developer
- 72 Workflows
- 17 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 408 Distribute
- 119 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 141 Manage
- 137 Governance & Security
- 8 Domo Community Gallery
- 47 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 114 Community Announcements
- 4.8K Archive