Registration Error in adding a Power Automate Flow to a PowerApps Button

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hi Everybody,

I have issues, in this last days, in associating a Power Automate Task with a button in PowerApps.

When I select the flow to add I get the error: "Registration Error", without any other details.

The flow triggers a stored procedure (with one nvarchar parameter) on a SQL Server on premise database and it works fine.

I have an old PowerApp Plan1 license (buyed in April 2019).

Could someone help me with this?

Thanks Vale

Categories:

Building Power Apps

All responses (5)

Answers (1)

Sort by

v-xida-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Anonymous ,

Could you please share a screenshot about your flow's configuration?

Do you add a "Response" action in your flow to return the stored procedure execution result back to your canvas app?

Based on the issue that you mentioned, I think there is something wrong with your flow's configuration. The user @stapes has faced similar issue with you, please check my response within the following thread:

https://powerusers.microsoft.com/t5/Building-Power-Apps/Trying-to-add-a-Flow-to-OnSelect-action-of-button-returns/m-p/406653

https://powerusers.microsoft.com/t5/Building-Power-Apps/Error-on-adding-a-flow-run-SQL-query-to-powerapps/td-p/119203

If you add a "Response" action within your flow, within the "Response" action, please make sure you have defined proper data type for each one of these required fields defined within the 'required' part of the Response Body JSON Schema.

Please take a try with above solution, then check if the issue is solved.

More details about returning a table value from a flow back to a canvas app, please check the following blog for more details:

https://powerapps.microsoft.com/en-us/blog/return-an-array-from-flow-to-powerapps-response-method/

Also please check my response within the following thread would help in your scenario:

https://powerusers.microsoft.com/t5/Building-Power-Apps/How-to-display-the-result-of-SQL-Server-on-prem-stored-procedure/m-p/195379

Best regards,
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Kris,
thank you for the support.
Here below you can find the flow configuration and the json code for the response: I've used the "Respond to PowerApps" task which works in many other apps I've created.

I can't still find the issue with this.

{
"kind": "PowerApp",
"inputs": {
"statusCode": 200,
"body": {
"esito": "OK"
},
"schema": {
"type": "object",
"properties": {
"esito": {
"title": "Esito",
"x-ms-dynamically-added": true,
"type": "string"
}
}
}
}
}

Thank you
Vale
v-xida-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @Anonymous ,

Based on the flow's configuration that you mentioned, I think there is something wrong with it.

Based on the flow's configuration screenshot that you mentioned, I assume that you want to check if the "Execute stored procedure" action could return proper result, if true, return "OK" back to your app, otherwise, return "KO" back to your app, is it right?

I have made a test on my side, please re-configure your flow as below:

Within the "Respond to a PowerApps or flow" action, provide the following expression for the Esito proeprty:

if(not(empty(body('Execute_stored_procedure_(V2)')?['ResultSets']?['Table1'])), 'OK', 'KO')

Please take a try with above solution, then check if the issue is solved.

Best regards,
Verified answer

Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Kris thank you for the support.
I tried the flow configuration you suggested but nothing changed.

However I've solved the issue simply changing the default language of Google Chrome from Italian to English.
I can't explain the actual reasons behind but now it's working perfectly.

Thank you again

Vale
Togusa 42 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi.
I'm having this same problem, randomly.
However, the "trick" of changing the browser's language doesn't solve it.

I have had better luck by copying the flow, as it is, into a new one ("Save As") and then in powerapps connect the new copy.

There is clearly some issue in the link between PowerApps and PowerAutomate, because if the flow is exactly the same just copied as a new one, if the problem was in the flow's logic, the copy shouldn't work as much as the original.