1. Juan Pedro Sanz Diez
  2. PowerBuilder
  3. Tuesday, 11 June 2019

 

Hello,

My name is Juan Pedro. We have installed the Appeon Powerbuilder 2019 Build 2082. We have realized that in the new version the computed field in the datawindow's sort are loosing.

I mean:

Appeon Powerbuilder 2017

1.- Add a field (F) in a datawindow
2.- Add Computed field (CF) in a datawindow.
3.- Go to rows -> sort and select F and CF for the second. OK and close.
4.- Go to rows -> sort and both F and CF are there.
5.- Save datawindow
6.- Go to rows -> sort and both F and CF are there.
7.- close datawindow
8.- Open datawindow
9.- Go to rows -> sort and both F and CF are there.


Appeon Powerbuilder 2019

1.- Add a field (F) in a datawindow
2.- Add Computed field (CF) in a datawindow.
3.- Go to rows -> sort and select F and CF for the second. OK and close.
4.- Go to rows -> sort and both F and CF are there.
5.- Save datawindow
6.- Go to rows -> sort and both F and CF are there.
7.- Close datawindow
8.- Open datawindow
9.- Go to rows -> sort and the CF ISN'T there.
10.- Close datawindow
11.- Edit Source Datawindow -> and the CF is There, in the sort. OK
12.- Open datawindow
13.- Go to rows -> sort and the CF ISN'T there.
14.- Save datawindow
15.- Edit Source Datawindow -> and the CF ISN'T There, in the sort, any more.

Comments:

1) If the computed field is alone in the sort, it works.
2) All fields behind a lost computed field , are loosing too, computed and not compute. Only not computed fields before the computed field are keeping.

 

Two problems:

1.- At runtime, it doesn't work, althought in edit source the field is in the sort.
2.- At maintenance, if we save any datawindow, computed fields are loosing, for ever.

Who is viewing this page
Preben Hansen Accepted Answer Pending Moderation
0
Votes
Undo

Thanks Juan for reporting and documenting this issue so well!

I believe we are many waiting for a fix of this issue. It prevents us from upgrading to PB2019 as well.

 

@Appeon: Please provide a date for the MR with the fix of this issue. Two months have passed now since it was first reported.

Thanks a lot.

Kind regards

Preben

Comment
We have also been waiting for the fix. I don't know how anyone can upgrade to 2019 without this error being corrected. We had to scrap plans of upgrading and testing over the summer because of this issue.



Is there an estimated date for the MR?



Thank You

Andy
  1. Andy Preman
  2. Wednesday, 28 August 2019
There are no comments made yet.
  1. Friday, 23 August 2019
  2. PowerBuilder
  3. # 1
Roland Smith Accepted Answer Pending Moderation
0
Votes
Undo

Is this a case of the DW Painter messing up the syntax?

Comment
There are no comments made yet.
  1. Wednesday, 26 June 2019
  2. PowerBuilder
  3. # 2
Chris Pollach Accepted Answer Pending Moderation
1
Votes
Undo

Hi Andy;

  Engineering has said that this is one of their top fixes and they hope to have it included in the next Maintenance Release (MR). Please note that I do not have as of yet ... a solid confirmation for this ticket's fix or an exact date of the MR at this time.

Regards ... Chris

Comment
Chris,

Any update to the time-frame of this fix? I am held up on my project of migrating from PB11.2 to PB2019 until this is resolved.



Thanks

Andy
  1. Andy Preman
  2. Monday, 15 July 2019
Hi Andy;

I have not received any PB2019 MR release date update yet.

Regards ... Chris
  1. Chris Pollach
  2. Wednesday, 17 July 2019
Hi Andy;

Our Appeon QA team just started testing the MR's for PowerBuilder and PowerServer this week. I do not have an exact release date yet but I expect early September (if everything goes well regression testing wise).

Regards ... Chris
  1. Chris Pollach
  2. Wednesday, 28 August 2019
There are no comments made yet.
  1. Wednesday, 26 June 2019
  2. PowerBuilder
  3. # 3
Andy Preman Accepted Answer Pending Moderation
0
Votes
Undo

Chris,

This is a major issue for me as well.  We are in the middle of upgrading to 2019 and ran into the same computed field  sort problem.  Any idea when this will be resolved.

Thanks,

Andy.

Comment
There are no comments made yet.
  1. Wednesday, 26 June 2019
  2. PowerBuilder
  3. # 4
Govinda Lopez Accepted Answer Pending Moderation
0
Votes
Undo

Hi Juan,

 

Please try using the SetSort() method of the DW. Plus, try the following:

In your DataWindow source, try removing leading and trailing spaces of the column names that are inside the parenthesis. 

For example, change from:

sort="abs( col_1 ) D"

to:

sort="abs(col_1) D"

 

Do let us know if this worked for you. If not, then yes, please open a support ticket for this case.

 

 

Regards,

Comment
Well, I'will begin with the second workarround.



1.) We actually don't use an expresión but a computed field.

2.) We tried to change the computed field by the correspondent expresion, but when we run the aplication, the execution fails and it gets out of the program. I think that it can be because we have a very long expresion.



That is:

IF( epigrafe = 'A1', 'A.1.-Derivadas del consumo de combustibles fósiles',

IF( epigrafe = 'A2', 'A.2.-Emisiones fugitivas (Derivadas de las recargas de sistemas de refrigeración)',

IF( epigrafe = 'B1', 'B.1.-Derivadas del consumo eléctrico',

IF( epigrafe = 'B2', 'B.2.-Derivadas de la gestión de residuos generados',

IF( epigrafe = 'B3', 'B.3.-Derivadas del consumo de agua potable','No Definido'))))) + ': ' + string(sum( cantidad_co2 for group 4 ),'#,##0.00000') + ' ' + c02_unidad



Problems:



1) The second point above.

2) As we said in the main exposition, all computed, not computed, expresion below any computed field or expresion is loosing, next time you save the datawindow.



The first workarround.



We tried it, and this is which we have been using with new datawindows since we found the problem. In this end, the problem is if we save any datawindow with this type of sorts in mantenace issues, and we don't be aware.



I think this is a very critical missing funtionalit, and for this cause we opened the ticket 2844. They are keeping me informed.



Thanks for your advise.



Regards.
  1. Juan Pedro Sanz Diez
  2. Thursday, 13 June 2019
There are no comments made yet.
  1. Wednesday, 12 June 2019
  2. PowerBuilder
  3. # 5
1
Votes
Undo

Hi Juan

That's a very clear case example of your problem, I suggest you raise a support ticket for Appeon to look at it.

Cheers

David

Comment
Ticket opened with number 2844
  1. Juan Pedro Sanz Diez
  2. Tuesday, 11 June 2019
Hi Juan .. FYI: we reproduced your issue from our Appeon side on that ticket.
  1. Chris Pollach
  2. Wednesday, 12 June 2019
There are no comments made yet.
  1. Tuesday, 11 June 2019
  2. PowerBuilder
  3. # 6
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.