Directory Input Documentation

[Treyson]

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.

[VojtechT]

Hi @Treyson, @OldDogNewTricks and @Atabarezz ,

this feature has been implemented in the 2020.2 version. Please let me know whether it works according to your expectations once you have opportunity try it.

Vojta