[Better Expense Report View] Expense Reports - Merchant is still displayed in the row after merchant is removed

[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.1.16-1
Reproducible in staging?: N
Reproducible in production?:
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #58360
Email or phone of affected tester (no customers): applausetester+kok1@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• Log in with Expensifail account

1. Go to staging.new.expensify.com
2. Open FAB > Submit expense > Manual
3. Submit a manual expense with merchant to any user
4. Go to transaction thread
5. Click Merchant
6. Clear the merchant and save it
7. Go to Reports
8. Go to Expense Reports
9. Click on the expense report from Step 3

Expected Result:

Merchant field will no longer show the previous merchant because it is removed

Actual Result:

Merchant field still shows the previous merchant after it is removed
This issue also happens when the merchant is changed from A to B. The expense row will show merchant A instead of merchant B
This issue also happens with Amount field

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

Bug6777287_1742499648586.20250321_033635.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @Kicu

[melvin-bot]

Triggered auto assignment to @cead22 (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.

[luacmartins]

This view is behind a beta. NAB. @Kicu