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

Resolved PowerServer 2021 Beta DataWindow C# Models

  1. Issue
0
Votes
Undo
  1. Nilotpal Bera
    Nilotpal Bera
  2. PowerServer 2020 or older (Obsolete)
  3. Sunday, 7 March 2021 09:56 AM UTC

Hi,

Using PowerServer 2021 Beta, some datatypes like tinyint(stored procedure), number(datawindow) etc. does not gets automatically converted correctly to C# models and needs to be manually modified and saved.

Like tinyint parses to int32 and number to double.

We have to manually save it as tinyint > byte and number > long

 

Thanks,

Nilotpal

Deploy application to linux server in Powerserver2...
Power Server deployment issues
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Sunday, 7 March 2021 15:13 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Nilotpal;

   For obvious possible errors like this vs general how-to questions, please open a Support Ticket and attach your findings / recreation details to the ticket.

Many thanks in advance.

Regards... Chris

Comment
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Sunday, 7 March 2021 15:23 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Nilotpal,

Adding to what Chris said, what you are testing is a "preview" version so it's not even beta quality... it is barely alpha quality.  We have released it so customers can get an idea what PowerServer 2021 will be like.  So it is expected this version has many many many bugs.

At any rate, we want the final release to be good quality.  So please do as Chris said and open a support ticket with the problem you discovered so we can make sure it is resolved by the final release.

Thanks,
Armeen

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 17 March 2021 01:27 AM UTC
We certainly tested it with Oracle as that is #2 database among our customers. But no, it is not beta quality. The beta version is planned towards end of April.

Certainly we hope people will test it, and so far most of our testers have been quite active. Of course we welcome tickets about bugs, but actually our primary goal besides letting customers get idea what the product is like is to get feedback about optimize features/usability.

Bugs can be fixed much faster than changing how features work. So if we get such feedback too late in the product release cycle it won't make it in the final release. That's the point of doing this pre-beta.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Wednesday, 17 March 2021 01:40 AM UTC
Hi Armeen,

I agree with getting as much feedback, and that's exactly the reason why I'm doing that. But getting initial errors on a simple outer join and datawindows giving errors until I convert them to syntax, made me have the impression that little testing had been done on Oracle. I'm getting great feedback from support on fixing things, so that's not the problem.

regards
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 17 March 2021 02:03 AM UTC
Thanks for explaining. I haven’t gotten this feedback from other beta testers, but we limited it to a very small group so we can properly take care of the customers. Anyway, please give the next version a spin and let me know what you think. It should be much better.
  1. Helpful
There are no comments made yet.
David Xiong @Appeon
David Xiong @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 9 March 2021 10:27 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Hi Nilotpal,

I can’t reproduce the issue.

Could you help provide a reproducible case for us to further analyze the issue? Thanks!

Regards,

David

Comment
Nilotpal Bera
  1. Nilotpal Bera
  2. Tuesday, 16 March 2021 09:32 AM UTC
Hi David,



Thanks for looking into this. PFB the steps to reproduce:



1. create a stored proc with a column in resultset having datatype tinyint

2. create a DW in PowerBuilder using this stored procedure resultset

3. deploy the project, it will parse the DW to C# model but with int32 datatype. Now build and run the api. It should give error during runtime.

4. now manually modify the int32 datatype to byte datatype in the model using snapdevelop ide, save, build and run the api. After this error should not be there



Database:

Sybase ASE 16

ODBC connection using Sybase ASE Driver 16



Thanks
  1. Helpful
David Xiong @Appeon
  1. David Xiong @Appeon
  2. Monday, 22 March 2021 10:36 AM UTC
Hi Nilotpal,



I followed your exact steps using Sybase ASE 16 with ODBC but still can't reproduce the issue. Could you submit a ticket with a reproducible test case at https://www.appeon.com/standardsupport/newbug so we can further analyze the issue?



BTW, are you on build 1076?



Regards,

David

  1. Helpful
Nilotpal Bera
  1. Nilotpal Bera
  2. Friday, 26 March 2021 10:46 AM UTC
Hi David,



Thanks for looking into this.

Yes I am using Build 1076.



Thanks,

Nilotpal
  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.