Corptax Connector set up not working

[volivares]

Hello!

Has anyone successfully got the corptax connector to work? I am in the process of setting it up. Once I get to the attached screen (see image attachment) I configured my Data Source and credentials, restarted Designer. However, when I click the dropdown on "enterprise", "data source", etc there are no options available. Any suggestions?

[GrowthNatives]

Hi @volivares ,

Thanks for sharing the screenshot — this is a common setup issue when working with the Corptax connector and DCM.

Here are a few things you can check:

1. After configuring credentials via the Configure... button under Security Configuration, make sure:

   • The credentials are saved under Data Connection Manager (DCM).

   • You can view and edit them via Options → Advanced Options → Manage Data Connections in Alteryx Designer.

2. In the Corptax Input tool, ensure you're selecting a valid DCM Connection from the dropdown, not just entering credentials manually.

3. If dropdowns like Enterprise and Data Source are empty:

   • It’s often because the DCM connection isn’t associated with the Corptax connector.

   • Try recreating the connection and making sure the proper connection type is selected (e.g., Corptax API).

4. Also, double-check that your network/firewall settings allow outbound access to Corptax’s services (if this is an on-prem or firewall-restricted environment).
5. If none of the fields populate even after these steps, restarting Alteryx Designer as an Administrator can sometimes resolve permission issues related to connector initialization.

⭐Hope this solution helps you make the most of Alteryx! If it did, click 'Mark as Solution' to help others find the right answers.

💡Found it helpful? Show some love with kudos 👍 as your support keeps our community thriving!

🚀Let’s keep building smarter, data-driven solutions together! 🚀

[volivares]

Thank you for the reply! The solution ended up being that we had to download Alteryx 2024.1. The Ctax connector is not supported by 2024.2 (which we were using originally). It's working now!