Message Threads | The Odoo Community Association

updating module no recreate removed `noupdate="True"` data

Hi there,

I'm wondering if there is any good reason for this default behavior from odoo that if I (as a user) remove a record created by a module using `noupdate="True"` this records is re-created by the ORM at the next update ?

Is there some module that changes that behaviour to let the record unlink while there is ir_model_data record without its related record ?

I'm on the way to suggest ir_model_norecreate module in server-bakend repo to change that behaviour.

I would be happy to hear from you, I think it could be a nice feature for next odoo version and maybe with a new tag `norecreate=True`, any thoughts ?

--

Pierre Verkest

06 81 12 25 20

Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest

by Pierre Verkest - 11:05 - 29 Mar 2021

Re: Discover the OCA priorities for 2021 proposed by the board

Hi Tom and other contributors,

Thanks a lot for your feedback! This post received a very nice welcome, it's really motivating!

I keep note of your ideas about helping functional people get involved and participate to communicate the high value of OCA modules.

If you're motivated for the first article (we can decide later on which platform/way of keeping this content) about the import/export module, that could be a first content to directly try and see how to diffuse it!

We can keep in touch (outside from this mailing list).

To the other contributors: if any other ideas/comments come to your minds, don't hesitate!

Have a nice end of week and super cool week-end!

Virginie

0477/64.17.20

-------- Message initial --------

De: Tom Blauwendraat <tom@sunflowerweb.nl>

Répondre à: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>

À: Contributors <contributors@odoo-community.org>

Objet: Re: Discover the OCA priorities for 2021 proposed by the board

Date: Wed, 17 Mar 2021 09:47:32 -0000

PS. Instead of blogs, which are perhaps a bit flighty and lose their actuality value over time, it could also be some kind of permanent wiki or github-based website, which is updated and community-reviewed as time goes by, with the latest insights per functional topic and Odoo version.

Anyway, ideas ideas... good luck in the new board for 2021!

Op 3/17/21 om 10:38 AM schreef Tom Blauwendraat:

Hi Virginie

In the post you are mentioning people to react below the blog post, but I can't... so then here:

As a part of communication - maybe a method can be to make a platform that facilitates functional people to write attractive documentation/blogs/howto's about solving Odoo problems with OCA modules. For one, this could supplement the thorough lack of documentation on Odoo CE; but also, if consultants and clients read these blogs with examples and understand better that OCA modules are better than alternatives, because they:

- usually solve problems in the best way, as there is hard-won community consensus on their design
- are designed to interoperate together as a holistic eco-system
- are extendible (even better than most Odoo modules are)
- are quality-controlled
- are OpenUpgradable
- etc.

Then they would understand better why it can be commercially more interesting to choose OCA modules and avoid technical debt, then go for the latest and greatest Odoo version supported by some crude customizations and App Store modules, and become disappointed in Odoo in the long run. And then, they would also become motivated to financially support OCA.

A case in point is for example the import/export modules in the "queue" repository - I'm seeing so many inferior hand-rolled syncing implementations lately, that I'm very motivated to write a furious blog to tell everyone to stop doing that and build on the OCA solution. But now, aside from starting my own blog on the subject, I wouldn't know where to place such an article.

Tom

Op 3/17/21 om 10:12 AM schreef Virginie Dewulf:
Hello contributors,

Here is our latest blog post to present the 2021 OCA priorities proposed by the Board:

https://odoo-community.org/blog/the-oca-blog-1/post/what-will-the-oca-community-do-in-2021-109

Don't hesitate to come back to us/me if you'd like to give your feedback!

Have a nice day,
--

Virginie for the Board
_______________________________________________
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 Virginie Dewulf. - 09:56 - 19 Mar 2021

Re: New module for data synchronization between Odoo instances

its done, Daniel, reliably operating at various franchise businesses, proven.

