Match on a FILTERXML with exactly 1 value results in an unexpected #N/A. Why?

[HansDouwe]

Match on a FILTERXML with more values ​​works fine.
Match on a FILTERXML with exactly 1 value results in an unexpected #N/A.

I do not understand why. Can someone explain that?

Details in workbook!

[romperstomper]

MATCH requires either a range or an array as the second argument. A simple constant value will not work. The odd thing, to me at least, is that if you pass any single value that can be coerced to a number, it returns #N/A, whereas for text it returns #VALUE!, which seems more appropriate.

[HansDouwe]

As far as I know, an array can also consist of 1 element. =MATCH(1,SEQUENCE(1),0) just returns a 1 and not #N/A.
If that doesn't work with FILTERXML, I see that as an imperfection of Excel.

I then have to take that into account and that leads to 'weird' formulas.

[romperstomper]

Yes an array can consist of one element, but 1 is not an array, whereas {1} is. SEQUENCE always returns an array whereas it would seem FILTERXML does not if there is only one item. You can view that as an imperfection or not, but it's not going to change it.