Netsuite/Intacct/Xero - Page not found when click Back error on Export tab

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.0.87-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/cases/view/3073348
Issue reported by: Applause - Internal Team
Component: Workspace Settings

Action Performed:

Precondition: workspace with connected Netsuite integration.

1. Go to Accounting > Netsuite
2. Click on Export
3. Click back arrow

Expected Result:

Accounting page opened

Actual Result:

Hmm... it's not here
Oops, this page cannot be found
(Netsuite/Intacct/Xero)

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6716836_1737130190584.bandicam_2025-01-17_18-08-37-417.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @dangrous (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

[github-actions]

👋 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.

[dangrous]

caused by #55209 - seeing if we can get a quick fix going.

[dangrous]

It's not handling the case where there's no backTo.

So if we don't want to go back to (ha) getUrlWithBackToParam, we need something like

`export${backTo ? `?backTo=${backTo}` : ''}`

instead of

`export?backTo=${backTo}`

which looks gross but would work. Basically if we have backTo with an empty string it causes this error. So we... shouldn't do that.

[mountiny]

Cc @narefyev91 @dukenv0307 can you have a look please