if you like, you have a look into IT IS odoo connect (Link: https://itis-odoo.de/page/it-is-connect Video:https://youtu.be/PhMa44wSp-g ), including a professional approach with an message broker, which operates way more reliable by design (parallelism of messaging, queuing, protocols) than any triggered and scheduled built in approach would do. Granted, this is not the one size fits all approach that others tell about, but you would not take a motorcycle to move concrete blocks, either, you rather take a truck.

Oh, and yes, it is configurable, of cause.

And sorry, for the elder screens, it is available for 12 and 14 now

Von: "Daniel Reis" <dreis@opensourceintegrators.com>
An: "Contributors" <contributors@odoo-community.org>
Gesendet: Freitag, 19. März 2021 15:17:00
Betreff: Re: New module for data synchronization between Odoo instances

Thank you for sharing.
It is interesting, and I may find some useful techniques to borrow.

It does rely on extending the Models to sync, and I have preference for a configuration based solution, like auditlog does.
There is still room to collaborate, this new solution can be designed to also fit your requirements.

On 19/03/2021 12:27, Antonio M. Vigliotti (gmail) wrote:

I have already developed a module to synchronize 2 odoo instances.
here you can find source code.

Currently is running under Odoo 10.0 (server side) and 6.1 7.0 8.0 and 10.0 client side.

I used it to migrate old Odoo DBs. It is a tool to connect and migrate in the same time. I planned portin to 12.0 and 14.0.

May be we can collaborate?

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

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

by Joerg Lorenz. - 06:30 - 19 Mar 2021

Re: New module for data synchronization between Odoo instances

Op 3/19/21 om 3:27 PM schreef Daniel Reis:

> 1) capture events

As for 'capturing' events, note also this discussion I had on the 
subject with Moises:

https://github.com/OCA/server-tools/issues/1249

If I had to do the auditlog module from scratch, I'd probably go for SQL 
triggers instead, since they have way less overhead. You could then let 
a background job do the syncing based on whatever was added to the 
"_changes" table as filled by the trigger.

by Tom Blauwendraat - 05:00 - 19 Mar 2021

Re: New module for data synchronization between Odoo instances

Hi Daniel

Whichever solution you choose, at least I would recommend to rely on 'queue_job' or any other module for asynchroneous job execution. If you use auditlog as a base, I assume your design is to perform a direct action once a record changes. But you don't want the user to wait on such a sync as he is saving the record, you want it to be done in the background, and should it fail for some reason you want it to be retried X times before giving up and notifying.

'Connector' module is following the same logic and also has several handy classes to facilitate dependent model sync.

You might also want to look at base_import_odoo by Holger, in there he's solved some pretty horrid technical corner cases such as the 'chicken and egg' problem that arises if you have a circular dependency in your model structure, eg. a partner record having a bank account which has the same partner as a follower - which record do you sync first? Base_import_odoo is not bidirectional though.

Lastly, I have an abandoned attempt here: https://github.com/sunflowerit/odoosync

The idea here was to have an external tool handle the sync between the both Odoo's and the model structure defined in declarative YAML files. "Labeling" the records is done via XMLids, so that you don't have to add any new fields into Odoo - it can work for a vanilla Odoo instance. I thought the design was pretty neat, and it already works for simple cases, but I never got around to finishing it.

Good luck!

Tom

Op 3/19/21 om 3:27 PM schreef Daniel Reis:

hello

the best repo for a module like this one can be https://github.com/OCA/connector-odoo2odoo

I'm not convinced, because that repo has no code and no activity.
I think OCA/server-tools might be a betetr candidate.

A question: why do you use audit_log as base and not https://github.com/OCA/connector/tree/13.0/connector ?

The problem has three big components:
1) capture events
2) pull/push between instances, and
3) apply/replay events.

The connector might be useful for 2) to push/pull data between instances.
For 1) audilog is the best starting point I found.
For 3) I'm still looking at the details, maybe base_synchro hos goos ideras to use.

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

_______________________________________________
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 - 05:00 - 19 Mar 2021

Re: New module for data synchronization between Odoo instances

hello

the best repo for a module like this one can be https://github.com/OCA/connector-odoo2odoo

I'm not convinced, because that repo has no code and no activity.
I think OCA/server-tools might be a betetr candidate.

A question: why do you use audit_log as base and not https://github.com/OCA/connector/tree/13.0/connector ?

The problem has three big components:
1) capture events
2) pull/push between instances, and
3) apply/replay events.

The connector might be useful for 2) to push/pull data between instances.
For 1) audilog is the best starting point I found.
For 3) I'm still looking at the details, maybe base_synchro hos goos ideras to use.

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

by Daniel Reis - 03:26 - 19 Mar 2021

Re: New module for data synchronization between Odoo instances

Thank you for sharing.
It is interesting, and I may find some useful techniques to borrow.

It does rely on extending the Models to sync, and I have preference for a configuration based solution, like auditlog does.
There is still room to collaborate, this new solution can be designed to also fit your requirements.

