Dropdown is not longer filled correctly after upgrading to EHP1 SP19

Question

Hi there,
we had a working dropdown element integrated in an ALV which worked properly all the time. Now, after the upgrade to HP1 SP19, it offers some strange behavior.
The code below is working properly and the dropdown always offers the correct values.
But if I exchange the hard coded
and ls_zbaps_req_role-svp_unit_id = '002'
in the marked line with this
and ls_zbaps_req_role-svp_unit_id = wd_this->ALV_SVP_UNIT_ID
the dorpdown is not filled correctly.
The strange thing about this is that the table lt_value_set_rr iss filled correctl yin both cases, but with the binding to the cell editor it's get corrupted when using the attribute instead of the hard coded number. Any idea what might be the issue here?
Regards, Steffen
data:  lr_dropdown_key_rr    type ref to cl_salv_wd_uie_dropdown_by_key.
*   Get all unitnames
*    SELECT * FROM zbaps_req_role INTO corresponding fields of table lt_req_role.
    lr_node_rr = wd_context->get_child_node( name = 'INTERNAL_PERSON_DAYS' ).
    lr_node_info_rr = lr_node_rr->get_node_info( ).
*   Paste svpunit to value set of zbaps_svp_unit
    loop at lt_zbaps_req_role into ls_zbaps_req_role.
    if ls_zbaps_req_role-svp_org_id = ls_authorisations-svp_org_id
    HERE --> and ls_zbaps_req_role-svp_unit_id = '002'
     and ls_zbaps_req_role-obsolete ne 'X'.
      wa_value_set_rr-value = ls_zbaps_req_role-req_role_name.
      wa_value_set_rr-text  = ls_zbaps_req_role-req_role_name.
      insert wa_value_set_rr into table lt_value_set_rr.
     endif.
    endloop.
    wa_value_set_rr-value = '000'.
    wa_value_set_rr-text  = 'No Role Available'.
    insert wa_value_set_rr into table lt_value_set_rr.
*----- Set attribute info
   lr_node_info_rr->set_attribute_value_set( name      = 'REQ_ROLE_NAME'
                                             value_set = lt_value_set_rr ).
lr_column_internal = lr_column_settings_internal->get_column( 'REQ_ROLE_NAME' ).
lr_column_internal->delete_header( ).
lr_column_header_internal = lr_column_internal->create_header( ).
lr_column_header_internal->set_text( ls_int_per_days-req_role_name ).
create object lr_dropdown_key_rr
      exporting
        selected_key_fieldname = 'REQ_ROLE_NAME'.
lr_column_internal->set_cell_editor( lr_dropdown_key_rr ).

Answer 1

In addtion to Altenbach's comments - 
I'd recommend trying another VI function to get the power spectrum for
your signal to see if the behavior is the same.  You can find some
examples of VIs using the power spectrum functions using the NI Example
Finder.
You can go to LabVIEW's Example Finder by going to Help >> Find Examples.
Then search for FFT. There should be some results that include FFT and
Power Spectrum Units.vi, Power Spectrum Measurement.vi, Basic Spectral Measurements.vi,  and Spectrum Measurements.vi. Try opening and
running these examples to see if the VIs are returning the proper
results.
Mark Walters
Application Engineer
National Instruments