Managed Solution publishing with different connection

[rpersad]

I am publishing a managed solution to production however it is using an old SMTP connector when I check. The unmanaged solution has the updated connection. What can I do to fix this?

[FLMike]

Hi @rpersad 

Delete the connection, re-install, resetup the connection during install, this way you dont generate another layer unintentionally

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[rpersad]

Hi @FLMike 

So the managed solution has the old connection and the unmanaged solution has the new connection.

So just to clarify do I delete and add back the connection in my unmanaged solution and then published it into my managed solution?

[FLMike]

Hi @rpersad 

Good for checking.

Stupid question maybe, but how do you know it has the old one in it?

Firstly, did you remember to delete the old connections out of the Environment that you created the Managed Solution in, before Exporting your solution as a Managed solution? Because there shouldn't be a way for the old one to be there once its removed and you have published all customizations and then exported.

So I would make sure its deleted from your dev/test/managed make environment. Republish, and then export again.

You will also want to delete the old one from Production and import again,

But I would test it in another environment and make sure in one that doesn't have the old, it creates and uses the new. I think its just a meta-data issue.

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[rpersad]

Thank you @FLMike for your assistance. That is not a stupid question given that you do not have a full understanding of the issue. When the connection was set up, buy someone else, the new connection was named differently.

My understand to the Microsoft solutions is new so I may not be explaining this correctly but a solution was created for the application and its flows. 

There is a development environment with an unmanaged "version" of the solution. I basically exported it solution and imported into the production environment which as a managed "version", where I assumed it would replace the old version of the solution with the application, flows and connections. Here is a screenshot of the solution with all the items listed on the left side of the image.

From my understanding you are not suppose to edit a managed solution given that it would created unmanaged layers, microsoft shows a warning message of this, shown in the image below

[FLMike]

Hi @rpersad 

Agree it should be that smart, but its almost like we have to make sure, so what I do if this happens and no matter what I do it won't fix itself. And as a last resort, I delete the managed copy in Prod that you already have. Then you would go into the Default Solution on the env and just make sure nothing still exists (connections etc)

Then import again.

Also, when you did the import, it should have said on the first little side window on the bottom, Patch or Upgrade, not new.

But what can happen at times is it will continue to use the old connection if you haven't deleted it, even though you dont want too, so if you delete it before you import it, it will use the new one for sure.

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[rpersad]

Hi @FLMike 

Not sure if I am doing anything wrong I am getting this error in the image below. I deleted the solution from another environment that I found the solution in, before deleting in production and making things worse. However I am getting this error, see the image below, when I try to import a managed or unmanaged solution.