Forum Discussion
Dynamic-aware Excel incorrectly flagging our custom XLL functions as being array functions?
MicrosoftHi 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 Manager
JoeMcDaid thank you very much for the follow up! I am glad to hear that the RTD array disconnect issue has been fixed, and it's now 100% clear to me why Excel is behaving this way. It did not appear to be consistently converting existing formulas to CSE formulas when I first started playing with this feature, is this something that has been improved or can you share the circumstances when it's supposed to happen?
Lastly - are you considering adding any ability to flag the custom function itself as not being an array function, so that we wouldn't need to prefix it with @ to avoid it being saved as a CSe array functino? My only concern at this point with this is that files can be shared with users of older versions of Excel which will still have the RTD array disconnect issue.