Why is the attribute that is defined as a Number showing a exponent rather than a number when I update it using Workato?

Question

We observe inconsistent behaviour in the integer datatype display in the Reltio UI.  When the data gets loaded to an attribute of 'Integer' datatype through Reltio UI and Reltio Console Dataloader, the integer data gets displayed as expected.

Output in UI

However, when we load the similar data into the 'Integer' datatype using Reltio Integration Hub, we see exponent part being appended in the data as shown in the screenshot.

The definition in the Workato recipe was:

Answer

If you execute

   POST: https://dev.reltio.com/reltio/api/6A0FmzzDdzgPbqa/entities?options=partialOverride

 Request Body:   

   "attributes": {
      "PermanentEquity": [{
          "value": 13345678900.98
      }],
      "Name": [{
          "value": "abcq"
      }]
   }

 The result returned was "1.234567890098E10".

However, if you execute the same API and use the following request body.

[{
   "type": "configuration/entityTypes/Transaction",
   "attributes": {
      "PermanentEquity": [{
          "value": "13345678900.98" <<<===
      }],
      "Name": [{
          "value": "abcq"
      }]
   },
   "crosswalks": [
      {
         "type": "configuration/sources/IDL",
         "value": "ABC",
         "sourceTable": "Transaction"
      }
   ]
}]

The result obtained produces the full number response.

"PermanentEquity": [
   {
      "type": "configuration/entityTypes/Transaction/attributes/PermanentEquity",
      "ov": true,
      "value": "13345678900.98",
      "uri": "entities/0SxHBo5/attributes/PermanentEquity/q85rpLn"
   }
]

To apply the quotes in the Reltio API in Workato, the following change should be made.

• Make sure that L3 configuration definition should defined as float.
• If L3 configuration is defined as a number, then change the recipe to use ".to_s" in Workato.