Message Threads | The Odoo Community Association

Re: Regular postgres VACUUM command

> can anyone recommend a visual Postgres monitoring tool

I use pgbadger too but PGHero is my favorite tool to see real time stats

El vie, 28 jul 2023 a las 3:22, Tom Blauwendraat (<notifications@odoo-community.org>) escribió:

Thanks Moises and Graeme for the detailed information!

I'm going to look at tweaking autovacuum and statistics settings for the 
busy tables. Also, whenever replacing a big chunk of data, I'll run 
ANALYSE <table> afterwards.

As for most situations the default Postgres settings are fine, and I 
can't think of any "generic" solutions other than monitoring and doing 
individual tweaks, I won't create an OCA module for it.

Parting question: can anyone recommend a visual Postgres monitoring tool 
that could ideally also work on Amazon RDS? I'm familiar with log 
parsing tools such as pgBadger, but maybe there's a tool out there 
somewhere that can give information just by connecting to the instance 
and running smart queries?

-Tom

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

Moisés López Calderón

Mobile: (+521) 477-752-22-30

Twitter: @moylop260

hangout: moylop260@vauxoo.com
http://www.vauxoo.com - Odoo Gold Partner

Twitter: @vauxoo

by Moisés López Calderón - 12:26 - 2 Aug 2023

Re: pricelist issue

base_user_company_role

On Mon, Jul 31, 2023 at 9:46 PM samir mahmoud <notifications@odoo-community.org> wrote:

I have a situation in a multi company environment where I want one of my user to have access to both of my companies A & B.

Moreover, this user must have access to the accounting of company A but not B.

Is it possible in Odoo to define application access rights per company ?

How can I achieve this ? By using record rules ? If so, how ?

Sent from Mail for Windows

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Graeme Gellatly - 02:00 - 31 Jul 2023

pricelist issue

I have a situation in a multi company environment where I want one of my user to have access to both of my companies A & B.

Moreover, this user must have access to the accounting of company A but not B.

Is it possible in Odoo to define application access rights per company ?

How can I achieve this ? By using record rules ? If so, how ?

Sent from Mail for Windows

by "samir mahmoud" <samir2010ksa@hotmail.com> - 11:46 - 31 Jul 2023

Re: Overtime calculation in Odoo 15 and OCA

In case you're interested I have a solution for OT calculation, payroll, etc for 14.0 here: https://github.com/trevi-software/trevi-hr. I'm currently porting it to 16.0, but it should give you a good place to start for 15.0.

Regards,

Mike.

On 28/07/2023 17:21, Janik von Rotz wrote:

Hi Florian

I think I resolved some issues with custom modules and actions. I assume you speak/read German.

Regarding hr_holidays_public have look at https://www.odoo-wiki.org/best-practice-working-times-and-holiday-allocations.html

Regarding hr_attendance_report_theoretical_time we have this alternative https://www.odoo-wiki.org/hr-employee-attendance-report.html

Regarding "Overtime ignores dates without attendance completly despite it's an actual working day." we created this: https://www.odoo-wiki.org/hr-attendance-actions.html#fehlende-anwesenheitseintrage-anzeigen

Cheers, Janik

On 7/28/23 13:51, Florian Kantelberg wrote:
Hello community,

we are currently looking on overtime calculation in Odoo 15.0. Odoo 15.0 introduced a new model (hr.attendance.overtime) and mechanisms for an overtime calculation. First I want to share our knowledge with digging into it. There are currently some core bugs with the overtime calculation:

The resource.calendar from hr.contract is not used for overtime calculation as you would expect if hr_attendance and hr_contract is installed. Causes wrong calculations if you edit attendance before a resource calendar (e.g. somebody forgot to logout and you are validating the attendance)

Overtime ignores dates without attendance completly despite it's an actual working day. E.g. if you have to work for 8h and login for 1min you have -7:59h overtime. If you don't login it's +/-0h. This isn't fully consistent.

We are currently trying to develop fixes for these core bugs. The bugs are present from 15.0 to master. We can share the PRs when they are ready.

Following are additional observations regarding the state of the OCA modules in regard to overtime and attendance:

hr_attendance_sheet and hr_attendance_validation: (up to 14.0)

There is a big intersection in the feature sets of both modules. Both are creating a kind of sheet and a multiple step process to verify/approve attendances. They also add features like overtime calculation etc. based on the sheets.

A simple migration PR[1] is maybe not worth it because of the core changes in the overtime calculation. E.g. if an approval process is needed shouldn't only approved attendances count towards your overtime?

hr_holidays_public: (already 15.0)

