Hi Johann,
You should be able to ask your questions in the forum as we have noticed that you currently do not have support tickets included in your subscription. It is not necessary to provide detailed explanation or sensitive details regarding your implementation.
To answer your question - if you want to use the system Users type what you could do is skip using the hierarchical datasource until the limitation is removed. Instead use the Everlive SDK directly by making the necessary requests and binding them manually. Here you can see how to bind your data to a Kendo View: https://github.com/PlatformSupport/screenbuilder-kendo/blob/master/Sample%20App%20Hybrid/home/index.js
Once you get the response you can provide the option to navigate to another view which would receive the parent's Id as a parameter, make another call to the relevant content type and bind the response to the new view.
In addition, I'd suggest that you take a look into this excellent blog post on the same matter. Note the section that explains how to pass the parameters in the query string since this also seems applicable to your use case.
Another helpful resource on binding data to views in Kendo can be found here: http://blog.falafel.com/view-context-for-kendo-ui-mobile-and-mvvm/
For more information on implementing this you can view the official Kendo documentation.
You can find the API reference for the kendo.ui.mobile.View class at this link.
Let me know if this helps.
Regards,
Vasil
Telerik
You should be able to ask your questions in the forum as we have noticed that you currently do not have support tickets included in your subscription. It is not necessary to provide detailed explanation or sensitive details regarding your implementation.
To answer your question - if you want to use the system Users type what you could do is skip using the hierarchical datasource until the limitation is removed. Instead use the Everlive SDK directly by making the necessary requests and binding them manually. Here you can see how to bind your data to a Kendo View: https://github.com/PlatformSupport/screenbuilder-kendo/blob/master/Sample%20App%20Hybrid/home/index.js
Once you get the response you can provide the option to navigate to another view which would receive the parent's Id as a parameter, make another call to the relevant content type and bind the response to the new view.
In addition, I'd suggest that you take a look into this excellent blog post on the same matter. Note the section that explains how to pass the parameters in the query string since this also seems applicable to your use case.
Another helpful resource on binding data to views in Kendo can be found here: http://blog.falafel.com/view-context-for-kendo-ui-mobile-and-mvvm/
For more information on implementing this you can view the official Kendo documentation.
You can find the API reference for the kendo.ui.mobile.View class at this link.
Let me know if this helps.
Regards,
Vasil
Telerik
Everlive is now Telerik Backend Services, and is part of the Telerik Platform.