Repository navigation
Conversation
Copied as is from Odoo 17.0 branch. Later commits will do the needed changes.
Currently translated at 100.0% (27 of 27 strings) Translation: spreadsheet-18.0/spreadsheet-18.0-spreadsheet_dashboard_purchase_oca Translate-URL: https://translation.odoo-community.org/projects/spreadsheet-18-0/spreadsheet-18-0-spreadsheet_dashboard_purchase_oca/it/
Currently translated at 100.0% (27 of 27 strings) Translation: spreadsheet-18.0/spreadsheet-18.0-spreadsheet_dashboard_purchase_oca Translate-URL: https://translation.odoo-community.org/projects/spreadsheet-18-0/spreadsheet-18-0-spreadsheet_dashboard_purchase_oca/fr/
Currently translated at 100.0% (31 of 31 strings) Translation: spreadsheet-19.0/spreadsheet-19.0-spreadsheet_dashboard_purchase_oca Translate-URL: https://translation.odoo-community.org/projects/spreadsheet-19-0/spreadsheet-19-0-spreadsheet_dashboard_purchase_oca/it/
Signed-off-by: Don Kendall <dkendall@ledoweb.com> Assisted-by: Claude Code
* data/dashboards.xml: payload loads with type="bytes", not type="base64". * vendors_dashboard.json: Dashboard sheet backgroundColor #F9FAFB, as core. * vendors_dashboard.json: adopt the 20.0 dashboard styling — white KPI cards and a card around each section's title and content, on the original layout. Signed-off-by: Don Kendall <dkendall@ledoweb.com> Assisted-by: Claude Opus 5
…y filters Wires both filters to the pivots, the list and the chart. purchase.report carries product_id and category_id; purchase.order reaches them through order_line. Assisted-by: Claude Opus 5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Built on the merged 20.0 (OCA#133 landed at
6d1d7bb), so this is a clean follow-up rather than a stacked branch. Proposed for upstream; 78 insertions, 0 deletions, no layout change.Takes one of @pedrobaeza's suggestions from the enterprise comparison: EE's Purchase & Vendor analysis carries Product and Product Category filters.
purchase.reportexposesproduct_idandcategory_idin community;purchase.orderreaches them throughorder_line.Verified on a clean 20.0 with demo data: filtering Product Category to Services drops every KPI to $0/0 and empties the tables, while the chart falls to the single Services purchase — a negative control, not just "the filter appears".
Deliberately excluded: the Avg order value KPI
It cannot be added without re-laying out the KPI row, which is exactly what @pilarvargas-tecnativa objected to on OCA#133. Measured on the merged payload: the row already ends at x=1045 of a 1047px canvas, and only 61px separate it from the chart card — too little for a second row of 108px. A sixth card therefore means either resizing all five or pushing the whole page down. That is a design decision for the maintainers, not something to slip into an IMP.
AI-assisted (Claude Code); every change reviewed, tested, and owned by the author.