Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Info Server VPS 
    Ciao Lorenzo,
come da comunicazione con Fabrizio, faccio un elendo dei task da
completare ed il relativo costo.

- creazione server virtuale 15 EUR
- installazione e configurazione backend 25 EUR
	* tomcat
	* php-fpm
	* postgresql
	* mariadb (mysql)

- Installazione Wordpress e wp-cli 15 EUR
- Installazione e configurazione letsencrypt 15 EUR
- Migrazione sito web Wordpress 25 EUR
- Migrazione applicazione in Java 25 EUR
- Migrazione DNS e SSL per il dominio booking 25 EUR
- Migrazione DNS e SSL per il sito web wordpress 25 EUR
- Creazione soluzione di backup in gdrive 75 EUR
- Migrazione database (postgresql, e mysql) 30 EUR
- Backup una tantum 25 EUR

In totale 300 EUR

Per il backup di postgres ci pensa Fabrizio, per il sito web avete
bisogno di backup?

Inoltre per la quota mensile posso fare 120 EUR con pagamento
anticipato trimestrale che include assistenza e monitoring, manutenzione
e aggiornamento del server con test di ripristino backup mensile.

Inoltre c'è un servizio opzionale di hardening del server, per la messa
in sicurezza.

Attendo tue,
Salvatore De Paolis
    by Salvatore - 06:55 - 14 Nov 2023
  • Re: intercompany transfer

    Il giorno mar 14 nov 2023 alle ore 15:32 Samir Hassan <notifications@odoo-community.org> ha scritto:
    dear all

    i have issue with inter company 
    i have to companies A&B
    both company sell and purchase from them
    when make this process between them i have in inventory tow delivery order or tow Receipts for one sales order or purchase 
    please i need help to solve it

    --
    Best Regards
    Samir Mahmoud
    00201062648111


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



    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790
    by Francesco Foresti - 03:51 - 14 Nov 2023
  • intercompany transfer
    dear all

    i have issue with inter company 
    i have to companies A&B
    both company sell and purchase from them
    when make this process between them i have in inventory tow delivery order or tow Receipts for one sales order or purchase 
    please i need help to solve it

    --
    Best Regards
    Samir Mahmoud
    00201062648111


    by Samir Mahmoud Hassan - 03:30 - 14 Nov 2023
  • Re: Expression of Interest in Becoming Maintainer for l10n-switzerland Repository
    Hello Emanuel,

    +1 for your application

    I will gladly welcome you as a PSC member.
    Most of the historical modules that Camptocamp helped to maintain have been included or replicated in the core thus becoming obsolete. Thus, for the latest versions there has been very few activitiy.

    To synchronize it's important to keep the "Migration to XX" github issues up to date:

    All the best,
    Yannick

    On Mon, 13 Nov 2023 at 12:29, Emanuel Cino <notifications@odoo-community.org> wrote:
    Dear community,

    I hope this email finds you well. My name is Emanuel, and I am writing to express my interest in the l10n-switzerland repository. I recently noticed that the repository appears to be inactive, and as someone passionate about its purpose, I am eager to contribute to its revitalization.

    I am writing to inquire about the current maintainers of the l10n-switzerland repository and to express my willingness to take on a role as a maintainer. The project's objectives align closely with my interests and skills, and I believe that by actively participating in its development, we can work together to ensure its continued growth and success.

    I have successfully contributed to various OCA repositories in the past, and I am committed to dedicating time and effort to this project to help bring it back to life.

    If the opportunity to become a maintainer is available, I would appreciate any guidance on the steps I need to ta ke or the process involved.

    Thank you for considering my request, and I look forward to your guidance on how I can assist in reviving this valuable open-source initiative.

    Best regards,

    Compassion Switzerland

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

    by Yannick Payot - 03:00 - 14 Nov 2023
  • Re: 17.0 branches
    Thanks a lot Stéphane for all these evolutions.

    Some of them have a really good impact on the environment, double thanks for that.

    David BEAL
    Consultant ERP Odoo


    Le lun. 13 nov. 2023 à 15:52, Juan José Scarafía <notifications@odoo-community.org> a écrit :
    Great, thanks!

    Ing. Juan José Scarafía

    (+54 9 341) 3 278039

    twitter: @jjscarafia

    github: @jjscarafia



    El dom, 12 nov 2023 a la(s) 13:25, Stéphane Bidoul (notifications@odoo-community.org) escribió:
    Hi everyone,

    The 17.0 branches are being created in all OCA repos as I'm writing this.

    There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

    • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
    • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
    • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
    • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
    The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

    In case of problem, let us know of any problem by creating an issue in the repo template project [3]

    Best regards,

    [1] https://docs.astral.sh/ruff/rules/

    --
    Stéphane Bidoul
    http://acsone.eu/

    _______________________________________________
    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 - 07:25 - 13 Nov 2023
  • Re: 17.0 branches
    Great, thanks!

    Ing. Juan José Scarafía

    (+54 9 341) 3 278039

    twitter: @jjscarafia

    github: @jjscarafia



    El dom, 12 nov 2023 a la(s) 13:25, Stéphane Bidoul (notifications@odoo-community.org) escribió:
    Hi everyone,

    The 17.0 branches are being created in all OCA repos as I'm writing this.

    There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

    • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
    • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
    • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
    • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
    The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

    In case of problem, let us know of any problem by creating an issue in the repo template project [3]

    Best regards,

    [1] https://docs.astral.sh/ruff/rules/

    --
    Stéphane Bidoul
    http://acsone.eu/

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

    by Juan José Scarafía - 03:51 - 13 Nov 2023
  • Re: 17.0 branches
    It can be decided per branch answering the copier question.

    Regards.
    by Pedro M. Baeza - 03:36 - 13 Nov 2023
  • Re: 17.0 branches
    Will Ruff also be used on earlier branches or will it only be used for 17.0+?

    Il giorno dom 12 nov 2023 alle ore 17:25 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:
    Hi everyone,

    The 17.0 branches are being created in all OCA repos as I'm writing this.

    There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

    • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
    • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
    • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
    • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
    The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

    In case of problem, let us know of any problem by creating an issue in the repo template project [3]

    Best regards,

    [1] https://docs.astral.sh/ruff/rules/

    --
    Stéphane Bidoul
    http://acsone.eu/

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



    --

    Francesco Apruzzese

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

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

    Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
    by Francesco Apruzzese - 03:31 - 13 Nov 2023
  • Re: 17.0 branches
    Thanks Stéphane

    On Sun, Nov 12, 2023 at 7:55 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:
    Hi everyone,

    The 17.0 branches are being created in all OCA repos as I'm writing this.

    There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

    • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
    • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
    • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
    • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
    The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

    In case of problem, let us know of any problem by creating an issue in the repo template project [3]

    Best regards,

    [1] https://docs.astral.sh/ruff/rules/

    --
    Stéphane Bidoul
    http://acsone.eu/

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

    by Mostafa Barmshory - 03:28 - 13 Nov 2023
  • Expression of Interest in Becoming Maintainer for l10n-switzerland Repository
    Dear community,

    I hope this email finds you well. My name is Emanuel, and I am writing to express my interest in the l10n-switzerland repository. I recently noticed that the repository appears to be inactive, and as someone passionate about its purpose, I am eager to contribute to its revitalization.

    I am writing to inquire about the current maintainers of the l10n-switzerland repository and to express my willingness to take on a role as a maintainer. The project's objectives align closely with my interests and skills, and I believe that by actively participating in its development, we can work together to ensure its continued growth and success.

    I have successfully contributed to various OCA repositories in the past, and I am committed to dedicating time and effort to this project to help bring it back to life.

    If the opportunity to become a maintainer is available, I would appreciate any guidance on the steps I need to take or the process involved.

    Thank you for considering my request, and I look forward to your guidance on how I can assist in reviving this valuable open-source initiative.

    Best regards,

    Compassion Switzerland
    by "Emanuel Cino" <emanuel@compassion.ch> - 12:29 - 13 Nov 2023
  • RE: Ledger for the individual related to a company

    Dear,

     

    You have to create a partner for you customer as an individual and create your sales order and invoice on this partner and not on the company with the person as a contact. Of course, when the order / invoice is recorded on the company, it is in the company ledger. The contact person is there only as extra information. When the order is intended for the private person and has to be paid by this person, you must assign this private person as the partner.

     

    With kind regards,

     

    Van Hirtum Johan

     

    Van: Ahmed Ragab [mailto:notifications@odoo-community.org]
    Verzonden: vrijdag 10 november 2023 22:02
    Aan: Contributors
    Onderwerp: Ledger for the individual related to a company

     

    Hi 

     

    If the customer is an individual without a related company, I would find the entries in the partner ledger. the same if it is a company.

    But if the customer is an individual (or a contact) related to a company, all records appear only in the partner ledger of the company itself but the individual contact ledger will be empty

     

    Is there an OCA module that shows whose contact this amount is for? in the partner ledger ?

    I mean a module that makes the entry appear in the contact-partner also, if he is chosen while invoicing or while creating a payment.

     

    Thanks alot

     

     

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

    by johan - 09:36 - 13 Nov 2023
  • Re: 17.0 branches
    Thanks! 🙏 
     
    Von: Stéphane Bidoul <notifications@odoo-community.org>
    Gesendet: Sonntag, November 12, 2023 5:25 PM
    An: Contributors <contributors@odoo-community.org>
    Betreff: 17.0 branches
     
    Hi everyone,

    The 17.0 branches are being created in all OCA repos as I'm writing this.

    There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

    • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
    • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
    • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
    • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
    The migration issues had been created last week Don't forget to announce yourself when you start migrating a module.

    In case of problem, let us know of any problem by creating an issue in the repo template project [3]

    Best regards,

    [1] https://docs.astral.sh/ruff/rules/

    --
    Stéphane Bidoul
    http://acsone.eu/

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

    by Nils Coenen - 09:10 - 13 Nov 2023
  • Re: 17.0 branches
    Thanks a lot, Stéphane!

    On Sun, Nov 12, 2023 at 5:25 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:
    Hi everyone,

    The 17.0 branches are being created in all OCA repos as I'm writing this.

    There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

    • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
    • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
    • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
    • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
    The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

    In case of problem, let us know of any problem by creating an issue in the repo template project [3]

    Best regards,

    [1] https://docs.astral.sh/ruff/rules/

    --
    Stéphane Bidoul
    http://acsone.eu/

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



    --
    by Alex Comba. - 09:01 - 13 Nov 2023
  • Re: 17.0 branches
    Thanks Stéphane for the amazing job.

    El lun, 13 nov 2023 a las 8:12, Pedro M. Baeza (<notifications@odoo-community.org>) escribió:
    Thanks!

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



    --
    Enric Tobella Alomar
    CEO & Founder

    by Enric Tobella Alomar - 08:15 - 13 Nov 2023
  • Re: 17.0 branches
    Thanks!
    by Pedro M. Baeza - 08:10 - 13 Nov 2023
  • Re: 17.0 branches
    Thank you Stéphane!

    El dom., 12 nov. 2023 17:25, Stéphane Bidoul <notifications@odoo-community.org> escribió:
    Hi everyone,

    The 17.0 branches are being created in all OCA repos as I'm writing this.

    There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

    • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
    • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
    • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
    • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
    The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

    In case of problem, let us know of any problem by creating an issue in the repo template project [3]

    Best regards,

    [1] https://docs.astral.sh/ruff/rules/

    --
    Stéphane Bidoul
    http://acsone.eu/

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

    by Jordi Ballester Alomar - 06:30 - 13 Nov 2023
  • 17.0 branches
    Hi everyone,

    The 17.0 branches are being created in all OCA repos as I'm writing this.

    There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

    • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
    • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
    • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
    • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
    The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

    In case of problem, let us know of any problem by creating an issue in the repo template project [3]

    Best regards,

    [1] https://docs.astral.sh/ruff/rules/

    --
    Stéphane Bidoul
    http://acsone.eu/

    by Stéphane Bidoul - 04:18 - 12 Nov 2023
  • Ledger for the individual related to a company
    Hi 

    If the customer is an individual without a related company, I would find the entries in the partner ledger. the same if it is a company.
    But if the customer is an individual (or a contact) related to a company, all records appear only in the partner ledger of the company itself but the individual contact ledger will be empty

    Is there an OCA module that shows whose contact this amount is for? in the partner ledger ?
    I mean a module that makes the entry appear in the contact-partner also, if he is chosen while invoicing or while creating a payment.

    Thanks alot


    by Ahmed - 10:01 - 10 Nov 2023
  • Re: Looking for a module
    Thanks Denis, 

    we've found https://github.com/OCA/sale-workflow/tree/14.0/sale_partner_shipping_invoice_domain that seems to do what's requested (and opened a PR to fix readme here: https://github.com/OCA/sale-workflow/pull/2771 )

    Cheers

    Francesco

    Il giorno ven 10 nov 2023 alle ore 11:32 Roussel, Denis <notifications@odoo-community.org> ha scritto:
    Hi Francesco,


    An extension should maybe done.

    On Fri, Nov 10, 2023 at 11:02 AM Francesco Foresti <notifications@odoo-community.org> wrote:
    Hi, 

    use case: in SO field "Delivery Address" user can select only contacts related to partner set in "Customer".

    is there a module doing this to your knowledge?

    Thanks!

    Francesco

    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790

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



    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone 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



    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790
    by Francesco Foresti - 12:01 - 10 Nov 2023
  • Re: Looking for a module
    Hi Francesco,


    An extension should maybe done.

    On Fri, Nov 10, 2023 at 11:02 AM Francesco Foresti <notifications@odoo-community.org> wrote:
    Hi, 

    use case: in SO field "Delivery Address" user can select only contacts related to partner set in "Customer".

    is there a module doing this to your knowledge?

    Thanks!

    Francesco

    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790

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



    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg
    by Denis Roussel - 11:32 - 10 Nov 2023