Skip to main content

ExtendInsights Financial Reporting Add-in Known Issues (MVP / Early Access)

A list of known bugs and limitations with XAVI formulas in the MVP version of the Excel Financial Reporting Add-in. Updated as issues are resolved.

Updated yesterday

You're Testing an Early Build — Here's What to Expect

Thank you for being an early access tester of the CloudExtend Financial Reporting Add-in for Excel. You are using a pre-release MVP version. This means the product has not gone through full QA hardening, and you will likely encounter bugs beyond the ones listed here. That is expected and it is exactly why your participation matters.

We want you to break the system. The more scenarios you test, the more edge cases you expose, the faster we can ship a polished production release. Please submit feedback using the link below whenever you find something unexpected.

How to Provide Feedback

If you have found a new issue not listed in our Known Issues or just want to provide general feedback kindly use this link to provide feedback.


⏳ A Note on Balance Sheet Accounts

If you are working with balance sheet accounts (assets, liabilities, equity), expect formulas to take longer to resolve than income statement accounts. This is because balance sheet figures are summed from the beginning of time across all periods. This is by design in NetSuite, not a bug in XAVI formulas. Please be patient when these formulas are calculating.


Known Issues

XLAN-7823 — Subsidiary Change Triggers Cell-by-Cell Queries For XAVI.TYPEBALANCE (Slow Refresh)

Status: In Progress | Severity: High

When a user changes a parameter — such as the subsidiary used as a reference in a XAVI.TYPEBALANCE formula — the add-in sends individual queries to NetSuite for every single cell instead of batching them. This can cause resolution times of several minutes instead of seconds.

Steps to reproduce:

  1. Add a series of months (e.g., 1/1/25 through 12/1/25) as column headers.

  2. Add a subsidiary field as a reference cell for the formulas.

  3. Use XAVI.TYPEBALANCE as row formulas for Income, COGS, and Expense — including the subsidiary field parameter.

  4. Change the subsidiary value and observe that cells resolve one by one.

Workaround: Use XAVI.BALANCE or consider XAVI with wildcards such as $*. Engineering is actively investigating.


XLAN-7277 — Right-Click Drill Down is Broken

Status: Known Issue — Workaround Available | Severity: Medium

Right-clicking a cell and selecting CloudExtend > View Transactions does not work correctly. Instead of opening the drill-down view inline, it downloads transaction data to a new sheet alongside a blank app pane.

Example formula: =XAVI.BALANCE("6150", "DEC 2013", "Dec 2013")

Workaround: Use the drill-down option in the Task Pane instead of the right-click menu. This works correctly.


XLAN-7799 — XAVI.PARENT Formula Returns Null

Status: In Progress | Severity: Medium

The XAVI.PARENT formula is not returning values. For example, =XAVI.PARENT("4810") (replace 4810 with any account number) returns a null value instead of the parent account.

Workaround: None at this time.


XLAN-7782 — XAVI.BALANCE and XAVI.TYPEBALANCE Do Not Share a Default Subsidiary

Status: Known — Fix Planned for Production Release | Severity: Medium

For XAVI.BALANCE, the default subsidiary is set to top level consolidated company.

XAVI.TYPEBALANCE does not have a default subsidiary value. As a result, users of XAVI.TYPEBALANCE must explicitly enter a subsidiary value as there is no default fallback.

Workaround: Always supply the subsidiary parameter when using XAVI.TYPEBALANCE. This will be resolved in the production release.


XLAN-7768 — Broken Hyperlink for Customer Payment Records in Drill-Down

Status: In Progress | Severity: Medium

When drilling into accounts where payment records are part of the details the list includes hyperlinks back to the original NetSuite records. For customer payment records, the URL is incorrect and returns a broken link.

The transaction type in the URL must be custpymt, not customerpayment.

Workaround: Manually edit the URL in your browser, replacing customerpayment with custpymt.


XLAN-7666 — XAVI.PARENT and XAVI.TYPE Don't Reliably Update When Referenced Cell Changes

Status: In Progress | Severity: Low

When XAVI.PARENT or XAVI.TYPE use a dynamic formula pointing to another cell that holds an account number, changing that account number does not reliably trigger a recalculation of the parent or type formula.

Workaround: Clear the formula cache, then press Enter on the referenced cell to force resolution.


XLAN-7615 — XAVI.BALANCE May Return Wrong Values for Multi-Period Ranges

Status: In Progress | Severity: High

When XAVI.BALANCE is used to calculate more than one period (e.g., =XAVI.BALANCE("4107", "Jan 2025", "Mar 2025")), a caching issue may cause incorrect values to be returned. Notably, the drill-down view does return the correct numbers.

Workaround: Use XAVI.BALANCE for single periods only until this is resolved. Avoid multi-period date ranges in this build.


XLAN-7616 — Pre-Cache Triggers Unexpectedly After Leaving Workbook Open for Over an Hour

Status: Under Investigation | Severity: Low

After loading balance sheet accounts and leaving the worksheet open for more than approximately one hour, clicking into any cell with an XAVI.BALANCE formula triggers a pre-cache run. This causes unexpected recalculation behavior.

Note: This issue is intermittent and engineers have not yet been able to reliably reproduce it in a test environment. If you experience this, please submit feedback with details about your session.

Workaround: Refresh the Task Pane to stop the pre-cache from running.


XLAN-7597 — XAVI.CTA and XAVI.RETAINEDEARNINGS May Time Out and Return #VALUE!

Status: Partially Mitigated | Severity: Medium

The XAVI.CTA (Cumulative Translation Adjustment) and XAVI.RETAINEDEARNINGS formulas may run for an extended period and ultimately return a #VALUE! error. Engineering has increased the timeout thresholds, which has reduced (but not fully eliminated) the issue. Performance may vary depending on the size and complexity of your NetSuite account.

Workaround: Retry the formula. If it continues to fail, submit feedback with your account details so engineering can investigate.


XLAN-7488 — Refresh All Runs the Income Statement Report Twice

Status: In Progress | Severity: Low

When the pre-built Income Statement is loaded and the user clicks Refresh All, the report refreshes twice instead of once. This results in double the query load and a longer wait time.

Workaround: None at this time. The report will still display correct data, but will take longer than expected to complete.


How to Submit Feedback

Found something not on this list? Great — that's exactly what we need. Please use the feedback link above to report what you found, including:

  • The formula(s) you were using

  • The accounts or subsidiaries involved

  • Steps to reproduce, if possible

  • A screenshot or error message if available

Every bug report moves us closer to a production-ready release. Thank you for your time and patience.

Did this answer your question?