AutoSave disabled when opening SharePoint-synced files from Finder after macOS Tahoe 26.6 update
Files stored in SharePoint Online and synchronized locally through OneDrive are opened as local documents when launched from Finder. Office applications display "Saved to my Mac" and AutoSave is turned off by default. However, opening the exact same files through Word/Excel > Open > Sites, or via SharePoint "Open in Desktop App", correctly identifies them as cloud documents. In that scenario, AutoSave is enabled and collaboration/version history features work as expected. Troubleshooting already performed: OneDrive reset and re-linked SharePoint library re-synced Signed out and back into both Office and OneDrive Removed Microsoft credentials from macOS Keychain and re-authenticated Recreated local OneDrive sync relationships Verified OneDrive File Provider extensions are enabled Verified Office applications and OneDrive are fully up to date Tested with newly created files and existing files Tested "Always Keep on This Device" with no change in behavior The issue appears to be specific to the Finder-to-Office launch path after upgrading to macOS Tahoe 26.6. Before upgrading to macOS Tahoe 26.6, opening the same SharePoint-synchronized files directly from Finder correctly preserved cloud document identity and AutoSave was enabled as expected. I discussed this issue in detail with Apple Support, but they quickly dismissed it, saying that the problem is not on Apple's side and that I should contact Microsoft instead.
Slicer not updating when source data is updated
Hello, I have a dashboard showing project data with multiple pivot tables. There are two slicers that are connected to all the pivot tables, Project ID and Project Status, these used to update when the source data changed but this is no longer the case and still doesn't update after refreshing the data. E.g. The Project Status of Project LIB682 changed from Active to Closed in the source data, however, if I select 'Active' in the Project Status slicer, LIB682 still appears in the ID slicer where it used to be greyed out to show it is not active. I have tried refreshing data and deleted and re-added the slicers but neither of these worked. When I first created the dashboard everything worked and I've not changed anything so would assume it should still be working. TIA
Lambda that uses INDEX with array arguments behaves inconsistently when saved in the Name Manager
Hello, I have encountered what appears to be inconsistent behavior when a particular type of lambda is saved in the Name Manager. The issue seems to occurs when the LAMBDA uses INDEX with either the row_num or column_num argument supplied as an array. The following is a minimal reproducible example: The formula "=LAMBDA(arr,INDEX(arr,1,{1,2,4}))({1,2,3,4})" correctly evaluates to {1,2,4}. Now, save the lambda as TEST (or any other name) in the name manager. The formula "=TEST({1,2,3,4})" also spills the expected array {1,2,4}. However, when the result is passed to another function, the behavior changes. For example, "=SUM(TEST({1,2,3,4}))" and "=COLUMNS(TEST({1,2,3,4}))" both evaluate to 1. In contrast, using the lambda inline instead of the defined name produces the expected results: "=SUM(LAMBDA(arr,INDEX(arr,1,{1,2,4}))({1,2,3,4}))" returns 7, and "=COLUMNS(LAMBDA(arr,INDEX(arr,1,{1,2,4}))({1,2,3,4}))" returns 3. Unfortunately, I am unable to attach a workbook to this post. Additionally, the issue is not reproducible on every machine I have tested, although it is consistently reproducible in Excel for the Web. I am currently using Excel version 2607 on the Current Channel. Does this appear to be expected behavior, or is it a bug? In the meantime, what would be the best way to mitigate this issue? I have found two potential workarounds. The first is to prepend the result of the named lambda with a unary + (e.g "=SUM(+TEST({1,2,3,4}))"), which appears to force excel to treat the result as an array. However, when using a shared lambda library (as is the case for most of my team), users generally do not know the implementation details of each lambda, so it is difficult to determine when this workaround is necessary. The second approach is to avoid passing an array to the row_num or column_num argument of Index by using MAP. For example, the TEST lambda defined above can be rewritten as =LAMBDA(arr,MAP({1,2,4},LAMBDA(idx,INDEX(arr,1,idx)))), which causes it to behave as expected. However, I am concerned about potential performance implications. Intuitively I would expect that a single INDEX call with an array argument would be more efficient than multiple INDEX calls wrapped in MAP, but I do not know whether this is the case. Has anyone else encountered this behavior before?Currency Formatting adding additional periods to number
Hi, This has started happening on Excel and its baffling me so I thought I'd reach out to the community to see anyone can help. This is Excel v2606 (M365) with latest updates. Issue: I have a new work book and in a cell I simply add the number 20 I right click the cell with the 20 in it and select "Format Cells.." and change it to currency and this happens If I go back into "Format Cells" the selection has moved from Currency to Custom and it shows this: And clicking on Currency the format is shown as this: No matter what I do I can't get it to format correctly, if I change the format back to "General" it goes back to being 20. I've tried doing an online repair and that hasn't had any affect. Any help gratefully received. Rob
autocomplete stopped working after update
Office 365 just updated. Now, autocomplete only works for some columns. So if I'm in column A, and typing the exact same text from the cell directly above, the text will suggest autocomplete and I can hit enter and move on. However, in column B, exact same text is never given autocomplete option. If I copy any cell from column A and paste in column B, that cell will now autocomplete. However if I copy and paste only formatting, the new cell will not autocomplete. None of this was an issue until the auto update that happened today after I restarted. Also, this issue is only in existing workbooks. If I create a new workbook, a cells seem to be fine in terms of autocomplete.
Unable to stop values field from calculating in pivot tables
Hello. I’ve created a pivot table where all the other fields are set up correctly. However I am unable to just include data in the “values” without it performing a calculation. Tried multiple times to select “no calculation” but doesn’t seem to work. Device is MacBook Pro. Excel 2016
