Problem is filter node

[asan]

Hi all,
I have a very weird problem in a filter node.
The input of my filter is a Baserow node (with getAll method). I had some weird behaviors so I tried to understand by simplying my Baserow database (I first wanted to use the filter function inside the Baserow node but I couldnt make it works). I end up with the following:

• I only have two similar elements in my filter input (I duplicated a single row in the database so that they only differ with the id_row)
• I apply a filter on an other field (not on the id_row) and the output of the field only contains one of the rows instead of both…
  
  
  
  
  

Have you ever experienced something similar?
Thanks for your answer,
asan

[EmeraldHerald]

Hi @asan Welcome to the community

While we’d need some example data structure for Baserow and an example workflow, I have a suspicion of what you might be running into. Can you check this post out by my teammate and see if this fixes it up for you? Your webhook node might only be returning one item, so your current expression will only work for the first item arriving on the current node. You could try an expression of {{ $('Webhook').first().json.body.items[0]['Votre Groupe Local'][0].id }}, for example.

"Set" losing value? Bug?

Hi @xewonder, this is because your Set node returns only a single item, but subsequent nodes return multiple items. Now what would happen for an expression like {{ $node["Set"].json["insertId"] }} is that for the first item on your MySQL2 node, n8n would look up the first item on your Set node (which works). For the second item, n8n would look up the second item on your Set node which won’t work and so on. To avoid this, you would want to use an expression like {{ $item(0).$node["Set"].json["i…

If not, can you please provide an example workflow that wouldn’t take credentials (outside of Baserow) and also an example of how your Baserow database is set up? That way we can test