[BUG] Connection Not Set Properly Based On Last Selected Tab And Show Wrong Environment Name

[LinnZawWin]

Describe the bug Based on previous behaviour and this comment, the new tools is opened for the same connection as the last selected tab. But recently, the behaviour changed in a way that it opens to the last connected environment. The worse problem is that the environment name on the tab, the connection name and the environment colour are being set as the last selected tab but the actual connection is pointing to the last connected environment.

To Reproduce

1. Open Webresources Manager and connect to Dev environment.
2. Right-click on the tab and choose Duplicate Tool with new connection.
3. Connect the 2nd tab to the Test environment.
4. Close the 2nd tab (Test) in the previous step.
5. Focus on the 1st tab (Dev) and the connection at the footer panel is shown as "Connected to [Dev environment URL]".
6. Open Webresources Manager from the Tools list.
7. A new tab is opened with the tab name "Webresources Manager [Dev connection name]" and the connection at the footer panel is shown as "Connected to [Dev environment URL]". But when the web resources are loaded, it loads the web resources from Test because the actual connection is pointed to Test.

Expected behavior The actual connection should be pointed to Dev as per the tab name and connection footer panel and the web resources from Test environment should be loaded.

Screenshots

Desktop (please complete the following information):

• XrmToolbox Version: 1.2022.2.54
• Tool version: 2.2022.2.20 (Webresources Manager)

Additional context N/A

[MscrmTools]

Hi @LinnZawWin, I'm sorry but following your scenario does not end with the same result. It does work as expected for me, the dev environment is the one used in the end. Would it be possible you had some organization renaming/restore that makes connections acting weirdly?

[LinnZawWin]

Hi

You are right. It only happens for a specific tenant (or maybe a set of connections). I have sent you the link to the video where I replicated the issue and the connection .XML file via email.

I created the new connection file, re-created the connections to both DEV and TEST in the new file and I am still experiencing that issue. Other than having MFA for this tenant, I do not see any difference with the other tenants which are working fine. (those are all in Oceania region)

Please let me know if you need any more logs or any other info. If you are not able to replicate the issue, I understand that it will be hard for you to fix the issue. In that case, I will try to debug it next weekend and I will keep you posted.