Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Re: Module to bulk select products to Transfer

    On Thu, Feb 23, 2023 at 10:52 AM Daniel Reis <notifications@odoo-community.org> wrote:
    Hello,

    I wonder if someone worked on a similar need:

    We are doing stock internal transfers, and would like to be able to select all the contents of the source location to the picking lines.
    A use case is where the Source Location is a Truck, and you want to unload (transfer) the content of the truck to another location.
    My target version is v16.


    Thank you
    Daniel

    _______________________________________________
    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 - 10:56 - 23 Feb 2023
  • Module to bulk select products to Transfer
    Hello,

    I wonder if someone worked on a similar need:

    We are doing stock internal transfers, and would like to be able to select all the contents of the source location to the picking lines.
    A use case is where the Source Location is a Truck, and you want to unload (transfer) the content of the truck to another location.
    My target version is v16.


    Thank you
    Daniel
    by Daniel Reis - 10:50 - 23 Feb 2023
  • Re: write access to repositories for oca-git-bot
    I'm afraid it's not anything about checking that field or not, but GitHub avoids the push to organization branches. We don't know the reason, but there's nothing in our hands that we can do about that.

    But the good news is that the `/ocabot merge ...` command performs a rebase on the merge branch.

    Regards.
    by Pedro M. Baeza - 08:20 - 23 Feb 2023
  • Re: OCA Contract Repository
    Hello! Thanks for your response Denis. I Just go back from vacation so I think next week I will start working on contract module.

    > In fact, the state is managed on line level, see https://github.com/OCA/contract/blob/14.0/contract/models/contract_line.py#L94

    Okay so, if state is managed in line level, will it make sense to make a computed contract level state that is based on line state? Because I think that for the user, they will expect contract to have a state, even some lines have different states we can make some logic to compute a state based on all lines states. Something like: 

    States: “active”, “canceled”, “closed” can be computed based on lines. “Active” can be the contract state when at least one line is active, “Canceled” when all lines are canceled and “closed” when all lines closed. If we have mixed situations like some lines canceled and some active, we can still show active. 

    This will allow the user to easily filter contracts without having to enter each contract to see lines. Or maybe we have to make a contract lines view. 

    Next week I will be with this project and open some PRs to see what people think, also make the view improvements that will make sure life easier. 

    And yes, base_conteact was just an idea but the point is to have more smaller and maintainable modules that plug-in functionalities, that’s always the easiest way to have a user-specific implementation without having a lot of functionalities that won’t be user by all users. Will try to open the issue next week to discuss this and also review the link between agreements and contracts PR. 

    Please if another people have more ideas/problems/suggestions to contract module, feel free to reply this thread. 

    Regards and good week for all of you! 



    El El mié, 15 de feb. de 2023 a la(s) 06:17, Roussel, Denis <notifications@odoo-community.org> escribió:
    > - Contract objects don’t have states. It appears to me that in some versions states existed but is a functionality that was dropped and some point. I strongly think that a module like this must have states.


    >  I think the name of the contract should be computed, or at least use a sequence. I don’t see the point of the name to be manually edited. Having a computed one will help with search and filtering. 

    Indeed, this can be improved.

    > - There is not grouping entity of contract objects. Meaning we don't have an easy way to group contracts by category or an hicherarchical structure. I think this is useful for usability and to set default parameters. 

    Maybe adding a 'contract.category' model could be great (in another module ?). But, for the time being, this can be done through contract tags. See: https://github.com/OCA/contract/blob/14.0/contract/models/contract.py#L110

    > - There is not link between contracts and agreement modules. My common sense dict that a contract should be created from an agreement, meaning that an agreement is a legal contract and when approved and signed, it creates a contract record which defines invoicing schedule. If not, i really don't see any use for agreements if they are not linked. Maybe this can be solved with a new module. 

    This is still tested in a draft PR: https://github.com/OCA/contract/pull/649 You can review it and make suggestions.

    > - I think all codebase should be refactored and maybe split the contract module to have one base_contract with basic functionality for simple cases and then other modules to plug-in more functionality. 

    This module has indeed a big history, refactored on 12.0 version I think. Since, some improvements have been done (refactoring on recurrency computations by Pedro see: https://github.com/OCA/contract/pull/533/commits/cd086ddbb4a9b85ccfcac288e53fb93e716d9446)

    Indeed, I think it has now a very complex implementation that makes user understanding (and debugging) difficult.

    We could make an issue on the github repository to help gathering ideas and focus discussion there than on this mailing list. But I agree that we could split some logic in separate modules (with meaningful names - if we could avoid base_contract).

    I hope this answered your questions.


    Regards,


    On Fri, Feb 10, 2023 at 5:57 PM Nicolas Rodriguez Sande <notifications@odoo-community.org> wrote:

    Hello, I’m writing to know your opinion about the contract repository. I started to use the modules in the repository and noted that the module versions of contract module differ a lot between odoo versions. 


    I have to do some implementations regarding that modules so I’m going to start making PRs to that repo and try to improve the modules starting in version 14.0 and then port it to the others. 

    I want to have your opinions on things you can tell me about what is missing in the modules and so I can organize my roadmap. Also, I don’t know if there are currently active PSC of the module, if not or you want me to join the team I will be interested, because I need to improve the modules and if that can help the development of the repo, count with me. 

    From what I saw, I see the following issues to solve, please if you know another issues or want to make an opinion of changes you would like to see in the module please comment me here: 

    - Contract objects don’t have states. It appears to me that in some versions states existed but is a functionality that was dropped and some point. I strongly think that a module like this must have states.

    - I think the name of the contract should be computed, or at least use a sequence. I don’t see the point of the name to be manually edited. Having a computed one will help with search and filtering. 

    - There is not grouping entity of contract objects. Meaning we don't have an easy way to group contracts by category or an hicherarchical structure. I think this is useful for usability and to set default parameters. 

    - There is not link between contracts and agreement modules. My common sense dict that a contract should be created from an agreement, meaning that an agreement is a legal contract and when approved and signed, it creates a contract record which defines invoicing schedule. If not, i really don't see any use for agreements if they are not linked. Maybe this can be solved with a new module. 

    - Contract views are awful and need to be improved to favor user usability and comprehension of the module mechanics and uses. This is one of the first changes i want to introduce. 

    - Contract reports and portal views need to be improved. Currently the contract report is not so much developed. Also could be a good idea to allow to see agreements from portal contracts. 

    - I think all codebase should be refactored and maybe split the contract module to have one base_contract with basic functionality for simple cases and then other modules to plug-in more functionality. 

    If you have more opinions and things you want to see in a roadmap, please tell me here and i can maybe add it to my next PRs. Also if you have opinions of how the module should work will be great for when we refactor it. 

    Regards and i want for your thoughts. 

    _______________________________________________
    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


    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

    by Nicolas Rodriguez Sande - 01:51 - 23 Feb 2023
  • Re: write access to repositories for oca-git-bot
    Yes the access is denied because the option o allow or not maintainers to push to PRs branch. 

    Anyways, the allow maintainers to push to the branch option is enabled by default and a lot of people leave it enabled, so the rebase command continue being useful for those cases. 

    Maybe a solution for this is to create a new command on the push level, like: 

    /ocabot merge patch —rebase 

    So the bot can rebase the PR when creating the merge branch so it don’t need access to PR repository. What do you think? 

    El El mié, 22 de feb. de 2023 a la(s) 08:06, Stéphane Bidoul <notifications@odoo-community.org> escribió:
    Hi Hugues,

    Last time I checked it was not possible for organizations to allow maintainers to push to their PRs. It was only possible for individual contributors.

    So this effectively limits the usefulness of the /ocabot rebase command.

    Best regards,

    -sbi


    On Wed, Feb 22, 2023 at 11:57 AM hugues de keyzer <notifications@odoo-community.org> wrote:

    hello,

    maybe this is documented somewhere but i could not find the information.

    for the /ocabot rebase command to work, oca-git-bot needs write access to the repository that contains the branch. without it, it fails like this:

    The rebase process failed, because command git push --force coopiteasy tmp-pr-40:12.0-cooperator_website_add_validation_hook failed with output: 

    remote: Permission to coopiteasy/cooperative.git denied to OCA-git-bot.
fatal: unable to access 'https://github.com/coopiteasy/cooperative/': The requested URL returned error: 403

    how is this supposed to be handled? should oca-git-bot be part of our github organization? i invited it, thinking that maybe it auto-accepts invites, but nothing changed.

    what should i do?

    cheers,

    hugues
    coop it easy

    _______________________________________________
    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 Nicolas Rodriguez Sande - 01:36 - 23 Feb 2023
  • Re: Odoo calendar <-> outlook calendar sync 
    I think this issue was fixed last week in 
https://github.com/odoo/odoo/commit/86862f2527341247b75df155de16b09d44a7eee6

Alexandre

On 22/02/2023 14:32, Simon Pessemesse wrote:

> Hello,

> We have a customer using native odoo synchronization between outlook calendar

> and odoo calendar.

> 

> But since 2 month, the following warning has be added to the odoo documentation

> <https://www.odoo.com/documentation/15.0/applications/general/calendars/outlook/outlook_calendar.html?highlight=outlook>

>        Warning

> 

>        Odoo highly recommends testing the Outlook calendar synchronization

>        on a test database and a test email address (that is not used for

>        any other purpose) before attempting to sync the desired Outlook

>        Calendar with the user’s production database.

>        If the user has any past, present, or future events on their Odoo

>        calendar before syncing their Outlook calendar, Outlook will treat

>        the events pulled from Odoo’s calendar during the sync as new

>        events, causing an email notification to be sent from Outlook to all

>        the event attendees.

>        To avoid unwanted emails being sent to all past, present, and future

>        event attendees, the user must add the events from the Odoo calendar

>        to the Outlook calendar before the first ever sync, delete the

>        events from Odoo, and then start the sync.

>        Even after synchronizing the Odoo Calendar with the Outlook

>        calendar, Outlook will still send a notification to all event

>        participants every time an event is edited (created, deleted,

>        unarchived, or event date/time changed), with no exceptions. This is

>        a limitation that cannot be fixed from Odoo’s side.

>        After one user syncs their Outlook calendar to the Odoo database,

>        unwanted email notifications are unavoidable because the first

>        synchronized user’s events will be in the Odoo Calendar. If the Odoo

>        database is shared amongst multiple users, and another user wants to

>        sync their Outlook calendar with Odoo Calendar, Outlook will again

>        pull the existing Odoo Calendar events during the sync and treat

>        them as new events, causing Outlook to send email invitations to all

>        event attendees.

> 

>        In summary, once a user synchronizes their Outlook calendar with the

>        Odoo calendar:

>            Creating an event in Odoo causes Outlook to send an invitation

>            to all event attendees.

>            Deleting an event in Odoo causes Outlook to send a cancellation

>            to all event attendees.

>            Unarchiving an event in Odoo causes Outlook to send an

>            invitation to all event attendees.

>            Archiving an event in Odoo causes Outlook to send a cancellation

>            to all event attendees.

>            Adding a contact to an event causes Outlook to send an

>            invitation to all event attendees.

>            Removing a contact from an event causes Outlook to send a

>            cancellation to all event attendees.

> 

> And indeed, the synchronization has became unusable because of all the

> invitations sent to all event attendees in outlook.

> 

> Odoo doesn't seem to address the problem, do you know any module that would work

> properly to sync the calendars?

> 

> Regards

> Simon

> 

> -- 

> 

> _______________________________________________

> 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:40 - 22 Feb 2023
  • Odoo calendar <-> outlook calendar sync 
    Hello,
We have a customer using native odoo synchronization between outlook calendar
and odoo calendar.

But since 2 month, the following warning has be added to the odoo documentation
<https://www.odoo.com/documentation/15.0/applications/general/calendars/outlook/outlook_calendar.html?highlight=outlook>
      Warning

      Odoo highly recommends testing the Outlook calendar synchronization
      on a test database and a test email address (that is not used for
      any other purpose) before attempting to sync the desired Outlook
      Calendar with the user’s production database.
      If the user has any past, present, or future events on their Odoo
      calendar before syncing their Outlook calendar, Outlook will treat
      the events pulled from Odoo’s calendar during the sync as new
      events, causing an email notification to be sent from Outlook to all
      the event attendees.
      To avoid unwanted emails being sent to all past, present, and future
      event attendees, the user must add the events from the Odoo calendar
      to the Outlook calendar before the first ever sync, delete the
      events from Odoo, and then start the sync.
      Even after synchronizing the Odoo Calendar with the Outlook
      calendar, Outlook will still send a notification to all event
      participants every time an event is edited (created, deleted,
      unarchived, or event date/time changed), with no exceptions. This is
      a limitation that cannot be fixed from Odoo’s side.
      After one user syncs their Outlook calendar to the Odoo database,
      unwanted email notifications are unavoidable because the first
      synchronized user’s events will be in the Odoo Calendar. If the Odoo
      database is shared amongst multiple users, and another user wants to
      sync their Outlook calendar with Odoo Calendar, Outlook will again
      pull the existing Odoo Calendar events during the sync and treat
      them as new events, causing Outlook to send email invitations to all
      event attendees.

      In summary, once a user synchronizes their Outlook calendar with the
      Odoo calendar:
          Creating an event in Odoo causes Outlook to send an invitation
          to all event attendees.
          Deleting an event in Odoo causes Outlook to send a cancellation
          to all event attendees.
          Unarchiving an event in Odoo causes Outlook to send an
          invitation to all event attendees.
          Archiving an event in Odoo causes Outlook to send a cancellation
          to all event attendees.
          Adding a contact to an event causes Outlook to send an
          invitation to all event attendees.
          Removing a contact from an event causes Outlook to send a
          cancellation to all event attendees.

And indeed, the synchronization has became unusable because of all the
invitations sent to all event attendees in outlook.

Odoo doesn't seem to address the problem, do you know any module that would work
properly to sync the calendars?

Regards
Simon


--
    by simon - 02:31 - 22 Feb 2023
  • Re: write access to repositories for oca-git-bot
    Hi Hugues,

    Last time I checked it was not possible for organizations to allow maintainers to push to their PRs. It was only possible for individual contributors.

    So this effectively limits the usefulness of the /ocabot rebase command.

    Best regards,

    -sbi


    On Wed, Feb 22, 2023 at 11:57 AM hugues de keyzer <notifications@odoo-community.org> wrote:

    hello,

    maybe this is documented somewhere but i could not find the information.

    for the /ocabot rebase command to work, oca-git-bot needs write access to the repository that contains the branch. without it, it fails like this:

    The rebase process failed, because command git push --force coopiteasy tmp-pr-40:12.0-cooperator_website_add_validation_hook failed with output: 

    remote: Permission to coopiteasy/cooperative.git denied to OCA-git-bot.
fatal: unable to access 'https://github.com/coopiteasy/cooperative/': The requested URL returned error: 403

    how is this supposed to be handled? should oca-git-bot be part of our github organization? i invited it, thinking that maybe it auto-accepts invites, but nothing changed.

    what should i do?

    cheers,

    hugues
    coop it easy

    _______________________________________________
    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 - 12:06 - 22 Feb 2023
  • write access to repositories for oca-git-bot

    hello,

    maybe this is documented somewhere but i could not find the information.

    for the /ocabot rebase command to work, oca-git-bot needs write access to the repository that contains the branch. without it, it fails like this:

    The rebase process failed, because command git push --force coopiteasy tmp-pr-40:12.0-cooperator_website_add_validation_hook failed with output: 

    remote: Permission to coopiteasy/cooperative.git denied to OCA-git-bot.
fatal: unable to access 'https://github.com/coopiteasy/cooperative/': The requested URL returned error: 403

    how is this supposed to be handled? should oca-git-bot be part of our github organization? i invited it, thinking that maybe it auto-accepts invites, but nothing changed.

    what should i do?

    cheers,

    hugues
    coop it easy

    by hugues - 11:51 - 22 Feb 2023
  • Re: booking of resources

    hello,

    thank you, pedro, olaf, and jairo, for your answers.

    what we ended up doing is creating a module (resource_booking_auto_create) that adds a wizard that allows to select resources by category, and create resource combinations on the fly. it is available in oca/calendar#83. reviews welcome.

    while this solution works, it feels to me like a big workaround. i realized too late into the development process (our budget on this was too limited) that a better solution would be to split the resource_booking module into multiple parts, because it handles too many independent things:

    • resource_booking would be the base module which defines the resource.booking model and allows to book resources directly (m2m relationship to resource.resource) and handle the availability of resources.
    • resource_booking_type would depend on resource_booking and define the resource.booking.type model.
    • resource_booking_combination would depend on resource_booking_type and define the resource.booking.combination model.

    installing resource_booking_combination would result in the same behavior as is currently the case with resource_booking. in our case, we would depend only on resource_booking instead of creating useless combinations under the hood.

    what do you think of this refactoring?

    we also needed to be able to link a resource booking to a sale order. the sale_resource_booking module (which has not yet been migrated to 14.0) allows this but works in the opposite way of what we needed: it allows to schedule a booking from an existing sale order, while we wanted to create a sale order from a scheduled booking.

    we ended up creating a new module resource_booking_sale that creates a sale order for each resource booking and displays (and allows to edit) the sale order lines directly on the resource booking form. it also allow to link a product to a resource booking type and to a resource and generates the sale order lines based on this. it is available here. what do you think? reviews welcome.

    for the module containing the wizard, we had to define a resource.category model. we did it in another module (resource_category) (oca/calendar#83 adds several modules). it is a really simple addition (just a simple resource.category model with a name and m2m relationship between it and resource.resource), but i think that it should not belong in oca/calendar. i think that we are missing an oca/resource repository for modules handling resources.

    what do you think?

    cheers,

    hugues
    coop it easy

    by hugues - 11:40 - 22 Feb 2023
  • Re: Pricelist sale price on form
    Thank you Pedro and Matthieu ^^

    I anticipate to you that I am also developing a module that will extend https://github.com/OCA/product-attribute/tree/14.0/product_form_pricelist  and allows to open the whole pricelist rule form by product form, compute product sales price for that specific product-pricelist rule, and will also try to implement one of my previous request:

    8 feb 2023, 20:41 Francesco Ballerini:Last question,  in pricelist based on formula do we have a way to compute the discount price percentage by setting up the sales price ?

     I can notify here when PR is ready in beta if someone is interested to help with this feature.

    Regards,
    Francesco


    Il giorno mer 15 feb 2023 alle ore 11:37 Matthieu Mequignon <notifications@odoo-community.org> ha scritto:
    On 2/15/23 11:27, Francesco Ballerini wrote:
    Thank you for mentioning about  https://github.com/OCA/sale-workflow/pull/2372, 

    It wasn't caching because of the with_delay function https://github.com/OCA/sale-workflow/blob/6c0549005b20e695173ab7b34901cf8493418960/pricelist_cache/models/product_pricelist_cache.py#L197, I removed it because I wasn't sure how to manage function parameters, not the best way to handle maybe but now it caches instantly.

    I want to ask one more thing: does Odoo not allow by default to export pricelist for customer? In that case we definitely want to use your module  = )

    Thanks for yor help,

    Francesco

    Il giorno mer 15 feb 2023 alle ore 09:52 Matthieu Mequignon <notifications@odoo-community.org> ha scritto:
    On 2/15/23 09:42, Francesco Ballerini wrote:
    Thank you very much for the feedback Matthieu,

    can I run the creation of the cache manually for testing purposes ?  
    I have found a cron "Reset pricelist cache" and an automation to update pricelists cache but I am not sure how to run the process from an empty cache.
    Il giorno mar 14 feb 2023 alle ore 12:47 Matthieu Mequignon <notifications@odoo-community.org> ha scritto:
    On 2/8/23 10:22, Francesco Ballerini wrote:




> Hello,




>




> I would like to be able to show sales price in pricelist items form.




>




> Very similar task to this module (only available for odoo13 at the 




> moment) 




> https://odoo-community.org/shop/product-list-pricelist-price-6617#attr=12054, 




> but this one does the job in the product template tree-view.




>




> We would need the same one in the product pricelist item form.




> I need it for odoo14 but I can consider modules for other version is 




> there is one available but not available for 14 (could try to perform 




> a migration in some cases).




>




> Thank you in advance. Regards,




>




> Francesco Ballerini




>




>




>




> _______________________________________________




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




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




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




>
Hi, I wrote a module for that 
https://github.com/OCA/sale-workflow/tree/14.0/pricelist_cache

Prices are cached everyday, so the price you see is today's price.
With this module, you get a "display pricelist prices" button on the 
pricelist's form.
Also, you get a handy "display customer prices" action on the partner.
Those are popping up a tree view with all prices, which you can then 
filter and so on.





-- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://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

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

    Yes, you can run the scheduled action manually.
    Please note that there's an ongoing bug (with the fix here https://github.com/OCA/sale-workflow/pull/2372).
    It is possible to retrieve prices while caching is not done, which is wrong.

    -- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://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

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

    Because it is very slow.
    In the case of the customer I wrote this module for, it takes ~10 minutes to retrieve all prices for a given pricelist.
    It is okay when you don't have much products, though.

    -- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://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

    by Francesco Ballerini - 12:40 - 15 Feb 2023
  • Re: Pricelist sale price on form
    On 2/15/23 11:27, Francesco Ballerini wrote:
    Thank you for mentioning about  https://github.com/OCA/sale-workflow/pull/2372, 

    It wasn't caching because of the with_delay function https://github.com/OCA/sale-workflow/blob/6c0549005b20e695173ab7b34901cf8493418960/pricelist_cache/models/product_pricelist_cache.py#L197, I removed it because I wasn't sure how to manage function parameters, not the best way to handle maybe but now it caches instantly.

    I want to ask one more thing: does Odoo not allow by default to export pricelist for customer? In that case we definitely want to use your module  = )

    Thanks for yor help,

    Francesco

    Il giorno mer 15 feb 2023 alle ore 09:52 Matthieu Mequignon <notifications@odoo-community.org> ha scritto:
    On 2/15/23 09:42, Francesco Ballerini wrote:
    Thank you very much for the feedback Matthieu,

    can I run the creation of the cache manually for testing purposes ?  
    I have found a cron "Reset pricelist cache" and an automation to update pricelists cache but I am not sure how to run the process from an empty cache.
    Il giorno mar 14 feb 2023 alle ore 12:47 Matthieu Mequignon <notifications@odoo-community.org> ha scritto:
    On 2/8/23 10:22, Francesco Ballerini wrote:



