[MIG] pim: Migration to 17.0 #194
Conversation
New organization : - attribute_set (former base_custom_attribute) - product_attribute_set (former pim_custom_attribute but without menus) - pim (The "PIM application" former pim_base) - pim_attrubute_set (depends on product_attribute_set and adds menus in the PIM application)
attribute_set need 'include_native_attribute' param in context in order to work properly
Currently translated at 100.0% (19 of 19 strings) Translation: odoo-pim-14.0/odoo-pim-14.0-pim Translate-URL: https://translation.odoo-community.org/projects/odoo-pim-14-0/odoo-pim-14-0-pim/es/
|
UncaughtPromiseError > EvalError Attribute Groups - Sort attributes on this one too. |
kobros-tech
force-pushed
the
17.0-mig-pim
branch
from
aa08978 to
e2031bc
Compare
|
The bug is fixed in a commit for PR #190, we can review in OCA boat. Screencast.2025-02-10.14.46.14.mp4 |
kobros-tech
force-pushed
the
17.0-mig-pim
branch
from
e2031bc to
785a903
Compare
|
In odoo to have your passed in context key to the current view not stripped away when you open another view from current one like wizard for example, you must suffix it with _view_ref. In case of opening a view from menu item via action it happens too, same as here! In this list view the sequence field is shown if context key is True, but this key is stripped away since odoo 17.0 unless it is lang or ends with _view_ref I strongly suggest we write about this in the wiki, @pedrobaeza @dnplkndll
|
|
Not sure to understand the possible change. Can you please redact the possible sentence to add to the migration guide? |
|
@pedrobaeza |
kobros-tech
force-pushed
the
17.0-mig-pim
branch
from
d070a5e to
ede907d
Compare
|
@wlin-kencove |
|
This module succeeded to run when I patched a fix to odoo code, I will introduce an isuue about that and refer to this PR there. Screencast.2025-02-19.23.24.38.mp4 |
|
Reference to odoo FIX PR that introduced in the patch file: |
kobros-tech
force-pushed
the
17.0-mig-pim
branch
from
ede907d to
eed91a4
Compare
There was a problem hiding this comment.
Deleting attributes will remove the fields from the database, which is good. In previous version the field would be removed form the view/model but the x_field was still in the db. This seems like it is resolved.
Only attribute associated with the item's attribute set is displayed in the note which is good. Previously the view was bugged and displayed all attributes even from unrelated attribute sets. This seems to be addressed.
Multi select display seems okay, could probably use a tag widget but this will work as well.
|
Ready to merge |
[17.0][MIG] attribute_set: Migration to 17.0 #190
[17.0][MIG] product_attribute_set: Migration to 17.0 #191