1. Ravi Kumar
  2. PowerServer
  3. Thursday, 27 June 2024 06:30 AM UTC

Hi Team,

 

We just used PB2022 R3 to deploy one of our products on PowerServer. We are seeing odd problems with datatype conversion on one of the application's screens. I am only receiving the error in the Powerserver deployed app, even though it does not occur when I run the application with PB2022 R3.

DataBase : SQL Anywhere 16

 

---------------------------
Errore sul Database N. -1
---------------------------
Select Error: ERROR [07006] [Sybase][ODBC Driver][SQL Anywhere]Cannot convert 'A12' to a integer
---------------------------
OK
---------------------------

Kindly find the required screenshots for the detailed information on the issue and let me know if you need any more information from my side. Thank you!

 

 

Attachments (1)
Marco Meoni Accepted Answer Pending Moderation
  1. Thursday, 27 June 2024 12:02 PM UTC
  2. PowerServer
  3. # 1

Hi Ravi,

can you verify columns' definition in the C# data model?

That is, open the PS solution from SnapDevelop -> AppModels -> YourProjectName -> Models -> <subfolder(s)> -> d_yourDwUsedForSelect.cs.

Do you see wrong int/string definition if compared to dataobject in PB?

Best,

.m 

Comment
There are no comments made yet.
Ravi Kumar Accepted Answer Pending Moderation
  1. Thursday, 27 June 2024 12:52 PM UTC
  2. PowerServer
  3. # 2

Hi Marco Meoni,

 

I didn't find any difference in the C# model and the PB data object used for the select. 

Please find attached screenshot of the C# model. Thank you

 

 

Attachments (1)
Comment
There are no comments made yet.
David Xiong @Appeon Accepted Answer Pending Moderation
  1. Monday, 1 July 2024 07:34 AM UTC
  2. PowerServer
  3. # 3

Hi Ravi,

 

We suggest that you submit this issue to our support portal at https://www.appeon.com/standardsupport/newbug and upload a small reproducible case (including table SQL, test data, etc.). This will help us analyze and reproduce the issue and provide feedback on our findings. Thanks.

 

Regards, 

David

Comment
  1. Ravi Kumar
  2. Thursday, 4 July 2024 13:01 PM UTC
Hi David,



We are able to manage the issue by tweaking the SQL query in the data object before it migrated into C# model.

Thank you for the help.

  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.