Ignore error serializing JSON that can either be a text or a structure

link管理

链接快照平台

输入网页链接，自动生成快照
标签化管理网页链接

相关文章推荐

精明的台灯 · 杭州国际学校学费一年多少钱？-125国际教育· 3 周前 ·

侠义非凡的小蝌蚪 · 江苏常州首套房贷利率下限降至3.8% | 极目新闻· 5 月前 ·

爱搭讪的大蒜 · 关于温州市市本级2023年11月份符合人才购 ...· 5 月前 ·

爱玩的小熊猫 · 藤蔓玫瑰abo最新章节列表_纪年全文免费阅读 ...· 7 月前 ·

爱喝酒的牙膏 · How Slack expedites ...· 1 年前 ·

Back to Forums

Tarek Nasser Sati

Ignore error serializing JSON that can either be a text or a structure

Question

JSON

API

Hi,

I'm having trouble consuming an REST API that on the respose, has a attribute that can either be a structure, a integer or a text. Bellow there is an example of the structure returned on the API.

{
  "_embedded": {
    "transactions": [
        "id": 359890,
        "entryType": 359890,
        "properties": "553399-transfer-20180613145954"
        "id": 359891,
        "entryType": 359895,
        "properties": {
                    "AccountName": "Tarek Sati",
                    "IdempotencyKey": "acb23be8-6029-4e60-9209-4c633bf8a2c1"
        "id": 359892,
        "entryType": 359899,
        "properties": 625
    ]

It is worth mentioning that when the properties data returns a text or a integer, it has no value to me, so I can ignore this. I'm only interested in the data of the structure.

Do you guys have any idea how I can consume or convert this structure to a JSON without having errors, basically I want to ignore the serialization erros. I've tried consuming the full response as a text and then serializing to JSON, tried consuming the properties structure as a text, and tried consuming it as an structure, but failed on all the atempts.

Thanks in Advance,

Tarek

20 Oct 2021

Dorine Boudry

MVP

Hi Tarek,

I had a try, and the full text + deserialize afterwords option works.

So it's important that you actually do consume it as text, not as JSON.

And then deserialize into a structure that fits the type of response you are interested in. So this will only work if you are only interested in just one of the response formats.

I suppose, if you are interested in the others, you could deserialize 3 times, each time into a different structure, and then bring everything together again...

See attached oml.

Dorine

QDR_ApiWithToBeIgnoredData.oml

20 Oct 2021

6 replies

Last reply 21 Oct 2021

Show thread

Hide thread

Tarek Nasser Sati

Hi Dorine,

I tried your solution and got the following error:

"Failed to deserialize JSON to GetStatementResponse:
Error converting value 44516 to type 'ssContaCore.RestRecords.JSONSTPropertiesStructure'. Path '_embedded.transactions[0].properties', line 1, position 474."

20 Oct 2021

Dorine Boudry

MVP

Replying to Tarek Nasser Sati's comment on 20 Oct 2021 22:04:04

my oml is just a demonstration of how you could do it, you would of course have to adust it to your exact json structure. Can you share exact test data and your oml ?

Dorine

20 Oct 2021

Tarek Nasser Sati

Replying to Dorine Boudry's comment on 20 Oct 2021 22:06:15

I just changed to the structure that was supposed to be received, using the properties as the structure that I want. The error occured exactly in the properties attribute and it makes sense, because it tried to convert a text to a structure, it's like trying to convert a text to a boolean, it will result in an error.

Unfortunately I can't share the data and the oml.

20 Oct 2021

Dorine Boudry

MVP

Replying to Tarek Nasser Sati's comment on 20 Oct 2021 22:26:13

Ok, can you go through it in debug, and share the result of GetStatement. And also share the proporties of the deserialise and also share the structure definitions you are deserialising to.

I can think of 2 reasons :

# you do a tiny thing different than me

# Deserialise on server is less tolerant than deserialese on client

I´ ll verify the second hypotheses

Dorine

21 Oct 2021

Dorine Boudry

MVP

Oke, I can confirm that deserializing on server doesn't work.

see attached oml for showcase.

So if this is reactive or mobile, you still have the escape of doing it on client side, for traditional, you're out of luck. You'll have to somehow preprocess the text with something like regexReplace and/or forge component 'JSON tool kit', taking out all the stuff with the unwanted values.

Dorine

PS : 2 final remarks, they won't help you, but I'd like to say them

1) i think an api that has different values / structures for the same item in it, is poor design

2) I think software that has same name/look/function in the eye of the developer, behaving differently dependent on where in the architecture/stack it is executed, is poor design

QDR_ApiWithToBeIgnoredData.oml

21 Oct 2021

Dorine Boudry

MVP

Replying to Dorine Boudry's comment on 21 Oct 2021 07:07:36

As an example, I had a little try with regex_replace, see attached oml.

Mind you, this works on the one example JSON you have given, it should be tested on more examples, but it gives you an idea what I mean with 'preprocessing'.

Dorine

QDR_ApiWithToBeIgnoredData.oml