I wonder if anyone can shed any light on this JSON parsing problem.
The following file structure is handled fine by the Hierarchical stage:
Code: Select all
[
{
"reach": "national",
"profile_id": "5y2",
"First_name": "Bob",
"last_name": "Xyz",
"address": {
"zip": "ABC 123",
"country": "United Kingdom",
"city": "Windsor",
"state": "Berks",
"state_code": "BK"
}
}
]
This example is NOT handled:
[
{
"profile_id": "567",
"First_name": "Bob",
"last_name": "Xyz",
"address": {
"zip": "ABC 123",
"country": "United Kingdom",
"city": "Windsor",
"state": "Berks",
"state_code": "BK"
},
"deciles": [
{
"decile_1": 4.0,
"decile_2": 4.0,
"decile_3": 6.0,
"decile_4": 1.0
}
]
}
]
The schema library import actually works fine for both examples, the problem comes with mapping the columns.
The name and address columns map fine but, although the decile columns are displayed, they are not available for mapping.
The imported structure looks like this:
Code: Select all
JSON_Parser_Step
ns0:root
root_anon_choice_0
e2res:@@choiceDescriminator
nullValue
objectValue
address
...
...
first_name
...
...
deciles
deciles_anon_choice_0
e2res:@@choiceDescriminator
nullValue
objectValue
decile_1
.....
.....
I should also add that I have no control over the JSON structure, that is decided elsewhere.
Cheers,
Bob