Data Input Tool is returning Nulls where there should be data

[JHope]

I just upgraded to version 2025.1.1.27 Patch 1. This process used to work in the previous version, but it's now broken.

The Data Input tool is failing to import some of the values, instead passing a [Null] value to the next tool.

It is reading data from an oledb backup, stored on the computer's hard drive.

When I run the workflow, any number over 100 gets removed, and the Input Data tool throws an error "... was too long to fit in this FixedDecimal". It is trying to import the field with 254 decimals, but can only accommodate 256 numerals and so it throws errors when the number is 3 digits or greater.

How can I reconfigure to force the Data Input tool to expect something other than a FixedDecimal?

[apathetichell]

When you say that it's an oledb backup store locally ---> are you still pulling it in via query? I'd recommend casting it as a specific type --- if it's DBTYPE_VARNUMERIC -- I'd recommend converting it. Basically Alteryx says (rightly or wrongly) that at the source this data has a precision beyond the realm of fixed decimal. Is that true?  Possibly?

[JHope]

There is a collection of files on the hard drive. Each stable has a set of 3 files, with the extensions .FIC .MMO and .NDX.

It looks like the consultant who set it up for us used PCSOFT HFSQL, so the Data Input tool is using the connection string that starts with "odb:Provider=PCSoft.HFSQL;..."

I can't use a query... the tool doesn't have access to the column names so the only query that works is SELECT * FROM "FACT"

I don't know if the source has that precision or not... I don't have a tool that can investigate. As I mentioned, the previous version of Alteryx worked fine. And I can import the same data into Excel without issue, so it's probably not a problem with the source data.

[apathetichell]

ok --- can you a) open a support ticket (under support) --- b) downgrade to 2024.X? This sounds like something is just wrong on the Alteryx end.