This idea has come up in the 2016 thread (now released) about adding any output ports to FeatureWriter but the use case for Rejected features remains - e.g. some web-based format has a transient HTTP error, the failed features need to be retried after a wee delay, or a field overflows and can’t be written. @markatsafe @rylanatsafe you guys were on that thread. FeatureReader has a Rejected port, very handy for retry logic in a looping custom transformer, lets see it for FeatureWriter!
There might need to be a Rejected port for each output port if you're going to loop it, or filter on feature type before looping to an input.
Released
Add a Rejected port to FeatureWriter
+11- Safer
Hi everyone!
I’m pleased to mark this one as released as FME 2026.3 is becoming available today, with a caveat as I mentioned before… We have to enable the feature for each format and it requires more effort than we would like. Support per format will vary but we are trickling them in with each release.
We are continuing to prioritize formats based on community requests & usage statistics.
Cheers
+10- Contributor
Is there a list with supported writer formats and what exceptions etc that pass a feature to the <rejected>-port?
I tried with the SQL Server writer and wrote to a not existing table(Table Handling = "Use Excisting") but that caused the translation to fail and no features passed tho the rejected port.
+11- Safer
Hi
The first batch of formats that was done during development of the feature and what’s available in 2026.3 is
-
Esri Shapefile
-
CSV2
-
PointCloud XYZ
2026.4 will bring in support for these AEC related formats, as well as more Document based ones (Excel, Word, raster formats, the precise list is fluid here and will be known closer to release time...):
-
DGN
-
IFC_API
-
ACAD
-
RealDWG
-
OBJ
2027.1 should bring support for some Web Connectors as well as XML based formats
2027.2 should bring support for some Database related formats
This is the current plan, it might change and is driven by community requests, formats popularity as well as our development schedule and team availability. As I mentioned, the work required per format is substantial so we have to have that phased approach.