On 19/03/2021 12:27, Antonio M. Vigliotti (gmail) wrote:

I have already developed a module to synchronize 2 odoo instances.
here you can find source code.

Currently is running under Odoo 10.0 (server side) and 6.1 7.0 8.0 and 10.0 client side.

I used it to migrate old Odoo DBs. It is a tool to connect and migrate in the same time. I planned portin to 12.0 and 14.0.

May be we can collaborate?

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

by Daniel Reis - 03:15 - 19 Mar 2021

Re: New module for data synchronization between Odoo instances

Hello Daniel,

the best repo for a module like this one can be https://github.com/OCA/connector-odoo2odoo

A question: why do you use audit_log as base and not https://github.com/OCA/connector/tree/13.0/connector ?

Il giorno ven 19 mar 2021 alle ore 13:16 Daniel Reis <dreis@opensourceintegrators.com> ha scritto:

Hello,

I'm working on a module to synchronize data between Odoo instances.
It will support one master with many slave databases, and allow for bidirectional sync.
My design builds on top of, and expands, the great auditlog module (https://github.com/OCA/server-tools/tree/14.0/auditlog)

I'm considering my options on:

a) the repo to contribute the module to, and
b) the name for the module.

Suggestions are welcome.

Thank you

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

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

--

Francesco Apruzzese

Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.

by Francesco Apruzzese - 02:15 - 19 Mar 2021

Re: New module for data synchronization between Odoo instances

Hello Daniel

Did you test https://github.com/JayVora-SerpentCS/SerpentCS_Contributions/tree/13.0/base_synchro ?

Best regards

Le ven. 19 mars 2021 à 02:16, Daniel Reis <dreis@opensourceintegrators.com> a écrit :

Hello,

I'm working on a module to synchronize data between Odoo instances.
It will support one master with many slave databases, and allow for bidirectional sync.
My design builds on top of, and expands, the great auditlog module (https://github.com/OCA/server-tools/tree/14.0/auditlog)

I'm considering my options on:

a) the repo to contribute the module to, and
b) the name for the module.

Suggestions are welcome.

Thank you

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

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

by Cyril VINH-TUNG - 02:06 - 19 Mar 2021

Re: New module for data synchronization between Odoo instances

I have already developed a module to synchronize 2 odoo instances.
here you can find source code.

Currently is running under Odoo 10.0 (server side) and 6.1 7.0 8.0 and 10.0 client side.

I used it to migrate old Odoo DBs. It is a tool to connect and migrate in the same time. I planned portin to 12.0 and 14.0.

May be we can collaborate?

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 19/03/21 13:16, Daniel Reis ha scritto:

Hello,

I'm working on a module to synchronize data between Odoo instances.
It will support one master with many slave databases, and allow for bidirectional sync.
My design builds on top of, and expands, the great auditlog module (https://github.com/OCA/server-tools/tree/14.0/auditlog)

I'm considering my options on:

a) the repo to contribute the module to, and
b) the name for the module.

Suggestions are welcome.

Thank you

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

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

by Antonio M. Vigliotti - 01:26 - 19 Mar 2021

3 attachments 3 attachments

Re: New module for data synchronization between Odoo instances

Hello Daniel,

I think It Is a great idea

Maybe repo could be server-tools and module name odoo_sync or odoo_synchronization?

Regards

Inviato da BlueMail

Il giorno 19 mar 2021, alle ore 13:17, Daniel Reis <dreis@opensourceintegrators.com> ha scritto:

Hello,

I'm working on a module to synchronize data between Odoo instances.
It will support one master with many slave databases, and allow for bidirectional sync.
My design builds on top of, and expands, the great auditlog module (https://github.com/OCA/server-tools/tree/14.0/auditlog)

I'm considering my options on:

a) the repo to contribute the module to, and
b) the name for the module.

Suggestions are welcome.

Thank you

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

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

by Andrea Cometa - 01:26 - 19 Mar 2021

New module for data synchronization between Odoo instances

Hello,

I'm working on a module to synchronize data between Odoo instances.
It will support one master with many slave databases, and allow for bidirectional sync.
My design builds on top of, and expands, the great auditlog module (https://github.com/OCA/server-tools/tree/14.0/auditlog)

I'm considering my options on:

a) the repo to contribute the module to, and
b) the name for the module.

Suggestions are welcome.

Thank you