This module works fine especially the automatic holiday generation with the modules built on top. The module has problems in the overtime calculation. The holidays reduce the days when you request additional holidays. But such a holiday is getting ignored for the overtime calculation. E.g. if you work on a holiday for 9h instead of the regular 8h you get 1h overtime with OCA holiday but 9h for core holiday. It's also not possible to use half holidays (e.g. the 24.12. or 31.12. in Germany). The module also ignores the holidays of the Odoo core. Are there any reasons to stick to the extra model we are not seeing?

In 15.0 Odoo core has a own model for public holidays. So just going on we community solution might result in a growing divergence from the core. The feature to generate public holidays is still very comfortable. A new approach could be to rebuild this to create entries of Odoo core model.

hr_attendance_report_theoretical_time

Here a intersection to the Odoo core overtime calculation in Odoo 15.0 exists, since it comes with some reports (pivot tables).

Is currently somebody else working on it and can share information or experience with overtime in Odoo 15.0 onwards?

Best Regards,

Florian

[1] https://github.com/OCA/hr-attendance/pull/114
-- 
Mit freundlichen Grüßen

Florian Kantelberg
Softwareentwickler

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel.: +49 (0) 4181 1350344
Fax: +49 (0) 4181 1350310

Email: florian.kantelberg@initos.com
Internet: https://www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht: Tostedt, HRB 205226
USt-IdNr: DE 815580155
Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Raphael Makonnen - 02:31 - 30 Jul 2023

Tier partial invoicing

Dear all

We have a case where product

--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.com
www.invitu.com

by Cyril VINH-TUNG - 11:41 - 28 Jul 2023

Re: Overtime calculation in Odoo 15 and OCA

Hi Florian

I think I resolved some issues with custom modules and actions. I assume you speak/read German.

Regarding hr_holidays_public have look at https://www.odoo-wiki.org/best-practice-working-times-and-holiday-allocations.html

Regarding hr_attendance_report_theoretical_time we have this alternative https://www.odoo-wiki.org/hr-employee-attendance-report.html

Regarding "Overtime ignores dates without attendance completly despite it's an actual working day." we created this: https://www.odoo-wiki.org/hr-attendance-actions.html#fehlende-anwesenheitseintrage-anzeigen

Cheers, Janik

On 7/28/23 13:51, Florian Kantelberg wrote:

Hello community,

we are currently looking on overtime calculation in Odoo 15.0. Odoo 15.0 introduced a new model (hr.attendance.overtime) and mechanisms for an overtime calculation. First I want to share our knowledge with digging into it. There are currently some core bugs with the overtime calculation:

The resource.calendar from hr.contract is not used for overtime calculation as you would expect if hr_attendance and hr_contract is installed. Causes wrong calculations if you edit attendance before a resource calendar (e.g. somebody forgot to logout and you are validating the attendance)

Overtime ignores dates without attendance completly despite it's an actual working day. E.g. if you have to work for 8h and login for 1min you have -7:59h overtime. If you don't login it's +/-0h. This isn't fully consistent.

We are currently trying to develop fixes for these core bugs. The bugs are present from 15.0 to master. We can share the PRs when they are ready.

Following are additional observations regarding the state of the OCA modules in regard to overtime and attendance:

hr_attendance_sheet and hr_attendance_validation: (up to 14.0)

There is a big intersection in the feature sets of both modules. Both are creating a kind of sheet and a multiple step process to verify/approve attendances. They also add features like overtime calculation etc. based on the sheets.

A simple migration PR[1] is maybe not worth it because of the core changes in the overtime calculation. E.g. if an approval process is needed shouldn't only approved attendances count towards your overtime?

hr_holidays_public: (already 15.0)

This module works fine especially the automatic holiday generation with the modules built on top. The module has problems in the overtime calculation. The holidays reduce the days when you request additional holidays. But such a holiday is getting ignored for the overtime calculation. E.g. if you work on a holiday for 9h instead of the regular 8h you get 1h overtime with OCA holiday but 9h for core holiday. It's also not possible to use half holidays (e.g. the 24.12. or 31.12. in Germany). The module also ignores the holidays of the Odoo core. Are there any reasons to stick to the extra model we are not seeing?

In 15.0 Odoo core has a own model for public holidays. So just going on we community solution might result in a growing divergence from the core. The feature to generate public holidays is still very comfortable. A new approach could be to rebuild this to create entries of Odoo core model.

hr_attendance_report_theoretical_time

Here a intersection to the Odoo core overtime calculation in Odoo 15.0 exists, since it comes with some reports (pivot tables).

Is currently somebody else working on it and can share information or experience with overtime in Odoo 15.0 onwards?

Best Regards,

Florian

[1] https://github.com/OCA/hr-attendance/pull/114
-- 
Mit freundlichen Grüßen

Florian Kantelberg
Softwareentwickler

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel.: +49 (0) 4181 1350344
Fax: +49 (0) 4181 1350310

