[19.0][IMP] attribute set: Add autocomplete on widget suggestion#228
Draft
[19.0][IMP] attribute set: Add autocomplete on widget suggestion#228
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)
And small FIX in _build_attribute_field()
[UPD] README.rst [UPD] README.rst
[UPD] README.rst
…d attribute_set [CHG] add required columns on attributes on attribute set form view attribute_set 13.0.1.0.1
[UPD] README.rst [UPD] README.rst [ADD] icon.png Apply dotfiles [UPD] Update attribute_set.pot attribute_set 14.0.1.0.1 [UPD] README.rst [IMP] update dotfiles [ci skip]
[UPD] Update attribute_set.pot attribute_set 14.0.1.1.0
[UPD] Update attribute_set.pot [UPD] README.rst
When you define an attribute as a select field and add a related model, you have the option to "Load attribute options". On this wizard, an "option_ids" dummy field is created via fields_view_get. This change deletes option_ids from create (once the options are created) and read
menu items are visible only for two levels
[UPD] Update attribute_set.pot [UPD] README.rst [UPD] README.rst
…ss data (tree/search...) Use get_view() to get the view_type directly. Moreover, this will allow to test it through odoo.tests.Form(). Add attribute_set_id field in test form (as it should be included in inherited views
If user is not in the base.group_erp_manager group, the value_ref field selection function will be computed without access rights on ir.model. So, hide the field for users not in that group.
Add all the attributes defined for the model into the list of fields to load to display the form view. Wihout this change a JS error occurs when displaying the form view of a x2many field for a model defining attributes. The origin of the error comes from the the get_views method which is called for the type 'form' only. In this case it's important to add all the custom attributes to the list of fields defined on the model for the view. When the same method is called without restriction it will load all the views. Since odoo include all the fields defined on the model for the search view, the error doesn't occur when using the form view from a menu action.
As model_id is referring to non accessible models for common users, set a related field in order to be able to use it in views domains. Moreover, add a domain on attribute_set_id field in attribute owner mixin in order to simplify inherited views.
As attribute view building is accessing ir.model records, do it with sudo. [UPD] Update attribute_set.pot [BOT] post-merge updates [UPD] Update attribute_set.pot
Currently translated at 100.0% (125 of 125 strings) Translation: odoo-pim-16.0/odoo-pim-16.0-attribute_set Translate-URL: https://translation.odoo-community.org/projects/odoo-pim-16-0/odoo-pim-16-0-attribute_set/es/
- Fix attribute_set native field updates during module upgrades - Fix Attribute record duplication to ensure unique names - Fix Attribute error where bool has no startswith method - Fix attribute set placeholder handling to improve compatibility - Fix popup attributes view to show more than 2 characters - Fix view styling and other compatibility improvements
- Shorten long comments to stay under 88 character limit - Update test file comments to comply with line length requirements - Format code to adhere to linter standards
- Fix native attribute creation to prevent "Properties of base fields cannot be altered" error - Update attribute_attribute model to properly handle native vs custom attributes - Correctly filter ir.model.fields values during native attribute creation to avoid modifying base fields - Add proper field ID preservation for native attribute linking - Update UI form to make attribute fields visible for native attributes - Fix test assertions to match actual working behavior - Clean up linting errors and remove temporary files - Preserve full functionality for both native and custom attributes - Remove unnecessary debug code and ensure code quality standards - Fix view rendering issues for proper attribute display in forms These changes ensure the attribute_set module works properly in Odoo 19, especially for native attributes that link to existing fields without attempting to modify their properties. The implementation maintains backward compatibility while fixing the core migration issues.
bosd
force-pushed
the
19.0-imp-attribute_set
branch
from
f27b64a to
fd67d7c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.