Skip to main content
  • EN

Hi,

 

I’m trying to create a project that contains an automation in which a workspace is using a wildcard in a filepath. The filepath looks something like this: SHAREDRESOURCES/DATA/FOLDER/**/*.csv

Fme Flow does not seem to like the wildcard in the filepath as I am guessing it wants to have a proper file to take in the dependencies and add to the project. 

I could manually just choose a dummy file to be able to make the project work but that would mean I would manually have to change the filepath later and I would like to do as little manual steps as possible.

 

Is there any way around it? Can I maybe exclude specific dependencies somehow?

Found a workaround to use a Directory and File Pathnames reader instead so I don’t have to use a wildcard in the file path :)

Hey Vera,

 

I think it might be worth to submit that as an issue 👍

Hey Vera,

 

I think it might be worth to submit that as an issue 👍

Will do that, thanks! :)

I’ve found the same thing (in the Amazon s3 Bucket node) - in my case though it’s for a folder that doesn't need to exist - the automation will create the (temporary) folder: 

$(FME_SHAREDRESOURCE_TEMP)/<productname_uploads>/{event.id}

I haven't bothered looking into a workaround for this yet - but certainly notable.

 

Community Stats

31,853
Posts
120,982
Replies
39,485
Members

Latest FME

Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.