November version . Set Flow Permissions does not work for flows in solution

[EmranCoE]

Describe the issue

Hi ,

We just upgaded the new version( Core 3.18 , Governance 2.8 ) from november , but following two functions are missing .

Unable to change the owner for flows in solution using “Set Flow Permissions” App .

Still the same message
[Flows in solutions can only be deleted or assigned new owners. They can not have their permission types edited programmatically ]
showing this error when trying --

Also did not found that environment variable in new version “Exclude Teams Environment from Compliance “ in order to exclude Teams from developer compliance center .

Many Thanks
Emran

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

3.18

What app or flow are you having the issue with?

Set Flow Permissions

Steps To Reproduce

No response

Anything else?

No response

[Jenefer-Monroe]

Hello, this is not an env variable we ever shipped: Exclude Teams Environment from Compliance
You can excuse individual environments from this in the Power Platform Admin View

[Jenefer-Monroe]

Can you please show me the steps you took to get to the error message shown here

[EmranCoE]

Thank you ! Jenefer ,
So , "Excuse from Compliance Flow " in Power Platform Admin View need to do it for each Teams Environment separately , for example we have more than 200 Teams Environments .
But I have seen earlier few weeks ago in my other computer while testing Demo CoE Env.

It could be good may be , if have one varible works for all upcoming Teams Env also

[Jenefer-Monroe]

Yes i dont know how that env var got in there, as you can tell from the name (new_... instead of admin._..) this didn't come from our official release at least. The flow does not look for this env var and so it wouldnt work unless you edited the flow as well. For now at least, you will need to exclude the teams envts individually. You could create a flow to mark them all up though if you wanted.

[Jenefer-Monroe]

Can you please show me the steps you took to get to the error message shown here

[EmranCoE]

Set Flow Permissions open the App >> search by owner (whos flows in solution>> in the left side you can see the caution symbol and right side the Add Permissions button is disable , flows those are not in solution this button shows enable.

When click on the flow its go to following page -that showing only Viwer and Editor Role >> when try to Add user >>comes that error I attached earlier

Also at the bottom of the page ---Changing flow ownership is not possible in the product, so changing it here only changes it in the context of your CoE Toolkit. It is stored and used as a property of the CoE Flow table: DerivedOwner--

[EmranCoE]

About the Env Variable . I am very sorry if I make you confused . I just remember now that I was created this Teams Env Variable last time for testing purpose in my other computer.
Ok , thanks for the idea (create a flow)

[Jenefer-Monroe]

i believe you have unmanaged layers on that app (Set Flow Permissions). The page now looks like this

[EmranCoE]

Checked just now , did not see any unmanaged layers

[Jenefer-Monroe]

Curious. Do you see multiple instances of the solution installed? I wonder if some upgrade failure hit you.

[EmranCoE]

Maybe its better , I explain to you the whole scenario during upgrade
After removed all the unmanaged layers >> started with following order (that might not needed)

1. Nurture (success , No error )
2. Governance (success , No error)
3. Audit Logs ( failed , got that error in the below screen )

and there were two Audit Logs >> I deleted the latest one( version 2.6)

4 . Core ( success ,No error )

5. Then did the Audit Logs again ( success , No error )
   But that API connection in [Child] Admin | Sync Logs (Office 365 Management API) could not connect yet . It was created by my another colleague (in vacation now, waiting for him , hope we dont have to create the API connection again) , currently Audit Logs components are turn off .
   So , the failure hit was in Audit Logs . Does that make this issue or might get other effect in ( Core and Governance Components )

[Jenefer-Monroe]

Alright, I'm not sure what to do here. We've already fixed this bug a while ago, but you arent receiving it for some reason.
You could try doing an overwrite of Core, as shown below.

Solution > Switch to Classic (note this can take some time, may have to try twice)

Click Import (fourth from the left)

Choose File (the solution file you were trying to install) > Next > Next > Overwrite customizations (note this is not the default) > Import

[EmranCoE]

Okay , thanks for the instructions , if I understand correct ! Don't have to remove unmanaged layers >> for overwrite option

would like to ask about below screen from Power Platform Admin View App

In maker page , if we change the Display Name and User Principal Name (maker email) , does this will change the owner (example this person has 13 Apps and 92 Flows) for all Canvas/Model Driven apps/flows ?

Also would like to know is there new CoE version coming in December !

[Jenefer-Monroe]

Yes you should always remove unmanaged layers, just in case.

The Power Platform Admin View app does not make changes to objects, its a read of the inventory. While it will change the value in your inventory temporarily these will be overwritten with the sync flows when the object next changes.
Use the Set App Permissions app to change ownership
Please post further questions in separate bugs.

[EmranCoE]

Okay . Thank you so much for all the help , you can close this issue