[ALM Accelerator - BUG]: Adding a deployment profile to a solution changes an environments URL

[ryanhodgson1]

Describe the issue

Hi

This is a continuation of this bug i raised in the past here: #4668

I have found that when i assign a deployment profile to a unmanaged solution in its environment the production URL gets changed to something it shouldnt be.

The environment URL is set to this:

Then i go to assign the profile here:

When i click save, the environments URL is changed to this:

The strange thing is that if i scroll down to the bottom when i apply the profile it shows the correct URL and when i save it it doesnt have the issue:

Its a bit hard to explain so might be best to show it over a remote call.

Expected Behavior

For the URL not to get randomly changed

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

1.0.20230308.1

Steps To Reproduce

As above and below video

test-20230529_152717-Meeting.Recording.mp4

Anything else?

No response

[mikefactorial]

Hey Ryan, sorry for the delayed response on this one. Thanks as always for going the extra mile to provide such great detail. Will take a look at what's going on since it does seem like it should be easy to reproduce even though I can't say I've seen this happen before.

[ryanhodgson1]

Thanks @mikefactorial

[mikefactorial]

Hey @ryanhodgson1 think a call might be in order for this one. @RajeevPentyala and I have both tried to duplicate the issue with no success. Feel free to set something up when you have time v-ochsmike at microsoft.com.

[mikefactorial]

Had a thought on this today. Since we have both the dropdown and the text field for entering a url I wonder if that has something to do with the strange behavior. The interface gets a little strange during the save and seems to flash the text box and then go back to the dropdown view during the Patch. Wondering if maybe there's something related to whether the text value or the dropdown value is being used in the patch.

[CoEStarterKitBot]

@ryanhodgson1 This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.