How do I use the vendor.evaluation.template model? or What operations can I perform on vendor.evaluation.template?

Response: To use the vendor.evaluation.template model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Explain the purchase_order_purchase_team_analysis_rel table schema. or What is stored in purchase_order_purchase_team_analysis_rel?

Response: The purchase_order_purchase_team_analysis_rel table has 2 columns and 2 foreign key relationships. It stores data related to purchase order purchase team analysis rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


How do I use the mrp.bom.line model? or What business logic is in mrp.bom.line?

Response: To use the mrp.bom.line model, you need to provide values for required fields: product_qty, bom_id, product_id, product_uom_id. Readonly fields: product_tmpl_id, company_id, product_uom_category_id, parent_product_tmpl_id, possible_bom_product_template_attribute_value_ids, allowed_operation_ids, child_bom_id, child_line_ids, attachments_count, branch_id, cost, operation_two_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: product_tmpl_id [readonly] [computed] [no_copy]; company_id [readonly] [computed] [no_copy]; product_qty [required] [has_default]; product_uom_category_id [readonly] [computed] [no_copy]; bom_id [required]; parent_product_tmpl_id [readonly] [computed] [no_copy]; possible_bom_product_template_attribute_value_ids [readonly] [computed] [no_copy]; allowed_operation_ids [readonly] [computed] [no_copy]; child_bom_id [readonly] [computed] [no_copy]; child_line_ids [readonly] [computed] [no_copy]; attachments_count [readonly] [computed] [no_copy]; branch_id [readonly] [computed] [no_copy]; cost [readonly] [computed] [no_copy]; product_id [required]; operation_two_ids [readonly] [computed] [no_copy]; product_uom_id [required] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What are the relationships in report.stock.report_stock_rule? or How does report.stock.report_stock_rule relate to other models?

Response: The report.stock.report_stock_rule model has no explicit relational fields defined in its field metadata.


What is the module hierarchy for product.ribbon? or Describe the implementation of product.ribbon.

Response: The product.ribbon model is defined in module: website_sale. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: name_get.


Show me the relational structure of sh.tsp.top.purchasing.product.wizard. or Describe the many2many relations for sh.tsp.top.purchasing.product.wizard.

Response: The sh.tsp.top.purchasing.product.wizard model has 3 relational fields: company_ids -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids. One2many fields: none.


How to query approval.matrix.purchase.agreement.line data? or How to work with approval.matrix.purchase.agreement.line fields?

Response: To use the approval.matrix.purchase.agreement.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: sequence2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: user_ids [required]; minimum_approver [required] [has_default]; sequence2 [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What columns have default values in approval_matrix_direct_purchase? or What data types are used in approval_matrix_direct_purchase?

Response: Columns in approval_matrix_direct_purchase: id (integer) [NOT NULL] [DEFAULT: nextval('approval_matrix_direct_purchase_id_seq'::regclass)] [PRECISION: 32]; campaign_id (integer) [PRECISION: 32] [COMMENT: Campaign]; source_id (integer) [PRECISION: 32] [COMMENT: Source]; medium_id (integer) [PRECISION: 32] [COMMENT: Medium]; access_token (character varying) [COMMENT: Security Token]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [NOT NULL] [COMMENT: Name]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; branch_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Branch]; minimum_amt (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Minimum Amount]; maximum_amt (double precision) [NOT NULL] [PRECISION: 53] [COMMENT: Maximum Amount]; order_type (character varying) [COMMENT: Order Type]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 16. Statistics: 10 nullable, 1 with defaults, 0 with length constraints.


What fields are readonly in mrp.consumption.warning.line? or How to work with mrp.consumption.warning.line fields?

