Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Having 2x CSV export methods (JS-based and server-based) adds complexity with little/no benefit to merchants #9764

Open
Jinksi opened this issue Nov 20, 2024 · 1 comment
Labels
component: reporting Issues related to Reporting focus: reporting type: enhancement The issue is a request for an enhancement.

Comments

@Jinksi
Copy link
Member

Jinksi commented Nov 20, 2024

We currently have 2x implementations for generating CSV exports for reporting views, e.g. Transactions list, Payouts list, etc.

  • front-end JS-based CSVs are exported for small row counts (<25-100)
  • async service-generated for larger CSVs that are emailed to the accountholder

We should simplify this to reduce complexity, maintenance footprint and merchant with the goal of improving the quality of the CSV export experience for our merchants.

@Jinksi Jinksi added the component: reporting Issues related to Reporting label Nov 20, 2024
@Jinksi Jinksi changed the title WooPayments has client and server CSV exports which add complexity with little/no benefit to merchants Having 2x CSV export methods (JS-based and server-based) adds complexity with little/no benefit to merchants Nov 20, 2024
@Jinksi Jinksi added the type: enhancement The issue is a request for an enhancement. label Nov 20, 2024
@haszari
Copy link
Contributor

haszari commented Nov 20, 2024

@Jinksi What's the outcome of this issue – a spike or a proposal for what we could change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: reporting Issues related to Reporting focus: reporting type: enhancement The issue is a request for an enhancement.
Projects
None yet
Development

No branches or pull requests

3 participants