BigSpill: A 90‑Function Excel LAMBDA Library for Dynamic Arrays
What is BigSpill? BigSpill is an Excel LAMBDA library containing 90 functions across 10 categories, built from extensive experimentation with dynamic arrays. The goal is to provide elegant, efficient tools that make sheet‑level formulas easier to read, more modular, and more dynamic. The library includes a mix of: quality‑of‑life helpers essential primitives mid‑level operators developer‑level tools a few functions you might not expect to see in Excel Who is it for? Everyone. BigSpill aims to make complex operations more approachable and expressive. A few examples from the library: Pairwiseλ Staircaseλ Grainλ PolarGridλ Convolveλ Foldλ Tessellateλ Revealλ Knapsackλ Magnifyλ Traverseλ The repository includes full documentation and 11 sample workbooks so you can explore the functions without setup. If you’re interested in experimenting with dynamic arrays, or LAMBDA workflows, feel free to take a look. Feedback and suggestions are always welcome. I've attached 1 onboarding workbook. There are 10 more at the link below. GitHub: BigSpill
When #VALUE! isn’t an error: The hidden reference behavior of Excel’s dynamic arrays
1. Mechanism Overview Functions such as TAKE, DROP, OFFSET, and INDIRECT normally produce a range when supplied with scalar parameters. When instead a 1-D or 2-D numeric array is passed to one of these parameters, Excel attempts to generate multiple range outputs (one per array element). Since Excel’s grid architecture does not allow a single function call to return multiple ranges in parallel, the function fails. The visible result is an array filled with #VALUE!. Example patterns: =TAKE(range, {1;2;3;4}) =DROP(range, {1;2;3;4}) =OFFSET(range, {1;2;3;4}, {1,2,3}) =INDIRECT("A1:B"&{1;2;3;4}) Excel returns: { #VALUE!; #VALUE!; #VALUE!; #VALUE! } Although the values appear identical, each #VALUE! is associated with a distinct internal range reference corresponding to the attempted slice, offset or address. This is a side effect of Excel’s reference-binding layer, which attaches metadata to #VALUE! propagation structures when a reference-producing function fails after partially resolving its operands. 2. Behavior Characterization 2.1 Reference Retention Each #VALUE! error produced by the above functions contains a deferred reference representing the range the function attempted to construct. The reference is not materialized because: a multi-range return is not allowed, and the evaluation is aborted at the final conversion stage. However, the binding phase (operand resolution) has already created a reference object. This object is preserved internally and passed forward along the calculation chain. 2.2 Deferred Evaluation Functions that inspect operand values (e.g., SUM, MIN, COUNT) cannot extract data from these encapsulated #VALUE! tokens and will propagate the error. Functions that inspect operand references — such as MAP, SCAN, REDUCE, MAKEARRAY, and aggregation functions that re-evaluate their inputs individually — trigger evaluation at the point of consumption. Example: =MAP( TAKE(range, {1;2;3;4}), SUM ) In each MAP iteration: ref is a #VALUE! carrying an unresolved range reference. SUM(ref) requests value-level evaluation of that range. The reference is resolved at that moment only. The resulting scalar is passed downstream. Thus, the #VALUE! error acts as a strict thunk. 3. Functional Implications for Formula Construction 3.1 Range-Object Semantics The technique enables modeling of ranges as first-class reference structures, not arrays of extracted values. This allows: passing range slices through pipelines keeping intermediate objects lightweight avoiding large intermediate spillage reducing recalculation costs for multi-slice operations 3.2 Lazy Slice Evaluation Using {n1; n2; …} arrays in index parameters creates a vector of deferred slices. Functions downstream resolve these slices on demand and only for the specific iteration that needs them. This is especially useful for: sliding-window logic multi-pass transformations tree/graph-like iterative algorithms in Excel dynamic partitioning of ranges recursive constructions implemented with SCAN/REDUCE
Help with a simple calculator for figuring a calculated cost
Hello, I am making a simple calculator for work. I enter square footage in cell E16 and have an equation to give a dollar value in cell K16. Trying to make things simple for others to price a job. This is my formula (=E16*0.45) in cell K16 that works perfect for my needs except for one thing. I need to set a minimum value for this equation. The formula needs to have an equal to or greater than 300 rule. I have a minimum price of 300 for any job done. So for example if I enter 500 square foot in E16. Cell K16 currently will have 225 as the value (500*0.45=225) but I need it to calculate 300. Any square footage over 667 will give me the value greater than 300 then. Please help me with this as I have looked over all the help topics and many forum threads but nothing seems to help. Using Excel with Office 365 on Windows 11 PC. Pictures below for reference. Thanks for your time - Chad
Excel Desktop Filter Checkboxes Not Visible – Windows 11 / Office Home & Student 2021
Excel Desktop Filter Checkboxes Not Visible – Windows 11 / Office Home & Student 2021 I am facing a persistent display/rendering issue in the Excel desktop application when using filters. When I apply a filter to a column, the filter dropdown opens correctly and the values are displayed. The filter functionality itself also works. However, the checkboxes beside the individual values are not visible properly. As shown in the attached screenshot, the values such as 11, 12, 22, and 34 are displayed in the filter list, but the checkbox controls beside them are either missing/not rendered correctly. Interestingly, the Select All checkbox area also appears abnormal. System details Operating System: Windows 11 Microsoft Office: Home & Student 2021 Application: Microsoft Excel Desktop Office is fully updated with the latest available updates. The same Excel file works correctly in Excel for the Web, where all filter checkboxes are displayed normally. Troubleshooting already performed by Microsoft Support Microsoft Support has already remotely checked the system and tried several troubleshooting steps, including: Reinstalling Microsoft Office Creating/modifying relevant Windows Registry entries Creating system restore/checkpoints during troubleshooting Creating and testing with a new Windows user profile Checking and installing all available Office updates Unfortunately, the issue still persists. Since the problem does not occur in Excel for the Web, it appears to be specific to the Excel desktop application's UI/rendering on my Windows 11 system. Has anyone experienced a similar issue with filter dropdown checkboxes not rendering or appearing invisible in Excel Desktop? Could this be related to: Excel hardware graphics acceleration/rendering Windows display scaling or DPI settings GPU/display drivers Office 2021 UI rendering Windows 11 accessibility/display settings A known Excel Desktop bug Any suggestions, known fixes, or confirmation of a similar issue would be appreciated. Screenshot attached for reference.Excel puzzle - can't type into cell, exhausted support steps, need a tech wizard !
Excel desktop app on Mac won't let me edit cells (Word is fine) already tried a full uninstall/reinstall with support MacBook Air, macOS Tahoma 26.2 - Microsoft 365 Premium subscription - Excel for Mac, Version 16.111.1 Problem: In the Excel desktop app I can navigate the sheet and select/highlight cells, but I cannot type into a cell or into the formula bar Already tried with a Microsoft support agent: 1. Confirmed subscription is active 2. Removed the Office license from Keychain Access 3. Fully removed the Office apps, emptied the Trash. 4. Reinstalled Office from account.microsoft.com 5. Result: Excel still won't let me type in a cell or in the formula bar, even in a new book 6. "Allow editing directly in cells" enabled. 8. Confirmed the keyboard itself is fine: Cmd+C works inside Excel, types normally in TextEdit 9. Opened Excel in safe mode (held Shift while launching) and creating a new blank workbook — issue persisted. Microsoft support agent confirmed this isn't a subscription/activation issue and isn't a general keyboard/OS issue, since Word, TextEdit, and Excel's own search box all accept input normally — the problem is specifically isolated to typing into a cell or the formula bar in Excel. Any ideas on what else could be blocking keyboard input specifically in Excel's grid/formula bar (e.g. a stuck editing mode, add-in, or accessibility permission specific to Excel) would be ! VERY ! appreciated.
Does a LET variable get computed even if it's only referenced inside IFNA's fallback argument?
In the formula below, expensiveMatch is defined in LET but only referenced as IFNA's fallback argument: =LET( matchRow, XMATCH(1, (A1=Sheet2!$A$1:$A$1000)*(B1=Sheet2!$B$1:$B$1000)), x, INDEX(Sheet2!$C$1:$C$1000, matchRow), expensiveMatch, INDEX(Sheet3!$C$1:$C$500, XMATCH(A1&B1, Sheet3!$A$1:$A$500&Sheet3!$B$1:$B$500)), IFNA(x, expensiveMatch) ) Question: When x resolves successfully (no #N/A), does expensiveMatch still get computed because it's a top-level LET variable - or does Excel skip it since IFNA's fallback argument is never reached? I know IFNA short-circuits its fallback argument, and LET avoids recomputing a variable if referenced multiple times - but I haven't found much documentation on the behavior of Let. Is the below a more efficient way to write the formula? =LET( matchRow, XMATCH(1, (A1=Sheet2!$A$1:$A$1000)*(B1=Sheet2!$B$1:$B$1000)), x, INDEX(Sheet2!$C$1:$C$1000, matchRow), IF(ISNA(x), INDEX(Sheet3!$C$1:$C$500, XMATCH(A1&B1, Sheet3!$A$1:$A$500&Sheet3!$B$1:$B$500)), x ) ) Is this restructuring necessary, or does the first version already skip the unused computation? Basically I'm wondering if Let computes lazily/defers calculation in the way SQL's optimizer works. Input from anyone with insight or knowledge into the calc engine would be greatly appreciated. Thanks (Currently on Microsoft Excel for Microsoft 365 MSO (Version 2607 Build 16.0.20228.20190) 64-bit)
GLSU Excel add-in fails to load after Office update from Version 2607 to 2608
Our Excel add-in, Process Runner GLSU , fails to load after Microsoft Office updates from Version 2607 to Version 2608. This started August 17, 2026 and is actively growing in scope. Error messages: Excel: Cannot run the macro 'onLoad' VBA: System Error &H80004005 (-2147467259). Unspecified error VBA: Compile error in hidden module: ThisWorkbook Has anyone encountered similar issue with their own custom add-on. If yes, any pointers to fix it. We are seeking help on priority. Thanks, Vrushali Pawale, Sr. Manager, Insightsoftware.Braille Translator Challenge
Using the Braille Alphabet lookup table provided: Part 1 - convert the given phrase from Braille to words. Part 2 - convert the given phrase from words to Braille. ✅ Solutions should be in the form of a single-cell formula. ✅ Generalized Lambda functions are welcome, provided the function definitions are included with your solution. ✅ Keep in mind, the "best" solution is not necessarily the shortest... Strive for conciseness, if you wish; just don't let your solutions be ordinary. 😉 Good luck and have fun!Benutzerdefinierte Listen gelöscht/lässt sich nicht öffnen
Hallo, ich habe ein Problem mit dem automatischen Ausfüllen von Monaten, Wochentagen, Zahlen etc. Meine Systemeinstellung für den PC war in Englisch eingestellt, dabei ging das automatische ausfüllen nur mit den englischen Begriffen. Nach Umstellung der Systemsprache auf Deutsch hat Excel gar keine benutzerdefinierten Listen mehr. Wenn mein auf Optionen -> Erweitert -> benutzerdefinierte Listen bearbeiten klickt, dann wird auch das Fenster nicht geöffnet. Wenn ich die Systemsprache wieder auf Englisch zurückstelle, dann funktioniert es wieder (nur in Englisch). Warum ist das so? Was kann ich machen, damit es wieder klappt?
