This project has moved and is read-only. For the latest updates, please go here.


Error when nested object is null


I am currently looking in to implementing a solution where I collect some GPS data from a web service. I have been testing your component with success on smaller and simple extract of data.

I now meet an issue when extracting data where the nested values does not exist.(null)

My file looks like this:

Downloaded: {
"list": [
  "id": "18389",
  "serialNumber": "20649596",
  "phoneNumber": "45555-555-55",
  "vehicleType": "Car",
  "deviceType": "Trackunit",
  "deviceModel": "ME301",
  "name": "Car 0211 ",
  "displayName": "Car 0211 ",
  "note": "",
  "createdAt": "2009-01-01T00:00:00Z",
  "input1Name": "Poweroutlet",
  "input2Name": "Ignition",
  "input3Name": "Input3",
  "input4Name": "Input4",
  "gpsFixTime": "2016-10-17T13:43:55Z",
  "messageTime": "2016-10-17T13:43:55Z",
  "location": {
    "latitude": 56.000000,
    "longitude": 12.000000
  "altitude": 0,
  "heading": 107,
  "speed": 79,
  "address": {
    "country": "DK",
    "zipCode": "9600",
    "city": "Helsingør",
    "streetAddress": "Kildevejrupsvej 11"

Sometimes I get null back on location and address which are nested, and then the source component cannot run when I have selected these fields to RawJson, which is a requirement since I would need to use Json Filter to lookup these fields.

Is this something you are aware of and do you have a workaround or an idea of what it will take to fix?
Closed Nov 24, 2016 at 3:12 PM by webking


danielhitch wrote Oct 27, 2016 at 9:36 AM

It sounds similar to an issue that I had with NULL or Blank fields in JSON.

I got around the issue by doing a Conditional Split on the NULL fields and then performing a Union All at a later stage to bring the NULL data back in.


webking wrote Oct 27, 2016 at 7:10 PM

Yes I confirm, that happens because some of the nested lines are null. So the componnt fails to detect those. Future release will also take into account this problem.

webking wrote Nov 7, 2016 at 12:47 AM

Latest version should fix the problem. Please give it a try!