Skip ke Konten
Odoo Menu
  • Login
  • Uji coba gratis
  • Aplikasi
    Keuangan
    • Akuntansi
    • Faktur
    • Pengeluaran
    • Spreadsheet (BI)
    • Dokumen
    • Tanda Tangan
    Sales
    • CRM
    • Sales
    • POS Toko
    • POS Restoran
    • Langganan
    • Rental
    Website
    • Website Builder
    • eCommerce
    • Blog
    • Forum
    • Live Chat
    • eLearning
    Rantai Pasokan
    • Inventaris
    • Manufaktur
    • PLM
    • Purchase
    • Maintenance
    • Kualitas
    Sumber Daya Manusia
    • Karyawan
    • Rekrutmen
    • Cuti
    • Appraisal
    • Referensi
    • Armada
    Marketing
    • Social Marketing
    • Email Marketing
    • SMS Marketing
    • Acara
    • Otomatisasi Marketing
    • Survei
    Layanan
    • Project
    • Timesheet
    • Layanan Lapangan
    • Meja Bantuan
    • Planning
    • Appointment
    Produktivitas
    • Diskusi
    • Approval
    • IoT
    • VoIP
    • Pengetahuan
    • WhatsApp
    Aplikasi pihak ketiga Odoo Studio Platform Odoo Cloud
  • Industri-Industri
    Retail
    • Toko Buku
    • Toko Baju
    • Toko Furnitur
    • Toko Kelontong
    • Toko Hardware
    • Toko Mainan
    Makanan & Hospitality
    • Bar dan Pub
    • Restoran
    • Fast Food
    • Rumah Tamu
    • Distributor Minuman
    • Hotel
    Real Estate
    • Agensi Real Estate
    • Firma Arsitektur
    • Konstruksi
    • Estate Management
    • Perkebunan
    • Asosiasi Pemilik Properti
    Konsultansi
    • Firma Akuntansi
    • Mitra Odoo
    • Agensi Marketing
    • Firma huku
    • Talent Acquisition
    • Audit & Sertifikasi
    Manufaktur
    • Tekstil
    • Logam
    • Perabotan
    • Makanan
    • Brewery
    • Corporate Gift
    Kesehatan & Fitness
    • Sports Club
    • Toko Kacamata
    • Fitness Center
    • Wellness Practitioners
    • Farmasi
    • Salon Rambut
    Perdagangan
    • Handyman
    • IT Hardware & Support
    • Sistem-Sistem Energi Surya
    • Pembuat Sepatu
    • Cleaning Service
    • Layanan HVAC
    Lainnya
    • Organisasi Nirlaba
    • Agen Lingkungan
    • Rental Billboard
    • Fotografi
    • Penyewaan Sepeda
    • Reseller Software
    Browse semua Industri
  • Komunitas
    Belajar
    • Tutorial-tutorial
    • Dokumentasi
    • Sertifikasi
    • Pelatihan
    • Blog
    • Podcast
    Empower Education
    • Program Edukasi
    • Game Bisnis 'Scale Up!'
    • Kunjungi Odoo
    Dapatkan Softwarenya
    • Download
    • Bandingkan Edisi
    • Daftar Rilis
    Kolaborasi
    • Github
    • Forum
    • Acara
    • Terjemahan
    • Menjadi Partner
    • Layanan untuk Partner
    • Daftarkan perusahaan Akuntansi Anda.
    Dapatkan Layanan
    • Temukan Mitra
    • Temukan Akuntan
    • Temui penasihat
    • Layanan Implementasi
    • Referensi Pelanggan
    • Bantuan
    • Upgrades
    Github Youtube Twitter Linkedin Instagram Facebook Spotify
    +1 (650) 691-3277
    Dapatkan demo
  • Harga
  • Bantuan

Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

  • CRM
  • e-Commerce
  • Akuntansi
  • Inventaris
  • PoS
  • Project
  • MRP
All apps
Anda harus terdaftar untuk dapat berinteraksi di komunitas.
Semua Post Orang Lencana-Lencana
Label (Lihat semua)
odoo accounting v14 pos v15
Mengenai forum ini
Anda harus terdaftar untuk dapat berinteraksi di komunitas.
Semua Post Orang Lencana-Lencana
Label (Lihat semua)
odoo accounting v14 pos v15
Mengenai forum ini
Help

Style Error after Upgrade from Odoo 14 to Odoo 16

Langganan

Dapatkan notifikasi saat terdapat aktivitas pada post ini

Pertanyaan ini telah diberikan tanda
1 Balas
2589 Tampilan
Avatar
Bandele Attah

After restoring a database upgraded from Odoo 14 to Odoo 16 we receive the Style error.

Style error

The style compilation failed, see the error below. Your recent actions may be the cause, please try reverting the changes you made.

Could not get content for /bi_view_editor/static/src/css/bve.css.

Uninstalled OCA / reporting\-engine /bi_view_editor,\ upgraded\ all\ modules\ in\ the\ database,\ regenerated\ asset\ bundles\ and\ sent\ the\ database\ away\ for\ upgrade\.

This\ did\ not\ clear\ the\ issue\.\ Still\ got\ the\ same\ style\ error\.

After\ selecting\ OK\ for\ the\ style\ error\ Odoo\ dashboard\ is\ not\ visible\. \ Blank\ page\ with\ none\ of\ the\ application\ icons\.

Restored\ the\ upgraded\ dump\ to\ Odoo\.sh\.  

This\ allowed\ access\ to\ the\ Odoo\ Dashboard\ but\ all\ the\ style\ sheets\ are\ in\ error\.


