Building flow inside or outside a solution prompting/not prompting for trial license (SQL Server connector)

[vllanso]

Hello community,

I have tried to create the same simple flow inside a solution and outside a solution:
* flow trigger is "Powerapps"

* next action is calling an SQL stored procedure using the SQL Server connector

and:

- When building the flow NOT in a solution, everything goes OK and I can save and test the flow.

- When building the flow INSIDE a solution, as soon as I add the SQL acction, it prompts for a trial license

Is this the expected behaviour ? Why would it require the trial if I am in a solution, and not require the trial when not in a solution ?

Any clue or any thing that I could check ?

I am probably missing something about licensing ... but right now I don't understand what.

Below are sample screen captures of the problem:

Regular flow, outside a solution
Trying same flow inside a solution

Thanks, Victor.

[Pstork1]

It should require a trial in either place.  What may be happening is that when not in a solution it is re-using an existing connection that was created prior to October, 2019.  Apps using SQL connections created before that were grandfathered in for a period of 5 years.  But when inside a solution it is definitely creating a new connection.  New SQL connections are premium and would require a premium license or a trial license.

[vllanso]

Thanks @Pstork1 for your quick answer.

The fact is that the SQL connection was created in November 2020, so way past the october 2019 limit. And that is what surprises me.

One additional question:

- if I assign a "Per-flow" license to the flow, before adding the "Execute SQL stored procedure" action

- then I open the flow and add the "Execute SQL stored procedure" action

- should I be allowed, without requiring the trial license ?

(Note: I do have 1 spare "per flow" license available).

Thanks, Victor.

[Pstork1]

If the connection was created in Nov, 2020 then it should be prompting you for a trial license wherever you are.  If you assign a per-flow license to the flow it should let you add the SQL connection.  But I can't guarantee that it won't prompt for a trial.  It shouldn't in that circumstance, but it might.  In that situation there is no legal requirement since the per flow license covers you.  But it won't cover anyone else since the flow is triggered by Power Apps.  Legally you should have a per app or per user license for every user using that power app and flow.

[vllanso]

@Pstork1 thanks again for your answer.

When you mention that it might prompt for a trial, in case it shows, is it a "true" prompt for a trial ? or it is a "fake" prompt for a trial ?.

How would I know if it will indeed start a trial license or not ?.

I was looking at this link from power apps, or this link from child flows, and both mention that sometimes you may get the trial prompt, but for me is not clear what happens if you do click to start the trial period.

Thanks, Victor.

[Pstork1]

If you click through on the trial link it will start a trial.  Its not a "fake" link.  Its just a false positive on the test of whether you need a premium license or not.