Skip to main content
Solved

Export Project with Automation containing wildcard

  • September 19, 2025
  • 4 replies
  • 72 views

veschwab
Contributor
Forum|alt.badge.img+20

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?

Best answer by alexbiz

Hey Vera,

 

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

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

veschwab
Contributor
Forum|alt.badge.img+20
  • Author
  • Contributor
  • 22 replies
  • September 19, 2025

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 :)


alexbiz
Influencer
Forum|alt.badge.img+28
  • Influencer
  • 161 replies
  • Best Answer
  • September 19, 2025

Hey Vera,

 

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


veschwab
Contributor
Forum|alt.badge.img+20
  • Author
  • Contributor
  • 22 replies
  • September 22, 2025

Hey Vera,

 

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

Will do that, thanks! :)


virtualcitymatt
Celebrity
Forum|alt.badge.img+47
  • Celebrity
  • 2000 replies
  • September 22, 2025

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.