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 had an idea, when you have an yxdb file, you have all the metadata including the field descriptions column from previous formulas or selects, it would be so usefull to have that in connect so that you can easily write a dictionnary from alteryx designer.
I published a workflow today that scans a directory for files and then pushes them to a Dynamic Input. I noticed that on Connect there is no relationship there anywhere referencing that we are scraping a directory.
Connect has the db inputs and outputs and the "File Input" that references what the Dynamic input is originally set to go find, but there is nothing referencing the directory other than any notes that I have added to the description.
The reason that I think this may be important. We connect to a folder where FTP files are dumped by a powershell script and we want to go through that folder with Alteryx and pull and upload as needed. However the file that existed in the original input (when we created this workflow) no longer exists. So the visual relationship is broken in Connect as soon as that file is dropped. If perhaps we don't have a tool that references this sort of connection to a directory, having the ability to designate a dynamic connection to the original file might be good instead. We just want to be able for those in the future to reference a location, rather than a file that hasn't existed in a while.
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.
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.
for the past 8 months I have been using alteryx and mostly working with the connect in db components , there are many issues which I am facing and i this this can be improved
1. there is no such flexibility of creating a table with the keys defined which is the most important pillar in database, also the options provided are limited , i.e. to create a new table , delete and append, drop table and recreate,
now, there are many times where in we need to update the tables based on the keys, which i find missing. Also how the option is defined is create a new table, next time if the job is run it states that the table is already created, for which we need to manually change the option in the next run.
2.which switching between in db and alteryx , if the records are more the alteryx lags completely and the job keeps running for hours , how can we achieve the flexibility of alteryx designer if there is such bottleneck.
3.the flexibility that is provided with alteryx designer should also be given to in db components.
4.the parameters defined in the workflow can not be accessed in the in db formula tools but can be used in the designer formula tools. this reduces the flexibility.