cancel
Showing results for 
Search instead for 
Did you mean: 

[Search GUIBB] Hide operator

guillaume-hrc
Active Contributor
0 Kudos

Hi,

Let's say that there is only 1 available operator (equals for instance) that I would like to hide to the user.

Is this possible to hide operator in Search GUIBB?

I though I had seen this in 7.31 or 7.4 new features but can"t find it...

Administrator personalization is of no use because user can add new criteria and operator is shown on these new lines.

Thanks in advance.

Best regards,

Guillaume

Accepted Solutions (1)

Accepted Solutions (1)

satyajit_mohapatra
Active Contributor
0 Kudos

Hi,

Seems like it's not possible. I don't see any options in method GET_DEFAULT_CONFIG or GET_DEFINITION in search feeder interface.

I'm really keen to know in case there's a workaround for this.

Regards,

Satyajit

guillaume-hrc
Active Contributor
0 Kudos

Hi,

I have started fooling around with a post-exit Enhancement of WDDOMODIFYVIEW of the SEARCH_VIEW in the FPM_SEARCH_GUIBB with some results.

   DATA: lo_render       TYPE REF TO cl_fpm_guibb_search_render.

   DATA: lo_input_field  TYPE REF TO cl_wd_input_field,

         lo_ddlb         TYPE REF TO cl_wd_dropdown_by_key.

   FIELD-SYMBOLS: <ls_search>  TYPE LINE OF cl_fpm_guibb_search_render=>t_search.

   lo_render ?= wd_assist->mo_render.

   LOOP AT lo_render->mt_search ASSIGNING <ls_search>.

     CLEAR: lo_input_field,

            lo_ddlb.

     " Hide operators

     lo_ddlb ?= view->get_element( <ls_search>-ui_id-op ).

     IF lo_ddlb IS BOUND.

       lo_ddlb->set_visible( cl_wd_uielement=>e_visible-none ).

     ENDIF.

     " Activate Suggest Values for criteria values

     lo_input_field ?= <ls_search>-ui_inp1.

     IF lo_input_field IS BOUND.

       lo_input_field->set_suggest_values( abap_true ).

     ENDIF.

ENDLOOP.


I think I'm going to post an article on this as I find this component seriously lacks some useful features.

Best regards,

Guillaume

Answers (1)

Answers (1)

hendrik_brandes
Contributor
0 Kudos

Hello Guillaume,

do you mean no operator-field visible, when you say "hide"? I did not seen this so far...

You can exclude and include the operations within the Method "GET_DEFINITION" directly for each field.

Kind regards,

Hendrik

guillaume-hrc
Active Contributor
0 Kudos

Hi,

Yes, it's the operator field that I would like to hide.

Best regards,

Guillaume