I was excited to start using XLOOKUP, but am distraught to see that it "looks up" blank cells and 'matches' them to the first blank cell found in the lookup array!
If you're like me an your lookup arrays are usually full-columns, which always have blank cells at the bottom, this is NOT GOOD!
When one uses VLOOKUP, and the lookup cell is blank, it would return an error, which was great, since one could nest the vlookup formula within the 'iferror' formula like this,
=iferror(vlookup(...),"")
so if the lookup was blank the result would be blank. SO this iferror formula would address any non-found values or blanks, and if you forgot the iferror formula the 'results' would remind you with their #N/A values.
Xlookup addresses non-found values within the formula itself ('if not found' parameter), which is nice, but since it matches blank lookup cells to blank cells in the lookup array, it will still need to be sandwhiched with another formula; I'm thinking:
=if('lookupcell'="","",xlookup(...))
which certianly detracts from the excitement. Also, if one forgot to nest a vlookup formula within an iferror formula, the error results would serve as a reminder. For Xlookup, howver, if one forgets to address blanks, it will likely generate clean-looking results that are not desired. For this reason I would prefer Microsoft change the xlookup to return error (or the not found parameter) if the lookup cell itself is blank. Anyone else agree? Any other suggestions or workarounds towards addressing my blank-blank match concern?
xlookup of blank cell.JPG
Bookmarks