User Profile
JoeMcDaid
Joined 10 years ago
User Widgets
Recent Discussions
Re: Named ranges with certain formulas don't return correct result
PeterBartholomew1 Thanks for looping me in here. Engineering have completed an investigation, and this is a long-standing bug. It's difficult to see any scenarios where the current behavior would be preferred as it's effectively truncating the users array, so we plan to take up a fix. Being a calc fix, we'll roll this out very slowly to ensure there are no unforeseen issues.2.8KViews1like0CommentsRe: A statement of truth or a wasted opportunity. Lambda helper functions reluctant to return 2D arrays.
SCAN iterates through the provided array argument in row-major order and returns its output in the same shape as the array argument. So this behavior is expected, array-of-array are not encountered as each iteration of SCAN only returns a scalar.6.3KViews0likes56CommentsRe: A statement of truth or a wasted opportunity. Lambda helper functions reluctant to return 2D arrays.
1x1 and scalars are distinct in Excel. =TYPE(1) returns 1. =TYPE({1}) returns 64. The Arrays of Arrays limitation is a long standing limitation, it doesn't serve a purpose per se - its just something that was never supported even in the CSE days. Now that arrays are more prominent, the limitation is more apparent. Changing this behavior has backcompat implications, so anything we do here in future needs careful engineering and consideration. It also needs to be weighed and prioritized against other customer asks.6.5KViews1like1CommentRe: Ways of performing Accumulation with Dynamic Arrays
PeterBartholomew1 This has been a great thread! Thanks to all the contributors. We just announced a new wave of lambda functions that I think will greatly help these scenarios. In particular, REDUCE, SCAN, BYROW and BYCOL.10KViews1like3CommentsRe: Using dynamic arrays to populate named ranges for ListBox Controls is unstable - user error?.
That does look rather odd. This is the first report I've had of this so, unfortunately, I don't have any quick answers. Would you mind crafting a simple workbook that reproduces the issue that you could share?5.9KViews0likes4CommentsRe: How old is VLOOKUP?
ExcelTL It's actually a little older, that's when it arrived in Excel. I believe VLOOKUP first appeared in Lotus 1-2-3 which predated Excel. According to Wikipedia, Lotus 1-2-3 launched in January 1983, so VLOOKUP appeared sometime around then. VLOOKUP was actually the successor to the original lookup style function, LOOKUP(), which first appeared in VisiCalc in 1979. LOOKUP was created to help with Bob Frankston's tax return. You can read about it here. LOOKUP and VLOOKUP have an amazing history, dating all the way back to the very early days of spreadsheeting. Hats off to the early spreadsheet pioneers.6.1KViews3likes2CommentsRe: #SPILL! Error when doing VLOOKUP?
Hi Jennifer Corcoran , This is likely because your VLOOKUP is looking up multiple values in the first argument (the red text below). =VLOOKUP(A:A,B:B,1,FALSE) By looking up A:A you are asking Excel to lookup a million cells. In the past this worked because Excel didn't know how to lookup multiple values, so it threw all but one away. This behaviour was called "implicit intersection". With the introduction of Dynamic Arrays, Excel now supports looking up multiple values and no longer does implicit intersection silently. If there isn't enough space to return the values you will see the #SPILL error. To modify your formula to return just a single value, you can use one of the following techniques: 1. Modify you formula to use the new implicit intersection operator @ to select one lookup value. =VLOOKUP(@A:A,B:B,1,FALSE) 2. Simply reference a single cell and copy down. =VLOOKUP(A2,B:B,1,FALSE) Both work but my preferred option is 2 as it is the simplest. Regards, Joe [Excel Team]102KViews3likes19CommentsRe: Dynamic-aware Excel incorrectly flagging our custom XLL functions as being array functions?
Hi GabrielMichaud, As UDF's are able to return arrays or ranges, Excel must save it as a CSE array for Pre-DA Excel to ensure it calculates the same way. The only exception is where it is consumed by a function that expects arrays or it is implicitly intersected using @. So for instance, you can enter =SUM(MYUDF()) or =@MyUDF() in DA Excel and it will not be array entered in Pre-DA Excel. For a full list of functions that can return an array visit this page: https://support.office.com/en-us/article/excel-functions-that-return-ranges-or-arrays-7d1970e2-cbaa-4279-b59c-b9dd3900fc69 We recently fixed the RTD array disconnect issue and have released it to insiders for testing. Please let me know if it has addressed the disconnect issues. Regards, Joe Excel Program Manager1.8KViews0likes1Comment