Rules - Vendor name changes after disconnecting accounting

[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.4.53-4
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod - Provide reasoning.
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #97811
Email or phone of affected tester (no customers): applausetester+ssndjois2jd1@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Enable Accounting and Rules.
• Connect workspace to Sage Intacct.
• Run Onyx.merge('betas', ['vendorMatching']); in console.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Rules.
3. Click Add merchant rule.
4. Click Merchant.
5. Enter merchant and save it.
6. Click Vendor.
7. Select a vendor.
8. Create the rule.
9. Go to Accounting and disconnect Sage Intacct.
10. Go to Rules.
11. Scroll down to the created rule.

Expected Result:

Vendor name will not change after disconnecting accounting.

Actual Result:

Vendor name changes after disconnecting accounting.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7232764_1786633390889.16.1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7232764

[applause-bot]

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

[melvin-bot]

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

[melvin-bot]

@mollfpr @abzokhattab you have been assigned to this deploy blocker because you reviewed the offending PR: #97811

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

[abzokhattab]

is that a backend issue @Beamanator