Skip to Content
0

Special value not always selected in complex table agentry client

Jan 03, 2017 at 10:41 AM

98

avatar image

Hi,

I have a screen with a field linked to a complex table. Based on rules (rule for index, rule for cascade parent), the complex table can be filtered when specific criteria are met. When these are not met, the complex table is not filtered at all.

This functionality works fine, but...

There is also a 'special value' defined which is shown as the default value of the drop down. This works fine when the complex table is NOT filtered; this special value is being shown in both the list of possible selection as well as the current value.

When the complex table IS filtered, the special value is available as possible value, but it is not the current value.

I have been looking for the reason, but can't find it. Who has a clue?

The version of Agentry client is 70.12.1, work manager 6.2.1 is the application.

Kind regards.

Mike

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Chung Yu
Jan 06, 2017 at 03:34 PM
0

Hi Mike,

I believe that's expected behavior, when not filtered, the default is shown as current. When filtered, it is putting the default value is put into as possible value not as current value since the filter is applied. I hope this helps.

If you need another behavior, Please talk to your account executives to open a open request.

Chung Yu

SAP Senior Support Engineer

Share
10 |10000 characters needed characters left characters exceeded
Mike Overmeijer Jan 09, 2017 at 06:48 AM
0

Hu Chung,

Thank you for your feedback.

The value of the underlying field is the same as the special value hence the drop down could show this. Doesnt the framework lookup the value of the underlying object in order to check whether it is also a value in the dropdown?

Kind regards,

Mike Overmeijer

Share
10 |10000 characters needed characters left characters exceeded