Skip to content

Report - INVALID part does not fall back to 0.00 in the report title #76770

Closed

Description

@vincdargento

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.2.72-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #71233
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: MacBook Air 15.6.1 Chrome, iPhone 15 iOS 26.1
App Component: Money Requests

Action Performed:

Preconditions: use Expensifail account or enable beta on gmail account using steps from the PR (see below)

  1. Navigate to Workspace where you are an admin and the default currency is USD
  2. In Reports section set the formula to "{report:total:jpy} | {report:total:nosymbol} | {report:total:INVALID}" (if using E account, need to enable "Prevent members from changing custom report titles" for the formula to work)
  3. Create a new report via FAB
  4. Add transactions totaling $150.50 USD
  5. Verify the report title

Expected Result:

The report title meets the requirement:

  • INVALID part falls back to 0.00

Actual Result:

INVALID part of the report title shows formula {report:total:INVALID}

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 4, 2025
  2. melvin-bot commented on Dec 4, 2025

    @melvin-bot

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

  3. kadiealexander commented on Dec 9, 2025

    @kadiealexander
    Contributor

    @JmillsExpensify @arosiclair tagging you here because you're on the linked PR. This doesn't seem like a bug to me, I would expect that if someone mistyped a report title field then we'd print what they typed, not change their report title field on their behalf to something acceptable. Do I have that right?

  4. JmillsExpensify commented on Dec 9, 2025

    @JmillsExpensify
    Contributor

    This feels more like something that is occurring as a result of the report titles project roll-out.

  5. JmillsExpensify commented on Dec 9, 2025

    @JmillsExpensify
    Contributor

    As for your question, I would just ignore anything in the report title formulas that isn't correct.

  6. arosiclair commented on Dec 9, 2025

    @arosiclair
    Contributor

    This doesn't seem like a bug to me, I would expect that if someone mistyped a report title field then we'd print what they typed, not change their report title field on their behalf to something acceptable. Do I have that right?

    Yeah that's exactly right - this isn't a bug. @vincdargento see this announcement: https://expensify.slack.com/archives/C9YU7BX5M/p1756996987310489

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions