Archives
Contributors
-
Re: Github runners
Hello everyone,This is an annoying situation, which you can track here: https://github.com/OCA/oca-addons-repo-template/issues/250I'll post there as the situation evolves.Best regards,-StéphaneOn Tue, Apr 30, 2024 at 9:46 AM Roussel, Denis <notifications@odoo-community.org> wrote:Hi all folks,@OCA/board Is there something changed about github runners configuration?Since yesterday, runners seems to take a long time to get available resource:Thanks for your support.--_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 09:56 - 30 Apr 2024 -
Re: Github runners
Ok, thanks to @Stephane :On Tue, Apr 30, 2024 at 9:44 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:Hi all folks,@OCA/board Is there something changed about github runners configuration?Since yesterday, runners seems to take a long time to get available resource:Thanks for your support.----
by Denis Roussel - 09:51 - 30 Apr 2024 -
Github runners
Hi all folks,@OCA/board Is there something changed about github runners configuration?Since yesterday, runners seems to take a long time to get available resource:Thanks for your support.--
by Denis Roussel - 09:45 - 30 Apr 2024 -
Re: Form field conditional formatting
David, thanks a lot. That is quite close to what I need. I need to highlight some fields to draw attention to them. I need them filled in but not hard-required because the user has the possibility to save the record as a "draft". To be able to go to next stage the fields need to be filled in. Best regards Radovan On piatok 26. apríla 2024 10:21:59 CEST David Beal wrote: > Hi Radovan, > Have you tried this module ? > https://github.com/OCA/web/blob/16.0/web_apply_field_style/README.rst [1] > Not sure it solves all your cases, but if you have many fields to highlight > and if you prefer python over xml override ... Regards > David BEAL Akretion [2] > Consultant ERP Odoo > > Le lun. 22 avr. 2024 à 17:17, Holger Brunn < notifications@odoo-community.org [3] > a écrit : > > OK, I found it's working. But it's working a bit differently than what I'd > > need. It colors the text in Char or Integer fields. It does nothing to > > fields that are empty or to let's say Selection fields. I am looking for a > > way to highlight some fields to draw attention to them even if they are > > empty - so maybe setting the background on them. Or add some icon besides > > them... Any ideas are welcome. > > don't forget plain css: > div.o_form_editable div[name="yourfield"]:not(.o_readonly_modifier) input { > background: red!important; > } > or combine this with the conditional bootstrap classes > div[name="yourfield"].text-danger { > background: red!important; > } > Up until v15 a form would have class o_form_model_name, which made it easy > to make this model specific. For ancient Odoo for exactly this use case I > made https://github.com/OCA/web/tree/6.1/web_widget_classes [4] > which you might want to resurrect and rename for this purpose. > But if you go into the module writing business for this anyways, probably > better patch > https://github.com/OCA/OCB/blob/17.0/addons/web/static/src/views/fields/ > field.js#L133 [5] > and allow something like > <field name="yourfield" o-class-yourclass="expression" /> > which would be much more versatile > > -- > Your partner for the hard Odoo problems > https://hunki-enterprises.com [6] > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [7] > Post to: mailto: contributors@odoo-community.org [8] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [9] > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [10] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [11] > > > > [1] https://github.com/OCA/web/blob/16.0/web_apply_field_style/README.rst > [2] https://akretion.com/fr > [3] mailto:notifications@odoo-community.org > [4] https://github.com/OCA/web/tree/6.1/web_widget_classes > [5] > https://github.com/OCA/OCB/blob/17.0/addons/web/static/src/views/fields/fie > ld.js#L133 [6] https://hunki-enterprises.com > [7] https://odoo-community.org/groups/contributors-15 > [8] mailto:contributors@odoo-community.org > [9] https://odoo-community.org/groups?unsubscribe > [10] https://odoo-community.org/groups/contributors-15 > [11] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 10:36 - 26 Apr 2024 -
Re: Form field conditional formatting
Hi Radovan,Have you tried this module ?Not sure it solves all your cases, but if you have many fields to highlight and if you prefer python over xml override ...Le lun. 22 avr. 2024 à 17:17, Holger Brunn <notifications@odoo-community.org> a écrit :> OK, I found it's working. But it's working a bit differently than what I'd > need. It colors the text in Char or Integer fields. It does nothing to > fields that are empty or to let's say Selection fields. I am looking for a > way to highlight some fields to draw attention to them even if they are > empty - so maybe setting the background on them. Or add some icon besides > them... Any ideas are welcome. don't forget plain css: div.o_form_editable div[name="yourfield"]:not(.o_readonly_modifier) input { background: red!important; } or combine this with the conditional bootstrap classes div[name="yourfield"].text-danger { background: red!important; } Up until v15 a form would have class o_form_model_name, which made it easy to make this model specific. For ancient Odoo for exactly this use case I made https://github.com/OCA/web/tree/6.1/web_widget_classes which you might want to resurrect and rename for this purpose. But if you go into the module writing business for this anyways, probably better patch https://github.com/OCA/OCB/blob/17.0/addons/web/static/src/views/fields/ field.js#L133 and allow something like <field name="yourfield" o-class-yourclass="expression" /> which would be much more versatile -- Your partner for the hard Odoo problems https://hunki-enterprises.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 David BEAL - 10:20 - 26 Apr 2024 -
Re: The OCA Functional Working Group asks for your help!
Hello,just a word to also encourage mkdocs if we aim at something additional to the current README markdown system. As Graeme said mkdocs is popular, capable and simple to manage (we really need to avoid big new tools that would be an infrastructure burden to manage). I think the README are slowly being improved, even if it's still by the module tech authors. In OCA/l10n-brazil we try to slowly improve these README for instance. At some point improving these README is lowering the entry barrier to the OCA and it somewhat makes sense that this entry barrier is lowered at the same time than the code is cleaned up and migrated so that non alien people will eventually succeed in their project with the OCA instead of just accumulating frustration by trying to attract at all cost people which will not make it with the current ecosystem (something that Odoo SA does quite a lot themselves in fact). So I mean it is not that bad if that documentation pace isn't as fast as some people who don't use to deliver real projects may dream...On Wed, Apr 24, 2024 at 11:27 AM Graeme Gellatly <notifications@odoo-community.org> wrote:I second mkdocs. All my non technical staff use it to build docs. Most.jist write markdown bit some use a specialised markdown editor although that seems to fail lintimg quite a bit.It is trivial to automate linting and deploy on merge.On Wed, 24 Apr 2024, 6:52 am Victor Champonnois, <notifications@odoo-community.org> wrote:Hello Julie,
>Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?
I think Weblate directly commits on the main branch, it does not create a PR.
As Andreas says, the edit functionality in Github seems like the simplest approach. However, it requires to create a fork of the repo, and to make a PR, so it's still a big barrier.
Victor Champonnois - Coop IT Easy Tel : +32 475 81 01 12
On 24/04/24 07:44, Andreas Perhab wrote:
Hi Julie,
I think the edit button in github does most of the forking work for you and even helps with creating a PR when one is finished editing the readme (really any markdown file).
It puts images into /assets/{number}/{uuid} so that might need changing or we could just accept this additional directory.
regards Andreas
On Tue, 23 Apr 2024 at 19:32, Julie LeBrun <notifications@odoo-community.org> wrote:
Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?
Hello everybody!
During the last OCA Days, the OCA Functional Working Group (FWG) presented the work made on the Documentation Project.
This project was created by the FWG to help and attract functional people to contribute to modules documentation.
2 main options were analyzed
Using the existing Read Me file in the code so we have only one module documentation which regroups technical and functional information.
Using the GitHub Wiki on the repositories which could be really easy to put in place and use.
The decision was made to use the existing Read Me but to convert it into Markdown so it could be easier to use and to add images.
Following this decision, an issue was opened in GitHub about the use of the Wiki instead of Read Me : https://github.com/OCA/maintainer-tools/issues/606
BUT, we still have a big issue regarding this solution: the process to contribute to Read Me is really, really complicated for non-technicals.
You need to have a Github account and sign the OCA CLA
You would have to fork the repository (well, here we already have lost most of the non-technical people).
Then edit the files of the Read Me using the Web Editor (so you can add images).
Download your images in the right folder than insert them into the file by Drag & Drop
Create a commit and a PR.
Finally, the changes would need to be approved by contributors who have those access rights.
So, we were thinking: if we add a Markdown tool that can be used to edit Read Me files and automatically push the changes into GitHub a little bit like the Weblate tool, we could combine the PROS of both options analyzed.
Does anyone have any idea of this kind of tool?
Thank you in advance for your help.
The OCA Functional Working Group
_______________________________________________
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
--Raphaël ValyiFounder and consultant
by "Raphaël Valyi" <rvalyi@akretion.com> - 05:16 - 25 Apr 2024 -
Re: The OCA Functional Working Group asks for your help!
I second mkdocs. All my non technical staff use it to build docs. Most.jist write markdown bit some use a specialised markdown editor although that seems to fail lintimg quite a bit.It is trivial to automate linting and deploy on merge.On Wed, 24 Apr 2024, 6:52 am Victor Champonnois, <notifications@odoo-community.org> wrote:Hello Julie,
>Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?
I think Weblate directly commits on the main branch, it does not create a PR.
As Andreas says, the edit functionality in Github seems like the simplest approach. However, it requires to create a fork of the repo, and to make a PR, so it's still a big barrier.
Victor Champonnois - Coop IT Easy Tel : +32 475 81 01 12
On 24/04/24 07:44, Andreas Perhab wrote:
Hi Julie,
I think the edit button in github does most of the forking work for you and even helps with creating a PR when one is finished editing the readme (really any markdown file).
It puts images into /assets/{number}/{uuid} so that might need changing or we could just accept this additional directory.
regards Andreas
On Tue, 23 Apr 2024 at 19:32, Julie LeBrun <notifications@odoo-community.org> wrote:
Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?
Hello everybody!
During the last OCA Days, the OCA Functional Working Group (FWG) presented the work made on the Documentation Project.
This project was created by the FWG to help and attract functional people to contribute to modules documentation.
2 main options were analyzed
Using the existing Read Me file in the code so we have only one module documentation which regroups technical and functional information.
Using the GitHub Wiki on the repositories which could be really easy to put in place and use.
The decision was made to use the existing Read Me but to convert it into Markdown so it could be easier to use and to add images.
Following this decision, an issue was opened in GitHub about the use of the Wiki instead of Read Me : https://github.com/OCA/maintainer-tools/issues/606
BUT, we still have a big issue regarding this solution: the process to contribute to Read Me is really, really complicated for non-technicals.
You need to have a Github account and sign the OCA CLA
You would have to fork the repository (well, here we already have lost most of the non-technical people).
Then edit the files of the Read Me using the Web Editor (so you can add images).
Download your images in the right folder than insert them into the file by Drag & Drop
Create a commit and a PR.
Finally, the changes would need to be approved by contributors who have those access rights.
So, we were thinking: if we add a Markdown tool that can be used to edit Read Me files and automatically push the changes into GitHub a little bit like the Weblate tool, we could combine the PROS of both options analyzed.
Does anyone have any idea of this kind of tool?
Thank you in advance for your help.
The OCA Functional Working Group
_______________________________________________
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 "Graeme Gellatly" <graeme@moahub.nz> - 04:26 - 24 Apr 2024 -
Re: The OCA Functional Working Group asks for your help!
Hello Julie,
>Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?
I think Weblate directly commits on the main branch, it does not create a PR.
As Andreas says, the edit functionality in Github seems like the simplest approach. However, it requires to create a fork of the repo, and to make a PR, so it's still a big barrier.
Victor Champonnois - Coop IT Easy Tel : +32 475 81 01 12
On 24/04/24 07:44, Andreas Perhab wrote:
Hi Julie,
I think the edit button in github does most of the forking work for you and even helps with creating a PR when one is finished editing the readme (really any markdown file).
It puts images into /assets/{number}/{uuid} so that might need changing or we could just accept this additional directory.
regards Andreas
On Tue, 23 Apr 2024 at 19:32, Julie LeBrun <notifications@odoo-community.org> wrote:
Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?
Hello everybody!
During the last OCA Days, the OCA Functional Working Group (FWG) presented the work made on the Documentation Project.
This project was created by the FWG to help and attract functional people to contribute to modules documentation.
2 main options were analyzed
Using the existing Read Me file in the code so we have only one module documentation which regroups technical and functional information.
Using the GitHub Wiki on the repositories which could be really easy to put in place and use.
The decision was made to use the existing Read Me but to convert it into Markdown so it could be easier to use and to add images.
Following this decision, an issue was opened in GitHub about the use of the Wiki instead of Read Me : https://github.com/OCA/maintainer-tools/issues/606
BUT, we still have a big issue regarding this solution: the process to contribute to Read Me is really, really complicated for non-technicals.
You need to have a Github account and sign the OCA CLA
You would have to fork the repository (well, here we already have lost most of the non-technical people).
Then edit the files of the Read Me using the Web Editor (so you can add images).
Download your images in the right folder than insert them into the file by Drag & Drop
Create a commit and a PR.
Finally, the changes would need to be approved by contributors who have those access rights.
So, we were thinking: if we add a Markdown tool that can be used to edit Read Me files and automatically push the changes into GitHub a little bit like the Weblate tool, we could combine the PROS of both options analyzed.
Does anyone have any idea of this kind of tool?
Thank you in advance for your help.
The OCA Functional Working Group
_______________________________________________
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 Victor - 03:51 - 24 Apr 2024 -
Re: The OCA Functional Working Group asks for your help!
Hello Julie.Thank you very much (and the rest of FWG) for the work in this regard. Indeed better tooling for functional docs would help a lot!My suggestion would be to have a plain hierarchy where OCA's docs exist.The backend for that hierarchy could be some SSG that renders those Markdowns into something beautiful.I have experience with 2 SSG: hugo (I use it for my blog) and mkdocs (I use it for Copier docs). I think that for our purpose, mkdocs fits better. One nice thing about those 2 SSGs is that both support translations (which is something that, surprisingly, Odoo built-in README doesn't).Regarding the UI for interaction, in my blog I use https://decapcms.org/ which is open source and very simple to setup. It basically provides an alternate UI for SSG, and the backend for that UI is github or gitlab (using its API as a controller, using Git as a storage backend, and Markdown as a storage format). It allows meda files management, and it even includes support for what they call "Editorial Workflow", which means that new posts or pages are added in a PR that advances through different stages (and it uses github labels to know the stage).So basically you'd have the same github PR UI for us techies to keep on going with our same code/review/merge flows we know and love, but you'd have let's say another UI for Github that would do the techie work for you if you're not a techie (or are one of those techie weirdos that love fancy UIs).Then just have a CI that renders those markdowns that land in the main branch of https://github.com/OCA/docs into a website published at oca.github.io/docs when merged.Even nicer, each module could have its space, and our dear bot could just publish our module's READMEs as the landing page for the same modules in that same project when doing its post-merge jobs.Of course this requires some setup that could be completely saved if you just go to wordpress.com, open an account and pay whatever they ask you. Or if you open up a google docs per module where functionals can go and write. Or you could even install a wiki system. Yikes, we could even create wiki modules for Odoo and install them in odoo-community.org and let our contributors contribute there the wiki.Many options, I hope some one of those help :)
by Jairo Llopis - 02:25 - 24 Apr 2024 -
Re: The OCA Functional Working Group asks for your help!
Hi Julie,I think the edit button in github does most of the forking work for you and even helps with creating a PR when one is finished editing the readme (really any markdown file).It puts images into /assets/{number}/{uuid} so that might need changing or we could just accept this additional directory.regards AndreasOn Tue, 23 Apr 2024 at 19:32, Julie LeBrun <notifications@odoo-community.org> wrote:Do you know of any tool that could easily allow to edit and create PRs of README files in GitHub without the need of having GitHub knowledge? Something similar to what Weblate does for .po files ?Hello everybody!
During the last OCA Days, the OCA Functional Working Group (FWG) presented the work made on the Documentation Project.
This project was created by the FWG to help and attract functional people to contribute to modules documentation.
2 main options were analyzed
Using the existing Read Me file in the code so we have only one module documentation which regroups technical and functional information.
Using the GitHub Wiki on the repositories which could be really easy to put in place and use.
The decision was made to use the existing Read Me but to convert it into Markdown so it could be easier to use and to add images.
Following this decision, an issue was opened in GitHub about the use of the Wiki instead of Read Me : https://github.com/OCA/maintainer-tools/issues/606
BUT, we still have a big issue regarding this solution: the process to contribute to Read Me is really, really complicated for non-technicals.
You need to have a Github account and sign the OCA CLA
You would have to fork the repository (well, here we already have lost most of the non-technical people).
Then edit the files of the Read Me using the Web Editor (so you can add images).
Download your images in the right folder than insert them into the file by Drag & Drop
Create a commit and a PR.
Finally, the changes would need to be approved by contributors who have those access rights.
So, we were thinking: if we add a Markdown tool that can be used to edit Read Me files and automatically push the changes into GitHub a little bit like the Weblate tool, we could combine the PROS of both options analyzed.
Does anyone have any idea of this kind of tool?
Thank you in advance for your help.
The OCA Functional Working Group
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Andreas Perhab" <a.perhab@wt-io-it.at> - 07:41 - 24 Apr 2024 -
Re: purchasing a set of products
Hi Frederik! Am 23.04.24 um 15:41 schrieb Frederik Kramer: > Hi Jan, > > it seems that you simply don't right functionality for your problem. If > the product is essentially a kit (we call that Handelsstückliste in > Germany in most cases), than why you use a different product for > selling? I mean the customer doesn't necessarly need to know what the Because we manufacture new products instead of just selling the purchased one. > kit contains and how it is purchased but doubling the amount of product > data seems wired and wrong to me. Of course there are a few other down > stream issues to be handled when using Odoo E-Commerce as you do, but > generally i would still avoid (and see no reason) to build out a > replicating product structure (separated for sales and purchases). If > you really do the assembly yourself you may also want to use full > "manufacturing" instead (at least for the laptop type products). To use full manufacturing instead of a kit as part of the purchasing process would only complicate things. But instead we might register the purchased product in our stock (e.g. 1x laptop with its parts instead of 1x laptop barebone, 1x RAM, 1x SSD) and use this as a component when producing our final product. This might work if we find a solution to produce more than just one product. For example: The purchased laptop contains 250 GB SSD and the manufactured one contains a 500 GB SSD. So the 250 GB SSD will result in the stock as a by-product of the manufacturing (replaced by a 500 GB SSD). Is this possible somehow? Still I'm not convinced that this approach works for all our cases because we may end up with many BOMs, one for each purchased product variant. To stay with this example we purchase the laptop with different RAM and different SSD and each combination would require a different BOM. Bests Jan > Best Frederik > > Am 23.04.24 um 15:12 schrieb Jan Suhr | Nitrokey: >> Hi! >> We have several products which we purchase together. For example some >> laptops are purchased together with RAM and a SSD, but which are >> separate products for us in Odoo. I can't expect from our purchase >> department to remember all the components. To make purchasing error >> prone and easy, we configured a laptop *kit* which BOM contains a laptop >> *barebone*, RAM, SSD. So our purchase department can simply buy the >> laptop kit and don't need to remember which components are included in >> which product. >> >> In general this setup works but it has the following shortcomings: >> >> The reordering rules need to be configured for the barebone product. >> Once the minimum amount is reached a PO will be created automatically. >> The purchase department needs to remember to replace the barebone laptop >> with the barebone kit. Obviously deactivating "Can be Purchased" can't >> be applied here. We support this by stating "DON'T BUY" in the product >> barebone's name. >> >> Generally, the amount of products and BOMs is doubling, increasing the >> overall complexity. >> >> Do you have any better idea how to deal with such situation? >> >> Best regards, >> Jan >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 > 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 > 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com <mailto:frederik.kramer@initos.com> > Internet:www.initos.com <http://www.initos.com> > > Geschäftsführung: > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke > > Sitz der Gesellschaft: Buchholz i.d.N. > Amtsgericht Tostedt, HRB 205226 > USt-IdNr.: DE815580155 > Steuer-Nr: 15/200/53247 > > _______________________________________________ > 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> >
by Jan Suhr - 04:16 - 23 Apr 2024 -
Re: purchasing a set of products
Hi Jan,
it seems that you simply don't right functionality for your problem. If the product is essentially a kit (we call that Handelsstückliste in Germany in most cases), than why you use a different product for selling? I mean the customer doesn't necessarly need to know what the kit contains and how it is purchased but doubling the amount of product data seems wired and wrong to me. Of course there are a few other down stream issues to be handled when using Odoo E-Commerce as you do, but generally i would still avoid (and see no reason) to build out a replicating product structure (separated for sales and purchases). If you really do the assembly yourself you may also want to use full "manufacturing" instead (at least for the laptop type products).
Best Frederik
Am 23.04.24 um 15:12 schrieb Jan Suhr | Nitrokey:
Hi! We have several products which we purchase together. For example some laptops are purchased together with RAM and a SSD, but which are separate products for us in Odoo. I can't expect from our purchase department to remember all the components. To make purchasing error prone and easy, we configured a laptop *kit* which BOM contains a laptop *barebone*, RAM, SSD. So our purchase department can simply buy the laptop kit and don't need to remember which components are included in which product. In general this setup works but it has the following shortcomings: The reordering rules need to be configured for the barebone product. Once the minimum amount is reached a PO will be created automatically. The purchase department needs to remember to replace the barebone laptop with the barebone kit. Obviously deactivating "Can be Purchased" can't be applied here. We support this by stating "DON'T BUY" in the product barebone's name. Generally, the amount of products and BOMs is doubling, increasing the overall complexity. Do you have any better idea how to deal with such situation? Best regards, Jan
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer - 03:40 - 23 Apr 2024 -
purchasing a set of products
Hi! We have several products which we purchase together. For example some laptops are purchased together with RAM and a SSD, but which are separate products for us in Odoo. I can't expect from our purchase department to remember all the components. To make purchasing error prone and easy, we configured a laptop *kit* which BOM contains a laptop *barebone*, RAM, SSD. So our purchase department can simply buy the laptop kit and don't need to remember which components are included in which product. In general this setup works but it has the following shortcomings: The reordering rules need to be configured for the barebone product. Once the minimum amount is reached a PO will be created automatically. The purchase department needs to remember to replace the barebone laptop with the barebone kit. Obviously deactivating "Can be Purchased" can't be applied here. We support this by stating "DON'T BUY" in the product barebone's name. Generally, the amount of products and BOMs is doubling, increasing the overall complexity. Do you have any better idea how to deal with such situation? Best regards, Jan
by Jan Suhr - 03:11 - 23 Apr 2024 -
Re: Form field conditional formatting
> OK, I found it's working. But it's working a bit differently than what I'd > need. It colors the text in Char or Integer fields. It does nothing to > fields that are empty or to let's say Selection fields. I am looking for a > way to highlight some fields to draw attention to them even if they are > empty - so maybe setting the background on them. Or add some icon besides > them... Any ideas are welcome. don't forget plain css: div.o_form_editable div[name="yourfield"]:not(.o_readonly_modifier) input { background: red!important; } or combine this with the conditional bootstrap classes div[name="yourfield"].text-danger { background: red!important; } Up until v15 a form would have class o_form_model_name, which made it easy to make this model specific. For ancient Odoo for exactly this use case I made https://github.com/OCA/web/tree/6.1/web_widget_classes which you might want to resurrect and rename for this purpose. But if you go into the module writing business for this anyways, probably better patch https://github.com/OCA/OCB/blob/17.0/addons/web/static/src/views/fields/ field.js#L133 and allow something like <field name="yourfield" o-class-yourclass="expression" /> which would be much more versatile -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 05:16 - 22 Apr 2024 -
Re: Form field conditional formatting
OK, I found it's working. But it's working a bit differently than what I'd need. It colors the text in Char or Integer fields. It does nothing to fields that are empty or to let's say Selection fields. I am looking for a way to highlight some fields to draw attention to them even if they are empty - so maybe setting the background on them. Or add some icon besides them... Any ideas are welcome. Best regards On pondelok 22. apríla 2024 14:37:38 CEST Jose Vizcaya wrote: > As far as I know it does work in pretty much almost every view > type. Could you provide a piece of the XML where you are using it? > > > Best regards, > José Vizcaya. > > On 4/22/24 07:52, Radovan Skolnik > wrote: > > > Jose, > this would be the obvious thing I was missing. Only if I haven't tried it > already and now re-tried again. It's not working for me in 15.0 I don't know > why. All the decorations seem to be ignored :-( Should this be working in > form views as well? I know it's working in tree views and all such usage in > source I can find is limited to tree views. > Best regards > Radovan > > On pondelok 22. apríla 2024 13:22:04 CEST José Ángel Vizcaya wrote: > > Hello Radovan, > > If you want to highlight fields you can use the decoration-* inside the > > Field declaration in the XML file of the view. Here's how it works: > > https://www.odoo.com/documentation/17.0/developer/reference/frontend/javas > > c [1] ript_reference.html#decorations [1] I hope it helps. Best regards, > > José Vizcaya. > > On Mon, Apr 22, 2024, 03:22 Radovan Skolnik < > > notifications@odoo-community.org [2] [2] > wrote: Hello, > > I am looking for something to allow me to conditionally highlight (i.e. > > decoration would be sufficient - no need for custom CSS styles) form(!) > > fields. I have a feeling there is something or I am missing something very > > obvious but I am at lost here. Any suggestions? Thank you very much. Best > > regards > > Radovan Skolnik > > > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [3] [3] > > Post to: mailto: contributors@odoo-community.org [4] [4] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [5] [5] > > > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] [6] > > Post to: mailto:contributors@odoo-community.org [7] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [8] [7] > > > > > > > > [1] > > https://www.odoo.com/documentation/17.0/developer/reference/frontend/javas > > c [9] ript_reference.html#decorations [2] > > mailto:notifications@odoo-community.org [10] [3] > > https://odoo-community.org/groups/contributors-15 [11] > > [4] mailto:contributors@odoo-community.org [12] > > [5] https://odoo-community.org/groups?unsubscribe [13] > > [6] https://odoo-community.org/groups/contributors-15 [14] > > [7] https://odoo-community.org/groups?unsubscribe [15] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [16] > Post to: mailto:contributors@odoo-community.org [17] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [18] > > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [19] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [20] > > > > [1] > https://www.odoo.com/documentation/17.0/developer/reference/frontend/javasc > [2] mailto:notifications@odoo-community.org > [3] https://odoo-community.org/groups/contributors-15 > [4] mailto:contributors@odoo-community.org > [5] https://odoo-community.org/groups?unsubscribe > [6] https://odoo-community.org/groups/contributors-15 > [7] mailto:contributors@odoo-community.org > [8] https://odoo-community.org/groups?unsubscribe > [9] > https://www.odoo.com/documentation/17.0/developer/reference/frontend/javasc > [10] mailto:notifications@odoo-community.org > [11] https://odoo-community.org/groups/contributors-15 > [12] mailto:contributors@odoo-community.org > [13] https://odoo-community.org/groups?unsubscribe > [14] https://odoo-community.org/groups/contributors-15 > [15] https://odoo-community.org/groups?unsubscribe > [16] https://odoo-community.org/groups/contributors-15 > [17] mailto:contributors@odoo-community.org > [18] https://odoo-community.org/groups?unsubscribe > [19] https://odoo-community.org/groups/contributors-15 > [20] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 03:31 - 22 Apr 2024 -
Re: Form field conditional formatting
Adam, I am looking for formatting fileds in form(!) views, not tree views. Best regards, Radovan On pondelok 22. apríla 2024 13:43:15 CEST Adam Heinz wrote: > I use the OCA/web web_tree_dynamic_colored_field module in a couple reports > to highlight targets being missed or met. On Mon, Apr 22, 2024 at 3:22 AM > Radovan Skolnik < notifications@odoo-community.org [1] > wrote: Hello, > I am looking for something to allow me to conditionally highlight (i.e. > decoration would be sufficient - no need for custom CSS styles) form(!) > fields. I have a feeling there is something or I am missing something very > obvious but I am at lost here. Any suggestions? Thank you very much. Best > regards > Radovan Skolnik > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [2] > Post to: mailto: contributors@odoo-community.org [3] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [4] > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [5] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [6] > > > > [1] mailto:notifications@odoo-community.org > [2] https://odoo-community.org/groups/contributors-15 > [3] mailto:contributors@odoo-community.org > [4] https://odoo-community.org/groups?unsubscribe > [5] https://odoo-community.org/groups/contributors-15 > [6] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 01:51 - 22 Apr 2024
