My Oracle Support Banner

Outbound REST Only Uses String DataType Regardless Of The Data Type Defined In The JSON Swagger File (Doc ID 2685628.1)

Last updated on JUNE 07, 2021

Applies to:

Siebel CRM - Version 19.11 and later
Information in this document applies to any platform.

Symptoms

Outbound REST calls are sending data as string even though they were described in the swagger file as numbers.


The behaviour can be reproduced as follows:

1.Use the PetStore.json from KM article "IP17 How To Set Up And Test Outbound RESTFul API Services (Doc ID 2409710.2)"

              ->  TAB: III. Generating the OpenAPI SWAGGER

                     ---> 3. Right click the SWAGGER JSON page > Save As > Save the page's content into a location and name it as: File Name: PetStore.json

   Import the JSON in Siebel Tools and generate the proxy BS REST_pet and IO "Order".


2. Simulate the request using the Siebel Client UI Business Service Simulator:

Business Service:       PRM ANI Utility Service
Method:                    CreateEmptyPropSet

Input Argument:        Hierarchy Name
Value:                       Order

This produces an empty IO at the output.


3. Click {Move to inputs} button to move this into the input for the next call


4. Edit the Order IO and provide values.  Notice the examples for string:   integer, date, integer, integer, boolean

The defined datatype from the JSON file should be respected and used, but that is not happening.

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


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