Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved select max(identitycol) from table error

  1. How-to
0
Votes
Undo
  1. Andres Slachevsky
    Andres Slachevsky
  2. PowerServer 2020 or older (Obsolete)
  3. Tuesday, 28 August 2018 13:51 PM UTC

PB12.5

MS SQL SERVER

a Dw with the identity column running on POWERSERVER give the following error

select max(identitycol) from table invalid column name identitycol

the sql is not written anywhere in our code (not PB nor Trigger/store procedure)

please any advice on how to solve the issue.

Regards.

Andres

 

How handle or replace RESPONSE WINDOWS
PowerServer run in hosting/ PowerServer se ejecuta...
Responses (2)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Wednesday, 29 August 2018 14:51 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

It looks like the real bug is that the identity checkbox defaults to on when it should not.

Comment
mike S
  1. mike S
  2. Wednesday, 29 August 2018 15:19 PM UTC
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
  1. Helpful
Tom Jiang @Appeon
  1. Tom Jiang @Appeon
  2. Monday, 3 September 2018 05:44 AM UTC
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
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 29 August 2018 01:55 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Andres,

Please open a support ticket with a simple PB case here so we can resolve it: https://www.appeon.com/standardsupport/search

Ragards,
ZhaoKai

Comment
Andres Slachevsky
  1. Andres Slachevsky
  2. Wednesday, 29 August 2018 13:20 PM UTC
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.

  1. Helpful
mike S
  1. mike S
  2. Wednesday, 29 August 2018 13:32 PM UTC
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.



  1. Helpful
Tom Jiang @Appeon
  1. Tom Jiang @Appeon
  2. Friday, 31 August 2018 08:48 AM UTC
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
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.