Hello,
Hi @Smith401
how are you getting the SKU's into Alteryx. If they're input through Excel, can you post a sample input file that displays this issue? Just a few lines would be enough. If you read them from a database, try using a Cast statement in the input SQL to force the numbers to be read in as text.
Dan
Hi Dan,
I've attached an example file containing a few lines of what would be inputted from excel into SQl. There are 3 data sets I use, which go into 3 separate SQL tables. I then extract the data from these 3 SQL tables in the master workflow, which is this one, where the 3 SQL inputs can be seen to start with. The plan is to join them all up through the SKU column. The join seems to work successfully, but the formatting seems to be lost, which is where I am having these scientific/algerba format issues in the final SQL output.
Thanks,
Will
hi @Smith401
When I use your file the values come in as expected in version 2021.1
When you have numbers that are meant to be treated as strings, i.e. SKUs, EANs, employee ids, etc. it's always a good idea to use a Select tool immediately after the Input tools to force the columns to strings. That way when you write the the data to SQL, creating a new table in the process, the resulting columns will be varchars in the tables as well. When you read them back out of the tables, they won't show the scientific notation issue.
Dan