Archives
Contributors
-
Re: New repos proposal
+1El mar, 14 jun 2022 a las 11:52, Antonio M. Vigliotti (gmail) (<antoniomaria.vigliotti@gmail.com>) escribió:1. web-api: may be useful if full documentation will be available; most of api and/or rest could not be used without documentation
2. pwa-builder: great idea! pwa applications are very very interesting and the give a lot of value to Odoo. Good! Good! Good!
Antonio M. Vigliotti
Mobile (+39) 342.8740910
Il 14/06/22 09:22, Simone Orsi ha scritto:
Hi all,
I'd like to propose 2 new repos:
1. web-api : collect modules to expose or deal with web api (eg: custom management for routes and endpoints, generic tools to handle calls to ext api, etc).
2. pwa-builder : collect modules that allow to create and manage standalone PWA apps. As many of you know I split the core of the shopfloor wms app some time ago and this core now allows you to create - potentially - any kind of PWA app w/ its backend (based on rest services) and frontend tools (VueJS based). This core is now in OCA/wms but that's not really the right place. The name is not adequate too (shopfloor_base) so I think I'm going to rename it to pwa_core or pwa_builder or something similar.
I'd say each of them should have its own PSC but maybe having one is fine too.
Looking fwd to your feedback.
Bests,--
Simone Orsi
Full 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
--Héctor Villarreal OrtegaTechnical Consultanttwitter: /h_vior | Linkedin: /hectorvior
The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
by Héctor Villarreal Ortega - 09:25 - 15 Jun 2022 -
Re: New repos proposal
1. web-api: may be useful if full documentation will be available; most of api and/or rest could not be used without documentation
2. pwa-builder: great idea! pwa applications are very very interesting and the give a lot of value to Odoo. Good! Good! Good!
Antonio M. Vigliotti
Mobile (+39) 342.8740910
Il 14/06/22 09:22, Simone Orsi ha scritto:
Hi all,
I'd like to propose 2 new repos:
1. web-api : collect modules to expose or deal with web api (eg: custom management for routes and endpoints, generic tools to handle calls to ext api, etc).
2. pwa-builder : collect modules that allow to create and manage standalone PWA apps. As many of you know I split the core of the shopfloor wms app some time ago and this core now allows you to create - potentially - any kind of PWA app w/ its backend (based on rest services) and frontend tools (VueJS based). This core is now in OCA/wms but that's not really the right place. The name is not adequate too (shopfloor_base) so I think I'm going to rename it to pwa_core or pwa_builder or something similar.
I'd say each of them should have its own PSC but maybe having one is fine too.
Looking fwd to your feedback.
Bests,--
Simone Orsi
Full 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 Antonio M. Vigliotti - 11:51 - 14 Jun 2022 -
Re: New repos proposal
Hi Daniel,On Tue, Jun 14, 2022 at 9:41 AM Daniel Reis <dreis@opensourceintegrators.com> wrote:
1.
I've been using server-backend to implement API tools.
Here is the WIP of what I've been working recently: https://github.com/OCA/server-backend/pull/151
Would be nice to understand what kind of requirements you are targeting, and compare to mine.Would be nice to have a good description there ;)After a quick look I'd say it contains a lot of duplicated things.Many of those concepts are already implemented in the edi repo and other repos.But this is out of scope I think.A new repo could be a good idea.Note that not all APIs are Web,The repo I propose is specifically for WEB API. I'd like to avoid to have yet a catch-them-all repo to host all the possible modules that might have to deal w/ any kind of "api".(This is also in line w/ what we discussed at board level regarding reducing the scope of the repos whenever possible).I also found the need to integrate with FTP/SFTP, EDI style.There's already an integration between EDI and storage repo ;)2.
Sounds like a good idea.
What about "pwa-tools", similar to "server-tools"Well, since the main scope is to offer a way to build pwa apps I'd prefer "-builder" or "-maker" or smth like that (all in all will be similar to "mis-builder").Thanks
DanielThanks to you. Hope I cleared my POV :)Cheers
On 14/06/22 08:22, Simone Orsi wrote:
Hi all,
I'd like to propose 2 new repos:
1. web-api : collect modules to expose or deal with web api (eg: custom management for routes and endpoints, generic tools to handle calls to ext api, etc).
2. pwa-builder : collect modules that allow to create and manage standalone PWA apps. As many of you know I split the core of the shopfloor wms app some time ago and this core now allows you to create - potentially - any kind of PWA app w/ its backend (based on rest services) and frontend tools (VueJS based). This core is now in OCA/wms but that's not really the right place. The name is not adequate too (shopfloor_base) so I think I'm going to rename it to pwa_core or pwa_builder or something similar.
I'd say each of them should have its own PSC but maybe having one is fine too.
Looking fwd to your feedback.
Bests,--
Simone Orsi
Full 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
--
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
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 11:06 - 14 Jun 2022 -
Re: New repos proposal
1.
I've been using server-backend to implement API tools.
Here is the WIP of what I've been working recently: https://github.com/OCA/server-backend/pull/151
Would be nice to understand what kind of requirements you are targeting, and compare to mine.
A new repo could be a good idea.
Note that not all APIs are Web, I also found the need to integrate with FTP/SFTP, EDI style.
2.
Sounds like a good idea.
What about "pwa-tools", similar to "server-tools"
Thanks
Daniel
On 14/06/22 08:22, Simone Orsi wrote:
Hi all,
I'd like to propose 2 new repos:
1. web-api : collect modules to expose or deal with web api (eg: custom management for routes and endpoints, generic tools to handle calls to ext api, etc).
2. pwa-builder : collect modules that allow to create and manage standalone PWA apps. As many of you know I split the core of the shopfloor wms app some time ago and this core now allows you to create - potentially - any kind of PWA app w/ its backend (based on rest services) and frontend tools (VueJS based). This core is now in OCA/wms but that's not really the right place. The name is not adequate too (shopfloor_base) so I think I'm going to rename it to pwa_core or pwa_builder or something similar.
I'd say each of them should have its own PSC but maybe having one is fine too.
Looking fwd to your feedback.
Bests,--
Simone Orsi
Full 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
--
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:41 - 14 Jun 2022 -
New repos proposal
Hi all,I'd like to propose 2 new repos:1. web-api : collect modules to expose or deal with web api (eg: custom management for routes and endpoints, generic tools to handle calls to ext api, etc).2. pwa-builder : collect modules that allow to create and manage standalone PWA apps. As many of you know I split the core of the shopfloor wms app some time ago and this core now allows you to create - potentially - any kind of PWA app w/ its backend (based on rest services) and frontend tools (VueJS based). This core is now in OCA/wms but that's not really the right place. The name is not adequate too (shopfloor_base) so I think I'm going to rename it to pwa_core or pwa_builder or something similar.I'd say each of them should have its own PSC but maybe having one is fine too.Looking fwd to your feedback.Bests,--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 09:21 - 14 Jun 2022 -
RE: l10n-estonia status and proposing myself as PSC
+1
De: Oleg Kuryan <oleg.kuryan@xpansa.com>
Enviado el: lunes, 13 de junio de 2022 13:07
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: l10n-estonia status and proposing myself as PSC+1
On Mon, Jun 13, 2022 at 11:07 AM Sergio Corato <sergiocorato@gmail.com> wrote:
Agree, +1
Sergio Corato
Il giorno lun 13 giu 2022 alle ore 11:01 Enric Tobella Alomar <etobella@creublanca.es> ha scritto:
+1 From my side, it seems the Project is not used, so any contributor who wants to be a team member is good from my side.
Enric Tobella Alomar
Desarrollo
Av. J. V. Foix 63
08034 Barcelona
Tlf. 932 522 522 (Ext. 1621)
From: "Alexey Pelykh" <alexey.pelykh@corphub.eu>
To: "Contributors" <contributors@odoo-community.org>
Date: Sat, 11 Jun 2022 05:22:34 -0000
Subject: l10n-estonia status and proposing myself as PSC
Dear all,
It seems that PSC for l10n-estonia is inactive entirely as it's been quite over a year since I've requested attention to https://github.com/OCA/l10n-estonia/pull/4 (https://github.com/OCA/l10n-estonia/pull/4#issuecomment-839124178).
Also, I'd like to apply for l10n-estonia PSC.
Kind regards,
Alexey_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación._______________________________________________
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 Rafael Blasco (Moduon) - 12:05 - 14 Jun 2022 -
Re: l10n-estonia status and proposing myself as PSC
It should be members from such PSC that needs to approve the inclusion, but I think it's a bit orphaned, and one of them (Oleg) already approved it, so I don't think it is a problem to include him.Regards.
by Pedro M. Baeza - 01:11 - 13 Jun 2022 -
Re: l10n-estonia status and proposing myself as PSC
+1On Mon, Jun 13, 2022 at 11:07 AM Sergio Corato <sergiocorato@gmail.com> wrote:Agree, +1Sergio CoratoIl giorno lun 13 giu 2022 alle ore 11:01 Enric Tobella Alomar <etobella@creublanca.es> ha scritto:+1 From my side, it seems the Project is not used, so any contributor who wants to be a team member is good from my side.Enric Tobella AlomarDesarrolloAv. J. V. Foix 6308034 BarcelonaTlf. 932 522 522 (Ext. 1621)From: "Alexey Pelykh" <alexey.pelykh@corphub.eu>
To: "Contributors" <contributors@odoo-community.org>
Date: Sat, 11 Jun 2022 05:22:34 -0000
Subject: l10n-estonia status and proposing myself as PSC
Dear all,
It seems that PSC for l10n-estonia is inactive entirely as it's been quite over a year since I've requested attention to https://github.com/OCA/l10n-estonia/pull/4 (https://github.com/OCA/l10n-estonia/pull/4#issuecomment-839124178).
Also, I'd like to apply for l10n-estonia PSC.
Kind regards,
Alexey_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
_______________________________________________
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 Oleg Kuryan - 01:06 - 13 Jun 2022 -
Re: l10n-estonia status and proposing myself as PSC
Agree, +1Sergio CoratoIl giorno lun 13 giu 2022 alle ore 11:01 Enric Tobella Alomar <etobella@creublanca.es> ha scritto:+1 From my side, it seems the Project is not used, so any contributor who wants to be a team member is good from my side.Enric Tobella AlomarDesarrolloAv. J. V. Foix 6308034 BarcelonaTlf. 932 522 522 (Ext. 1621)From: "Alexey Pelykh" <alexey.pelykh@corphub.eu>
To: "Contributors" <contributors@odoo-community.org>
Date: Sat, 11 Jun 2022 05:22:34 -0000
Subject: l10n-estonia status and proposing myself as PSC
Dear all,
It seems that PSC for l10n-estonia is inactive entirely as it's been quite over a year since I've requested attention to https://github.com/OCA/l10n-estonia/pull/4 (https://github.com/OCA/l10n-estonia/pull/4#issuecomment-839124178).
Also, I'd like to apply for l10n-estonia PSC.
Kind regards,
Alexey_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
_______________________________________________
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 - 11:06 - 13 Jun 2022 -
Re: l10n-estonia status and proposing myself as PSC
+1 From my side, it seems the Project is not used, so any contributor who wants to be a team member is good from my side.Enric Tobella AlomarDesarrolloAv. J. V. Foix 6308034 BarcelonaTlf. 932 522 522 (Ext. 1621)From: "Alexey Pelykh" <alexey.pelykh@corphub.eu>
To: "Contributors" <contributors@odoo-community.org>
Date: Sat, 11 Jun 2022 05:22:34 -0000
Subject: l10n-estonia status and proposing myself as PSC
Dear all,
It seems that PSC for l10n-estonia is inactive entirely as it's been quite over a year since I've requested attention to https://github.com/OCA/l10n-estonia/pull/4 (https://github.com/OCA/l10n-estonia/pull/4#issuecomment-839124178).
Also, I'd like to apply for l10n-estonia PSC.
Kind regards,
Alexey_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
pueden contener información reservada y/o confidencial, destinada exclusivamente
para el uso del destinatario o la persona responsable de entregarlo al mismo,
estando su uso no autorizado prohibido legalmente.
Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
salvo ratificación escrita por ambas partes. En caso de su recepción por error,
rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
a su eliminación.
by Enric Tobella Alomar - 11:00 - 13 Jun 2022 -
Re: Problem when 2 person click same button on the same state at the same time.
Thanks Raph for confirming.I am also testing, def _check_concurrency(self): without successSeems to be useless without passing __last_update from the client side. May we we keep our hope on v16 OWL.On Fri, Jun 10, 2022 at 10:46 AM Raphaël Valyi <rvalyi@akretion.com> wrote:Yes an old one... A few years ago, some Odoo employee told me they planned to push live changes to all Odoo open sessions (server push). Might be a way to make such possibility extremely unlikely enough. But so far it seems they didn't developp the idea further. I guess the web client JS/OWL overhaul would come first anyway.Well in the places were this is extremely important like accounting move posting or stock reservation, we should ensure we have some sort of checking. In the other places, cross fingers, detect and fix later, try to partition the records processing over the users in ways that tend to avoid concurrent updates...May be leaving tabs open forever should also be avoided. May be some minimal autoresfresh could help and cost little dev...On Thu, Jun 9, 2022, 3:42 PM Kitti U. <kittiu@ecosoft.co.th> wrote:Found this problem discussed wayed back by our OCA people, https://github.com/odoo/odoo/issues/6737After reading, sound not quite possible, does it?On Fri, Jun 10, 2022 at 1:02 AM Kitti U. <kittiu@ecosoft.co.th> wrote:OK, I think it called the page is "Dirty"I found from ERPNext on the same scenario, the 2nd person attempt to update, it will show warning like following,Error: Document has been modified after you have opened it (2022-06-10 00:59:10.014101, 2022-06-10 00:59:24.963271). Please refresh to get the latest document.This would be good too.On Fri, Jun 10, 2022 at 12:45 AM Kitti U. <kittiu@ecosoft.co.th> wrote:Yes Tom, but with that we need to write checking code everywhere. I wonder if there are better way (or yet some base server module in OCA).I know that in other big name ERP., such an issue was prevented at the framework level, no way it can happen at all. Such things, when occur in accounting documents, can be a serious one.Another thing (of the same technical shallowness of Odoo) I experienced iwas, user somehow click reverse document twice (because slow response), and it produce reverse entries twice!On Fri, Jun 10, 2022 at 12:26 AM Tom Blauwendraat <tom@sunflowerweb.nl> wrote:Regular way is just to check if the sale order is already confirmed, and then don't increase the sequence again.
On 6/9/22 19:22, Kitti U. wrote:
Dear community,
I don't know technical word to describe this. As we knew, Odoo's view is not refreshed in real time as data got updated backend. And this is problematic.
For example,- 2 users open the same document at state Draft, and a Confirm Button visible.
- 1st user clicks Confirm, and document sequence set to 1001
- 2nd user still see the same Confirm button (as page not refreshed), and click it, sequence now change to 1002 without consent of the first person.
Because Odoo don't have mechanism to prevent this by the framework, and this can happen easily on less mature code.
Anyone have good techniques to prevent this, rather than writing the blocking everywhere?
Thanks!_______________________________________________
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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Kitti Upariphutthiphong - 06:36 - 10 Jun 2022 -
Re: Problem when 2 person click same button on the same state at the same time.
Found this problem discussed wayed back by our OCA people, https://github.com/odoo/odoo/issues/6737After reading, sound not quite possible, does it?On Fri, Jun 10, 2022 at 1:02 AM Kitti U. <kittiu@ecosoft.co.th> wrote:OK, I think it called the page is "Dirty"I found from ERPNext on the same scenario, the 2nd person attempt to update, it will show warning like following,Error: Document has been modified after you have opened it (2022-06-10 00:59:10.014101, 2022-06-10 00:59:24.963271). Please refresh to get the latest document.This would be good too.On Fri, Jun 10, 2022 at 12:45 AM Kitti U. <kittiu@ecosoft.co.th> wrote:Yes Tom, but with that we need to write checking code everywhere. I wonder if there are better way (or yet some base server module in OCA).I know that in other big name ERP., such an issue was prevented at the framework level, no way it can happen at all. Such things, when occur in accounting documents, can be a serious one.Another thing (of the same technical shallowness of Odoo) I experienced iwas, user somehow click reverse document twice (because slow response), and it produce reverse entries twice!On Fri, Jun 10, 2022 at 12:26 AM Tom Blauwendraat <tom@sunflowerweb.nl> wrote:
Regular way is just to check if the sale order is already confirmed, and then don't increase the sequence again.
On 6/9/22 19:22, Kitti U. wrote:
Dear community,
I don't know technical word to describe this. As we knew, Odoo's view is not refreshed in real time as data got updated backend. And this is problematic.
For example,- 2 users open the same document at state Draft, and a Confirm Button visible.
- 1st user clicks Confirm, and document sequence set to 1001
- 2nd user still see the same Confirm button (as page not refreshed), and click it, sequence now change to 1002 without consent of the first person.
Because Odoo don't have mechanism to prevent this by the framework, and this can happen easily on less mature code.
Anyone have good techniques to prevent this, rather than writing the blocking everywhere?
Thanks!_______________________________________________
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 Kitti Upariphutthiphong - 08:41 - 9 Jun 2022 -
Re: Problem when 2 person click same button on the same state at the same time.
OK, I think it called the page is "Dirty"I found from ERPNext on the same scenario, the 2nd person attempt to update, it will show warning like following,Error: Document has been modified after you have opened it (2022-06-10 00:59:10.014101, 2022-06-10 00:59:24.963271). Please refresh to get the latest document.This would be good too.On Fri, Jun 10, 2022 at 12:45 AM Kitti U. <kittiu@ecosoft.co.th> wrote:Yes Tom, but with that we need to write checking code everywhere. I wonder if there are better way (or yet some base server module in OCA).I know that in other big name ERP., such an issue was prevented at the framework level, no way it can happen at all. Such things, when occur in accounting documents, can be a serious one.Another thing (of the same technical shallowness of Odoo) I experienced iwas, user somehow click reverse document twice (because slow response), and it produce reverse entries twice!On Fri, Jun 10, 2022 at 12:26 AM Tom Blauwendraat <tom@sunflowerweb.nl> wrote:
Regular way is just to check if the sale order is already confirmed, and then don't increase the sequence again.
On 6/9/22 19:22, Kitti U. wrote:
Dear community,
I don't know technical word to describe this. As we knew, Odoo's view is not refreshed in real time as data got updated backend. And this is problematic.
For example,- 2 users open the same document at state Draft, and a Confirm Button visible.
- 1st user clicks Confirm, and document sequence set to 1001
- 2nd user still see the same Confirm button (as page not refreshed), and click it, sequence now change to 1002 without consent of the first person.
Because Odoo don't have mechanism to prevent this by the framework, and this can happen easily on less mature code.
Anyone have good techniques to prevent this, rather than writing the blocking everywhere?
Thanks!_______________________________________________
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 Kitti Upariphutthiphong - 08:06 - 9 Jun 2022 -
Re: Problem when 2 person click same button on the same state at the same time.
Yes Tom, but with that we need to write checking code everywhere. I wonder if there are better way (or yet some base server module in OCA).I know that in other big name ERP., such an issue was prevented at the framework level, no way it can happen at all. Such things, when occur in accounting documents, can be a serious one.Another thing (of the same technical shallowness of Odoo) I experienced iwas, user somehow click reverse document twice (because slow response), and it produce reverse entries twice!On Fri, Jun 10, 2022 at 12:26 AM Tom Blauwendraat <tom@sunflowerweb.nl> wrote:
Regular way is just to check if the sale order is already confirmed, and then don't increase the sequence again.
On 6/9/22 19:22, Kitti U. wrote:
Dear community,
I don't know technical word to describe this. As we knew, Odoo's view is not refreshed in real time as data got updated backend. And this is problematic.
For example,- 2 users open the same document at state Draft, and a Confirm Button visible.
- 1st user clicks Confirm, and document sequence set to 1001
- 2nd user still see the same Confirm button (as page not refreshed), and click it, sequence now change to 1002 without consent of the first person.
Because Odoo don't have mechanism to prevent this by the framework, and this can happen easily on less mature code.
Anyone have good techniques to prevent this, rather than writing the blocking everywhere?
Thanks!_______________________________________________
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 Kitti Upariphutthiphong - 07:45 - 9 Jun 2022 -
Problem when 2 person click same button on the same state at the same time.
Dear community,I don't know technical word to describe this. As we knew, Odoo's view is not refreshed in real time as data got updated backend. And this is problematic.For example,
- 2 users open the same document at state Draft, and a Confirm Button visible.
- 1st user clicks Confirm, and document sequence set to 1001
- 2nd user still see the same Confirm button (as page not refreshed), and click it, sequence now change to 1002 without consent of the first person.
Because Odoo don't have mechanism to prevent this by the framework, and this can happen easily on less mature code.Anyone have good techniques to prevent this, rather than writing the blocking everywhere?Thanks!
by Kitti Upariphutthiphong - 07:20 - 9 Jun 2022 -
Re: How to import old invoices from legacy system
Hi Radovan,I think that a good approach to bring legacy data in Odoo is to create a model like in your case account.move.imported or account.invoice.imported.In this table you'll create some of important fields to use for comparison with new data.Don't set too many constraints on these fields even if you can setup many2one.After imported data, you can create sql views (query in init function of the new model including the 2 previous ones) in which you can aggregate the two models with Union sqlWith this you can have real statistics on whole history without too many headaches on importYou may customize functions used in Smart Buttons to have a real count or create new ones to have the 2 statsMy 2 cents.Le jeu. 9 juin 2022 à 14:02, Dominique k <dominique.k@elico-corp.com.sg> a écrit :importing old and paid invoices is complicated.you need to import invoicesand the payment entries. then you would need to reconcile them. consequently, they won't appear any longer in your list of unpaid invoicesnext you need to reverse them: let me explain. as you enter old invoices, they would generate revenue and the yearly balance will go to accumulated profit on the balance sheet. But this will be double counted when you will import your actual opening accounting balances. so.. the easiest method would be to reverse (to zero-ise) the entries so that you start with a clean balance sheet.hope this helps--On Thu, 9 Jun 2022 at 6:27 PM, Radovan Skolnik <radovan@skolnik.info> wrote:That makes sense but I guess this will enter into "accounting" and affect many things (accounting-wise). These are invoices spanning more than 15 years and have been "processed" (for the lack of better term on my side). Also not sure I am able to create those balanced entries. So I guess I'd stick with Sale Orders. Best regards Radovan On štvrtok 9. júna 2022 12:17:26 CEST Pedro M. Baeza (Tecnativa) wrote: > You have to create the whole `account.move` with `line_ids` one2many totally > filled and balanced. > > > 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
Dominique KON-SUN-TACK [Project Manager]Odoo Gold Partner, best Odoo Partner 2014 for APACMobile: + 65 8502 2399Skype: dominique_elicoWebsite: www.elico-corp.com
_______________________________________________
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 - 06:20 - 9 Jun 2022 -
Re: Weblate translation locked down for account-analytic-15-0
Thank you 👍--
Yann PAPOUIN, Ingénieur R&D | DEC
by Yann Papouin - 05:01 - 9 Jun 2022
