Skip to main content
Solved

Rejection Code: EXTRA_REFERENCE_FEATURE

jelle
Contributor
Forum|alt.badge.img+16
  • jelleContributor
  • Contributor

Hi FME'ers,

on the FeatureMerger, I get the rejection code 'EXTRA_REFERENCE_FEATURE. Does anyone know what this could mean?

The problem occurs on a Supplier object, coming from AutoCAD Map3D, with OD objects. It merges with an Oracle table, using two attributes. When checking visually, the attributes should match, but it doesn't come that far because of the rejection.

Best answer by takashi

Hi @jelle, check if the rejected features match one of the conditions described in the help: "If Process Duplicate Suppliers is No, then duplicate suppliers will be rejected. If Reject Null and Missing Keys is Yes, then keyless features will be rejected." -- description about the <Rejected> port in the help doc of FeatureMerger

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

5 replies

takashi
Influencer
  • takashiInfluencer
  • Best Answer
  • May 19, 2017

Hi @jelle, check if the rejected features match one of the conditions described in the help: "If Process Duplicate Suppliers is No, then duplicate suppliers will be rejected. If Reject Null and Missing Keys is Yes, then keyless features will be rejected." -- description about the <Rejected> port in the help doc of FeatureMerger

jneujens
Forum|alt.badge.img
  • jneujens
  • May 19, 2017

Could you maybe give an example of the data? And your settings in the FeatureMerger?

 

 

Is your comparison mode set to automatic?

 

 

Did you try using a DatabaseJoiner? If yes, you had the same issue?
jelle
Contributor
Forum|alt.badge.img+16
  • jelleContributor
  • Author
  • Contributor
  • May 23, 2017
takashi wrote:

Hi @jelle, check if the rejected features match one of the conditions described in the help: "If Process Duplicate Suppliers is No, then duplicate suppliers will be rejected. If Reject Null and Missing Keys is Yes, then keyless features will be rejected." -- description about the <Rejected> port in the help doc of FeatureMerger

Thank you Takashi. There is indeed a problem with values that should be unique. Duplicate suppliers has to be on No. I was focussing too much on the message 'EXTRA_REFERENCE_FEATURE'. Maybe 'DUPLICATE_SUPPLIER' would have been better.

 

 

koen
Contributor
Forum|alt.badge.img+10
  • koenContributor
  • Contributor
  • June 29, 2018

I had the same issue the other day (using fme 2017.1)

Checked my data, and I was sure I really didn't have any duplicate suppliers.

 

I manage to solve it by changing the Comparison mode of my key field from Automatic to String.

.

The field had type char(8), but apparently FME tried to compare it as Integer and found a match. Possibly because the value started with a number?

takashi
Influencer
  • takashiInfluencer
  • June 29, 2018
koen wrote:

I had the same issue the other day (using fme 2017.1)

Checked my data, and I was sure I really didn't have any duplicate suppliers.

 

I manage to solve it by changing the Comparison mode of my key field from Automatic to String.

.

The field had type char(8), but apparently FME tried to compare it as Integer and found a match. Possibly because the value started with a number?

It's intentional. "The Comparison Mode column specifies how to perform the comparison between Requestor and Supplier attribute values. If Automatic or Numeric is specified, an attempt will be made to convert attribute values to numbers before comparing them." -- Help on FeatureMerger

 

Reply


Helpful Members This Week

Community Stats

31,182
Posts
118,186
Replies
38,791
Members

Latest FME

Terms & ConditionsCookie settings

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
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.