Shreeram Yadav

3 Simple ways to add page navigation icons to your dashboard. 1: When you add a navigation icon alone, tooltips should be added to specify page. 2: Adding the page name at the bottom is great for lesser space. 3: Adding the page name by the side is perfect if you have more space.

٢١١

٣٨ تعليق

PostgreSQL performance under Odoo is a recurring theme in conversations with engineering leaders. When workloads spike, teams often react by scaling hardware. It fixes the symptom, but not the cause. Since Odoo is built entirely on PostgreSQL, its performance hinges on the efficiency of SQL generated by the ORM. That is why the query-level improvements rolled out in versions 17, 18, and now 19 matter so much. They reduce overhead at the source and allow PostgreSQL to execute queries efficiently at scale. I have long maintained that query optimization drives the most meaningful performance gains. It is encouraging to see Odoo putting focus here across recent releases. With Odoo 19 now live and support for version 16 ended, I have compiled a blog that details the PostgreSQL performance enhancements introduced from version 17 through 19. 👉 Read here: https://lnkd.in/dza9gaVq

٤٨

٤ تعليق

Every company is racing to add AI as the trend gains popularity.  However, Odoo has a different approach. In fact, Odoo has been using AI long before the term became trendy. For example, Odoo 16 introduced AI in its website builder that can automatically generate content and layouts tailored to specific industries. When Odoo 19 launched last month, I was there to witness every feature. Now, with Odoo 19, they aren't just putting AI everywhere to follow the trend. Instead, they ask: What business problems can AI actually solve?  That's why Odoo uses AI to:  - Automate low-value tasks, so employees can focus on the work that matters. - Make processes smarter with predictions.   - Improve usability with natural language-based actions.  Odoo uses AI when it's needed, not for overuse. But for real, tangible impact.  And that's what makes Odoo's vision unique.  What do you think about the AI adoption in Odoo 19? Note: This picture was taken in front of Belgium’s Atomium, right after Odoo’s annual event unveiling Odoo 19 and its new AI app

٦٥

٥ تعليق

Comparing Odoo Environments: Local | Staging | Live Every Odoo project relies on three key environments, each serving a distinct purpose: 🔹 Local – Developer environment for coding, debugging, and safe module testing. 🔹 Staging – A replica of production, used for QA, UAT, and stability checks before deployment. 🔹 Live (Production) – The actual business environment handling real data and daily operations. A structured use of these environments ensures smoother rollouts, reliable performance, and minimal risk to business continuity. At OctagoTech, we design and manage Odoo environments with a strong focus on stability and efficiency, helping organizations operate with confidence. #odoo #odoo19 #odooai #odooerp #erp

٤٤

٣ تعليق

💻 Odoo Devs, Get Ready for Cleaner Code! ✨ New in Odoo 19: QWeb just got simpler! The t-call update replaces bulky <t t-set> tags with clean attributes directly in the call. ✅ Easier to write & maintain ✅ Faster template development ✅ Improved readability for everyone #Odoo19 #OdooDevelopment #QWeb #OdooTemplates #PythonProgramming #OdooERP #CodeOptimization #DeveloperTools #TechUpdate #CybrosysTechnologies #BusinessAutomation

١٨٢

🚨 Your ERP is Costing You Growth. Here’s How Odoo Fixes That in 2025 🚨 Habibi, Saudi Arabia’s digital transformation is no longer just a dream. It’s here, and Vision 2030 is driving it forward. Yet, many companies are facing a hard truth: legacy ERP systems can’t keep up with modern demands. Here enters Odoo 19, more than just an upgrade—it’s a powerful engine driving growth and transforming operations for businesses in Saudi Arabia. Here's why I know Odoo 19 is the exactly the leap your business needs in 2025: - Streamlined User Experience: Arabic-first UI designed for fast onboarding. - OWL-Powered Speed: Faster, more responsive experience for all teams. - eCommerce Integration: Seamless connections with Google Merchant, Gelato, and payment gateways. - End-to-End Automation: From invoicing to inventory tracking, automation is key to improving efficiency. - Built for Saudi Arabia: Seamless ZATCA Compliance - Real-Time Integration: QR codes, cryptographic stamps, and invoice validation. - Automated VAT & Archiving: Say goodbye to audit headaches. - Privacy-First Infrastructure: Meets Saudi data protection laws by default. To sum it up, here's why Odoo is dominating the Saudi Market: - Modular Growth Path: Start with core functions, scale as you grow. - Fast Go-Live: Odoo can be up and running in weeks, not months. - Arabic Support & Local Features: Full language, tax, and payroll support. - Certified Local Experts: At Carpe Diem, we partner with certified experts who understand the Saudi business landscape. To conclude, here some pearls of wisdom from my experience or you can say best practices for successful Odoo Implementation: - Partner Wisely: Work with certified local Odoo experts. - Prioritize People: Focus on team training and smooth transitions. - Integrate Early: Connect to ZATCA, payment gateways, and banks from day one. Odoo’s impact on Saudi Arabia’s businesses is undeniable—its seamless compliance, scalability, and rapid deployment are aligning with Vision 2030 to propel the Kingdom’s businesses into the future. 💬 What’s your take on the rise of Odoo in Saudi Arabia? How do you think it’s changing the ERP landscape? Let’s discuss in the comments below. #Odoo #ERP #SaudiArabia #Vision2030 #AI #DigitalTransformation #BusinessGrowth #ZATCA #ECommerce #CarpeDiem #TechInnovation

٢٤

٨ تعليق

Maybe SuiteBrowser — the purpose-built Web browser for NetSuite users — isn’t such a crazy idea after all. 🤔 Yesterday, Atlassian acquired The Browser Company, makers of Arc and Dia. Their vision: “The web browser is one of the most important tools we use… The world has changed in the past 15 years, but our web browsers look and behave pretty much the same. It’s time to push the web browser forward again.” That’s what I’ve been exploring with SuiteBrowser — a browser designed specifically for the NetSuite ecosystem. Not a generic browser with plugins. Not a reskinned Chrome. But a browser purpose-built for how NetSuite users actually work. Some of SuiteBrowser's features include: • Enhanced SuiteQL tools (Query Tool + Schema Tool) • Context Bridge — a local Web API powered by your NetSuite session, enabling queries, saved searches, record access, and even ad hoc SuiteScript from external apps • SuiteConsole — an alternative environment for SuiteScript development • Multi-window/tab layouts designed for NetSuite workflows If Arc and Dia are rethinking how we interact with the web in general, SuiteBrowser is about rethinking how we work with NetSuite. And I’m looking forward to getting back to work on it — once I wrap up the Suite.js updates that I’ve been heads-down on. 🔗 Atlassian x Browser Company news: https://lnkd.in/eva2sapy 🔗 SuiteBrowser Preview: https://lnkd.in/e_ZN2Rez 🔗 Suite.js: https://suitejs.io

٨١

١ تعليق واحد

Let's get into the real financial pain points Odoo users face. Especially in the UK and EU context. Here are a few critical errors that tend to sneak in: 🚩 VAT Misreporting: Usually caused by incorrect tax tag mapping or missing fiscal positions. Fix it by reviewing how taxes are applied across sales/purchase journals, especially if you're trading across borders. 🚩 CIS Submission Errors: If you’re working in construction and CIS is set up incorrectly, your reports (and HMRC submissions) will be off. Odoo handles CIS, but it needs the right flow from supplier invoice → reverse charge → subcontractor logic. 🚩 Duplicate Entries: It’s not always a user mistake. Sometimes it’s poor import structure or workflows with no checks in place. Train teams on validation steps, and lean into AI + bank reconciliation tools where possible. None of these are caused by Odoo “not working.” They come from setups that are not designed with reporting in mind. And once they’re baked in… fixing them can become messy. That’s why we should be slowing down early, question assumptions, and work backwards from the reports the business actually needs, whether that means adjusting configuration or building something more robust where it matters. What are the financial pains you are constantly seeing across projects?

٧١

٨ تعليق