Flow inside managed solution cannot be shared (run-only users) with a SharePoint list

[Anonymous]

I have  a Flow inside a managed solution that is an instant flow. It get triggered manually by a selected file inside a SharePoint document library (Approval Workflow).

I deployed the solution to the customer and re-configured the actions to point to the right libraries and approval actions etc.

For the users to be able to start the Flow I wanted to add the SharePoint list (library) where the Flow is attached to to the run-only users. So in the Flow "Dashboard" in the "Run-Only Users" section I wanted to click on "SharePoint" and select the site and library, but there is no "SharePoint" option available. I see only the option to invite users or teams directly.

I then created a test Flow inside the customer tenant, with the same type (instant flow for selected item/file) and added it to the same library. When I open up "Run-Only Users" section of this flow, I see the "SharePoint" option there.

So, my question is. Is this a bug or a normal behaviour? Can Flows of managed solution (and unmanaged?) not be shared with SharePoint lists?

I read in another post that a user had a similar issue and it worked for him suddenly and that the Power Automate Platform has issues with flows not directly created but coming from a solution - is this still true and I have to wait... some days (which would be not very cool)?

[zylantha2]

… deal with null values in power automate given that power automate fails at the first sign of one

[Anonymous]

Hi @MicaelLev . I think I may have missed this the first few times. But are you saying that if you use a Sharepoint CustomRowCommand and use "ExecuteFlow" then you can execute a flow buried in a solution IF you use the envID as well as the FLow ID? are these just both but in the actionparam "ID" thus "envID/FLowID" or are the separate action params? This may be the solution I am after

[MicaelLev]

Hi @Anonymous , yes this is exactly what I am saying. 

You need to follow the security guidelines mentionned in this thread to make sure the user has access to the environment where the flow is hosted!

[urklnme]

The entire way flows are implemented is a PITA.    and they want people to use them in solutions.  M$ sells this crap to mgmt and worker bees like me get stuck with all the warts.