[ALM Accelerator - BUG]: Profiles randomly unassign

[ryanhodgson1]

Describe the issue

Dont have too much info on this yet but i have found that for some reason profiles are randomly getting unassigned and then a user will report it to me and i have to assign the profile to the solution again.

I havent found any pattern that is causing this just yet but have you come across this issue before? im the only one with access to be able to manage profile assignments so people havent been unassigning them and i havent been removing them.

Expected Behavior

Profile assignments to remain on the solution

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

1.0.20230606.1

Steps To Reproduce

No response

Anything else?

No response

AB#1403

[mikefactorial]

Hey @ryanhodgson1 thanks for reporting this. The solution to profile relationship is a bit clunky the way it is setup currently. It just looks for the most recent Deployment Request with type "Profile" to determine which profile is associated with a solution. We have another issue open to make this relationship more direct. Wonder if this is what you are running into #3584

[ryanhodgson1]

Thanks @mikefactorial it does look like its doing something like that and the result is that it removes the profile assignment. That ticket looks like it would fix the issue but is there any work around for now that i could apply to retain profile assignments?

[ryanhodgson1]

Hey @mikefactorial was there any update on profile assignments? we have 40+ profiles now and it cant remember all the assignments. Its becoming a daily task to reassign the profiles.

[mikefactorial]

@RyanHodgson thanks for bringing this back up. I've included this in the October release. There will be a new table called Deployment Solution Profile that looks up to the Deployment Profile and includes the Solution Name and Maker Environment Id. The app has been updated to create Deployment Solution Profile records based on the existing Deployment Requests logic when a profile is found so there should be no manual steps necessary for using the new table and setting a new profile in the app will update the existing Deployment Solution Profile based on Environment Id and Solution name or create a new record if one doesn't exist.

[ryanhodgson1]

Hey @mikefactorial I am moving on from my current role so tagging in Nomer and Jhiggy below to follow up on these outstanding issues after im gone, thanks.

@agent-roman @abesamisj FYI

[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.