If\ for\ example\ sale\ order\ form\ selected\ get\ message\.

How\ can\ the\ backend\ assets\ be\ forced\ to\ regenerate\ either\ at\ Odoo\ 14\ before\ database\ sent\ for\ upgrade\ or at\ Odoo\ 16\ after\ the\ upgrade\?


Or\ How\ can\ the\ reference\ to 

UncaughtPromiseError\ >\ TypeError
Uncaught\ Promise\ >\ viewFieldsInfo\ is\ undefined
TypeError:\ viewFieldsInfo\ is\ undefined
\ \ \ \ processArch/https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68188:21\ \(/web/static/src/legacy/legacy_load_views\.js:73\)
\ \ \ \ traverse@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68122:10\ \(/web/static/src/legacy/legacy_load_views\.js:7\)
\ \ \ \ traverse/https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68124:21\ \(/web/static/src/legacy/legacy_load_views\.js:9\)
\ \ \ \ each@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_common\.js:1900:17\ \(/web/static/lib/underscore/underscore\.js:1330\)
\ \ \ \ traverse@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68123:11\ \(/web/static/src/legacy/legacy_load_views\.js:8\)
\ \ \ \ traverse/https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68124:21\ \(/web/static/src/legacy/legacy_load_views\.js:9\)
\ \ \ \ each@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_common\.js:1900:17\ \(/web/static/lib/underscore/underscore\.js:1330\)
\ \ \ \ traverse@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68123:11\ \(/web/static/src/legacy/legacy_load_views\.js:8\)
\ \ \ \ traverse/https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68124:21\ \(/web/static/src/legacy/legacy_load_views\.js:9\)
\ \ \ \ each@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_common\.js:1900:17\ \(/web/static/lib/underscore/underscore\.js:1330\)
\ \ \ \ traverse@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68123:11\ \(/web/static/src/legacy/legacy_load_views\.js:8\)
\ \ \ \ traverse/https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68124:21\ \(/web/static/src/legacy/legacy_load_views\.js:9\)
\ \ \ \ each@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_common\.js:1900:17\ \(/web/static/lib/underscore/underscore\.js:1330\)
\ \ \ \ traverse@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68123:11\ \(/web/static/src/legacy/legacy_load_views\.js:8\)
\ \ \ \ processArch@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68174:13\ \(/web/static/src/legacy/legacy_load_views\.js:59\)
\ \ \ \ generateLegacyLoadViewsResult@https://bizanova\-edgeupgrade\.odoo\.com/web/assets/debug/web\.assets_backend\.js:68148:64\ \(/web/static/src/legacy/legacy_load_views\.js:33\)
\ \ \ \ loadViews/cache\[key\]https://bizanova-edgeupgrade.odoo.com/web/assets/debug/web.assets_backend.js:57391:41 (/web/static/src/views/view_service.js:115)

0
Avatar
Buang
Avatar
Cybrosys Techno Solutions Pvt.Ltd
Jawaban Terbai

Hi,


The Style error usually appears when an asset file path (like /bi_view_editor/static/src/css/bve.css) no longer exists after the upgrade. This often happens when a third-party module was removed or renamed between Odoo 14 and 16.


Ensure that all custom and OCA modules referenced in the old database are either installed, replaced, or fully uninstalled before performing the upgrade.


On the upgraded Odoo 16 instance, clear all asset bundles by deleting the /web/assets/ directories and running Odoo with --update=all --load=web,base to force full asset regeneration.


If the issue persists, connect to the upgraded database in developer mode and check ir.attachment records where name like '%assets_%' — delete those to trigger a clean rebuild of assets.


For the “viewFieldsInfo is undefined” JS error, one of the legacy views still contains deprecated XML fields; identify and correct or remove those custom views (often leftover from Odoo 14).


To prevent recurrence, test the upgrade on a clean database clone with all obsolete modules uninstalled and ensure all dependencies are migrated to their Odoo 16 equivalents before re-upgrading.


Hope it helps.

0
Avatar
Buang
Menikmati diskusi? Jangan hanya membaca, ikuti!

Buat akun sekarang untuk menikmati fitur eksklufi dan agar terlibat dengan komunitas kami!

Daftar
Komunitas
  • Tutorial-tutorial
  • Dokumentasi
  • Forum
Open Source
  • Download
  • Github
  • Runbot
  • Terjemahan
Layanan
  • Odoo.sh Hosting
  • Bantuan
  • Peningkatan
  • Custom Development
  • Pendidikan
  • Temukan Akuntan
  • Temukan Mitra
  • Menjadi Partner
Tentang Kami
  • Perusahaan kami
  • Aset Merek
  • Hubungi kami
  • Tugas
  • Acara
  • Podcast
  • Blog
  • Pelanggan
  • Hukum • Privasi
  • Keamanan
الْعَرَبيّة Català 简体中文 繁體中文 (台灣) Čeština Dansk Nederlands English Suomi Français Deutsch हिंदी Bahasa Indonesia Italiano 日本語 한국어 (KR) Lietuvių kalba Język polski Português (BR) română русский язык Slovenský jazyk slovenščina Español (América Latina) Español ภาษาไทย Türkçe українська Tiếng Việt

Odoo adalah rangkaian aplikasi bisnis open source yang mencakup semua kebutuhan perusahaan Anda: CRM, eCommerce, akuntansi, inventaris, point of sale, manajemen project, dan seterusnya.

Mudah digunakan dan terintegrasi penuh pada saat yang sama adalah value proposition unik Odoo.

Website made with

Odoo Experience on YouTube

1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.

Live support on Youtube
Watch now