Skip to main content
Archived

"Reject"port for writers changes to error log behavior with rejected features

Related products:Transformers
danilo_fme
  • danilo_fme
    danilo_fme

wolters
Contributor

***Note from Migration:***

Original Title was: "Reject"port for writers changes to error log behavior with rejected features by writers


Currently, when features are rejected when writing a file, there is no way to tell until you open the file.

For example, if 51 features are passed by a transformer (and are visible in the inspector or other data formats), but 4 cannot be written to a specific writer (rejected), FME will still report

"51 features written, Transformation successful"

even though in actuality only 47 features are written.

I propose that the FME logger and workspace will say

"47 features written, 4 rejected by output file, Transformation successful"

Alternatively, the addition of a "reject" port for writers can also be a solution.

As there is no "reject" port for writers as there is with transformers, there is no way to tell without scrolling in the error log whether all features are written by a specific writer, until you open exported file in FME Data inspector.

This behavior is discussed in this thread with an example. https://knowledge.safe.com/questions/69542/missing-points-when-exporting-to-shapefile.html?childToView=69550#comment-69550

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

fmelizard
Contributor
Forum|alt.badge.img+17
Be sure to check out this related idea: Add Rejected Port and Filter Tab to Writer Feature Type

LizAtSafe
Safer
Forum|alt.badge.img+15
Idea merged into:

All the votes from this idea have been transferred.

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