Skip to Content
Meniu
Trebuie să fiți înregistrat pentru a interacționa cu comunitatea.
Această întrebare a fost marcată
2 Răspunsuri
201 Vizualizări

Hi all,


I am new to Odoo Studio and i want to know what is the best practice of developing new features with Odoo Studio. 

How to I do the source control / version control when i do development with Odoo studio? Which environment should i use? PRD, testing or dev? 


Anything I should aware when i use Odoo Studio? 


Thanks 

Iris

Imagine profil
Abandonează
Cel mai bun răspuns

How to I do the source control / version control when i do development with Odoo studio?

There is no version control built in into Odoo for Studio customization. You can however Export Studio customization via Settings -> Technical --> Database Structure -> Studio Export and version control it externally.

Which environment should i use? PRD, testing or dev?

Depends on whether you know what you're doing. Given the fact that you can Export and Import Studio customization, I'd suggest to start with a testing environment, test your changes and then import it to production.

Anything I should aware when i use Odoo Studio?

Studio creates generic code. This is especially true for view modifications. Expect headaches with these when upgrading Odoo to newer versions.


Example:

<data>
  <xpath expr="/form/sheet/notebook/page[@name='lead']/group/group[2]/field[@name='function']" position="after">
    <field name="x_studio_demo"/>
  </xpath>
</data>

Above view addition doesn't do more than adding a field Demo to a particular area of the CRM form:


Personal opinion:

If this looks oddly specific to you - it is. And that's one general draw back when using Studio. Thus, when modifying views with Studio and you need to debug or upgrade it, be prepared to count nodes a lot.

Another thing to keep in mind: Don't mix custom developments (actual custom modules) with Studio customization. This is especially true when you feel like you need to use a x_studio_-field (a field created via Studio) in a custom module. I guarantee you would regret it at some point.

A general word of advice: If you have to use Studio, don't overdo it just because it looks simple right now. Any modification will have to be maintained in one or the other way. Potentially not having actual source code at hand to read makes debugging no fun. Also, Studio customization can't be documented directly (views may be edited later on but the lack of actual model files will leave you with guess-worthy field definitions). Don't forget you're manipulating your ERP software, thus, handle with care.

Imagine profil
Abandonează

Also, you will have to repeat the changes that you made in your development database to apply it to testing or production.

https://odootricks.tips/odoo-studio/

Cel mai bun răspuns

Hi,


Odoo Studio is great for quick customizations but not complex development. Always start with a clear goal, sketch your UI changes, and never develop directly in your production environment. Use separate development and testing environments first. Make small, incremental changes, testing after each one, and meticulously document everything since Studio lacks built-in change tracking. Be aware of Studio's limitations, especially its limited code customization and potential performance impacts.


Since Studio lacks native version control, manually document all changes and, if you have Odoo Enterprise, export your customizations as a module and add it to a Git repository. This provides snapshots of your changes. Remember that Studio customizations can be affected by Odoo upgrades, so test thoroughly after each upgrade. For complex features, consider traditional Odoo development instead.


Reference:-

https://www.youtube.com/watch?v=laF9XUPaCc4

https://www.odoo.com/documentation/19.0/applications/studio.html

https://www.youtube.com/playlist?list=PL1-aSABtP6ADrLdkRuSAuLPd7qqql4T8c

https://www.cybrosys.com/blog/how-to-customize-views-reports-in-odoo-18-studio


Hope it helps

Imagine profil
Abandonează
Related Posts Răspunsuri Vizualizări Activitate
2
mar. 25
1519
0
oct. 25
320
0
oct. 25
295
2
oct. 25
5849
2
oct. 25
599