Email: florian.kantelberg@initos.com
Internet: https://www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht: Tostedt, HRB 205226
USt-IdNr: DE 815580155
Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Janik von Rotz - 04:16 - 28 Jul 2023

Re: Overtime calculation in Odoo 15 and OCA

Hi Florian,

I wouldn't call most of the overtime behavior bugs, but differences in 
expectation between Odoo SA's legislation and ours and possibly the use case.


> Is currently somebody else working on it and can share information or

> experience with overtime in Odoo 15.0 onwards?

indeed. For a German customer I've simply replaced Odoo core's overtime 
calculation with the results of
https://github.com/OCA/hr-attendance/tree/15.0/
hr_attendance_report_theoretical_time
which according to the customer gives the correct results. This is pending 
testing and a couple of recalculations on changing things like the work 
calendar or vacations, but with the existing code you already can do sums on 
the overtime table and get the results you'd expect.

As the customer is eager to contribute to OCA, you can expect a PR on hr-
attendance for a module doing this in at most a few weeks :-)

If the customer agrees to share the work done up to now here, I'll happily 
follow up with a link, there we can also discuss further collaboration if 
you're interested.

Best regards,
Holger


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

by Holger Brunn - 03:01 - 28 Jul 2023

1 attachments 1 attachments

Overtime calculation in Odoo 15 and OCA

Hello community,

we are currently looking on overtime calculation in Odoo 15.0. Odoo 15.0 introduced a new model (hr.attendance.overtime) and mechanisms for an overtime calculation. First I want to share our knowledge with digging into it. There are currently some core bugs with the overtime calculation:

The resource.calendar from hr.contract is not used for overtime calculation as you would expect if hr_attendance and hr_contract is installed. Causes wrong calculations if you edit attendance before a resource calendar (e.g. somebody forgot to logout and you are validating the attendance)
Overtime ignores dates without attendance completly despite it's an actual working day. E.g. if you have to work for 8h and login for 1min you have -7:59h overtime. If you don't login it's +/-0h. This isn't fully consistent.

We are currently trying to develop fixes for these core bugs. The bugs are present from 15.0 to master. We can share the PRs when they are ready.

Following are additional observations regarding the state of the OCA modules in regard to overtime and attendance:

hr_attendance_sheet and hr_attendance_validation: (up to 14.0)

There is a big intersection in the feature sets of both modules. Both are creating a kind of sheet and a multiple step process to verify/approve attendances. They also add features like overtime calculation etc. based on the sheets.
A simple migration PR[1] is maybe not worth it because of the core changes in the overtime calculation. E.g. if an approval process is needed shouldn't only approved attendances count towards your overtime?

hr_holidays_public: (already 15.0)

This module works fine especially the automatic holiday generation with the modules built on top. The module has problems in the overtime calculation. The holidays reduce the days when you request additional holidays. But such a holiday is getting ignored for the overtime calculation. E.g. if you work on a holiday for 9h instead of the regular 8h you get 1h overtime with OCA holiday but 9h for core holiday. It's also not possible to use half holidays (e.g. the 24.12. or 31.12. in Germany). The module also ignores the holidays of the Odoo core. Are there any reasons to stick to the extra model we are not seeing?
In 15.0 Odoo core has a own model for public holidays. So just going on we community solution might result in a growing divergence from the core. The feature to generate public holidays is still very comfortable. A new approach could be to rebuild this to create entries of Odoo core model.

hr_attendance_report_theoretical_time

Here a intersection to the Odoo core overtime calculation in Odoo 15.0 exists, since it comes with some reports (pivot tables).

Is currently somebody else working on it and can share information or experience with overtime in Odoo 15.0 onwards?

Best Regards,

Florian

[1] https://github.com/OCA/hr-attendance/pull/114

-- 
Mit freundlichen Grüßen

Florian Kantelberg
Softwareentwickler

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel.: +49 (0) 4181 1350344
Fax: +49 (0) 4181 1350310

Email: florian.kantelberg@initos.com
Internet: https://www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht: Tostedt, HRB 205226
USt-IdNr: DE 815580155
Steuer-Nr: 15/200/53247

by Florian Kantelberg - 01:50 - 28 Jul 2023

Re: Regular postgres VACUUM command

Thanks Moises and Graeme for the detailed information!

I'm going to look at tweaking autovacuum and statistics settings for the 
busy tables. Also, whenever replacing a big chunk of data, I'll run 
ANALYSE <table> afterwards.

As for most situations the default Postgres settings are fine, and I 
can't think of any "generic" solutions other than monitoring and doing 
individual tweaks, I won't create an OCA module for it.

Parting question: can anyone recommend a visual Postgres monitoring tool 
that could ideally also work on Amazon RDS? I'm familiar with log 
parsing tools such as pgBadger, but maybe there's a tool out there 
somewhere that can give information just by connecting to the instance 
and running smart queries?

