Missing from Readme: How should Industry modules be used?

[mrlowe]

We'd love to use (for example) the accounting_firm industry module when demoing Odoo to an accounting firm, but if we manually install industry modules their demodata tends to collide with demodata for modules like website.

Are we using the modules in a way that wasn't intended? Is the industry repo out of date for Odoo 19? A note in the Readme explaining the intended use of the industry repo would help!

[dhrs-odoo]

Hello @mrlowe
Greetings of the day!!
I’ve tested the accounting_firm industry on a fresh database in Runbot, and everything is working perfectly.
If you prefer not to install it manually, you can simply use industry Runbot where all industries are already available. Just wake up the required industry branch, and you’re good to go.

If you still face any issue do let us know 😇
Thanks!!

[mrlowe]

Thank you for the response @dhrs-odoo!

I’ve tested the accounting_firm industry on a fresh database in Runbot, and everything is working perfectly. If you prefer not to install it manually, you can simply use industry Runbot where all industries are already available. Just wake up the required industry branch, and you’re good to go.

Runbot is doing something special, though, because when install that industry on runbot I get this:

And I've never seen this dialog on v19 run locally. Do you know what is happening here that the server provides a dialog asking about demodata? And if you have a local odoo 19 environment, are you able to successfully install the industry modules there?

[dhrs-odoo]

Hello @mrlowe
Greetings of the day !!
Yes, this dialog is part of our industry. When you import the module locally, you will see this dialog box. The purpose of this dialog is to let the user choose whether they want to start with a completely blank database or with demo examples.
In your local setup, you don’t see it because you install the module using the -i command, while on the runbot it appears since the module is imported directly .
I hope this helps answer your question 😇

[mrlowe]

@dhrs-odoo thanks so much for working through this with me, this commitment to actually solving a problem is what's great about the odoo team!

I apologize, I think I gave you a bad example in using accounting firm; that one does install successfully locally. Let's talk about textile_manufacturing, as it is a better example. And I think we're closing in on the confusion.

In your local setup, you don’t see it because you install the module using the -i command

I'm not actually using -i at the command line, I'm cloning odoo/industry and then installing from the local module. when I do that on a db with its demodata flag set, I get errors like the following:

But I realized that when you're installing on runbot, you're actually using the industry category -- I didn't realize there was an industry category -- and installing from there!

When I try that on local, I do get the demodata dialog, but it still shows an error related to that design key:

On runbot, though, it installs fine. Could it be because a runbot image already has a lot of things/dependencies preinstalled? Could the industry category locally be installing from my industry clone?

[dhrs-odoo]

Hello @mrlowe
Greetings of the day !!
The issue is caused by a unique name constraint. In the standard demo data, a Design project tag already exists, and the same tag is being created again in the mentioned industry module, which leads to the conflict.
We currently have an ongoing task addressing this problem, and the fix will be merged soon.
Thank you for reporting the issue and for your patience 😇

[mrlowe]

Thank you @dhrs-odoo . Is there a GitHub issue you can link to? I'm still confused about why it installs without the collision on runbot.