I have an application based off of the mobile music store example. I have cut everything down to the following in order to illustrate the problem.
I have 2 views, initial-view and detail-view.
The first view initial-view contains a listview of Ids pulled from a DataSource.
The second view performs a datasource.get on the id passed in the query string link to the view using the show event in order to grab the correct details from the datasource. However when you attempt to navigate from the listview link to the detail view, you get an immediate error after the view is shown with a #! in the url.
If you bind the initial-view listview to something else, a static array, or hard code the links to detail-view the show event and navigation to the detail-view works as expected.
Example attached.
Edit: Found that if I create another DataSource from the same original data.
If I then use that datasource in the show event of the detail-view to bind it works. Kind of a major hack though, I'd prefer to know what I am doing wrong or if this is a bug that will be fixed.
I have 2 views, initial-view and detail-view.
The first view initial-view contains a listview of Ids pulled from a DataSource.
The second view performs a datasource.get on the id passed in the query string link to the view using the show event in order to grab the correct details from the datasource. However when you attempt to navigate from the listview link to the detail view, you get an immediate error after the view is shown with a #! in the url.
If you bind the initial-view listview to something else, a static array, or hard code the links to detail-view the show event and navigation to the detail-view works as expected.
Example attached.
Edit: Found that if I create another DataSource from the same original data.
var
detailDS2 =
new
kendo.data.DataSource(
{
data:details,
schema: {model: {id:
"Id"
}}
});
If I then use that datasource in the show event of the detail-view to bind it works. Kind of a major hack though, I'd prefer to know what I am doing wrong or if this is a bug that will be fixed.