Archives
Contributors
-
Re: New repo proposal: repair
I agree +1El mié, 12 ene 2022 a las 16:42, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:+1 for me tooEl mié., 12 ene. 2022 15:41, Raphaël Valyi <rvalyi@akretion.com> escribió:Great! +1On Wed, Jan 12, 2022 at 11:27 AM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:It makes sense.On Wed, Jan 12, 2022 at 3:12 PM Sergio Corato <sergiocorato@gmail.com> wrote:+1Sergio CoratoIl giorno mer 12 gen 2022 alle ore 15:06 David Beal <david.beal@akretion.com> ha scritto:Le mer. 12 janv. 2022 à 14:12, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
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
--Lois Rilo AnteloOdoo consultant at ForgeFlow S.L._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ValyiFounder and consultant_______________________________________________
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
--Harald Panten López
CEO
Sygel Technology S.L
+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 07:45 - 12 Jan 2022 -
Re: New repo proposal: repair
+1 for me tooEl mié., 12 ene. 2022 15:41, Raphaël Valyi <rvalyi@akretion.com> escribió:Great! +1On Wed, Jan 12, 2022 at 11:27 AM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:It makes sense.On Wed, Jan 12, 2022 at 3:12 PM Sergio Corato <sergiocorato@gmail.com> wrote:+1Sergio CoratoIl giorno mer 12 gen 2022 alle ore 15:06 David Beal <david.beal@akretion.com> ha scritto:Le mer. 12 janv. 2022 à 14:12, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
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
--Lois Rilo AnteloOdoo consultant at ForgeFlow S.L._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ValyiFounder and consultant_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Pedro M. Baeza - 04:41 - 12 Jan 2022 -
Re: New repo proposal: repair
Great! +1On Wed, Jan 12, 2022 at 11:27 AM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:It makes sense.On Wed, Jan 12, 2022 at 3:12 PM Sergio Corato <sergiocorato@gmail.com> wrote:+1Sergio CoratoIl giorno mer 12 gen 2022 alle ore 15:06 David Beal <david.beal@akretion.com> ha scritto:Le mer. 12 janv. 2022 à 14:12, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
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
--Lois Rilo AnteloOdoo consultant at ForgeFlow S.L._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ValyiFounder and consultant
by "Raphaël Valyi" <rvalyi@akretion.com> - 03:41 - 12 Jan 2022 -
Re: New repo proposal: repair
It makes sense.On Wed, Jan 12, 2022 at 3:12 PM Sergio Corato <sergiocorato@gmail.com> wrote:+1Sergio CoratoIl giorno mer 12 gen 2022 alle ore 15:06 David Beal <david.beal@akretion.com> ha scritto:Le mer. 12 janv. 2022 à 14:12, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
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
--Lois Rilo AnteloOdoo consultant at ForgeFlow S.L.
by Lois Rilo Antelo - 03:26 - 12 Jan 2022 -
Re: New repo proposal: repair
+1El 12 ene 2022, a las 15:12, Sergio Corato <sergiocorato@gmail.com> escribió:
+1Sergio CoratoIl giorno mer 12 gen 2022 alle ore 15:06 David Beal <david.beal@akretion.com> ha scritto:Le mer. 12 janv. 2022 à 14:12, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
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
by Valentín Vinagre - 03:26 - 12 Jan 2022 -
Re: New repo proposal: repair
+1El mié., 12 de enero de 2022 8:12 a. m., Sergio Corato <sergiocorato@gmail.com> escribió:+1Sergio CoratoIl giorno mer 12 gen 2022 alle ore 15:06 David Beal <david.beal@akretion.com> ha scritto:Le mer. 12 janv. 2022 à 14:12, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
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
by "Jesús Alan Ramos Rodríguez" <alan.ramos@jarsa.com> - 03:26 - 12 Jan 2022 -
Re: New repo proposal: repair
+1Sergio CoratoIl giorno mer 12 gen 2022 alle ore 15:06 David Beal <david.beal@akretion.com> ha scritto:Le mer. 12 janv. 2022 à 14:12, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
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 Sergio Corato - 03:11 - 12 Jan 2022 -
Re: New repo proposal: repair
Le mer. 12 janv. 2022 à 14:12, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869_______________________________________________
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 BEAL - 03:06 - 12 Jan 2022 -
New repo proposal: repair
Hi Community,The reasons that support this new repo are:* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repoNow there are no repair modules in 15.0 branches so I think it is a good moment for doing that.For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.WDYT?Thank you for considering this proposal.Have a nice day.--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
by Aarón Henríquez - 02:10 - 12 Jan 2022 -
Re: Sale Workflow v14
That's nice! ThanksOn Tue, Jan 11, 2022 at 9:52 AM Daniel Reis <dreis@opensourceintegrators.com> wrote:Thank you for caring and doing this Denis.
/Daniel
On 11/01/22 07:36, David Beal wrote:
Thanks a lot for this fix,
Le lun. 10 janv. 2022 à 15:47, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,
FYI and thanks to @hailangv, flows have been improved on sale-workflow v14 as now, two modules that were incompatible together are dependent (sale_isolated_quotation depends on sale_quotation_number). Migration scripts have been taken into account and modules updated their major version.
That will easy future tests flows : 2 travis jobs instead of 6.
Best wishes for 2022!
--
Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg
_______________________________________________
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
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
_______________________________________________
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 AnteloOdoo consultant at ForgeFlow S.L.
by Lois Rilo Antelo - 05:01 - 11 Jan 2022 -
Re: Sale Workflow v14
Thank you for caring and doing this Denis.
/Daniel
On 11/01/22 07:36, David Beal wrote:
Thanks a lot for this fix,
Le lun. 10 janv. 2022 à 15:47, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,
FYI and thanks to @hailangv, flows have been improved on sale-workflow v14 as now, two modules that were incompatible together are dependent (sale_isolated_quotation depends on sale_quotation_number). Migration scripts have been taken into account and modules updated their major version.
That will easy future tests flows : 2 travis jobs instead of 6.
Best wishes for 2022!
--
Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg
_______________________________________________
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
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
by Daniel Reis - 09:50 - 11 Jan 2022 -
Re: PSC Real Estate
Sorry. Should be ok on next sync.On Tue, Jan 11, 2022 at 8:56 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:Hi Simone,Wrong PSC ;-) I can stay in Rental but I don't have any input there :-)ThanksOn Mon, Jan 10, 2022 at 3:51 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:Great! Thanks.On Mon, Jan 10, 2022 at 11:42 AM Simone Orsi <simahawk@gmail.com> wrote:Hello,Sorry, I was still on holidays :PYou've been added Denis :)Happy new year everyone!On Wed, Jan 5, 2022 at 4:16 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:Hi all,I think this is not the interest of too much people, but it would be helpful to have write access to it to go forward as some core people approved this.ThanksLe dim. 21 nov. 2021 à 14:52, Roussel, Denis <denis.roussel@acsone.eu> a écrit :@Ignacio Yes, it could be great to push a PR.That can be a base for beginning.ThanksOn Mon, Nov 15, 2021 at 10:12 AM Ignacio Ibeas (Acysos S.L.) <ignacio@acysos.com> wrote:Hello,
This is correct, but we not commit modules because there aren't compliant with the OCA requirements. The modules are in production but are to extense, i we don't make tests.
We can make a PR with all our work.
Greetings
El 15/11/21 a las 9:52, Stéphane Bidoul escribió:
The PSC Representative and only member is currently Ignacio Ibeas (https://odoo-community.org/psc-teams/real-estate-116).
Best regards,
-sbi
On Mon, Nov 15, 2021 at 9:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:
+1
Le ven. 12 nov. 2021 à 15:57, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
@Pedro Manuel Baeza there is one there https://github.com/orgs/OCA/teams/vertical-real-state-maintainers
Le ven. 12 nov. 2021 à 15:52, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Not sure which is the PSC for that, but a valuable contributor like you is a sure +1
Regards.
_______________________________________________
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
--
Raphaël Reverdy
Mobile +33 6 38 02 03 93
Fixe +33 4 82 53 84 60_______________________________________________
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
--
Ignacio Ibeas
Acysos S.L. (www.acysos.com)
Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
Github (http://www.github.com/acysos)
Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
C/ Miguel Astrain 18, 1º Oficina A
31006 Pamplona, Navarra.
ignacio@acysos.com
Tel. 948238905
---------------------- // -------------------
La información contenida en este mensaje de correo electrónico es
confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
persona a la que va dirigido, cualquier divulgación, copia o distribución de
la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
tomada o dejada de tomar basada en la información contenida en este mensaje
queda prohibida y puede ser ilegal.
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this e-mail by anyone is
unauthorised. If you are not the intended recipient, any disclousure,
copying, distribuition or any action taken or omited to be taken in reliance
on it, is prohibited and may be unlawful.
_______________________________________________
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
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source._______________________________________________
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
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 09:06 - 11 Jan 2022 -
Re: PSC Real Estate
Hi Simone,Wrong PSC ;-) I can stay in Rental but I don't have any input there :-)ThanksOn Mon, Jan 10, 2022 at 3:51 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:Great! Thanks.On Mon, Jan 10, 2022 at 11:42 AM Simone Orsi <simahawk@gmail.com> wrote:Hello,Sorry, I was still on holidays :PYou've been added Denis :)Happy new year everyone!On Wed, Jan 5, 2022 at 4:16 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:Hi all,I think this is not the interest of too much people, but it would be helpful to have write access to it to go forward as some core people approved this.ThanksLe dim. 21 nov. 2021 à 14:52, Roussel, Denis <denis.roussel@acsone.eu> a écrit :@Ignacio Yes, it could be great to push a PR.That can be a base for beginning.ThanksOn Mon, Nov 15, 2021 at 10:12 AM Ignacio Ibeas (Acysos S.L.) <ignacio@acysos.com> wrote:Hello,
This is correct, but we not commit modules because there aren't compliant with the OCA requirements. The modules are in production but are to extense, i we don't make tests.
We can make a PR with all our work.
Greetings
El 15/11/21 a las 9:52, Stéphane Bidoul escribió:
The PSC Representative and only member is currently Ignacio Ibeas (https://odoo-community.org/psc-teams/real-estate-116).
Best regards,
-sbi
On Mon, Nov 15, 2021 at 9:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:
+1
Le ven. 12 nov. 2021 à 15:57, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
@Pedro Manuel Baeza there is one there https://github.com/orgs/OCA/teams/vertical-real-state-maintainers
Le ven. 12 nov. 2021 à 15:52, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Not sure which is the PSC for that, but a valuable contributor like you is a sure +1
Regards.
_______________________________________________
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
--
Raphaël Reverdy
Mobile +33 6 38 02 03 93
Fixe +33 4 82 53 84 60_______________________________________________
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
--
Ignacio Ibeas
Acysos S.L. (www.acysos.com)
Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
Github (http://www.github.com/acysos)
Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
C/ Miguel Astrain 18, 1º Oficina A
31006 Pamplona, Navarra.
ignacio@acysos.com
Tel. 948238905
---------------------- // -------------------
La información contenida en este mensaje de correo electrónico es
confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
persona a la que va dirigido, cualquier divulgación, copia o distribución de
la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
tomada o dejada de tomar basada en la información contenida en este mensaje
queda prohibida y puede ser ilegal.
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this e-mail by anyone is
unauthorised. If you are not the intended recipient, any disclousure,
copying, distribuition or any action taken or omited to be taken in reliance
on it, is prohibited and may be unlawful.
_______________________________________________
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
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
----
by Denis Roussel - 08:56 - 11 Jan 2022 -
Re: Sale Workflow v14
Thanks a lot for this fix,Le lun. 10 janv. 2022 à 15:47, Roussel, Denis <denis.roussel@acsone.eu> a écrit :Hi all,FYI and thanks to @hailangv, flows have been improved on sale-workflow v14 as now, two modules that were incompatible together are dependent (sale_isolated_quotation depends on sale_quotation_number). Migration scripts have been taken into account and modules updated their major version.That will easy future tests flows : 2 travis jobs instead of 6.Best wishes for 2022!--
_______________________________________________
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 BEAL - 08:35 - 11 Jan 2022 -
Re: PSC Real Estate
Great! Thanks.On Mon, Jan 10, 2022 at 11:42 AM Simone Orsi <simahawk@gmail.com> wrote:Hello,Sorry, I was still on holidays :PYou've been added Denis :)Happy new year everyone!On Wed, Jan 5, 2022 at 4:16 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:Hi all,I think this is not the interest of too much people, but it would be helpful to have write access to it to go forward as some core people approved this.ThanksLe dim. 21 nov. 2021 à 14:52, Roussel, Denis <denis.roussel@acsone.eu> a écrit :@Ignacio Yes, it could be great to push a PR.That can be a base for beginning.ThanksOn Mon, Nov 15, 2021 at 10:12 AM Ignacio Ibeas (Acysos S.L.) <ignacio@acysos.com> wrote:
Hello,
This is correct, but we not commit modules because there aren't compliant with the OCA requirements. The modules are in production but are to extense, i we don't make tests.
We can make a PR with all our work.
Greetings
El 15/11/21 a las 9:52, Stéphane Bidoul escribió:
The PSC Representative and only member is currently Ignacio Ibeas (https://odoo-community.org/psc-teams/real-estate-116).
Best regards,
-sbi
On Mon, Nov 15, 2021 at 9:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:
+1
Le ven. 12 nov. 2021 à 15:57, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
@Pedro Manuel Baeza there is one there https://github.com/orgs/OCA/teams/vertical-real-state-maintainers
Le ven. 12 nov. 2021 à 15:52, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Not sure which is the PSC for that, but a valuable contributor like you is a sure +1
Regards.
_______________________________________________
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
--
Raphaël Reverdy
Mobile +33 6 38 02 03 93
Fixe +33 4 82 53 84 60_______________________________________________
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
--
Ignacio Ibeas
Acysos S.L. (www.acysos.com)
Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
Github (http://www.github.com/acysos)
Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
C/ Miguel Astrain 18, 1º Oficina A
31006 Pamplona, Navarra.
ignacio@acysos.com
Tel. 948238905
---------------------- // -------------------
La información contenida en este mensaje de correo electrónico es
confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
persona a la que va dirigido, cualquier divulgación, copia o distribución de
la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
tomada o dejada de tomar basada en la información contenida en este mensaje
queda prohibida y puede ser ilegal.
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this e-mail by anyone is
unauthorised. If you are not the intended recipient, any disclousure,
copying, distribuition or any action taken or omited to be taken in reliance
on it, is prohibited and may be unlawful.
_______________________________________________
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
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
by Denis Roussel - 03:55 - 10 Jan 2022 -
Sale Workflow v14
Hi all,FYI and thanks to @hailangv, flows have been improved on sale-workflow v14 as now, two modules that were incompatible together are dependent (sale_isolated_quotation depends on sale_quotation_number). Migration scripts have been taken into account and modules updated their major version.That will easy future tests flows : 2 travis jobs instead of 6.Best wishes for 2022!--
by Denis Roussel - 03:46 - 10 Jan 2022 -
Re: PSC Real Estate
Hello,Sorry, I was still on holidays :PYou've been added Denis :)Happy new year everyone!On Wed, Jan 5, 2022 at 4:16 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:Hi all,I think this is not the interest of too much people, but it would be helpful to have write access to it to go forward as some core people approved this.ThanksLe dim. 21 nov. 2021 à 14:52, Roussel, Denis <denis.roussel@acsone.eu> a écrit :@Ignacio Yes, it could be great to push a PR.That can be a base for beginning.ThanksOn Mon, Nov 15, 2021 at 10:12 AM Ignacio Ibeas (Acysos S.L.) <ignacio@acysos.com> wrote:
Hello,
This is correct, but we not commit modules because there aren't compliant with the OCA requirements. The modules are in production but are to extense, i we don't make tests.
We can make a PR with all our work.
Greetings
El 15/11/21 a las 9:52, Stéphane Bidoul escribió:
The PSC Representative and only member is currently Ignacio Ibeas (https://odoo-community.org/psc-teams/real-estate-116).
Best regards,
-sbi
On Mon, Nov 15, 2021 at 9:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:
+1
Le ven. 12 nov. 2021 à 15:57, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
@Pedro Manuel Baeza there is one there https://github.com/orgs/OCA/teams/vertical-real-state-maintainers
Le ven. 12 nov. 2021 à 15:52, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Not sure which is the PSC for that, but a valuable contributor like you is a sure +1
Regards.
_______________________________________________
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
--
Raphaël Reverdy
Mobile +33 6 38 02 03 93
Fixe +33 4 82 53 84 60_______________________________________________
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
--
Ignacio Ibeas
Acysos S.L. (www.acysos.com)
Odoo Partner (https://www.odoo.com/es_ES/partners/acysos-s-l-80090)
Asociado Asociación Española de Odoo (https://www.aeodoo.org/members/acysos-s-l-24)
Odoo Community Association (https://odoo-community.org/members/acysos-s-l-ignacio-ibeas-760)
Github (http://www.github.com/acysos)
Odoo Apps (https://www.odoo.com/apps/modules/browse?author=Acysos S.L.)
C/ Miguel Astrain 18, 1º Oficina A
31006 Pamplona, Navarra.
ignacio@acysos.com
Tel. 948238905
---------------------- // -------------------
La información contenida en este mensaje de correo electrónico es
confidencial, para ser leída por la(s) persona(s) a quién se dirige. El
acceso a este mensaje por otras personas no está autorizado. Si Ud. no es la
persona a la que va dirigido, cualquier divulgación, copia o distribución de
la información queda prohibida y puede ser ilegal. Asimismo, cualquier acción
tomada o dejada de tomar basada en la información contenida en este mensaje
queda prohibida y puede ser ilegal.
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this e-mail by anyone is
unauthorised. If you are not the intended recipient, any disclousure,
copying, distribuition or any action taken or omited to be taken in reliance
on it, is prohibited and may be unlawful.
_______________________________________________
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
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 11:41 - 10 Jan 2022 -
Re: Odoo v14 - Bank reconciliation flow
Hi Julien, what Graeme is saying is what Odoo put here https://www.youtube.com/watch?v=ZOxsB7F6omY at 1:30 ff Best Frederik Am Freitag, dem 07.01.2022 um 22:52 +0000 schrieb Graeme Gellatly: > Just watch the official Odoo video on how to do this. > > Now personally as an accountant I prefer the new way. It is more > accurate, easy to audit and easier to identify and correct issues, > but to do the old way you just make the transit account and bank > account the same. > > On Sat, Jan 8, 2022 at 10:12 AM Julien Jezequel < > julien.jezequel@numigi.com> wrote: > > Hello All > > > > First, we send our best wishes for this new year, with success in > > your projects. > > > > We wanted to reach because we are starting to plan migrations to > > V14. > > > > We are not satisfied with the v14 bank reconciliation process, and > > the systematic use of transit accounts on payments. > > > > We started to have an analysis on how we could propose a more > > direct and simple way of managing payments and bank > > reconciliation. > > > > We wondered if any of you has already started a project of module > > on which we could contribute, or have any information / feedback to > > share on this matter. > > > > Ideally, we would have an option to offer end users, enabling them > > to manage payments and bank reconciliation with a transit account, > > or with a direct flow close to the one of v12, but this is still an > > analysis in progress. > > > > Have a great day. > > > > > > Julien Jézéquel-Bréard - Chargé de projets > > NUMIGI SOLUTIONS INC. > > julien.jezequel@numigi.com > > > > > > Longueuil, Québec, Canada > > http://www.numigi.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 -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 12:11 - 8 Jan 2022 -
Re: stock: Retroactively removing lots from incompatible products in
stock move history
Oh FYI,The inventory issue you've had I've had tens of times. What you've done is pretty much what I do.On Sat, Jan 8, 2022 at 11:42 AM Graeme Gellatly <gdgellatly@gmail.com> wrote:Personally if they are meant to have lots I wouldn't null them. Just create them new ones and set.Now as for quants there are 2 choices (these are v14) - first backport the Odoo way with a server action like this (if database is small) or the second is the same thing just specific to products.Model Server Actionquants = env['stock.quant'].sudo().search([])
move_line_ids = []
move_line_to_recompute_ids = []
logging = ''
for quant in quants:
move_lines = env['stock.move.line'].search([
('product_id', '=', quant.product_id.id),
('location_id', '=', quant.location_id.id),
('lot_id', '=', quant.lot_id.id),
('package_id', '=', quant.package_id.id),
('owner_id', '=', quant.owner_id.id),
('product_qty', '!=', 0),
])
move_line_ids += move_lines.ids
reserved_on_move_lines = sum(move_lines.mapped('product_qty'))
move_line_str = str.join(', ', [str(move_line_id) for move_line_id in move_lines.ids])
if quant.location_id.should_bypass_reservation():
# If a quant is in a location that should bypass the reservation, its `reserved_quantity` field
# should be 0.
if quant.reserved_quantity != 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is not 0 while its location should bypass the reservation\n"
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
else:
logging += "no move lines are reserved on it, you can safely reset its `reserved_quantity` to 0\n"
logging += '******************\n'
quant.write({'reserved_quantity': 0})
else:
# If a quant is in a reservable location, its `reserved_quantity` should be exactly the sum
# of the `product_qty` of all the partially_available / assigned move lines with the same
# characteristics.
if quant.reserved_quantity == 0:
if move_lines:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is 0 while these move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
elif quant.reserved_quantity < 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is negative while it should not happen\n"
quant.write({'reserved_quantity': 0})
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
logging += '******************\n'
else:
if reserved_on_move_lines != quant.reserved_quantity:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` does not reflect the move lines reservation\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})
else:
if any(move_line.product_qty < 0 for move_line in
move_lines):
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` correctly reflects the move lines reservation but some are negatives\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})
move_lines = env['stock.move.line'].search([('product_id.type', '=',
'product'), ('product_qty', '!=', 0), ('id', 'not in',
move_line_ids)])
move_lines_to_unreserve = []
for move_line in move_lines:
if not move_line.location_id.should_bypass_reservation():
logging += "Problematic move line found: %s (reserved_quantity: %s)\n" % (move_line.id, move_line.product_qty)
logging += "There is no exiting quants despite its `reserved_quantity`\n"
logging += '******************\n'
move_lines_to_unreserve.append(move_line.id)
move_line_to_recompute_ids.append(move_line.id)
if len(move_lines_to_unreserve) > 0:
env.cr.execute("""
UPDATE stock_move_line SET product_uom_qty = 0, product_qty = 0 WHERE id in %s ;
"""
% (tuple(move_lines_to_unreserve), ))
if logging:
env['ir.logging'].sudo().create({
'name': 'Unreserve stock.quant and stock.move.line',
'type': 'server',
'level': 'DEBUG',
'dbname': env.cr.dbname,
'message': logging,
'func': '_update_reserved_quantity',
'path': 'addons/stock/models/stock_quant.py',
'line': '0',
})
if move_line_to_recompute_ids:
env['stock.move.line'].browse(move_line_to_recompute_ids).move_id._recompute_state()Or if database is large/many users I create a Server Action on Product secured to inventory manager with an actionif records:
quants = env['stock.quant'].sudo().search([('product_id', 'in', records.ids)])
move_line_ids = []
move_line_to_recompute_ids = []
logging = ''
for quant in quants:
move_lines = env['stock.move.line'].search([
('product_id', '=', quant.product_id.id),
('location_id', '=', quant.location_id.id),
('lot_id', '=', quant.lot_id.id),
('package_id', '=', quant.package_id.id),
('owner_id', '=', quant.owner_id.id),
('product_qty', '!=', 0),
])
move_line_ids += move_lines.ids
reserved_on_move_lines = sum(move_lines.mapped('product_qty'))
move_line_str = str.join(', ', [str(move_line_id) for move_line_id in move_lines.ids])
if quant.location_id.should_bypass_reservation():
# If a quant is in a location that should bypass the reservation, its `reserved_quantity` field
# should be 0.
if quant.reserved_quantity != 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is not 0 while its location should bypass the reservation\n"
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
else:
logging += "no move lines are reserved on it, you can safely reset its `reserved_quantity` to 0\n"
logging += '******************\n'
quant.write({'reserved_quantity': 0})
else:
# If a quant is in a reservable location, its `reserved_quantity` should be exactly the sum
# of the `product_qty` of all the partially_available / assigned move lines with the same
# characteristics.
if quant.reserved_quantity == 0:
if move_lines:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is 0 while these move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
elif quant.reserved_quantity < 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is negative while it should not happen\n"
quant.write({'reserved_quantity': 0})
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
logging += '******************\n'
else:
if reserved_on_move_lines != quant.reserved_quantity:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` does not reflect the move lines reservation\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})
else:
if any(move_line.product_qty < 0 for move_line in
move_lines):
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` correctly reflects the move lines reservation but some are negatives\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})
move_lines = env['stock.move.line'].search([('product_id.type', '=',
'product'), ('product_qty', '!=', 0), ('id', 'not in',
move_line_ids), ('product_id', 'in', records.ids)])
move_lines_to_unreserve = []
for move_line in move_lines:
if not move_line.location_id.should_bypass_reservation():
logging += "Problematic move line found: %s (reserved_quantity: %s)\n" % (move_line.id, move_line.product_qty)
logging += "There is no exiting quants despite its `reserved_quantity`\n"
logging += '******************\n'
move_lines_to_unreserve.append(move_line.id)
move_line_to_recompute_ids.append(move_line.id)
if len(move_lines_to_unreserve) > 0:
env.cr.execute("""
UPDATE stock_move_line SET product_uom_qty = 0, product_qty = 0 WHERE id in %s ;
"""
% (tuple(move_lines_to_unreserve), ))
if logging:
env['ir.logging'].sudo().create({
'name': 'Unreserve stock.quant and stock.move.line',
'type': 'server',
'level': 'INFO',
'dbname': env.cr.dbname,
'message': logging,
'func': '_update_reserved_quantity',
'path': 'addons/stock/models/stock_quant.py',
'line': '0',
})
if move_line_to_recompute_ids:
env['stock.move.line'].browse(move_line_to_recompute_ids).move_id._recompute_state()On Fri, 7 Jan 2022, 11:27 pm Carmen Bianca Bakker, <carmen@coopiteasy.be> wrote:Hello, Bedankt Tom, you are right. I have exclusively updated stock_quant from a previous backup, and I get effectively the same behaviour as I did when I updated both. That helps narrow down my research a lot---thank you. With kindness, Carmen
_______________________________________________
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:51 - 7 Jan 2022
