Openui5: odata tutorial, step 5: works against mockserver, fails with real backend

[AndreaBorgia-Abo]

OpenUI5 version: 1.80

Browser/version (+device/version): Firefox / Chromium

URL (minimal example if possible): https://services.odata.org/TripPinRESTierService/(S(id))/People?$count=true&$select=Age,FirstName,LastName,UserName&$skip=0&$top=10

Steps to reproduce the problem:

1. as suggested in step 2 of the tutorial, implement the changes needed to work with a real backend and verify it functions correctly
2. test step 5 against the mockserver
3. test it again against the real backend

What is the expected result?
step 5 works in both cases, just like step 2

What happens instead?
step 5 works only against the mockserver

Any other information?

• thread on StackOverflow
• the minimal example above is what step 5 sends to the backend, resulting in an error message; according to ODATA docs, that request should be valid but in practice it isn't. I'm not totally sure this is a problem with UI5, for example in the way the URI is generated, but it sure is weird that an official test service fails like that.

[dimovpetar]

Hello @AndreaBorgia-Abo ,

Thank you for sharing this finding. I've created an internal incident 2070390646. The status of the issue will be updated here in GitHub.

Regards,
Petar

[Zwaartekracht]

Hi dimovpetar,

the problem comes from the service it seems the $count does not interact here with $select/$skip & $top. This is something a service should. I will double check with some colleagues why the TripPin service currently does not work as it should.

Regards
Silke

[ThomasChadzelek]

Hello!

This is a known issue with the TripPinRESTierService. We try to use our channels towards Microsoft to see if we can get it fixed.

Best regards,
Thomas

[ThomasChadzelek]

Microsoft has confirmed the issue: "This was due to an error in the version of the OData WebAPI library we were using in the backing service. I have an update with various fixes, including updating to the latest WebAPI library that contains this fix, that I just haven't pushed out to production yet. Let me see when if I can get that deployed." Not sure how long it will take for the fix to be deployed, but there's nothing we can do from SAP side here. Thus I'm closing the issue. Thanks for reporting it!