What fields does account.asset.asset have? or Show me the fields of account.asset.asset.

Response: The account.asset.asset model has 86 fields. Field types distribution: integer: 14, char: 6, float: 5, many2one: 17, text: 1, date: 4, boolean: 14, selection: 12, one2many: 7, many2many: 3, datetime: 3. Computed fields: 28. Field details: entry_count (integer) [readonly] [compute: _entry_count] [not stored] [module: om_account_asset]; name (char) [required] [readonly] [module: om_account_asset]; code (char) [readonly] [module: om_account_asset]; value (float) [required] [readonly] [module: om_account_asset]; currency_id (many2one) [required] [readonly] -> res.currency [module: om_account_asset]; note (text) [module: om_account_asset]; category_id (many2one) [required] [readonly] -> account.asset.category [module: om_account_asset]; date (date) [required] [readonly] [module: om_account_asset]; active (boolean) [module: om_account_asset]; partner_id (many2one) [readonly] -> res.partner [module: om_account_asset]; method_number (integer) [readonly] [module: om_account_asset]; method_period (integer) [required] [readonly] [module: om_account_asset]; method_end (date) [readonly] [module: om_account_asset]; method_progress_factor (float) [readonly] [module: om_account_asset]; value_residual (float) [readonly] [compute: _amount_residual] [not stored] [module: om_account_asset]; method_time (selection) [required] [readonly] [module: om_account_asset]; prorata (boolean) [readonly] [module: om_account_asset]; depreciation_line_ids (one2many) [readonly] -> account.asset.depreciation.line [module: om_account_asset]; salvage_value (float) [readonly] [module: om_account_asset]; invoice_id (many2one) -> account.move [module: om_account_asset]; type (selection) [required] [readonly] [compute: <bound method Field._compute_related of account.asset.asset.type>] [not stored] [module: om_account_asset] [related: category_id.type]; account_analytic_id (many2one) -> account.analytic.account [module: om_account_asset]; analytic_tag_ids (many2many) -> account.analytic.tag [module: om_account_asset]; first_depreciation_manual_date (date) [readonly] [module: om_account_asset]; user_id (many2one) -> res.users [module: equip3_accounting_operation]; is_monthly_depreciation (boolean) [module: equip3_accounting_asset]; is_reset_january (boolean) [module: equip3_accounting_asset]; months_remaining (integer) [readonly] [compute: _compute_months_remaining] [not stored] [module: equip3_accounting_asset]; method (selection) [required] [readonly] [module: equip3_accounting_asset]; cut_off_asset_date (integer) [module: equip3_accounting_asset]; date_first_depreciation (selection) [readonly] [module: equip3_accounting_asset]; fiscal_category_id (many2one) [readonly] -> account.asset.category.fiscal [module: equip3_accounting_asset]; method_fiscal (selection) [required] [readonly] [module: equip3_accounting_asset]; asset_type (selection) [module: equip3_accounting_asset]; asset_type_1 (selection) [module: equip3_accounting_asset]; sub_asset_type (selection) [module: equip3_accounting_asset]; non_building_type (selection) [module: equip3_accounting_asset]; is_monthly_depreciation_fiscal (boolean) [module: equip3_accounting_asset]; is_reset_january_fiscal (boolean) [module: equip3_accounting_asset]; months_remaining_fiscal (integer) [readonly] [compute: _compute_months_remaining_fiscal] [not stored] [module: equip3_accounting_asset]; method_number_fiscal (integer) [readonly] [module: equip3_accounting_asset]; method_period_fiscal (integer) [required] [readonly] [module: equip3_accounting_asset]; method_end_fiscal (date) [readonly] [module: equip3_accounting_asset]; depreciation_line_ids_fiscal (one2many) [readonly] -> account.asset.fiscal.line [module: equip3_accounting_asset]; asset_history_lines_ids (one2many) -> asset.asset.revalue [module: equip3_accounting_asset]; asset_value_residual (float) [readonly] [compute: _amount_residual] [not stored] [module: equip3_accounting_asset]; account_cip_id (many2one) -> asset.cip [module: equip3_accounting_asset]; state (selection) [required] [module: equip3_accounting_asset]; state1 (selection) [readonly] [compute: <bound method Field._compute_related of account.asset.asset.state1>] [not stored] [module: equip3_accounting_asset] [related: state]; state2 (selection) [readonly] [compute: <bound method Field._compute_related of account.asset.asset.state2>] [not stored] [module: equip3_accounting_asset] [related: state]; approval_matrix_id (many2one) [readonly] -> assets.approval.matrix [compute: _compute_approval_matrix_id] [stored] [module: equip3_accounting_asset]; approved_matrix_ids (one2many) [readonly] -> assets.approval.matrix.line [compute: _compute_approving_matrix_lines] [stored] [module: equip3_accounting_asset]; is_approval_matrix (boolean) [readonly] [compute: _compute_approval_matrix] [not stored] [module: equip3_accounting_asset]; is_approve_button (boolean) [readonly] [compute: _get_approve_button] [not stored] [module: equip3_accounting_asset]; approval_matrix_line_id (many2one) [readonly] -> assets.approval.matrix.line [compute: _get_approve_button] [not stored] [module: equip3_accounting_asset]; request_partner_id (many2one) -> res.partner [module: equip3_accounting_asset]; company_id (many2one) [required] [readonly] -> res.company [module: equip3_accounting_asset]; branch_id (many2one) [required] -> res.branch [compute: <bound method Field._compute_related of account.asset.asset.branch_id>] [not stored] [module: equip3_accounting_asset] [related: user_id.branch_id] [inverse: <bound method Field._inverse_related of account.asset.asset.branch_id>]; asset_sequence (char) [module: equip3_accounting_asset]; product_id (many2one) -> product.product [module: equip3_accounting_asset]; fiscal_prorata_temporis (boolean) [module: equip3_accounting_asset]; location (char) [module: equip3_accounting_asset]; po_ref (char) [module: equip3_accounting_asset]; asset_post_entries_count (integer) [readonly] [compute: _compute_asset_post_entries_count] [not stored] [module: equip3_accounting_asset]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; 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].


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

