cancel
Showing results for 
Search instead for 
Did you mean: 

DDLB in model node attribute

Former Member
0 Kudos

Hi All!

What generates the drop down list box input help for a model attribute? There is no get_v method generated for the attribute, but in the screen there is a DDLB.

For example in the 'ApptSQ' view of the 'BT126S_APPT' component for the 'Struct.Process_Type' attribute of the 'BTQACT' model node there is no 'get_v' method generated, but if I call this screen in the WEB Client somehow a DDLB is generated.

The problem is that there is no value in this drop down list box.

Please help, where the search help is genereated for this attribute?

Thank you very much.

Regards,

Attila

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Attilla,

In case of search view, the implementation would be in the GET_DQUERY_DEFINITIONS method of the view controller(_IMPL class). You can also find the GET_V method for the corresponding attribute in the view controller itself.

Thanks & Best Regards,

Leon

Former Member
0 Kudos

Thank you Leon.

It is a little confusing, that the "get_v" methods for model node attributes are reside in the _IMPL class, but for the value node attributes these methods are in the _CNXX class.

Can you please tell me the reason for it?

Regard,

Attila

0 Kudos

Hi Attila,

In case of search query views, this is how the query field definitions are defined. The method GET_DQUERY_DEFINITIONS has been provided by the framework in the class CL_BSP_WD_ADVSEARCH_CONTROLLER which will be a super class for the search view controller. Whenever required, this method would be redefined in the subclasses/view controller in order to define the search query fields. Since the GET_V methods are to be explicitly called in the GET_DQUERY_DEFINITIONS method, it would be convenient to define them in the IMPL class itself.

So there need not be any confusion when it comes to search query views.

Thanks & Best Regards,
Leon

Answers (0)