> Hello,



>



> I would like to be able to show sales price in pricelist items form.



>



> Very similar task to this module (only available for odoo13 at the 



> moment) 



> https://odoo-community.org/shop/product-list-pricelist-price-6617#attr=12054, 



> but this one does the job in the product template tree-view.



>



> We would need the same one in the product pricelist item form.



> I need it for odoo14 but I can consider modules for other version is 



> there is one available but not available for 14 (could try to perform 



> a migration in some cases).



>



> Thank you in advance. Regards,



>



> Francesco Ballerini



>



>



>



> _______________________________________________



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



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



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



>
Hi, I wrote a module for that 
https://github.com/OCA/sale-workflow/tree/14.0/pricelist_cache

Prices are cached everyday, so the price you see is today's price.
With this module, you get a "display pricelist prices" button on the 
pricelist's form.
Also, you get a handy "display customer prices" action on the partner.
Those are popping up a tree view with all prices, which you can then 
filter and so on.




-- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://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

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

    Yes, you can run the scheduled action manually.
    Please note that there's an ongoing bug (with the fix here https://github.com/OCA/sale-workflow/pull/2372).
    It is possible to retrieve prices while caching is not done, which is wrong.

    -- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://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

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

    Because it is very slow.
    In the case of the customer I wrote this module for, it takes ~10 minutes to retrieve all prices for a given pricelist.
    It is okay when you don't have much products, though.

    -- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://www.camptocamp.com/
    by Matthieu Méquignon - 11:36 - 15 Feb 2023
  • Re: Pricelist sale price on form
    by Pedro M. Baeza - 11:31 - 15 Feb 2023
  • Re: Pricelist sale price on form
    Thank you for mentioning about  https://github.com/OCA/sale-workflow/pull/2372, 

    It wasn't caching because of the with_delay function https://github.com/OCA/sale-workflow/blob/6c0549005b20e695173ab7b34901cf8493418960/pricelist_cache/models/product_pricelist_cache.py#L197, I removed it because I wasn't sure how to manage function parameters, not the best way to handle maybe but now it caches instantly.

    I want to ask one more thing: does Odoo not allow by default to export pricelist for customer? In that case we definitely want to use your module  = )

    Thanks for yor help,

    Francesco

    Il giorno mer 15 feb 2023 alle ore 09:52 Matthieu Mequignon <notifications@odoo-community.org> ha scritto:
    On 2/15/23 09:42, Francesco Ballerini wrote:
    Thank you very much for the feedback Matthieu,

    can I run the creation of the cache manually for testing purposes ?  
    I have found a cron "Reset pricelist cache" and an automation to update pricelists cache but I am not sure how to run the process from an empty cache.
    Il giorno mar 14 feb 2023 alle ore 12:47 Matthieu Mequignon <notifications@odoo-community.org> ha scritto:
    On 2/8/23 10:22, Francesco Ballerini wrote:



