Hello @Debayan Chanda ,
Sorry for the delayed reply I missed the initial mention, and I am just now seeing this question.
I moved your comment to a new thread from the original post to give it individual attention, The original post for referance:
First question is if you are still running into the error, as its been a while since you were working on this one or were you able to resolve this one?
Next looking a the error you are encountering and giving some context:
Can not deserialize instance of java.lang.String out of START_OBJECT token
This error will generally be triggered due to a formatting error in payload, like an incorrect spelling in a package item i.e. using "field" instead of "fields" or using an incorrect package formatting for the document type like using the old format/server format of "{"lead":{"key":"user_name"}}" where the new formatting would look for "{"lead":"user_name"}"
A really good resource we have put together for troubleshooting the doc format packages can be found at the following links, the first one is a package validator where you can drop the doc formatted JSON to verify the formatting and see what it will look like rendered, the second link is a WYSIWYG editor that lets you build out a formatted text field using the new editor and will output the doc formatting in the correct JSON that can be copied and dropped to the API call as an Example if you were updating the Description field build out the description table in the Builder and add it in like this:
{
"fields": {
"description": {
paste DOC formatted JSON content here
}
}
}
The document builder will help take all the guess work out of the package formatting for things like tables. But let me know if this helps out or if you are still running into any errors, and if so post the data package and what endpoint your hitting and I can take a closer look.
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.