Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

after message e

Former Member
0 Likes
507

Hi,

In dialog programming, after the display of error message all the elements in the screen are greyed out. Can I avoid this ?

I use, for example

MESSAGE Ennn(F2) with ' my message'.

thks

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
475

Hi,

In dialog program if you use the error message with in the Chain and enchain, the first field where it is getting the error will be enabled and all the other fields will be greyed out.

If all the entries are good enough then it is ok.

ERROR message in dialog program will definitely grey out the screen fields. It wil not allow you to go to next screen field until it is having the right data.

Use chain and end chain.

Regards,

Venkatesh

3 REPLIES 3
Read only

Former Member
0 Likes
476

Hi,

In dialog program if you use the error message with in the Chain and enchain, the first field where it is getting the error will be enabled and all the other fields will be greyed out.

If all the entries are good enough then it is ok.

ERROR message in dialog program will definitely grey out the screen fields. It wil not allow you to go to next screen field until it is having the right data.

Use chain and end chain.

Regards,

Venkatesh

Read only

RichHeilman
Developer Advocate
Developer Advocate
0 Likes
475

This is the basic behavior when dealing with error messages. In module pool programming, you will always want to wrap your error checking in specific modules. So lets say that you have three fields on your screen, F1, F2, and F3. and you want to do checking only on the F2 field. You should create a module called something like CHECK_F2, and put your logic in there. In your screen flow logic, in the PAI section, you would tie that screen field to that module like this.

FIELD F2 MODULE CHECK_F2.

What this does is if there is an error, then that field will be open for input so that you can change the value to a correct value, all other fields will be greyed out. This is the normal behavior.

In your case, you have NO fields tied to your error checking module, which is why they are ALL greyed out. You need to tie your error checking module to the specific field that you may be checking. If you require to allow the user to change multiple fields when an error occurs, then we use the CHAIN statement in the screen flow logic to tie more than one field to a MODULE.

Chain.
  field: F1, F2, F3.
  module check_all_three.
EndChain.

I think this syntax is right.

Regards,

Rich Heilman

Read only

Former Member
0 Likes
475

Using Chain and Endchain you can make them open for edit.

Check this Program

DEMO_DYNPRO_FIELD_CHAIN