Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Async import external employee data from db view to Odoo.
    Dear Community,

    We need to get data from external HR applications (they will provide an mssql database view), for users and employee data into Odoo.

    It seems to be quite a generic use case, to become an addon, so I want to check with community, would be nice to know how you normally cope with this.

    I checked OCA and plan to use the followings as starting point.
    Thank you!
    Kitti U.

    by Kitti Upariphutthiphong - 09:51 - 28 Feb 2021
  • Re: Postgresql Table partitioning in Odoo
    Graeme,

    I have considered for example to create materialized views for aggregated data in connection with the financial reports, MIS Builder, etc. The drawback is that it essentially requires you to introduce a lot of changes to the application logic in order to make use of those materialized views. At this stage partitioning seems to me like a better idea, because the change is (almost) limited to the database, and you can continue to use the application as it has been designed.

    I'm not concerned (yet) by the 32 bits limitation of id's.

    On Sat, Feb 27, 2021 at 3:12 AM Graeme Gellatly <gdgellatly@gmail.com> wrote:
    Hi,

    It's not really practical unfortunately. You can't just decide to use partitions. Well I suppose maybe you could rename the existing table, create a new one partitioned and then attach the renamed table as a partition if you were doing partition by date or id. I think a lot of the problem with aml in particular is the rows have gotten very wide as well.

    Materialized views, partial indexes, clustering tables, even just good GIN indexing are all quite a lot simpler and can offer far better performance depending on need. Indeed I remember 8 or 9 years ago there was a popular module for account move lines which implemented what could best be described as homegrown matviews to store aggregate AML data. However, all these solutions are still constrained by Odoo 32 bit id's. So if by getting large you mean approaching the billions, then that's a new set of problems.

    There is one set of solutions which I'm quite interested in for performance. That is using logical BDR to partition the write server of multi master databases. It seems this is doable without too much change but Odoo's id model doesn't meet the requirements, needing either GUID or BIGSERIAL. My idea is essentially to partition tables say geographically on some field, say company id, or create_uid and then run local Odoo instances in those geographies with their own pg cluster but achieving global consistency.

    On Sat, Feb 27, 2021 at 8:17 AM Jordi Ballester Alomar <jordi.ballester@forgeflow.com> wrote:
    Dear contributors,

    We have a case of a database where some tables, like account.move.line are growing to absurd numbers of records. At this point we are considering using Postgresql Table partitioning to speed up performance. Has anyone of you had experience with table partitioning?

    Looking forward to hearing your thoughts. 

    Regards,
    --
    Jordi Ballester Alomar
    CEO & Founder | ForgeFlow

    _______________________________________________
    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



    --
    Jordi Ballester Alomar
    CEO & Founder | ForgeFlow
    by Jordi Ballester Alomar - 07:26 - 27 Feb 2021
  • Re: Postgresql Table partitioning in Odoo
    Nhomar,

    In this case the account_move_line table is larger than 10 millions records. The company is using inventory accounting, and does a lot of inventory transactions. That does not help, as it creates a big number of inventory related AML's. I'd like to get rid of inventory accounting, of course! :)

    We refactored the OCA financial reports completely, for example, and certainly this has added a lot of benefits.

    What makes sense for me with partitioning a table, especially in accounting, is that you don't often make use of previous years move lines, except when you are computing an initial balance.

    I tried to manually transform the account_move_line to a partitioned table with success. See https://github.com/odoo/odoo/pull/66964. I would need to test with a large database now to check if this really brings the expected benefits.

    As Daniel Reis suggestested, using partial indexes seems interesting. However the Postgres recommends not to use them when partitioning really makes more sense. https://www.postgresql.org/docs/current/indexes-partial.html

    "If your table is large enough that a single index really is a bad idea, you should look into using partitioning instead (see Section 5.11). With that mechanism, the system does understand that the tables and indexes are non-overlapping, so far better performance is possible."

    Partitioning in odoo must be limited to using always the "id" column in the partitions, as the primary key must be contained in all partitions.



    On Fri, Feb 26, 2021 at 8:57 PM Nhomar Hernández <nhomar@vauxoo.com> wrote:
    How many records is for you **Absurd**.?

    We try to fix odoo performance in the views or tools that are slow with records over between 1 and 10 millions.

    But not always touch postgres will help.. Did you make the measurement?

    El vie, 26 de feb. de 2021 a la(s) 13:17, Jordi Ballester Alomar (jordi.ballester@forgeflow.com) escribió:
    Dear contributors,

    We have a case of a database where some tables, like account.move.line are growing to absurd numbers of records. At this point we are considering using Postgresql Table partitioning to speed up performance. Has anyone of you had experience with table partitioning?

    Looking forward to hearing your thoughts. 

    Regards,
    --
    Jordi Ballester Alomar
    CEO & Founder | ForgeFlow

    _______________________________________________
    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 phone 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



    --
    Jordi Ballester Alomar
    CEO & Founder | ForgeFlow
    by Jordi Ballester Alomar - 07:21 - 27 Feb 2021
  • Re: Postgresql Table partitioning in Odoo
    Hi,

    It's not really practical unfortunately. You can't just decide to use partitions. Well I suppose maybe you could rename the existing table, create a new one partitioned and then attach the renamed table as a partition if you were doing partition by date or id. I think a lot of the problem with aml in particular is the rows have gotten very wide as well.

    Materialized views, partial indexes, clustering tables, even just good GIN indexing are all quite a lot simpler and can offer far better performance depending on need. Indeed I remember 8 or 9 years ago there was a popular module for account move lines which implemented what could best be described as homegrown matviews to store aggregate AML data. However, all these solutions are still constrained by Odoo 32 bit id's. So if by getting large you mean approaching the billions, then that's a new set of problems.

    There is one set of solutions which I'm quite interested in for performance. That is using logical BDR to partition the write server of multi master databases. It seems this is doable without too much change but Odoo's id model doesn't meet the requirements, needing either GUID or BIGSERIAL. My idea is essentially to partition tables say geographically on some field, say company id, or create_uid and then run local Odoo instances in those geographies with their own pg cluster but achieving global consistency.

    On Sat, Feb 27, 2021 at 8:17 AM Jordi Ballester Alomar <jordi.ballester@forgeflow.com> wrote:
    Dear contributors,

    We have a case of a database where some tables, like account.move.line are growing to absurd numbers of records. At this point we are considering using Postgresql Table partitioning to speed up performance. Has anyone of you had experience with table partitioning?

    Looking forward to hearing your thoughts. 

    Regards,
    --
    Jordi Ballester Alomar
    CEO & Founder | ForgeFlow

    _______________________________________________
    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 - 03:11 - 27 Feb 2021
  • Re: Postgresql Table partitioning in Odoo
    Hello Jordi,

    In some cases Partial Indexes can do the trick.

    For example, you could have a partial index only for active records. Since most of the time there is filter condition on the active field, the smaller partial index can be used instead of a full index.

    This can give you the same benefits as a partitioned table, with a simpler solution (no need to push data around).

    More info:


    --dr 

    No dia 26/02/2021, às 19:17, Jordi Ballester Alomar <jordi.ballester@forgeflow.com> escreveu:

    
    Dear contributors,

    We have a case of a database where some tables, like account.move.line are growing to absurd numbers of records. At this point we are considering using Postgresql Table partitioning to speed up performance. Has anyone of you had experience with table partitioning?

    Looking forward to hearing your thoughts. 

    Regards,
    --
    Jordi Ballester Alomar
    CEO & Founder | ForgeFlow

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

    by Daniel Reis - 09:36 - 26 Feb 2021
  • Re: Postgresql Table partitioning in Odoo
    How many records is for you **Absurd**.?

    We try to fix odoo performance in the views or tools that are slow with records over between 1 and 10 millions.

    But not always touch postgres will help.. Did you make the measurement?

    El vie, 26 de feb. de 2021 a la(s) 13:17, Jordi Ballester Alomar (jordi.ballester@forgeflow.com) escribió:
    Dear contributors,

    We have a case of a database where some tables, like account.move.line are growing to absurd numbers of records. At this point we are considering using Postgresql Table partitioning to speed up performance. Has anyone of you had experience with table partitioning?

    Looking forward to hearing your thoughts. 

    Regards,
    --
    Jordi Ballester Alomar
    CEO & Founder | ForgeFlow

    _______________________________________________
    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 phone vauxoo.com/contactus  

    by Nhomar Hernández - 08:56 - 26 Feb 2021
  • Postgresql Table partitioning in Odoo
    Dear contributors,

    We have a case of a database where some tables, like account.move.line are growing to absurd numbers of records. At this point we are considering using Postgresql Table partitioning to speed up performance. Has anyone of you had experience with table partitioning?

    Looking forward to hearing your thoughts. 

    Regards,
    --
    Jordi Ballester Alomar
    CEO & Founder | ForgeFlow
    by Jordi Ballester Alomar - 08:16 - 26 Feb 2021
  • Re: Issues with Travis
    On Fri, Feb 26, 2021 at 9:23 AM Tom Blauwendraat <tom@sunflowerweb.nl> wrote:
    Beginner's question, but do the Docker containers then run on Github's servers (as a replacement of Travis' servers currently) or on OCA servers?

    They'd run on GitHub servers, although GitHub allows self hosted runners if we want to.
    Or, if the need arises again in the future, switch more easily to any another CI runner.

    -sbi

    by Stéphane Bidoul - 09:31 - 26 Feb 2021
  • Re: Issues with Travis


    Op 2/22/21 om 5:37 PM schreef Stéphane Bidoul:
    - docker images with Odoo pre-installed that are rebuilt nightly with the latest Odoo (inspired from the latest runbot Dockerfile template)
    - a minimalist GitHub action that orchestrates the thing (example a in Shopinvader repo)

    Beginner's question, but do the Docker containers then run on Github's servers (as a replacement of Travis' servers currently) or on OCA servers?

    Tom

    by Tom Blauwendraat - 09:26 - 26 Feb 2021
  • Re: Prevent accidental emails to external addresses
    Usually solved with training of email client. This could happen with Gmail or Outlook, thunderbird... Which is the difference? --> 

    I have an idea and is make like Gmail, it doesn't ask again to send the email but shoe you clearly the recipients.

    My proposal would be where Odoo says

    "Send to Followers"

    Replace with the name and email of the followers to make explicit visually ( like in de mobiles or webmail, or email's clients) to who is going to be delivered the email before pressing send!

    The next level (without pop-ups which no email client or any application I. The work do) could be to colour the "Send button" in red.

    As my first paragraph, I think this is because the followers are "hidden".

    My best!




    El jue., 25 feb. 2021 19:31, Daniel Reis <dreis@opensourceintegrators.com> escribió:
    Hello,

    A concern came up, about Odoo users accidentally send out email to external email addresses, such as customers or vendors.
    To goal is not the prevent this from happening, such as in a blacklist/whitelist feature, but to avoid that from happening accidentally.

    I'm not sure should looks like.
    One idea could be having a dialog box confirmation before posting a message mentioning an external user.
    Maybe we could external email from chatter messages, and only allow it from a Action menu send email option.

    On the OCA i've only found "mail_restrict_follower_selection" (https://github.com/OCA/social/tree/13.0/mail_restrict_follower_selection).
    But I'm not sure this is the solution I want to go to.
    At least it may not be enough on itself.


    Did some of you faced the same issue?
    Any thoughts, solutions, tips you can share?


    Thanks!

    --
    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 Rafael Blasco (Moduon) - 09:21 - 26 Feb 2021
  • Re: Prevent accidental emails to external addresses
    Hi Daniel,

    mail_optional_follower_notification and mail_footer_notified_partner could be interesting for you.

    -sbi


    On Thu, Feb 25, 2021 at 7:31 PM Daniel Reis <dreis@opensourceintegrators.com> wrote:
    Hello,

    A concern came up, about Odoo users accidentally send out email to external email addresses, such as customers or vendors.
    To goal is not the prevent this from happening, such as in a blacklist/whitelist feature, but to avoid that from happening accidentally.

    I'm not sure should looks like.
    One idea could be having a dialog box confirmation before posting a message mentioning an external user.
    Maybe we could external email from chatter messages, and only allow it from a Action menu send email option.

    On the OCA i've only found "mail_restrict_follower_selection" (https://github.com/OCA/social/tree/13.0/mail_restrict_follower_selection).
    But I'm not sure this is the solution I want to go to.
    At least it may not be enough on itself.


    Did some of you faced the same issue?
    Any thoughts, solutions, tips you can share?


    Thanks!

    --
    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 Stéphane Bidoul - 09:10 - 26 Feb 2021
  • Re: Prevent accidental emails to external addresses
    Dear Daniel
    We had another case here that is related to the odoo messaging system.
    It's not the same story but it has been critical as the person has been fired after that...
    An external recipient answered to an odoo email coming from a lead... as you know, with standard odoo, the external recipient do not see other external recipients (that are followers of the lead)... she did not see that her hr manager was follower of the lead and she wrote bad words on him...
    She was fired the day after...
    It was very hard for us to prouve that we were not responsible of the use of Odoo by the external partners of our customer...
    That's the reason why we consider mail_footer_notified_partner as mandatory and we wanted to have the notification in header instead of footer here :

    and by the way, we are very interested in your use case and the solution with the popup...

    Best regards

    Le jeu. 25 févr. 2021 à 19:57, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> a écrit :
    Hi Daniel,


    We face  the same problem here. I'm interested to follow up with you on this.

    I like the warning pop-up personality. 

    Joël 

    Le jeu. 25 févr. 2021 à 22:22, Quentin Lavallee <quentin.lavallee@numigi.com> a écrit :
    Hi Daniel,

    For similar concerns (in v12), we've used https://github.com/OCA/web/tree/12.0/web_send_message_popup.

    While not preventing external emails, it adds a visual step so the user realizes this is not an internal note. Note that there is a slight delay before the popup opens, but I find it totally usable nonetheless.

    Cheers,



    Le jeu. 25 févr. 2021 à 13:31, Daniel Reis <dreis@opensourceintegrators.com> a écrit :
    Hello,

    A concern came up, about Odoo users accidentally send out email to external email addresses, such as customers or vendors.
    To goal is not the prevent this from happening, such as in a blacklist/whitelist feature, but to avoid that from happening accidentally.

    I'm not sure should looks like.
    One idea could be having a dialog box confirmation before posting a message mentioning an external user.
    Maybe we could external email from chatter messages, and only allow it from a Action menu send email option.

    On the OCA i've only found "mail_restrict_follower_selection" (https://github.com/OCA/social/tree/13.0/mail_restrict_follower_selection).
    But I'm not sure this is the solution I want to go to.
    At least it may not be enough on itself.


    Did some of you faced the same issue?
    Any thoughts, solutions, tips you can share?


    Thanks!

    --
    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



    --
    Quentin Lavallee - Chargé de projets
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter

    _______________________________________________
    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 Cyril VINH-TUNG - 08:41 - 26 Feb 2021
  • Re: Issue with runbot 
    Hello Jay,

If you're referring to the 14.0 migration PR, nothing wrong on runbot. 
The PR is red on Travis because one view cannot be loaded -> fix this 
and runbot should get you a build. See 
https://github.com/OCA/vertical-hotel/pull/135#issuecomment-786464703

Or are you referring to something else ?

Alexandre

On 26/02/2021 07:52, Jay Vora wrote:

> Can you help with runbot on OCA/vertical-hotel ?

> Thanks.

> 

> On Thu, Feb 25, 2021 at 6:47 PM Alexandre Fayolle 

> <alexandre.fayolle@camptocamp.com 

> <mailto:alexandre.fayolle@camptocamp.com>> wrote:

> 

>     I forgot, this should be fixed since monday evening; please drop me an

>     email if it is not.

> 

>     Alexandre

> 

>     On 22/02/2021 15:51, Alexandre Fayolle wrote:

>     > Hello Enric,

>     > 

>     > Possibly a nginx issue. I'll check this tonight.

>     > 

>     > Alexandre

>     > 

>     > On 22/02/2021 11:47, Enric Tobella Alomar wrote:

>     >> Dear friends,

>     >> I have checked that sometimes, when accessing runbot, we are 

>     >> redirected to runbot main site and we are unable to access the runbot 

>     >> machine. After a little investigation, it seems related to runbot1-3 

>     >> as the main problem. It seems like a redirect is defined somewhere 

>     >> (maybe on nginx?).

>     >> I don't know if this happens to everyone.

>     >> Kind regards,

>     >> Enric Tobella Alomar

>     >> etobella@creublanca.es <mailto:etobella@creublanca.es>

>     >> Centros Médicos Creu Blanca

>     >> Tel: 902 202 230
 
>     >> 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.
>     >>
>     >>
>     >>
>     >>
>     >> 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
>     <https://odoo-community.org/groups/contributors-15>
>     >> <https://odoo-community.org/groups/contributors-15
>     <https://odoo-community.org/groups/contributors-15>>
>     >> Post to: mailto:contributors@odoo-community.org <mailto:contributors@odoo-community.org>
>     >> Unsubscribe: https://odoo-community.org/groups?unsubscribe
>     <https://odoo-community.org/groups?unsubscribe>
>     >> <https://odoo-community.org/groups?unsubscribe
>     <https://odoo-community.org/groups?unsubscribe>>
>     >>
>     > 
>     > 
> 
> 
>     -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20
>     30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le
>     Bourget-du-Lac France http://www.camptocamp.com
>     <http://www.camptocamp.com>
> 
>     _______________________________________________
>     Mailing-List: https://odoo-community.org/groups/contributors-15
>     <https://odoo-community.org/groups/contributors-15>
>     Post to: mailto:contributors@odoo-community.org
>     <mailto:contributors@odoo-community.org>
>     Unsubscribe: https://odoo-community.org/groups?unsubscribe
>     <https://odoo-community.org/groups?unsubscribe>
> 
> 
> 
> -- 
> SerpentCS Modules on Odoo AppStore 
> <https://www.odoo.com/apps/modules/browse?author=Serpent Consulting 
> Services Pvt. Ltd.>
> 
> The Splendid journey of 8 years 
> <https://www.youtube.com/watch?v=rue4vGQusbI>
> 
> Technology Services @ www.serpentcs.com <http://www.serpentcs.com/>
> Business Solutions @ www.serpentcs.in <http://www.serpentcs.in/>
> Enterprise Mobile Apps @ www.odooonline.com <http://www.odooonline.com/>
> Quality Assurance @ www.odooqa.com <http://www.odooqa.com/>
> SAP Hana @ www.prozone-tech.com <http://www.prozone-tech.com/>
> Portal & DMS @ www.alfray.in <http://www.alfray.in/>
> 
> 
> 
> Regards,
> ----------------------------------------------------------------------------------------------------------------------------
> <https://pbs.twimg.com/profile_images/472402041336119296/H1HdN-ST_400x400.jpeg>
> 
> 	
> Jay Vora
> Managing Director
> 
> 
> <http://in.linkedin.com/in/jaynvora>
> 
> 		
> Direct: +91-9879354457
> Office: +91-9033472982
> Skype: jaynvora
> Twitter : _jaynvora_
> 
> 	
> 
> -------------------------------------------------------------------------------------------------
> Visit our website : http://www.serpentcs.com <http://www.serpentcs.com>
> 	
> 
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 
> <https://odoo-community.org/groups/contributors-15>
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe 
> <https://odoo-community.org/groups?unsubscribe>
> 
-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
    by Alexandre Fayolle - 08:25 - 26 Feb 2021
  • Re: Issue with runbot
    Can you help with runbot on OCA/vertical-hotel ?
    Thanks.

    On Thu, Feb 25, 2021 at 6:47 PM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
    I forgot, this should be fixed since monday evening; please drop me an 
email if it is not.

Alexandre

On 22/02/2021 15:51, Alexandre Fayolle wrote:


> Hello Enric,


> 


> Possibly a nginx issue. I'll check this tonight.


> 


> Alexandre


> 


> On 22/02/2021 11:47, Enric Tobella Alomar wrote:


>> Dear friends,


>> I have checked that sometimes, when accessing runbot, we are 


>> redirected to runbot main site and we are unable to access the runbot 


>> machine. After a little investigation, it seems related to runbot1-3 


>> as the main problem. It seems like a redirect is defined somewhere 


>> (maybe on nginx?).


>> I don't know if this happens to everyone.


>> Kind regards,


>> Enric Tobella Alomar


>> etobella@creublanca.es


>> Centros Médicos Creu Blanca


>> Tel: 902 202 230


>> 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.


>>


>>


>>


>>


>> 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 


>> <https://odoo-community.org/groups/contributors-15>


>> Post to: mailto:contributors@odoo-community.org


>> Unsubscribe: https://odoo-community.org/groups?unsubscribe 


>> <https://odoo-community.org/groups?unsubscribe>


>>


> 


> 




-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com

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



    --

    Technology Services @ www.serpentcs.com
    Business Solutions @ www.serpentcs.in
    Enterprise Mobile Apps @ www.odooonline.com 
    Quality Assurance @ www.odooqa.com
    Portal & DMS @ www.alfray.in



    Regards,
    ----------------------------------------------------------------------------------------------------------------------------
    Jay Vora
    Managing Director


    		 
    Direct: +91-9879354457
    Office: +91-9033472982
    Skype: jaynvora
    Twitter : jaynvora
     
       
    -------------------------------------------------------------------------------------------------
    Visit our website : http://www.serpentcs.com
     
    by Jay Vora - 07:51 - 26 Feb 2021
  • Re: Prevent accidental emails to external addresses
    Hi Daniel,


    We face  the same problem here. I'm interested to follow up with you on this.

    I like the warning pop-up personality. 

    Joël 

    Le jeu. 25 févr. 2021 à 22:22, Quentin Lavallee <quentin.lavallee@numigi.com> a écrit :
    Hi Daniel,

    For similar concerns (in v12), we've used https://github.com/OCA/web/tree/12.0/web_send_message_popup.

    While not preventing external emails, it adds a visual step so the user realizes this is not an internal note. Note that there is a slight delay before the popup opens, but I find it totally usable nonetheless.

    Cheers,



    Le jeu. 25 févr. 2021 à 13:31, Daniel Reis <dreis@opensourceintegrators.com> a écrit :
    Hello,

    A concern came up, about Odoo users accidentally send out email to external email addresses, such as customers or vendors.
    To goal is not the prevent this from happening, such as in a blacklist/whitelist feature, but to avoid that from happening accidentally.

    I'm not sure should looks like.
    One idea could be having a dialog box confirmation before posting a message mentioning an external user.
    Maybe we could external email from chatter messages, and only allow it from a Action menu send email option.

    On the OCA i've only found "mail_restrict_follower_selection" (https://github.com/OCA/social/tree/13.0/mail_restrict_follower_selection).
    But I'm not sure this is the solution I want to go to.
    At least it may not be enough on itself.


    Did some of you faced the same issue?
    Any thoughts, solutions, tips you can share?


    Thanks!

    --
    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



    --
    Quentin Lavallee - Chargé de projets
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter

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

    by Joël Grand Guillaume - 06:56 - 26 Feb 2021
  • Re: Prevent accidental emails to external addresses
    Hi Daniel,

    For similar concerns (in v12), we've used https://github.com/OCA/web/tree/12.0/web_send_message_popup.

    While not preventing external emails, it adds a visual step so the user realizes this is not an internal note. Note that there is a slight delay before the popup opens, but I find it totally usable nonetheless.

    Cheers,



    Le jeu. 25 févr. 2021 à 13:31, Daniel Reis <dreis@opensourceintegrators.com> a écrit :
    Hello,

    A concern came up, about Odoo users accidentally send out email to external email addresses, such as customers or vendors.
    To goal is not the prevent this from happening, such as in a blacklist/whitelist feature, but to avoid that from happening accidentally.

    I'm not sure should looks like.
    One idea could be having a dialog box confirmation before posting a message mentioning an external user.
    Maybe we could external email from chatter messages, and only allow it from a Action menu send email option.

    On the OCA i've only found "mail_restrict_follower_selection" (https://github.com/OCA/social/tree/13.0/mail_restrict_follower_selection).
    But I'm not sure this is the solution I want to go to.
    At least it may not be enough on itself.


    Did some of you faced the same issue?
    Any thoughts, solutions, tips you can share?


    Thanks!

    --
    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



    --
    Quentin Lavallee - Chargé de projets
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter
    by Quentin Lavallée-Bourdeau - 10:21 - 25 Feb 2021
  • Prevent accidental emails to external addresses
    Hello,

    A concern came up, about Odoo users accidentally send out email to external email addresses, such as customers or vendors.
    To goal is not the prevent this from happening, such as in a blacklist/whitelist feature, but to avoid that from happening accidentally.

    I'm not sure should looks like.
    One idea could be having a dialog box confirmation before posting a message mentioning an external user.
    Maybe we could external email from chatter messages, and only allow it from a Action menu send email option.

    On the OCA i've only found "mail_restrict_follower_selection" (https://github.com/OCA/social/tree/13.0/mail_restrict_follower_selection).
    But I'm not sure this is the solution I want to go to.
    At least it may not be enough on itself.


    Did some of you faced the same issue?
    Any thoughts, solutions, tips you can share?


    Thanks!

    --
    Daniel Reis
    Managing Director
    M: +351 919991307
    E: DReis@OpenSourceIntegrators.com
    Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal


    by Daniel Reis - 07:31 - 25 Feb 2021
  • Re: Issue with runbot 
    I forgot, this should be fixed since monday evening; please drop me an 
email if it is not.

Alexandre

On 22/02/2021 15:51, Alexandre Fayolle wrote:

> Hello Enric,

> 

> Possibly a nginx issue. I'll check this tonight.

> 

> Alexandre

> 

> On 22/02/2021 11:47, Enric Tobella Alomar wrote:

>> Dear friends,

>> I have checked that sometimes, when accessing runbot, we are 

>> redirected to runbot main site and we are unable to access the runbot 

>> machine. After a little investigation, it seems related to runbot1-3 

>> as the main problem. It seems like a redirect is defined somewhere 

>> (maybe on nginx?).

>> I don't know if this happens to everyone.

>> Kind regards,

>> Enric Tobella Alomar

>> etobella@creublanca.es

>> Centros Médicos Creu Blanca

>> Tel: 902 202 230

>> 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.

>>

>>

>>

>>

>> 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 

>> <https://odoo-community.org/groups/contributors-15>

>> Post to: mailto:contributors@odoo-community.org

>> Unsubscribe: https://odoo-community.org/groups?unsubscribe 

>> <https://odoo-community.org/groups?unsubscribe>

>>

> 

> 



-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
    by Alexandre Fayolle - 02:16 - 25 Feb 2021
  • Re: Convert quantity from an UoM to another one
    Thanks for your insight, I think this is noticeably different 🤔

    Le mer. 24 févr. 2021 à 16:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    Check product_secondary_unit and the rest of the family.

    Regards.

    El mié., 24 feb. 2021 16:02, Pierre Verkest <pierreverkest84@gmail.com> escribió:
    I'd like to propose a new module in product-attribute repo to convert from an UoM to another one, I would suggest "base_uom_converter" or "uom_converter".

    This conversion would work in oneway as it requires a scale to use it.

    For instance, as a developer, I'm generating sales orders from business code. I know that the sale is regarding a given distance of something "D", the work force can be translated from a scale where distance "D" would be the scale entry. The expected result "R" would be the amount of time with a given formula:
    R (hours) = scale line fix amount (hours)  + D (meter) * scale line coef ( hours / meter).

    I guess this could be hooked to the existing system while we change the uom on a sale order line but this is not the intent of this module from my point of view, that's why I suggest base_uom_converter !

    Does this exist already ? Does the OCA want to maintain such a module ?
    --
    Pierre Verkest
    06 81 12 25 20
    Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest

    _______________________________________________
    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



    --
    Pierre
    by Pierre Verkest - 05:46 - 24 Feb 2021
  • Re: Header sorting in form view
    Just a PR, thanks

    David




    Le mer. 24 févr. 2021 à 17:22, Yann Papouin <y.papouin@dec-industrie.com> a écrit :
    Is there a procedure somewhere ? or just make a pull request ?

    --
    Yann PAPOUIN, Ingénieur R&D | DEC


    Le mer. 24 févr. 2021 à 09:10, David Beal <david.beal@akretion.com> a écrit :
    Thanks Yann,

    Probably a good addition in oca repo ?



    Le mar. 23 févr. 2021 à 23:36, Yann Papouin <y.papouin@dec-industrie.com> a écrit :
    For the record:

    Values are kept locally until a full reload.
    The user orderedBy is stored in a dictionary where the primary key is model,res_id and the secondary key is the field name.

    --
    Yann PAPOUIN, Ingénieur R&D | DEC


    Le lun. 11 janv. 2021 à 11:06, Yann Papouin <y.papouin@dec-industrie.com> a écrit :
    Dear community,

    I'm looking for an addon or a way to keep user sorting choices.

    As you know, you can click on a One2Many or Many2Many header (of a stored field) to sort the lines but any action in the form (validate something or encoding quantities, etc.) reload it and reset the user sort.

    I don't have a great JS expertise that's why I'm asking here before starting to work on a new module/hook dedicated to this feature.

    Thank you.
    --
    Yann Papouin

    _______________________________________________
    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 David BEAL - 05:36 - 24 Feb 2021