We are using SQL Server 2017.
I made the change and it did not correct the issue.
Did it work before the Wappler update? As far as I know the above code was the only thing changed in the last update, unless you had an older version.
Yes, it worked before the update. What I did was go through a few pages on the site looking for what I needed change for the customer. I had updated Wappler on Thursday but have not used it since. I made a simple html change but Wappler uploaded all the updated core files. When I returned to the site to test it, thatâs when the Retrieve Identity broke. Now, it may have been 3.5.6 that broke it, as I have not had to update this site in a couple of weeks.
We didnât have any other changes to the database module in the last 3 months other than the above.
Is there another way to troubleshoot it besides having to revert to an earlier version and upload the Lib files?
I pulled the files from a backup of the server. Only when I replace my Server action did it work. I checked my server action and it is the same as it was last time, so I put the two files in a file compare and the one that is working (from the backup) has line 41 âreturningâ: âAppointmentIDâ. The new file does not have that, even though the server action is the same.
File compare:
One on the left works, itâs the backup. One one the right does not, itâs the new file. Here is the server action, same as before the update:
The only thing I have done differently in the server connect files is I added a column to the insert step. It works correctly adding the value, there are no errors.
It is 3.5.7 that is not including the line to return the identity in the server connect file.
Are you sure that the old one has the returning and the new one not? The fix we had was adding the returning instead of removing it.
Yes, the one that works has returning on it, the one that does not work does not. In 3.5.7, it does not add the line âreturningâ. If I add it manually and upload it, it works.