Skip to main content
Open

Add a 'Case sensitive' Option to the Joiner

Related products:Transformers
hvukasinovic
tcrossman
chriswilson
+5
  • kmassey
  • ismail_imgs
  • hvukasinovic
    hvukasinovic
  • tcrossman
    tcrossman
  • chriswilson
    chriswilson
  • revesz
    revesz
  • apaul
    apaul
  • gavinpark
    gavinpark
  • hrvoje
    hrvoje
  • zubair

lars_de_vries
Add a 'Case sensitive' option to the Joiner. Sometimes capitalization of attributes differs between source and target attributes. It would be nice if you could just use an option to take this into account or not.

5 replies

geosander
Forum|alt.badge.img+7
  • November 10, 2015
Yes, this is a great idea. In fact, I think this should be an option for a lot of transformers where strings are being compared (e.g. Tester, TestFilter, AttributeValueMapper...). Sometimes, I don't care how FME compares values, but I do need to keep the original writing style. Now I need to copy the old value and apply an @LowerCase() function or StringCaseChanger, which clutters my workflow a little.

  • June 23, 2016

I had the same idea for the featuremerger,...


rylanatsafe
Safer
Forum|alt.badge.img+13

See also Idea: 'Case Sensitive' option when testing attribute values.


oscard
Influencer
Forum|alt.badge.img+21
  • Influencer
  • January 16, 2018
Having that option in the FeatureMerger (or any other transformer with similar functionality) would be a charm!

 

 

Yesterday, I had to deal with un unexpected change of case that nobody told me about.

 

 


jdh
Contributor
Forum|alt.badge.img+28
  • Contributor
  • December 10, 2018

The Tester now has Case Sensitive, Case Insensitive options in the Comparison mode. It would be nice if the FeatureMerger/Feature joiner could do so as well.


Reply


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