Invalid navigation short dump in extended ODATA service with expand & filter

[Priyanka_Vana]

Hello,

I created an ODATA project by extending API_PRODUCT_SRV service using SEGW. A new entity type is created using DDIC object import. Association is created between A_Product entity and the new Z entity with 1:1 cardinality.

When a filter is applied on the expanded entity as below, there is a short dump.

SAP has provided a work around for this scenario in case of services generated by MDS approach. Below are some of the blogs and documents in sap help portal I referred to.

Using Query Options for Executing SADL-Based Gateway Services | SAP Help Portal

Optimized $expand with SADL and Non-SADL Entities | SAP Help Portal

Handling OData Navigation | SAP Help Portal

https://answers.sap.com/questions/306661/ui5odata-filter-on-deep-entity.html?childToView=308923

https://answers.sap.com/questions/12239082/odata-entity-association-from-cds-view--cxsadlcont.html

https://blogs.sap.com/2019/11/27/sadl-handling-odata-navigation-without-association/

https://answers.sap.com/questions/71178/unable-to-find-ifsadlgwquerycontrol--setqueryoptio.html

After referring to these documents, I understood that solution is provided only for MDS based generated gateway services. (I might be wrong as well)

Is there any way to bypass this navigation error in RDS(Referenced data source approach) generated gateway services? The method "if_sadl_gw_query_control~set_query_options" is not available in my DPC class and only "CL_SADL_GW_DPC_HELPER=>GET_QUERY_OPTIONS_ENTITY_SET" is being called in my DPC method where there is a chance to remove navigation info. But, the interface method is not available in DPC class to redefine the logic.

Any kind of clue or help is highly appreciated!

Thanks,

Priyanka.

[Priyanka_Vana]

Thanks Andre for your advice.

I followed your blog and created an extended Odata service to API_PRODUCT_SRV. I used your program to generate extended SADL xml code and updated DPC_EXT, MPC_EXT methods. I could see all the entity types inside the service.

I created a navigation/ association from A_Product and Z-cds view with 1..1 cardinality.

When I used expand with filter it resulted a short dump very similar to the ABAP based code implementation.

As I could not found this newly created association inside the DPC, MPC methods, I updated the DPC & MPC methods by adding this association manually by adding the following line. That also gave an HTTP 500 error.

It would be great if you share information on how to create a navigation link between A_Product and Z entity type?

Regards,

Priyanka.

[Andre_Fischer]

Would it be possible to use a CDS view to extend your RDS based OData service?

Then my following blog post might be of help for you:

https://blogs.sap.com/2021/12/08/how-to-redefine-rds-based-odata-services

Kind regards,

Andre