FPM search UIBB - F4 help

[a_figueredo]

Hi all,

We have to implement a search using FPM Search UIBB component. The filters were properly created with their F4 search helps (both freely: using value help listener and classic: using a search function)

The search helps for all fields have 2 fields: Code and description.

As per requirement, we should show the description in the field when returning from the search help, but technically, for all database operations we need the codes.

With old select option we used to the save descriptions and codes in low and high fields (and not allowing range selections) with this trick, we were able to show the description and complete the database operations with the codes. Maybe it is not a good practice, but solved the requirement.

Is there any way to do something like that with the select options 2.0 / FPM search UIBB component?

Including the description field next to code in filter would be also great.

Thanks a lot,

Agustín.

[a_figueredo]

Hi,

We will use conversion exit for this problem, but as the description could be the same for different IDs, we will have a little problem for the INPUT conversion.

EG:

ID    Title
1      OrgUnit
2      OrgUnit

There is no way to get more than 1 ID when title is filled.

Kr,

Agustín.

[ulrich_miller]

Hi Agustín,
I did not quite understand the requirement. Could you add a picture that shows how it looked liked with the old select options?

Ulrich

[a_figueredo]

Hi Ulrich,

The help opened with the match-code or F4 looks like following:

When we select one record, the field is filled with the description instead of the object ID (code):

There is no point from user side to show the codes in filter, as they work with descriptions, but at technical side, we need the Object ID in order to access to database etc.

With original select options, as I mentioned before, we used to save Description in LOW field of select option range and Object ID in HIGH. Doing that, we can show only the description but we keep the object id in range in order to operate with it.

We know it is probably not a good practice, but it was the only way we found to solve the requirement. It needs some coding, and add some restrictions (ranges cannot be used, its mandatory to use the match code..) but works.

We would need something similar for FPM SEARCH UIBB.

Thanks a lot,

Kr,

Agustín.