Updates Made In Existing Data Model Transformations Do Not Get Saved In DMW
(Doc ID 2902028.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Data Management Workbench - Version 3.1.1.2 and laterInformation in this document applies to any platform.
Symptoms
When changing the join condition of a table from one set of columns to a different set of columns, the save button will not be enabled. But when clicking on another table, a message will appear saying there are unsaved changes.
After changing something else about the mapping, such as adding a package, the save button appears.
After clicking the save button, it acts like it saves. When looking at the table again to check the join, it shows the prior join condition with the old columns.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |