oData Tree Binding support for OData v4

[HeneryHawk]

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?

[uhlmannm]

Hi,

the topic of a tree binding is on our agenda but it will still take some time. The SAPUI5 roadmap shows the current status of planning. Please note the legal disclaimer in the roadmap document, e.g.

All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

Best regards Mathias.

[HerzogIgzorn]

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:

https://openui5.org/releases/

I will close this issue.

Regards Sebastian

[HeneryHawk]

Hi Sebastian, Thank you so much for your answer. Too bad, then we have to continue using OData v2.

Best regards

[boghyon]

The new roadmap doesn't seem to mention the V4 tree binding anymore. Is it still in the roadmap?

[uhlmannm]

@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 Mathias.

[betterharderfasterstronger]

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

[betterharderfasterstronger]

PS: why was this issue closed ?

[uhlmannm]

@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 sap.ui.model.odata.v4.ODataListBinding#setAggregation / $$aggregation. That journey is far from over and the remaining "round-offs" will cause a significant amount of development effort still. Another topics that we have been working on is the data synchronization in a master-detail scenario, which is of particular importance with the flexible column layout. Here you may refer to "Extending the Lifetime of a Context that is not Used Exclusively by a Table Collection" in Data reuse or sap.ui.model.odata.v4.Context#setKeepAlive. Also that story is not finished. On the horizon is the "deferred delete", i.e. the possibility to use sap.ui.model.odata.v4.Context#delete also for API groups, i.e. deferred. This is a clear gap when providing non-Draft applications with the OData V4 Model. And so on. There are so many clear gaps ... In the end not everything can be done. In particular, trying to provide the tree binding in parallel to the data aggregation would be bound to fail (with the current capacity).

Sorry for the bad news! Best regards Mathias.

[boghyon]

@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.

[ramondebeijer]

Why closed? Decent support for odata V4 is a must have feature in my opinion

[uhlmannm]

@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. What would be the benefit of keeping this issue open?

Best regards Mathias.

[boghyon]

What would be the benefit of keeping this issue open?

GitHub is the only open platform for non-SAP employees to learn about open issues. I cannot speak for all GitHub users, but for me, an open issue signals that the topic is not abandoned. Also less people will be confused why this issue is closed.

How about reopening this issue but locking the conversation?

[uhlmannm]

Locking the conversation does not seem a good idea to me.

Best regards Mathias.

[ramondebeijer]

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?

[uhlmannm]

The roadmap does not go far enough into the future, I fear. :(

Best regards Mathias.

[codeworrior]

The official roadmap for OpenUI5 at least mentions "OData V4 model / Tree support".

[uhlmannm]

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.

[boghyon]

@yanaminkova Any reasons for closing this issue?

[jcailan]

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.

[ThomasChadzelek]

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.