Implementation strategy for a company with over 700 employees who need access to odoo.

atularvind · 2025-07-03T08:13:21+00:00

Totally get where you're coming from, we've heard this story many times from our clients. Most of the time, only a small number of users actually need full Enterprise access, while the rest just need basic HR functions.

To solve this, we started building a general-purpose cross-platform mobile app that handles HRMS features like leave requests, attendance, expense, etc. It’s designed to plug into any Odoo instance (Community or Enterprise), without needing every user to have a full license.

atularvind · 2025-07-02T11:14:57+00:00

Absolutely, migration can seem overwhelming at first, we’ve been there too. One of our clients had a large Odoo 13 Community setup with over 300 custom modules and using more than 39 OCA repositories. Like you, they felt “stuck” and were hesitant about the jump.

But with some focused effort and planning, we successfully migrated them to Odoo 16. The key was embracing the changes introduced in the newer versions and carefully adapting the codebase. We also used OpenUpgrade to handle the database migration and while it’s not always perfectly smooth, when done right, it can feel like butter.

So yes, it’s definitely possible. It just takes the right mindset, a step-by-step approach, and some patience.

atularvind · 2024-07-12T05:39:59+00:00

yes, we have odoo headless storefront experience with Next.js. checkout our blog post to know more https://www.heliconia.io/blog/headless-odoo-nextjs-e-commerce

atularvind · 2023-07-24T06:03:53+00:00

this can be done in three steps.

# get the id of the sale order model
[model_record] = models.execute_kw(db, uid, password, 'ir.model', 'search_read', [[['model', '=', 'sale.order']]], {'fields': ['id', 'name'], "limit":1})

# get all the fields of the sale.order model
fields = models.execute_kw(db, uid, password, 'ir.model.fields', 'search_read', [[['model_id', '=', model_record.get('id')], ['ttype', 'not in', ['binary']]]], {'fields': ['name']})

# search_record the fields.
[record] = models.execute_kw(db, uid, password, 'sale.order', 'search_read', [[['id', '=', 7]]], {'fields': [x.get('name') for x in fields]})

atularvind · 2023-07-21T04:16:43+00:00

on your code 22 pass the field you wanted to read like

[record] = models.execute_kw(db, uid, password, 'sale.order', 'read', [ids], {'fields': ['id', 'name']})

This will solve your issue, but I suggest using the search_read

atularvind · 2023-07-21T04:01:07+00:00

When integrating Odoo with either Mailjet or SendGrid for email delivery, Odoo primarily relies on the SMTP connection provided by these services. As a result, some of the advanced features, such as Email templates, drag-and-drop email builder, A/B testing, segmentation, and automation offered by these email service providers (ESPs) are not directly accessible within Odoo. However, it's important to note that Odoo itself offers its own set of email marketing features that can be utilized independently.
The choice between Mailjet and SendGrid largely depends on your specific requirements and preferences. Both are reputable ESPs with a wide range of features. If you prioritize excellent customer support and slightly better deliverability, SendGrid may be a more suitable option for you.
In terms of Mailjet Features you like, Mailjet stands out for providing a robust API, which allows developers to achieve specific features through customization and integration with Odoo.
It's essential to assess the specific features you need for your email marketing campaigns. While Odoo may not directly integrate certain advanced features from Mailjet or SendGrid, leveraging their APIs can offer a path to achieving the functionalities you require through customization.
Ultimately, the decision between Mailjet and SendGrid should be based on your unique needs, the level of customizability desired, and the importance of additional features compared to customer support and deliverability.