1. Kari Paukku
  2. PowerServer
  3. Monday, 3 July 2023 09:15 AM UTC


I wanted to share the following situation, in case there is a solution for this.
I'm using PB2022, build 1900 and the database is Oracle 19

I'm getting the error "The Int64 type is not compatible..." and below is an example of a situation where I can see the mapping in the .cs file going wrong, but I can't see any reason why it goes wrong.

Here are two data windows, the 'd_company' works ok and the 'd_document_list' not

d_company column specification is here

and the column specification for d_document_list is here

Both have the "key" field specifies as number.

in the data models here is the d_company.cs and how the fields get mapped. The company_key is mapped to long

but in the d_document_list.cs the document_key gets mapped to double, resulting in showing the error when runnung the PS application, Running as PB application all works fine.

To me the data window specification looks the same for both (number), so why does PS map the other one to long and the other one to double?

Is there a way to control the mapping or some other fix to resolve this? 




David Xiong @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 4 July 2023 09:20 AM UTC
  2. PowerServer
  3. # 1

Hi Kari,


We recommend that you submit a ticket to our Support system and provide a small case (including SRD, table SQL, etc.) that can reproduce the problem to help us analyze and reproduce the issue locally.




There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 3 July 2023 12:13 PM UTC
  2. PowerServer
  3. # 2

Hi Kari;

  The use of Int64 is also an issue in ASE, SS, DBMS's as well. Appeon has had tickets opened already for this issue in PS2022 already. I'm hoping for a resolution to this in PB/PS2022 R2. 

Regards... Chris 

  1. Kari Paukku
  2. Monday, 3 July 2023 12:36 PM UTC
ok, thanks.
  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.