Forum Discussion

vaidyarm's avatar
vaidyarm
Contributor
6 years ago

How to approach when we have array of data to be distributed as key value paired array

Hi, I am running lot of iterations, but not able to find the solution for below case : Case : Input is an array like below : { "olditem": [ { "id": "1" }, ...
Sharique's avatar
Sharique
New Contributor
5 years ago
Copy LinkReport

Hi,

For others who are in the same boat, this is the response from the SnapLogic support team.

The list provided in the documentation is for reference purposes and only the major objects are supported and not all objects, therefore I will raise an enhancement. I will submit the enhancement request on your behalf for this feature to be considered to be included into a future release.

  • winosky's avatar
    winosky
    New Contributor III
    5 years ago
    Copy LinkReport

    Hi @fmdf, depending on the destination if it’s another db usually it could take care of it without the conversion but if it’s to excel then I would try using an execute snap and converting it within the execute snap or if that’s not an option maybe look into the match data type option in the select snap maybe.

    • fmdf's avatar
      fmdf
      New Contributor III
      5 years ago
      Copy LinkReport

      It chokes because the source is bit and the destination is bit. It is converting bit to string and then when it tries to insert into the target, it fails.

      I have it working with a mapper but it seems like they should stop converting bit to string.

  • bojanvelevski's avatar
    bojanvelevski
    Valued Contributor
    5 years ago
    Copy LinkReport

    Hi @fmdf ,

    I can think of two solutions:

    1. You can cast the value while reading in your query => SELECT CAST(field AS int)
    2. Use a Mapper with a ternary operator within SnapLogic => $field == ‘true’ ? 1 : 0

    Regards,
    Bojan

    • fmdf's avatar
      fmdf
      New Contributor III
      5 years ago
      Copy LinkReport

      Thank you for the suggestions.

      I am doing the mapper solution now.

      Why should I have to cast a field as int when it is already a bit and therefore not string?

      I don’t really want to do either of these options but it seems I have no choice.

      I just want them to stop converting my bit data to a string. If they can’t handle bit, at least automate it to int instead of a string.

      It creates extra work for me with the “no code” solution (rolling eyes).