SharePoint List Input - "too many digits after the decimal" when column is a whole number

Configuration: My workflow begins by reading a SharePoint list, one column of which is "% Complete". (Select tool connected to output of SharePoint List Input shows % Complete as a FixedDecimal, size = 18.0). Every list item has a value for "% Complete" between 0 and 100; no empty values. The SharePoint column is defined as a number type, min = 0, max = 100, 0 decimal places. There are 103 list items. When I run the workflow, it reports 13 conversion errors "SharePoint List Input | % Complete: "0" has too many digits after the decimal and was truncated." (About half of the conversion errors cite "0", the other half cite "1".) 52 of the list items have a % Complete value of "0", but none of the list items have a % Complete value of 1.

So, questions:

Why does Alteryx think "0" has any digits after the decimal?
Why does Alteryx think any of the list items have a % Complete value of "1"?
Is there a way to see exactly which row (list item) Alteryx thinks has an error?

Thanks!

Darin

Input

Accepted answers

All comments

KyleB

Hi Darin,

My suspicion is the source data from SharePoint carried some type of formatting throughout its lineage as a dataset. Do you happen to know where the data that populated the SharePoint list came from? Did it come from Excel? Those columns may have been formatted as a % for example.

Did you set the FixedDecimal size to = 18.0? Does it behave the same way when it is set to the default 19.6?

Thanks!

Kyle

darindavis

Kyle,

The SharePoint data I entered manually. However, your question prompted me to check and the SP column is set to show as a percentage, but the number of decimal places is set to 0. Unfortunately, my 14-day Alteryx trial license has expired, so I can't check how the FixedDecimal size is configured. We may be doing a 30-day trial later, so I'll have to come back to this at that time.

Thanks,

Darin

lpuskarich

I was getting this error with my SharePoint input tool. My formula was calculating the difference between today and a manual date. There were no decimals in SharePoint so I placed a round function into my formula in SharePoint and no more conversion errors. Example: ROUND((Date-TODAY()),0)

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703