cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with lookupdisplay after migrated the code to PB12.6

Former Member
0 Kudos

Hi Team,

We are migrating our applications from PB12.5 to PB 12.6, as part of migration we are facing some issue with lookupdisplay() in datawindow expression. We have tried with the PB 12.6 build 4088. Application crashed wherever the lookupdisplay expression is used. We have tried with using the datawindow expression directly in the code, after that crashing issue is fixed but, the datawindow with lookupdisplay expression is not loaded properly.

Can you please suggest some ideas to fix these issues.?

Thanks in advance.

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member202249
Active Participant
0 Kudos

Hi Nishanth,


As Chris says, please try the newest EBF.   Although the bug is not listed in the fixed bug list, there is a fix for a LookUpDisplay crash in build 4098.

Pat

Former Member
0 Kudos

Hi Nishanth;

  FYI: The current build is 4098. I wonder if its worth giving that version a try to see if SAP have also addressed the LookUpDisplay ( ) stability issue in that build?

Regards ... Chris

Former Member
0 Kudos

We had similar issues in Build 4091 with lookupvalues in computed fields.

The values are not displayed anymore.

It seems that the evaluation of the computed fields runs before the dddw are retrieved.

A workaround is to re-assign the expression again in the retrieveend event.

string exp

exp = this.Object.kostentraeger.Expression

this.Object.kostentraeger.Expression = exp

Does this match your problem?

KR Ludwin