New connection when changing ownership Dataset

[NicoVerachtert]

Hi,

I'm in the process of automating a release pipeline where the connections of datasets are changed from the development sql server to those of the production environment. Using the Rest API's I'm able to take ownership of the dataset as Service Principal, and even able to change the connectionDetails. However the next step is to bind it to the correct gateway, and this is where the setup fails thusfar. 

We have 2 On-Premise Gateways, both configured with connections for the dev and prd - sql server.

For some reason, every time the dataset ownership is changed, the new owner will have created a new (offline) connection leading nowwhere. 

So before the ownership: we have in connections for that dataset: Connection_DEV, Connection_PRD. After the ownership change, the new owner will also see 'server.net;database'. Now this new connection should already be known to the system, as the Connection_PRD also points to the same connection. When I tried it with a normal user, and with a Service Principal, I made sure both users were added to both the connections and the gateways as admins.

Is this normal behaviour? Is there a way to disable the creation of this new connection when changing ownership? 

[GilbertQ]

Hi @NicoVerachtert 

What I think you need to do first is to create a connection for your service principal in the gateway prior to changing the ownership. I would then assume that it would find the connection because it will use the combination of the service principal and connection to map it correctly.

[NicoVerachtert]

Hi Gilbert,

Thanks for the reply!

I made sure both the user and service principal were added as admins to the existing connections (both were part of the group that was the default admin, but I made sure to add them again). This still results in the same behaviour.

Or did you mean something else?