-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🔥 URGENT: Excel corrupts files with Pivot tables based on the output of custom functions which include formatted number values #4915
Comments
Hi @wh1t3cAt1k Thanks for reporting this issue. |
@shanshanzheng-dev perhaps you're not selecting the header row when creating the pivot table. I will update the issue description. |
Thanks @wh1t3cAt1k we're actively investigating the issue. |
@wh1t3cAt1k @jgamboavx Thanks for your information. MACNotRepro.movcf-issue.mp4 |
@XuanZhouMSFT I just retraced the same exact steps as in your Windows recording, and the problem is present: The error log:
As a sanity check, I also cleared the addin cache, with the same result. The only other difference I can see is the product version. Given that there are differences in Office.js's behavior when used with regular O356 licenses versus a Office 2021 perpetual license, could the difference in versions here explain why the issue does not reproduce for you? Here's a video recording of me retracing your steps: repro.mp4 |
Thanks @jgamboavx for the quick response. Meanwhile, could you help to double check from your place with some other steps to see if the issue still repro.
We want to know if the issue is only happens with formula or also repros for other FormattedNumber. Thanks in advance. |
@XuanZhouMSFT do you guys also use a different (compliant) CDN for the Office.js bundle? If yes, maybe it's important to use exactly the same Office.js library as us (from the usual CDN). |
@XuanZhouMSFT , repro2.mp4 |
@jgamboavx Thanks for the testing. So it seems doesn't related to CF rich data but related to pivot table and maybe FormattedNumber. We will help to re-path the issue internally to further investigation. @wh1t3cAt1k We already confirmed that it doesn't caused by CF side, so the CDN should not be a problem. Thanks also for the remaindering. :) |
@XuanZhouMSFT could it also depend on the regional settings of the OS? @jgamboavx please let us know what the settings are on your machine (digits separator, date format etc.) |
I synced my setting to be same as @jgamboavx but still fail to reproduce. |
@XuanZhouMSFT not the same in this menu. Mine are: However, the issue still reproduces after changing my settings to match yours. So it's likely not related to regional settings |
Agree with you @jgamboavx , after sync to your version, it also couldn't reproduce. |
@XuanZhouMSFT is there any other team member on your side who can try to replicate? |
@wh1t3cAt1k I already asked several members for some help on this case. And we event created several test account to test. But until now, none of us could able to reproduce. :( |
@XuanZhouMSFT how can we help? We can do a joint call with @jgamboavx if you are able to remotely collect data for troubleshooting? It's not just us, it's our customers complaining too, so clearly it's not just an issue with a developer's machine... |
@wh1t3cAt1k How about we have a debug session after tomorrow sync meeting? It is already mid-night for us. Perhaps not all of us could attend the meeting now. |
Yes please shoot us an invite, you know my email! |
Your Environment
Steps to reproduce
Actual result:
Recovery process removes the pivot table (!):
If you replace the FNV in the code snippet with any primitive value, repeat the process and see how the issue does not reproduce.
Expected result:
Pivot tables should work just fine with FNVs...
Context
This issue is a support volume driver for Velixo and does not have any recovery. This started happening relatively recently.
We currently had to disable all FNV support in our apps to prevent being overwhelmed with support requests. Please fix this soon!
Sample of the corrupted file
Repro (1).xlsx
The text was updated successfully, but these errors were encountered: