Openui5: UI5 cannot detect the expanded property

[mjza]

OpenUI5 version: 1.71.4

Browser/version (+device/version): Latest version of chrome.

I defined a list like the following:

<List id="list" width="auto"
    items="{ path: '/CategorySet', parameters: {expand: 'CategoryType,Status,Articles'}, filters: [{ path : 'CategoryType/Name', operator : 'EQ', value1 : 'Frei'}] , sorter: { path: 'Name', descending: false }, groupHeaderFactory: '.createGroupHeader' }"
    busyIndicatorDelay="{masterView>/delay}" noDataText="{masterView>/noDataText}"
    mode="{= ${device>/system/phone} ? 'None' : 'SingleSelectMaster'}" growing="true" growingScrollToLoad="true"
    updateFinished=".onUpdateFinished" selectionChange=".onSelectionChange">

Despite I have expanded CategoryType but the filter will causes the following error:

MockServer: navigation property 'CategoryType' was not expanded, so Property 'Name' not found -

I used WebIDE and the project is a simple Master-Details project from the template ones in WebIDE!

Any suggestion?

[tsanislavgatev]

Hello @mjza,
Can you please provide us jsBin example or example of the json you are using with the date formats and etc.
It will be helpful to have this information when looking at the problem.

[mjza]

@tsanislavgatev Unfortunately have no time to do that. You can just make simple metadata with 2 entities, that have a navigation in between and then try to apply the filter on the expanded element.

[boghyon]

Here is a small sample: https://embed.plnkr.co/DxnjUkYGxBO0oUMv?show=view%2FApp.viewl.xml,preview
After filtering by "Ca", mock server logs the error saying that the 'FlightCarrier' was not expanded, even though the list binding has expand: 'FlightCarrier'.

[mjza]

Related question in Stack Overflow.

Thanks a million @boghyon

[tsanislavgatev]

Hello @mjza ,

Thank you for sharing this finding also @boghyon thanks for the example. I've created an internal incident 2070331558. The status of the issue will be updated here in GitHub.

Regards,
Tsanislav

[michawai]

Hi @mjza,
This is a mockserver limitation.

[mjza]

@michawai We already know it is a limitation by mockserver, and we hope they solve it soon.