Skip to content

[Payment due @abdulrahuman5196] Send the view's expense columns when exporting a grouped current view - #98291

Merged
deetergp merged 9 commits into
mainfrom
rodrigo-grouped-export-columns
Aug 14, 2026
Merged

[Payment due @abdulrahuman5196] Send the view's expense columns when exporting a grouped current view#98291
deetergp merged 9 commits into
mainfrom
rodrigo-grouped-export-columns

Conversation

@rlinoz

@rlinoz rlinoz commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

On a grouped Search — the Bank Reconciliation view, or any groupBy: search — "Export current view" produced a CSV whose expense rows carried a fixed eight columns rather than the columns configured in the view, so adding From or Tag to the view did not add them to the export.

This PR sends the necessary info so Auth exports

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/669002
$ https://github.com/Expensify/Expensify/issues/668120
$ https://github.com/Expensify/Expensify/issues/652978
PROPOSAL: N/A — internal

Tests

Export basic export expense/reports

  1. Go to the spend page > select a few expenses > X selected > export > basic export
  2. Verify it has all the basic export columns
634266265-ccb84ca2-95be-49c6-b1a3-518bb50274cf
  1. Go to the spend page > reports > select a few reports > X selected > export > basic export
  2. Verify it has all the basic export columns
634266626-8ae610e3-2ab4-4714-a110-250621626289

Export current view expense/reports

  1. In the spend page > Display > Add a few more columns
  2. Select a few expenses > X selected > export > current view
  3. Verify it has all the selected columns
634267729-5e38681d-1e98-446f-b1c1-daf59a5934ed
  1. In the spend page > reports > Display > Add a few more columns
  2. Select a few reports> X selected > export > current view
  3. Verify it has all the selected columns
634268387-942dec72-e46b-4b23-a106-a4789fe6645a

Export current view grouped expenses

  1. In the spend page > cash accruals > Display > Add a few more columns
  2. Select a few accounts > X selected > export > current view
  3. Verify it has the summary and all the selected columns
634270516-eb5d0bca-c094-4b20-bf53-c52ff4e7b667
  • Verify that no errors appear in the JS console

Offline tests

An export is a network request and is unchanged here — only the parameters it carries differ. Offline, choosing "Current view" behaves exactly as it does on main.

QA Steps

Export basic export expense/reports

  1. Go to the spend page > select a few expenses > X selected > export > basic export

  2. Verify it has all the basic export columns

  3. Go to the spend page > reports > select a few reports > X selected > export > basic export

  4. Verify it has all the basic export columns

Export current view expense/reports

  1. In the spend page > Display > Add a few more columns

  2. Select a few expenses > X selected > export > current view

  3. Verify it has all the selected columns

  4. In the spend page > reports > Display > Add a few more columns

  5. Select a few reports> X selected > export > current view

  6. Verify it has all the selected columns

Export current view grouped expenses

  1. In the spend page > cash accruals > Display > Add a few more columns
  2. Select a few accounts > X selected > export > current view
  3. Verify it has the summary and all the selected columns

Same as tests, steps 3 onward, on staging once the Auth and Web-Expensify changes are deployed.

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

N/A — telemetry configuration change with no UI.

Android: mWeb Chrome

N/A — telemetry configuration change with no UI.

iOS: Native

N/A — telemetry configuration change with no UI.

iOS: mWeb Safari

N/A — telemetry configuration change with no UI.

MacOS: Chrome / Safari

N/A — telemetry configuration change with no UI.

@rlinoz
rlinoz marked this pull request as ready for review August 12, 2026 20:41
@rlinoz
rlinoz requested review from a team as code owners August 12, 2026 20:41
@melvin-bot
melvin-bot Bot requested review from abdulrahuman5196 and removed request for a team August 12, 2026 20:41
@melvin-bot

melvin-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

@abdulrahuman5196 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot requested review from trjExpensify and removed request for a team August 12, 2026 20:41
@quinthar quinthar removed the #migrate label Aug 13, 2026
@rlinoz

rlinoz commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

hey @abdulrahuman5196 please review this one when you have a chance.

trjExpensify
trjExpensify previously approved these changes Aug 13, 2026

@trjExpensify trjExpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lovely, thanks for jumping on this. 👍

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

Hi, Will check on this.

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

Checking now

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

@codex review

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

@rlinoz I am getting 404 for the images attached in the authors list?

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 03e05a00cd

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/hooks/useSearchBulkActions.ts
@rlinoz

rlinoz commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

I am getting 404 for the images attached in the authors list?

can you try again please

@abdulrahuman5196

abdulrahuman5196 commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

I am getting 404 for the images attached in the authors list?

can you try again please

Works now, thanks.

@rlinoz
The code looks fine IMO, I checked in web and i am able to see the new columns getting adding the response.

But I am not seeing rows of "First Approved", "First Approver" columns coming up in the csv, i assume that would be a backend fix?

Also kindly respond to this as well - #98291 (comment)

@rlinoz

rlinoz commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

But I am not seeing rows of "First Approved", "First Approver" columns coming up in the csv, i assume that would be a backend fix?

yes, some columns are not being processed in the backend, that will be a separate issue/pr.

@rlinoz

rlinoz commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

@abdulrahuman5196 this should be ready for you to finish the review/checklis 😄

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

Oh got it. Will close out in couple of hours

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

expensify_basic_export_91019944305973742.csv
expensify_basic_export_2445097254055797733.csv
expensify_current_view_132619113550437920.csv
expensify_current_view_488368789407659307.csv
expensify_current_view_9047206646080020437.csv

@abdulrahuman5196 abdulrahuman5196 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes looks good and works well. Reviewers checklist is also complete.

All yours.

🎀 👀 🎀
C+ Reviewed

@melvin-bot
melvin-bot Bot requested a review from deetergp August 14, 2026 16:03
@melvin-bot

melvin-bot Bot commented Aug 14, 2026

Copy link
Copy Markdown

@deetergp Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot changed the title Send the view's expense columns when exporting a grouped current view [Payment due @abdulrahuman5196] Send the view's expense columns when exporting a grouped current view Aug 14, 2026
@melvin-bot

melvin-bot Bot commented Aug 14, 2026

Copy link
Copy Markdown

🎯 @abdulrahuman5196, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/669002.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

@deetergp
deetergp merged commit 53c7448 into main Aug 14, 2026
45 of 47 checks passed
@deetergp
deetergp deleted the rodrigo-grouped-export-columns branch August 14, 2026 21:17
@github-actions

Copy link
Copy Markdown
Contributor

🚧 deetergp has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants