Skip to main content
Solved

Change Detector - Attribute Matching Strategy

fionae
Participant
Forum|alt.badge.img
Hi,

 

 

I am using the Change Detector transformer and had planned on using the Match all Except Selected Attributes parameter for the Attribute Matching Strategy since my list of excluded fields is shorter than the list of included fields.  I'm wondering if this parameter is working as it should?  Everything appears to have changed when I used this parameter (which is not correct).  However, when I reverse it and use the Match Selected Attributes (and select all the appropriate fields), it works as expected.

 

 

I can use the transformer the way that I have it working but I was wondering if I am missing something?

 

 

Thanks,

 

fiona

 

 

P.S. I'm using FME 2013 Build 13264 WIN 32 with SDE 10.1 data (from SQL Server).

Best answer by takashi

Hi Fiona,

 

 

'All Except Selected Attributes' seems to include Format Attributes (e.g. fme_feature_type etc.) unless you specified explicitly them as 'Selected Attributes'.

 

Check whether format attributes of ORIGINAL feature are same as RIVISED feature's.

 

 

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

7 replies

takashi
Contributor
Forum|alt.badge.img+19
  • takashiContributor
  • Contributor
  • Best Answer
  • May 1, 2013
Hi Fiona,

 

 

'All Except Selected Attributes' seems to include Format Attributes (e.g. fme_feature_type etc.) unless you specified explicitly them as 'Selected Attributes'.

 

Check whether format attributes of ORIGINAL feature are same as RIVISED feature's.

 

 

Takashi
tim_wood
Contributor
Forum|alt.badge.img+8
  • tim_woodContributor
  • Contributor
  • October 21, 2016
@fionae @takashi I've found that this happens with the Matcher as well (comparing Feature Classes in two different FGDBs). If I select "Match All Except Selected Attributes", everything comes out of the NotMatched port. However if I reverse it to "Match Selected Attributes", then it works as expected.

 

fmelizard
Contributor
Forum|alt.badge.img+17
  • fmelizardContributor
  • Contributor
  • October 21, 2016

Hi @tim_wood The ChangeDetector and Matcher are working correctly. Unexposed attributes are included with "Match All Except Selected Attributes". Use an AttributeExposer before or else "Match Selected Attributes" in the Matcher.

sammy
Supporter
Forum|alt.badge.img+16
  • sammySupporter
  • Supporter
  • March 26, 2024

@fmelizard can you please explain how using an AttributeExposer would get the desired result?

I would like to use "Match All Except Selected Attributes" in ChangeDetector but not have it compare the format attributes.

I want to do it this way because I have multiple data sets I plan to run through the same workbench but their tables are slightly different. They all have the same fields I wish to exclude from comparison. I can’t list the attributes to compare for each table as that list will be different depending on the source that I am running through the workbench so "Match Selected Attributes" won’t work.

kketola
Contributor
Forum|alt.badge.img+3
  • kketolaContributor
  • Contributor
  • January 17, 2025

​@fmelizard I would not have expected ChangeDetector to be working against unexposed attributes. That through me for a loop but I see it is in the documentation.

Attribute Matching Strategy

In conjunction with Selected Attributes, this parameter controls which attributes of input features must have the same value before a match is declared.

  • Match Selected Attributes: the attributes specified in the Selected Attributes parameter will be matched.
  • Match All Except Selected Attributes: all attributes will be matched, except those specified in Selected Attributes. Matching is performed on all attributes, including unexposed format attributes.
  • Match All Attributes: matching is performed on all attributes, including unexposed format attributes.

 

Is there any way to permanently remove unexposed attributes from the feature to allow us to use the other matching strategies? Alternatively, it sounds like it would be helpful to have the option to select whether unexposed attributes should be included or not.

 

Cheers, Ken
sammy
1 person upvoted this
  • sammy
    sammy
sammy
Supporter
Forum|alt.badge.img+16
  • sammySupporter
  • Supporter
  • January 17, 2025
kketola wrote:

Alternatively, it sounds like it would be helpful to have the option to select whether unexposed attributes should be included or not.

 

​@kketola if this isn’t already posted to ideas you should definitely add it. I would upvote this idea.

kketola
Contributor
Forum|alt.badge.img+3
  • kketolaContributor
  • Contributor
  • January 17, 2025

​@sammy found one and upvoted it.

 

Not sure if you have also had this issue too, but I struggled with comparing decimal numbers and so I also upvoted this one.
 

 

Cheers, Ken
sammy
1 person upvoted this
  • sammy
    sammy

Reply


Helpful Members This Week

Community Stats

30,944
Posts
117,271
Replies
38,743
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.