-Tom

by Tom Blauwendraat - 11:20 - 28 Jul 2023

Re: Bulk return of serials from multiple partner locations to wh/stock

Hi, George.

You might want to complement stock_return_request with its sidekicks sale_stock_return_request and purchase_stock_return_request.

The defaults are quite straight forward: you select the customer, the products that are going to be returned and then you can choose from all the deliveries which serials you'll be receiving. You can add more filters on top of that (operation type, date limit...). The only thing you need to know in advance is the products the customer is returning. When you pick the proper serials, you'll be able to:

- Make a single return picking from several delivery picking origins.

- Refund the linked sale orders at once.

--

David Vidal

Tecnativa

El jue, 20 jul 2023 a las 7:31, George Daramouskas (<notifications@odoo-community.org>) escribió:

Hi,

I have a situation where a lot of lots/serials go to a lot of customers/partners and I have partial returns and need to create backorders.

As it is, I have to go to the serial and - based on the traceability - see which outgoing shipment put it in that location, start an Incoming shipment by clicking Return, leave only the serial that I care about and create backorders for the rest.

This workflow is overwhelming for the warehouse staff due to the volume of movements and I am looking for an alternative workflow, ideally:

1) New Incoming Transfer
2) Add the serials that need to come in stock added one per line
3) Have Odoo find the outgoing shipments for these shipments, create a return incoming shipment only for the serials selected (and a backorder for the rest)
4) Process the incoming shipment

This is what I am roughly looking for, I see https://github.com/OCA/stock-logistics-workflow/tree/15.0/stock_return_request which somewhat does what I want but not exactly since it requires me to add a From: location, among other things.

Any ideas/directions will be appreciated

Cheers

--
George Daramouskas
Odoo Development, https://bitwise.solutions

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by David Vidal - 08:16 - 28 Jul 2023

Re: Packaging in the warehouse

https://youtu.be/ETYINUCDTx4

On Thu, 27 Jul 2023 at 12:47 AM Rafael Blasco <notifications@odoo-community.org> wrote:

https://github.com/OCA/product-attribute/tree/14.0/packaging_uom
https://github.com/OCA/product-attribute/tree/14.0 (search packging or package)

https://github.com/OCA/stock-logistics-warehouse/tree/14.0/stock_product_qty_by_packaging

https://github.com/OCA/stock-logistics-workflow/tree/14.0/stock_quant_package_product_packaging
https://github.com/OCA/stock-logistics-workflow/tree/14.0 (search packging or package)

De: Radovan Skolnik <notifications@odoo-community.org>
Enviado el: miércoles, 28 de junio de 2023 17:47
Para: Contributors <contributors@odoo-community.org>
Asunto: Packaging in the warehouse
Hello,
 
another question for another customer. The customer is dealing with storing 
and distribution of food supplies. The way the products are modelled (in SAP 
which is the source of master data) is a product - for example rice, and a 
packaging - for example 50kg bag, 25kg bag, ...
 
So the first idea was to use Odoo's packaging. However Odoo does not use it for 
inventory management (inside warehouse). The different types of packaging could 
maybe be modelled as attributes for variants. But that doesn't feel right as 
well. In this scenario I would expect to be able to get a report of total 
amount of rice in the warehouse as well as grouped by different packaging 
types.
 
Any pointers are highly welcome. Thank you.
 
Best regards
 
        Radovan Skolnik
 
 
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by lijozom - 06:11 - 27 Jul 2023

Re: OCA Days 2023 - can you help?

This is great.
Tom, I'll be in touch about your workgroup idea here.

We'll definitely need help with the setting up again!

Gonzalo, awesome, thanks for your talk proposal.

The correct link with the missing "L" is here for anyone else wanting to share a talk: https://odoo-community.org/event/oca-days-2023-liege-2023-11-06-2023-11-08-143/track_proposal

On Thu, 27 Jul 2023 at 00:17, Tom Blauwendraat <notifications@odoo-community.org> wrote:

Hi Rebecca!

I wont be doing a talk this year, but I can host a workgroup related to the "tools" repositories, as part of my PSC membership there. I'd love to spend my 2 days hacking around with other people who have an interest in modules in that repository, to share ideas, get things merged, etc. The range of modules there is quite broad. If you need me to prepare a text, I can send it.

I think we're also happy to arrive a bit earlier like last time and help to set up things, but if you have more workgroups that need members, please share

On 7/26/23 05:01, Rebecca Gellatly wrote:

Hello OCA Community.

I hope this finds you all well.

We are gearing for a great OCA Days 2023 but we would love some help from you.

CODESPRINT:

This was an area that last year we felt could certainly use more attention - we want to make this great for you! Would anyone be keen to join a workgroup to help make this part of the event a success? You can either email events@odoo-community.org or reply directly to this email and we'll get things rolling.

