In CB data is stored as a:
- Int(“100”)
- String (“bob smith”)
- JSON(“{“data”:“yup”}”)
- base64 Binary string(“4nsou9…”)
Looks like that data is not “true” JSON and its stored in CB it as a binary base64 string.
YOUR SG
I think there is something in the JSON who is updating the doc either SDK or SG is storing it as a binary object instead of JSON, and SG is complaining.
SEEN IT BEFORE
I’ve seen it happen before on very large JSON strings ,16MB, were the JAVA App JSON encoder/decoder didn’t translate the string correctly and thus stored it as a base64 string. The funny thing was in the even though the JAVA App stored it as a base64 string it still read the object like JSON. So the encoder/decoded was imperfect both ways. In the dev environment it was stored as JSON and UAT it was a base64 string in CB. So that meant the encoding/decoding between the two environments for the same data object was different, crazy.