Skip to Content

Contributors

  • Re: Tree view with preview - is it possible?

    Alexandre,


    that's exactly what I was looking for. A bit pity it's closed source and I'd also need it for 14 but great find. I think something like this could be part of Odoo itself or at least a very worthy OCA module.


    Best regards


        Radovan


    On piatok 21. júna 2024 16:57:32 CEST Alexandre Fayolle wrote:

    > There's a closed source addon on the app store which seems to do that:

    > rmt_advance_list_form

    > Alexandre

    >

    > On 21/06/2024 11:22, Radovan Skolnik wrote:

    > > Hello,

    > >

    > >

    > > is there some view or widget or a way to display something like a split

    > > screen where one part would be holding a tree view of objects and second

    > > part would having a form view (read only is sufficient) of selected

    > > (clicked) record from the first part?

    > >

    > >

    > > I seem to remember seeing something like that somewhere but cannot

    > > remember where. Any hints / pointers are greatly welcome.

    > >

    > >

    > > Best regards

    > >

    > >

    > >     Radovan Skolnik

    > >

    > > _______________________________________________

    > > 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 [1]

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

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

    >

    >

    >

    > [1] https://odoo-community.org/groups/contributors-15

    > [2] https://odoo-community.org/groups?unsubscribe




    by Radovan Skolnik - 05:06 - 21 Jun 2024
  • Is there a module...? :)
    G'day to all!
    
    Prior to jumping into making a new module, maybe someone solved the following somehow:
    
    "Document Generator". 
     - a document part (component) with variants and per-variant versions
     - can be attached to a a document (e.g. product) via a dynamic "no-code" field
     - to be used in a report generation through that field.
     - wizard that kicks in before the report generation to set the actual "variant value" to that dynamic field.
    
    Use-case: Statement of Work generation, proposal generation.
    
    Kind regards,
    Alexey

    by Alexey Pelykh - 05:06 - 21 Jun 2024
  • Re: Tree view with preview - is it possible?
    There's a closed source addon on the app store which seems to do that: 
    rmt_advance_list_form
    
    Alexandre
    
    On 21/06/2024 11:22, Radovan Skolnik wrote:
    
    > Hello,
    
    > 
    
    > 
    
    > is there some view or widget or a way to display something like a split 
    
    > screen where one part would be holding a tree view of objects and second 
    
    > part would having a form view (read only is sufficient) of selected 
    
    > (clicked) record from the first part?
    
    > 
    
    > 
    
    > I seem to remember seeing something like that somewhere but cannot 
    
    > remember where. Any hints / pointers are greatly welcome.
    
    > 
    
    > 
    
    > Best regards
    
    > 
    
    > 
    
    >      Radovan Skolnik
    
    > 
    
    > _______________________________________________
    
    > 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 - 04:56 - 21 Jun 2024
  • Re: x2many fields vertical scrollbar?
    I'm sorry for bottom posting, just wanted to notify that adding

    .table-responsive {
        overflow: visible;
    }

    actually made the overflow-x always visible as well. I didn't notice because I didn't have enough fields in the view while checking for it.

    Regards,
    Francesco Ballerini

     

    by Francesco Ballerini - 02:46 - 21 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change

    Hi Janik,

    On 6/21/24 14:02, Janik von Rotz wrote:
    A simple solution is probably a fixed list of modules that should always 
    be updated (from the cli) after the code change and before restarting 
    the Odoo container.
    

    This is indeed the more crude solution that we generally use for our clients - either figure out by hand which modules to update if you're in a hurry, or just `-u base`.

    But the two solutions mentioned are smarter in that sense because they figure out from the code change what to update.

    Cheers


    by Tom Blauwendraat - 02:31 - 21 Jun 2024
  • Re: x2many fields vertical scrollbar?
    Hi David, the module you've suggested actually makes the x2m listview header sticky ! 
    As there were few scss lines I've tested them one by one, realized that you also need to add these lines in order to actually apply this web responsive code which makes list-view header sticky to x2m list as well
    .table-responsive {
    overflow: visible;
    }
    I don't have a good perception or particular skills in scss/css so I am not sure why these lines are required to apply the "position:sticky" thing, but I guess we made it 😁

    The footer issue remains as it's still only visible when scrolling to the bottom, but the sticky header was more important. Thanks for all the advice!

    Regards,
    Francesco Ballerini


    Il giorno ven 21 giu 2024 alle ore 12:32 David Beal <notifications@odoo-community.org> ha scritto:
    Hi all,
    
    Consider using https://github.com/CybroOdoo/CybroAddons/tree/16.0/list_view_sticky_header
    for this use case.
    It works very well.
    
    It might be nice if Cybrosys would consider bringing this module under
    the OCA umbrella.
    
    CybroAddons repo is very huge, it could be an advantage to move it to
    a smaller one.
    
    
    Regards
    
    
    David BEAL
    Akretion
    Consultant ERP Odoo
    
    Le ven. 21 juin 2024 à 11:27, Francesco Ballerini
    <notifications@odoo-community.org> a écrit :
    
    
    >
    
    
    > Hi Yann,
    
    
    >
    
    
    >
    
    
    > I'm really grateful for the feedback, your approach is working. I only have couple of issues with:
    
    
    >
    
    
    >
    
    
    > - sticky header/footer, I have web responsive installed and I verified that this web responsive code is also applying to the x2m list views by changing some colours : ) . But for some reason header and footer will not actually be when adding vertical scrolling to x2m list
    
    
    >
    
    
    >
    
    
    > - overflow-x: useful when we have a decent number of fields in the x2m listview, at the moment I only see it when I reach the bottom of scroll-Y.
    
    
    >
    
    
    >   I need it always visible though
    
    
    >
    
    
    >
    
    
    > Do you have additional suggestions to cover this?
    
    
    >
    
    
    >
    
    
    > Thank you
    
    
    >
    
    
    > --
    
    
    >
    
    
    > Francesco Ballerini
    
    
    >
    
    
    >
    
    
    > Il giorno ven 21 giu 2024 alle ore 10:53 Yann Papouin <notifications@odoo-community.org> ha scritto:
    
    
    >
    
    
    > This should be enough:
    
    
    >
    
    
    > .o_form_view .o_field_widget .o_list_view {
    
    
    >   overflow-y: scroll;
    
    
    >   max-height: 600px;
    
    
    > }
    
    
    >
    
    
    > Add it using a custom module
    
    
    >
    
    
    > --
    
    
    > Yann PAPOUIN, Ingénieur R&D | DEC
    
    
    >
    
    
    >
    
    
    > Le ven. 21 juin 2024 à 10:09, Francesco Ballerini <notifications@odoo-community.org> a écrit :
    
    
    >
    
    
    > Hi,
    
    
    >
    
    
    >
    
    
    > I am managing a situation where we often have a lot of lines on some main apps x2many fields (sale, picking, invoice, purchase..).
    
    
    >
    
    
    >
    
    
    > It's not really handy when we are in a range of 60-200 lines, I just discovered that I could permanently increase the "limit" attribute on the tree-view.
    
    
    >
    
    
    >
    
    
    > That would partially solve the problem, but in my opinion another part of the issue is that if you increase the "pager limit" to contain all lines, all the elements after the field will be pushed down in the view.
    
    
    >
    
    
    > It would be nice to have a vertical scrolling so that we can let's say set a limit of 500 lines (so they will all be loaded in the same pager) then have a limited height and be able to vertically scroll through the lines.
    
    
    >
    
    
    >
    
    
    > Do you know any way to achieve this? Maybe someone already made a module for that?
    
    
    >
    
    
    >
    
    
    > Have a nice day,
    
    
    > 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
    
    
    >
    
    
    > _______________________________________________
    
    
    > 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 Francesco Ballerini - 02:31 - 21 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change
    Hi Pedro,
    
    Thanks for your reply.
    
    Yes exactly, access to res.partner/res.user is done before I can act. 
    Updating the module with the cli works (but you have to know the module 
    name). As I understand click-odoo-update works similar to 
    module_auto_update, but can update all changed modules from a separate 
    Odoo process.
    
    A simple solution is probably a fixed list of modules that should always 
    be updated (from the cli) after the code change and before restarting 
    the Odoo container.
    
    Regards, Janik
    
    On 6/21/24 11:52, Pedro M. Baeza wrote:
    
    > Maybe the problem is that you want to update from the UI, and in that 
    
    > case, an access to res.partner/res.users is done before you can act. 
    
    > You should do it in the command line with the -u argument (or 
    
    > click-odoo-update), or with a parallel run (in Docker environments), 
    
    > or similar.
    
    >
    
    > Regards.
    
    >
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    >
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    

    by Janik von Rotz - 02:01 - 21 Jun 2024
  • Re: x2many fields vertical scrollbar?
    Hi all,
    
    Consider using https://github.com/CybroOdoo/CybroAddons/tree/16.0/list_view_sticky_header
    for this use case.
    It works very well.
    
    It might be nice if Cybrosys would consider bringing this module under
    the OCA umbrella.
    
    CybroAddons repo is very huge, it could be an advantage to move it to
    a smaller one.
    
    
    Regards
    
    
    David BEAL
    Akretion
    Consultant ERP Odoo
    
    Le ven. 21 juin 2024 à 11:27, Francesco Ballerini
    <notifications@odoo-community.org> a écrit :
    
    >
    
    > Hi Yann,
    
    >
    
    >
    
    > I'm really grateful for the feedback, your approach is working. I only have couple of issues with:
    
    >
    
    >
    
    > - sticky header/footer, I have web responsive installed and I verified that this web responsive code is also applying to the x2m list views by changing some colours : ) . But for some reason header and footer will not actually be when adding vertical scrolling to x2m list
    
    >
    
    >
    
    > - overflow-x: useful when we have a decent number of fields in the x2m listview, at the moment I only see it when I reach the bottom of scroll-Y.
    
    >
    
    >   I need it always visible though
    
    >
    
    >
    
    > Do you have additional suggestions to cover this?
    
    >
    
    >
    
    > Thank you
    
    >
    
    > --
    
    >
    
    > Francesco Ballerini
    
    >
    
    >
    
    > Il giorno ven 21 giu 2024 alle ore 10:53 Yann Papouin <notifications@odoo-community.org> ha scritto:
    
    >
    
    > This should be enough:
    
    >
    
    > .o_form_view .o_field_widget .o_list_view {
    
    >   overflow-y: scroll;
    
    >   max-height: 600px;
    
    > }
    
    >
    
    > Add it using a custom module
    
    >
    
    > --
    
    > Yann PAPOUIN, Ingénieur R&D | DEC
    
    >
    
    >
    
    > Le ven. 21 juin 2024 à 10:09, Francesco Ballerini <notifications@odoo-community.org> a écrit :
    
    >
    
    > Hi,
    
    >
    
    >
    
    > I am managing a situation where we often have a lot of lines on some main apps x2many fields (sale, picking, invoice, purchase..).
    
    >
    
    >
    
    > It's not really handy when we are in a range of 60-200 lines, I just discovered that I could permanently increase the "limit" attribute on the tree-view.
    
    >
    
    >
    
    > That would partially solve the problem, but in my opinion another part of the issue is that if you increase the "pager limit" to contain all lines, all the elements after the field will be pushed down in the view.
    
    >
    
    > It would be nice to have a vertical scrolling so that we can let's say set a limit of 500 lines (so they will all be loaded in the same pager) then have a limited height and be able to vertically scroll through the lines.
    
    >
    
    >
    
    > Do you know any way to achieve this? Maybe someone already made a module for that?
    
    >
    
    >
    
    > Have a nice day,
    
    > 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
    
    >
    
    > _______________________________________________
    
    > 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 - 12:31 - 21 Jun 2024
  • Re: Tree view with preview - is it possible?

    That's not what I aim for. Imagine having split screen where on left side you have list of Sale Orders and when you click on one it is displayed in the right side.


        Radovan


    On piatok 21. júna 2024 11:48:25 CEST Tom Blauwendraat wrote:

    > Dashboards?

    >

    > _______________________________________________

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

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

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

    >

    >

    >

    > [1] https://odoo-community.org/groups/contributors-15

    > [2] https://odoo-community.org/groups?unsubscribe




    by Radovan Skolnik - 12:05 - 21 Jun 2024
  • Re: db not yet committed when overriding create/update.

    Hi Yves,

    flush wouldn't work, but commit should do it! But I wonder if the automated action is using the same cursor as the main process.

    Maybe a nice way could be to install OCA's "queue_job" and in your automated action, call the webhook in a separate function that you call using .with_delay().some_function()

    Then it will be executed as a queue.job, and you are sure that whenever it's picked up the original action will already have finished (or if it failed, and the cr is rolled back, then the webhook won't be called at all since the queue job record will also not have been created, which is also a feature you won't have if you call the webhook directly)

    cheers


    On 6/21/24 11:48, Yves Goldberg wrote:
    Hello,
    I send a webhook when an event occurs in Odoo.
    The problem I have is that when overriding create/update; and triggering my webhook, the data is not yet committed in the db.
    (the external system is sending in it's response that the record is not found in the case of create and get the old field value -before changes- for an update).

    I tried to use env.cr.flush() and/or env.cr.commit() both in my automated action and in my code before the webhook but nothing seems to work.
    Any other way I could check?
    Thank you
     --
    Yves Goldberg
    --

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


    by Tom Blauwendraat - 11:56 - 21 Jun 2024
  • Re: db not yet committed when overriding create/update.
    You can send your webhook using a callback on the postcommit callback.
    Check in the Odoo code for the use of the decorator @self.env.cr.postcommit.add

    class BaseCursor:
        """ Base class for cursors that manage pre/post commit hooks. """

        def __init__(self):
            self.precommit = tools.Callbacks()
            self.postcommit = tools.Callbacks()
            self.prerollback = tools.Callbacks()
            self.postrollback = tools.Callbacks()

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


    Le ven. 21 juin 2024 à 11:48, Yves Goldberg <notifications@odoo-community.org> a écrit :
    Hello,
    I send a webhook when an event occurs in Odoo.
    The problem I have is that when overriding create/update; and triggering my webhook, the data is not yet committed in the db.
    (the external system is sending in it's response that the record is not found in the case of create and get the old field value -before changes- for an update).

    I tried to use env.cr.flush() and/or env.cr.commit() both in my automated action and in my code before the webhook but nothing seems to work.
    Any other way I could check?
    Thank you
     --
    Yves Goldberg
    --

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


    by Yann Papouin - 11:56 - 21 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change
    Maybe the problem is that you want to update from the UI, and in that case, an access to res.partner/res.users is done before you can act. You should do it in the command line with the -u argument (or click-odoo-update), or with a parallel run (in Docker environments), or similar.

    Regards.

    by Pedro M. Baeza - 11:51 - 21 Jun 2024
  • Re: Tree view with preview - is it possible?
    Dashboards?
    

    by Tom Blauwendraat - 11:46 - 21 Jun 2024
  • db not yet committed when overriding create/update.
    Hello,
    I send a webhook when an event occurs in Odoo.
    The problem I have is that when overriding create/update; and triggering my webhook, the data is not yet committed in the db.
    (the external system is sending in it's response that the record is not found in the case of create and get the old field value -before changes- for an update).

    I tried to use env.cr.flush() and/or env.cr.commit() both in my automated action and in my code before the webhook but nothing seems to work.
    Any other way I could check?
    Thank you
     --
    Yves Goldberg
    --


    by Yves Goldberg - 11:46 - 21 Jun 2024
  • Re: Tree view with preview - is it possible?
    The only place I can recall the combining of different views is in the Enterprise Documents module, but that is Tree,Kanban and Form. I watched a presentation many years ago on how they achieved but remember not a lot tbh.

    On Fri, Jun 21, 2024 at 9:22 PM Radovan Skolnik <notifications@odoo-community.org> wrote:

    Hello,


    is there some view or widget or a way to display something like a split screen where one part would be holding a tree view of objects and second part would having a form view (read only is sufficient) of selected (clicked) record from the first part?


    I seem to remember seeing something like that somewhere but cannot remember where. Any hints / pointers are greatly welcome.


    Best regards


        Radovan Skolnik

    _______________________________________________
    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" <graeme@moahub.nz> - 11:41 - 21 Jun 2024
  • Re: x2many fields vertical scrollbar?

    Hi Yann,


    I'm really grateful for the feedback, your approach is working. I only have couple of issues with: 


    - sticky header/footer, I have web responsive installed and I verified that this web responsive code is also applying to the x2m list views by changing some colours : ) . But for some reason header and footer will not actually be when adding vertical scrolling to x2m list


    - overflow-x: useful when we have a decent number of fields in the x2m listview, at the moment I only see it when I reach the bottom of scroll-Y.

      I need it always visible though


    Do you have additional suggestions to cover this?


    Thank you

    --

    Francesco Ballerini


    Il giorno ven 21 giu 2024 alle ore 10:53 Yann Papouin <notifications@odoo-community.org> ha scritto:
    This should be enough:

    .o_form_view .o_field_widget .o_list_view {
      overflow-y: scroll;
      max-height: 600px;
    }

    Add it using a custom module

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


    Le ven. 21 juin 2024 à 10:09, Francesco Ballerini <notifications@odoo-community.org> a écrit :

    Hi, 


    I am managing a situation where we often have a lot of lines on some main apps x2many fields (sale, picking, invoice, purchase..).


    It's not really handy when we are in a range of 60-200 lines, I just discovered that I could permanently increase the "limit" attribute on the tree-view.


    That would partially solve the problem, but in my opinion another part of the issue is that if you increase the "pager limit" to contain all lines, all the elements after the field will be pushed down in the view.

    It would be nice to have a vertical scrolling so that we can let's say set a limit of 500 lines (so they will all be loaded in the same pager) then have a limited height and be able to vertically scroll through the lines.


    Do you know any way to achieve this? Maybe someone already made a module for that?


    Have a nice day,
    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

    _______________________________________________
    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 - 21 Jun 2024
  • Tree view with preview - is it possible?

    Hello,


    is there some view or widget or a way to display something like a split screen where one part would be holding a tree view of objects and second part would having a form view (read only is sufficient) of selected (clicked) record from the first part?


    I seem to remember seeing something like that somewhere but cannot remember where. Any hints / pointers are greatly welcome.


    Best regards


        Radovan Skolnik


    by Radovan Skolnik - 11:21 - 21 Jun 2024
  • Re: x2many fields vertical scrollbar?
    This should be enough:

    .o_form_view .o_field_widget .o_list_view {
      overflow-y: scroll;
      max-height: 600px;
    }

    Add it using a custom module

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


    Le ven. 21 juin 2024 à 10:09, Francesco Ballerini <notifications@odoo-community.org> a écrit :

    Hi, 


    I am managing a situation where we often have a lot of lines on some main apps x2many fields (sale, picking, invoice, purchase..).


    It's not really handy when we are in a range of 60-200 lines, I just discovered that I could permanently increase the "limit" attribute on the tree-view.


    That would partially solve the problem, but in my opinion another part of the issue is that if you increase the "pager limit" to contain all lines, all the elements after the field will be pushed down in the view.

    It would be nice to have a vertical scrolling so that we can let's say set a limit of 500 lines (so they will all be loaded in the same pager) then have a limited height and be able to vertically scroll through the lines.


    Do you know any way to achieve this? Maybe someone already made a module for that?


    Have a nice day,
    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


    by Yann Papouin - 10:46 - 21 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change
    Do you define the database in the command with -d <database_name> beside the -u argument? 
    I had some effects when the -d was missing. 

    Von: Janik von Rotz <notifications@odoo-community.org>
    Gesendet: Friday, June 21, 2024 8:50:04 AM
    An: Contributors <contributors@odoo-community.org>
    Betreff: Re: Technical Question: Restart Odoo process after res.partner model change
     

    ACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.

    Hi Graeme,

    there is no own code so there is no bug. I am pretty sure what I described is reproducible with any Odoo setup.

    As I understand updating the database schema for a running Odoo process without restarting the process is simply not possible.

    I assume Odoo has an internal state of the field defined in the module code. Only if the process is restarted the state is updated.

    Regards,

    Janik

    On 6/20/24 22:02, Graeme Gellatly wrote:
    Then that is a bug in your own code, or you have not also restarted another running odoo process with the old info. -u has worked forever.

    On Fri, Jun 21, 2024 at 6:45 AM Janik von Rotz <notifications@odoo-community.org> wrote:

    Hi Tom

    Thanks for the reply.

    I did another test with the same results.

    The Odoo log tells that it updated the tables for the module, but it didn't.

    Cheers,

    Janik


    Init Odoo database with the required modules:

    ```
    task start
    docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    Getting the hash for `partner_fax`: `d1db56b45a4c5baa9a6cb0c571c37b0c394d8840`

    Then changing the file:

    ```
    cd oca/partner-contact
    vi partner_fax/models/res_partner.py
    ```

    By adding:

    ```python
    xy = fields.Char()
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    The Odoo log:

    ```
    2024-06-20 18:32:03,665 1 INFO 16.0 odoo.modules.registry: module partner_fax: creating or updating database tables
    ```

    Getting the hash for `partner_fax`: `b8236a3734e752fa62b669674afaa1db750f031d`

    When doing a restart.

    ```
    task restart
    ```

    I still get this message:

    ```
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
                                                                 ^
    ```

    The issue can be resolved by installing the module:

    ```
    docker-odoo-install -d 16.0 -i partner_fax  
    ```

    On 6/20/24 19:57, Tom Blauwendraat wrote:
    Hi Janik

    -i is wrong anyway, it installs, -u is what you need

    I dont know why the field update does not trigger, it should - did you restart odoo beforehand?

    20 jun. 2024 18:58:18 Janik von Rotz <notifications@odoo-community.org>:

    Hi Tom

    I tested this module and like it! However, it seems its only doing an update and not an install, which does not update the database schema.

    Cheers, Janik

    Here is how I tested the module with https://odoo.build/:

    Init Odoo database with the required modules.

    ```
    task start
    docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
    ```

    Checking the hash: `"partner_fax": "b8236a3734e752fa62b669674afaa1db750f031d"`

    Then changing a module file.

    ```
    vi oca/partner-contact/partner_fax/models/res_partner.py
    ```

    Adding:

    ```python
    xy = fields.Char()
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    When doing a restart.

    ```
    task restart
    ```

    I still get this message:

    ```
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
                                                                 ^
    ```

    Resolving the issue by installing the module:

    ```

    docker-odoo-install -d 16.0 -i partner_fax
    ```

    On 6/20/24 17:42, Tom Blauwendraat wrote:
    module_auto_update

    20 jun. 2024 17:22:17 Janik von Rotz <notifications@odoo-community.org>:

    Hello Odoo contributors,
    
    I am developing, deploying and fixing Odoo for a while and there is one 
    issue I haven't bothered enough to come up with a proper solution or 
    strategy.
    
    The problem is simple: I have an Odoo instance running with a module 
    that extends the res.partner model. The res.partner code of this module 
    is updated with a new field. The Odoo server is restarted and exits with 
    a "column does not exist" error.
    
    The same procedure works for modules that extend other models than 
    res.partner or res.user. As I understand the res.partner (and other) 
    tables are queried when the Odoo process starts. The SQL queries fail, 
    because the model code does not match the database schema.
    
    The solution to the problem seems obvious, before starting the Odoo 
    server with the new code you install module (odoo-bin -i ...). However, 
    automating this step in a deployment pipeline is difficult as you don't 
    know which module needs to be updated. Always updating the base module 
    seems like an overkill.
    
    Do you know this problem? Have you solved this problem?
    
    I would be glad to hear from you.
    
    Regards,
    
    Janik
    
    Here is a guide to reproduce the issue with https://odoo.build/:
    
    1. Init a new datbase and start the Odoo server: `task start db; task 
    init-db; task start native`
    
    2. Install the contacts module: `task install-module contacts`
    
    3. Stop the Odoo process.
    
    4. Add a new field to the res.partner code: `vi 
    odoo/odoo/addons/base/models/res_partner.py`
    
    ```python
    
    xy = fields.Char()
    
    ```
    
    5. Start the Odoo server: `task start native`
    
    It fails with:
    
    ```
    
    ...
    
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn...
    ```                                                        ^
    
    
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

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

    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

    _______________________________________________
    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 - 10:32 - 21 Jun 2024
  • x2many fields vertical scrollbar?

    Hi, 


    I am managing a situation where we often have a lot of lines on some main apps x2many fields (sale, picking, invoice, purchase..).


    It's not really handy when we are in a range of 60-200 lines, I just discovered that I could permanently increase the "limit" attribute on the tree-view.


    That would partially solve the problem, but in my opinion another part of the issue is that if you increase the "pager limit" to contain all lines, all the elements after the field will be pushed down in the view.

    It would be nice to have a vertical scrolling so that we can let's say set a limit of 500 lines (so they will all be loaded in the same pager) then have a limited height and be able to vertically scroll through the lines.


    Do you know any way to achieve this? Maybe someone already made a module for that?


    Have a nice day,
    Francesco Ballerini

    by Francesco Ballerini - 10:06 - 21 Jun 2024