TALKS and PRESENTATIONS:

Now is the time to share your talk proposals - deadline for this is 15th September. Have you got a cool new module, an update of an existing module, a case study, training, tutorials, discussion topics.....? Submit your proposals here: https://odoo-community.org/event/oca-days-2023-liege-2023-11-06-2023-11-08-143/track_proposal

Remember this year we will also have a functional track so please share your topics!

REGISTRATIONS ARE OPEN:

Did you know it is the same price to become a member and register for the OCA Days as it is to register for just the non-member ticket?
You can still become a 2023 member and then just book your member event registration for the OCA Days. If you aren't sure if you have bought a membership this year, please get in touch with me (membership@odoo-community.org)

We can't wait to see everyone to celebrate 10 years of the OCA! Lets continue to share knowledge and learn as a community. Making Odoo mightier, together.

Take care,

Rebecca

--

Rebecca Gellatly
General Secretary

Odoo Community Association

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

Rebecca Gellatly

General Secretary

Odoo Community Association

by Rebecca Gellatly - 02:11 - 27 Jul 2023

RE: Issues with outgoing email management in Odoo

And finally

https://github.com/OCA/social/tree/15.0/mail_composer_cc_bcc

Thank you!

De: Lois Rilo Antelo <notifications@odoo-community.org>
Enviado el: jueves, 1 de junio de 2023 11:32
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Issues with outgoing email management in Odoo

Cyril,

Thanks for the insights, I will follow the discussion there to be notified if the work is finished.

Kind regards,

On Thu, Jun 1, 2023 at 10:58 AM Cyril VINH-TUNG <notifications@odoo-community.org> wrote:

Hi Lois
We did not merge mail_body_notified_partner with mail_show_followers because they don't have same functionalities
Check final comment from rafael https://github.com/OCA/social/pull/855#issuecomment-1102348461

We will definitely keep mail_body_notified_partner

Best regards

--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.com
www.invitu.com
Le mer. 31 mai 2023, 21:42, Lois Rilo Antelo <notifications@odoo-community.org> a écrit :
Hi all,

Indeed this is really annoying while dealing with Odoo mailing.

A bit inline with Cyril's answer, as far as I know mail_tracking does not provide the information of the cc'd recipients to the external people (who only receive the email). In our case we have used mail_show_follower module which is already migrated to recent versions, not sure if there is any big difference with mail_body_notified_partner and maybe they can converge in a single module.

Kind regards,
On Wed, May 31, 2023 at 8:27 PM Cyril VINH-TUNG <notifications@odoo-community.org> wrote:
Hi Alex

