Skip to Content
avatar image
Former Member

Bug in OData Backend Navigation into external Services

If someone knows any workarounds to these bugs, I'd be glad to hear about them.

Here are the bugs:

1. navigation into entities of external services doesn't work if the primary entity lies in the external service (although in the external assoziation wizard there are fields that would only make sense if it would work, and debugging it, the code looked like it was supposed to be implemented - so it definately is a bug)

2. the $expand-feature doesn't work on navigations to entities from external services

We are heavily using OData-Services in our development and continue to experience difficulties with navigation into external services. We want to be able to transport some base services without dependancies to some more specific services, which is why we did split the services up into multiple packages. We can handle the navigation into external services without having dependancies in the wrong direction, so it's a pitty, that there are a few bugs left.

The only workarounds to these bugs - as far as I know - is to not split up the services, so there's no external service anymore. Or in case of the first bug, you can always switch the primary and dependant entity (has nothing to do with cardinality) - though in that case, sometimes, you have to add unnecessary attributes to the dependant entity to match on, so that the navigation works properly.

Some technical infos:

About the first bug:

Within the method '/IWFND/IF_MGW_MDL_COMPOSITION~RESOLVE_NAVIGATION' (class: /IWFND/CL_MGW_MDL_MDL_COMPOSITION) it misses to match the foreign key - so an error is thrown (error: /IWFND/CM_MGW062).

About the second bug:

Within the method 'GET_ENTITY_BY_ID' (class: /IWBEP/CL_MGW_ODATA_MODEL) the internal table 'mt_entities' misses entries for external entities - so an error is thrown (error: /IWBEP/CM_MGW_RT/105).

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers