Format issue in output

[vishalnegi]

In my excel file, there are two columns A and B. Each coloumn has cell value of a 8 digit number stored as string. For e.g A1 = 12345678, B1 = 87654321

I need to concatenate these two values into a single value and store the result as an integer i.e. 123356787654321

I have used tonumber([col a]+[col b]+, '.0') in formula tool. In browse tool, i can see correct data but when i am writing this to excel it is pasting value in scientific format and rounding off last digit i.e. ouput is 

123356787654320

[alexnajm]

That sounds like an Excel issue rather than an Alteryx issue - the format of how it outputs is typically determined by the end program. 

Can you share your workflow?

[vishalnegi]

Hi, I dont have a workflow ready because i need to perform this step only.

Consider the data as

Amp_code Mon_code   Amp+MonCode

12345678  87654321   1234567887654321

 I need to make "Amp+MonCode" column with the help of alteryx' tools and ouput it correctly into the excel

[alexnajm]

You said you have a workflow so I wanted to see what was wrong with it so it could be fixed. But here you go from scratch - this provides the expected output in Alteryx. 

[DavidSkaife]

Hi @vishalnegi 

While it shows the correct value in Alteryx it will not display correctly in Excel, due to it being a limitation of Excel and how it handles large numbers; essentially it will only store 15 digits, and anything after will be a 0. https://learn.microsoft.com/en-us/office/troubleshoot/excel/last-digits-changed-to-zeros

You will have to save the value as a string in order for it to display correctly within Excel

@alexnajm you're workflow still outputs with the 0 once its in excel

[alexnajm]

@DavidSkaife my workflow works in Alteryx per the requirements, and as mentioned above anything wrong with the output would likely be an Excel issue.

[DavidSkaife]

@alexnajm if you read the original post they already have stated it's working as expected in Alteryx as they can see the correct value in the browse tool.

Merely posting a workflow saying this works is not really helpful when in fact, the actual output is not as expected due to the excel issue as we have both pointed out

[alexnajm]

I read that scientific notation was part of the issue as well, which is addressed in the workflow. And luckily the workflow is easy to change now - it’s just a matter of changing the output to a string as mentioned. Or perhaps Excel really means csv, in which case it can work (although a bit silly) - see attached.

This is a positive Community that builds on each others solutions and works together, not against 👍