My Oracle Support Banner

E1: ORCH JSON Parse Issue with Orchestration calling Orchestration, then Passing Second ORCH Result to REST Connector (Doc ID 2585243.1)

Last updated on JUNE 26, 2020

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

 

Orchestration response JSON was getting send out in a JSON format.  After upgrade of tools release (9.2.3.4), the "(double quote) is replaced with {".

Example:
   "step": "FREQ_P55OR004_SalesOrderPreValidation",
vs
    {"step":"FREQ_P55OR004_SalesOrderPreValidation","

 

Error:
---------


Another example was with arrays where the Json is being generated like this without the square brackets []:

{
 "correlationId": "1",
 "contractRegion": "1",
 "contractNumber": "1234",
 "assetsList": [
   {
     "assetId": "aaa"
   },
   {
     "assetId": "bbb"
   }
 ]
}

When it should be generated like this with the square brackets []:
[{
 "correlationId": "1",
 "contractRegion": "1",
 "contractNumber": "1234",
 "assetsList": [
   {
     "assetId": "aaa"
   },
   {
     "assetId": "bbb"
   }
 ]
}]

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.