Union Tool - The Input "#2" was not initialized.

I have two data streams which need to be unioned together. One of the data streams often contains no data which is causing the union tool to encounter an error, input was not initialized. I have read through other discussions and have tried adding a text input, another .xlsx file with a single blank line, adding a block until done, etc. Nothing seems to resolve the error.

Join

Accepted answers

Tonya_Smith

This will be fixed with the 2023.1 Release.

All comments

Felipe_Ribeir0

Hi @mschmeiser

You are using the filter to separate the filepaths, open each file with one dynamic input and union them, right?

The files have the same schema (column names and data type)? If yes, you need just one dynamic input and you can pass both filepaths to the same dynamic input.

If this is not the case, why you need to separate the filepaths?

mschmeiser

The dynamic inputs are database connections to two different servers. Can a single dynamic input handle two different connections?

mschmeiser

I use the filter tool to determine which server to connect to.

Felipe_Ribeir0

Ok, i was thinking about excel files, sorry.

My only try would be to include an text input with null data and union it with the second dynamic input before the main union, or to include a select tool after the second dynamic input (to generate metadata).

Felipe_Ribeir0

If you already tried it, lets wait for other users to reply here.

MartWClimber

got the same issue with a union tool as well. first time I deleted the union tool replaced it and it ran oke (forgot to save) day after same issue but couldn't update the union tool without getting the same error on an other union tool in the same workflow.

after this I used a production workflow where this error wasn't happening. strange part is it was the same workflow only saved on a different location.

so a tip in sort of fixing this issue could be try and use a back-up or acceptance,development or production (where the error isn't there) and copy the workflow over it (via fileserver)

I've got a similar post. i might help you out @mschmeiser

POST: https://community.alteryx.com/t5/Alteryx-Designer-Discussions/The-input-quot-1-quot-was-not-initialized-union-tool-error-after/m-p/1016480#M251223

@TonyaS

Tonya_Smith

Thanks for tagging me.

What version are you using @mschmeiser ?

I'm curious whether this is the same with and without AMP Engine.

If you have a yxzp you could send me I could try it on one of our recent Dev builds as well as 22.1 to see if it is still an issue.

Thanks!

Tonya_Smith

I was actually just able to reproduce this on a Dev build. I will create a defect and link both of these recent posts so we can come back and update with the version that will contain a fix.

Tonya_Smith

This will be fixed with the 2023.1 Release.

wesleygrey

Hi @TonyaS, I'm currently responsible for upgrading my users to Designer/Server 2022.1, and will likely not upgrade to 2023.1+ until a year from now. I just randomly encountered this issue while running an already mature and functional 2021.3 workflow (tried using both AMP and non-AMP, and still experiencing it). I can't imagine having to work with my users' tickets for a year to handle this. Is there any way this can be resolved for v2022+ through patching, please?

Tonya_Smith

@wesleygrey
We had not planned on backporting the fix to any prior versions, but we will discuss internally to see what can be done.

wesleygrey

Thank you. If patching is not an option, then having an understanding of the root causes so we can configure our workflows to avoid it, or any workarounds would be helpful. The Union is a very common tool, so it's only a matter of time before several of my hundreds of users bombard me with troubleshooting this problem. Right now, I'm backed into a corner. Thanks.

flying008

Hi, @TonyaS

Could you please tell me that when about the v2023.1 Release ?

Tonya_Smith

Sorry, but we do not provide dates for future Releases.
I can only say that 2023.1 is our next planned Release and there are 2 major GA Releases planned for 2023.

Tonya_Smith

This fix will be included in the next patches to both the 2022.1 and 2022.3 Release versions.

nbondarchuk

I’m happy to announce that the fix has been released in the 2023.1 GA Release version May 17, 2023, which is available for download from our licensing portal.

It is also available in the next patches:

2022.1.1 Patch 6 Release: Mar 29, 2023

2022.3.1 Patch 3 Release: May 5, 2023

Larissa_Sanches

Hi,

This error occurred in the 2023.1 versions. Do we have any new solution for this error ?

ashirsat9

Is there no solution to this error? I am trying to find workarounds and haven't been able to find one

flying008

Hi, @Larissa_Sanches @ashirsat9

Are your Input "#1" and Input "#2" all have full same schema ? only maybe have no data ? this seem fixed in v2024.2.

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15879

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703