Extract Variable from ODATA API

svenhuberti — Tue, 24 May 2016 14:36:44 GMT

Hello all,

I went through the very good guide from Holger in order to get started with HCP SAP APIM.

In order to create a custom dashboard, I would like to retrieve some information from the response of the SalesOrderSet resource, using an ExtractVariables policy, combined with a Statistics Collector Policy.

Here is the XML response I get for a specific SalesOrder:

<?xml version="1.0" encoding="utf-8"?>

<id>https://SAPES4.SAPDEVCENTER.COM:443/sap/opu/odata/iwbep/GWSAMPLE_BASIC/SalesOrderSet('0500000000')</id>

<title type="text">SalesOrderSet('0500000000')</title>

<m:properties>

<d:SalesOrderID>0500000000</d:SalesOrderID>

To extract the SalesOrderID, I configured my ExtractVariables policy as follows:

<Source clearPayload="false">response</Source>

<Namespace prefix="d">http://schemas.microsoft.com/ado/2007/08/dataservices</Namespace>

<Namespace prefix="m">http://schemas.microsoft.com/ado/2007/08/dataservices/metadata</Namespace>

</Namespaces>

<XPath>//d:SalesOrderID</XPath>

</Variable>

</XMLPayload>

</ExtractVariables>

However, when saving and updating the proxy, I get the following error message:

[Request ID: c27460bb-74f4-427f-a8b7-637f3be0db38]

Policy content for policy "SalesOrderID" is invalid. cvc-complex-type.2.4.d: Invalid content was found starting with element 'Namespace'. No child element is expected at this point.

IMHO, my policy is in line with the documentation SAP API Management

My workaround is pretty easy (XML-to-JSON, and then using a JPath) but I would like to see this working natively.

Thanks for any help!

Sven

Re: Extract Variable from ODATA API

Elijah_Martinez1 — Wed, 25 May 2016 02:10:38 GMT

Hi Sven,

At the risk of showing my ignorance in a public place as to XML and the like, it seems that cvc-complex-type.2.4.d is an XML schema validation issue (hence why JSON works).

If in fact you remove the namespaces, it will clear up the error (but you will now have the issue of creating an XPath to the element).

I believe this is an issue with the parser being quite strict, as I tried to same scenario with a simpler OData response (from http://api.openweathermap.org ) and was able to extract variable on a field (tested with country) successfully.

I know this doesn't totally help, but perhaps it can lead to some ideas of what to do next.

topic Extract Variable from ODATA API in Application Development and Automation Discussions

Extract Variable from ODATA API

Re: Extract Variable from ODATA API