Write data to Azure AQL Database table via power apps form

[JWPowder]

Hello All, I am trying to use this method to write data to my Azure SQL table. 

https://www.mssqltips.com/sqlservertip/7032/power-apps-read-write-data-sql-server-database-azure/

I have created the connection to my SQL database in power apps using Azure AD integrated credentials. I then created the power automate query below as instructed in the guide:

However, when I try to insert that DataFlow into my app I get an error, eventhough the dataflow is associated with the button I am trying to use to trigger it. The SQL connection was added to my app so I'm really unsure what the hangup is. 

[Pstork1]

What is the error message you are getting?

[JWPowder]

@Pstork1 ,

[Pstork1]

It looks like you added the Ask in PowerApps content to the SQL query after you added the flow to the button in Power Apps.  Do the following:

1) Copy your current onSelect in Power Apps

2) Remove the flow from the Power App OnSelect

3) Re-add the flow

4) Paste your original OnSelect code back into place.

When you add a flow to a Power App it takes a snapshot of the flow's input and output parameters.  If you change the flow later you need to re-add it to Power Apps to update that snapshot.  That's why you are getting an error saying its not expecting any input parameters.

[JWPowder]

I have done this several times with no success. 

[Pstork1]

Try replacing the Power Apps trigger in the flow with the Power Apps v2 trigger.  Using that you can specify the input parameters for the flow in the trigger.  

[JWPowder]

Just tried that as well and I am still getting the same error. 

Set(
    feedback,
    'PowerAppV2->ExecuteQuery'.Run(
    Title.SelectedText,
    Status1.SelectedText,
    Operator.Text,
    Start_Time.SelectedDate
));
If(
    !IsBlank(feedback.statuscode),
    Notify("Data Input Unsuccessful", NotificationType.Error),
    Notify("Data Input Successful", NotificationType.Success))

[Pstork1]

I don't know why its not working.  But the error is still suggesting that it is working off the wrong definition of the flow since it claims there are no input parameters.  That should have cleared up if you removed and re-added the flow.  I don't know what else to suggest.