Office-js: Range.getDirectPrecedents issue when equivalent XLL are specified

Created on 21 Oct 2020  路  4Comments  路  Source: OfficeDev/office-js

We are developing an Excel JS addin which makes use of custom functions, and we also have equivalent XLL specified in our manifest for compatibility with our legacy COM addin. We welcome Office JS team's efforts on constantly bringing new functionality to us, one of the latest of which is Range.getDirectPrecedents api.

Invoking the api mentioned on a cell which contains one of our custom functions and a further context.sync() is throwing an "internal error" with no meaningful description. We spent a while trying to figure out the error cause, and we finally managed to find out that we don't get any error if we remove EquivalentAddins tag from our manifest.

Expected Behavior

No error, direct precedents returned.

Current Behavior

We are getting RichApi.Error: An internal error has occurred.
image

Any further manipulation within workbook leads to the error modal being displayed:
image

Steps to Reproduce, or Live Example

Minimal repro: https://github.com/sshukurov/getDirectPrecedentsIssue

  1. Build and run the repro on Excel on the web instance.
  2. Insert numbers to a couple of cells.
  3. Insert a formula on a third cell referencing the cells with numbers: =ADD(FirstCell, SecondCell) (note the CONTOSO prefix is not needed because XLL equivalence is specified in the manifest).
  4. Select the cell with the formula, click 'Run' on the addin's side panel.

Your Environment

  • Platform: Office on the web
  • Host: Excel
  • Operating System: Windows 10 Pro Version 2004 OS build 19041.572
  • Browser: Google Chrome Version 86.0.4240.111 (Official Build) (64-bit)
Excel custom functions

Most helpful comment

Thanks @wh1t3cAt1k for your ask, the issue was fixed, it is rolling out stage, but not yet deployed to production.

All 4 comments

Thanks @sshukurov for reporting this issue, we can repro this issue, a bug(4580782) is created to track this issue.

Hey guys, also encountering this issue, any update so far? @lumine2008

Thanks @wh1t3cAt1k for your ask, the issue was fixed, it is rolling out stage, but not yet deployed to production.

@lumine2008, has the fix reached the production yet?

Was this page helpful?
0 / 5 - 0 ratings