Odoo Changelog — 2024-02-12

Monday, February 12, 2024

2 changes · master

New Features(2)

New functionality added to Odoo

[ADD] VAT functionality added in General Ledger report

Enterprisemasterl10n_de_reportsMedium

The German DATEV export from the General Ledger now includes a VAT column for invoice-related entries. This helps accounting teams export more complete audit data, using the VAT number from the invoice address or its parent company when needed.

Original PR description

Before this commit, If "DATEV" was exported from the general ledger of the audit report.
There is no VAT column present on the EXTF_accounting_entries.csv report.

As a result, we added a VAT field to the invoice, and it's value is propagated from the VAT field defined on the invoice address.
If the VAT number is not present on the invoice address, the commercial entity of the invoice address is used.
We added the VAT column to the DATEV report of General Ledger.

Steps to reproduce:
1. Assign the VAT number on the invoice address or it's parent customer.
2. Create an invoice for the customer, and the VAT is automatically propagated.
3. Accountancy—>Audit report—>General Ledger—> Export the DATEV report by clicking the "DATEV" button.
4. Based on the invoice, VAT is added to the EXTF accounting entries.csv report.

#VAT#DATEV#General Ledger#audit report

[IMP] knowledge: add article finder

PR #44257

EnterprisemasterknowledgeHigh impact

Knowledge now includes a stronger search experience that can find articles based on their content, not just their titles. This helps users quickly locate relevant information across large documentation collections and reduces time spent browsing manually.

Original PR description

Knowledge is a wonderful tool for gathering, organizing and sharing documentation with colleagues. With this module, people can easily create rich documents that help them in their day-to-day jobs.

Currently, Knowledge lacks an effective search feature. The existing search functionality only searches documents based on their titles and cannot search within the document content.

This PR will implement a new search feature for Knowledge that will enable people to quickly find the information they need within a large collection of documents. This new feature will save a significant amount of time for users who are unsure which specific document contains the information they need.

The search feature will work like a small search engine: People will have to type a few words or a sentence and the system will retrieve the documents that match the most with those keywords.

To implement that search feature, we will use the build-in "Full Text Search" feature of PostgreSQL. By leveraging this feature, the database will do all the heavy lifting for us: It will be able to automatically encode the documents in a vector space, apply stemming on the words, include statistical measures to evaluate the similarity between a document and a query, strip the html tags, highlight the piece of text containing the search terms, etc.

Reference: https://www.postgresql.org/docs/15/textsearch.html

task-3071299

Before this commit, If "DATEV" was exported from the general ledger of the audit report. There is no VAT column present on the EXTF_accounting_entries.csv report. As a result, we added a VAT field to the invoice, and it's value is propagated from the VAT field defined on the invoice address. If the VAT number is not present on the invoice address, the commercial entity of the invoice address is used. We added the VAT column to the DATEV report of General Ledger. Steps to reproduce: 1. Assign the VAT number on the invoice address or it's parent customer. 2. Create an invoice for the customer, and the VAT is automatically propagated. 3. Accountancy—>Audit report—>General Ledger—> Export the DATEV report by clicking the "DATEV" button. 4. Based on the invoice, VAT is added to the EXTF accounting entries.csv report.

Knowledge is a wonderful tool for gathering, organizing and sharing documentation with colleagues. With this module, people can easily create rich documents that help them in their day-to-day jobs. Currently, Knowledge lacks an effective search feature. The existing search functionality only searches documents based on their titles and cannot search within the document content. This PR will implement a new search feature for Knowledge that will enable people to quickly find the information they need within a large collection of documents. This new feature will save a significant amount of time for users who are unsure which specific document contains the information they need. The search feature will work like a small search engine: People will have to type a few words or a sentence and the system will retrieve the documents that match the most with those keywords. To implement that search feature, we will use the build-in "Full Text Search" feature of PostgreSQL. By leveraging this feature, the database will do all the heavy lifting for us: It will be able to automatically encode the documents in a vector space, apply stemming on the words, include statistical measures to evaluate the similarity between a document and a query, strip the html tags, highlight the piece of text containing the search terms, etc. Reference: https://www.postgresql.org/docs/15/textsearch.html task-3071299