--

Daniel Reis
Managing Director

M: +351 919991307
E: DReis@OpenSourceIntegrators.com

Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal

by Daniel Reis - 01:15 - 19 Mar 2021

Re: Sale stock: widget qty_to_date

Agreed with Maxime

Il 18.03.2021 09:07, Joël Grand-Guillaume ha scritto:

Agreed with you Maxime !

On Wed, Mar 17, 2021 at 8:37 PM Sandip Mangukiya <smangukiya@opensourceintegrators.com> wrote:

👍

SANDIP MANGUKIYA
TEAM LEAD MANAGER

O: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.com

P.O. BOX 940, HIGLEY, AZ 85236

On Wed, Mar 17, 2021 at 12:22 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:

Here you go

https://github.com/odoo/odoo/pull/68044

MAXIME CHAMBREUIL
MANAGING DIRECTOR LATAM

O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com

P.O. BOX 940, HIGLEY, AZ 85236

On Wed, Mar 17, 2021 at 10:56 AM Nhomar Hernández <nhomar@vauxoo.com> wrote:

El mié, 17 de mar. de 2021 a la(s) 09:32, Maxime Chambreuil (mchambreuil@opensourceintegrators.com) escribió:

Hello everyone,

We recently went live with a customer on Odoo 14.0. On sales order lines, Odoo added this widget with the green/red graph icon and the quantity available/forecasted.

The widget assumes that all the products in the warehouse are available for sales. It takes the view location "WH" to compute the quantities available/forecasted and provides that information to sales people.

In previous versions, it was documented that the "Location Stock field on the warehouse shows the place of products available for delivery to a customer directly from this warehouse. Availability is given by all the products in that location and any child locations."

This was the reason locations like Output, RMA, Repair or any use case where a company store items that are not for sales were NOT created under "Stock", so that they would not show up as available to salespeople.

I reported an issue to Odoo support but their answer is to create a location outside of any warehouse using the Rental location as an example.

This sounds terribly wrong to me and disconnected from the reality.

You are right... In fact we can not do that because then if you have let's say 10 stores you will need 20 unlinked elements to manage for example RMA for each one of them?

I think you should include in your ticket the fact that it was a supported feature (Exclude locations, it does not matter the reason).

In fact the rent warehouse does not make sense either to be outside (but I did not work with that module yet).

Short term solution, we patched the stock and sale_stock modules to use the Stock location, but there are risks of breaking something

What do you think? What's your opinion?

I think it is a bug, May you please include the patch in a PR to odoo/odoo?

Then we can discuss the technical topic... I would love to give opinions there because that's one of the key features we use to arrange medium/big warehouses.

Regards

MAXIME CHAMBREUIL
MANAGING DIRECTOR LATAM

O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com

P.O. BOX 940, HIGLEY, AZ 85236

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

--

Nhomar G Hernández

Vauxoo | CEO

¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar

México · Venezuela · Costa Rica · Perú

nhomar@vauxoo.com vauxoo.com/contactus

_______________________________________________
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

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

--

camptocamp

INNOVATIVE SOLUTIONS

BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head

Business Solutions

+41 21 619 10 28

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

-- 

Stefano Sforzi
Tel (CH): +41 91 210 23 40
Tel (IT): +39 0331 158 7090 
https://www.agilebg.com

by stefano sforzi - 09:16 - 18 Mar 2021

Re: Sale stock: widget qty_to_date

Agreed with you Maxime !

On Wed, Mar 17, 2021 at 8:37 PM Sandip Mangukiya <smangukiya@opensourceintegrators.com> wrote:

👍
SANDIP MANGUKIYA
TEAM LEAD MANAGER
O: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

On Wed, Mar 17, 2021 at 12:22 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
Here you go

https://github.com/odoo/odoo/pull/68044

MAXIME CHAMBREUIL
MANAGING DIRECTOR LATAM
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

On Wed, Mar 17, 2021 at 10:56 AM Nhomar Hernández <nhomar@vauxoo.com> wrote:

El mié, 17 de mar. de 2021 a la(s) 09:32, Maxime Chambreuil (mchambreuil@opensourceintegrators.com) escribió:
Hello everyone,

We recently went live with a customer on Odoo 14.0. On sales order lines, Odoo added this widget with the green/red graph icon and the quantity available/forecasted.

The widget assumes that all the products in the warehouse are available for sales. It takes the view location "WH" to compute the quantities available/forecasted and provides that information to sales people.

In previous versions, it was documented that the "Location Stock field on the warehouse shows the place of products available for delivery to a customer directly from this warehouse. Availability is given by all the products in that location and any child locations."

This was the reason locations like Output, RMA, Repair or any use case where a company store items that are not for sales were NOT created under "Stock", so that they would not show up as available to salespeople.

I reported an issue to Odoo support but their answer is to create a location outside of any warehouse using the Rental location as an example.

This sounds terribly wrong to me and disconnected from the reality.

You are right... In fact we can not do that because then if you have let's say 10 stores you will need 20 unlinked elements to manage for example RMA for each one of them?

I think you should include in your ticket the fact that it was a supported feature (Exclude locations, it does not matter the reason).

In fact the rent warehouse does not make sense either to be outside (but I did not work with that module yet).

Short term solution, we patched the stock and sale_stock modules to use the Stock location, but there are risks of breaking something

What do you think? What's your opinion?

I think it is a bug, May you please include the patch in a PR to odoo/odoo?

Then we can discuss the technical topic... I would love to give opinions there because that's one of the key features we use to arrange medium/big warehouses.

Regards

MAXIME CHAMBREUIL
MANAGING DIRECTOR LATAM
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

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

--
Nhomar G Hernández
Vauxoo | CEO
¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar
México · Venezuela · Costa Rica · Perú
nhomar@vauxoo.com vauxoo.com/contactus

_______________________________________________
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

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

--

camptocamp

INNOVATIVE SOLUTIONS

BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume

Department Head

Business Solutions

+41 21 619 10 28

www.camptocamp.com

by Joël Grand Guillaume - 09:06 - 18 Mar 2021

Re: Sale stock: widget qty_to_date

👍

SANDIP MANGUKIYA
TEAM LEAD MANAGER

O: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.com

P.O. BOX 940, HIGLEY, AZ 85236

On Wed, Mar 17, 2021 at 12:22 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:

Here you go

https://github.com/odoo/odoo/pull/68044

MAXIME CHAMBREUIL
MANAGING DIRECTOR LATAM
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

On Wed, Mar 17, 2021 at 10:56 AM Nhomar Hernández <nhomar@vauxoo.com> wrote:

El mié, 17 de mar. de 2021 a la(s) 09:32, Maxime Chambreuil (mchambreuil@opensourceintegrators.com) escribió:
Hello everyone,

We recently went live with a customer on Odoo 14.0. On sales order lines, Odoo added this widget with the green/red graph icon and the quantity available/forecasted.

The widget assumes that all the products in the warehouse are available for sales. It takes the view location "WH" to compute the quantities available/forecasted and provides that information to sales people.

In previous versions, it was documented that the "Location Stock field on the warehouse shows the place of products available for delivery to a customer directly from this warehouse. Availability is given by all the products in that location and any child locations."

This was the reason locations like Output, RMA, Repair or any use case where a company store items that are not for sales were NOT created under "Stock", so that they would not show up as available to salespeople.

I reported an issue to Odoo support but their answer is to create a location outside of any warehouse using the Rental location as an example.

This sounds terribly wrong to me and disconnected from the reality.

You are right... In fact we can not do that because then if you have let's say 10 stores you will need 20 unlinked elements to manage for example RMA for each one of them?

I think you should include in your ticket the fact that it was a supported feature (Exclude locations, it does not matter the reason).

In fact the rent warehouse does not make sense either to be outside (but I did not work with that module yet).

Short term solution, we patched the stock and sale_stock modules to use the Stock location, but there are risks of breaking something

What do you think? What's your opinion?

I think it is a bug, May you please include the patch in a PR to odoo/odoo?

Then we can discuss the technical topic... I would love to give opinions there because that's one of the key features we use to arrange medium/big warehouses.

Regards

MAXIME CHAMBREUIL
MANAGING DIRECTOR LATAM
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

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

--
Nhomar G Hernández
Vauxoo | CEO
¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar
México · Venezuela · Costa Rica · Perú
nhomar@vauxoo.com vauxoo.com/contactus

_______________________________________________
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 Sandip Mangukiya - 08:36 - 17 Mar 2021

Re: Sale stock: widget qty_to_date

Here you go

https://github.com/odoo/odoo/pull/68044

MAXIME CHAMBREUIL
MANAGING DIRECTOR LATAM

