That won’t be a problem here, because I’m using destructuring assignment ( the three dots ) before the $group array ...$group, this will always work for every $group array regardless of the array size, you don’t have to get each index from the $group array, just use ...$group, this will destructure the array and will be the same as writing $group[0]... $group[n] multiple times.
Woah. That’s great. I didn’t know that. You’re my hero. hahaha. Here is my result. I worked.
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.
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.
Hi @fmdf ,
I can think of two solutions:
field AS int)Regards,
Bojan
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).
