If I'm reading this correctly, there is no way test the contents of the file without reading them in first. You are on the right track by first reading the filenames using the Directory and File Pathnames reader, and then reading those in with the FeatureReader (exposing the fme_basename)
From there I would feed all the features into your AttributeFilter, and based on the results, use the FeatureMerger to get all the original features that match based on fme_basename. 
If I'm reading this correctly, there is no way test the contents of the file without reading them in first. You are on the right track by first reading the filenames using the Directory and File Pathnames reader, and then reading those in with the FeatureReader (exposing the fme_basename)
From there I would feed all the features into your AttributeFilter, and based on the results, use the FeatureMerger to get all the original features that match based on fme_basename.
Thank you for the response.
I hope this better explains what I'm trying to achieve with the AttributeFilter.
The attributefilter is only checking the file names from the PATH input as these folders contain many files I don't need. I was planning to read in these filtered features using a the FeatureReader.
That simplifies things. The Directory and File Pathnames reader gives you several attributes you can filter by. I normally use path_rootname or path_filename. In your FeatureReader, you would point it to path_windows, which is the full path of the files.
If I'm reading this correctly, there is no way test the contents of the file without reading them in first. You are on the right track by first reading the filenames using the Directory and File Pathnames reader, and then reading those in with the FeatureReader (exposing the fme_basename)
From there I would feed all the features into your AttributeFilter, and based on the results, use the FeatureMerger to get all the original features that match based on fme_basename.
The generic port from my FeatureReader only contains a column named <no schema>, how do you set up the FeatureReader to output values which your AttributreFilter is processing?
The generic port from my FeatureReader only contains a column named <no schema>, how do you set up the FeatureReader to output values which your AttributreFilter is processing?
You can expose attributes in the parameters of the FeatureReader.
The generic port from my FeatureReader only contains a column named <no schema>, how do you set up the FeatureReader to output values which your AttributreFilter is processing?
Would you be able to take a look at my attached workspace?
The workflow in the top bookmark is functioning for a single dataset. In the second workflow I'm attempting to use the same process to reveal the features of two datasets.
The generic port from my FeatureReader only contains a column named <no schema>, how do you set up the FeatureReader to output values which your AttributreFilter is processing?
It's failing because it's trying to read a CSV file into a FeatureReader set to read an excel file. I would create a 3rd FeatureReader which is fed from the AttributeFilter CSV port. Then set that FeatureReader to CSV.
I'm attempting to do the same thing, having read the post I have managed to isolate the files i wish to process but can't work out the final stage as to ho to process them. any assistance appreciated.