O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com

P.O. BOX 940, HIGLEY, AZ 85236

On Wed, Mar 17, 2021 at 10:56 AM Nhomar Hernández <nhomar@vauxoo.com> wrote:

El mié, 17 de mar. de 2021 a la(s) 09:32, Maxime Chambreuil (mchambreuil@opensourceintegrators.com) escribió:
Hello everyone,

We recently went live with a customer on Odoo 14.0. On sales order lines, Odoo added this widget with the green/red graph icon and the quantity available/forecasted.

The widget assumes that all the products in the warehouse are available for sales. It takes the view location "WH" to compute the quantities available/forecasted and provides that information to sales people.

In previous versions, it was documented that the "Location Stock field on the warehouse shows the place of products available for delivery to a customer directly from this warehouse. Availability is given by all the products in that location and any child locations."

This was the reason locations like Output, RMA, Repair or any use case where a company store items that are not for sales were NOT created under "Stock", so that they would not show up as available to salespeople.

I reported an issue to Odoo support but their answer is to create a location outside of any warehouse using the Rental location as an example.

This sounds terribly wrong to me and disconnected from the reality.

You are right... In fact we can not do that because then if you have let's say 10 stores you will need 20 unlinked elements to manage for example RMA for each one of them?

I think you should include in your ticket the fact that it was a supported feature (Exclude locations, it does not matter the reason).

In fact the rent warehouse does not make sense either to be outside (but I did not work with that module yet).

Short term solution, we patched the stock and sale_stock modules to use the Stock location, but there are risks of breaking something

What do you think? What's your opinion?

I think it is a bug, May you please include the patch in a PR to odoo/odoo?

Then we can discuss the technical topic... I would love to give opinions there because that's one of the key features we use to arrange medium/big warehouses.

Regards

MAXIME CHAMBREUIL
MANAGING DIRECTOR LATAM
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

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

--
Nhomar G Hernández
Vauxoo | CEO
¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar
México · Venezuela · Costa Rica · Perú
nhomar@vauxoo.com vauxoo.com/contactus

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

by Maxime Chambreuil - 08:21 - 17 Mar 2021

Re: Sale stock: widget qty_to_date

El mié, 17 de mar. de 2021 a la(s) 09:32, Maxime Chambreuil (mchambreuil@opensourceintegrators.com) escribió:

Hello everyone,

We recently went live with a customer on Odoo 14.0. On sales order lines, Odoo added this widget with the green/red graph icon and the quantity available/forecasted.

The widget assumes that all the products in the warehouse are available for sales. It takes the view location "WH" to compute the quantities available/forecasted and provides that information to sales people.

In previous versions, it was documented that the "Location Stock field on the warehouse shows the place of products available for delivery to a customer directly from this warehouse. Availability is given by all the products in that location and any child locations."

This was the reason locations like Output, RMA, Repair or any use case where a company store items that are not for sales were NOT created under "Stock", so that they would not show up as available to salespeople.

I reported an issue to Odoo support but their answer is to create a location outside of any warehouse using the Rental location as an example.

This sounds terribly wrong to me and disconnected from the reality.

You are right... In fact we can not do that because then if you have let's say 10 stores you will need 20 unlinked elements to manage for example RMA for each one of them?

I think you should include in your ticket the fact that it was a supported feature (Exclude locations, it does not matter the reason).

In fact the rent warehouse does not make sense either to be outside (but I did not work with that module yet).

Short term solution, we patched the stock and sale_stock modules to use the Stock location, but there are risks of breaking something

What do you think? What's your opinion?

I think it is a bug, May you please include the patch in a PR to odoo/odoo?

Then we can discuss the technical topic... I would love to give opinions there because that's one of the key features we use to arrange medium/big warehouses.

Regards

MAXIME CHAMBREUIL
MANAGING DIRECTOR LATAM
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236

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

--

Nhomar G Hernández

Vauxoo | CEO

¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar

México · Venezuela · Costa Rica · Perú

phone nhomar@vauxoo.com vauxoo.com/contactus

by Nhomar Hernández - 05:56 - 17 Mar 2021

Sale stock: widget qty_to_date

Hello everyone,

We recently went live with a customer on Odoo 14.0. On sales order lines, Odoo added this widget with the green/red graph icon and the quantity available/forecasted.

The widget assumes that all the products in the warehouse are available for sales. It takes the view location "WH" to compute the quantities available/forecasted and provides that information to sales people.

