The Alteryx Community is a finalist in three 2026 CMX Awards! Help us win Customer Support Community, Most Engaged Community, and User Group Program of the Year - vote now! (it only takes about 2 minutes) before January 9.
ACT NOW: The Alteryx team will be retiring support for Community account recovery and Community email-change requests Early 2026. Make sure to check your account preferences in my.alteryx.com to make sure you have filled out your security questions. Learn more here
Start Free Trial

Alteryx Designer Desktop Discussions

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

Input Data Tool Warning "This Action will remove your current tool configuration"

hope_larosa16
5 - Atom

I keep getting the following error when I try and change the connection in my input data tool to a new excel file: "This action will remove your current tool configuration.  Do you want to proceed?".  I used to be able to maintain my connection settings, but ever since the new update, I keep getting this warning.  Is there a way to maintain my input data tool settings (ie. start data import on line) when I change the excel file?  TIA!

3 REPLIES 3
jrlindem
13 - Pulsar

Can you describe more about the previous and new excel file that you are using in the input tool?  Are they both .xlsx, did they switch or change schemas, or did the sheet change?

Also, since the last time you did this, did your Alteryx version change?  Hoping you can provide more context so a solution can be zeroed in on.  Cheers, -Jay

hope_larosa16
5 - Atom

The files are formatted the same way and have the same schema only change is one file has October data and one has November data.

 

Yes, I noticed the change when I updated to the newest Alteryx version.  I did not have this issue with the prior version. TY!

 

jrlindem
13 - Pulsar

I'm not 100% sure of this, but I recall reading something like what you're describing having to do with Alteryx Version changes.  I'm not sure why or why this makes sense, but it could be related.  Are you able to go back in version and see if it still gives you this error to isolate the issue?

 

If it's related to your version, you might want to open up a ticket to Alteryx.  -Jay

Labels
Top Solution Authors