SQl connection suddenly throws "Server respose: Not a valid connector Error response" on SubmitForm()

[MrMarshall]

I am having two SQL tables in a Azure SQL, they are a bit different but consists only of a few nvarchar(255) and Int columns.

The application is editing these tables through simple forms and it was working from the beginning, but now I am recieving error "An error occurred on the server. Server respose: Not a valid connector Error response" as soon as I am trying to edit a row in ONE of the tables. But the other one works..? 

Viewing data (rows) is still possible in both. 

I have tried: 

1. Recreate the Connection with SA admin for the database.
2. Recreate the application in new tenant against the same SQL.
3. Recreating the SQL Table with different name on another SQL-server.

But the application still throws this error, are PowerApps having some issues here or what's cause this issues on my SQL-table?

What else could i try?

Added the error message as an attchment.

CREATE TABLE [dbo].[Test](
[Id] [int] PRIMARY KEY IDENTITY(1,1) NOT NULL,
[TEST1] [int] NOT NULL,
[TEST2] [nvarchar](255) NOT NULL,
[TEST3] [nvarchar](255) NOT NULL,
[TEST4] [nvarchar](255) NOT NULL,
[TEST5] [nvarchar](255) NOT NULL,
[TEST6] [nvarchar](255) NOT NULL,
[TEST7] [nvarchar](255) NOT NULL,
[TEST8] [datetime] NOT NULL,
[TEST9] [nvarchar](255) NOT NULL,
[TEST10] [nvarchar](255) NOT NULL,
[TEST11] DECIMAL(12,3) NOT NULL,
[TEST12] [datetime] NOT NULL,
[TEST13] [nvarchar](255) NULL,
[TEST14] DECIMAL(12,3) NOT NULL,
[TEST15] [nvarchar](255) NOT NULL,
[TEST16] [nvarchar](255) NOT NULL,
[TEST17] [nvarchar](255) NOT NULL,
[TEST18] [int] NOT NULL,
[TEST19] [nvarchar](255) NOT NULL,
[TEST20] [nvarchar](255) NOT NULL)

(No of course I didnt named my records TestX, that's only here)

[Anonymous]

A client sent me the attached screen capture

[Anonymous]

Reporting back, in my case it was because Microsoft updated how comparison works with boleans in Filter function.

I had Filter(table, bolean_column) and it worked until yesterday
I had to change to Filter(table, bolean_column = true)

Maybe check if you are making comparisons in your functions.

[Mannyman]

I had this *exact* same issue that started yesterday sometime between 11am - 2pm Eastern Time, and I got off the phone with Microsoft a couple hours ago with the same resolution. I guess any filter using a boolean value must specify the 'true' condition going forward. It sucks this just changed on their end without notice and brought my workflows offline for a day.

Anyway, I'm glad you also figured it out, I found your thread and was going to reply with my own findings.

[v-xida-msft · Accepted solution]

Hi @MrMarshall ,

Do you mean that the issue occurs when you use the SubmitForm function to submit your form data?

Have you defined a Trigger within your SQL Table ([dbo].[Test])?

Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned.

Please consider take a try to submit your form data using Patch function instead of the SubmitForm function, then check if the issue is solved. Please set the OnSelect property of the "Submit" button to following:

If(
   EditForm1.Mode = FormMode.New,
   Patch(                            /* <-- Add new record */
        '[dbo].[Test]'),
         Defaults('[dbo].[Test]'),
         EditForm1.Updates
  ),
  Patch(                           /* <-- Modify existing record */
      '[dbo].[Test]',
       BrowseGallery1.Selected,
       EditForm1.Updates
 )
)

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

Please check if you have defined a Trigger within your SQL Table. If you defined a Trigger within your SQL Table, the Insert and update operation from PowerApps app to your table does not work. Please consider remove the Trigger from your SQL Table, then re-create a new connection to your SQL Table from your app, check if the issue is solved.

It is an known limit within SQL Server connector, please check the following article for more details:

https://docs.microsoft.com/en-us/connectors/sql/#known-issues-and-limitations

The user @emh has faced same issue with you, please check the response within the following thread:

https://powerusers.microsoft.com/t5/General-Discussion/Message-is-Server-error-Server-response-Not-a...

Note: Also please make sure you have defined a proper PRIMARY KEY within your SQL Table.

If the issue still exists, please consider remove the SQL Table from your Azure SQL, then re-create a new one, re-create a new app based on the new created SQL Table, check if the issue is solved.

Best regards,

[Mannyman]

@MrMarshall,

I'm sorry but for some reason I saw asix7's post but I did not realize you were the OP. I just want to make sure your issue isn't the same as what me and asix7 experienced yesterday where our app stopped working unexpectedly. Was your app previously working?

If so, I would recommend reviewing any code on your your Item properties and event actions (e.g. OnClick, OnLoad, Items, etc.) to see if any boolean filters were used in your PowerApp. If you have any filters applied using boolean variables, make sure that the filter includes the = true/false condition. Before yesterday, this was a non-issue but due to some unannounced change on Microsoft's end this is now required.

For example, I might have theoretically populated a gallery with Filter(table_Clients, active) which would have pulled all active clients in my table. This syntax no longer works. You must now use Filter(table_Clients, active = true). Also, some of my objects (buttons, timers, etc) would refresh a dataset and trigger the error so I had to update those too.

While using PowerApps Editor, try reproduce the error. Once you have done that, if you use the app checker tool (the stethoscope icon in the upper right corner), you can locate problematic object properties under the Runtime section. Update any properties you find that use a boolean filter, then save and reload your app and try again.

Hope this helps!

[MrMarshall]

Hi and thanks for all the good answers. 

However I couldn't test any of it because today the error was gone. No changes has been made to the application.

How strange, but lets hope that never happends again...

[v-xida-msft]

Hi @MrMarshall ,

Have you solved your problem?

Based on the issue that you mentioned, I think it may be related to the PowerApps server.

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

Best regards,

[MrMarshall]

Nope, I was wrong. 

The issue was a trigger on the table.