Well yes we received it - but it will be really useful if you also describe the problem and also enter steps to reproduce.
That is the above for form.
Otherwise we have now idea what you are reporting.
Sorry if I didn’t include it, but as this was a part of a longer string I thought that you had it.
The problem is that when I establish a Server Connect Update Action, the filter variable does not automatically appear in the Conditions panel. If one chooses the column to be used as the index or key - for example Towns.id , the corresponding Post.id, value is not displayed. As a result unless the SQL is incomplete as it does not include the " WHERE ID = Post.id ".
I realize that this can be corrected manually, but all the tutorials published indicate that this is an automatic function.
Since I have experienced problems with almost every update of Wappler, I suspect that the installation may have become corrupted, and I wonder if a uninstall/reinstall would produce the correct results.
Would you mind posting some screenshots of the server action possibly, the more information the merrier with stuff like this. I am on the latest and have done about 15 update actions this week that all worked flawlessly, so unless this is somehow a little out of the ordinary I cant see why it should not work.
Here are two screenshot: The first is the Update Table and the second is the Conditions panel after selecting column ID. Note that the SQL is incomplete.
What options do you get when you click the Lightening Bolt icon on the Conditions TAB? Do you get a list of $_POST variables where you can possibly select $_POST_id?
The second thing that seems a little strange on your update is why on the Columns and Values pane you even have an entry for ID, you should never be updating the physical ID itself?
Is that how it came up as default or did you change anything to say add the ID manually.
Found the problem - it is only in the ASP.NET model - seems primary keys aren’t auto added there.
Will fix it in the next update
1 Like
Thanks for finding it. I was beginning to doubt my sanity.
The id column came up as a default value. I normally would check for that and remove it, but I wanted to show want was not happening. As it turns out there was a problem in the ASP.NET version. Thank for looking at it.
No problem. Glad someone found the issue though. That’s good news.
@wld, after seeing your db structure I was a little concerned about your Id being called id and decided to do some investigation
I realise this was not the cause of your problem and you are waiting for a wappler fix but might be worth noting these comments when you are fully operational again.
I appreciate your looking into this. The DB structure is not ideal, as I was just trying to do something that should have been real quick and easy and did not contain foreign keys.
1 Like
This is solved now in version 1.7.1