[ALM Accelerator - BUG]: Keyvault Connection reference issue

[Miti-Shah]

Describe the issue

We have a Solution aware Power Automate flow that connects to 4 different Key vaults. For this we use 4 different connection references pointing to appropriate key vault connection.
When deploying the solution using ALM Accelerator to higher environments, in the configuration screen, we create connections in the target and map it to the appropriate connection references.

After the deployment is completed we see that all the 4 connections references are mapped to the same connection id, they are no longer mapped to the connections created and mapped in the configuration section.
This results in the solution to fail in the higher environments.

Expected Behavior

keyvault connection should be mapping to appropriate connection references when we move the solution to higher environments

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

1.0.20231006.2(Managed)

Steps To Reproduce

No response

Anything else?

No response

AB#555

AB#1613

[RajeevPentyala]

@Miti-Shah You can utilize the toggle option (highlighted below) in the 'Connection References' tab to specify the Connection IDs. This approach will help avoid confusion when creating connections for a similar type of 'Connection Reference'.

'Connection Id' can be grabbed from the browser's connection url as shown below.

[Miti-Shah]

@RajeevPentyala we do not see the toggle option yet in the 'Connection References' under ALM , do let us know if we need to adjust any settings from our end to make it visible.

[RajeevPentyala]

@Miti-Shah Its 'ABC' button from your screen.

Among the following buttons.

[Miti-Shah]

@RajeevPentyala we tried this method and issue still exist , we mapped respective KV connection references and closed and saved solution but issue still persists. All the references points back to first one.

[RajeevPentyala]

@Miti-Shah We modified the design a bit and the fix will be part of January month's release.

[Miti-Shah]

Thanks @RajeevPentyala also once we save and close the solution , all references shouldn't point back to 1st one. As per below screenshot

[RajeevPentyala]

@Miti-Shah Yes, reference selection will be persisted when you close and comeback.

[CoEStarterKitBot]

@Miti-Shah 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.