Skip to main content

Hello my fellow FME’ers,

Probably I'm missing something or I stumbled upon a bug, but I can't get something to work like I expect. Maybe someone can point out what I'm missing.

 

Workspace snippet

My data is going trough a Matcher to find features that belong to the same object. I then sort them on _match_id and an attribute called lighted.  

Result of Sorter_4

As a result I have something above. If lighted is null it will be the first feature.

In the AttributeManager I use Adjacent Features to look 1 feature further and have the following condition statement for a new attribute called _filter. The second one is another attempt to get the same result, but that also doesn't work.
 

Conditional statement 
Alternative conditional statement I tried

I expect the two <null> values in the screenshot above to get the value ‘yes’, but it doesn't. What am I missing here?

Hi ​@matthieuv ,

In my quick test, I wasn’t able to reproduce the issue you described, with FME 2024.2.5. The two <null> rows got ‘yes’ as shown below. See also the attachment.

Can you share a workspace and related dataset which reproduce the issue?


Possibly a case issue? I see in statements you are using “Lighted” but in the data screens shot its “lighted” with a lower case “L”.

 


Can't believe I missed that 😮

But also a little bit strange that FME doesn't say the attribute Lighted doesn't exist.


I feel like i can sometimes reproduce the behaviour in 2025.1.2. but then it disappears again, I haven’t been able to pinpoint something that causes it. At one point I copied a working conditional from attributemanager A into attributemanager B and both attribute managers stopped working. 

 

edit: lol my test workbench has problems with feature order playback it seems :P so thats causing my problem. Sorry everyone