Ant Keep Marching on Patch to New Azure SQL DB

(0) Share

Report

Posted on by schuess3

353

Issue:

Data Source Never Gets Patched

Background

New Azure SQL DB
Connector was established using SQL Admin Credentials Defined when Database was Created
Patch Statement is: Patch('[dbo].[CPT_Codes]',Defaults('[dbo].[CPT_Codes]'),{CPT_Code:txtCPT_Code,CPT_Value:txtCPT_Value});Reset(txtCPT_Code);Reset(txtCPT_Value);
Ants keep marching across top of screen
No Errors
No info

What can i check? Is this possibly a permissions thing cause I used the SQL Admin credentials?

Update

I was able to successfully add data to the database table using the SubmitForm() method. So that confirms the account has the access I need. So my problem must relate to how I am trying to patch() the data.

More Updates

I was able to get the Data Source Patched after creating a new login and user account on the DB with dbo rights. I will say that it sucks that you do not get a GUI Wizard when using SSMS with Azure SQL DBs. I am still fighting with some data source refreshes and unknown runtime errors but i am hoping that gets resolved.

Thanks

Matt

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

v-xida-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hi @schuess3 ,

Have you solved your problem?

Does the txtCPT_Code, txtCPT_Value represent the Text Input box in your app?

If the txtCPT_Code, txtCPT_Value represents the Text Input box in your app, please modify your formula as below:

Patch(
'[dbo].[CPT_Codes]',
Defaults('[dbo].[CPT_Codes]'),
{
CPT_Code: txtCPT_Code.Text,
CPT_Value: txtCPT_Value.Text
}
);
Reset(txtCPT_Code);
Reset(txtCPT_Value);

or

Collect( '[dbo].[CPT_Codes]', { CPT_Code: txtCPT_Code.Text, CPT_Value: txtCPT_Value.Text } ); Reset(txtCPT_Code); Reset(txtCPT_Value);

If you have solved your problem, please go ahead to click "Accept as Solution" to identify this thread has been solved.

Best regards,

Was this reply helpful? Yes No
schuess3 353 on at

Like (0)

Report
Copy link

Link copied!

Missing the .text was part of the unknown runtime error. And the bulk of the original issue was a SQL Database permissions issue.

Thanks.

Was this reply helpful? Yes No