NeighborFinder error

everything perfect but again, I'm getting same issue

is there any alternate

please suggest

You can open the rejected features (if using caching) and have a look at the rejection reason, what does it say?

Then I'd suggest what FME suggests. :-) Which is to go to the Navigator and change Workspace Parameters > Translation > Rejected Features to "Continue Translation" to see if it's just one or a few features that are rejected or if everything is rejected.

Alternatively you can simply connect an Inspector to the <Rejected> port of the NeighborFinder and look at what comes out, it may even contain an attribute with an error message. That way you won't have to change any workspace-wide behavior.

See also the reply from @itay

Yes all rejected ports have am fme_rejection_code attribute which is very useful for debugging.

@rakeshreddy0996

This error occurs when using a groupby and it receives objects without the used groupby attribute.

..which you can see if you check which object(s) cause the error.

Often the relevant ffs in your ..fme\\temp folder (check the code in the error message) can be opened (when the rejection code doe not say anything, which is often the case.

Hi,

I think error may get for below reason

Bases and candidates both having same header names

plz suggest