Mathias Uhlmann

Hi @tiagobalmeida , your issue description does not explain the use case which makes it hard to understand details of a solution. However, the requirement to show index and count...

Hi Fabrice, you have run into an issue that is known for some time and has several facets. An actual solution is unfortunately quite complex. This is being tracked as...

Hi, the topic of a tree binding is on our agenda but it will still take some time. The [SAPUI5 roadmap](https://www.sap.com/products/roadmaps/finder-all.html?pdf-asset=faeb805a-d07c-0010-82c7-eda71af511fa) shows the current status of planning. Please note the...

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

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

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

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

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

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.

We are discussing internally how to achieve the requested functionality without creating redundancies. This is tracked internally as CPOUI5MODELS-1111.