Response: Columns in approval_matrix_purchase_order: id (integer) [NOT NULL] [DEFAULT: nextval('approval_matrix_purchase_order_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.


Explain the invoice_template_footer table schema. or What columns does invoice_template_footer have?

Response: The invoice_template_footer table has 8 columns and 4 foreign key relationships. It stores data related to invoice template footer in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, timestamp without time zone: 2. Nullable columns: 6, columns with defaults: 1.


Which fields in acrux.chat.base.message are computed? or What methods are available in acrux.chat.base.message?

Response: The acrux.chat.base.message model is defined in module: acrux_chat. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


What are common use cases for account.analytic.line? or How do I use the account.analytic.line model?

Response: To use the account.analytic.line model, you need to provide values for required fields: name, account_id, company_id, date, amount. Readonly fields: product_uom_category_id, currency_id, general_account_id, department_id, encoding_uom_id, timesheet_invoice_type, timesheet_invoice_id, company_id, group_id, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: product_uom_category_id [readonly] [computed] [no_copy]; currency_id [readonly] [computed] [no_copy]; general_account_id [readonly] [computed] [no_copy]; task_id [computed]; project_id [computed]; user_id [computed] [has_default]; department_id [readonly] [computed] [no_copy]; encoding_uom_id [readonly] [computed] [no_copy]; timesheet_invoice_type [readonly] [computed] [no_copy]; timesheet_invoice_id [readonly] [no_copy]; so_line [computed]; name [required]; account_id [required]; company_id [required] [readonly] [has_default]; group_id [readonly] [computed] [no_copy]; date [required] [has_default]; amount [required] [has_default]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [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.


Tell me about the setu.inventory.overstock.bi.report model. or Describe the setu.inventory.overstock.bi.report model in Odoo.

Response: The setu.inventory.overstock.bi.report model represents setu.inventory.overstock.bi.report in the ERP system. It contains 31 fields and is used to manage setu.inventory.overstock.bi.report data. Defined in module: setu_advance_inventory_reports. Key fields include: product_id, product_category_id, warehouse_id, company_id, sales, ads, qty_available, incoming, outgoing, forecasted_stock, demanded_qty, coverage_days, overstock_qty, overstock_value, wh_overstock_qty_per, wh_overstock_value_per, turnover_ratio, stock_movement, last_purchase_date, last_purchase_qty, last_purchase_price, currency_name, vendor_name, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the pos_promotion_partner_group_rel table? or What is stored in pos_promotion_partner_group_rel?

Response: The pos_promotion_partner_group_rel table has 2 columns and 2 foreign key relationships. It stores data related to pos promotion partner group rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What does the pmps.adv.wizard.product.line model represent? or Describe the pmps.adv.wizard.product.line model in Odoo.

Response: The pmps.adv.wizard.product.line model represents Purchase Multi Product Selection Advanced Wizard Product Line in the ERP system. It contains 13 fields and is used to manage purchase multi product selection advanced wizard product line data. Defined in module: sh_all_in_one_purchase_tools. Key fields include: pmps_adv_wizard_id, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Describe the field structure of pos.promotion.multilevel.gift. or What data can be stored in pos.promotion.multilevel.gift?

Response: The pos.promotion.multilevel.gift model has 11 fields. Field types distribution: boolean: 1, many2one: 4, float: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: active (boolean) [module: equip3_pos_masterdata]; product_id (many2one) [required] -> product.product [module: equip3_pos_masterdata]; quantity_free (float) [required] [module: equip3_pos_masterdata]; promotion_id (many2one) [required] -> pos.promotion [module: equip3_pos_masterdata]; 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 account_tax_map_sales_line? or List all columns in account_tax_map_sales_line.

Response: Columns in account_tax_map_sales_line: id (integer) [NOT NULL] [DEFAULT: nextval('account_tax_map_sales_line_id_seq'::regclass)] [PRECISION: 32]; sales_tax_id (integer) [PRECISION: 32] [COMMENT: Parent Sales Tax]; target_sales_tax (integer) [PRECISION: 32] [COMMENT: Child Sales Tax]; map_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Map]; 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: 8. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.


What modules define account.partial.reconcile? or What is the module hierarchy for account.partial.reconcile?

Response: The account.partial.reconcile model is defined in module: account. It has 7 computed fields: company_currency_id, debit_currency_id, credit_currency_id, company_id, max_date, display_name, __last_update. Stored computed fields: debit_currency_id, credit_currency_id, company_id, max_date. Related fields: company_currency_id -> company_id.currency_id, company_id -> debit_move_id.company_id. Original module methods: _check_required_computed_currencies, _compute_max_date, _compute_debit_currency_id, _compute_credit_currency_id, unlink, _collect_tax_cash_basis_values, _prepare_cash_basis_base_line_vals, _prepare_cash_basis_counterpart_base_line_vals, _prepare_cash_basis_tax_line_vals, _prepare_cash_basis_counterpart_tax_line_vals, _get_cash_basis_base_line_grouping_key_from_vals, _get_cash_basis_base_line_grouping_key_from_record, _get_cash_basis_tax_line_grouping_key_from_vals, _get_cash_basis_tax_line_grouping_key_from_record, _fix_cash_basis_full_balance_coverage, _create_tax_cash_basis_moves.


List all columns in mail_compose_message_ir_attachments_rel. or Show me the column structure of mail_compose_message_ir_attachments_rel.

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


What are common use cases for budget.purchase.lines? or What operations can I perform on budget.purchase.lines?

Response: To use the budget.purchase.lines model, you need to provide values for required fields: purchase_budget_id, date_from, date_to, planned_amount. Readonly fields: name, analytic_group_id, currency_id, practical_amount, remaining_amount, theoritical_amount, percentage, company_id, is_above_budget, purchase_budget_state, account_tag_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [readonly] [computed] [no_copy]; purchase_budget_id [required]; analytic_group_id [readonly] [computed] [no_copy]; date_from [required]; date_to [required]; currency_id [readonly] [computed] [no_copy]; planned_amount [required]; practical_amount [readonly] [computed] [no_copy]; remaining_amount [readonly] [computed] [no_copy]; theoritical_amount [readonly] [computed] [no_copy]; percentage [readonly] [computed] [no_copy]; company_id [readonly] [computed] [no_copy]; is_above_budget [readonly] [computed] [no_copy]; purchase_budget_state [readonly] [computed] [no_copy]; account_tag_ids [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 is the module hierarchy for report.reordering? or Which fields are stored computed fields in report.reordering?

Response: The report.reordering model is defined in module: allfresh_mod_report_reordering. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: onchange_warehouse_id, get_report_data, download_report_ordering_in_listview, create_data, download_report_xlsx.


Show me the column structure of stock_quant_queue. or Describe the columns of stock_quant_queue.

Response: Columns in stock_quant_queue: id (integer) [NOT NULL] [DEFAULT: nextval('stock_quant_queue_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [PRECISION: 32] [COMMENT: Product Variant]; quant_id (integer) [PRECISION: 32] [COMMENT: Quant ID]; datas (text) [COMMENT: Datas]; 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: 8. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


How to query budget.purchase.wizard data? or How do I use the budget.purchase.wizard model?

Response: To use the budget.purchase.wizard 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 relational structure of report_layout. or What relationships exist for report_layout?

Response: Foreign keys in report_layout: create_uid -> res_users.id [constraint: report_layout_create_uid_fkey]; view_id -> ir_ui_view.id [constraint: report_layout_view_id_fkey]; write_uid -> res_users.id [constraint: report_layout_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: ir_ui_view, res_users.


What is the module hierarchy for saleblanket.saleblanket? or Which fields in saleblanket.saleblanket are computed?

Response: The saleblanket.saleblanket model is defined in module: blanket_sale_order_app. It has 46 computed fields: sale_order_count, order_line_count, currency_id, state1, state2, state3, bo_state, bo_state_1, approving_matrix_bo_sale_id, is_bo_approval_matrix, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, approved_matrix_ids, amount_untaxed, amount_tax, amount_total, analytic_accounting, is_product_filled, max_line_sequence, report_template_id1, amount_to_text, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, display_name, __last_update. Stored computed fields: order_line_count, currency_id, approving_matrix_bo_sale_id, approved_matrix_ids, amount_untaxed, amount_tax, amount_total, analytic_accounting. Related fields: currency_id -> company_id.currency_id, state1 -> state, state2 -> state, state3 -> state, bo_state -> state, bo_state_1 -> state, activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: _sale_order_count, create, open_button, open_sale_order, onchange_partner_id, action_view_sale_order, button_cancel, to_draft, unlink.


How does cancel.tender.memory relate to other models? or What foreign keys exist in cancel.tender.memory?

Response: The cancel.tender.memory model has 3 relational fields: tender_id -> purchase.agreement; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How is queue.job.dashboard used in the system? or What is the queue.job.dashboard model?

Response: The queue.job.dashboard model represents Queue Job Dashboard in the ERP system. It contains 3 fields and is used to manage queue job dashboard data. Defined in module: queue_job. Key fields include: id, display_name, __last_update.


What field types are used in kpi.item? or Which fields are required in kpi.item?

Response: The kpi.item model has 36 fields. Field types distribution: char: 6, many2one: 6, one2many: 2, selection: 3, many2many: 10, boolean: 2, text: 1, integer: 2, html: 1, datetime: 3. Computed fields: 10. Field details: name (char) [required] [module: kpi_scorecard]; category_id (many2one) [required] -> kpi.category [module: kpi_scorecard]; formula (char) [module: kpi_scorecard]; formula_warning (char) [readonly] [compute: <function kpi_item._compute_measures_ids at 0x2f19951f0>] [not stored] [module: kpi_scorecard]; line_ids (one2many) -> kpi.scorecard.line [module: kpi_scorecard]; result_type (selection) [required] [module: kpi_scorecard]; result_appearance (selection) [required] [module: kpi_scorecard]; result_suffix (char) [module: kpi_scorecard]; result_preffix (char) [module: kpi_scorecard]; currency_id (many2one) -> res.currency [module: kpi_scorecard]; result_rounding (selection) [module: kpi_scorecard]; parent_id (many2one) -> kpi.item [module: kpi_scorecard]; all_parent_ids (many2many) [readonly] -> kpi.item [compute: <function kpi_item._compute_all_parent_ids at 0x2f1995280>] [stored] [module: kpi_scorecard]; child_ids (one2many) -> kpi.item [module: kpi_scorecard]; measures_ids (many2many) [readonly] -> kpi.measure.item [compute: <function kpi_item._compute_measures_ids at 0x2f19951f0>] [not stored] [module: kpi_scorecard]; constant_ids (many2many) [readonly] -> kpi.constant [compute: <function kpi_item._compute_measures_ids at 0x2f19951f0>] [not stored] [module: kpi_scorecard]; kpi_ids (many2many) [readonly] -> kpi.item [compute: <function kpi_item._compute_measures_ids at 0x2f19951f0>] [not stored] [module: kpi_scorecard]; company_id (many2one) -> res.company [module: kpi_scorecard]; active (boolean) [module: kpi_scorecard]; description (text) [module: kpi_scorecard]; sequence (integer) [module: kpi_scorecard]; user_ids (many2many) -> res.users [module: kpi_scorecard]; user_group_ids (many2many) -> res.groups [module: kpi_scorecard]; access_user_ids (many2many) [readonly] -> res.users [compute: <function kpi_item._compute_access_user_ids at 0x2f1995310>] [stored] [module: kpi_scorecard]; edit_user_ids (many2many) -> res.users [module: kpi_scorecard]; edit_user_group_ids (many2many) -> res.groups [module: kpi_scorecard]; edit_access_user_ids (many2many) [readonly] -> res.users [compute: <function kpi_item._compute_edit_access_user_ids at 0x2f19953a0>] [stored] [module: kpi_scorecard]; help_notes (html) [readonly] [compute: <function kpi_help._compute_show_kpi_help at 0x2f195ae50>] [not stored] [module: kpi_scorecard]; kpi_help_dummy (boolean) [module: kpi_scorecard]; 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].


What is the module hierarchy for approval.matrix.purchase.order? or Describe the implementation of approval.matrix.purchase.order.

Response: The approval.matrix.purchase.order model is defined in module: equip3_purchase_operation. It has 25 computed fields: is_good_services_order, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, display_name, __last_update. Stored computed fields: none. Related fields: activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: default_branch, _check_validation_minimum_approver, _compute_is_good_services_order, _check_existing_record, _reset_sequence, onchange_company_id.


What fields are readonly in ir.qweb.field.qweb? or How do I use the ir.qweb.field.qweb model?

Response: To use the ir.qweb.field.qweb 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.


How to query ir.actions.act_window data? or How to create records in ir.actions.act_window?

Response: To use the ir.actions.act_window model, you need to provide values for required fields: name, type, context, res_model, view_mode, binding_type. Readonly fields: views, search_view, xml_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; type [required] [has_default]; context [required] [has_default]; res_model [required]; view_mode [required] [has_default]; views [readonly] [computed] [no_copy]; search_view [readonly] [computed] [no_copy]; xml_id [readonly] [computed] [no_copy]; binding_type [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 field types are used in setu.rfm.score? or List all fields in the setu.rfm.score model.

Response: The setu.rfm.score model has 15 fields. Field types distribution: char: 2, many2one: 3, selection: 3, text: 1, one2many: 1, integer: 2, datetime: 3. Computed fields: 3. Field details: name (char) [module: setu_rfm_analysis]; rfm_segment_id (many2one) -> setu.rfm.segment [module: setu_rfm_analysis]; recency (selection) [module: setu_rfm_analysis]; frequency (selection) [module: setu_rfm_analysis]; monetization (selection) [module: setu_rfm_analysis]; description (text) [module: setu_rfm_analysis]; partner_ids (one2many) -> res.partner [module: setu_rfm_analysis]; total_customers (integer) [readonly] [compute: _compute_customers] [not stored] [module: setu_rfm_analysis]; 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].


What relationships exist for limit_approval_matrix? or How does limit_approval_matrix relate to other tables?

Response: Foreign keys in limit_approval_matrix: branch_id -> res_branch.id [constraint: limit_approval_matrix_branch_id_fkey]; campaign_id -> utm_campaign.id [constraint: limit_approval_matrix_campaign_id_fkey]; company_id -> res_company.id [constraint: limit_approval_matrix_company_id_fkey]; create_uid -> res_users.id [constraint: limit_approval_matrix_create_uid_fkey]; medium_id -> utm_medium.id [constraint: limit_approval_matrix_medium_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: limit_approval_matrix_message_main_attachment_id_fkey]; source_id -> utm_source.id [constraint: limit_approval_matrix_source_id_fkey]; write_uid -> res_users.id [constraint: limit_approval_matrix_write_uid_fkey]. Total foreign key relationships: 8. Referenced tables: utm_source, utm_medium, res_company, ir_attachment, res_users, res_branch, utm_campaign.


Describe the relational structure of sales_order_commission. or What relationships exist for sales_order_commission?

Response: Foreign keys in sales_order_commission: create_uid -> res_users.id [constraint: sales_order_commission_create_uid_fkey]; invoice_id -> account_move.id [constraint: sales_order_commission_invoice_id_fkey]; job_id -> hr_job.id [constraint: sales_order_commission_job_id_fkey]; order_id -> sale_order.id [constraint: sales_order_commission_order_id_fkey]; user_id -> res_users.id [constraint: sales_order_commission_user_id_fkey]; write_uid -> res_users.id [constraint: sales_order_commission_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: hr_job, sale_order, res_users, account_move.


Which fields are required in account.tour.upload.bill.email.confirm? or What data can be stored in account.tour.upload.bill.email.confirm?

Response: The account.tour.upload.bill.email.confirm model has 8 fields. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: email_alias (char) [readonly] [module: account]; 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 field structure of mail.compose.message. or Which fields are required in mail.compose.message?

Response: The mail.compose.message model has 38 fields. Field types distribution: char: 8, html: 1, many2one: 10, many2many: 3, boolean: 8, selection: 2, integer: 2, text: 1, datetime: 3. Computed fields: 2. Field details: subject (char) [module: mail]; body (html) [module: mail]; parent_id (many2one) -> mail.message [module: mail]; template_id (many2one) -> mail.template [module: mail]; attachment_ids (many2many) -> ir.attachment [module: mail]; layout (char) [module: mail]; add_sign (boolean) [module: mail]; email_from (char) [module: mail]; author_id (many2one) -> res.partner [module: mail]; composition_mode (selection) [module: mail]; model (char) [module: mail]; res_id (integer) [module: mail]; record_name (char) [module: mail]; use_active_domain (boolean) [module: mail]; active_domain (text) [readonly] [module: mail]; message_type (selection) [required] [module: mail]; subtype_id (many2one) -> mail.message.subtype [module: mail]; mail_activity_type_id (many2one) -> mail.activity.type [module: mail]; reply_to (char) [module: mail]; no_auto_thread (boolean) [module: mail]; is_log (boolean) [module: mail]; partner_ids (many2many) -> res.partner [module: mail]; notify (boolean) [module: mail]; auto_delete (boolean) [module: mail]; auto_delete_message (boolean) [module: mail]; mail_server_id (many2one) -> ir.mail_server [module: mail]; mass_mailing_id (many2one) -> mailing.mailing [module: mass_mailing]; campaign_id (many2one) -> utm.campaign [module: mass_mailing]; mass_mailing_name (char) [module: mass_mailing]; mailing_list_ids (many2many) -> mailing.list [module: mass_mailing]; is_wp (boolean) [module: sh_all_in_one_purchase_tools]; 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].


How do I use the mailing.trace.report model? or What business logic is in mailing.trace.report?

Response: To use the mailing.trace.report model, you need to provide values for required fields: mailing_type. Readonly fields: name, campaign, scheduled_date, state, email_from, sent, delivered, opened, replied, clicked, bounced, id, display_name, __last_update. Field usage details: name [readonly]; mailing_type [required] [has_default]; campaign [readonly]; scheduled_date [readonly]; state [readonly] [no_copy]; email_from [readonly]; sent [readonly]; delivered [readonly]; opened [readonly]; replied [readonly]; clicked [readonly]; bounced [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Describe the res_user_order_point_rel table structure. or What columns does res_user_order_point_rel have?

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


List all fields in the assets.approval.reject model. or Describe the field structure of assets.approval.reject.

Response: The assets.approval.reject model has 8 fields. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: reason (text) [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].


What methods are available in account.incoterms? or Which fields in account.incoterms are computed?

Response: The account.incoterms model is defined in module: account. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


Can you explain the purpose of pos.coupon.apply.code? or Describe the pos.coupon.apply.code model in Odoo.

Response: The pos.coupon.apply.code model represents POS Coupon Apply Code in the ERP system. It contains 8 fields and is used to manage pos coupon apply code data. Defined in module: equip3_pos_general. Key fields include: coupon_code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How does account_tax_report_line relate to other tables? or List all constraint names in account_tax_report_line.

Response: Foreign keys in account_tax_report_line: create_uid -> res_users.id [constraint: account_tax_report_line_create_uid_fkey]; parent_id -> account_tax_report_line.id [constraint: account_tax_report_line_parent_id_fkey]; report_action_id -> ir_act_window.id [constraint: account_tax_report_line_report_action_id_fkey]; report_id -> account_tax_report.id [constraint: account_tax_report_line_report_id_fkey]; write_uid -> res_users.id [constraint: account_tax_report_line_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: account_tax_report_line, res_users, ir_act_window, account_tax_report.


What is stored in approval_matrix_accounting? or How many columns are in approval_matrix_accounting?

Response: The approval_matrix_accounting table has 17 columns and 8 foreign key relationships. It stores data related to approval matrix accounting in the system. The table has 2 indexes for performance optimization. Column types: integer: 9, character varying: 3, double precision: 3, timestamp without time zone: 2. Nullable columns: 14, columns with defaults: 1.


What is the mail.notification model? or Describe the mail.notification model in Odoo.

Response: The mail.notification model represents Message Notifications in the ERP system. It contains 15 fields and is used to manage message notifications data. Defined in module: mail. Key fields include: mail_message_id, mail_id, res_partner_id, notification_status, is_read, read_date, failure_reason, sms_id, sms_number, notification_type, letter_id, failure_type, id, display_name, __last_update.


What are the length constraints in access_management_comapnay_rel? or Which columns are nullable in access_management_comapnay_rel?

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


Show me the fields of base_import.tests.models.m2o. or What are the available fields for base_import.tests.models.m2o?

Response: The base_import.tests.models.m2o model has 8 fields. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: value (many2one) -> base_import.tests.models.m2o.related [module: base_import]; 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].


Show me the column structure of crm_salesperson_tracking_history. or What columns have default values in crm_salesperson_tracking_history?

Response: Columns in crm_salesperson_tracking_history: id (integer) [NOT NULL] [DEFAULT: nextval('crm_salesperson_tracking_history_id_seq'::regclass)] [PRECISION: 32]; sales_person_name (character varying) [COMMENT: Salesperson]; history_date (character varying) [COMMENT: Date]; track_lan_lng (character varying) [COMMENT: Tracking Coordinates]; track_hist (text) [COMMENT: Visit History]; 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 mail.moderation model? or Describe the mail.moderation model in Odoo.

Response: The mail.moderation model represents Channel black/white list in the ERP system. It contains 10 fields and is used to manage channel black/white list data. Defined in module: mail. Key fields include: email, status, channel_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is stored in crm_convert_lead_mass_lead_rel? or What indexes exist on crm_convert_lead_mass_lead_rel?

Response: The crm_convert_lead_mass_lead_rel table has 2 columns and 2 foreign key relationships. It stores data related to crm convert lead mass lead rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Explain the whatsapp_template_message table schema. or How many columns are in whatsapp_template_message?

Response: The whatsapp_template_message table has 9 columns and 4 foreign key relationships. It stores data related to whatsapp template message in the system. The table has 2 indexes for performance optimization. Column types: integer: 5, character varying: 1, text: 1, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.


What operations can I perform on queue.job.function? or What are common use cases for queue.job.function?

Response: To use the queue.job.function model, you need to provide values for required fields: channel_id. Readonly fields: channel, id, display_name, __last_update. Field usage details: name [computed] [no_copy]; channel_id [required] [has_default]; channel [readonly] [computed] [no_copy]; edit_retry_pattern [computed] [no_copy]; edit_related_action [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What computed fields exist in receipt.voucher? or What are the available fields for receipt.voucher?

Response: The receipt.voucher model has 53 fields. Field types distribution: many2one: 11, datetime: 3, integer: 6, one2many: 6, char: 6, many2many: 5, date: 5, text: 1, selection: 3, monetary: 1, boolean: 6. Computed fields: 26. Field details: create_by (many2one) -> res.users [module: equip3_accounting_operation]; create_date (datetime) [module: equip3_accounting_operation]; payment_count (integer) [readonly] [compute: _get_payment_count] [not stored] [module: equip3_accounting_operation]; payment_ids (one2many) -> account.payment [module: equip3_accounting_operation]; name (char) [required] [readonly] [module: equip3_accounting_operation]; partner_id (many2one) -> res.partner [module: equip3_accounting_operation]; partner_ids (many2many) [required] -> res.partner [module: equip3_accounting_operation]; voucher_date (date) [required] [module: equip3_accounting_operation]; bank_id (many2one) [required] -> account.journal [module: equip3_accounting_operation]; cheque_number (char) [module: equip3_accounting_operation]; cheque_date (date) [module: equip3_accounting_operation]; customer_invoice_ids (many2many) [required] -> account.move [module: equip3_accounting_operation]; currency_id (many2one) [required] -> res.currency [module: equip3_accounting_operation]; remarks (text) [module: equip3_accounting_operation]; company_id (many2one) [required] -> res.company [module: equip3_accounting_operation]; branch_id (many2one) [required] -> res.branch [module: equip3_accounting_operation]; state (selection) [readonly] [module: equip3_accounting_operation]; amount (monetary) [readonly] [compute: _compute_amount] [not stored] [module: equip3_accounting_operation]; receipt_voucher_line_ids (one2many) -> receipt.voucher.line [module: equip3_accounting_operation]; invoice_cutoff_date (date) [module: equip3_accounting_operation]; customer_allowed_ids (many2many) [readonly] -> account.move [compute: _compute_customer_allowed_ids] [not stored] [module: equip3_accounting_operation]; is_cutoff_date (boolean) [readonly] [compute: _get_cut_off_date_config] [not stored] [module: equip3_accounting_operation]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of receipt.voucher.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of receipt.voucher.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of receipt.voucher.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of receipt.voucher.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of receipt.voucher.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of receipt.voucher.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of receipt.voucher.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; 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]; 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].


How does pos.order.log relate to other models? or List all relational fields in pos.order.log.

Response: The pos.order.log model has 18 relational fields: config_id -> pos.config; session_id -> pos.session; branch_id -> res.branch; company_id -> res.company; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids. One2many fields: activity_ids, message_follower_ids, message_ids, website_message_ids.


Can you explain the purpose of export.product.csv? or How is export.product.csv used in the system?

Response: The export.product.csv model represents export.product.csv in the ERP system. It contains 40 fields and is used to manage export.product.csv data. Defined in module: equip3_accounting_efaktur. Key fields include: name, product_id_attachment_id, product_id_csv_created, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How do I use the account.tax.report.wizard model? or What business logic is in account.tax.report.wizard?

Response: To use the account.tax.report.wizard model, you need to provide values for required fields: journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: journal_ids [required] [has_default]; target_move [required] [has_default]; company_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.


List all columns in ks_report_actions. or Which columns are nullable in ks_report_actions?

Response: Columns in ks_report_actions: id (integer) [NOT NULL] [DEFAULT: nextval('ks_report_actions_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; help (text) [COMMENT: Action Description]; binding_model_id (integer) [PRECISION: 32] [COMMENT: Binding Model]; binding_type (character varying) [NOT NULL] [COMMENT: Binding Type]; binding_view_types (character varying) [COMMENT: Binding View Types]; type (character varying) [NOT NULL] [COMMENT: Action 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: 11. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


How does res.country.city relate to other models? or Show me the relational structure of res.country.city.

Response: The res.country.city model has 12 relational fields: state_id -> res.country.state; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids. One2many fields: activity_ids, message_follower_ids, message_ids, website_message_ids.


What fields are readonly in stock.assign.serial? or What operations can I perform on stock.assign.serial?

Response: To use the stock.assign.serial model, you need to provide values for required fields: product_id, move_id. Readonly fields: product_id, picking_type_code, serial_no, next_serial_number, is_serial_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: product_id [required] [readonly] [computed] [no_copy]; move_id [required]; picking_type_code [readonly] [computed] [no_copy]; serial_no [readonly] [computed] [no_copy]; next_serial_number [readonly] [computed] [no_copy]; is_serial_number [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.


Which fields are required in dynamic.balance.sheet.report? or What fields does dynamic.balance.sheet.report have?

Response: The dynamic.balance.sheet.report model has 17 fields. Field types distribution: many2one: 3, many2many: 5, selection: 2, date: 2, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: company_id (many2one) [required] -> res.company [module: dynamic_accounts_report]; journal_ids (many2many) [required] -> account.journal [module: dynamic_accounts_report]; account_ids (many2many) -> account.account [module: dynamic_accounts_report]; account_tag_ids (many2many) -> account.account.tag [module: dynamic_accounts_report]; analytic_ids (many2many) -> account.analytic.account [module: dynamic_accounts_report]; analytic_tag_ids (many2many) -> account.analytic.tag [module: dynamic_accounts_report]; display_account (selection) [required] [module: dynamic_accounts_report]; target_move (selection) [required] [module: dynamic_accounts_report]; date_from (date) [module: dynamic_accounts_report]; date_to (date) [module: dynamic_accounts_report]; 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 report_layout? or What are the length constraints in report_layout?

Response: Columns in report_layout: id (integer) [NOT NULL] [DEFAULT: nextval('report_layout_id_seq'::regclass)] [PRECISION: 32]; view_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Document Template]; image (character varying) [COMMENT: Preview image src]; pdf (character varying) [COMMENT: Preview pdf src]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; name (character varying) [COMMENT: Name]; 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: 10. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


Describe the many2many relations for customer.statement. or Show me the relational structure of customer.statement.

Response: The customer.statement model has 16 relational fields: partner_ids -> res.partner; company_ids -> res.company; report_currency_id -> res.currency; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; journal_ids -> account.journal; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, company_ids, message_partner_ids, message_channel_ids, journal_ids. One2many fields: activity_ids, message_follower_ids, message_ids, website_message_ids.


How many columns are in pos_loyalty_rule? or Explain the pos_loyalty_rule table schema.

Response: The pos_loyalty_rule table has 18 columns and 3 foreign key relationships. It stores data related to pos loyalty rule in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, timestamp without time zone: 2, character varying: 4, boolean: 4, numeric: 1, double precision: 1. Nullable columns: 12, columns with defaults: 1.


What modules define account.analytic.tag? or What is the module hierarchy for account.analytic.tag?

Response: The account.analytic.tag model is defined in module: analytic. It has 22 computed fields: activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, display_name, __last_update. Stored computed fields: none. Related fields: activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: .


What is the pos_global_discount_branch_rel table? or Describe the pos_global_discount_branch_rel table structure.

Response: The pos_global_discount_branch_rel table has 2 columns and 2 foreign key relationships. It stores data related to pos global discount branch rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Which columns are nullable in pos_config_users_void_order_rel? or What fields are available in pos_config_users_void_order_rel?

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


Which fields are stored computed fields in vendor.evaluation.rating? or Which fields in vendor.evaluation.rating are computed?

Response: The vendor.evaluation.rating model is defined in module: equip3_purchase_report. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _query, init.


What are common use cases for limit.request.wizard? or What fields are readonly in limit.request.wizard?

Response: To use the limit.request.wizard 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.


What are the length constraints in mrp_bom_line? or What columns have default values in mrp_bom_line?

Response: Columns in mrp_bom_line: id (integer) [NOT NULL] [DEFAULT: nextval('mrp_bom_line_id_seq'::regclass)] [PRECISION: 32]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Component]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; product_qty (numeric) [NOT NULL] [COMMENT: Quantity]; product_uom_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product Unit of Measure]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; bom_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Parent BoM]; operation_id (integer) [PRECISION: 32] [COMMENT: Consumed in Operation]; 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]; cost (double precision) [PRECISION: 53] [COMMENT: Cost]; operation_two_id (integer) [PRECISION: 32] [COMMENT: Operation]. Total columns: 14. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.


What field types are used in setu.inventory.fsn.analysis.bi.report? or What fields does setu.inventory.fsn.analysis.bi.report have?

Response: The setu.inventory.fsn.analysis.bi.report model has 18 fields. Field types distribution: many2one: 7, float: 5, char: 2, integer: 1, datetime: 3. Computed fields: 2. Field details: product_id (many2one) -> product.product [module: setu_advance_inventory_reports]; product_category_id (many2one) -> product.category [module: setu_advance_inventory_reports]; warehouse_id (many2one) -> stock.warehouse [module: setu_advance_inventory_reports]; company_id (many2one) -> res.company [module: setu_advance_inventory_reports]; opening_stock (float) [module: setu_advance_inventory_reports]; closing_stock (float) [module: setu_advance_inventory_reports]; average_stock (float) [module: setu_advance_inventory_reports]; sales (float) [module: setu_advance_inventory_reports]; turnover_ratio (float) [module: setu_advance_inventory_reports]; stock_movement (char) [module: setu_advance_inventory_reports]; wizard_id (many2one) -> setu.inventory.fsn.analysis.report [module: setu_advance_inventory_reports]; 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].


Tell me about the uom_conversion_history table. or What is the uom_conversion_history table?

Response: The uom_conversion_history table has 15 columns and 10 foreign key relationships. It stores data related to uom conversion history in the system. The table has 1 indexes for performance optimization. Column types: integer: 11, numeric: 2, timestamp without time zone: 2. Nullable columns: 10, columns with defaults: 1.


What is the module hierarchy for pos.report.payment? or Which fields are stored computed fields in pos.report.payment?

Response: The pos.report.payment model is defined in module: equip3_pos_report. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: get_crnt_ssn_payment_pos_order.


What is stored in account_invoice_exchange_account_move_rel? or How many columns are in account_invoice_exchange_account_move_rel?

Response: The account_invoice_exchange_account_move_rel table has 2 columns and 4 foreign key relationships. It stores data related to account invoice exchange account move rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What indexes exist on res_users_log? or Explain the res_users_log table schema.

Response: The res_users_log table has 5 columns and 2 foreign key relationships. It stores data related to res users log in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, timestamp without time zone: 2. Nullable columns: 4, columns with defaults: 1.


What tables are connected to account_analytic_tag_purchase_order_rel? or Show me the foreign key constraints of account_analytic_tag_purchase_order_rel.

Response: Foreign keys in account_analytic_tag_purchase_order_rel: account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_purchase_or_account_analytic_tag_id_fkey13]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_purchase_or_account_analytic_tag_id_fkey15]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_purchase_ord_account_analytic_tag_id_fkey1]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_purchase_ord_account_analytic_tag_id_fkey3]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_purchase_ord_account_analytic_tag_id_fkey7]; account_analytic_tag_id -> account_analytic_tag.id [constraint: account_analytic_tag_purchase_ord_account_analytic_tag_id_fkey9]; purchase_order_id -> purchase_order.id [constraint: account_analytic_tag_purchase_order_rel_purchase_order_id_fkey]. Total foreign key relationships: 7. Referenced tables: purchase_order, account_analytic_tag.


How do I use the customer.target model? or How to create records in customer.target?

Response: To use the customer.target model, you need to provide values for required fields: res_name, applied_to, target_amount, start_date, end_date, reward_type, voucher_expiration. Readonly fields: name, company_id, currency_id, customer_voucher_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [readonly] [has_default] [no_copy]; res_name [required]; company_id [readonly] [has_default]; applied_to [required] [has_default]; target_amount [required]; currency_id [readonly] [computed] [no_copy]; start_date [required]; end_date [required]; reward_type [required] [has_default]; customer_voucher_count [readonly] [computed] [no_copy]; voucher_expiration [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.


What is the base.language.export model? or How is base.language.export used in the system?

Response: The base.language.export model represents Language Export in the ERP system. It contains 13 fields and is used to manage language export data. Defined in module: base. Key fields include: name, lang, format, modules, data, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all constraint names in sale_data_margin. or How does sale_data_margin relate to other tables?

Response: Foreign keys in sale_data_margin: branch_id -> res_branch.id [constraint: sale_data_margin_branch_id_fkey]; company_id -> res_company.id [constraint: sale_data_margin_company_id_fkey]; create_uid -> res_users.id [constraint: sale_data_margin_create_uid_fkey]; partner_id -> res_partner.id [constraint: sale_data_margin_partner_id_fkey]; write_uid -> res_users.id [constraint: sale_data_margin_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: res_partner, res_company, res_users, res_branch.


What is the sh_tsp_top_selling_product_wizard table? or Describe the sh_tsp_top_selling_product_wizard table structure.

Response: The sh_tsp_top_selling_product_wizard table has 14 columns and 4 foreign key relationships. It stores data related to sh tsp top selling product wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 6, character varying: 1, timestamp without time zone: 6, double precision: 1. Nullable columns: 10, columns with defaults: 1.


Describe the implementation of res.bank. or What methods are available in res.bank?

Response: The res.bank model is defined in module: base. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: name_get, _name_search, _onchange_country_id, _onchange_state, create.


List all constraint names in customer_voucher_sale_order_rel. or What relationships exist for customer_voucher_sale_order_rel?

Response: Foreign keys in customer_voucher_sale_order_rel: customer_voucher_id -> customer_voucher.id [constraint: customer_voucher_sale_order_rel_customer_voucher_id_fkey]; sale_order_id -> sale_order.id [constraint: customer_voucher_sale_order_rel_sale_order_id_fkey]. Total foreign key relationships: 2. Referenced tables: customer_voucher, sale_order.


What is the purchase_agreement_line table? or Tell me about the purchase_agreement_line table.

Response: The purchase_agreement_line table has 18 columns and 9 foreign key relationships. It stores data related to purchase agreement line in the system. The table has 1 indexes for performance optimization. Column types: integer: 12, double precision: 2, timestamp without time zone: 2, date: 1, text: 1. Nullable columns: 15, columns with defaults: 1.


What does the pos.query.log model represent? or Tell me about the pos.query.log model.

Response: The pos.query.log model represents POS Query Log in the ERP system. It contains 9 fields and is used to manage pos query log data. Defined in module: equip3_pos_masterdata. Key fields include: name, results, write_date, id, display_name, create_uid, create_date, write_uid, __last_update.


What is the gamification_challenge_users_rel table? or Describe the gamification_challenge_users_rel table structure.

Response: The gamification_challenge_users_rel table has 2 columns and 2 foreign key relationships. It stores data related to gamification challenge users rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


How does target.kpi relate to other models? or List all relational fields in target.kpi.

Response: The target.kpi model has 15 relational fields: purchase_team_id -> dev.purchase.team; user_id -> res.users; company_id -> res.company; branch_id -> res.branch; target_based_on_ids -> purchase.target.based.on; product_categories -> product.category; products -> product.product; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: target_based_on_ids, product_categories, products, message_partner_ids, message_channel_ids. One2many fields: message_follower_ids, message_ids, website_message_ids.


Which fields are required in report.equip3_accounting_reports.tax_report? or What fields does report.equip3_accounting_reports.tax_report have?

Response: The report.equip3_accounting_reports.tax_report 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 columns have default values in account_budget_post_s_curve_budget_rel? or Which columns are nullable in account_budget_post_s_curve_budget_rel?

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


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

Response: Foreign keys in sh_target_commision: brand_id -> product_brand.id [constraint: sh_target_commision_brand_id_fkey]; campaign_id -> utm_campaign.id [constraint: sh_target_commision_campaign_id_fkey]; company_id -> res_company.id [constraint: sh_target_commision_company_id_fkey]; create_uid -> res_users.id [constraint: sh_target_commision_create_uid_fkey]; medium_id -> utm_medium.id [constraint: sh_target_commision_medium_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: sh_target_commision_message_main_attachment_id_fkey]; sales_team -> crm_team.id [constraint: sh_target_commision_sales_team_fkey]; source_id -> utm_source.id [constraint: sh_target_commision_source_id_fkey]; user_id -> res_users.id [constraint: sh_target_commision_user_id_fkey]; write_uid -> res_users.id [constraint: sh_target_commision_write_uid_fkey]. Total foreign key relationships: 10. Referenced tables: utm_source, crm_team, utm_medium, res_company, ir_attachment, product_brand, res_users, utm_campaign.


How does account.pettycash.analysis relate to other models? or Show me the relational structure of account.pettycash.analysis.

Response: The account.pettycash.analysis model has 7 relational fields: journal_ids -> account.journal; account_ids -> account.account; branch_ids -> res.branch; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: journal_ids, account_ids, branch_ids. One2many fields: none.


What are the column types in account_aged_trial_balance? or What are the length constraints in account_aged_trial_balance?

Response: Columns in account_aged_trial_balance: id (integer) [NOT NULL] [DEFAULT: nextval('account_aged_trial_balance_id_seq'::regclass)] [PRECISION: 32]; period_length (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Period Length (days)]; date_from (date) [COMMENT: Start Date]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; date_to (date) [COMMENT: End Date]; target_move (character varying) [NOT NULL] [COMMENT: Target Moves]; result_selection (character varying) [NOT NULL] [COMMENT: Partner's]; 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]; report_currency_id (integer) [PRECISION: 32] [COMMENT: Report Currency]. Total columns: 12. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.


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

Response: The account_move_reversal_move table has 2 columns and 2 foreign key relationships. It stores data related to account move reversal move in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What is the res_config_settings table? or Tell me about the res_config_settings table.

Response: The res_config_settings table has 539 columns and 20 foreign key relationships. It stores data related to res config settings in the system. The table has 1 indexes for performance optimization. Column types: integer: 73, timestamp without time zone: 2, boolean: 368, character varying: 82, double precision: 8, text: 1, date: 5. Nullable columns: 535, columns with defaults: 1.


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

Response: Columns in generate_opening_entries: id (integer) [NOT NULL] [DEFAULT: nextval('generate_opening_entries_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name of new entries]; old_fiscal_year_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Fiscal Year to close]; new_fiscal_year_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: New Fiscal Year]; journal_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Opening Entries Journal]; period_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Opening Entries Period]; 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: 10. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


List all constraint names in mailing_list_mailing_list_merge_rel. or Show me the foreign key constraints of mailing_list_mailing_list_merge_rel.

Response: Foreign keys in mailing_list_mailing_list_merge_rel: mailing_list_id -> mailing_list.id [constraint: mailing_list_mailing_list_merge_rel_mailing_list_id_fkey]; mailing_list_merge_id -> mailing_list_merge.id [constraint: mailing_list_mailing_list_merge_rel_mailing_list_merge_id_fkey]. Total foreign key relationships: 2. Referenced tables: mailing_list, mailing_list_merge.


What indexes exist on account_account_account_partner_ledger_rel? or Explain the account_account_account_partner_ledger_rel table schema.

Response: The account_account_account_partner_ledger_rel table has 2 columns and 2 foreign key relationships. It stores data related to account account account partner ledger rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What foreign keys exist in base.language.import? or Describe the many2many relations for base.language.import.

Response: The base.language.import model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Which fields are required in ks_dashboard_ninja.board_template? or What data can be stored in ks_dashboard_ninja.board_template?

Response: The ks_dashboard_ninja.board_template model has 13 fields. Field types distribution: char: 3, integer: 2, selection: 1, one2many: 1, many2one: 3, datetime: 3. Computed fields: 2. Field details: name (char) [module: ks_dashboard_ninja]; ks_gridstack_config (char) [module: ks_dashboard_ninja]; ks_item_count (integer) [module: ks_dashboard_ninja]; ks_template_type (selection) [module: ks_dashboard_ninja]; ks_dashboard_item_ids (one2many) -> ks_dashboard_ninja.item [module: ks_dashboard_ninja]; ks_dashboard_board_id (many2one) -> ks_dashboard_ninja.board [module: ks_dashboard_ninja]; 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 mrp.quality.alert.report? or What is the module hierarchy for mrp.quality.alert.report?

Response: The mrp.quality.alert.report model is defined in module: sh_inventory_mrp_qc. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: print_report.


Describe the account.analytic.account model in Odoo. or What does the account.analytic.account model represent?

Response: The account.analytic.account model represents Analytic Account in the ERP system. It contains 57 fields and is used to manage analytic account data. Defined in module: analytic. Key fields include: code, active, line_ids, partner_id, balance, debit, credit, currency_id, project_ids, project_count, name, crossovered_budget_line, subscription_product_line_ids, not_subscription_product_line_ids, terms_and_conditions, start_date, end_date, recurring_interval, recurring_next_date, journal_id, invoice_count, number_of_days, contract_lock, recurring_rule_type, stage, sub_amount_untaxed, sub_amount_tax, sub_amount_total, sale_amount_untaxed, sale_amount_tax, sale_amount_total, order_invoice_currency_id, group_id, company_id, branch_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


List all constraint names in stock_warn_insufficient_qty_repair. or How does stock_warn_insufficient_qty_repair relate to other tables?

Response: Foreign keys in stock_warn_insufficient_qty_repair: create_uid -> res_users.id [constraint: stock_warn_insufficient_qty_repair_create_uid_fkey]; location_id -> stock_location.id [constraint: stock_warn_insufficient_qty_repair_location_id_fkey]; product_id -> product_product.id [constraint: stock_warn_insufficient_qty_repair_product_id_fkey]; repair_id -> repair_order.id [constraint: stock_warn_insufficient_qty_repair_repair_id_fkey]; write_uid -> res_users.id [constraint: stock_warn_insufficient_qty_repair_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: product_product, repair_order, res_users, stock_location.


What operations can I perform on product.ribbon? or How to work with product.ribbon fields?

Response: To use the product.ribbon model, you need to provide values for required fields: html, html_class. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: html [required]; html_class [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 indexes exist on pos_tag? or Explain the pos_tag table schema.

Response: The pos_tag table has 10 columns and 4 foreign key relationships. It stores data related to pos tag in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 2, boolean: 1, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.


Show me the column structure of snailmail_letter. or What are the column types in snailmail_letter?

Response: Columns in snailmail_letter: id (integer) [NOT NULL] [DEFAULT: nextval('snailmail_letter_id_seq'::regclass)] [PRECISION: 32]; user_id (integer) [PRECISION: 32] [COMMENT: Sent by]; model (character varying) [NOT NULL] [COMMENT: Model]; res_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Document ID]; partner_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Recipient]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; report_template (integer) [PRECISION: 32] [COMMENT: Optional report to print and attach]; attachment_id (integer) [PRECISION: 32] [COMMENT: Attachment]; color (boolean) [COMMENT: Color]; cover (boolean) [COMMENT: Cover Page]; duplex (boolean) [COMMENT: Both side]; state (character varying) [NOT NULL] [COMMENT: Status]; error_code (character varying) [COMMENT: Error]; info_msg (character varying) [COMMENT: Information]; message_id (integer) [PRECISION: 32] [COMMENT: Snailmail Status Message]; street (character varying) [COMMENT: Street]; street2 (character varying) [COMMENT: Street2]; zip (character varying) [COMMENT: Zip]; city (character varying) [COMMENT: City]; state_id (integer) [PRECISION: 32] [COMMENT: State]; country_id (integer) [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]. Total columns: 25. Statistics: 19 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in ai_model_selection_wizard: config_id -> ai_agent_config.id [constraint: ai_model_selection_wizard_config_id_fkey]; create_uid -> res_users.id [constraint: ai_model_selection_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: ai_model_selection_wizard_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: ai_agent_config, res_users.


Show me the relational structure of approval.matrix.sale.order.lines. or What foreign keys exist in approval.matrix.sale.order.lines?

Response: The approval.matrix.sale.order.lines model has 8 relational fields: approval_matrix -> approval.matrix.sale.order; order_id -> sale.order; user_name_ids -> res.users; last_approved -> res.users; approved_users -> res.users; bo_order_id -> saleblanket.saleblanket; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_name_ids, approved_users. One2many fields: none.


How does ai.agent.config relate to other models? or Describe the many2many relations for ai.agent.config.

Response: The ai.agent.config model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What are the relationships in report.paperformat? or What foreign keys exist in report.paperformat?

Response: The report.paperformat model has 3 relational fields: report_ids -> ir.actions.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: report_ids.


Which fields are required in pos.order.line? or What field types are used in pos.order.line?

Response: The pos.order.line model has 88 fields. Field types distribution: many2one: 24, char: 9, float: 25, many2many: 4, one2many: 2, boolean: 12, text: 4, integer: 2, selection: 2, monetary: 1, datetime: 3. Computed fields: 17. Field details: company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of pos.order.line.company_id>] [stored] [module: point_of_sale] [related: order_id.company_id]; name (char) [required] [module: point_of_sale]; notice (char) [module: point_of_sale]; product_id (many2one) [required] -> product.product [module: point_of_sale]; price_unit (float) [module: point_of_sale]; qty (float) [module: point_of_sale]; price_subtotal (float) [required] [readonly] [module: point_of_sale]; price_subtotal_incl (float) [required] [readonly] [module: point_of_sale]; discount (float) [module: point_of_sale]; order_id (many2one) [required] -> pos.order [module: point_of_sale]; tax_ids (many2many) [readonly] -> account.tax [module: point_of_sale]; tax_ids_after_fiscal_position (many2many) [readonly] -> account.tax [compute: _get_tax_ids_after_fiscal_position] [not stored] [module: point_of_sale]; pack_lot_ids (one2many) -> pos.pack.operation.lot [module: point_of_sale]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of pos.order.line.currency_id>] [not stored] [module: point_of_sale] [related: order_id.currency_id]; full_product_name (char) [module: point_of_sale]; mp_dirty (boolean) [module: pos_restaurant]; promotion (boolean) [readonly] [module: equip3_pos_masterdata]; promotion_id (many2one) [readonly] -> pos.promotion [module: equip3_pos_masterdata]; promotion_reason (char) [readonly] [module: equip3_pos_masterdata]; coupon_program_id (many2one) [readonly] -> coupon.program [module: equip3_pos_masterdata]; coupon_id (many2one) [readonly] -> coupon.coupon [module: equip3_pos_masterdata]; coupon_ids (many2many) [readonly] -> coupon.coupon [module: equip3_pos_masterdata]; discount_amount_percent (float) [module: equip3_pos_masterdata]; discount_from_pricelist (float) [module: equip3_pos_masterdata]; all_discount_except_pricelist (float) [module: equip3_pos_masterdata]; tax_amount (float) [module: equip3_pos_masterdata]; untax_amount (float) [module: equip3_pos_masterdata]; total_price (float) [module: equip3_pos_masterdata]; unit_price_pricelist (float) [module: equip3_pos_masterdata]; active (boolean) [module: equip3_pos_masterdata]; zone_id (many2one) -> pos.zone [module: equip3_pos_masterdata]; promotion_stack_ids (one2many) -> pos.order.line.promotion [module: equip3_pos_masterdata]; promotion_stack_data (text) [readonly] [compute: _compute_promotion_stack_data] [stored] [module: equip3_pos_masterdata]; pos_coupon_id (many2one) -> pos.coupon [module: equip3_pos_masterdata]; pos_coupon_reward_description (char) [module: equip3_pos_masterdata]; picking_type_id (many2one) -> stock.picking.type [module: equip3_pos_general]; partner_id (many2one) [readonly] -> res.partner [compute: <bound method Field._compute_related of pos.order.line.partner_id>] [not stored] [module: equip3_pos_general] [related: order_id.partner_id]; is_return (boolean) [module: equip3_pos_general]; order_uid (text) [readonly] [module: equip3_pos_general]; user_id (many2one) -> res.users [module: equip3_pos_general]; session_info (text) [readonly] [module: equip3_pos_general]; uid (text) [readonly] [module: equip3_pos_general]; tag_ids (many2many) -> pos.tag [module: equip3_pos_general]; discount_reason (char) [module: equip3_pos_general]; margin (float) [readonly] [compute: _compute_multi_margin] [stored] [module: equip3_pos_general]; margin_percent (float) [readonly] [compute: _compute_multi_margin] [stored] [module: equip3_pos_general]; purchase_price (float) [readonly] [compute: _compute_multi_margin] [stored] [module: equip3_pos_general]; config_id (many2one) [readonly] -> pos.config [compute: <bound method Field._compute_related of pos.order.line.config_id>] [not stored] [module: equip3_pos_general] [related: order_id.session_id.config_id]; pos_branch_id (many2one) [readonly] -> res.branch [compute: <bound method Field._compute_related of pos.order.line.pos_branch_id>] [stored] [module: equip3_pos_general] [related: order_id.pos_branch_id]; manager_user_id (many2one) -> res.users [module: equip3_pos_general]; analytic_account_id (many2one) [readonly] -> account.analytic.account [compute: <bound method Field._compute_related of pos.order.line.analytic_account_id>] [stored] [module: equip3_pos_general] [related: order_id.analytic_account_id]; returned_qty (float) [module: equip3_pos_general]; returned_order_line_id (many2one) -> pos.order.line [module: equip3_pos_general]; uom_id (many2one) [readonly] -> uom.uom [module: equip3_pos_general]; product_uom_id (many2one) -> uom.uom [module: equip3_pos_general]; is_shipping_cost (boolean) [module: equip3_pos_general]; order_time (char) [module: equip3_pos_general]; price_extra (float) [module: equip3_pos_general]; not_returnable (boolean) [readonly] [compute: <bound method Field._compute_related of pos.order.line.not_returnable>] [stored] [module: equip3_pos_general] [related: product_id.not_returnable]; returnable_by_categories (boolean) [readonly] [compute: _compute_allowed_categories] [stored] [module: equip3_pos_general]; line_qty_returned (integer) [module: equip3_pos_general]; original_line_id (many2one) -> pos.order.line [module: equip3_pos_general]; last_supplier_id (many2one) [readonly] -> res.partner [compute: <bound method Field._compute_related of pos.order.line.last_supplier_id>] [stored] [module: equip3_pos_general] [related: product_id.last_supplier_id]; is_done_self_pickup (boolean) [module: equip3_pos_general]; item_state (selection) [required] [module: equip3_pos_general]; is_complementary (boolean) [module: equip3_pos_general]; note (char) [module: equip3_pos_general]; mp_skip (boolean) [module: equip3_pos_general]; is_product_exchange (float) [module: equip3_pos_general_contd]; product_exchange_price (float) [module: equip3_pos_general_contd]; is_fee_of_product_exchange (boolean) [module: equip3_pos_general_contd]; reward_id (many2one) -> pos.loyalty.reward [module: equip3_pos_membership]; is_product_redeemed (boolean) [module: equip3_pos_membership]; plus_point (float) [readonly] [module: equip3_pos_membership]; plus_point_no_rounding (float) [readonly] [module: equip3_pos_membership]; redeem_point (float) [readonly] [module: equip3_pos_membership]; redeem_point_no_rounding (float) [readonly] [module: equip3_pos_membership]; state_related (selection) [readonly] [compute: <bound method Field._compute_related of pos.order.line.state_related>] [not stored] [module: equip3_pos_report] [related: order_id.state]; disc_fixed (float) [module: allfresh_mod_pos]; disc_manual (float) [module: allfresh_mod_pos]; disc_untax_amount (monetary) [module: allfresh_mod_pos]; 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].


How does pos_category_branch_rel relate to other tables? or List all constraint names in pos_category_branch_rel.

Response: Foreign keys in pos_category_branch_rel: branch_id -> res_branch.id [constraint: pos_category_branch_rel_branch_id_fkey]; categ_id -> pos_category.id [constraint: pos_category_branch_rel_categ_id_fkey]. Total foreign key relationships: 2. Referenced tables: pos_category, res_branch.


Explain the account_analytic_tag_invoice_recurring_rel table schema. or What indexes exist on account_analytic_tag_invoice_recurring_rel?

Response: The account_analytic_tag_invoice_recurring_rel table has 2 columns and 2 foreign key relationships. It stores data related to account analytic tag invoice recurring rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


Show me the column structure of res_users_kpi_category_rel_table. or What data types are used in res_users_kpi_category_rel_table?

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


Show me the column structure of pos_sessions. or What data types are used in pos_sessions?

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


How many columns are in base_import_module? or Describe the base_import_module table structure.

Response: The base_import_module table has 9 columns and 2 foreign key relationships. It stores data related to base import module in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, bytea: 1, character varying: 1, text: 1, boolean: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


How is setu.inventory.age.breakdown.report implemented technically? or Which fields in setu.inventory.age.breakdown.report are computed?

Response: The setu.inventory.age.breakdown.report model is defined in module: setu_advance_inventory_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: onchange_product_category_id, get_file_name, create_excel_workbook, create_excel_worksheet, set_column_width, set_format, set_report_title, get_inventory_age_breakdown_report_data, prepare_data_to_write, download_report, get_column_header, set_breakdown_header, write_report_data_header, write_data_to_worksheet.


What indexes exist on acrux_chat_select_conversation_wizard? or What columns does acrux_chat_select_conversation_wizard have?

Response: The acrux_chat_select_conversation_wizard table has 6 columns and 3 foreign key relationships. It stores data related to acrux chat select conversation wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, timestamp without time zone: 2. Nullable columns: 4, columns with defaults: 1.


Describe the many2many relations for sh.mrp.allow.qc.measurement. or Show me the relational structure of sh.mrp.allow.qc.measurement.

Response: The sh.mrp.allow.qc.measurement model has 5 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; mrp_id -> mrp.production; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What tables does split_pr_line_wizard reference? or What are the foreign keys in split_pr_line_wizard?

Response: Foreign keys in split_pr_line_wizard: create_uid -> res_users.id [constraint: split_pr_line_wizard_create_uid_fkey]; new_user_id -> res_users.id [constraint: split_pr_line_wizard_new_user_id_fkey]; pr_line_id -> purchase_request_line.id [constraint: split_pr_line_wizard_pr_line_id_fkey]; product_id -> product_product.id [constraint: split_pr_line_wizard_product_id_fkey]; user_id -> res_users.id [constraint: split_pr_line_wizard_user_id_fkey]; wizard_id -> split_pr_wizard.id [constraint: split_pr_line_wizard_wizard_id_fkey]; write_uid -> res_users.id [constraint: split_pr_line_wizard_write_uid_fkey]. Total foreign key relationships: 7. Referenced tables: product_product, purchase_request_line, res_users, split_pr_wizard.