Archives
Contributors
-
Re: [NEWS] oca-port: a new version has been released!
Hi Sébastien,Congrats for this news,> integrate odoo-module-migrator to automatically upgrade code when migrating a module (WIP)Ohpopoppopopoooo .... incrediblesuper fast, super easy, facileLe mer. 20 nov. 2024 à 15:52, Rolando Pérez Rebollo <notifications@odoo-community.org> a écrit :Wow, are there any OCA talks or similar about this? I've just discovered. From the readme looks like could assist in the migration of addons. Is It a helper that replace manual work when doing stuff like https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-16.0?
On 11/20/24 06:13, Mignon, Laurent wrote:
Thank you Sébastion for this useful and powerful tool!
On Wed, Nov 20, 2024 at 11:47 AM David Vidal <notifications@odoo-community.org> wrote:
Thanks for the great work!
El mié, 20 nov 2024 a las 11:38, Sebastien Alix (<notifications@odoo-community.org>) escribió:
Hello there!
A new version of oca-port has been released:
- CHANGELOG: https://github.com/OCA/oca-port/releases/tag/v0.16
(+ https://github.com/OCA/oca-port/releases/tag/v0.17
- fix)
- GitHub: https://github.com/OCA/oca-port
- PyPI: https://pypi.org/project/oca-port/
This new version changed the CLI parameters, and now allows to migrate modules or port commits from one repository to another thanks to the new syntax.
Let's say that origin remote is for OCA/social, and mail remote for the newly created OCA/mail repository, to check if mail_tracking is migrated or have commits to port from 16.0 to 18.0:
$ cd ~/OCA/social $ git remote add mail git@github.com:OCA/mail.git $ oca-port origin/16.0 mail/18.0 mail_tracking --verbose --fetch --dry-run
Output:
Source: origin/16.0, remote origin git@github.com:OCA/social.git Target: mail/18.0, remote mail git@github.com:OCA/mail.git Fetch origin/16.0 from git@github.com:OCA/social.git Fetch mail/18.0 from git@github.com:OCA/mail.git ⚠️ Migration of mail_tracking seems handled in this PR: https://github.com/OCA/mail/pull/1 (by trisdoan) We invite you to review this PR instead of opening a new one. Thank you! ℹ️ mail_tracking can be migrated from 16.0 to 18.0.
Seems there is already a PR open on OCA/mail to migrate this module, better to review this one before opening a new one!
Otherwise, by removing the --dry-run flag (with an optional --destination) we could handle the migration, following OCA migration guide.
If a module is already migrated, the list of missing commits (if any) grouped by PR will be listed, up to the user to port or to blacklist them if they are not relevant.
This new version also allows you to migrate modules located in a subfolder instead of the root directory, useful for private project repositories for instance.
ROADMAP:
- integrate odoo-module-migrator to automatically upgrade code when migrating a module (WIP)
- register/handle renamed modules
Ideas, bugfixes and improvements are welcome.
Have a good day,
-- Sébastien Alix Business Solutions Odoo Developer Camptocamp France SA 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
_______________________________________________
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 - 04:21 - 20 Nov 2024 - CHANGELOG: https://github.com/OCA/oca-port/releases/tag/v0.16
(+ https://github.com/OCA/oca-port/releases/tag/v0.17
- fix)
-
Re: [NEWS] oca-port: a new version has been released!
Wow, are there any OCA talks or similar about this? I've just discovered. From the readme looks like could assist in the migration of addons. Is It a helper that replace manual work when doing stuff like https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-16.0?
On 11/20/24 06:13, Mignon, Laurent wrote:
Thank you Sébastion for this useful and powerful tool!
On Wed, Nov 20, 2024 at 11:47 AM David Vidal <notifications@odoo-community.org> wrote:
Thanks for the great work!
El mié, 20 nov 2024 a las 11:38, Sebastien Alix (<notifications@odoo-community.org>) escribió:
Hello there!
A new version of oca-port has been released:
- CHANGELOG: https://github.com/OCA/oca-port/releases/tag/v0.16
(+ https://github.com/OCA/oca-port/releases/tag/v0.17
- fix)
- GitHub: https://github.com/OCA/oca-port
- PyPI: https://pypi.org/project/oca-port/
This new version changed the CLI parameters, and now allows to migrate modules or port commits from one repository to another thanks to the new syntax.
Let's say that origin remote is for OCA/social, and mail remote for the newly created OCA/mail repository, to check if mail_tracking is migrated or have commits to port from 16.0 to 18.0:
$ cd ~/OCA/social $ git remote add mail git@github.com:OCA/mail.git $ oca-port origin/16.0 mail/18.0 mail_tracking --verbose --fetch --dry-run
Output:
Source: origin/16.0, remote origin git@github.com:OCA/social.git Target: mail/18.0, remote mail git@github.com:OCA/mail.git Fetch origin/16.0 from git@github.com:OCA/social.git Fetch mail/18.0 from git@github.com:OCA/mail.git ⚠️ Migration of mail_tracking seems handled in this PR: https://github.com/OCA/mail/pull/1 (by trisdoan) We invite you to review this PR instead of opening a new one. Thank you! ℹ️ mail_tracking can be migrated from 16.0 to 18.0.
Seems there is already a PR open on OCA/mail to migrate this module, better to review this one before opening a new one!
Otherwise, by removing the --dry-run flag (with an optional --destination) we could handle the migration, following OCA migration guide.
If a module is already migrated, the list of missing commits (if any) grouped by PR will be listed, up to the user to port or to blacklist them if they are not relevant.
This new version also allows you to migrate modules located in a subfolder instead of the root directory, useful for private project repositories for instance.
ROADMAP:
- integrate odoo-module-migrator to automatically upgrade code when migrating a module (WIP)
- register/handle renamed modules
Ideas, bugfixes and improvements are welcome.
Have a good day,
-- Sébastien Alix Business Solutions Odoo Developer Camptocamp France SA 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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Ing. Rolando Pérez Rebollo - 03:50 - 20 Nov 2024 - CHANGELOG: https://github.com/OCA/oca-port/releases/tag/v0.16
(+ https://github.com/OCA/oca-port/releases/tag/v0.17
- fix)
-
FOSDEM Call for Participation: would OCA contributors join? + OCA Code Sprint in Brussels
Hello Contributors,Hope this email finds you well.As open source fan, you might know that the FOSDEM DevsRooms have been launched and there are Call for Participation with deadline by the 1st December.If you don't know what the FOSDEM is, here is their own presentation: "FOSDEM is a free event for software developers to meet, share ideas and collaborate. Every year, thousands of developers of free and open source software from all over the world gather at the event in Brussels. You don't need to register. Just turn up and join in!"The event will take place on Saturday 1st and Sunday 2nd February (unfortunately this is winter time in Brussels, so it's even worse than the OCA Days/Odoo XP event in October, weather-wise. But seeing thousands of open source developers gathering for a full weekend of conferences is hearth-warming, you'll see!).Wouldn't it be awesome to have OCA contributors pitching their knowledge during this big event? There are many DevRooms, one is Python and here is what they are looking for:* Best practices for Python developers * New developments in Python land * How to get started with a specific library/framework * Launching and growing Python communities * How Python is being used for education * Python for Hardware / Infrastructure * Security tools in Python and securing Python * Data science, AI and Machine Learning * Data engineering and management * Video Games (or game-related tooling) written in Python * MicroPython, CircuitPython, embedded software * Scaling Python applications
Another one is related to "Funding the FOSS Ecosystem" and another to Community On both those topics, if someone of you would like to co-host a topic with me, we can make it work! I am still shy to propose a talk at such an event all by myself, not being a developer and all that.On the side of FOSDEM, we might organize an OCA Code Sprint (either on 30/31st January or 3th/4th February) if several of you want to travel to Brussels and take this opportunity to code sprint together. Let me know if this might interest you by answering this 1 minute survey:Many thanks,
by Virginie Dewulf - 12:35 - 20 Nov 2024 -
Re: [NEWS] oca-port: a new version has been released!
Thank you Sébastion for this useful and powerful tool!On Wed, Nov 20, 2024 at 11:47 AM David Vidal <notifications@odoo-community.org> wrote:Thanks for the great work!El mié, 20 nov 2024 a las 11:38, Sebastien Alix (<notifications@odoo-community.org>) escribió:Hello there!
A new version of oca-port has been released:
- CHANGELOG: https://github.com/OCA/oca-port/releases/tag/v0.16
(+ https://github.com/OCA/oca-port/releases/tag/v0.17 - fix)
- GitHub: https://github.com/OCA/oca-port
- PyPI: https://pypi.org/project/oca-port/
This new version changed the CLI parameters, and now allows to migrate modules or port commits from one repository to another thanks to the new syntax.
Let's say that origin remote is for OCA/social, and mail remote for the newly created OCA/mail repository, to check if mail_tracking is migrated or have commits to port from 16.0 to 18.0:
$ cd ~/OCA/social $ git remote add mail git@github.com:OCA/mail.git $ oca-port origin/16.0 mail/18.0 mail_tracking --verbose --fetch --dry-run
Output:
Source: origin/16.0, remote origin git@github.com:OCA/social.git Target: mail/18.0, remote mail git@github.com:OCA/mail.git Fetch origin/16.0 from git@github.com:OCA/social.git Fetch mail/18.0 from git@github.com:OCA/mail.git ⚠️ Migration of mail_tracking seems handled in this PR: https://github.com/OCA/mail/pull/1 (by trisdoan) We invite you to review this PR instead of opening a new one. Thank you! ℹ️ mail_tracking can be migrated from 16.0 to 18.0.
Seems there is already a PR open on OCA/mail to migrate this module, better to review this one before opening a new one!
Otherwise, by removing the --dry-run flag (with an optional --destination) we could handle the migration, following OCA migration guide.
If a module is already migrated, the list of missing commits (if any) grouped by PR will be listed, up to the user to port or to blacklist them if they are not relevant.
This new version also allows you to migrate modules located in a subfolder instead of the root directory, useful for private project repositories for instance.
ROADMAP:
- integrate odoo-module-migrator to automatically upgrade code when migrating a module (WIP)
- register/handle renamed modules
Ideas, bugfixes and improvements are welcome.
Have a good day,
-- Sébastien Alix Business Solutions Odoo Developer Camptocamp France SA 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
by Laurent Mignon - 12:11 - 20 Nov 2024 - CHANGELOG: https://github.com/OCA/oca-port/releases/tag/v0.16
(+ https://github.com/OCA/oca-port/releases/tag/v0.17 - fix)
-
[NEWS] oca-port: a new version has been released!
Hello there!
A new version of oca-port has been released:
- CHANGELOG: https://github.com/OCA/oca-port/releases/tag/v0.16
(+ https://github.com/OCA/oca-port/releases/tag/v0.17 - fix)
- GitHub: https://github.com/OCA/oca-port
- PyPI: https://pypi.org/project/oca-port/
This new version changed the CLI parameters, and now allows to migrate modules or port commits from one repository to another thanks to the new syntax.
Let's say that origin remote is for OCA/social, and mail remote for the newly created OCA/mail repository, to check if mail_tracking is migrated or have commits to port from 16.0 to 18.0:
$ cd ~/OCA/social $ git remote add mail git@github.com:OCA/mail.git $ oca-port origin/16.0 mail/18.0 mail_tracking --verbose --fetch --dry-run
Output:
Source: origin/16.0, remote origin git@github.com:OCA/social.git Target: mail/18.0, remote mail git@github.com:OCA/mail.git Fetch origin/16.0 from git@github.com:OCA/social.git Fetch mail/18.0 from git@github.com:OCA/mail.git ⚠️ Migration of mail_tracking seems handled in this PR: https://github.com/OCA/mail/pull/1 (by trisdoan) We invite you to review this PR instead of opening a new one. Thank you! ℹ️ mail_tracking can be migrated from 16.0 to 18.0.
Seems there is already a PR open on OCA/mail to migrate this module, better to review this one before opening a new one!
Otherwise, by removing the --dry-run flag (with an optional --destination) we could handle the migration, following OCA migration guide.
If a module is already migrated, the list of missing commits (if any) grouped by PR will be listed, up to the user to port or to blacklist them if they are not relevant.
This new version also allows you to migrate modules located in a subfolder instead of the root directory, useful for private project repositories for instance.
ROADMAP:
- integrate odoo-module-migrator to automatically upgrade code when migrating a module (WIP)
- register/handle renamed modules
Ideas, bugfixes and improvements are welcome.
Have a good day,
-- Sébastien Alix Business Solutions Odoo Developer Camptocamp France SA https://www.camptocamp.com/
by Sébastien Alix - 11:37 - 20 Nov 2024 - CHANGELOG: https://github.com/OCA/oca-port/releases/tag/v0.16
(+ https://github.com/OCA/oca-port/releases/tag/v0.17 - fix)
-
Re: Automatically Generating Serial Numbers or Lots Upon MO Start in Multi-BoM Scenarios
Hi Francesco,
can you contact me directly? So we could phone in Italian, that is simpler and clear for both us.
My software is a beta version for 12.0 and I am available to migrate or else give the source code to any collaborator.
My 2 cent.
Antonio M. Vigliotti
Mobile (+39) 342.8740910
Il 19/11/2024 22:02, Francesco Di Battista ha scritto:
@Antonio,do you can resend the attach?
I can't view the files.Thanks
Il giorno lun 18 nov 2024 alle ore 11:21 Francesco Di Battista <fra.dibattista@gmail.com> ha scritto:
Hi all,
I use odoo 17 Enterprise.If they agree, I can take care of the migration to this version. It would be fantastic to see it on OCA.
Francesco
Il giorno sab 16 nov 2024 alle ore 06:58 Antonio M. Vigliotti <notifications@odoo-community.org> ha scritto:
We developed this feature on old Odoo version but we could migrate to more recent versions.
Antonio M. Vigliotti
Mobile (+39) 342.8740910
Il 15/11/2024 17:32, Hed Shefer ha scritto:
In one of our projects, we had to develop this functionality. The goal of the dev we did was to set the lot of MO based on components lots for specific BOMs.We can add it to OCA if needed.
בתאריך יום ו׳, 15 בנוב׳ 2024, 13:03, מאת Daniel Reis <notifications@odoo-community.org>:
I may be missing details, but doesn't the out of the box traceability feature solve this?
The sublevel BOMs will produce lot tracked intermediate products, and the final product lot can inspect the tree of consumed lots.
/Daniel
On 15/11/2024 08:42, Francesco Di Battista wrote:
Dear OCA Community,
I hope this message finds you well.
I am reaching out to inquire about a specific functionality in Odoo regarding serial numbers and lot tracking in manufacturing processes. My use case involves the following scenario:
When starting a Manufacturing Order (MO) for a product, I would like to automatically generate a serial number (or lot number) for the final product. The product in question has multiple Bills of Materials (BoMs), and during the manufacturing process, it might be necessary to associate serial numbers with the components that make up the BoM.
Ideally, the serial number or lot of the final product should retain the ability to reference and track all the serial numbers of the sub-products used in its production. This would be extremely useful for traceability and managing complex manufacturing flows.
Is there any existing functionality or module within Odoo or OCA that can address this requirement? Alternatively, any guidance or recommendations for customization to achieve this would also be greatly appreciated.
Looking forward to your insights and suggestions.
Thank you in advance for your help!
Best regards,
Francesco_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING PARTNER>> Schedule time on my calendar.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais![[Logo OpenSourceIntegrators.com]](https://www.opensourceintegrators.com/images/opensource-logo-2022.svg)
_______________________________________________
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 Antonio M. Vigliotti - 11:26 - 20 Nov 2024 -
[14.0 CE] product_list_pricelist_price
Hi,did some one migrate https://github.com/OCA/product-attribute/tree/13.0/product_list_pricelist_price to version 14.0 and have the chance to share it ?I remember that I've tried to use it on v14.0 and spotted some incompatibilities, if I remember well the GUI was crashing when adding a new pricelist column unless odoo was restarted. I remember that I spent some time on it but didn't find a solution to it.Thanks--Francesco B
by Francesco Ballerini - 11:11 - 20 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
Hello Francesco,
I have seen your message right now, and I would like to thank you so much for not only your answer, but also for you writing the code I should do. I do not know how could I pay you back this favor that you have done for me.I rely on the community because I am in my beginnings and because of everything that my company JLBB ERP has given me through good collaboration, I am now checking it out. Do not doubt that everything I can contribute, you will find me here.Thank you Francesco for the help.Salutations to the community.El 20/11/2024 0:02 CET Francesco Ballerini <notifications@odoo-community.org> escribió:I apologize, it is now clear to me also that you need both the search from a custom field and the way the name is displayed, but the search is indeed prioritized.As Daniel and Xavier pointed out, in Odoo 17.0 you can already submit the "ref" field (field label on GUI is "Reference") and get the right record. E.g. if you have a contact named John Doe with Reference set on "ab-001" and you search for "ab-001" in the contacts search or dropdown you will fetch John Doe.You could migrate your "x_cliente_interno" data into the "ref" field, and this would automatically unlock the search feature. However if you need to keep this data in a specific custom field you will need to override _name_search() method.In every case you will also need to override _compute_display_name if you want to also show the code before the field. I provided a couple of snippet below (just as an example, especially the _name_search override needs to be refined).Let me point out another thing: from the field name I assume you are using a field defined from GUI, unfortunately it's not recommended to use those kind of fields in python methods as it will easily lead to inconsistencies and bugs (e.g. if you delete field from db and not remove it from python methods..). This means that if you want to use a custom field in _name_search() override you should migrate data to a standard field aniway.
This is an example of what you might do on a custom module. As you can see the _name_search() implementation has to be refined while the_compute_display_name method will work as is.If you decide to migrate data into the "ref" field you can only implement _compute_display_name by replacing "cliente_interno" with "ref" and you do not need to implement _name_search() in this case.from odoo import models, fields, apifrom odoo.osv import expression
class ResPartner(models.Model):_inherit = "res.partner"
cliente_interno = fields.Char() # use a standard field for consistency
@api.depends("name", "cliente_interno")def _compute_display_name(self):"""Show reference code before partner name"""super()._compute_display_name()for partner in self:name = partner.name or "unknown"cliente_interno = f"[{partner.cliente_interno}] " if partner.cliente_interno else ""# !! Disclaimer !!#I f you copy this code and change it DO NOT ASSIGN the value of partner.name,# that would compromise your datas. Only re-assign partner.display_namepartner.display_name = cliente_interno + name
@api.modeldef _name_search(self, name, domain=None, operator='ilike', limit=None, order=None):"""Add custom field `cliente_interno` to the search domain"""domain = expression.OR([domain or [], [("cliente_interno", operator, name)]])# this doesn't work properly, it seems like the domain we pass gets overridden,# might take this as example and adjust by debugging/find more examples on source codereturn super()._name_search(name, domain=domain, operator=operator, limit=limit, order=order)Regards--FrancescoIl giorno mar 19 nov 2024 alle ore 14:13 Daniel Reis <notifications@odoo-community.org> ha scritto:From your description, it feels like this is already available in standard Odoo:
The "ref" field is to be used for Client codes
The code is no longer presented in front of the name.
I think an OCA module is needed to bring that feature back.
/Daniel
On 19/11/2024 09:22, Redes Sociales JLBBERP wrote:Hello everyone,I am writing this message because I need assistance with modifying how searching a client while doing a budget works.What I am trying to do is, instead of searching just by the name, I want it to work like the following: I made a custom field called "x_cliente_interno", which is a number to identify the client, and I would like to make the search work like how product search works: If you write either the product's ID or the product's name, it will show you both fields merged from the data you wrote. Something like this:And when you select it, it shows the data like this:To sum up, what I am trying to do is that when you search a client, the search shows you the field "x_cliente_interno" behind the client name, like this: "[x_cliente_interno] client name" and it should also stay like in the second image when selected.Thanks in advance for the help._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING PARTNER>> Schedule time on my calendar.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais _______________________________________________
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 Alejandro Párraga Alcázar - 09:26 - 20 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
> I apologize, it is now clear to me also that you need both the search from a > custom field and the way the name is displayed, but the search is indeed > prioritized. anybody interested in only the searching part can use https://apps.odoo.com/apps/modules/16.0/base_name_search_improved without typing any code. The migration to v17 happened in https://github.com/OCA/server-tools/pull/2831 Could be worthwhile to add a companion to this module allowing to configure the display name via UI too. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 02:55 - 20 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
I apologize, it is now clear to me also that you need both the search from a custom field and the way the name is displayed, but the search is indeed prioritized.As Daniel and Xavier pointed out, in Odoo 17.0 you can already submit the "ref" field (field label on GUI is "Reference") and get the right record. E.g. if you have a contact named John Doe with Reference set on "ab-001" and you search for "ab-001" in the contacts search or dropdown you will fetch John Doe.You could migrate your "x_cliente_interno" data into the "ref" field, and this would automatically unlock the search feature. However if you need to keep this data in a specific custom field you will need to override _name_search() method.In every case you will also need to override _compute_display_name if you want to also show the code before the field. I provided a couple of snippet below (just as an example, especially the _name_search override needs to be refined).Let me point out another thing: from the field name I assume you are using a field defined from GUI, unfortunately it's not recommended to use those kind of fields in python methods as it will easily lead to inconsistencies and bugs (e.g. if you delete field from db and not remove it from python methods..). This means that if you want to use a custom field in _name_search() override you should migrate data to a standard field aniway.This is an example of what you might do on a custom module. As you can see the _name_search() implementation has to be refined while the_compute_display_name method will work as is.If you decide to migrate data into the "ref" field you can only implement _compute_display_name by replacing "cliente_interno" with "ref" and you do not need to implement _name_search() in this case.from odoo import models, fields, apifrom odoo.osv import expressionclass ResPartner(models.Model):_inherit = "res.partner"cliente_interno = fields.Char() # use a standard field for consistency@api.depends("name", "cliente_interno")def _compute_display_name(self):"""Show reference code before partner name"""super()._compute_display_name()for partner in self:name = partner.name or "unknown"cliente_interno = f"[{partner.cliente_interno}] " if partner.cliente_interno else ""# !! Disclaimer !!#I f you copy this code and change it DO NOT ASSIGN the value of partner.name,# that would compromise your datas. Only re-assign partner.display_namepartner.display_name = cliente_interno + name@api.modeldef _name_search(self, name, domain=None, operator='ilike', limit=None, order=None):"""Add custom field `cliente_interno` to the search domain"""domain = expression.OR([domain or [], [("cliente_interno", operator, name)]])# this doesn't work properly, it seems like the domain we pass gets overridden,# might take this as example and adjust by debugging/find more examples on source codereturn super()._name_search(name, domain=domain, operator=operator, limit=limit, order=order)Regards--FrancescoIl giorno mar 19 nov 2024 alle ore 14:13 Daniel Reis <notifications@odoo-community.org> ha scritto:From your description, it feels like this is already available in standard Odoo:
The "ref" field is to be used for Client codes
The code is no longer presented in front of the name.
I think an OCA module is needed to bring that feature back.
/Daniel
On 19/11/2024 09:22, Redes Sociales JLBBERP wrote:
Hello everyone,I am writing this message because I need assistance with modifying how searching a client while doing a budget works.What I am trying to do is, instead of searching just by the name, I want it to work like the following: I made a custom field called "x_cliente_interno", which is a number to identify the client, and I would like to make the search work like how product search works: If you write either the product's ID or the product's name, it will show you both fields merged from the data you wrote. Something like this:And when you select it, it shows the data like this:To sum up, what I am trying to do is that when you search a client, the search shows you the field "x_cliente_interno" behind the client name, like this: "[x_cliente_interno] client name" and it should also stay like in the second image when selected.Thanks in advance for the help._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING PARTNER>> Schedule time on my calendar.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais
_______________________________________________
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:00 - 20 Nov 2024 -
Re: Automatically Generating Serial Numbers or Lots Upon MO Start in Multi-BoM Scenarios
@Antonio,do you can resend the attach?I can't view the files.ThanksIl giorno lun 18 nov 2024 alle ore 11:21 Francesco Di Battista <fra.dibattista@gmail.com> ha scritto:Hi all,I use odoo 17 Enterprise.If they agree, I can take care of the migration to this version. It would be fantastic to see it on OCA.FrancescoIl giorno sab 16 nov 2024 alle ore 06:58 Antonio M. Vigliotti <notifications@odoo-community.org> ha scritto:We developed this feature on old Odoo version but we could migrate to more recent versions.
Antonio M. Vigliotti
Mobile (+39) 342.8740910
Il 15/11/2024 17:32, Hed Shefer ha scritto:
In one of our projects, we had to develop this functionality. The goal of the dev we did was to set the lot of MO based on components lots for specific BOMs.We can add it to OCA if needed.
בתאריך יום ו׳, 15 בנוב׳ 2024, 13:03, מאת Daniel Reis <notifications@odoo-community.org>:
I may be missing details, but doesn't the out of the box traceability feature solve this?
The sublevel BOMs will produce lot tracked intermediate products, and the final product lot can inspect the tree of consumed lots.
/Daniel
On 15/11/2024 08:42, Francesco Di Battista wrote:
Dear OCA Community,
I hope this message finds you well.
I am reaching out to inquire about a specific functionality in Odoo regarding serial numbers and lot tracking in manufacturing processes. My use case involves the following scenario:
When starting a Manufacturing Order (MO) for a product, I would like to automatically generate a serial number (or lot number) for the final product. The product in question has multiple Bills of Materials (BoMs), and during the manufacturing process, it might be necessary to associate serial numbers with the components that make up the BoM.
Ideally, the serial number or lot of the final product should retain the ability to reference and track all the serial numbers of the sub-products used in its production. This would be extremely useful for traceability and managing complex manufacturing flows.
Is there any existing functionality or module within Odoo or OCA that can address this requirement? Alternatively, any guidance or recommendations for customization to achieve this would also be greatly appreciated.
Looking forward to your insights and suggestions.
Thank you in advance for your help!
Best regards,
Francesco_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING PARTNER>> Schedule time on my calendar.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais _______________________________________________
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 fra.dibattista - 10:01 - 19 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
From your description, it feels like this is already available in standard Odoo:
The "ref" field is to be used for Client codes
The code is no longer presented in front of the name.
I think an OCA module is needed to bring that feature back.
/Daniel
On 19/11/2024 09:22, Redes Sociales JLBBERP wrote:
Hello everyone,I am writing this message because I need assistance with modifying how searching a client while doing a budget works.What I am trying to do is, instead of searching just by the name, I want it to work like the following: I made a custom field called "x_cliente_interno", which is a number to identify the client, and I would like to make the search work like how product search works: If you write either the product's ID or the product's name, it will show you both fields merged from the data you wrote. Something like this:And when you select it, it shows the data like this:To sum up, what I am trying to do is that when you search a client, the search shows you the field "x_cliente_interno" behind the client name, like this: "[x_cliente_interno] client name" and it should also stay like in the second image when selected.Thanks in advance for the help._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING PARTNER>> Schedule time on my calendar.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais
by Daniel Reis - 02:11 - 19 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
I think we should ask @Redes to clarify what he actually needs, I have read his message like 3 times before answering and I still have doubt: from the start of his message it seems that he needs to change "how the field is searched" , but accordingly to his example it seems that he actually needs to change "the way the field is displayed".I am aware that _compute_display_name() has a different purpose than name_search(), it all depends on what he needs.If he only needs to change the way the field is displayed AFTER the record has been selected, _compute_display_name() will fit the case and I could provide a snippet. On the other hand if the goal is to change the way the field is searched (not how the field is displayed) please take the other answers as correct and ignore mine.Regards--FrancescoIl giorno mar 19 nov 2024 alle ore 11:53 Xavier Brochard <notifications@odoo-community.org> ha scritto:
Hi in case you just need a shortcut for customers, you can use the 'ref' field in res.partner. Search its content in name or company name. Beware, it is case sensitive. --- Librement, Xavier Brochard xavier@alternatif.org La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre Rosnay) Le 19.11.2024 10:22, Redes Sociales JLBBERP a écrit : > Hello everyone, > > > I am writing this message because I need assistance with modifying how > searching a client while doing a budget works. > > > What I am trying to do is, instead of searching just by the name, I > want it to work like the following: I made a custom field called > "x_cliente_interno", which is a number to identify the client, and I > would like to make the search work like how product search works: If > you write either the product's ID or the product's name, it will show > you both fields merged from the data you wrote. Something like this: > > > > > > And when you select it, it shows the data like this: > > > > > > To sum up, what I am trying to do is that when you search a client, > the search shows you the field "x_cliente_interno" behind the client > name, like this: "[x_cliente_interno] client name" and it should also > stay like in the second image when selected. > > > Thanks in advance for the help. > > > > > _______________________________________________ > 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
_______________________________________________
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 - 01:26 - 19 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
If you are in search filter then it is basic. Partner filter has below for example. If you do not then you will need to modify args passed to either search or _search method. Do not mess with display_name, it is a different purpose.<field name="name"filter_domain="['|', '|', '|', '|', ('display_name', 'ilike', self), ('ref', 'ilike', self), ('email', 'ilike', self), ('vat', 'ilike', self), ('company_registry', 'ilike', self)]"/>
On Tue, Nov 19, 2024 at 10:22 PM Redes Sociales JLBBERP <notifications@odoo-community.org> wrote:Hello everyone,I am writing this message because I need assistance with modifying how searching a client while doing a budget works.What I am trying to do is, instead of searching just by the name, I want it to work like the following: I made a custom field called "x_cliente_interno", which is a number to identify the client, and I would like to make the search work like how product search works: If you write either the product's ID or the product's name, it will show you both fields merged from the data you wrote. Something like this:And when you select it, it shows the data like this:To sum up, what I am trying to do is that when you search a client, the search shows you the field "x_cliente_interno" behind the client name, like this: "[x_cliente_interno] client name" and it should also stay like in the second image when selected.Thanks in advance for the help._______________________________________________
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 - 11:36 - 19 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
Hi,you can implement the search in Many2one fields of models via adjustments to name_search() or _name_search().Best RegardsChristian ZöllnerVon: "Redes Sociales JLBBERP" <notifications@odoo-community.org>
An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Gesendet: Dienstag, 19. November 2024 11:22:43
Betreff: Re: [Odoo CE 17.0] Help needed with client search on budgetsHello Francesco,I have read your message, and I thank you for answering my problem. The thing is: I would need to be specified how to extend the method you mentioned (_compute_display_name()) so I can achieve my search display modification for budgets.El 19/11/2024 11:02 CET Francesco Ballerini <notifications@odoo-community.org> escribió:Hi,I think you can achieve your goal by extending in your model the ORM method _compute_display_name which allows you to choose how the name will be represented when searching for a record. It should also affect the record visualization once selected.Note that if this requirement should apply to only specific views you could add a context attribute (e.g. context="{'show_x_cliente_interno: True'}" ) to the XML definition of the field node, it will be propagated to the _compute_display_name() method when searching on that field so you can choose whether or not show the client reference before the record name.Feel free to ask again if you need more specific information on how to properly extend method _compute_display_name() or adding context to the field node.Regards--Francesco
Il giorno mar 19 nov 2024 alle ore 10:23 Redes Sociales JLBBERP <notifications@odoo-community.org> ha scritto:Hello everyone,I am writing this message because I need assistance with modifying how searching a client while doing a budget works.What I am trying to do is, instead of searching just by the name, I want it to work like the following: I made a custom field called "x_cliente_interno", which is a number to identify the client, and I would like to make the search work like how product search works: If you write either the product's ID or the product's name, it will show you both fields merged from the data you wrote. Something like this:And when you select it, it shows the data like this:To sum up, what I am trying to do is that when you search a client, the search shows you the field "x_cliente_interno" behind the client name, like this: "[x_cliente_interno] client name" and it should also stay like in the second image when selected.Thanks in advance for the help._______________________________________________
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 Christian Zöllner - 11:31 - 19 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
Hello Francesco,I have read your message, and I thank you for answering my problem. The thing is: I would need to be specified how to extend the method you mentioned (_compute_display_name()) so I can achieve my search display modification for budgets.El 19/11/2024 11:02 CET Francesco Ballerini <notifications@odoo-community.org> escribió:Hi,I think you can achieve your goal by extending in your model the ORM method _compute_display_name which allows you to choose how the name will be represented when searching for a record. It should also affect the record visualization once selected.Note that if this requirement should apply to only specific views you could add a context attribute (e.g. context="{'show_x_cliente_interno: True'}" ) to the XML definition of the field node, it will be propagated to the _compute_display_name() method when searching on that field so you can choose whether or not show the client reference before the record name.Feel free to ask again if you need more specific information on how to properly extend method _compute_display_name() or adding context to the field node.Regards--Francesco
Il giorno mar 19 nov 2024 alle ore 10:23 Redes Sociales JLBBERP <notifications@odoo-community.org> ha scritto:Hello everyone,I am writing this message because I need assistance with modifying how searching a client while doing a budget works.What I am trying to do is, instead of searching just by the name, I want it to work like the following: I made a custom field called "x_cliente_interno", which is a number to identify the client, and I would like to make the search work like how product search works: If you write either the product's ID or the product's name, it will show you both fields merged from the data you wrote. Something like this:And when you select it, it shows the data like this:To sum up, what I am trying to do is that when you search a client, the search shows you the field "x_cliente_interno" behind the client name, like this: "[x_cliente_interno] client name" and it should also stay like in the second image when selected.Thanks in advance for the help._______________________________________________
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 Alejandro Párraga Alcázar - 11:21 - 19 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
Hi,I think you can achieve your goal by extending in your model the ORM method _compute_display_name which allows you to choose how the name will be represented when searching for a record. It should also affect the record visualization once selected.Note that if this requirement should apply to only specific views you could add a context attribute (e.g. context="{'show_x_cliente_interno: True'}" ) to the XML definition of the field node, it will be propagated to the _compute_display_name() method when searching on that field so you can choose whether or not show the client reference before the record name.Feel free to ask again if you need more specific information on how to properly extend method _compute_display_name() or adding context to the field node.Regards--FrancescoIl giorno mar 19 nov 2024 alle ore 10:23 Redes Sociales JLBBERP <notifications@odoo-community.org> ha scritto:Hello everyone,I am writing this message because I need assistance with modifying how searching a client while doing a budget works.What I am trying to do is, instead of searching just by the name, I want it to work like the following: I made a custom field called "x_cliente_interno", which is a number to identify the client, and I would like to make the search work like how product search works: If you write either the product's ID or the product's name, it will show you both fields merged from the data you wrote. Something like this:And when you select it, it shows the data like this:To sum up, what I am trying to do is that when you search a client, the search shows you the field "x_cliente_interno" behind the client name, like this: "[x_cliente_interno] client name" and it should also stay like in the second image when selected.Thanks in advance for the help.
_______________________________________________
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:01 - 19 Nov 2024
