Skip to content

Integration- Unable to upgrade Netsuite connection #104687

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.5.16-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #103927
Email or phone of affected tester (no customers): duytestnguyen+dk49@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11 Chrome
App Component: Workspace Settings

Action Performed:

Preconditions:

  • Have one or more connections connected to the NetSuite accounting integration over SOAP TBA.
  1. Open https://staging.new.expensify.com/
  2. Navigate to Home
  3. Navigate to Workspace settings
  4. Click on Accounting

Expected Result:

At Home, Verify that a time-sensitive item corresponding to each workspace connected to NetSuite over SOAP TBA is displayed.
Verify that there is a notice below the Last synced notice asking to upgrade the NetSuite connection.

Actual Result:

There is no option to upgrade Netsuite connection in Accounting and there is no time-sensitive item corresponding to each workspace connected to NetSuite over SOAP TBA is displayed.
reproduce in both Gmail and Expensifail accounts.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7292854_1792646303847.103927W.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Rizky Gunawan
Bug ID: 7292854

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 22, 2026
  2. applause-bot commented on Oct 22, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/8b7dc04ff07a4ece9b8632dd94256b3d225918cc4ff0502525e4f1f375e3c81e

  3. melvin-bot commented on Oct 22, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #103927

  4. melvin-bot commented on Oct 22, 2026

    @melvin-bot

    @francoisl @yuwenmemon you have been assigned to this deploy blocker because you reviewed the offending PR: #103927

  5. github-actions commented on Oct 22, 2026

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. melvin-bot commented on Oct 22, 2026

    @melvin-bot

    @akinwale you have been assigned to this deploy blocker because you authored the offending PR: #103927

  7. melvin-bot commented on Oct 22, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  8. MelvinBot commented on Oct 22, 2026

    @MelvinBot
    Contributor

    Deploy Blocker Analysis

    Recommendation: Demote, don't revert. Add NetSuite OAuth migration nudges is most likely working as designed. During review, the PR was changed to show the nudge only for workspaces with a simple NetSuite sync configuration. The QA steps were never updated to include that precondition, so a typical SOAP TBA test connection correctly shows nothing.

    Next step: Ask QA to retest with a NetSuite TBA connection where all of these are true:

    • Tax import, reimbursed-report sync, custom segments, and custom lists are all off.
    • No other admin workspace on the same NetSuite account has any of those on.

    If the nudge appears, close this issue. If it still doesn't appear, check whether the tester's policy data includes connections.netsuite.tokenSecret and options.config.syncOptions. If either is missing, the cause is a backend data dependency, not this App PR.

    Confidence: medium. I couldn't inspect the tester's account data.

    Investigation details

    Both the Home time-sensitive item and the Accounting notice use shouldShowNetSuiteOAuthMigrationNudge (utils.ts:114-142). It returns true only when all of these hold:

    1. NetSuite is connected, not verified === false, and authType isn't oauth2.
    2. accountID, tokenID, and tokenSecret are all set.
    3. hasSimpleNetSuiteSyncConfiguration is true (utils.ts:101-112). syncOptions must exist, and syncTax, syncReimbursedReports, syncCustomSegments, and syncCustomLists must be off, with no custom segments or lists.
    4. No other non-archived admin workspace on the same NetSuite accountID has a non-simple configuration (utils.ts:129-141).

    Conditions 3 and 4 came from review commits 0e35c05a ("limit OAuth migration nudges") and 10198c89 ("account for shared connections"). The PR's Tests and QA steps still list only "connected to NetSuite over SOAP TBA" as the prerequisite.

    Other checks:

    • Home item: also needs the admin role and a workspace that isn't archived or pending delete (useTimeSensitiveNetSuiteMigration.ts).
    • Accounting notice: also needs canWriteAccounting. A QuickBooks Online expiry hint takes priority if present (PolicyAccountingPage.tsx).
    • There is no beta gate. The deadline severity only changes the wording.

    Why not revert: This is a new feature that isn't in production yet. The PR adds a nudge and changes no existing behavior.

    Follow-up for the PR author: Add the simple-configuration precondition to the PR's QA steps.


    Next Steps: Reply with @MelvinBot <your feedback> to refine this analysis.


    view run

  9. yuwenmemon commented on Oct 22, 2026

    @yuwenmemon
    Contributor

    @akinwale I would imagine we should still show the upgrade option, even if we're not showing the banner.

  10. melvin-bot commented on Oct 23, 2026

    @melvin-bot

    @francoisl / @yuwenmemon @akinwale

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.18-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  11. melvin-bot commented on Oct 26, 2026

    @melvin-bot

    @francoisl, @akinwale, @yuwenmemon Whoops! This issue is 2 days overdue. Let's get this updated quick!

  12. francoisl commented on Oct 26, 2026

    @francoisl
    Contributor

    PR #104777 is on production. I believe there's no one-off payments due for this issue, but let me know if I'm wrong!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions