Test for grid with one list field - this is the case that would need config if admit container types like Employees on list controller - it is true that is more clear with grid but the types make no sense: a list of complex whose only field is a list..why not a single list directly ? Required [element], Single Occurrence, with Simple Type [inline-Form-date] localName is [date] without namespace Required [element], Multiple Occurrence, with Complex Type [RowSimple] localName is [Simple] without namespace Required [element], Multiple Occurrence, with Complex Type [RowComplex] localName is [Complex] without namespace Required [element], Multiple Occurrence, with Complex Type [RowSimple] localName is [SimpleNoGrid] without namespace Required [element], Multiple Occurrence, with Complex Type [RowComplex] localName is [ComplexNoGrid] without namespace Required [element], Multiple Occurrence, with Simple Type [inline-Form-SimpleDirect] localName is [SimpleDirect] without namespace Required [element], Multiple Occurrence, with Complex Type [RowComplex] localName is [ComplexDirect] without namespace Test for grid with one list field - this is the case that would need config if admit container types like Employees on list controller - it is true that is more clear with grid but the types make no sense: a list of complex whose only field is a list..why not a single list directly ? Required [element], Multiple Occurrence, with Complex Type [Address] localName is [rows] without namespace Required [element], Single Occurrence, with Simple Type [inline-Address-Street] localName is [Street] without namespace Required [element], Single Occurrence, with Simple Type [inline-Address-city] localName is [city] without namespace Required [element], Multiple Occurrence, with Simple Type [inline-RowSimple-rows] localName is [rows] without namespace