We use xamDataGrid in our application and have a pretty complicated set of data, which is put inside System.Data.DataTable instance. The xamDataGrid settings allow automatic creation of field layouts.

There is a special case when xamDataGrid enters the state shown in screenshot (two sets of headers visible).

Combo boxes of column 'Hierarchy' always contain all values from column 'ets'. Combo boxes content is refreshed whenever there are some changes to column 'ets'. When we delete a row, comboboxes referencing 'ets' value being deleted are set empty.

This was the case when I deleted a row containing 'ets' value '102'. When I discarded the changes (running method Reject from System.Data.DataTable) the record which was put back into the grid, for some reason obtained FieldLayout which was different from the field layout assigned for all the rest of the grid.

Apart from the 'double header set' whole control state gets broken, for example, we cannot select records having different field layouts, so many pieces of our code start to fail.

Is there some workaround we could take, for example a way to enforce SINGLE field layout for any records entering the grid?

Is there some possible reason why a record re-entering the grid gets  field layout different from the one it had before deleting?