How do you know that the Odata service expose the association like you would expect? Is it a Mendix application exposing like that? In most cases whenintegrating with a non-Mendix oData service it is high likely a different domain model, so the exposed service (domain) is set up differently.
How I get normally oData implemented is:
1 – get just the response with Postman, by executing the oData get call including the headers
2 – based on the response of 1 ( a JSON) you can create a JSON structure and IMPORT mapping to your domain model, and create the non persistent entities based on the response
3 – Then you can do whatever you want towards the other (non) persistent objects of your choice, including the associated objects etc.
I think I've got it. Looks like you can construct it all by yourself, or just use the parent (see Query where the parent used is the PurchaseOrder.)
So I'm finally integrating a sap odata service (reverse proxy) but I'm still struggling with the association part. I use the method as described above but somehow I get a 403 error (nothing more). Funny thing is that when I get the url from debugging and put that into the browser, all works well. I included the current CSRF token as well in the call.
So, current call is: $ENTITYFROMSAP/TO_OTHERENTITYDeferred (just like the Purchaseorder example)
Anyone got an idea what could cause the problem of 403?