E1: ORCH: Unable to Use Nested Array in the Orchestration Input
(Doc ID 3032786.1)
Last updated on JULY 05, 2024
Applies to:
JD Edwards EnterpriseOne Orchestrator - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Currently, there is no option to define a Nested Array (Array inside another Array) in the Orchestrator Input.
The requirement is to create One "Header" with Multiple "Detail" which further has Multiple "Detail Pricing" under each detail and should be processed in one transaction.
Example:
------------
Pass the Orchestrator Input with Nested Array.
[Header
{Detail 1
{
Detail Pricing 1.1,
Detail Pricing 1.2,
Detail Pricing 1.3,
Detail Pricing 1.4,
},
Detail 2
{
Detail Pricing 2.1,
Detail Pricing 2.2,
Detail Pricing 2.3,
Detail Pricing 2.4,
Detail Pricing 2.5,
Detail Pricing 2.6,
}}]
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 |
Cause |
Solution |
References |