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

Resolved PB2019 Bug?

  1. Issue
0
Votes
Undo
  1. Praveen Rajarao
    Praveen Rajarao
  2. PowerBuilder
  3. Tuesday, 23 July 2019 14:55 PM UTC

Hi,

I migrated one of my PB12.5 apps to PB2019. 

I have a tree-view datawindow with Sort order defined in the design mode. 

When I migrated, this datawindow somehow lost the sort columns. So I manually added them back in 2019. 

However, when I run the application, the sort order disappears. No matter how many times I have tried to add this back, it just doesnt remain in the design mode. 

See attached screenshots. 

Anyone else facing this issue? 

Thanks

Praveen

Attachments (1)
PB Bug.pdf
Simultaneous use of PB2019 R2 and PB2017 Rx?
Creating a DLL that can be registered with RegSvr3...
Responses (6)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 23 July 2019 15:12 PM UTC
  2. PowerBuilder
  3. # 1

Hi Praveen;

  FYI: I just tried this in my PB2019 IDE and cannot replicate your Sort issue.

Q1: Is this DWO controlled by some sort of "Source Control"? If so, did you "Check Out" the DWO first?

Q2: Is there a possibility that your have the DWO in two locations?

Regards ... Chris

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 23 July 2019 15:36 PM UTC
FWIW: Make sure that the PB App's work folder and it's sub-folders & files are *not* "write protected".

FYI: Just tested with computed columns being sorted as well. No issues with loosing the Sort settings.

  1. Helpful
Kevin Ridley
  1. Kevin Ridley
  2. Wednesday, 24 July 2019 12:27 PM UTC
One thing to be sure to check is that you don't have another dw with the exact same name in a PBL higher in the library list. If it works fine in design mode, but then is wrong when you run it, you may have another dw somewhere in another pbl that is being picked up before the one you are changing.
  1. Helpful
Praveen Rajarao
  1. Praveen Rajarao
  2. Wednesday, 24 July 2019 13:29 PM UTC
Kevin - No, I have confirmed that there are no duplicates. Also, when I exit my application, the DW is losing the sort columns. So it is not a object hierarchy issue.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Tuesday, 23 July 2019 16:11 PM UTC
  2. PowerBuilder
  3. # 2

there are some reported issues with sorting, including when used with compute fields

https://www.appeon.com/standardsupport/search/view?id=2844

 

see if that is similar to what you are seeing in your application

 

 

 

Comment
Praveen Rajarao
  1. Praveen Rajarao
  2. Tuesday, 23 July 2019 16:15 PM UTC
Yes, looks like this is related to what is already reported. Thanks.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 23 July 2019 18:07 PM UTC
  2. PowerBuilder
  3. # 3

Hi Praveen;

   I just tried a complete suite of DWO "sorting" tests on SQL computed columns, DWO computed columns, regular columns and any combination of the above.

  I could not reproduce your issue on my W10 based PB2019 IDE PC's.

Regards ... Chris

Comment
Praveen Rajarao
  1. Praveen Rajarao
  2. Tuesday, 23 July 2019 20:26 PM UTC
Hi Chris,



I zeroed in on the issue. It is only happening when I have a computed column and a regular column in the sort. If I have just the computed column then it works fine. Regular column sort is also fine. Only when it is a combination of both.



Similar to the issue here - https://www.appeon.com/standardsupport/search/view?id=2844



Thanks

Praveen
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 23 July 2019 20:29 PM UTC
Hi Praveen ... I tried that combination as one of my test cases and the DWO did not loose any sort settings.
  1. Helpful
There are no comments made yet.
Vipin Dwivedi
Vipin Dwivedi Accepted Answer Pending Moderation
  1. Thursday, 14 November 2019 18:33 PM UTC
  2. PowerBuilder
  3. # 4

Hi Chirs,

 

We are seeing this issue in PB2019 MR 2082. It is happening to my application as well. If I put the compute field at top in the sorting order. It works fine. but if I put my compute field as second sort criteria. It is not doing. I can see someone already reported this as bug and Appeon team were able to reproduce it. https://www.appeon.com/standardsupport/search/view?id=2844

Let us know when this will get fix. It is impacting the whole application.

 

Vipin

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 14 November 2019 18:46 PM UTC
Hi Vipin;

In the ticket system, it shows that this particular sorting issue should be fixed in the up coming PB2019R2 GA release and the upcoming PB2017R3 maintenance release. However, I have not received 100% confirmation of this fix yet. I will follow up on this.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Charles Winters
Charles Winters Accepted Answer Pending Moderation
  1. Wednesday, 20 November 2019 17:37 PM UTC
  2. PowerBuilder
  3. # 5

We have discovered the same problem.  This will cause a major headache for our large financial application.

 

Comment
There are no comments made yet.
Julie Jiang @Appeon
Julie Jiang @Appeon Accepted Answer Pending Moderation
  1. Thursday, 21 November 2019 01:27 AM UTC
  2. PowerBuilder
  3. # 6

Hi Praveen,

Yes our team is aware of this bug and plan to have it fixed in the coming 2019 MR, which is targeted to be delivered next month.

Best regards, Julie

 

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