Archives
Contributors
-
Sync odoo's calendar smartphones without Google nor Outlook
Dear allDoes anybody manage to sync odoo's calendar without Google/outlook ?Actually I tried Myodoo that has bugs and I'm going to try the old z-push odoo's backend https://github.com/funbaker/odoozpushThanks and have a great weekend--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.com
www.invitu.com
by Cyril VINH-TUNG - 08:06 - 14 Dec 2024 -
RE: Awnings dimensions app
Thanks David ! I’ll have a look.
With kind regards,
Van Hirtum Johan
Van: David Beal [mailto:notifications@odoo-community.org]
Verzonden: vrijdag 13 december 2024 14:02
Aan: Contributors
Onderwerp: Re: Awnings dimensions appLe ven. 13 déc. 2024 à 12:29, David Beal <david.beal@akretion.com> a écrit :
Hi Ahmed,
You might consider taking a look here
Let me know if you have any questions
Le ven. 13 déc. 2024 à 09:16, Johan Van Hirtum <notifications@odoo-community.org> a écrit :
Thanks a lot for your answers, Graeme -)
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: donderdag 12 december 2024 11:54
Aan: Contributors
Onderwerp: Re: Awnings dimensions appFor the awning issue in particular, we used to do something similar in another system. You just end up making arbitrary distinctions in your variants. e.g. 500-1000mm W add $10, 1000-1500m add $20 and same for depth. I did that for 20 years and still have 1 customer doing like that. In fact even for all the advancement with DSL's etc mentioned above, 90% of pricing still internally follows that pattern. The main reason being is that other peoples systems can't handle truly dynamic dimensions at the invoice level and needs the arbitrary partcodes and distinctions.
On Thu, Dec 12, 2024 at 11:36 PM Graeme Gellatly <graeme@moahub.nz> wrote:
Well primarily i work with dimensioned products. Timber is actually a bit more complex because it is bought in cubes but sold in usually sizes x length. I did that with variants and so.e customisation.
But for basic things, if you consider a sale of a widget is 1 unit, then a sale of a dimensioned producy is 1 x 1.8 of something it is just one extra field or of 3d then d x w x h = v. If you need to record a whole list of things then say 4@ 4.8 6@3.2 adds up to roughly 38lm of something and can be held in a o2m on order line. All you are really manipulating is order qty.
Le jeu. 12 déc. 2024, 21:57, Johan Van Hirtum <notifications@odoo-community.org> a écrit :
Hi Graeme,
Do you have or know about a module that let define dimensions on products and on variants ? Because most things with awnings can be done with variants ( fabric color, alu color, operation mode ) but there is no possibility to have an attribute that let you specify a dimension as an integer value. The same for products. In for example wood products, you sell pieces but the price is in meter and the length is a parameter you must provide. Sometimes you also have a product with fixed dimensions ( a profile or a plate ), price in m of m², where you can sell as a hole or cut to dimensions ( with sometimes an extra fee as % for cutting ). A solution for these situations would be all is needed I think for a lot of use cases.
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: woensdag 11 december 2024 20:58
Aan: Contributors
Onderwerp: Re: Awnings dimensions appHi,
It doesn't really explain very well your question.
Is it off plans, is it for pricing, is it for BoMs, for manufacturing machine integration e.g. CNC, is it the paper cutting problem, etc etc etc. I've done a lot of work in this space within custom MTO for manufacturing and pricing of construction materials. The 2 most difficult modules I used to maintain are mrp_dynamic_line (public, but always too risky/aggressive to be OCA) which calculates Production Orders dynamically from template attributes. The second is a DSL for managing the specification for a particular industry to do pricing, send to BoM (using dynamic_line and materials list from DSL, and does calculate all the dimensions) and api to manufacturing equipment on the SO Line which is private. The actual part of that module that handles the dimensions calculation is quite simple. It is just a one2many on sale order line with a few basic fields (and every similar model)
Those between them + Odoo + OCA cover maybe 30% of the problem space.
If it is custom MTO, then you also have a LOT of product code/cost/attribute/tracking/valuation considerations because every item at least in this case can have a different cost based on those DSL attributes with no real relation to any UoM concept. You need to avoid this if you can.
Modern QS stuff, uses google earth to approximate dimension in brownfields, can read pdf plans, has onsite site measure functionality, produces necessary legal docs, quotes, 3d models etc, calculates angles and rakes, material specific things like can waste be reused elsewhere, environmental specific things like wind loading and engineering and legal requirements for them. And it does it in a few minutes, just needing regularly updated component pricing via a csv or similar.
Then production planning software manages complex scheduling like the 2d and 3d cutting problems.
Then machine specific software handles the rest.
But for simple cases, in newer versions of Odoo, and possibly just enterprise, they allow a configuration spreadsheet at the sale to populate the sale. And they have a new Engineering to Order approach. I have two other smaller manufacturing for construction clients who had been using external tools wanting this investigated, but not started yet.
On Thu, Dec 12, 2024 at 1:52 AM Ahmed Trigui <notifications@odoo-community.org> wrote:
Hello community,
I'm looking for a module to calculate awnings dimensions.
Is there any app which covers this need please ?
Thank you!
--
Ahmed Trigui
Conseiller Analyste fonctionnel
+1 514-317-7944
Nouveau
Savez-vous tout sur l'open source ?_______________________________________________
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_______________________________________________
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 johan - 03:41 - 13 Dec 2024 -
Re: Awnings dimensions app
Le ven. 13 déc. 2024 à 12:29, David Beal <david.beal@akretion.com> a écrit :Hi Ahmed,You might consider taking a look hereLet me know if you have any questionsLe ven. 13 déc. 2024 à 09:16, Johan Van Hirtum <notifications@odoo-community.org> a écrit :Thanks a lot for your answers, Graeme -)
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: donderdag 12 december 2024 11:54
Aan: Contributors
Onderwerp: Re: Awnings dimensions appFor the awning issue in particular, we used to do something similar in another system. You just end up making arbitrary distinctions in your variants. e.g. 500-1000mm W add $10, 1000-1500m add $20 and same for depth. I did that for 20 years and still have 1 customer doing like that. In fact even for all the advancement with DSL's etc mentioned above, 90% of pricing still internally follows that pattern. The main reason being is that other peoples systems can't handle truly dynamic dimensions at the invoice level and needs the arbitrary partcodes and distinctions.
On Thu, Dec 12, 2024 at 11:36 PM Graeme Gellatly <graeme@moahub.nz> wrote:
Well primarily i work with dimensioned products. Timber is actually a bit more complex because it is bought in cubes but sold in usually sizes x length. I did that with variants and so.e customisation.
But for basic things, if you consider a sale of a widget is 1 unit, then a sale of a dimensioned producy is 1 x 1.8 of something it is just one extra field or of 3d then d x w x h = v. If you need to record a whole list of things then say 4@ 4.8 6@3.2 adds up to roughly 38lm of something and can be held in a o2m on order line. All you are really manipulating is order qty.
Le jeu. 12 déc. 2024, 21:57, Johan Van Hirtum <notifications@odoo-community.org> a écrit :
Hi Graeme,
Do you have or know about a module that let define dimensions on products and on variants ? Because most things with awnings can be done with variants ( fabric color, alu color, operation mode ) but there is no possibility to have an attribute that let you specify a dimension as an integer value. The same for products. In for example wood products, you sell pieces but the price is in meter and the length is a parameter you must provide. Sometimes you also have a product with fixed dimensions ( a profile or a plate ), price in m of m², where you can sell as a hole or cut to dimensions ( with sometimes an extra fee as % for cutting ). A solution for these situations would be all is needed I think for a lot of use cases.
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: woensdag 11 december 2024 20:58
Aan: Contributors
Onderwerp: Re: Awnings dimensions appHi,
It doesn't really explain very well your question.
Is it off plans, is it for pricing, is it for BoMs, for manufacturing machine integration e.g. CNC, is it the paper cutting problem, etc etc etc. I've done a lot of work in this space within custom MTO for manufacturing and pricing of construction materials. The 2 most difficult modules I used to maintain are mrp_dynamic_line (public, but always too risky/aggressive to be OCA) which calculates Production Orders dynamically from template attributes. The second is a DSL for managing the specification for a particular industry to do pricing, send to BoM (using dynamic_line and materials list from DSL, and does calculate all the dimensions) and api to manufacturing equipment on the SO Line which is private. The actual part of that module that handles the dimensions calculation is quite simple. It is just a one2many on sale order line with a few basic fields (and every similar model)
Those between them + Odoo + OCA cover maybe 30% of the problem space.
If it is custom MTO, then you also have a LOT of product code/cost/attribute/tracking/valuation considerations because every item at least in this case can have a different cost based on those DSL attributes with no real relation to any UoM concept. You need to avoid this if you can.
Modern QS stuff, uses google earth to approximate dimension in brownfields, can read pdf plans, has onsite site measure functionality, produces necessary legal docs, quotes, 3d models etc, calculates angles and rakes, material specific things like can waste be reused elsewhere, environmental specific things like wind loading and engineering and legal requirements for them. And it does it in a few minutes, just needing regularly updated component pricing via a csv or similar.
Then production planning software manages complex scheduling like the 2d and 3d cutting problems.
Then machine specific software handles the rest.
But for simple cases, in newer versions of Odoo, and possibly just enterprise, they allow a configuration spreadsheet at the sale to populate the sale. And they have a new Engineering to Order approach. I have two other smaller manufacturing for construction clients who had been using external tools wanting this investigated, but not started yet.
On Thu, Dec 12, 2024 at 1:52 AM Ahmed Trigui <notifications@odoo-community.org> wrote:
Hello community,
I'm looking for a module to calculate awnings dimensions.
Is there any app which covers this need please ?
Thank you!
--
Ahmed Trigui
Conseiller Analyste fonctionnel
+1 514-317-7944
Nouveau
Savez-vous tout sur l'open source ?_______________________________________________
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_______________________________________________
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 - 02:01 - 13 Dec 2024 -
Re: Awnings dimensions app
Hi Ahmed,You might consider taking a look hereLet me know if you have any questionsLe ven. 13 déc. 2024 à 09:16, Johan Van Hirtum <notifications@odoo-community.org> a écrit :
Thanks a lot for your answers, Graeme -)
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: donderdag 12 december 2024 11:54
Aan: Contributors
Onderwerp: Re: Awnings dimensions appFor the awning issue in particular, we used to do something similar in another system. You just end up making arbitrary distinctions in your variants. e.g. 500-1000mm W add $10, 1000-1500m add $20 and same for depth. I did that for 20 years and still have 1 customer doing like that. In fact even for all the advancement with DSL's etc mentioned above, 90% of pricing still internally follows that pattern. The main reason being is that other peoples systems can't handle truly dynamic dimensions at the invoice level and needs the arbitrary partcodes and distinctions.
On Thu, Dec 12, 2024 at 11:36 PM Graeme Gellatly <graeme@moahub.nz> wrote:
Well primarily i work with dimensioned products. Timber is actually a bit more complex because it is bought in cubes but sold in usually sizes x length. I did that with variants and so.e customisation.
But for basic things, if you consider a sale of a widget is 1 unit, then a sale of a dimensioned producy is 1 x 1.8 of something it is just one extra field or of 3d then d x w x h = v. If you need to record a whole list of things then say 4@ 4.8 6@3.2 adds up to roughly 38lm of something and can be held in a o2m on order line. All you are really manipulating is order qty.
Le jeu. 12 déc. 2024, 21:57, Johan Van Hirtum <notifications@odoo-community.org> a écrit :
Hi Graeme,
Do you have or know about a module that let define dimensions on products and on variants ? Because most things with awnings can be done with variants ( fabric color, alu color, operation mode ) but there is no possibility to have an attribute that let you specify a dimension as an integer value. The same for products. In for example wood products, you sell pieces but the price is in meter and the length is a parameter you must provide. Sometimes you also have a product with fixed dimensions ( a profile or a plate ), price in m of m², where you can sell as a hole or cut to dimensions ( with sometimes an extra fee as % for cutting ). A solution for these situations would be all is needed I think for a lot of use cases.
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: woensdag 11 december 2024 20:58
Aan: Contributors
Onderwerp: Re: Awnings dimensions appHi,
It doesn't really explain very well your question.
Is it off plans, is it for pricing, is it for BoMs, for manufacturing machine integration e.g. CNC, is it the paper cutting problem, etc etc etc. I've done a lot of work in this space within custom MTO for manufacturing and pricing of construction materials. The 2 most difficult modules I used to maintain are mrp_dynamic_line (public, but always too risky/aggressive to be OCA) which calculates Production Orders dynamically from template attributes. The second is a DSL for managing the specification for a particular industry to do pricing, send to BoM (using dynamic_line and materials list from DSL, and does calculate all the dimensions) and api to manufacturing equipment on the SO Line which is private. The actual part of that module that handles the dimensions calculation is quite simple. It is just a one2many on sale order line with a few basic fields (and every similar model)
Those between them + Odoo + OCA cover maybe 30% of the problem space.
If it is custom MTO, then you also have a LOT of product code/cost/attribute/tracking/valuation considerations because every item at least in this case can have a different cost based on those DSL attributes with no real relation to any UoM concept. You need to avoid this if you can.
Modern QS stuff, uses google earth to approximate dimension in brownfields, can read pdf plans, has onsite site measure functionality, produces necessary legal docs, quotes, 3d models etc, calculates angles and rakes, material specific things like can waste be reused elsewhere, environmental specific things like wind loading and engineering and legal requirements for them. And it does it in a few minutes, just needing regularly updated component pricing via a csv or similar.
Then production planning software manages complex scheduling like the 2d and 3d cutting problems.
Then machine specific software handles the rest.
But for simple cases, in newer versions of Odoo, and possibly just enterprise, they allow a configuration spreadsheet at the sale to populate the sale. And they have a new Engineering to Order approach. I have two other smaller manufacturing for construction clients who had been using external tools wanting this investigated, but not started yet.
On Thu, Dec 12, 2024 at 1:52 AM Ahmed Trigui <notifications@odoo-community.org> wrote:
Hello community,
I'm looking for a module to calculate awnings dimensions.
Is there any app which covers this need please ?
Thank you!
--
Ahmed Trigui
Conseiller Analyste fonctionnel
+1 514-317-7944
Nouveau
Savez-vous tout sur l'open source ?_______________________________________________
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_______________________________________________
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:30 - 13 Dec 2024 -
RE: Awnings dimensions app
Thanks a lot for your answers, Graeme -)
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: donderdag 12 december 2024 11:54
Aan: Contributors
Onderwerp: Re: Awnings dimensions appFor the awning issue in particular, we used to do something similar in another system. You just end up making arbitrary distinctions in your variants. e.g. 500-1000mm W add $10, 1000-1500m add $20 and same for depth. I did that for 20 years and still have 1 customer doing like that. In fact even for all the advancement with DSL's etc mentioned above, 90% of pricing still internally follows that pattern. The main reason being is that other peoples systems can't handle truly dynamic dimensions at the invoice level and needs the arbitrary partcodes and distinctions.
On Thu, Dec 12, 2024 at 11:36 PM Graeme Gellatly <graeme@moahub.nz> wrote:
Well primarily i work with dimensioned products. Timber is actually a bit more complex because it is bought in cubes but sold in usually sizes x length. I did that with variants and so.e customisation.
But for basic things, if you consider a sale of a widget is 1 unit, then a sale of a dimensioned producy is 1 x 1.8 of something it is just one extra field or of 3d then d x w x h = v. If you need to record a whole list of things then say 4@ 4.8 6@3.2 adds up to roughly 38lm of something and can be held in a o2m on order line. All you are really manipulating is order qty.
Le jeu. 12 déc. 2024, 21:57, Johan Van Hirtum <notifications@odoo-community.org> a écrit :
Hi Graeme,
Do you have or know about a module that let define dimensions on products and on variants ? Because most things with awnings can be done with variants ( fabric color, alu color, operation mode ) but there is no possibility to have an attribute that let you specify a dimension as an integer value. The same for products. In for example wood products, you sell pieces but the price is in meter and the length is a parameter you must provide. Sometimes you also have a product with fixed dimensions ( a profile or a plate ), price in m of m², where you can sell as a hole or cut to dimensions ( with sometimes an extra fee as % for cutting ). A solution for these situations would be all is needed I think for a lot of use cases.
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: woensdag 11 december 2024 20:58
Aan: Contributors
Onderwerp: Re: Awnings dimensions appHi,
It doesn't really explain very well your question.
Is it off plans, is it for pricing, is it for BoMs, for manufacturing machine integration e.g. CNC, is it the paper cutting problem, etc etc etc. I've done a lot of work in this space within custom MTO for manufacturing and pricing of construction materials. The 2 most difficult modules I used to maintain are mrp_dynamic_line (public, but always too risky/aggressive to be OCA) which calculates Production Orders dynamically from template attributes. The second is a DSL for managing the specification for a particular industry to do pricing, send to BoM (using dynamic_line and materials list from DSL, and does calculate all the dimensions) and api to manufacturing equipment on the SO Line which is private. The actual part of that module that handles the dimensions calculation is quite simple. It is just a one2many on sale order line with a few basic fields (and every similar model)
Those between them + Odoo + OCA cover maybe 30% of the problem space.
If it is custom MTO, then you also have a LOT of product code/cost/attribute/tracking/valuation considerations because every item at least in this case can have a different cost based on those DSL attributes with no real relation to any UoM concept. You need to avoid this if you can.
Modern QS stuff, uses google earth to approximate dimension in brownfields, can read pdf plans, has onsite site measure functionality, produces necessary legal docs, quotes, 3d models etc, calculates angles and rakes, material specific things like can waste be reused elsewhere, environmental specific things like wind loading and engineering and legal requirements for them. And it does it in a few minutes, just needing regularly updated component pricing via a csv or similar.
Then production planning software manages complex scheduling like the 2d and 3d cutting problems.
Then machine specific software handles the rest.
But for simple cases, in newer versions of Odoo, and possibly just enterprise, they allow a configuration spreadsheet at the sale to populate the sale. And they have a new Engineering to Order approach. I have two other smaller manufacturing for construction clients who had been using external tools wanting this investigated, but not started yet.
On Thu, Dec 12, 2024 at 1:52 AM Ahmed Trigui <notifications@odoo-community.org> wrote:
Hello community,
I'm looking for a module to calculate awnings dimensions.
Is there any app which covers this need please ?
Thank you!
--
Ahmed Trigui
Conseiller Analyste fonctionnel
+1 514-317-7944
Nouveau
Savez-vous tout sur l'open source ?_______________________________________________
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 johan - 09:15 - 13 Dec 2024 -
Re: [Odoo CE 17.0] Fields related to custom fields don't save any values
Hello Houssine,Of course, I'm sending you the link to the custom code in GitHub:The custom code is inside the "models" folder.Best regards.El 12/12/2024 15:17 CET Houssine BAKKALI <notifications@odoo-community.org> escribió:Hi,Could you show the custom code to allow us to have a better view of what you did ?Don't hesitate to put your question on the odoo forum and share the link with us.Regards,Houssine
Le mar. 10 déc. 2024, 10:58, Redes Sociales JLBBERP <notifications@odoo-community.org> a écrit :Hello Jesus,I don't fully understand what you mean by "add the name field in the module". Do you mean giving the module a name field like "_name="product.example""?El 10/12/2024 10:32 CET Jesus Sokamby <notifications@odoo-community.org> escribió:Hi, there,
I suggest you add the name field in the model and also the security/ir.model.access.csv file in the module.
Le mar. 10 déc. 2024 à 10:08, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hello, add parameter `store=True` on those related fields. Update module after it.Regards--Francesco Ballerini
Il giorno mar 10 dic 2024 alle ore 09:38 Redes Sociales JLBBERP <notifications@odoo-community.org> ha scritto:Hello everyone,I am writing this message because I need help with making fields related to custom fields store values into the database.Some days ago, I made a custom model through Python called "product_measures", which is inside a model called "product_dimension". Said model not only has three Many2one fields, each one for the product's measures, but is also inside another model of "product_dimension" called "product_template", which has the same fields but with the related field section and different names. The problem is that whenever I write anything on the fields, it doesn't save anything. Also, I'm trying to make it so every value that is created and is a number is converted into a Float.I'm sending the module in a zip file because I have been stuck with this problem for quite some time, and I would like to solve this problem as soon as possible.Thanks in advance for anyone who answers.Best regards._______________________________________________
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_______________________________________________
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:06 - 13 Dec 2024 -
Re: demo data and tests
HiOn my projects tests are run at 2 levels:- At development level: The developer tests the code he has written to ensure that it works as expected. For this, the developper writes unit tests that are run on an empty database with only this addon installed. This ensures that the code is correct and works properly in the context defined by the dependencies of the addon.
- At integration level: The CI runs all the tests on a database with all the addons installed. This ensures that the code is correct and works properly in the context of the whole system.
To achieve this, we apply the following guidelines:- Tests don't rely on demo data; This eases the maintenance of the tests and ensures that the tests are not impacted by changes in the demo data. Moreover, it helps the developer to understand the context in which the tests are run.
- Code that modifies / constrains an existing behavior must be disabled by default and must be enabled by a configuration parameter. This ensures that if you run the tests from other addons on a database where this addon is installed, the tests will not be impacted by this addon. It also ensures that if the tests are run at insall and another addon modifies the same behavior, the tests will not be impacted by this addon if it has been installed previously in the installation process. (The disabled behaviour is activated at test setup). All the disabled features are enabled in a top level addon which is excluded from the installation by the CI and installed only into the client database.
- Some specific test addons are developed for specific integration tests. These addons are useful to ensure that addons installed side by side are compatible even if they don't depend on each other. At test setup, we first activate the features of the addons that are activable by configuration parameter.
- To avoid the need to use the "post_install' annotation, the CI runs the tests with pytest-odoo. The main difference compared to the way odoo runs the tests is that the registry is populated with all the addons installed into the database. pytest-odoo is a test runner only while when you run the tests with odoo, the tests are run along the installation/upgrade of the addons at the same time the registry is populated. To run tests with pytest-odoo, the first requirement is to have the addons to test installed in the database. One advantage of this approach is that even if your addon creates a new record for which another addon has created a new required field with a default value the tests will run correctly even if you don't depend on this addon.
- ...
We are still not perfect and since all the code modifying an existing behaviour is activated in production, some tests will fail if they are run on the production database since they are not designed to run with the modified behaviour.. But we solved a lot of issues we encountered in the past when tests were run by odoo at install/upgrade time.Regards,lmi
Use post install test tags and remove at install. And refuse PRs with required fields that don't set defaults. This is the normal practice anyway as you would get errors with or without using demo data.Also, one other benefit, particularly in number based tests is we use a library called hypothesis to determine values and try to find failing combos.Le ven. 13 déc. 2024, 04:52, Raphaël Valyi <notifications@odoo-community.org> a écrit :Hello Odoo community,More and more the OCA contributors avoid writing tests which depend on demo data and so does Odoo SA. This makes it easier to ensure tests are simple and will run no matter how demo data might be touched by other modules.But eventually this could bring other benefits such as the ability to run these standard tests in the CI with production database dumps (that is where the demo data cannot be loaded in general).In this case, I have a first question: probably some customization's might add required fields. What would be the best practice to be able to run these "native" or OCA tests that might fail to create records with such new constraints? We could imagine some monkey patches and standard hooks to help... We kind of face this already today by running tests with all repo modules installed, but with production dumps, much more modules would be installed together along with some non OCA customization which also need to be developed more cheaply...But more important is my second question: if we set it as a good practice that OCA tests shouldn't depend on demo data, why are we still running the OCA CI with demo data enabled (still the case with Odoo 18 CI) ? Or is it planned we stop doing this in Odoo 19? I mean we could also save a good deal of server resources/time by not loading the gazillions of catchy Odoo CE demo data in each test run...Thank you very much for your answers.
--Raphaël ValyiFounder and consultant_______________________________________________
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
--Laurent MignonTechnical lead / Management TeamT: +32 2 8883148Atrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumVal Benoit, Quai Banning 6 | B-4000 Liège | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg
by Laurent Mignon - 09:06 - 13 Dec 2024 -
Re: demo data and tests
Irt to loading demo data, afaik, post test it is a demo instance as well for manual testingLe ven. 13 déc. 2024, 06:28, Graeme Gellatly <graeme@moahub.nz> a écrit :HiUse post install test tags and remove at install. And refuse PRs with required fields that don't set defaults. This is the normal practice anyway as you would get errors with or without using demo data.Also, one other benefit, particularly in number based tests is we use a library called hypothesis to determine values and try to find failing combos.Le ven. 13 déc. 2024, 04:52, Raphaël Valyi <notifications@odoo-community.org> a écrit :Hello Odoo community,More and more the OCA contributors avoid writing tests which depend on demo data and so does Odoo SA. This makes it easier to ensure tests are simple and will run no matter how demo data might be touched by other modules.But eventually this could bring other benefits such as the ability to run these standard tests in the CI with production database dumps (that is where the demo data cannot be loaded in general).In this case, I have a first question: probably some customization's might add required fields. What would be the best practice to be able to run these "native" or OCA tests that might fail to create records with such new constraints? We could imagine some monkey patches and standard hooks to help... We kind of face this already today by running tests with all repo modules installed, but with production dumps, much more modules would be installed together along with some non OCA customization which also need to be developed more cheaply...But more important is my second question: if we set it as a good practice that OCA tests shouldn't depend on demo data, why are we still running the OCA CI with demo data enabled (still the case with Odoo 18 CI) ? Or is it planned we stop doing this in Odoo 19? I mean we could also save a good deal of server resources/time by not loading the gazillions of catchy Odoo CE demo data in each test run...Thank you very much for your answers.
--Raphaël ValyiFounder and consultant_______________________________________________
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 - 06:31 - 12 Dec 2024 -
Re: demo data and tests
HiUse post install test tags and remove at install. And refuse PRs with required fields that don't set defaults. This is the normal practice anyway as you would get errors with or without using demo data.Also, one other benefit, particularly in number based tests is we use a library called hypothesis to determine values and try to find failing combos.Le ven. 13 déc. 2024, 04:52, Raphaël Valyi <notifications@odoo-community.org> a écrit :Hello Odoo community,More and more the OCA contributors avoid writing tests which depend on demo data and so does Odoo SA. This makes it easier to ensure tests are simple and will run no matter how demo data might be touched by other modules.But eventually this could bring other benefits such as the ability to run these standard tests in the CI with production database dumps (that is where the demo data cannot be loaded in general).In this case, I have a first question: probably some customization's might add required fields. What would be the best practice to be able to run these "native" or OCA tests that might fail to create records with such new constraints? We could imagine some monkey patches and standard hooks to help... We kind of face this already today by running tests with all repo modules installed, but with production dumps, much more modules would be installed together along with some non OCA customization which also need to be developed more cheaply...But more important is my second question: if we set it as a good practice that OCA tests shouldn't depend on demo data, why are we still running the OCA CI with demo data enabled (still the case with Odoo 18 CI) ? Or is it planned we stop doing this in Odoo 19? I mean we could also save a good deal of server resources/time by not loading the gazillions of catchy Odoo CE demo data in each test run...Thank you very much for your answers.
--Raphaël ValyiFounder and consultant_______________________________________________
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 - 06:31 - 12 Dec 2024 -
demo data and tests
Hello Odoo community,More and more the OCA contributors avoid writing tests which depend on demo data and so does Odoo SA. This makes it easier to ensure tests are simple and will run no matter how demo data might be touched by other modules.But eventually this could bring other benefits such as the ability to run these standard tests in the CI with production database dumps (that is where the demo data cannot be loaded in general).In this case, I have a first question: probably some customization's might add required fields. What would be the best practice to be able to run these "native" or OCA tests that might fail to create records with such new constraints? We could imagine some monkey patches and standard hooks to help... We kind of face this already today by running tests with all repo modules installed, but with production dumps, much more modules would be installed together along with some non OCA customization which also need to be developed more cheaply...But more important is my second question: if we set it as a good practice that OCA tests shouldn't depend on demo data, why are we still running the OCA CI with demo data enabled (still the case with Odoo 18 CI) ? Or is it planned we stop doing this in Odoo 19? I mean we could also save a good deal of server resources/time by not loading the gazillions of catchy Odoo CE demo data in each test run...Thank you very much for your answers.
--Raphaël ValyiFounder and consultant
by "Raphaël Valyi" <rvalyi@akretion.com> - 04:51 - 12 Dec 2024 -
Re: [Odoo CE 17.0] Fields related to custom fields don't save any values
Hi,Could you show the custom code to allow us to have a better view of what you did ?Don't hesitate to put your question on the odoo forum and share the link with us.Regards,HoussineLe mar. 10 déc. 2024, 10:58, Redes Sociales JLBBERP <notifications@odoo-community.org> a écrit :Hello Jesus,I don't fully understand what you mean by "add the name field in the module". Do you mean giving the module a name field like "_name="product.example""?El 10/12/2024 10:32 CET Jesus Sokamby <notifications@odoo-community.org> escribió:Hi, there,
I suggest you add the name field in the model and also the security/ir.model.access.csv file in the module.
Le mar. 10 déc. 2024 à 10:08, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hello, add parameter `store=True` on those related fields. Update module after it.Regards--Francesco Ballerini
Il giorno mar 10 dic 2024 alle ore 09:38 Redes Sociales JLBBERP <notifications@odoo-community.org> ha scritto:Hello everyone,I am writing this message because I need help with making fields related to custom fields store values into the database.Some days ago, I made a custom model through Python called "product_measures", which is inside a model called "product_dimension". Said model not only has three Many2one fields, each one for the product's measures, but is also inside another model of "product_dimension" called "product_template", which has the same fields but with the related field section and different names. The problem is that whenever I write anything on the fields, it doesn't save anything. Also, I'm trying to make it so every value that is created and is a number is converted into a Float.I'm sending the module in a zip file because I have been stuck with this problem for quite some time, and I would like to solve this problem as soon as possible.Thanks in advance for anyone who answers.Best regards._______________________________________________
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 Houssine BAKKALI - 03:16 - 12 Dec 2024 -
Re: Awnings dimensions app
On Thu, Dec 12, 2024 at 5:53 AM Graeme Gellatly <notifications@odoo-community.org> wrote:For the awning issue in particular, we used to do something similar in another system. You just end up making arbitrary distinctions in your variants. e.g. 500-1000mm W add $10, 1000-1500m add $20 and same for depth. I did that for 20 years and still have 1 customer doing like that. In fact even for all the advancement with DSL's etc mentioned above, 90% of pricing still internally follows that pattern. The main reason being is that other peoples systems can't handle truly dynamic dimensions at the invoice level and needs the arbitrary partcodes and distinctions.Our manufacturers price their products in size buckets as you describe above, but we order bespoke products with precise measurements.Le jeu. 12 déc. 2024, 21:57, Johan Van Hirtum <notifications@odoo-community.org> a écrit :
Do you have or know about a module that let define dimensions on products and on variants ? Because most things with awnings can be done with variants ( fabric color, alu color, operation mode ) but there is no possibility to have an attribute that let you specify a dimension as an integer value. The same for products. In for example wood products, you sell pieces but the price is in meter and the length is a parameter you must provide. Sometimes you also have a product with fixed dimensions ( a profile or a plate ), price in m of m², where you can sell as a hole or cut to dimensions ( with sometimes an extra fee as % for cutting ). A solution for these situations would be all is needed I think for a lot of use cases.
Have you experimented with the sale_product_configurator module and the product.attribute.custom.value model?
by Adam Heinz - 02:41 - 12 Dec 2024 -
Re: Awnings dimensions app
For the awning issue in particular, we used to do something similar in another system. You just end up making arbitrary distinctions in your variants. e.g. 500-1000mm W add $10, 1000-1500m add $20 and same for depth. I did that for 20 years and still have 1 customer doing like that. In fact even for all the advancement with DSL's etc mentioned above, 90% of pricing still internally follows that pattern. The main reason being is that other peoples systems can't handle truly dynamic dimensions at the invoice level and needs the arbitrary partcodes and distinctions.On Thu, Dec 12, 2024 at 11:36 PM Graeme Gellatly <graeme@moahub.nz> wrote:Well primarily i work with dimensioned products. Timber is actually a bit more complex because it is bought in cubes but sold in usually sizes x length. I did that with variants and so.e customisation.But for basic things, if you consider a sale of a widget is 1 unit, then a sale of a dimensioned producy is 1 x 1.8 of something it is just one extra field or of 3d then d x w x h = v. If you need to record a whole list of things then say 4@ 4.8 6@3.2 adds up to roughly 38lm of something and can be held in a o2m on order line. All you are really manipulating is order qty.Le jeu. 12 déc. 2024, 21:57, Johan Van Hirtum <notifications@odoo-community.org> a écrit :
Hi Graeme,
Do you have or know about a module that let define dimensions on products and on variants ? Because most things with awnings can be done with variants ( fabric color, alu color, operation mode ) but there is no possibility to have an attribute that let you specify a dimension as an integer value. The same for products. In for example wood products, you sell pieces but the price is in meter and the length is a parameter you must provide. Sometimes you also have a product with fixed dimensions ( a profile or a plate ), price in m of m², where you can sell as a hole or cut to dimensions ( with sometimes an extra fee as % for cutting ). A solution for these situations would be all is needed I think for a lot of use cases.
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: woensdag 11 december 2024 20:58
Aan: Contributors
Onderwerp: Re: Awnings dimensions appHi,
It doesn't really explain very well your question.
Is it off plans, is it for pricing, is it for BoMs, for manufacturing machine integration e.g. CNC, is it the paper cutting problem, etc etc etc. I've done a lot of work in this space within custom MTO for manufacturing and pricing of construction materials. The 2 most difficult modules I used to maintain are mrp_dynamic_line (public, but always too risky/aggressive to be OCA) which calculates Production Orders dynamically from template attributes. The second is a DSL for managing the specification for a particular industry to do pricing, send to BoM (using dynamic_line and materials list from DSL, and does calculate all the dimensions) and api to manufacturing equipment on the SO Line which is private. The actual part of that module that handles the dimensions calculation is quite simple. It is just a one2many on sale order line with a few basic fields (and every similar model)
Those between them + Odoo + OCA cover maybe 30% of the problem space.
If it is custom MTO, then you also have a LOT of product code/cost/attribute/tracking/valuation considerations because every item at least in this case can have a different cost based on those DSL attributes with no real relation to any UoM concept. You need to avoid this if you can.
Modern QS stuff, uses google earth to approximate dimension in brownfields, can read pdf plans, has onsite site measure functionality, produces necessary legal docs, quotes, 3d models etc, calculates angles and rakes, material specific things like can waste be reused elsewhere, environmental specific things like wind loading and engineering and legal requirements for them. And it does it in a few minutes, just needing regularly updated component pricing via a csv or similar.
Then production planning software manages complex scheduling like the 2d and 3d cutting problems.
Then machine specific software handles the rest.
But for simple cases, in newer versions of Odoo, and possibly just enterprise, they allow a configuration spreadsheet at the sale to populate the sale. And they have a new Engineering to Order approach. I have two other smaller manufacturing for construction clients who had been using external tools wanting this investigated, but not started yet.
On Thu, Dec 12, 2024 at 1:52 AM Ahmed Trigui <notifications@odoo-community.org> wrote:
Hello community,
I'm looking for a module to calculate awnings dimensions.
Is there any app which covers this need please ?
Thank you!
--
Ahmed Trigui
Conseiller Analyste fonctionnel
+1 514-317-7944
Nouveau
Savez-vous tout sur l'open source ?_______________________________________________
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 - 11:51 - 12 Dec 2024 -
Re: Awnings dimensions app
Well primarily i work with dimensioned products. Timber is actually a bit more complex because it is bought in cubes but sold in usually sizes x length. I did that with variants and so.e customisation.But for basic things, if you consider a sale of a widget is 1 unit, then a sale of a dimensioned producy is 1 x 1.8 of something it is just one extra field or of 3d then d x w x h = v. If you need to record a whole list of things then say 4@ 4.8 6@3.2 adds up to roughly 38lm of something and can be held in a o2m on order line. All you are really manipulating is order qty.Le jeu. 12 déc. 2024, 21:57, Johan Van Hirtum <notifications@odoo-community.org> a écrit :
Hi Graeme,
Do you have or know about a module that let define dimensions on products and on variants ? Because most things with awnings can be done with variants ( fabric color, alu color, operation mode ) but there is no possibility to have an attribute that let you specify a dimension as an integer value. The same for products. In for example wood products, you sell pieces but the price is in meter and the length is a parameter you must provide. Sometimes you also have a product with fixed dimensions ( a profile or a plate ), price in m of m², where you can sell as a hole or cut to dimensions ( with sometimes an extra fee as % for cutting ). A solution for these situations would be all is needed I think for a lot of use cases.
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: woensdag 11 december 2024 20:58
Aan: Contributors
Onderwerp: Re: Awnings dimensions appHi,
It doesn't really explain very well your question.
Is it off plans, is it for pricing, is it for BoMs, for manufacturing machine integration e.g. CNC, is it the paper cutting problem, etc etc etc. I've done a lot of work in this space within custom MTO for manufacturing and pricing of construction materials. The 2 most difficult modules I used to maintain are mrp_dynamic_line (public, but always too risky/aggressive to be OCA) which calculates Production Orders dynamically from template attributes. The second is a DSL for managing the specification for a particular industry to do pricing, send to BoM (using dynamic_line and materials list from DSL, and does calculate all the dimensions) and api to manufacturing equipment on the SO Line which is private. The actual part of that module that handles the dimensions calculation is quite simple. It is just a one2many on sale order line with a few basic fields (and every similar model)
Those between them + Odoo + OCA cover maybe 30% of the problem space.
If it is custom MTO, then you also have a LOT of product code/cost/attribute/tracking/valuation considerations because every item at least in this case can have a different cost based on those DSL attributes with no real relation to any UoM concept. You need to avoid this if you can.
Modern QS stuff, uses google earth to approximate dimension in brownfields, can read pdf plans, has onsite site measure functionality, produces necessary legal docs, quotes, 3d models etc, calculates angles and rakes, material specific things like can waste be reused elsewhere, environmental specific things like wind loading and engineering and legal requirements for them. And it does it in a few minutes, just needing regularly updated component pricing via a csv or similar.
Then production planning software manages complex scheduling like the 2d and 3d cutting problems.
Then machine specific software handles the rest.
But for simple cases, in newer versions of Odoo, and possibly just enterprise, they allow a configuration spreadsheet at the sale to populate the sale. And they have a new Engineering to Order approach. I have two other smaller manufacturing for construction clients who had been using external tools wanting this investigated, but not started yet.
On Thu, Dec 12, 2024 at 1:52 AM Ahmed Trigui <notifications@odoo-community.org> wrote:
Hello community,
I'm looking for a module to calculate awnings dimensions.
Is there any app which covers this need please ?
Thank you!
--
Ahmed Trigui
Conseiller Analyste fonctionnel
+1 514-317-7944
Nouveau
Savez-vous tout sur l'open source ?_______________________________________________
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 - 11:40 - 12 Dec 2024 -
Re: [18.0] Project Task Git integration
Hi Francesco, I have developed a module to manage git repositories: https://github.com/Mint-System/Odoo-Apps-Connector/tree/16.0/git_base And here are the docs: https://www.odoo-wiki.org/git-base.html I will eventually develop a "project_git" module that connects projects with git repos and supports creating feature branches from tasks. All Mint System modules live up to the OCA standards. Cheers, Janik On 12/6/24 6:48 PM, Francesco Ballerini wrote: > Hi, > > we're looking for an Odoo 18 project task git integration. > > Specifically we need the feature that allows linking PR and commits to > the task by branch name/commit name containing the name of the task, > basically like Atlassian/Jira git integration. > > If you have any open source resource to provide as example we we might > try to migrate it to version 18.0. > > Thanks > > --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 > -- 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 - 10:16 - 12 Dec 2024 -
RE: Awnings dimensions app
Hi Graeme,
Do you have or know about a module that let define dimensions on products and on variants ? Because most things with awnings can be done with variants ( fabric color, alu color, operation mode ) but there is no possibility to have an attribute that let you specify a dimension as an integer value. The same for products. In for example wood products, you sell pieces but the price is in meter and the length is a parameter you must provide. Sometimes you also have a product with fixed dimensions ( a profile or a plate ), price in m of m², where you can sell as a hole or cut to dimensions ( with sometimes an extra fee as % for cutting ). A solution for these situations would be all is needed I think for a lot of use cases.
With kind regards,
Van Hirtum Johan
Van: Graeme Gellatly [mailto:notifications@odoo-community.org]
Verzonden: woensdag 11 december 2024 20:58
Aan: Contributors
Onderwerp: Re: Awnings dimensions appHi,
It doesn't really explain very well your question.
Is it off plans, is it for pricing, is it for BoMs, for manufacturing machine integration e.g. CNC, is it the paper cutting problem, etc etc etc. I've done a lot of work in this space within custom MTO for manufacturing and pricing of construction materials. The 2 most difficult modules I used to maintain are mrp_dynamic_line (public, but always too risky/aggressive to be OCA) which calculates Production Orders dynamically from template attributes. The second is a DSL for managing the specification for a particular industry to do pricing, send to BoM (using dynamic_line and materials list from DSL, and does calculate all the dimensions) and api to manufacturing equipment on the SO Line which is private. The actual part of that module that handles the dimensions calculation is quite simple. It is just a one2many on sale order line with a few basic fields (and every similar model)
Those between them + Odoo + OCA cover maybe 30% of the problem space.
If it is custom MTO, then you also have a LOT of product code/cost/attribute/tracking/valuation considerations because every item at least in this case can have a different cost based on those DSL attributes with no real relation to any UoM concept. You need to avoid this if you can.
Modern QS stuff, uses google earth to approximate dimension in brownfields, can read pdf plans, has onsite site measure functionality, produces necessary legal docs, quotes, 3d models etc, calculates angles and rakes, material specific things like can waste be reused elsewhere, environmental specific things like wind loading and engineering and legal requirements for them. And it does it in a few minutes, just needing regularly updated component pricing via a csv or similar.
Then production planning software manages complex scheduling like the 2d and 3d cutting problems.
Then machine specific software handles the rest.
But for simple cases, in newer versions of Odoo, and possibly just enterprise, they allow a configuration spreadsheet at the sale to populate the sale. And they have a new Engineering to Order approach. I have two other smaller manufacturing for construction clients who had been using external tools wanting this investigated, but not started yet.
On Thu, Dec 12, 2024 at 1:52 AM Ahmed Trigui <notifications@odoo-community.org> wrote:
Hello community,
I'm looking for a module to calculate awnings dimensions.
Is there any app which covers this need please ?
Thank you!
--
Ahmed Trigui
Conseiller Analyste fonctionnel
+1 514-317-7944
Nouveau
Savez-vous tout sur l'open source ?_______________________________________________
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 johan - 09:56 - 12 Dec 2024 -
Re: Awnings dimensions app
OK, well that is a common basic use case. Using Excel as a configurator into an ERP system for essentially pricing purposes. I know lots of people who do that in many different ERP systems. It reaches its limits when it comes to production and stock, you end up with manually creating production orders as well, but still has a use case.So if it is really simple, then you can just use a form view for sale order lines add a few fields and run the calculations there. If it isn't, say they need to choose the arm strength, or I don't know something else about awnings, then watch the Odoo videos of using odoo spreadsheet configurator linked to sale. I think it was partly covered in keynote. I am not sure if community or enterprise, but even if only enterprise, the actual concept is not hard to bring to community.On Thu, Dec 12, 2024 at 9:02 PM Ahmed Trigui <notifications@odoo-community.org> wrote:Hello Graeme,Thank you for your answer.This is a company that manufactures shelters. >From an excel file, it generates a quote based on dynamic dimensions.
The excel sheet also calculates the dimensions of fabric required for the shelter and the price.
I thought about the OCA product configurator but that doesn't cover the needs.Thank you !Le mer. 11 déc. 2024 à 20:57, Graeme Gellatly <notifications@odoo-community.org> a écrit :Hi,It doesn't really explain very well your question.Is it off plans, is it for pricing, is it for BoMs, for manufacturing machine integration e.g. CNC, is it the paper cutting problem, etc etc etc. I've done a lot of work in this space within custom MTO for manufacturing and pricing of construction materials. The 2 most difficult modules I used to maintain are mrp_dynamic_line (public, but always too risky/aggressive to be OCA) which calculates Production Orders dynamically from template attributes. The second is a DSL for managing the specification for a particular industry to do pricing, send to BoM (using dynamic_line and materials list from DSL, and does calculate all the dimensions) and api to manufacturing equipment on the SO Line which is private. The actual part of that module that handles the dimensions calculation is quite simple. It is just a one2many on sale order line with a few basic fields (and every similar model)Those between them + Odoo + OCA cover maybe 30% of the problem space.If it is custom MTO, then you also have a LOT of product code/cost/attribute/tracking/valuation considerations because every item at least in this case can have a different cost based on those DSL attributes with no real relation to any UoM concept. You need to avoid this if you can.Modern QS stuff, uses google earth to approximate dimension in brownfields, can read pdf plans, has onsite site measure functionality, produces necessary legal docs, quotes, 3d models etc, calculates angles and rakes, material specific things like can waste be reused elsewhere, environmental specific things like wind loading and engineering and legal requirements for them. And it does it in a few minutes, just needing regularly updated component pricing via a csv or similar.Then production planning software manages complex scheduling like the 2d and 3d cutting problems.Then machine specific software handles the rest.But for simple cases, in newer versions of Odoo, and possibly just enterprise, they allow a configuration spreadsheet at the sale to populate the sale. And they have a new Engineering to Order approach. I have two other smaller manufacturing for construction clients who had been using external tools wanting this investigated, but not started yet.On Thu, Dec 12, 2024 at 1:52 AM Ahmed Trigui <notifications@odoo-community.org> wrote:Hello community,I'm looking for a module to calculate awnings dimensions.Is there any app which covers this need please ?Thank you!--
Ahmed TriguiConseiller Analyste fonctionnel+1 514-317-7944
Nouveau
Savez-vous tout sur l'open source ?Découvrir _______________________________________________
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
--
Ahmed TriguiConseiller Analyste fonctionnel+1 514-317-7944
Nouveau
Essayez l'IA OpenSource pendant 30 joursDécouvrir _______________________________________________
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 - 09:16 - 12 Dec 2024 -
Re: Awnings dimensions app
Hello Graeme,Thank you for your answer.This is a company that manufactures shelters. From an excel file, it generates a quote based on dynamic dimensions.
The excel sheet also calculates the dimensions of fabric required for the shelter and the price.
I thought about the OCA product configurator but that doesn't cover the needs.Thank you !Le mer. 11 déc. 2024 à 20:57, Graeme Gellatly <notifications@odoo-community.org> a écrit :Hi,It doesn't really explain very well your question.Is it off plans, is it for pricing, is it for BoMs, for manufacturing machine integration e.g. CNC, is it the paper cutting problem, etc etc etc. I've done a lot of work in this space within custom MTO for manufacturing and pricing of construction materials. The 2 most difficult modules I used to maintain are mrp_dynamic_line (public, but always too risky/aggressive to be OCA) which calculates Production Orders dynamically from template attributes. The second is a DSL for managing the specification for a particular industry to do pricing, send to BoM (using dynamic_line and materials list from DSL, and does calculate all the dimensions) and api to manufacturing equipment on the SO Line which is private. The actual part of that module that handles the dimensions calculation is quite simple. It is just a one2many on sale order line with a few basic fields (and every similar model)Those between them + Odoo + OCA cover maybe 30% of the problem space.If it is custom MTO, then you also have a LOT of product code/cost/attribute/tracking/valuation considerations because every item at least in this case can have a different cost based on those DSL attributes with no real relation to any UoM concept. You need to avoid this if you can.Modern QS stuff, uses google earth to approximate dimension in brownfields, can read pdf plans, has onsite site measure functionality, produces necessary legal docs, quotes, 3d models etc, calculates angles and rakes, material specific things like can waste be reused elsewhere, environmental specific things like wind loading and engineering and legal requirements for them. And it does it in a few minutes, just needing regularly updated component pricing via a csv or similar.Then production planning software manages complex scheduling like the 2d and 3d cutting problems.Then machine specific software handles the rest.But for simple cases, in newer versions of Odoo, and possibly just enterprise, they allow a configuration spreadsheet at the sale to populate the sale. And they have a new Engineering to Order approach. I have two other smaller manufacturing for construction clients who had been using external tools wanting this investigated, but not started yet.On Thu, Dec 12, 2024 at 1:52 AM Ahmed Trigui <notifications@odoo-community.org> wrote:Hello community,I'm looking for a module to calculate awnings dimensions.Is there any app which covers this need please ?Thank you!--
Ahmed TriguiConseiller Analyste fonctionnel+1 514-317-7944
Nouveau
Savez-vous tout sur l'open source ?Découvrir _______________________________________________
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
--
Ahmed TriguiConseiller Analyste fonctionnel+1 514-317-7944
Nouveau
Essayez l'IA OpenSource pendant 30 joursDécouvrir
by Ahmed Trigui - 09:01 - 12 Dec 2024 -
Re: Awnings dimensions app
Hi,It doesn't really explain very well your question.Is it off plans, is it for pricing, is it for BoMs, for manufacturing machine integration e.g. CNC, is it the paper cutting problem, etc etc etc. I've done a lot of work in this space within custom MTO for manufacturing and pricing of construction materials. The 2 most difficult modules I used to maintain are mrp_dynamic_line (public, but always too risky/aggressive to be OCA) which calculates Production Orders dynamically from template attributes. The second is a DSL for managing the specification for a particular industry to do pricing, send to BoM (using dynamic_line and materials list from DSL, and does calculate all the dimensions) and api to manufacturing equipment on the SO Line which is private. The actual part of that module that handles the dimensions calculation is quite simple. It is just a one2many on sale order line with a few basic fields (and every similar model)Those between them + Odoo + OCA cover maybe 30% of the problem space.If it is custom MTO, then you also have a LOT of product code/cost/attribute/tracking/valuation considerations because every item at least in this case can have a different cost based on those DSL attributes with no real relation to any UoM concept. You need to avoid this if you can.Modern QS stuff, uses google earth to approximate dimension in brownfields, can read pdf plans, has onsite site measure functionality, produces necessary legal docs, quotes, 3d models etc, calculates angles and rakes, material specific things like can waste be reused elsewhere, environmental specific things like wind loading and engineering and legal requirements for them. And it does it in a few minutes, just needing regularly updated component pricing via a csv or similar.Then production planning software manages complex scheduling like the 2d and 3d cutting problems.Then machine specific software handles the rest.But for simple cases, in newer versions of Odoo, and possibly just enterprise, they allow a configuration spreadsheet at the sale to populate the sale. And they have a new Engineering to Order approach. I have two other smaller manufacturing for construction clients who had been using external tools wanting this investigated, but not started yet.On Thu, Dec 12, 2024 at 1:52 AM Ahmed Trigui <notifications@odoo-community.org> wrote:Hello community,I'm looking for a module to calculate awnings dimensions.Is there any app which covers this need please ?Thank you!--
Ahmed TriguiConseiller Analyste fonctionnel+1 514-317-7944
Nouveau
Savez-vous tout sur l'open source ?Découvrir _______________________________________________
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 - 08:56 - 11 Dec 2024
