search

SAP / openui5

OpenUI5 lets you build enterprise-ready web applications, responsive to all devices, running on almost any browser of your choice.
http://openui5.org
Apache License 2.0
2.97k stars 1.24k forks source link

oData Tree Binding support for OData v4 #2728

Open HeneryHawk opened 5 years ago

HeneryHawk commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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

Best regards

boghyon commented 3 years ago

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

uhlmannm commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

PS: why was this issue closed ?

uhlmannm commented 3 years ago

@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 commented 3 years ago

@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 commented 3 years ago

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

uhlmannm commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

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

Best regards Mathias.

ramondebeijer commented 3 years ago

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 commented 3 years ago

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

Best regards Mathias.

codeworrior commented 3 years ago

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

uhlmannm commented 3 years ago

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 commented 3 years ago

@yanaminkova Any reasons for closing this issue?

jcailan commented 1 year ago

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 commented 1 year ago

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.

denislutz commented 3 months ago

Hey Guys, since over a year passed by again, I would appreciate it a lot if some one could tell if the odatav4 is being or will be supported soon by the TreeTable component.

If not, what is road map for it? What I see in the doc is a sample without v4 https://ui5.sap.com//#/entity/sap.ui.table.TreeTable

We have a fiori freestyle app, thats why fiori elements annotations is also not really a choice for us.

Thanks in advance...

uhlmannm commented 3 months ago

Hi @denislutz,

there is a straightforward and a more complicated answer. Last time I asked, the sap.ui.table.TreeTable was not supported for OData V4. An up to date answer needs to be provided by the respective PO who is on vacation starting this week.

If your question is more about general hierarchy support. The answer is a bit longer. First of all, there is support by the v4.ODataModel, see Data Aggregation and Recursive Hierarchy, and also by Fiori elements V4, in particular including the Table building block.

That by itself will not be of much help without a backend supporting it as well. As the example requests listed in Data Aggregation and Recursive Hierarchy highlight we use the OData Extension for Data Aggregation Version 4.0 plus some SAP specific extensions (additional annotations, the TopLevels transformation) and the specific requests need to be processed as specified.

As explained at UI5con, see UI5con 2024, the backend hierarchies support is currently available only by RAP (ABAP RESTful Application Programming Model) in read-only mode. It is not completely clear, when hierarchy maintenance will also become available with RAP. The last that I heard was the 2502 release to come out next February. However, that may still change. On the CAP side there is nothing available yet.

As to the point of not having annotations: For hierarchies some of the annotations are evaluated by the v4.ODataModel. Which annotations are required is described in Data Aggregation and Recursive Hierarchy. Having these annotations is mandatory but with RAP they also come out of the box.

Best regards Mathias.

simlin commented 2 months ago

CPOUIFTEAMB-2418

denislutz commented 2 months ago

For the one who are interested, meanwhile I gave it up to wait for the odata4 support, I just transfer the response to a json model and have my freedom.