Dealing with complex JSON & CRUD

[Steven]

I have a web service that returns something similar to this

{ "RowSet": {

        "Key": "7256bd2d-879f-494b-a7c0-f0d6ed2eba84",

        "Rows": [

            { "RowNum": 1, "Name": "Fred", "Value": 123 },

            { "RowNum": 2, "Name": "Mary", "Value": 323 },

            { "RowNum": 3, "Name": "John", "Value": 732 },

            { "RowNum": 4, "Name": "Sue", "Value": 895 }

        ]

    }

}

In a data source, I bind to RowSet.Rows, but I need the Key field to be part of the rows in order to enable CRUD operations.

ideally, I would like to specify something like this:

schema: {

    data: "RowSet.Rows",

    model: {

        id: "RowNum",

        fields: {

            Key: { editable: false, type: "string", path="..\Key" or path="this.parent().Key" }

            RowNum: { editable: false, type: "number" },

            Name: { editable: true, type: "string" },

            Value: { editable: true, type: "number" },

        }

    }

Is this possible in some way?

[Alexander Valchev]

Hi Steven,

Currently the dataSource does not support nested structures and for that reason I am afraid the scenario that you described is not possible.

This functionality is of a high priority and its implementation is already planned for future versions of the framework.

Regards,
Alexander Valchev
the Telerik team

[Steven]

That is great news!    I look forward to the next release.    Thanks.

[Alexander Valchev]

Hello Steven,

After reviewing your case with the developer team, it seems that your requirement is not connected with the hierarchical dataSource and is not going to be implemented in the next release.

It may be a good addition to the dataSource component though, that is why we will appreciate if you submit it at our user voice page. Thus way the other users would be able to evaluate the idea and cast their votes for it. If it turns out to be popular, we will consider it for one of the future versions.

Please accept my apologies for the inconvenience that my previous reply may caused.

Kind regards,
Alexander Valchev
the Telerik team