Have I found a bug in the Dataverse Input tool?

[craigja]

I have a dataverse table with a number column, set to 2 decimal places, if I try to insert 1.00 into it I get the error below, inserting 1.01 (or anything else) is fine.  I wondered if somebody could confirm if this is a bug or me doing something silly!

Dataverse Output (1) API response: Error code 400: Bad request syntax or unsupported method.

[KGT]

Can you paste an image of the metadata on the connection to the Dataverse tool? So, click on the connection (line) and then screenshot the column config.

Try having it as a FixedDecimal (19.2) first and see if that works.

[craigja]

Here you go - it is a fixed decimal, Ive also tried setting it as a double

[KGT]

I'm not the knowledge base on it, but it looks like a bug to me. If that simple workflow works with 1.01, but not with 1.00 then I don't know what else it could be other than a bug. I don't have it operational to test though...

[apathetichell · Accepted solution]

@craigja  -- i'll bite. note - I've used Dataverse excatly 0 times. What field type is your value in Dataverse? My hypothesis is that a rounding is going on somewhere --- the 1 becomes 1 --- and 1 isn't a 19.2 it's an integer which is causing an error.

two successive tests --- can you switch both types in Alteryx and in Dataverse to Float? Why? I have no idea. But let's try it.

can you switch both types in Alteryx and Dataverse to string? Let's confirm that those work. 

Basically my hunch is this is fixed decimal to decimaltype in Dataverse. Alteryx is either using some stupid auto-field methodology in the input tool --- or in the python --- or the issue is in the python wrapper.

and last question -- any behavior differences if 1.00 is the only value vs one of a series of values?