NetSuite - Previous steps when returning from confirm page do not show the correct data

[mitarachim]

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.3.33-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #80995
Email or phone of affected tester (no customers): sdosidjiosdjnojsio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Workspace is connected to NetSuite.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Accounting.
3. Click Import > Custom lists.
4. Click Add custom list.
5. Select any option and reach the confirm page.
6. On confirm page, edit each field.
7. After editing the fields, click RHP back button on confirm page until it returns to the first step.

Expected Result:

When returning to previous page via back button, each section will show the newly selected option from Step 6.

Actual Result:

When returning to previous page via back button, each section shows the previously selected option.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7096065_1772840209463.1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @dukenv0307

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @greg-schroeder (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

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