Exports to CSV only visible records instead of complete set

Bug #479157 reported by R. Messier
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Odoo GTK Client (MOVED TO GITHUB)
Fix Released
Undecided
Unassigned
Odoo Web Client
Fix Released
Undecided
Unassigned

Bug Description

When more than 80 records are presented at the same time in a list (tree) view, the records are split across multiple pages of 80 records. This behaviour seems to be carried in the "Export to CSV" function which break the record set into pages of 80 records. I feel that the export function should export the whole record set at the same time to avoid having to export and merge multiple CSV files (quite tedious for large record sets).

Revision history for this message
Christophe CHAUVET (christophe-chauvet) wrote :

I confirm this issue

Regards,

affects: openobject-doc → openobject-client
Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello guys,

Its not a bug at all.

It simply says that you are exporting the records you are able to watch or the records which are listed.

If you want all the records, you may simply change the limit(total no. of records are seen at the bottom).

If we make it to export all the records,it will be unwell for whom who want specific no. of records/filtered records to be exported.

You may go for a blueprint in this context.

May be, we can set an option (ALL or listed).
Thank you.

Changed in openobject-client:
status: New → Invalid
Revision history for this message
R. Messier (raphaelmessier) wrote :

I never expected this function to export ALL records in the model being viewed. Only those after all filters are applied, even if they span on multiple pages, all at the same time instead of one page at a time.

Revision history for this message
Christophe CHAUVET (christophe-chauvet) wrote :

Hi Jay

Yes we can change the limit, but only on the GTK client, on the web client it's not possible to change it.

After debug this, why cannot execute a search with the same criteria as the current list before export to CSV ?

Regards,

Changed in openobject-client:
status: Invalid → New
Changed in openobject-client-web:
status: New → Confirmed
Changed in openobject-client:
milestone: none → 5.0.7
Changed in openobject-client-web:
milestone: none → 5.0.7
Changed in openobject-client:
status: New → Confirmed
Changed in openobject-client-web:
assignee: nobody → gpa(Open ERP) (gpa-openerp)
Revision history for this message
Stephane Wirtel (OpenERP) (stephane-openerp) wrote :

Who can fix this bug in the GTK Client ?

Thanks

Changed in openobject-client:
assignee: nobody → gpa(Open ERP) (gpa-openerp)
Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Guys,

Here is one of the ways we can meet to this facility. It uses 2 RPC calls.

Thanks.

Changed in openobject-client:
status: Confirmed → In Progress
Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Another way, reducing one RPC call with modifications on server.
2 Back to back patches.

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Patch for server modification with 1 RPC call.

Changed in openobject-client:
milestone: 5.0.7 → 5.0.8
Changed in openobject-client-web:
milestone: 5.0.7 → 5.0.8
Revision history for this message
Ferdinand (office-chricar) wrote :

Obviously users have various needs
* export all matching records (regardless of limit)
* export all selected records
* mostly never - export only visible (20/80 depending on client) records - IMHO this is sort of not user friendly behaviour because users usually do not know which records are visible and whcih not.

Revision history for this message
Sananaz (Open ERP) (sma-tiny) wrote :

Hello,

I have attached the patch for web-client, which solved problem of export only visible rows.
So kindly apply the patch and notify us.

Thanks.

Changed in openobject-client-web:
importance: Undecided → Medium
Changed in openobject-client:
importance: Undecided → Medium
Revision history for this message
Stephane Wirtel (OpenERP) (stephane-openerp) wrote :

I prefer to assign this bug to the next milestone (5.0.9) because we have not checked the fix and the release of 5.0.8 will be this week. I prefer to avoid a regression in the client.

Stephane

Changed in openobject-client-web:
status: Confirmed → In Progress
Changed in openobject-client:
milestone: 5.0.8 → 5.0.9
Changed in openobject-client-web:
milestone: 5.0.8 → 5.0.9
Changed in openobject-client-web:
milestone: 5.0.9 → 5.0.10
Changed in openobject-client:
milestone: 5.0.9 → 5.0.10
Changed in openobject-client:
milestone: 5.0.10 → 5.0.11
Changed in openobject-client-web:
milestone: 5.0.10 → 5.0.11
Changed in openobject-client:
milestone: 5.0.11 → 5.0.12
Changed in openobject-client-web:
milestone: 5.0.11 → 5.0.12
Revision history for this message
Navrang Oza (noz-tiny) wrote :

Hello,

I think we should close this bug because there is no result after our given patch.
We already provided server and web client patch but no action after that.
So no need to continue for next milestone.

Thanks.

Changed in openobject-client:
assignee: gpa(Open ERP) (gpa-openerp) → nobody
importance: Medium → Undecided
milestone: 5.0.12 → none
status: In Progress → Fix Released
Changed in openobject-client-web:
assignee: gpa(Open ERP) (gpa-openerp) → nobody
importance: Medium → Undecided
milestone: 5.0.12 → none
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.