Thanks i found the source of the problem and solution.

if the table have no identity column and a identity column is set in the update properties of the datawindow then we have the problem

the solution is really simple just set to (none) the identity column and the problem is solved.

I have seen where the datawindow sets an identity column when it shouldn't ( the developer didn't set it, PB set it for some reason). I believe that only occurs when you are using native driver in development with MS SQL. if you use oledb it does not happen.

Hi Mike,



I don't seem to be able to reproduce the issue using native driver with 12.6 or 2017 where datawindow sets an identity column when there isn't an identity column in the database table. It only happens when the database has an identity column.

Please kindly let us know how do you do it if you can reproduce it in 12.6 or 2017. Thanks very much!



Regards,



Tom Jiang

yes, this was a 12.5x bug. I had reported it to SAP, i have no idea if it was ever fixed in 12.6 or 2017.



The other bug is that PowerServer is apparently doing select max() instead of getting the identity value via SQL Server's function for this

Hi Roland & Mike,



I've been trying duplicate the issue regarding the wrong default identity column setting in Rows->Update Properties... I verified using native driver with 11.5, 12.5, 12.6 or 2017, but I have never seen it defaults to anything but (none) if the table itself doesn't has an identity column.Please kindly let us know how do you reproduce the issue. Thanks very much!



Regards,



Tom Jiang