Initiate flow from within app

[Anonymous]

So I have a fairly simple flow that copies an item from one SP list to another SP list and then deletes the item in the original list: 

Essentially they are lists of orders that are due and orders that have been completed.

Now, my issue is in the delivery app, I'm building. I want to implement a button (located in a screen that contains a DetailForm showing the selected item from the SP list) that will trigger said flow. To wit, I inserted a button, selected Power Automate for its OnSelect property, located my flow in the menu and then the following appeared in the formula bar: 

'Ekspeditionu.foto'.Run(
// I then added the reference to direct the flow to the Item Id in question:
'Ekspeditionu.foto'.Run(DataCardValue26)

This all works well and good. However, being the go-getter I like to think I am, I've decided to add a bit of panache. Taking a cue from one of Shane Young's tutorial videos (I'm sure you're all familiar) - https://www.youtube.com/watch?v=UWy5I_MuIgU - I decided to add a loading spinner to occupy and lock the screen while the flow is running and ultimately a navigation to a different screen, that holds a gallery showing the list of completed orders:

Set(varShowSpinner, true);
Set(varFlow,'Ekspeditionu.foto'.Run(DataCardValue26).result);   // This bit triggers a few errors
Navigate('ArkivTransporter_BrowseScreen');
Set(varShowSpinner, false);

This is where my issues really start. When I put the trigger for the flow into a variable ('varFlow') I get a few errors:

Incompatible type we can't evaluate your formula because the context types are incompatible with the types of values in other places in your app.

and:

Invalid use of '.'    // this is marked for the ".result" part of the formula)

I am scratching my head to figure out why this can work in the tutorial scenario and not mine.

Any ideas?

[Jeff_Thorpe]

Have you tried adding the Power Apps action "Respond to a PowerApp or flow" to the end of the flow?

[Anonymous · Accepted solution]

@Jeff_Thorpe That's a great idea, but I seem to have solved the issue by editing the formula to this:

Or, in a more generic variant:

Set(nameOfYourVariable, 'titleOfFlow'.run(parameterToPassToFlow))

I guess it was the ".result" appendix that threw me off. But that's what you get when using a year-old tutorial 🙂

The connected flow doesn't have a "Respond to a PowerApp or flow" action at the end, but PowerApps seems to respect its runtime regardless. I think the "Respond to a PowerApp or flow" action is intended for when you want to specify the contents of said response between flow and app/flow.