Bug? Compare node not excluding fields as instructed

Describe the problem/error/question

I am using a Compare node to compare datasets, and I am having an issue with it including some fields in the comparison when I have asked it to exclude them. I don’t know if this is a bug, it seems it could be, although I could be doing something wrong too.

Screenshot showing the Compare node is showing id is different between the two datasets, even though I have it set to skip comparing. Also the property_repo field, and some others.

Screenshot of some of the fields I’m excluding, particularly you’ll see I’ve included both forms of id just to be sure.

But then you’ll see below that it respects some other fields fine. Particularly the name field, which you will see is included in the skip comparison list above.

Please share your workflow

I’m just including the Compare node, because the datasets are loaded from my local disk. If you need me to export a sample of the data I can do that.

Information on your n8n setup

  • n8n version: 1.10.0
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker/Local

Hey @protechtedd

could you provide some inputs for tests, which replicate the issue?

Sure, I just stripped down the original data into just a thin slice to make an example. I pinned the results into the Compare node i’m working with. See if that works for you, if not then I can also send the original .csv files I’m processing.

In particular if you look at the id and name fields, they are in the “skip comparing” box, but they still show up in the “different” section in the results, whereas they should show up in the “skipped” section like all the other skipped fields.

I just looked at the node that I pasted above and it doesn’t include the “Different” or “Same” columns like I see it in my n8n instance. In case that happens for you too, I pasted the whole workflow below. Everything is pinned now except the Compare, so I think you can just run it and then look at the output.

Not a bug, your fields id and name have an invisible character in them.

You can also find it with

or

your options -

  • understand where this is coming from and fix it
  • preprocess and remove invisible characters
  • add both the field names - with and without the hidden character to the skip list in the Compare node.
2 Likes

Wow, that is so bizarre, since I’m getting the data via the Notion API directly. Okay well at least I have a path forward now. Thanks for pointing this out to me, I was starting to question my sanity.

1 Like

Ok I think I found an immediate solution. On the Extract A/B nodes, I enabled “Exclude Byte Order Mark (BOM)” and it removed the invisible characters.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.