Vlocity

I got the solution.

If that particular object spec have layout and attributes mention in layout , it will give the error, just remove the attribute from the layout , it will unassigned the attribute aswell.

Thanks

Uday

@Pramod Jana, 

• Use Set Values before the Save Action and explicitly set the field to an empty value ("")
• Or use a Formula / DataRaptor Transform to send an empty string instead of null
• If the field is not text, set it to a valid “blank” value (like 0 or false where applicable)

Best practice: 

 Use a DataRaptor Load + Transform and map nulls → empty values before update. 

 That’s the only reliable way to force overwrite in OmniStudio.

*** Solution Here ***

Hi @Sakthivel M,

Thanks for replying. I managed to solve this issue. 

Here is some more details in case anyone else is facing the same issue:

• The tool was "HTTP Action" in a OmniStudio Integration Procedure. 
• The issue was that All parameters I passed as part of the payload were not being added to the JSON body and therefore not being sent over with the request. The error message I was getting in the response was: 

{
  "success": false,
  "info": {
    "statusCode": 400,
    "status": "Bad Request",
    "Content-Type": "application/json;charset=UTF-8",
    "Date": "Tue, 23 Nov 2021 21:07:49 GMT",
    "X-XSS-Protection": "1; mode=block",
    "Set-Cookie": "BrowserId=xxx; domain=.salesforce.com; path=/; expires=Wed, 23-Nov-2022 21:07:49 GMT; Max-Age=31536000;LSKey-c$CookieConsentPolicy=0:1; domain=TEST.my.salesforce.com; path=/; expires=Wed, 23-Nov-2022 21:07:49 GMT; Max-Age=31536000;CookieConsentPolicy=0:1; domain=TEST.my.salesforce.com; path=/; expires=Wed, 23-Nov-2022 21:07:49 GMT; Max-Age=31536000",
    "X-Content-Type-Options": "nosniff",
    "Cache-Control": "no-cache,must-revalidate,max-age=0,no-store,private",
    "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
    "X-Robots-Tag": "none",
    "Transfer-Encoding": "chunked"
  },
  "result": [
    {
      "message": "The request body must contain a _______ definition",
      "errorCode": "118"
    }
  ]
}

The solution was:

• • Add "Content-Type" to the Integration Procedure > Rest Options > Header. 
    • Example: "Content-Type": "application/json; charset=UTF-8"
  • Add Body Parameters as "Additional Input"

 Here is an example: