Renderer Being Called Different Based On Column Order

Running into a wierd renderer rendering issue. Before I submit as a bug I wanted to post here to see if anyone could see an obvious mistake.

Below, very similar code, two records being returned. Second record has a value for 'c', both records have a value for 'd'.

Scenario 1:

Code:

{text: 'id'  , dataIndex  : 'id'  , flex  : 1 },
{text: 'a' , dataIndex : 'a' , flex : 1},
{text: 'b' , dataIndex : 'b' , flex : 1},
{
    text: 'c' ,
    renderer: function  (value, meta, record) {
        return (record._c. data.cName );
    },
    flex : 1
},
{
    text: 'd' ,
    renderer: function  (value, meta, record) {
        console  .log(record);
        return (record._d.data.dName );
    },
    flex : 1
}

'C' has values in Row 1, but not Row 2

'D' has values in both Row 1 and Row 2. Only row 2 is rendered to the screen.

Scenario 1:

Code:

{text: 'id'  , dataIndex  : 'id'  , flex  : 1 },
{text: 'a' , dataIndex : 'a' , flex : 1},
{text: 'b' , dataIndex : 'b' , flex : 1},
{
    text: 'd' ,
    renderer: function  (value, meta, record) {
        console  .log(record);
        return (record._d.data.dName );
    },
    flex : 1
},
{
    text: 'c' ,
    renderer: function  (value, meta, record) {
        return (record._c. data.cName );
    },
    flex : 1
}

'C' has values in Row 1, but not Row 2

'D' has values in both Row 1 and Row 2. BOTH rows are rendered to the screen.

***The only major difference between the two code bits is the order​ of the rows.

Renderer Being Called Different Based On Column Order