This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We have some scheduled workflows that utilize the download tool for API calls. When we scrape them with connect there aren't any references to them in the "Relationships" or "Data Connections" areas.
Even if this is something that would be difficult for Alteryx to scrape through a workflow, I would love the ability to create entities like this and manually connect them as a data source. Like we have some partners where there 10 to 15 API calls are required to pull the entire data set. It would be great to know which workflows reference those APIs so that if changes are made on their side, we can easily identify which workflows are impacted.
Would be good to create an Alteryx Connect plugin for Tableau so that you can access Connect from Tableau? Would improve user experience if the user can access the information catalog without leaving their BI tool. So for example, have an Alteryx Connect sidebar in Tableau to allow you to search for a table or file then click and add as a data source and immediately start data discovery/analysis.
as per the title, when selecting "Use in workflow" a user should have the option to connect with the in-db tools when applicable rather than being stuck on a green input tool with an odbc connection. Ditto when searching from the omnibox in designer.
In order for us to make sense of Connect assets in an environment with hundreds of users; thousands of canvasses and databases etc - we need to strongly categorise and describe every asset using mandatory tags.
Every asset needs to have mandatory tags
- The admin team set up the list of tags which are required for different types of assets
- For example - every Alteryx Canvas may need Product; Process; Team - every DB table may need Product and Tech Team
Admin team need to be able to define these tags and the acceptable values (which can be a tree)
When searching for assets - these meta-tags need to be available as filters
Asset is identified by the scanners and brought into Connect
Owner is then required to describe their asset using the mandatory tags set up by the admin team
Product (this is a tree that would be controlled centrally – admin can add or update this list; users have to select 1 or more products that this canvas relates to)
Team (tree based)
Is this regulatory (Y/N)
Public / Private
In this case – every asset needs 6 tags; with the taxonomy(valid values) controlled centrally