We wrote a transaction using an ALV Grid where the users didn't want to see any row marks. So when initializing the grid, we used the following:
data: gs_layout_art TYPE lvc_s_layo.
gs_layout_art-NO_ROWMARK = 'X'.
CALL METHOD gridart->set_table_for_first_display
is_layout = gs_layout_art
and it used to work just fine.
But what happened? Users want some more data on that screen, but outside the grid. That data has to be hidden sometimes. So we now work with subscreens on the main screen, one of the subscreens contains the container with the grid, and another subscreen contains the other fields.
The trouble is - when the main screen shows up for the first time, the grid shows up with rowmarks. Which is not what we want. And after we do something to the fields in the other subscreen and press 'Enter', the rowmarks disappear. It's like the grid only 'remembers' that it should have hidden the rowmarks during the first PAI...
And there has been no change to the coding of the grid, only the whole PBO was moved to the subscreen...
Any help would be appreciated.