Share via

User-defined LAMBDA functions involving thunks evaluate to #VALUE! errors when saved in .xlsb workbook

Anonymous
2024-05-17T15:07:46+00:00

I will outline a simple process that demonstrates this issue

  1. Create a new workbook
  2. Define a LAMBDA function in Name Manager called "thunk" with definition =LAMBDA(x,LAMBDA(x))
  3. In A1, enter =thunk(5)(), which as expected will evaluate to 5
  4. Save this workbook as an xlsx, xlsm, and xlsb so that there are three versions of the file
  5. Reopen each of these workbooks, click into A1 as if to edit the formula, and then hit enter to reevaluate

At least for me, this always results in the xlsb formula evaluating to #VALUE!, while the xlsx and xlsm formulae have no issues. The xlsb formula can be fixed by going into Name Manager and redefining the function, but this is inconvenient. Is this a bug, or is it an unavoidable consequence of the xlsb format? Is it somehow an issue with my version of Excel?

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2024-05-17T20:03:20+00:00

    Interesting - this is my version. Strange because it says that I am up to date.

    Image

    I tested in the April 2024 release and it is not an issue there. I guess this must have been fixed - would be curious to hear if anyone else can replicate in the semi-annual enterprise channel.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-05-17T17:08:55+00:00

    OK with all three versions here.

    Was this answer helpful?

    0 comments No comments