Skip to main content
Solved

Emailer Attachment

  • October 23, 2019
  • 5 replies
  • 242 views

pflegpet
Contributor
Forum|alt.badge.img+8

Hi,

I'm trying to set up a workflow where I attach the intermediate result of a workspace to an Email as an Excel spreadsheet but I have troubles writing only one file. The Emailer documentation hints at using TempPathNameCreator and a FeatureWriter but I could not find any concrete examples on FME hub. When I run the translation every feature is written to a separate Excel file instead of a single one. I'm sure this can easily be done but I can't figure out how. Thanks for any help!

Best answer by itay

Hi @kasparlov,

How is the FeatureWriter configured? can you share a screendump of the settings?

View original
Did this help you find an answer to your question?

5 replies

itay
Supporter
Forum|alt.badge.img+17
  • Supporter
  • Best Answer
  • October 23, 2019

Hi @kasparlov,

How is the FeatureWriter configured? can you share a screendump of the settings?


pflegpet
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • October 23, 2019
itay wrote:

Hi @kasparlov,

How is the FeatureWriter configured? can you share a screendump of the settings?

Hi, the current setup looks like this:


virtualcitymatt
Celebrity
Forum|alt.badge.img+35
itay wrote:

Hi @kasparlov,

How is the FeatureWriter configured? can you share a screendump of the settings?

Ahh, yeah, for each feature passing through the TempPathnameCreator you will get a new path. Instead of directing all your features though it you can use a separate branch with a Creator to create the temp path. Make sure the FeatureMerger is set to Suppliers First so that it doesn't cause a memory block.

 

 


itay
Supporter
Forum|alt.badge.img+17
  • Supporter
  • October 23, 2019
pflegpet wrote:

Hi, the current setup looks like this:

Yes @virtualcitymatt is correct a single feature for a single path is needed.


pflegpet
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • October 23, 2019

Thank you @virtualcitymatt, it works now as expected.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings