Request clarification before answering.
Entity is like a data set which holds the values in variables/properties. You first say that which is the dataset i.e. entity for the table. Then, bind the properties in that entity to the columns or rows in the table. In a view XML, you can map only one entity set for a control.
If you want to use data from multiple entities, then you have to manually set the properties to the controls in the table.
Regards,
Sharath
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
thx for you answer.
The binding works via <table [...] items="{XY}">.
All data is now visible.
Is it also possible to filter this data to only see the relevant data based on the atm viewed detail page?
I'm pretty sure this is only possible with the help of the controller, but I cant get it going.
best regards
Johannes
Hi,
i got the issue solved today. Thank you a lot for your patience and answers.
The reason was that there was no navigation property/association between the detaildata and the masterlist data in the oData Service. I got it this morning.
Best regards
Johannes
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.