|
Jan,
What error are you getting? Something like:
invalid char in json text.
This is what I got when testing the JSON. Can you confirm? It also seems
that it's happening when trying to parse ANY node.
On Tue, Aug 16, 2016 at 10:03 AM, Jan Grove Vejlstrup <jgv@xxxxxxxx> wrote:
Hello,
I see the Bold doesn't come through. My problem is withe the two nodes
"MeasureUnit".
Best regards
Jan
Am 16.08.2016 um 16:37 schrieb Jan Grove Vejlstrup:
Hello--
I am using yajl in the version from Scott Klement to parse JSON. But I
have a problem with this one:
{
"SalesOrderNo":"000001",
"PackageQuantity":1.0,
"PalletQuantity":0.0,
"Weight":3.44,
"SalesOrderState":40,
"SalesOrderItems":
[
{
"PositionsNo":"1",
"ItemNo":"31200200",
*"MeasureUnit"{"UnitDesc":"Stück","UnitDescShort":"Stk","Uni
tCode":"01","UnitItemCount":1.0,"DecimalCount":0},*
"ItemDescription":"Granito 1 Sahara",
"SortNo":1,
"TotalQuantity":11.0,
"QuantityPicked":11.0,
"StorageLocation":"A0201 03",
"IsFloorItem":true
},
{
"PositionsNo":"2",
"ItemNo":"31200201",
*"MeasureUnit":{"UnitDesc":"Multipack","UnitDescShort":"Pack
","UnitCode":"02","UnitItemCount":5.0,"DecimalCount":0},*
"ItemDescription":"Granito 2 Sahara",
"SortNo":2,
"TotalQuantity":12.0,
"QuantityPicked":12.0,
"StorageLocation":"A0201 04",
"IsFloorItem":false
}
]
}
My problem is with the two nodes, that I have put to bold. How can I
handle those with yajl?
Best regards
Jan
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.