Skip to main content
Solved

FeatureJoiner failing

  • September 3, 2025
  • 3 replies
  • 159 views
tullus
Observer
Forum|alt.badge.img+1

Hi all,

I have two CSV files (A and B) that I've included using CSV readers, and I need to join them using a feature joiner on a specific column. CSV A contains numbers in all rows, whereas CSV B has numerous <Null> cells in the column. When I run the feature joiner it fails. I already tried:

  • Changing both attribute types to number
  • I included attribute managers before each CSV to include letters with the numbers of each CSV file to force matching as text

Does anyone have any suggestions?Β 

Many thanks.

Β 

Β 

Best answer by alexbiz

Maybe the best strategy would be to filter those features without values (using a simple tester) before your FeatureJoiner

    This post is closed to further activity.
    It may be an old question, an answered question, an implemented idea, or a notification-only post.
    Please check post dates before relying on any information in a question or answer.
    For follow-up or related questions, 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.

    3 replies

    takashi
    Celebrity
    • takashiCelebrity
    • September 3, 2025

    Hi ​@tullusΒ ,

    FeatureJoiner outputs features through the <Rejected> port, if a Join On attribute was <null>. It's an intentional behavior, see also the Help on FeatureJoiner.

    Configuration / Output Ports / <Rejected>
    Invalid features from any input port. Features will be rejected if a Join On value is missing or null.

    Β 

    If you want to continueΒ the translation when a feature was rejected, try connecting a transformer e.g. Logger or Junction to the <Rejected> port.

    Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
    alexbiz
    Influencer
    Forum|alt.badge.img+33
    • alexbizInfluencer
    • Influencer
    • Best Answer
    • September 4, 2025

    Maybe the best strategy would be to filter those features without values (using a simple tester) before your FeatureJoiner

    Draw it, map it, shape it, fix it, share it, change it, send, translate it 🎡
      tullus
      Observer
      Forum|alt.badge.img+1
      • tullusObserver
      • Author
      • Observer
      • September 4, 2025

      Thanks both. I filtered the features using the tester and then the feature joiner worked. Then I linked the other part of the tester to an Attribute Manager together with the feature joiner result. Kind of bypassed the <null> cells and them put them together in the process using the attribute manager.Β Worked well.

      Community Stats

      32,662
      Posts
      123,959
      Replies
      41,098
      Members
      Terms & ConditionsAccessibility statement
      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.