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.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.2K Connectors
- 284 Workbench
- 4 Cloud Amplifier
- 4 Federated
- 2.9K Transform
- 88 SQL DataFlows
- 554 Datasets
- 2.2K Magic ETL
- 3.3K Visualize
- 2.3K Charting
- 562 Beast Mode
- 9 App Studio
- 27 Variables
- 577 Automate
- 140 Apps
- 414 APIs & Domo Developer
- 22 Workflows
- 1 DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 350 Distribute
- 90 Domo Everywhere
- 258 Scheduled Reports
- 2 Software Integrations
- 91 Manage
- 88 Governance & Security
- 9 Product Release Questions
- Community Forums
- 42 Getting Started
- 28 Community Member Introductions
- 85 Community Announcements
- 4.8K Archive