3577750 - SAP Datasphere replication flow issue after export from one space to another

• You are moving a Replication Flow definition from one space A to another space B.
• You are expecting that Datasphere auto-maps the source and target columns so that the transported replication flows run correctly in B.
• RF is getting deployed and but during execution, RF is giving errors indicating that the table does not exist in the new space container.

• Container and connection is not getting auto-mapped to the new space container and connection.

• SAP Datasphere

1. Export the flow definition from the source space, then import it into the target space.
2. Container and connection is not getting auto-mapped to the new space container and connection.

Missing feature.

When we export and import replication flows from one space to another, the source connection and container cannot be auto mapped as the export will not automatically know which connection and container to use.

Hence, this is a feature request and we recommend you to create an influence request with your scenario
Please follow this link to create an enhancement request: https://influence.sap.com/go/datasphere

Creating, Finding, and Sharing Objects

3297105 - Important considerations for SAP Datasphere Replication Flows

KBA , DS-DI-RF , Replication Flows , Problem