Forum Discussion
4 Replies
- winoskyNew Contributor III
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.
- fmdfNew Contributor III
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.
- bojanvelevskiValued Contributor
Hi @fmdf ,
I can think of two solutions:
- You can cast the value while reading in your query => SELECT CAST(
field
AS int) - Use a Mapper with a ternary operator within SnapLogic => $field == ‘true’ ? 1 : 0
Regards,
Bojan- fmdfNew Contributor III
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).
- You can cast the value while reading in your query => SELECT CAST(