> Hello,



>



> I would like to be able to show sales price in pricelist items form.



>



> Very similar task to this module (only available for odoo13 at the 



> moment) 



> https://odoo-community.org/shop/product-list-pricelist-price-6617#attr=12054, 



> but this one does the job in the product template tree-view.



>



> We would need the same one in the product pricelist item form.



> I need it for odoo14 but I can consider modules for other version is 



> there is one available but not available for 14 (could try to perform 



> a migration in some cases).



>



> Thank you in advance. Regards,



>



> Francesco Ballerini



>



>



>



> _______________________________________________



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



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



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



>
Hi, I wrote a module for that 
https://github.com/OCA/sale-workflow/tree/14.0/pricelist_cache

Prices are cached everyday, so the price you see is today's price.
With this module, you get a "display pricelist prices" button on the 
pricelist's form.
Also, you get a handy "display customer prices" action on the partner.
Those are popping up a tree view with all prices, which you can then 
filter and so on.




-- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://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

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

    Yes, you can run the scheduled action manually.
    Please note that there's an ongoing bug (with the fix here https://github.com/OCA/sale-workflow/pull/2372).
    It is possible to retrieve prices while caching is not done, which is wrong.

    -- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://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

    by Francesco Ballerini - 11:26 - 15 Feb 2023
  • Re: OCA Contract Repository
    > - Contract objects don’t have states. It appears to me that in some versions states existed but is a functionality that was dropped and some point. I strongly think that a module like this must have states.


    >  I think the name of the contract should be computed, or at least use a sequence. I don’t see the point of the name to be manually edited. Having a computed one will help with search and filtering. 

    Indeed, this can be improved.

    > - There is not grouping entity of contract objects. Meaning we don't have an easy way to group contracts by category or an hicherarchical structure. I think this is useful for usability and to set default parameters. 

    Maybe adding a 'contract.category' model could be great (in another module ?). But, for the time being, this can be done through contract tags. See: https://github.com/OCA/contract/blob/14.0/contract/models/contract.py#L110

    > - There is not link between contracts and agreement modules. My common sense dict that a contract should be created from an agreement, meaning that an agreement is a legal contract and when approved and signed, it creates a contract record which defines invoicing schedule. If not, i really don't see any use for agreements if they are not linked. Maybe this can be solved with a new module. 

    This is still tested in a draft PR: https://github.com/OCA/contract/pull/649 You can review it and make suggestions.

    > - I think all codebase should be refactored and maybe split the contract module to have one base_contract with basic functionality for simple cases and then other modules to plug-in more functionality. 

    This module has indeed a big history, refactored on 12.0 version I think. Since, some improvements have been done (refactoring on recurrency computations by Pedro see: https://github.com/OCA/contract/pull/533/commits/cd086ddbb4a9b85ccfcac288e53fb93e716d9446)

    Indeed, I think it has now a very complex implementation that makes user understanding (and debugging) difficult.

    We could make an issue on the github repository to help gathering ideas and focus discussion there than on this mailing list. But I agree that we could split some logic in separate modules (with meaningful names - if we could avoid base_contract).

    I hope this answered your questions.


    Regards,


    On Fri, Feb 10, 2023 at 5:57 PM Nicolas Rodriguez Sande <notifications@odoo-community.org> wrote:

    Hello, I’m writing to know your opinion about the contract repository. I started to use the modules in the repository and noted that the module versions of contract module differ a lot between odoo versions. 


    I have to do some implementations regarding that modules so I’m going to start making PRs to that repo and try to improve the modules starting in version 14.0 and then port it to the others. 

    I want to have your opinions on things you can tell me about what is missing in the modules and so I can organize my roadmap. Also, I don’t know if there are currently active PSC of the module, if not or you want me to join the team I will be interested, because I need to improve the modules and if that can help the development of the repo, count with me. 

    From what I saw, I see the following issues to solve, please if you know another issues or want to make an opinion of changes you would like to see in the module please comment me here: 

    - Contract objects don’t have states. It appears to me that in some versions states existed but is a functionality that was dropped and some point. I strongly think that a module like this must have states.

    - I think the name of the contract should be computed, or at least use a sequence. I don’t see the point of the name to be manually edited. Having a computed one will help with search and filtering. 

    - There is not grouping entity of contract objects. Meaning we don't have an easy way to group contracts by category or an hicherarchical structure. I think this is useful for usability and to set default parameters. 

    - There is not link between contracts and agreement modules. My common sense dict that a contract should be created from an agreement, meaning that an agreement is a legal contract and when approved and signed, it creates a contract record which defines invoicing schedule. If not, i really don't see any use for agreements if they are not linked. Maybe this can be solved with a new module. 

    - Contract views are awful and need to be improved to favor user usability and comprehension of the module mechanics and uses. This is one of the first changes i want to introduce. 

    - Contract reports and portal views need to be improved. Currently the contract report is not so much developed. Also could be a good idea to allow to see agreements from portal contracts. 

    - I think all codebase should be refactored and maybe split the contract module to have one base_contract with basic functionality for simple cases and then other modules to plug-in more functionality. 

    If you have more opinions and things you want to see in a roadmap, please tell me here and i can maybe add it to my next PRs. Also if you have opinions of how the module should work will be great for when we refactor it. 

    Regards and i want for your thoughts. 

    _______________________________________________
    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 - 10:16 - 15 Feb 2023
  • Re: Pricelist sale price on form
    On 2/15/23 09:42, Francesco Ballerini wrote:
    Thank you very much for the feedback Matthieu,

    can I run the creation of the cache manually for testing purposes ?  
    I have found a cron "Reset pricelist cache" and an automation to update pricelists cache but I am not sure how to run the process from an empty cache.
    Il giorno mar 14 feb 2023 alle ore 12:47 Matthieu Mequignon <notifications@odoo-community.org> ha scritto:
    On 2/8/23 10:22, Francesco Ballerini wrote:


> Hello,


>


> I would like to be able to show sales price in pricelist items form.


>


> Very similar task to this module (only available for odoo13 at the 


> moment) 


> https://odoo-community.org/shop/product-list-pricelist-price-6617#attr=12054, 


> but this one does the job in the product template tree-view.


>


> We would need the same one in the product pricelist item form.


> I need it for odoo14 but I can consider modules for other version is 


> there is one available but not available for 14 (could try to perform 


> a migration in some cases).


>


> Thank you in advance. Regards,


>


> Francesco Ballerini


>


>


>


> _______________________________________________


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


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


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


>
Hi, I wrote a module for that 
https://github.com/OCA/sale-workflow/tree/14.0/pricelist_cache

Prices are cached everyday, so the price you see is today's price.
With this module, you get a "display pricelist prices" button on the 
pricelist's form.
Also, you get a handy "display customer prices" action on the partner.
Those are popping up a tree view with all prices, which you can then 
filter and so on.



-- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://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

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

    Yes, you can run the scheduled action manually.
    Please note that there's an ongoing bug (with the fix here https://github.com/OCA/sale-workflow/pull/2372).
    It is possible to retrieve prices while caching is not done, which is wrong.

    -- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://www.camptocamp.com/
    by Matthieu Méquignon - 09:51 - 15 Feb 2023
  • Re: Pricelist sale price on form
    Thank you very much for the feedback Matthieu,

    can I run the creation of the cache manually for testing purposes ?  
    I have found a cron "Reset pricelist cache" and an automation to update pricelists cache but I am not sure how to run the process from an empty cache.
    Il giorno mar 14 feb 2023 alle ore 12:47 Matthieu Mequignon <notifications@odoo-community.org> ha scritto:
    On 2/8/23 10:22, Francesco Ballerini wrote:


> Hello,


>


> I would like to be able to show sales price in pricelist items form.


>


> Very similar task to this module (only available for odoo13 at the 


> moment) 


> https://odoo-community.org/shop/product-list-pricelist-price-6617#attr=12054, 


> but this one does the job in the product template tree-view.


>


> We would need the same one in the product pricelist item form.


> I need it for odoo14 but I can consider modules for other version is 


> there is one available but not available for 14 (could try to perform 


> a migration in some cases).


>


> Thank you in advance. Regards,


>


> Francesco Ballerini


>


>


>


> _______________________________________________


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


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


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


>
Hi, I wrote a module for that 
https://github.com/OCA/sale-workflow/tree/14.0/pricelist_cache

Prices are cached everyday, so the price you see is today's price.
With this module, you get a "display pricelist prices" button on the 
pricelist's form.
Also, you get a handy "display customer prices" action on the partner.
Those are popping up a tree view with all prices, which you can then 
filter and so on.



-- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://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

    by Francesco Ballerini - 09:41 - 15 Feb 2023
  • Re: Pricelist sale price on form 
    On 2/8/23 10:22, Francesco Ballerini wrote:

> Hello,

>

> I would like to be able to show sales price in pricelist items form.

>

> Very similar task to this module (only available for odoo13 at the 

> moment) 

> https://odoo-community.org/shop/product-list-pricelist-price-6617#attr=12054, 

> but this one does the job in the product template tree-view.

>

> We would need the same one in the product pricelist item form.

> I need it for odoo14 but I can consider modules for other version is 

> there is one available but not available for 14 (could try to perform 

> a migration in some cases).

>

> Thank you in advance. Regards,

>

> Francesco Ballerini

>

>

>

> _______________________________________________

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

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

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

>
Hi, I wrote a module for that 
https://github.com/OCA/sale-workflow/tree/14.0/pricelist_cache

Prices are cached everyday, so the price you see is today's price.
With this module, you get a "display pricelist prices" button on the 
pricelist's form.
Also, you get a handy "display customer prices" action on the partner.
Those are popping up a tree view with all prices, which you can then 
filter and so on.


-- 
Matthieu Méquignon
Business Solutions Odoo Developer

Camptocamp France SA
Phone: +33 4 58 48 20 18
https://www.camptocamp.com/
    by Matthieu Méquignon - 12:46 - 14 Feb 2023
  • Re: Odoo -- Community v Enterprise Questions
    On Sun, Feb 12, 2023 at 6:12 PM Dev <notifications@odoo-community.org> wrote:

    The reason for it being complicated is to do with database setup. I haven't found any way to have a docker install creates no database, so you can open the page and create/restore a database as described in the docs for a new installation. 


    Ah, that makes sense. For local containers, we don't restore a database, so no problem. In production, I never wanted /web/database/manage to show up for even a second, so I have Terraform get the database into shape prior to running Odoo for the first time.
     
    by Adam Heinz - 02:20 - 13 Feb 2023
  • Re: Odoo -- Community v Enterprise Questions
    On 13/02/2023 00:12, Dev wrote:
    Overall, I love the experience of dealing with containerized apps, compared to the old school style of installing them directly. However, there were two apps that stood out as being as struggle to install. One was Outline wiki (a great app once installed, however). The other was Odoo, both community and enterprise, but especially enterprise.
    Hello Lewy,

    Don't hesitate to contact us using the Odoo support if you have issues to use our docker image.

    Martin
    by Martin Trigaux - 10:05 - 13 Feb 2023