Categories - GL code comes back after clearing the field and reopening the category editor

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

issue found when validating #43155
Version Number: 9.0.7-3
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:

Action Performed:

Precondition:

• Workspace is under Control plan.

1. Go to staging.new.expensify.com
2. Go to Control workspace settings > Categories.
3. Click on any category.
4. Click GL code.
5. Enter a GL code and save.
6. Click GL code again.
7. Clear the GL code and save.
8. Close the RHP.
9. Click on the same category again.

Expected Result:

The GL code field will remain cleared.

Actual Result:

The GL code field is populated with old value and is not cleared.

Workaround:

unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6543254_1721080709801.20240716_055555.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

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

[dylanexpensify]

cc @rushatgabhane @Gonals

[Gonals]

Not a blocker, as it doesn't break existing functionality. This is getting fixed here

[dylanexpensify]

Perfecto!

[dylanexpensify]

fix ongoing

[dylanexpensify]

@Gonals is this still occurring?

[Gonals]

Nope!