![]() ![]() The field for File Drop automations is a literal string, meaning that if you type in myfile_%%month%% it will look for literally myfile_%%month%% and not myfile_01 like it would inside the import of file transfer activities. Wildcards that are available inside of the Import Activities and File Transfer Activities are NOT available inside of the File Drop Filenaming Patterns. (Special thanks to Jason Cort and Christine Potochny for their conversation on Email-Geeks Slack channel about this) Using pattern (Ends with bus) will succeed for: Using pattern (Begins with bus) will succeed for: Similar to SQL LIKE with no wildcard at the front. This can lead to issues if dropping more than 1 file to the location meeting the pattern (Thanks to Michal Rzepka who runs v and Rafał Pawelec) *Important note – using contains will not process the files in queue order but instead in what appears to be a random selection. Using pattern (contains bus) will succeed for: Similar to LIKE in SQL and just looks for if those characters exist in that order in any file. To ‘test the automation, you will need to drop a file while it is Active. This pauses the trigger or activates it to allow for editing without distortion of output. There is no ‘run once’ option in File Drop Automations, it instead uses ‘Active’ and ‘Inactive’.You can have multiple automations running on a single folder, but they cannot be triggered off the same file. (Thanks to James Lamb for the note on this) If you export a file via another automation to sit on the SFMC SFTP, a File Drop automation will NOT pick it up.Changing the file name on the FTP or things such as File Transfers from Safehouse, etc. ![]()
0 Comments
Leave a Reply. |