MSSQL DB Query Manager Warning for existing Server Actions - Table does not exist

[guptast]

Wappler Version : 3.8.1
Operating System : MacOS
Server Model: ASP.Net
Database Type: MSSQL

Expected behavior

What do you think should happen?

When an existing Server Action Query is opened in Database Query Builder, no warning for tables is expected. There’s no warning for new Server Actions.

Actual behavior

What actually happens?

When an existing Server Action Query is opened in Database Query Builder, a warning is displayed Table 'ABC' doesn't exist! Please select the new table. If the same table is re-selected from the drop-down menu and query is updated, the SA stops working.

How to reproduce

1. Open an existing Server Action with Query Builder
2. A warning is displayed (screenshot attached)

[almatry]

Wappler Version : 3.8.1
Operating System : MacOS
Server Model: ASP.NET
Database Type: MSSQL 2017

I thought this would be fixed in the latest version but since version 3.8.0 after selecting the table name from the list and opening the page it says

“message”: “Exception has been thrown by the target of an invocation.”
and
“Message”: “Invalid object name TABLE NAME”

Workaround:

I have to edit the API action file manually and change the line

“table”:“dbo.table_name”
to
“table”:“table_name”

[George]

The new MS SQL connector uses dbo as table prefix to handle multiple schemas.

There was however a bug in the asp.net version that will be solved in the next next update:

Connection error mssql in asp.net

I have an update here that you can test, place the files in the Bin folder. DatabaseConnector.zip (27.4 KB)

[George]

Maybe we should support both with and without the dbo prefix in the query builder so no renaming is necessary @patrick

[Teodor]

This has been fixed in Wappler 3.8.2