Forum Discussion
Despair over external references to local scope Lambdas
I have no solution or workaround, but that's better to discuss with AFE team here Issues · microsoft/advanced-formula-environment (github.com).
SergeiBaklanThanks for replying to my post. My bugbear is not with AFE. It would be nice if it respected local Lambdas but the real problem here is with Excel.
When it's better to separate. AFE is not part of the Excel, actually that's third-party product. Even if Cambridge is under Microsoft umbrella.
If you add directly in Name Manger, like myLamda=LAMBDA(x, x+1), it could be in sheet or workbook scope, as we define. AFE always use only workbook scope.
SergeiBaklanThe only workaround I can think of is to create a VBA macro which I can give the input "myFunc" and which scours all the Worksheets in my Workbook to create a new global Lambda bugFix_Worksheet_myFunc and defines that to be =Worksheet!myFunc.
This is blooming awful.
