cancel
Showing results for 
Search instead for 
Did you mean: 

How to handle the screen elements appear and disappear in personas 3.0

surendra_battula
Participant
0 Kudos

I have tried searching for this but have came across screen id and control id information and some from other posts but barely found weather it is a note issue

or something to do with screen id. we are having the latest personas 3.0 and kernel release 7.42.

I had created a flavor for transaction BP with merging tabs and this is a bdt transaction.

everything is working fine but when I open my flavor some of the screen elements  appears few seconds later ( they are from other tab in actual screen) and when I am entering data I have the same issue few few fields disappear and the appear back.but all screen elements have the same screen number and program name.  but they don't lose data I have entered.

thanks in advance for your precious time reading my query.

Regards

surendra b

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

hi,

as of today, BDT screens are not supported.

Please see our limitation note : 2050838

Sushant

Answers (2)

Answers (2)

surendra_battula
Participant
0 Kudos

thanks for the replies

what would be the best option for me to go

should I make a custom object and copy the data to the original object or wait  for any new updates.

regards

surendra b

Former Member
0 Kudos

Can you explain a bit more - what do you want to achieve? also, is this "appear/disappear" behavior correct according to you point? Thx.

You can check if you need to do "Control ID overwrite" setting. When dealing with Tabs, control ids are often changed for the same UI control, which cause your script code going banana. Hope I am hitting the right spot. Thx.

Br,


Dong

surendra_battula
Participant
0 Kudos

thanks for the reply Dong.

my issue is my flavor look like the image below when I open it with few screen elements.

and few seconds later  I get  rest of the screen elements as the image below.

so if  it is analysed  ID details appears later in the second image

which is not in the first image.

how can I resolve this issue.

kind regards

surendra b

Former Member
0 Kudos

This looks like a UI rendering delay for the component moved from other Tabs. I haven't figured out any ideas. Maybe SAP experts may have some tips.

Br,

Dong