It seems the recordset is correctly initialized in "initializer" method of datatable-scroll:

dt.get("recordset").plug(Y.Plugin.RecordsetSort, {dt: dt});

Then in _onEventSortColumn method it seems the recordset is another one and it has not "sort" property.

dt.get("recordset").sort.sort(field, dir === DESC, sorter);

(dt.get("recordset").sort --> undefined)

Maybe DataTableDataSource plugin overwrites the recordset in onDataReturnInitializeTable method.

Workaround:

    dt = new Y.DataTable.Base({

        columnset: cols,

    }).plug(Y.Plugin.DataTableDataSource, {

        datasource: ds

    }).render("#pizza");


dt.datasource.onDataReturnInitializeTable = function (e) {

        this.get("host").set("recordset", new Y.Recordset({records: e.response.results}));

        this.get("host").plug(Y.Plugin.DataTableSort, {

            lastSortedBy: {

                field: "field1",

                dir: "asc"

            }

        });

    }

This issue also occurs without using a DataSource when setting the datatable's recordset property if the base Y.RecordSet is used.

A workaround that I use is as follows:

    // snippet from a MasterView widget that has a datatable


refresh : function() {

        var index = this.selectedRecordIndex();

var dataArray = this.getData();

        var set = new Y.Recordset({records: dataArray});

// otherwise sort plugin breaks on next column sort

        set.plug(Y.Plugin.RecordsetSort, {dt: this._dataTable});

        set.sort.addTarget(this._dataTable);

this._dataTable.set('recordset', set);

this.selectTR(index);

    }

This is a kind of "multi-inheritance" problem and I can see how it would come up quite often with any plugin that modifies RecordSet. One suggestion would be to have the DataTable itself have a reference to a RecordSet constructor and then have plugins register new constructors as added. Then we can create new RecordSets of the appropriate type by using the DT field:
eg. var newSet = new myDT.RecordSetType({records: dataArray})

Would have to chain constructor calls so not sure what issues that would raise.

Yeah, onDataReturnInitializeTable is creating a new RecordSet, which does not inherit the plugins assigned to its predecessor. Same goes for any invocation of table.set('recordset', new Y.RecordSet(...));

This ticket was marked as a duplicate of #2529872

A possibly simpler workaround:

<code>
myDT.after("recordsetChange", function() { myDT.plug(Y.Plugin.DataTableSort); });
</code>

nelson_menezes,
That would only work for the specific case of sorting. The heart of the issue is that the Recordset is replaced instead of having the existing Recordset's data replaced.