Forum Discussion

jhagist's avatar
jhagist
New Contributor III
8 years ago

Problem with Pipeline Parameter in Mapper Snap

I am using a mapper snap to extract data from a json schema. This is the code from the expression {id:$id}.extend($.fieldValues.map (elem => [elem.id, elem.type, elem.value])) What I want to do...
manjunathsinghs's avatar
manjunathsinghs
New Contributor II
2 years ago

Thank You, SpiroTaleski , Aleksandar_A .
With your suggestion, am able to capture all the input data coming to my pipeline.
Is there any way i can capture only invalid input data, which fails at json parser?
Thanks.

  • cjhoward18's avatar
    cjhoward18
    Employee
    5 years ago

    Hi @Henchway

    If you have the key $content mapped in your response document, that will be considered the response body, and the rest of the key/value pairs are treated as response headers.

  • asharifian's avatar
    asharifian
    Employee
    5 years ago

    Hi @Henchway,

    If you are referring to having a SnapLogic triggered task respond with a custom HTTP header value, then these are the following scenarios:

    1. If you’re using the ground URL on a groundplex, then it’s possible by having the custom value go to the $[‘content-type’] variable in a Mapper snap. Ensure your Mapper snap has a Binary output and that it’s unlinked.

    The $content variable within the Mapper will contain the response body so ensure that’s there if necessary.

    1. If you’re using the cloud URL (whether it be via a groundplex or cloudplex), this is currently not possible and only standard HTTP headers can be returned in that case.

    Thanks,

    Ali

    • Henchway's avatar
      Henchway
      Contributor
      5 years ago

      Thank you very much, i wasn’t aware that I had to use the override URL to use custom headers!

      Best regards
      Thomas