Beate
You aren't mistaken. I don't think it is possible, but it should be...
Sub Run_MoveTo
msgbox "Hit"
Run_Fields.Field("RN_RUN_NAME").IsVisible = False
End Sub
Of course that .IsVisible property is effective in other contexts, but not here. I put the msgbox in the sub to make sure it was firing when I opened a Run. I also explored Data-Hiding at the Group level and this field doesn't exist in that context.
You can do it by altering the project db/schema directly and making the field inactive. First backup the project database. Then issue the following...
For MSSQL...
update td.SYSTEM_FIELD set sf_is_active = 'N' where sf_column_name = 'RN_RUN_NAME'
update td.sequences set sq_seq_value=sq_seq_value+1 where sq_seq_name='fields_version';
update td.sequences set sq_seq_value=sq_seq_value+1 where sq_seq_name='lists_version';
update td.sequences set sq_seq_value=sq_seq_value+1 where sq_seq_name='tree_version';
For Oracle...
update SYSTEM_FIELD set sf_is_active = 'N' where sf_column_name = 'RN_RUN_NAME'
update sequences set sq_seq_value=sq_seq_value+1 where sq_seq_name='fields_version';
update sequences set sq_seq_value=sq_seq_value+1 where sq_seq_name='lists_version';
update sequences set sq_seq_value=sq_seq_value+1 where sq_seq_name='tree_version';
Note, the first statement changes the value for the field so its not active.
The following three statements update the sequences so the change will be seen in the project. If we don't issue these the field will still be visible even after we issue the first line where the change is made.
Then bounce the ALM service to refresh server cache. This is because the sequences are cached at the server. Alternatively you can remove the project (careful not to delete!) and restore the project by pointing to the project's dbid.xml file. Either will refresh the server cache.
Phil