In previous versions, it was documented that the "Location Stock field on the warehouse shows the place of products available for delivery to a customer directly from this warehouse. Availability is given by all the products in that location and any child locations."

This was the reason locations like Output, RMA, Repair or any use case where a company store items that are not for sales were NOT created under "Stock", so that they would not show up as available to salespeople.

I reported an issue to Odoo support but their answer is to create a location outside of any warehouse using the Rental location as an example.

This sounds terribly wrong to me and disconnected from the reality.

Short term solution, we patched the stock and sale_stock modules to use the Stock location, but there are risks of breaking something.

What do you think? What's your opinion?

MAXIME CHAMBREUIL
MANAGING DIRECTOR LATAM

O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com

P.O. BOX 940, HIGLEY, AZ 85236

by Maxime Chambreuil - 04:31 - 17 Mar 2021

Re: Discover the OCA priorities for 2021 proposed by the board

Hi,

Short and essential sharing of the targets and anticipated means to try to achieve them.
Thank you very much to Virginie and all the board.

My 2 cents idea today regarding the documentation:

On our side, we tried and I experienced several attempts at different companies over the past 20 years.

In the end, we decided with the creation of the Numigi company 3 years ago:

- advanced readme into the module,

- functional and technical specifications upstream of the development of the module then transferred to a page as wiki.

This last year, we moved this last part of documentation in document.page (OCA modules ;-) instead of a couple github + netlify which were good and interesting but external to our monitoring and management system.

Have a nice day and all the best from Canada!

Bruno Joliveau - Président

NUMIGI SOLUTIONS INC.

bruno.joliveau@numigi.com

(514) 317-7944

Longueuil, Québec, Canada

http://www.numigi.com/

Le mer. 17 mars 2021 à 05:12, Virginie Dewulf <virginie@coopiteasy.be> a écrit :

Hello contributors,

Here is our latest blog post to present the 2021 OCA priorities proposed by the Board:
https://odoo-community.org/blog/the-oca-blog-1/post/what-will-the-oca-community-do-in-2021-109

Don't hesitate to come back to us/me if you'd like to give your feedback!

Have a nice day,
--
Virginie for the Board
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Bruno Joliveau - 01:26 - 17 Mar 2021

Re: Mail cc

I am interested!

On Sun, 27 Dec 2020 at 22:47, Rafael Blasco <rblasco@rbnpro.com> wrote:

Hello,

I would recommend as best approach this one: https://github.com/sygel-technology/sy-server-backend/tree/12.0/mail_show_follower

I’m sure Valentin can propose this module to OCA if there is interest.

Regards,
Rafael

De: Sergio Corato <sergiocorato@gmail.com>
Enviado el: martes, 1 de diciembre de 2020 10:47
Para: Contributors <contributors@odoo-community.org>
Asunto: Mail cc

Hi all,

AFAIK there isn't a generic approach to send mail with CC instead of A, or I miss something?

The use case would be something like: if a mail is sent to 1 recipient, go with A. If there are multiple recipients, 1 go with A and the other with CC.

So an 'integrated' logic, without user intervention (except to optionally change the A recipient, or something other).

Thanks in advance!

Sergio Corato
_______________________________________________
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

--

Lorenzo Battistini
https://github.com/eLBati

takobi.online | Facebook | Linkedin | Youtube

by Lorenzo Battistini. - 11:21 - 17 Mar 2021

Archives

Contributors

updating module no recreate removed `noupdate="True"` data

Re: Discover the OCA priorities for 2021 proposed by the board

Re: New module for data synchronization between Odoo instances

Re: New module for data synchronization between Odoo instances

Re: New module for data synchronization between Odoo instances

Re: New module for data synchronization between Odoo instances

Re: New module for data synchronization between Odoo instances

Re: New module for data synchronization between Odoo instances

Re: New module for data synchronization between Odoo instances

Re: New module for data synchronization between Odoo instances

Re: New module for data synchronization between Odoo instances

New module for data synchronization between Odoo instances

Re: Sale stock: widget qty_to_date

Re: Sale stock: widget qty_to_date

Re: Sale stock: widget qty_to_date

Re: Sale stock: widget qty_to_date

Re: Sale stock: widget qty_to_date

Sale stock: widget qty_to_date

Re: Discover the OCA priorities for 2021 proposed by the board

Re: Mail cc

Follow us