07-19-2021 08:25 PM
Everytime I pull data from SQL Server / Salesforce etc, if the data type is bit, it returns a string of ‘true’ or ‘false’ that I am then having to convert back to a 0 or 1.
How do I get this to behave differently?
07-20-2021 01:40 PM
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.
07-20-2021 04:15 PM
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.
07-20-2021 02:02 PM
Hi @fmdf ,
I can think of two solutions:
field
AS int)Regards,
Bojan
07-20-2021 02:24 PM
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).