Project

General

Profile

Bug #9187

Multiple issues with read-json

Added by Andrei Plugaru almost 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

9187_hierarchy.p Magnifier (1.29 KB) Andrei Plugaru, 09/19/2024 07:07 AM

9187_error.p Magnifier (2.32 KB) Andrei Plugaru, 09/19/2024 07:50 AM

History

#1 Updated by Andrei Plugaru almost 2 years ago

While investigating another task, I found out there are multiple differences between OE and FWD behaviour regarding read-json for datasets.
I think that the root cause for some issues may be that the hierarchy is not preserved when reading form JsonObject.
9187_hierarchy.p test tries to show this issue.
FWD output: before {"Parent":[{"parentField":"AAA","ttChild1":[{"childField":"BBB"}],"ttChild2":[{"childField":"CCC"}]}]}
after {"Parent":[{"parentField":"AAA"}]}

OE output: before {"Parent":[{"parentField":"AAA","ttChild1":[{"id":43264,"childField":"BBB"}],"ttChild2":[{"id":43264,"childField":"CCC"}]}]}
after {"Parent":[{"parentField":"AAA","ttChild1":[{"id":43264,"childField":"BBB"}],"ttChild2":[{"id":43264,"childField":"CCC"}]}]}

Another issue, which actually could only be a consequence of the first one, is that if the buffer name exists in the dataset(no mater the current position in the hierarchy) it doesn't throw any error. In OE this error is thrown Error parsing JSON: unexpected token: string. (15360). 9187_error.p shows this issue.

Also available in: Atom PDF