New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oData Tree Binding support for OData v4 #2728
Comments
Hi, the topic of a tree binding is on our agenda but it will still take some time.
Best regards |
Hi, I assume that this is probably not the answer you were expecting. As for now, we are unable to provide further details due to legal reasons. Please stick to the "What's new" and "Roadmap" sections at: I will close this issue. Regards Sebastian |
Hi Sebastian, Best regards |
The new roadmap doesn't seem to mention the V4 tree binding anymore. Is it still in the roadmap? |
@boghyon, the V4 tree binding is still on the agenda. However, with the current capacity of the team working on the OData V4 model it seems unrealistic that we will be able to work on the V4 tree binding this year. Best regards |
sap.m.Tree and sap.ui.table.Tree are first-class elements in the Fiori guidelines: https://experience.sap.com/fiori-design-web/tree/. However they only work with Odata V2. The official recommendation in general is to use Odata V4. So this clearly is a huge gap. Without working tree elements based on Odata V4 how is one supposed to implement visual, interactive support for hierarchical data ? The world is not flat. BR, Alex |
PS: why was this issue closed ? |
@betterharderfasterstronger , I agree that the tree is important. Unfortunately the same can be said about other topics (data aggregation, data synchronization, deferred delete, ...). We had set out last year to continue the work on the data aggregation topic, see e.g. the What's New entries related to Sorry for the bad news! |
@HerzogIgzorn @uhlmannm I see more and more requests for the V4 TreeBinding from the community. I think this issue should be reopened until the support is there. |
Why closed? Decent support for odata V4 is a must have feature in my opinion |
@ramondebeijer and @boghyon : We are tracking this internally in Jira (FIORITECHP1-3388, FIORITECHP1-5603, FIORITECHP1-5604). The importance of the topic is also clear but, as stated in March, the capacity for working on the topic is not there. Best regards |
GitHub is the only open platform for non-SAP employees to learn about open issues. How about reopening this issue but locking the conversation? |
Locking the conversation does not seem a good idea to me. Best regards |
If it is still on some roadmap/backlog i dont mind closing this, is there a ( rough) overview/roadmap somewhere we can follow? Obviously without any hard dates? |
The roadmap does not go far enough into the future, I fear. :( Best regards |
The official roadmap for OpenUI5 at least mentions "OData V4 model / Tree support". |
The pdf has been replaced by another tool. The current roadmap can be seen at https://roadmaps.sap.com/board?PRODUCT=73554900100800001361&range=CURRENT-LAST. |
This comment was marked as resolved.
This comment was marked as resolved.
As more and more customers upgrade their system to S4HANA, and therefore, more adoption of BTP, this missing feature becomes all the more needed. Hopefully, this issue get's reopened, and we could see some updates about this. I wish to see this feature to be realized at least before I retire from my SAP career. |
Fear not! There is hope ;-) Please refer to https://openui5.hana.ondemand.com/api/sap.ui.model.odata.v4.ODataListBinding#methods/setAggregation and the "hierarchyQualifier" mentioned there. Note that this is an experimental API so far. |
The oData v4 model is now available for a while. But unfortunately it is not yet possible to create a tree binding for the oData v4 model.
To use the Gantt-Chart 2.0 or the TreeTable with the oData v4 model it is mandatory to support tree binding.
Are there plans when this will be supported?
The text was updated successfully, but these errors were encountered: