M
marian.edu
Guest
Clearly a bug imho, all relations are defined as nested so the parser should be able to know that a 'child' node inside 'parent2' is actually a 'child2' record and also set it's parent id even if set as serialize hidden. It seems to be confused by the serialize-name which is the same for both child tables, if you change the serialize-name for child2 and update the name in the json it will yield the correct results. Even more, if you change the serialize name to the second child table to be different from 'child' the result will still be wrong because it will create one correct record in parent 2 table and one erroneous record in child 1 table with no parent id set and this should not happen. Having a 'child' property at dataset level also incorrectly creates records in the child table although those are bound to be inside of a parent node given the nested option set on the data relation. lcData = '~{"test": ~{ "parent2": [ ~{ "id": "2", "name": "parent2" ~} ], "child": [ ~{ "value": "test2" ~} ] ~}~}'. Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
Continue reading...