Data Product moves to target domain, but related Data Product Port asset stays in New Data Products domain | Workflow

Timur Djalalov · 2026-04-10T20:58:08.295700Z

Hello,I'm testing the latest Data Product Workflows version 2.2 community offering and I am seeing behavior that differs from the training materials.When I submit/create Request Data Product and complete the ownership flow, the workflow moves the Data Product asset to the selected target Data Product Catalog domain, but it does “NOT” move the Data Product Port. The Port asset remains in New Data Products (Data Product Catalog domain).Based on the Collibra University training video/material “Manage data products in Collibra”, section “Request”, video #2 “Assign and Accept Ownership”, I expected both the Data Product and its Port to move together into the target domain.From the BPMN, I can see a step to "Move the Data Product to Target Domain", but I do not see a step to move related Port assets.Can anyone confirm whether this is expected behavior in the newer package/release, or whether the workflow should also move the related Port asset to the same target domain? If you have addressed this already, which workflow did you update? Should the operating model also be updated or configured in addition to the workflows to ensure that related Data Product Port assets move with Data Product to the target domain?Thank you.

MoreDiscussions

Data Product moves to target domain, but related Data Product Port asset stays in New Data Products domain | Workflow | Collibra Community