Upgrading Server to version 22.1? We’ve enabled the faster AMP engine by default. Read about how these system settings changes might affect you.

2022-05-24 Updates: Login: If you are facing issues with logging in, please try clearing all your cookies or trying another browser. We have a fix being deployed on the evening of 5/25. Email: If you're not seeing emails be delivered from the Community, please check your spam and mark the Community emails as not junk. Thank you for your patience.

Alteryx Designer Ideas

Share your Designer product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Loading of ALL the tables in the entire Oracle Database is an overkill in the Input Tool

Hello,

 

I'm using the latest Alteryx Designer version 2021.1. When I drag an Input Tool, before I can proceed with anything, it asks me to choose a pre-saved, named, data connection from the Gallery. This named connection is pre-configured with a USERNAME, target SCHEMA NAME to connect to, with a PASSWORD. This is also known as a PROXY CONNECT method as follows:-

 

USERNAME[SCHEMA_NAME]

 

Once I have selected a named, data connection, the assumption is that in the next screen, if I click on the Tables button, that it would ONLY load the tables inside that target SCHEMA_NAME and not take 10 mins to load thousands of tables that exist in the entire Oracle Database, some of them I would not have access to even connect to, so then why load and make us wait for that long?

 

The same thing should apply WITHOUT a PROXY CONNECT method. For instance, if a saved, data connection only has a USERNAME and PASSWORD, it means the user would like to strictly connect to their own personal schema.

 

Again, when this connection is chosen, the Tables button should strictly ONLY load the tables that exist in this personal schema by the name of that USERNAME and no need to load thousands of tables that exist in the entire Oracle Database.

 

I know the workaround would be to select SQL Editor to open by default which is what I'm currently using but seriously, this has to be fixed as the performance hit and showing of table names for which a user may not even have access to connect to is not good.