3577750 - Does SAP Datasphere support automatic remapping of connections when replication flows are imported into another space?

After transporting a Replication Flow from Space A to Space B within the same SAP Datasphere tenant, although deployment succeeds, errors occur indicating that the source table is missing.
The issue is caused by the source connection and container not being automatically remapped to the target space.

Looking for a way to automatically remap the source connection and container when transporting a Replication Flow from one space to another in SAP Datasphere, but this feature is not currently available.

• SAP Datasphere

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

Missing feature.

Currently it needs manual mapping.

And there is a submitted enhancement request idea 343040 on the SAP Customer Influence Portal for SAP Datasphere.

Please contact with your Customer Success Partner (CSP) to get updates on this enhancement request.

Furthermore, stay tuned about upcoming features in SAP Datasphere Roadmap.

• KBA 3332382 - How to create an enhancement request for SAP Datasphere?
• SAP Customer Influence Portal for SAP Datasphere
• Roadmap for SAP Datasphere
• Creating, Finding, and Sharing Objects
• 3297105 - Important considerations for SAP Datasphere Replication Flows

Replication Flow, SAP Datasphere, Connection Mapping, Container Mapping, Import Export, Space to Space Transport, Enhancement Request , KBA , DS-DI-RF , Replication Flows , Problem