We also faced long time issues with Odoo mail system and the worst part is that someone lost her job because of that 'unsual' email system (https://github.com/OCA/social/pull/855#issuecomment-1068256758)

We solved this with :
- mail_footer_notified_partner now renamed mail_body_notified_partner (better because the added text is located at the top of the body) + customization of the message saying 'WARNING if you reply to this email the following people will be cc :...'
- disclaimer in the signature of every user that also ask people to reply to the mail with information about the subject and not reply with information that does not concern it

We also use the amazing mail_tracking as mandatory for all our customers but it does not warn the recipients about who will receive the reply.
On the other hand, for incoming emails, we did a PR to mail_tracking that allows to show in the chatter the aliases who were in to and cc (https://github.com/OCA/social/pull/941/commits/d6443446ceca845792d50fd3daa3d1ebdb06c3f0)

We think that Odoo's mail system is great because it organizes communication very well but it's also very hard to convince our customers. People have very bad habits with standard mail systems (they reply to email with information that have nothing to see with the subject, they start another thread instead of replying existing discussion... so on)
That said, we have some customers who use Odoo as 'the' mail system of the company and therefore improve their 'information organization'.
We wrote a blog about it a few years ago (in french) https://www.easypme.com/blog/blog-5/post/le-futur-de-la-messagerie-d-entreprise-55
IMHO best configuration is
- odoo as the main mail system of the company for almost all the employees (notifications in Odoo)
- dedicated standard mailboxes (outside Odoo) for Managers (notifications by email) who might have very sensitive and private information to share directly with partners

Best regards
--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.com
www.invitu.com
Le mer. 31 mai 2023, 05:11, Alexandre Fayolle <notifications@odoo-community.org> a écrit :
Hello everyone,
 
This is a long standing topic in Odoo, but I'm facing it again with an 
unhappy customer. The way Odoo manages the sending of messages to 
followers of a "thread" by sending 1 email per follower, loosing all 
information from people who could have been in CC of an incoming mail, 
is really lame.
 
Is there some knowledge hanging around about a way to change this so 
that Odoo would:
 
* record the CC in a secondary field (say follower_cc_ids) for incoming 
message
* promote a follower_cc to follower in case an incoming mail comes with 
this person in To: rather than CC:
* send outgoing mails with 1 single mail with all followers in To: and 
follower_cc_ids in CC:
 
I'm not super keen in touching this part of the Odoo source code, which 
I find quite obscure,  and but maybe some have walked this path and 
could provide feedback, advice (or even maybe source code).
 
Thanks for your help,
 
 
 
 
 
 
-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30
 
Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France
 
http://www.camptocamp.com
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Lois Rilo Antelo
ERP Consultant Manager at ForgeFlow S.L.
lois.rilo@forgeflow.com | https://www.forgeflow.com
Twitter: /LoisRForgeFlow
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

Lois Rilo Antelo

ERP Consultant Manager at ForgeFlow S.L.

lois.rilo@forgeflow.com | https://www.forgeflow.com

Twitter: /LoisRForgeFlow

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Rafael Blasco (Moduon) - 10:51 - 26 Jul 2023

RE: Packaging in the warehouse

https://github.com/OCA/product-attribute/tree/14.0/packaging_uom

https://github.com/OCA/product-attribute/tree/14.0 (search packging or package)

https://github.com/OCA/stock-logistics-warehouse/tree/14.0/stock_product_qty_by_packaging

https://github.com/OCA/stock-logistics-workflow/tree/14.0/stock_quant_package_product_packaging

https://github.com/OCA/stock-logistics-workflow/tree/14.0 (search packging or package)

De: Radovan Skolnik <notifications@odoo-community.org>
Enviado el: miércoles, 28 de junio de 2023 17:47
Para: Contributors <contributors@odoo-community.org>
Asunto: Packaging in the warehouse

Hello,

another question for another customer. The customer is dealing with storing

and distribution of food supplies. The way the products are modelled (in SAP

which is the source of master data) is a product - for example rice, and a

packaging - for example 50kg bag, 25kg bag, ...

So the first idea was to use Odoo's packaging. However Odoo does not use it for

inventory management (inside warehouse). The different types of packaging could

maybe be modelled as attributes for variants. But that doesn't feel right as

well. In this scenario I would expect to be able to get a report of total

amount of rice in the warehouse as well as grouped by different packaging

types.

Any pointers are highly welcome. Thank you.

Best regards

        Radovan Skolnik

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Rafael Blasco (Moduon) - 10:46 - 26 Jul 2023

Re: OCA Days 2023 - can you help?

Hi Rebecca!

I wont be doing a talk this year, but I can host a workgroup related to the "tools" repositories, as part of my PSC membership there. I'd love to spend my 2 days hacking around with other people who have an interest in modules in that repository, to share ideas, get things merged, etc. The range of modules there is quite broad. If you need me to prepare a text, I can send it.

I think we're also happy to arrive a bit earlier like last time and help to set up things, but if you have more workgroups that need members, please share

On 7/26/23 05:01, Rebecca Gellatly wrote:

Hello OCA Community.

I hope this finds you all well.

We are gearing for a great OCA Days 2023 but we would love some help from you.

CODESPRINT:

This was an area that last year we felt could certainly use more attention - we want to make this great for you! Would anyone be keen to join a workgroup to help make this part of the event a success? You can either email events@odoo-community.org or reply directly to this email and we'll get things rolling.

TALKS and PRESENTATIONS:

Now is the time to share your talk proposals - deadline for this is 15th September. Have you got a cool new module, an update of an existing module, a case study, training, tutorials, discussion topics.....? Submit your proposals here: https://odoo-community.org/event/oca-days-2023-liege-2023-11-06-2023-11-08-143/track_proposal

Remember this year we will also have a functional track so please share your topics!

REGISTRATIONS ARE OPEN:

Did you know it is the same price to become a member and register for the OCA Days as it is to register for just the non-member ticket?
You can still become a 2023 member and then just book your member event registration for the OCA Days. If you aren't sure if you have bought a membership this year, please get in touch with me (membership@odoo-community.org)

We can't wait to see everyone to celebrate 10 years of the OCA! Lets continue to share knowledge and learn as a community. Making Odoo mightier, together.

Take care,

Rebecca

--

Rebecca Gellatly
General Secretary

Odoo Community Association

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Tom Blauwendraat - 02:15 - 26 Jul 2023

Re: OCA Days 2023 - can you help?

Rebecca

Thanks as always, I have already proposed a talk in the form. Be aware that the link is not complete (final L is missing in the link) so you have to complete it manually in order to access it

See you in november

Gonzalo

El mié, 26 jul 2023 a la(s) 00:01, Rebecca Gellatly (notifications@odoo-community.org) escribió:

Hello OCA Community.

I hope this finds you all well.

We are gearing for a great OCA Days 2023 but we would love some help from you.

CODESPRINT:
This was an area that last year we felt could certainly use more attention - we want to make this great for you! Would anyone be keen to join a workgroup to help make this part of the event a success? You can either email events@odoo-community.org or reply directly to this email and we'll get things rolling.

TALKS and PRESENTATIONS:
Now is the time to share your talk proposals - deadline for this is 15th September. Have you got a cool new module, an update of an existing module, a case study, training, tutorials, discussion topics.....? Submit your proposals here: https://odoo-community.org/event/oca-days-2023-liege-2023-11-06-2023-11-08-143/track_proposal
Remember this year we will also have a functional track so please share your topics!

REGISTRATIONS ARE OPEN:
Did you know it is the same price to become a member and register for the OCA Days as it is to register for just the non-member ticket?
You can still become a 2023 member and then just book your member event registration for the OCA Days. If you aren't sure if you have bought a membership this year, please get in touch with me (membership@odoo-community.org)

We can't wait to see everyone to celebrate 10 years of the OCA! Lets continue to share knowledge and learn as a community. Making Odoo mightier, together.

Take care,
Rebecca
--
Rebecca Gellatly
General Secretary
Odoo Community Association

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Gonzalo Ruzafa. - 01:56 - 26 Jul 2023

1 attachments 1 attachments

Inventory barcodes

Hello, we have built most of our system logic and code on barcodes in the inventory page, we use it to activate methods, once barcode is activated it is called form/list_barcode_scanned to enable functionalities.

While trying to upgrade from V15 to V16, I have realised that the odoo code of barcodes changed and we no longer have a way to use our old modules.

I would like to ask if it's possible to enable barcode scanning in any page in inventory(if barcode is scanned while one is on list or form view, to call said model method). So far I have figured out that barcode/barcode_handlers.js barcodeGenericHandlers is responsible for barcode behaviour, but I haven't found a proper way to inherit it and change it's behaviour to fit our needs

by martynas.greicius - 08:31 - 26 Jul 2023

OCA Days 2023 - can you help?

Hello OCA Community.

I hope this finds you all well.

We are gearing for a great OCA Days 2023 but we would love some help from you.

CODESPRINT:

This was an area that last year we felt could certainly use more attention - we want to make this great for you! Would anyone be keen to join a workgroup to help make this part of the event a success? You can either email events@odoo-community.org or reply directly to this email and we'll get things rolling.

TALKS and PRESENTATIONS:

Now is the time to share your talk proposals - deadline for this is 15th September. Have you got a cool new module, an update of an existing module, a case study, training, tutorials, discussion topics.....? Submit your proposals here: https://odoo-community.org/event/oca-days-2023-liege-2023-11-06-2023-11-08-143/track_proposal

Remember this year we will also have a functional track so please share your topics!

REGISTRATIONS ARE OPEN:

Did you know it is the same price to become a member and register for the OCA Days as it is to register for just the non-member ticket?

You can still become a 2023 member and then just book your member event registration for the OCA Days. If you aren't sure if you have bought a membership this year, please get in touch with me (membership@odoo-community.org)

We can't wait to see everyone to celebrate 10 years of the OCA! Lets continue to share knowledge and learn as a community. Making Odoo mightier, together.

Take care,

Rebecca

--

Rebecca Gellatly

General Secretary

Odoo Community Association

by Rebecca Gellatly - 05:00 - 26 Jul 2023

Re: Regular postgres VACUUM command

It is a PostgreSQL tune

However, PSQL <14 had issues related to vacuum process

Be sure to upgrade the PostgreSQL version >=14.6 where many issues related were already fixed

I have tested from odoo >=12.0 and it is working fine!

Check the different release notes for 14.x versions related to vacuum fixes:

https://www.postgresql.org/docs/release/14.6/

- Avoid rare PANIC during updates occurring concurrently with VACUUM (Tom Lane, Jeff Davis)

- Avoid long-term memory leakage in the autovacuum launcher process (Reid Thompson)

https://www.postgresql.org/docs/release/14.2/

- Fix corruption of HOT chains when a RECENTLY_DEAD tuple changes state to fully DEAD during page pruning (Andres Freund)

- Allow parallel vacuuming and concurrent index building to be ignored while computing oldest xmin (Masahiko Sawada)

https://www.postgresql.org/docs/release/14.1/

- Ensure that parallel VACUUM doesn't miss any indexes (Peter Geoghegan, Masahiko Sawada)

- Allow the autovacuum launcher process to respond to pg_log_backend_memory_contexts() requests more quickly (Koyu Tanigawa)

https://www.postgresql.org/docs/release/14.0/

- Numerous performance improvements have been made for parallel queries, heavily-concurrent workloads, partitioned tables, logical replication, and vacuuming.

- Allow vacuum to skip index vacuuming when the number of removable index entries is insignificant (Masahiko Sawada, Peter Geoghegan)
- Allow vacuum to more eagerly add deleted btree pages to the free space map (Peter Geoghegan)
- Allow vacuum to reclaim space used by unused trailing heap line pointers (Matthias van de Meent, Peter Geoghegan)
- Allow vacuum to be more aggressive in removing dead rows during minimal-locking index operations (Álvaro Herrera)
- Speed up vacuuming of databases with many relations (Tatsuhito Kasahara)
- Reduce the default value of vacuum_cost_page_miss to better reflect current hardware capabilities (Peter Geoghegan)
- Add ability to skip vacuuming of TOAST tables (Nathan Bossart)
- Have COPY FREEZE appropriately update page visibility bits (Anastasia Lubennikova, Pavan Deolasee, Jeff Janes)
- Cause vacuum operations to be more aggressive if the table is near xid or multixact wraparound (Masahiko Sawada, Peter Geoghegan)
- Increase warning time and hard limit before transaction id and multi-transaction wraparound (Noah Misch)
- Add per-index information to autovacuum logging output (Masahiko Sawada)

Even if you are not able to upgrade postgresql version you can run a cron to run a "vacuum full"

WARNING: Consider it could get down the whole production instance during this process

El mar, 25 jul 2023 a las 15:02, Graeme Gellatly (<notifications@odoo-community.org>) escribió:

Hi,

In general, auotvaccum is a postgres setting which does that. Usually, I thought it was enabled by default.

In terms of index choice and counts, that is also a postgres setting, default_statistics_target which is probably set too low.

Of course there are myriad other postgres settings which affect what the planner does.

There are some OCA/FOSS modules I have seen over the years for logging slow queries, creating indexes etc, I've never used, but if you really want to run specific commands in Odoo, then it is simple enough with a server action as you can just do env.cr.execute.

On Wed, Jul 26, 2023 at 6:52 AM tblauwendraat <notifications@odoo-community.org> wrote:
Hello,

I'm faced with an Odoo database that is quite active and has some very big tables. I also notice that sometimes, indexes go unused and the query plans go haywire (30 secs where it could be 70ms if using a certain index)

I've learned that this could be because Postgres misestimates the size of the tables, and i should run ANALYZE on the table. VACUUM ANALYZE and other VACUUM commands can remedy this, when run regularly.

I would have expected some kind of OCA module that has scheduled actions for this, but I havent found any.

How would you / have you handle(d) this situation? Would a new OCA module be of use?

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

--

Moisés López Calderón

Mobile: (+521) 477-752-22-30

Twitter: @moylop260

hangout: moylop260@vauxoo.com
http://www.vauxoo.com - Odoo Gold Partner

Twitter: @vauxoo

by Moisés López Calderón - 12:46 - 26 Jul 2023

Re: Regular postgres VACUUM command

Hi,

In general, auotvaccum is a postgres setting which does that. Usually, I thought it was enabled by default.

In terms of index choice and counts, that is also a postgres setting, default_statistics_target which is probably set too low.

Of course there are myriad other postgres settings which affect what the planner does.

There are some OCA/FOSS modules I have seen over the years for logging slow queries, creating indexes etc, I've never used, but if you really want to run specific commands in Odoo, then it is simple enough with a server action as you can just do env.cr.execute.

On Wed, Jul 26, 2023 at 6:52 AM tblauwendraat <notifications@odoo-community.org> wrote:

Hello,

I'm faced with an Odoo database that is quite active and has some very big tables. I also notice that sometimes, indexes go unused and the query plans go haywire (30 secs where it could be 70ms if using a certain index)

I've learned that this could be because Postgres misestimates the size of the tables, and i should run ANALYZE on the table. VACUUM ANALYZE and other VACUUM commands can remedy this, when run regularly.

I would have expected some kind of OCA module that has scheduled actions for this, but I havent found any.

How would you / have you handle(d) this situation? Would a new OCA module be of use?

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Graeme Gellatly - 11:01 - 25 Jul 2023

Archives

Contributors

Re: Regular postgres VACUUM command

Re: pricelist issue

pricelist issue

Re: Overtime calculation in Odoo 15 and OCA

Tier partial invoicing

Re: Overtime calculation in Odoo 15 and OCA

Re: Overtime calculation in Odoo 15 and OCA

Overtime calculation in Odoo 15 and OCA

Re: Regular postgres VACUUM command

Re: Bulk return of serials from multiple partner locations to wh/stock

Re: Packaging in the warehouse

Re: OCA Days 2023 - can you help?

RE: Issues with outgoing email management in Odoo

RE: Packaging in the warehouse

Re: OCA Days 2023 - can you help?

Re: OCA Days 2023 - can you help?

Inventory barcodes

OCA Days 2023 - can you help?

Re: Regular postgres VACUUM command

Re: Regular postgres VACUUM command

Follow us