How to POST Data into ERP from an Oracle Analytics Cloud workbook?

Question

Hi,

We have a workbook with a couple of tables and are looking to make a POST request to - https://fa-enqu-dev1-saasfaprod1.fa.ocs.oraclecloud.com:443/fscmRestApi/resources/11.13.18.05/dataSecurities. We've tried the data actions with type: http api using the following:

HTTP Method: POST

Enter url field - https://fa-enqu-dev1-saasfaprod1.fa.ocs.oraclecloud.com:443/fscmRestApi/resources/11.13.18.05/dataSecurities and

https://fa-enqu-dev1-saasfaprod1.fa.ocs.oraclecloud.com:443/fscmRestApi/resources/11.13.18.05/dataSecurities&SecurityContext=${valuesForColumn:XSA('152139'.'Data Access Nonprod')."Columns"."Security Context"}&SecurityContextValue=${valuesForColumn:XSA('152139'.'Data Access Nonprod')."Columns"."Security Context Value"}&UserName=${valuesForColumn:XSA('152139'.'Data Access Nonprod')."Columns"."User Name"}&RoleNameCr=${valuesForColumn:XSA('152139'.'Data Access Nonprod')."Columns"."Oracle Role Name"}

Payload Type: Raw Data

Data Payload:

{

"SecurityContext":"Asset book",

"SecurityContextValue":"AUS CORP LGAAP",

"UserName": "4972",

"RoleNameCr": "Van Asset Accountant"

}

and empty with the longer url above

HTTP Headers:

{

"Authorization": "Basic base64Encoded(<appId:password>)",

"Content-type": "application/json",

"Connection": "keep-alive",

"Accept": "*/*"

}

The error we are getting back is - Unable to parse Data Action URL (syntax error): Data Access NP.

Does anyone know a workaround for this issue?

OAC_REST_Error.PNG

Steve F-2 · Answer

Hi,

Perhaps you have already reviewed the guide, but there are a couple of key points when using POST.

* About Creating HTTP API Data Actions
* If you use a POST method, or custom HTTP header that overrides the HTTP header, the following apply:* Enter each parameter as a name-value pair with the name and value separated by "=". 
* You can use the same URL token syntax in the name-value pairs as required by the API that you're calling. For example:

paramName1=paramValue1
﻿
paramName2=${valuesForColumn:"Product"}

* A custom header works if the target of the HTTP request specifically allows the HTTP headers that you're using to be set on the request. If the headers aren't allowed, the browser blocks the request and displays an error message, for example a Cookie header, containing Content-Type=application/json will be blocked.

Other comments welcomed.