Flow seems broken after add it to an app

[Cengelmann]

Hey everyone, I'm using a normal flow to save/update some data into SharePoint and call a custom connector to proceed with my process. Nevertheless, I figured out some problem as soon as I insert the flow (or any flow with a SharePoint Connection) to a Power App. When I insert the flow into the app, the flow itself can't be open by the new designer anymore. The error says it's because of using connections instead of connection references, which is not the case, because I'm in a solution and check it several times. Even when I remove the flow from the app, it still seems broken. In general, it should be okay to use the old designer, but the problem is, that I want to send some PDF content bytes as base64, but when I add the logic to the flow, it will be removed after I save it. 

So yeah, there must be some issue in the connection between the app and the flow.
Please, can anybody help me here?

P.S. The URL always throws this parameter, as soon as I open the flow: "?v3=false&reason=fromV3"

[FLMike]

@Cengelmann 

Please open every action that uses data.

Take a picture. I feel you will find that one of them in fact is a connection. I dont' see you post anything to demonstrate they aren't other than saying it.

Please Click the ... for each action, and the popup will show whether its a connection or CR.

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

[Cengelmann]

Okay, so that you understand my problem better, I created a TestFlow to prove.

1. I created a TestFlow into a solution

2. I have the connection reference as well in the solution

3. This is the TestFlow in the new designer with the desired connection reference

 

4. I insert the TestFlow into the app

5. Now it's broken ...

It still has the previous selected connection reference, but the problem comes, as soon as I insert the flow into an app ...

 

 

[Cengelmann]

Okay, I figured out, that the base64() function still works against my expectations, cause it's there, but the old designer hides it in the view ...
You can only see it in the code peek.

So the error above is still annoying, but not that important to me anymore.

Thanks anyway, if anyone can fix the problem ;D