Flow has been broken in Export / Import

[stapes]

I have been deploying a recently completed project to Live.

This involved Exporting & Importing my App between the 2 Environments, and Creating all the required SQL Tables and Stored Procedures.

I had to edit all the flows to change the Connection in the Execute stored procedure control to point to the live database.

When this particular flow is run from the App, it fails with the following error:

Unable to process template language expressions in action 'Execute_stored_procedure_(V2)' inputs at line '1' and column '2137': 'The template language expression 'json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$connections']['shared_sql_1']['connectionId']' cannot be evaluated because property 'shared_sql_1' doesn't exist, available properties are 'shared_sql'. Please see https://aka.ms/logicexpressions for usage details.'.

This stored procedure is doing an insert.

I am getting similar errors from other stored procedures, only line and column numbers change.

The Flow works when I run Test (in the new environment) but not when run from the App.

What is the problem?

[DeepakS]

Hi @stapes ,
After looking at the error message , it seems you should use shared_sql instead of shared_sql_1. Please update and try again.


——————————————————
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

[stapes]

Thanks @Deepak-S , but neither of those (shared_sql or shared_sql_1) are in my code. Where do I find these?

[DeepakS]

Hi @stapes ,

it may be the connection or table name property. Could you please share a screen capture of your Power Automate so i can help you finding this.

——————————————————
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

[yashag2255 · Accepted solution]

Hello @stapes 

If your flow is being triggered from a Power Apps control, this is a very known issue. The best resolution and the simplest one is, remove the flow from the powerapps control and then re add it. 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[stapes]

It looks like these values are connected with the new SQL Connections. I hadn't added these before doing the Import.

I have since redone the import, and it gives me the choice of which connectors to use, so now I can select the new connections on Import.

I had to go back & re-edit all the flows again. They had the correct connections now, but the Server Name is also changed, so I had to manually do all those. It would be nice if I didn't have to do this for every Import!

The flows still did not work in the app.

To make it work, I had to Edit the App, then delete each flow run & add it again.

I don't know if that makes sense.

This is highly unsatisfactory, and makes deployment very long winded.

I hope there is a better way of doing this.