Skip to content
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

Excel desktop version refuses to load and parse CF metadata file bigger than 1MB #4808

Closed
Yuri2b opened this issue Aug 21, 2024 · 3 comments
Closed
Assignees
Labels
Area: Excel Issue related to Excel add-ins Needs: author feedback Waiting for author (creator) of Issue to provide more info Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP Status: no recent activity Issue or PR is stale (no recent activity)

Comments

@Yuri2b
Copy link

Yuri2b commented Aug 21, 2024

Provide required information needed to triage your issue

I am converting a VSTO Excel plugin to use the new JS API. The current plugin has 500+ UDFs that need to be converted into custom functions. I have created a functions.json CF metadata file and have run into the problem that the desktop version of Excel refuses to load this functions.json file if it exceeds 1 MB. The same build works in web version of Excel without issues.

Your Environment

  • Platform: PC Desktop
  • Host: Excel
  • Office version number: Excel for Microsoft 365 MSO (Version 2406 Build 16.0.17726.20078) 64-bit
  • Operating System: Windows 11 Pro

Expected behavior

Add-in should be loaded successfully even its CF metadata file is bigger than 1 MB

Current behavior

Add-in loading failed with this error:
355028567-1819b096-78c0-412a-b47d-0c84de906aab

Looks like Excel doesn't even try to parse the CF metadata file if its size is bigger than 1 MB.
No [Metadata] [Parsing] [Begin] records appear in OfficeAddins.log file.

Steps to reproduce

  1. Create a new CF shared runtime project using the Yeoman template
  2. Add some dummy functions to src/functions/functions.ts
  3. Generate CF metadata file by the plugin or manually. Check that this file is bigger than 1 MB
  4. Run the project in dev mode or build and side-load your add-in manually
  5. Compare behavior in desktop and web version

Provide additional details

More details and steps to reproduce here: OfficeDev/Excel-Custom-Functions#422

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP label Aug 21, 2024
@shanshanzheng-dev
Copy link
Contributor

shanshanzheng-dev commented Aug 22, 2024

Hi @Yuri2b Thanks for reaching us. Just like OfficeDev/Excel-Custom-Functions#422, Currently we have a size limitation for the metadata of 1MB. We did some test before and found that around 20k CF may hit the limitation. So we'd like to suggest you to help reducing some description in the metadata file may helps. If we have any new updates, we'll report back. Thanks.

@shanshanzheng-dev shanshanzheng-dev added the Needs: author feedback Waiting for author (creator) of Issue to provide more info label Aug 27, 2024
@stevefengjin stevefengjin added the Area: Excel Issue related to Excel add-ins label Aug 28, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Status: no recent activity Issue or PR is stale (no recent activity) label Sep 1, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins!

Copy link
Contributor

This issue has been closed due to inactivity. Please comment if you still need assistance and we'll re-open the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Excel Issue related to Excel add-ins Needs: author feedback Waiting for author (creator) of Issue to provide more info Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP Status: no recent activity Issue or PR is stale (no recent activity)
Projects
None yet
Development

No branches or pull requests

4 participants