Response: To use the mrp.consumption.warning.line model, you need to provide values for required fields: mrp_consumption_warning_id, mrp_production_id, product_id. Readonly fields: mrp_consumption_warning_id, mrp_production_id, consumption, product_id, product_uom_id, product_consumed_qty_uom, product_expected_qty_uom, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: mrp_consumption_warning_id [required] [readonly]; mrp_production_id [required] [readonly]; consumption [readonly] [computed] [no_copy]; product_id [required] [readonly]; product_uom_id [readonly] [computed] [no_copy]; product_consumed_qty_uom [readonly]; product_expected_qty_uom [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How to create records in list.pay? or How to query list.pay data?

Response: To use the list.pay model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Describe the field structure of mr_line.pr.wizard. or What data can be stored in mr_line.pr.wizard?

Response: The mr_line.pr.wizard model has 8 fields. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: pr_wizard_line (one2many) -> mr_line.pr.wizard_line [module: equip3_inventory_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Describe the columns of purchase_request_warning_line. or List all columns in purchase_request_warning_line.

Response: Columns in purchase_request_warning_line: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_request_warning_line_id_seq'::regclass)] [PRECISION: 32]; warning_id (integer) [PRECISION: 32] [COMMENT: Warning]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; purchase_req_budget (double precision) [PRECISION: 53] [COMMENT: Purchase Budget]; realized_amount (double precision) [PRECISION: 53] [COMMENT: Realized Budget]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


What is the res_currency_rate table? or How many columns are in res_currency_rate?

Response: The res_currency_rate table has 11 columns and 4 foreign key relationships. It stores data related to res currency rate in the system. The table has 5 indexes for performance optimization. Column types: integer: 5, date: 1, numeric: 2, timestamp without time zone: 2, double precision: 1. Nullable columns: 8, columns with defaults: 1.


What models are connected to inter.transfer.company.line? or What foreign keys exist in inter.transfer.company.line?

Response: The inter.transfer.company.line model has 4 relational fields: internal_id -> inter.transfer.company; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What are the technical details of pos.loyalty.rule? or Which fields are stored computed fields in pos.loyalty.rule?

Response: The pos.loyalty.rule model is defined in module: equip3_pos_membership. It has 4 computed fields: categories, coefficient_note, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: create, write, _get_coefficient_note, onchange_type, _compute_categories.


How many columns are in res_company_setu_inventory_turnover_analysis_report_rel? or Tell me about the res_company_setu_inventory_turnover_analysis_report_rel table.

Response: The res_company_setu_inventory_turnover_analysis_report_rel table has 2 columns and 2 foreign key relationships. It stores data related to res company setu inventory turnover analysis report rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


How to create records in ai.model.selection.wizard? or What operations can I perform on ai.model.selection.wizard?

Response: To use the ai.model.selection.wizard model, you need to provide values for required fields: config_id, selected_model. Readonly fields: provider, available_models_text, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: config_id [required]; provider [readonly] [computed] [no_copy]; available_models_text [readonly] [computed] [no_copy]; selected_model [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Show me the fields of theme.utils. or What data can be stored in theme.utils?

Response: The theme.utils model has 3 fields. Field types distribution: integer: 1, char: 1, datetime: 1. Computed fields: 2. Field details: id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


What are the length constraints in product_optional_rel? or What data types are used in product_optional_rel?

Response: Columns in product_optional_rel: src_id (integer) [NOT NULL] [PRECISION: 32]; dest_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


What tables does module_advanced_upgrade reference? or What relationships exist for module_advanced_upgrade?

Response: Foreign keys in module_advanced_upgrade: create_uid -> res_users.id [constraint: module_advanced_upgrade_create_uid_fkey]; module_id -> ir_module_module.id [constraint: module_advanced_upgrade_module_id_fkey]; parent_id -> module_advanced_upgrade.id [constraint: module_advanced_upgrade_parent_id_fkey]; write_uid -> res_users.id [constraint: module_advanced_upgrade_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: module_advanced_upgrade, res_users, ir_module_module.


What data can be stored in asset.cip.line? or Which fields are required in asset.cip.line?

Response: The asset.cip.line model has 15 fields. Field types distribution: many2one: 6, char: 2, float: 1, boolean: 2, integer: 1, datetime: 3. Computed fields: 3. Field details: product_id (many2one) -> product.template [module: equip3_accounting_asset]; label (char) [required] [module: equip3_accounting_asset]; account_id (many2one) -> account.account [module: equip3_accounting_asset]; amount (float) [module: equip3_accounting_asset]; cip_id (many2one) -> asset.cip [module: equip3_accounting_asset]; move_id (many2one) -> account.move [module: equip3_accounting_asset]; move_check (boolean) [module: equip3_accounting_asset]; move_posted_check (boolean) [readonly] [compute: _get_move_posted_check] [stored] [module: equip3_accounting_asset]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


List all constraint names in coupon_program_product_product_sale. or What are the foreign keys in coupon_program_product_product_sale?

Response: Foreign keys in coupon_program_product_product_sale: coupon_program_id -> coupon_program.id [constraint: coupon_program_product_product_sale_coupon_program_id_fkey]; product_product_id -> product_product.id [constraint: coupon_program_product_product_sale_product_product_id_fkey]. Total foreign key relationships: 2. Referenced tables: coupon_program, product_product.


Which fields are required in whatsapp.scan.qr? or What data can be stored in whatsapp.scan.qr?

Response: The whatsapp.scan.qr model has 8 fields. Field types distribution: binary: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: qr_code_img_data (binary) [readonly] [module: pragmatic_odoo_delivery_boy]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Which columns are nullable in approval_matrix_purchase_order_line_res_users_rel? or What are the column types in approval_matrix_purchase_order_line_res_users_rel?

Response: Columns in approval_matrix_purchase_order_line_res_users_rel: approval_matrix_purchase_order_line_id (integer) [NOT NULL] [PRECISION: 32]; res_users_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


What fields are available in account_fiscal_year? or Describe the columns of account_fiscal_year.

Response: Columns in account_fiscal_year: id (integer) [NOT NULL] [DEFAULT: nextval('account_fiscal_year_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; date_from (date) [NOT NULL] [COMMENT: Start Date]; date_to (date) [NOT NULL] [COMMENT: End Date]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


What are the column types in product_category_sh_sale_category_wizard_rel? or List all columns in product_category_sh_sale_category_wizard_rel.

Response: Columns in product_category_sh_sale_category_wizard_rel: sh_sale_category_wizard_id (integer) [NOT NULL] [PRECISION: 32]; product_category_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.


What data can be stored in login.as? or What are the available fields for login.as?

Response: The login.as model has 12 fields. Field types distribution: many2one: 5, many2many: 2, integer: 1, char: 1, datetime: 3. Computed fields: 5. Field details: group_id (many2one) -> res.groups [module: oi_login_as]; user_id (many2one) [required] -> res.users [module: oi_login_as]; group_ids (many2many) [readonly] -> res.groups [compute: _calc_group_ids] [not stored] [module: oi_login_as]; company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of login.as.company_id>] [not stored] [module: oi_login_as] [related: user_id.company_id]; company_ids (many2many) [readonly] -> res.company [compute: <bound method Field._compute_related of login.as.company_ids>] [not stored] [module: oi_login_as] [related: user_id.company_ids]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Which fields are stored computed fields in product.packaging? or How is product.packaging implemented technically?

Response: The product.packaging model is defined in module: product. It has 6 computed fields: product_uom_id, weight_uom_name, length_uom_name, maximum_volume, display_name, __last_update. Stored computed fields: none. Related fields: product_uom_id -> product_id.uom_id. Original module methods: .


What columns does gamification_karma_rank have? or What is stored in gamification_karma_rank?

Response: The gamification_karma_rank table has 9 columns and 2 foreign key relationships. It stores data related to gamification karma rank in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, text: 3, timestamp without time zone: 2. Nullable columns: 6, columns with defaults: 1.


How to query report.sh_purchase_reports.rpt_purchase_order_day_wise data? or How do I use the report.sh_purchase_reports.rpt_purchase_order_day_wise model?

Response: To use the report.sh_purchase_reports.rpt_purchase_order_day_wise model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


List all relational fields in sh.purchase.report.representative.wizard. or What are the relationships in sh.purchase.report.representative.wizard?

Response: The sh.purchase.report.representative.wizard model has 5 relational fields: user_ids -> res.users; company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, company_ids, branch_ids. One2many fields: none.


List all columns in account_tax_report. or What data types are used in account_tax_report?

Response: Columns in account_tax_report: id (integer) [NOT NULL] [DEFAULT: nextval('account_tax_report_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; country_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Country]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; branch_id (integer) [PRECISION: 32] [COMMENT: Branch]. Total columns: 9. Statistics: 5 nullable, 1 with defaults, 0 with length constraints.


What is the module hierarchy for update.customer.segment? or What are the technical details of update.customer.segment?

Response: The update.customer.segment model is defined in module: setu_rfm_analysis. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _default_end_date, _get_default_note, update_customer_segment.


What are the relationships in sale.order.alternative.product? or Describe the many2many relations for sale.order.alternative.product.

Response: The sale.order.alternative.product model has 6 relational fields: alter_product_ids -> product.product; product_id -> product.product; sale_line_id -> sale.order.line; selected_product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: alter_product_ids. One2many fields: none.


What tables are connected to purchase_change_request_line? or List all constraint names in purchase_change_request_line.

Response: Foreign keys in purchase_change_request_line: create_uid -> res_users.id [constraint: purchase_change_request_line_create_uid_fkey]; product_id -> product_product.id [constraint: purchase_change_request_line_product_id_fkey]; purchase_chn_req_id -> purchase_change_request.id [constraint: purchase_change_request_line_purchase_chn_req_id_fkey]; write_uid -> res_users.id [constraint: purchase_change_request_line_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: product_product, res_users, purchase_change_request.