What version FME? Whicht output format? I rarely use this functionality so I had to give it a try. The only way I can reproduce this (no features leaving the FeatureWriter) is when no features are actually written. For example when writing to a file geodatabase using truncate in a not existing featureclass.

As @danilo_fme suggests, check your log for errors. There are probably warnings or errors saying the data can't be written. From FME 2018 you the log can be easily filtered with the Errors / Warnings / Information buttons. (This is really a great improvement my dear Safers!)

The FME version I am using is 2018.1.2.1. The writer is a Esri SDE Geodatabase writer. I am not getting any errors or warnings in the log but it says that 0 features written. The writer is being used to update the attributes in the target table. Upon successful run I can see the values getting updated but in summary it just gives me number of records updated/processed. What I am looking for is a feature by feature summary.

I have no SDE to test with, but using a File Geodatabase I get different behavior. I always get output, even if a row is not found.

featurewriteroutput2018.fmwt

Maybe someone from Safe can chime in and check how it should work.

The FME version I am using is 2018.1.2.1. The writer is a Esri SDE Geodatabase writer. I am not getting any errors or warnings in the log but it says that 0 features written. The writer is being used to update the attributes in the target table. Upon successful run I can see the values getting updated but in summary it just gives me number of records updated/processed. What I am looking for is a feature by feature summary.

If the log and summary port are saying 0 features written, I wouldn't expect any output from that port. Are you sure the features are being updated?

@nielsgerrits At least you are getting something in the Output port. In my case I do not get anything.

@harshal.gharat I think this was a quite recent development if I check out the original idea. So it probably does not work as expected with all formats.

Not sure what you need exactly but you could easy route another stream of the features entering the FeatureWriter around it, using a Holder, FeatureMerger and Tester (To filter out the Summary Feature). If I read the comments...

"There is not yet any Rejected Output Port and it currently will only output the Features that are passed through it."

and

"Additionally, the FeatureWriter will only output features once writing has completed."

... you will not lose any information or performance.

To check if the changes are written correctly you still need to read and compare those, one way or the other.

It works fine with ArcSDE writer for me, I don't know whether the transaction type makes a difference?

It works fine with ArcSDE writer for me, I don't know whether the transaction type makes a difference?

It works fine with ArcSDE writer for me, I don't know whether the transaction type makes a difference?

@egomm does your log also say "0 features written"? I suspect the outputport depends on the same mechanism.

@harshal.gharat I think it is wise to Report a problem at Safe, sending them your workspace and the details around it so they can fix it if it is a bug.

The features written summary at the end reports 0 features written as there is no writer - the part of the log relating to the feature writer reports 10 features written, the summary port reports 10 features written, and 10 features are output from the writer