Mapper Snap with Null-Safe Access Enabled

This example demonstrates the functionality of Null safe access in the Mapper Snap.


Null safe access enabled

Download this pipeline
  1. Configure the JSON Generator Snap with the following input document:
    {
      "recordData": {
        "id": "AUTHT",
        "testCustomer360": {
          "digitalAggregate": {
            "digitalPseudo": null,
            "test_string": "com.temp",
            "test_booleant": true,
            "test_booleanf": false,
            "test_int0": 0,
            "test_null": null,
            "test_date": "2025-11-25T03:20:52.166Z"
          }
        }
      }
    }
  2. On validating, it generates a single JSON document containing a nested record with an ID of "AUTHT" and a set of test fields under the "digitalAggregate" object, including a null value, a string, boolean values, an integer, a null field, and a date.


  3. Configure the Mapper Snap with Null-safe access selected, and the following mappings:

    Mapper Snap Configuration

  4. On validating the Mapper Snap, it extracts and maps specific fields from the input document. The following output document is displayed in the output preview.
    {
      "id": "AUTHT",
      "test_string": "com.temp",
      "test_null": null,
      "test_int0": 0,
      "digitalPseudo": null
    }

The test_int1 field is dropped during transformation because it is missing in the source and therefore not see in the output. While test_null and digitalPsuedo fields with explicit values of null are retained as null values.