In case you missed the announcement: The Alteryx One Fall Release is here! Learn more about the new features and capabilities here
Start Free Trial

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.

In-accurate JOIN using a "Sharepoint Input" connected to "Data Stream In"

AshCarter_
5 - Atom

Hi All,

 

I was wondering if you could offer an explanation and solution for a possible Sharepoint error.

 

Workflow description:

I have a workflow where my excel lookup file is within Sharepoint Input Tool which is connected to a Data Stream In Tool. This is then connected to the right input of a Join In DB Tool. My sales table is connected to the Left Input.

 

Issue:

 

I noticed there was a data inaccuracy issue when checking my final data output. After investigation, I identified that Alteryx is reading my Sharepoint file incorrectly for certain rows. It seems to be replacing the first 2 digits (19 or 22 in my example) with "01/01". The suffix remains the same. This only seems to be for a few rows (occurring at random), which therefore took me a while to spot. This Sharepoint file is also used by other colleagues who are not experiencing an issue. Please see below screenshots

Consequence:


This caused my Join to function incorrectly, and resulted in in-accurate data. I checked my Sharepoint file and there didn't seem to be any data type issues etc. I only noticed this when looking in the Alteryx browse functions.

3 REPLIES 3
dreldrel
9 - Comet

Hi, could you try to untick Select Range and see if that helps?

dreldrel_0-1760996471270.png

 

AshCarter_
5 - Atom

Hi, Thanks for your response. This did not resolve this issue.

apathetichell
20 - Arcturus

Alteryx says your cells in the underlying excel file are set up as dates --- more specifically dates that don't exist. I do not think In-DB has anything to do with your issue. Attach browse tools from Sharepoint input down and filter for those records. see where the values propagate from. Are you mapping a numeric column to a date field at some point?

Labels
Top Solution Authors