Skip to content

Accounting - Non-reimbursable expense becomes empty after going offline and online #45191

Closed

Description

@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.6-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Issue found when executing PR #44921

Action Performed:

Pre-requisite

  • Collect workspace with accounting enabled.
  • NetSuite beta enabled for the user. (Use expensifail account)
  • Setup NetSuite in OldDot.
  1. Open the app with the pre-setup workspace.
  2. Go to Accounting
  3. Click on the Advanced button.
  4. Click on Non-reimbursable expense option (Enable Custom form ID to access this field)
  5. Input any number and confirm
  6. Wait a few seconds and go offline
  7. Go back online again

Expected Result:

The value in Non-reimbursable expense persists

Actual Result:

The value in Non-reimbursable expense becomes empty

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

Add any screenshot/video evidence

Bug6538055_1720626623688.bandicam_2024-07-10_18-45-35-410.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jul 10, 2024
  2. melvin-bot commented on Jul 10, 2024

    @melvin-bot

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

  3. github-actions commented on Jul 10, 2024

    @github-actions
    Contributor

    👋 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.
  4. lanitochka17 commented on Jul 10, 2024

    @lanitochka17
    Author

    @Gonals FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

  5. Gonals commented on Jul 10, 2024

    @Gonals
    Contributor

    Hmm. This looks like a backend issue, at first glance. Can it be reproduced consistently?

  6. added
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jul 10, 2024
  7. melvin-bot commented on Jul 10, 2024

    @melvin-bot

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

  8. Gonals commented on Jul 10, 2024

    @Gonals
    Contributor

    Ok, that field is not working at all. It is not a blocker, as this is new functionality and doesn't break any existing stuff, but we need to fix it. I'll look more into it today/tomorrow

  9. added
    ImprovementItem broken or needs improvement.
    InternalRequires API changes or must be handled by Expensify staff
    on Jul 10, 2024
  10. Gonals commented on Jul 10, 2024

    @Gonals
    Contributor

    Yeeep. This is a typo in the backend. Fix incoming

  11. Christinadobrzyn commented on Jul 11, 2024

    @Christinadobrzyn
    Contributor

    I assume we can move this from hourly to daily now that a PR is in the works. @Gonals does that sound okay?

  12. Gonals commented on Jul 11, 2024

    @Gonals
    Contributor

    Yep!

  13. Christinadobrzyn commented on Jul 15, 2024

    @Christinadobrzyn
    Contributor
  14. Christinadobrzyn commented on Jul 16, 2024

    @Christinadobrzyn
    Contributor

    I think I'm going to move this to weekly since we're working on PR - https://github.com/Expensify/Web-Expensify/pull/42707

  15. Christinadobrzyn commented on Jul 23, 2024

    @Christinadobrzyn
    Contributor

    PR is in production - https://github.com/Expensify/Web-Expensify/pull/42707 as of the 16th. Can we close this out @Gonals and @lakchote?

  16. Christinadobrzyn commented on Jul 30, 2024

    @Christinadobrzyn
    Contributor

    I'm going to close this out. We can reopen if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringImprovementItem broken or needs improvement.InternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions