Server Connect dropping query conditions on re-open

[baub]

Windows 10/Asp.net wappler 7.2.2

Here are my conditions:

And then I close it. And save it. But when I open it back up the conditions are all gone!!!

Any way for an emergency update on this @patrick. Supposed to be launching a site on Monday and need to work on this this weekend….

[Teodor]

Hey Baub, please check:

Server Action files getting corrupted when modified

Could you make sure that your database schema in the database manager is well updated? Just run from the context menu "Refresh Full Schema" when the tables node is selected of your database. Let us know if it is all fixed after that.

[baub]

Nope that didn’t work. Not sure if the other post was node or something different. I am using asp.net and microsoft sql. the other post was node.js

[baub]

And if I click on open in code editor this is all i get…

[guptast]

I can confirm this issue in a NodeJS project with MSSQL database. I can see the code for condition in the code editor, however, it doesn’t show conditions in the UI.

I have seen this issue off and on with MSSQL database in Database Query Builder, especially where APIs have been added over the course of multiple versions of Wappler. It is most likely related to [dbo] prefix in the table and field names. In some cases I was able to fix the UI issue by removing [dbo]. prefixes from the tables and field names, in others I had to rebuild the queries.

[turn3636]

This is what my issue is now. I’m on a Mac with Node and MS SQL Server. I thought it was fixed by doing the database schema refresh but it does not. While it kept my selected fields, It clears out the conditions and parameters.

Server Action files getting corrupted when modified

I also just tried creating a new server action. It works if you create it and save, but if you modify the query, it gets corrupted again by clearing out your selected columns and adding Select all.

This is not fixed, but this issue was closed.

Here is code view of my query:

But here it is in the query builder with no condition.

[sid]

There is something broken in the new auto-alias configuration in 7.2.2. Was about to post the same issue. 3 days - I am suprised it has not been fixed yet!

For older/existing queries, opening it messes with conditions because it does not match the alias Wappler is trying to add to the query.

Additionally, join conditions are broken too.

Making changes in the join UI is also broken - it does not show the table name, only the alias input.
Any change in any query now requires me to rewite the whole query and every join. Please release an urgent fix.

[sid]

@patrick / @Teodor Any update on this?

[turn3636]

Bump for an update. Starting to get a pretty big backlog of changes that need to be done.

[George]

Will be fixed in the next update

[turn3636]

Thanks. Gonna be a long two days.

[Teodor]

Fixed in Wappler 7.3