What methods are defined in rn.approval_matrix_detail original module? or Which fields in rn.approval_matrix_detail are computed?

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


What one2many fields are in access.rights.profile? or List all relational fields in access.rights.profile.

Response: The access.rights.profile model has 3 relational fields: group_ids -> res.groups; create_uid -> res.users; write_uid -> res.users. Many2many fields: group_ids. One2many fields: none.


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

Response: Foreign keys in account_payment_register_res_partner_bank_rel: account_payment_register_id -> account_payment_register.id [constraint: account_payment_register_res_p_account_payment_register_id_fkey]; res_partner_bank_id -> res_partner_bank.id [constraint: account_payment_register_res_partner_b_res_partner_bank_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_partner_bank, account_payment_register.


Show me the foreign key constraints of res_partner. or What are the foreign keys in res_partner?

Response: Foreign keys in res_partner: approving_matrix_vendor_id -> approval_matrix_vendor.id [constraint: res_partner_approving_matrix_vendor_id_fkey]; associate_member -> res_partner.id [constraint: res_partner_associate_member_fkey]; branch_id -> res_branch.id [constraint: res_partner_branch_id_fkey]; city_id -> res_city.id [constraint: res_partner_city_id_fkey]; commercial_partner_id -> res_partner.id [constraint: res_partner_commercial_partner_id_fkey]; company_id -> res_company.id [constraint: res_partner_company_id_fkey]; country_id -> res_country.id [constraint: res_partner_country_id_fkey]; create_uid -> res_users.id [constraint: res_partner_create_uid_fkey]; customer_category -> customer_category.id [constraint: res_partner_customer_category_fkey]; customer_target_id -> customer_target.id [constraint: res_partner_customer_target_id_fkey]; discount_id -> pos_global_discount.id [constraint: res_partner_discount_id_fkey]; industry_id -> res_partner_industry.id [constraint: res_partner_industry_id_fkey]; interest_customer_account_receivable -> account_account.id [constraint: res_partner_interest_customer_account_receivable_fkey]; interest_vendor_account_payable -> account_account.id [constraint: res_partner_interest_vendor_account_payable_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: res_partner_message_main_attachment_id_fkey]; parent_id -> res_partner.id [constraint: res_partner_parent_id_fkey]; pos_branch_id -> res_branch.id [constraint: res_partner_pos_branch_id_fkey]; pos_loyalty_type -> pos_loyalty_category.id [constraint: res_partner_pos_loyalty_type_fkey]; preferred_location -> stock_location.id [constraint: res_partner_preferred_location_fkey]; property_product_pricelist -> product_pricelist.id [constraint: res_partner_property_product_pricelist_fkey]; related_company_id -> res_company.id [constraint: res_partner_related_company_id_fkey]; report_delivery_template_id -> ir_act_report_xml.id [constraint: res_partner_report_delivery_template_id_fkey]; report_picking_template_id -> ir_act_report_xml.id [constraint: res_partner_report_picking_template_id_fkey]; report_po_template_id -> ir_act_report_xml.id [constraint: res_partner_report_po_template_id_fkey]; report_pr_template_id -> ir_act_report_xml.id [constraint: res_partner_report_pr_template_id_fkey]; report_rfq_template_id -> ir_act_report_xml.id [constraint: res_partner_report_rfq_template_id_fkey]; report_sale_template_id -> ir_act_report_xml.id [constraint: res_partner_report_sale_template_id_fkey]; report_template_id -> ir_act_report_xml.id [constraint: res_partner_report_template_id_fkey]; request_partner_id -> res_partner.id [constraint: res_partner_request_partner_id_fkey]; res_city_id -> res_country_city.id [constraint: res_partner_res_city_id_fkey]; rfm_score_id -> setu_rfm_score.id [constraint: res_partner_rfm_score_id_fkey]; rfm_segment_id -> setu_rfm_segment.id [constraint: res_partner_rfm_segment_id_fkey]; state_id -> res_country_state.id [constraint: res_partner_state_id_fkey]; team_id -> crm_team.id [constraint: res_partner_team_id_fkey]; title -> res_partner_title.id [constraint: res_partner_title_fkey]; user_id -> res_users.id [constraint: res_partner_user_id_fkey]; website_id -> website.id [constraint: res_partner_website_id_fkey]; write_uid -> res_users.id [constraint: res_partner_write_uid_fkey]. Total foreign key relationships: 38. Referenced tables: res_partner_industry, stock_location, res_company, res_partner_title, res_country_state, ir_attachment, customer_category, crm_team, res_country, res_country_city, pos_loyalty_category, setu_rfm_segment, account_account, res_users, res_branch, setu_rfm_score, website, res_partner, ir_act_report_xml, res_city, approval_matrix_vendor, customer_target, pos_global_discount, product_pricelist.


Tell me about the reward_gift_product_product_rel table. or Explain the reward_gift_product_product_rel table schema.

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


What are the relationships in hide.view.nodes? or What one2many fields are in hide.view.nodes?

Response: The hide.view.nodes model has 7 relational fields: model_id -> ir.model; btn_store_model_nodes_ids -> store.model.nodes; page_store_model_nodes_ids -> store.model.nodes; link_store_model_nodes_ids -> store.model.nodes; access_management_id -> access.management; create_uid -> res.users; write_uid -> res.users. Many2many fields: btn_store_model_nodes_ids, page_store_model_nodes_ids, link_store_model_nodes_ids. One2many fields: none.


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

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


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

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


What tables does account_fiscal_position_tax_template reference? or What tables are connected to account_fiscal_position_tax_template?

Response: Foreign keys in account_fiscal_position_tax_template: create_uid -> res_users.id [constraint: account_fiscal_position_tax_template_create_uid_fkey]; position_id -> account_fiscal_position_template.id [constraint: account_fiscal_position_tax_template_position_id_fkey]; tax_dest_id -> account_tax_template.id [constraint: account_fiscal_position_tax_template_tax_dest_id_fkey]; tax_src_id -> account_tax_template.id [constraint: account_fiscal_position_tax_template_tax_src_id_fkey]; write_uid -> res_users.id [constraint: account_fiscal_position_tax_template_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: account_fiscal_position_template, account_tax_template, res_users.


What are the available fields for purchase.order.history? or What field types are used in purchase.order.history?

Response: The purchase.order.history model has 18 fields. Field types distribution: boolean: 1, many2one: 7, char: 2, float: 2, monetary: 1, selection: 1, integer: 1, datetime: 3. Computed fields: 9. Field details: purchase_reorder (boolean) [module: sh_all_in_one_purchase_tools]; name (many2one) -> purchase.order.line [module: sh_all_in_one_purchase_tools]; order_id (many2one) [readonly] -> purchase.order [module: sh_all_in_one_purchase_tools]; po_id (char) [module: sh_all_in_one_purchase_tools]; product_id (many2one) [readonly] -> product.product [compute: <bound method Field._compute_related of purchase.order.history.product_id>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.product_id]; price_unit (float) [readonly] [compute: <bound method Field._compute_related of purchase.order.history.price_unit>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.price_unit]; product_qty (float) [readonly] [compute: <bound method Field._compute_related of purchase.order.history.product_qty>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.product_qty]; product_uom (many2one) [readonly] -> uom.uom [compute: <bound method Field._compute_related of purchase.order.history.product_uom>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.product_uom]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of purchase.order.history.currency_id>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.currency_id]; price_subtotal (monetary) [readonly] [compute: <bound method Field._compute_related of purchase.order.history.price_subtotal>] [not stored] [module: sh_all_in_one_purchase_tools] [related: name.price_subtotal]; purchase_state (selection) [readonly] [compute: <bound method Field._compute_related of purchase.order.history.purchase_state>] [stored] [module: equip3_purchase_operation] [related: order_id.state]; 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 wizard.asset.create? or What modules define wizard.asset.create?

Response: The wizard.asset.create model is defined in module: equip3_accounting_asset. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: create_new_asset.


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

Response: Foreign keys in base_import_tests_models_preview: create_uid -> res_users.id [constraint: base_import_tests_models_preview_create_uid_fkey]; write_uid -> res_users.id [constraint: base_import_tests_models_preview_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: Columns in login_as: id (integer) [NOT NULL] [DEFAULT: nextval('login_as_id_seq'::regclass)] [PRECISION: 32]; group_id (integer) [PRECISION: 32] [COMMENT: Group]; user_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: User]; 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: 7. Statistics: 5 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in print_purchase_tender_report: create_uid -> res_users.id [constraint: print_purchase_tender_report_create_uid_fkey]; write_uid -> res_users.id [constraint: print_purchase_tender_report_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Show me the fields of term.condition. or What computed fields exist in term.condition?

Response: The term.condition model has 10 fields. Field types distribution: char: 3, html: 1, integer: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: name (char) [module: equip3_purchase_operation]; description (char) [module: equip3_purchase_operation]; term_condition (html) [module: equip3_purchase_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What are the relationships in account.cash.rounding? or List all relational fields in account.cash.rounding.

Response: The account.cash.rounding model has 5 relational fields: profit_account_id -> account.account; loss_account_id -> account.account; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


List all relational fields in pos.loyalty.history.update.point. or Describe the many2many relations for pos.loyalty.history.update.point.

Response: The pos.loyalty.history.update.point model has 4 relational fields: pos_order_ids -> pos.order; parent_id -> pos.loyalty.update.point; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_order_ids. One2many fields: none.


What columns have default values in account_partner_ledger_res_partner_category_rel? or Which columns are nullable in account_partner_ledger_res_partner_category_rel?

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


What methods are defined in ir.model.relation original module? or What methods are available in ir.model.relation?

Response: The ir.model.relation 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: _module_data_uninstall, _reflect_relation, create.


What are common use cases for sale.order.partner.credit? or How to query sale.order.partner.credit data?

Response: To use the sale.order.partner.credit model, you need to provide values for required fields: none. Readonly fields: name, order_partner, customer_credit_limit, total_receivable, current_order, sale_orders_cnt_amt, cust_invoice_cnt_amt, invoice_number, customer_max_invoice_overdue, is_set_customer_on_hold, avl_open_inv_limt, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [readonly]; order_partner [readonly]; customer_credit_limit [readonly]; total_receivable [readonly]; current_order [readonly]; sale_orders_cnt_amt [readonly]; cust_invoice_cnt_amt [readonly]; invoice_number [readonly]; customer_max_invoice_overdue [readonly]; is_set_customer_on_hold [readonly]; avl_open_inv_limt [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Describe the project.task.recurrence model in Odoo. or Can you explain the purpose of project.task.recurrence?

Response: The project.task.recurrence model represents Task Recurrence in the ERP system. It contains 28 fields and is used to manage task recurrence data. Defined in module: project. Key fields include: task_ids, next_recurrence_date, recurrence_left, repeat_interval, repeat_unit, repeat_type, repeat_until, repeat_number, repeat_on_month, repeat_on_year, mon, tue, wed, thu, fri, sat, sun, repeat_day, repeat_week, repeat_weekday, repeat_month, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What one2many fields are in res.mail.activity? or What models are connected to res.mail.activity?

Response: The res.mail.activity model has 6 relational fields: activity_type_id -> mail.activity.type; calendar_event_id -> calendar.event; res_id -> crm.lead; act_id -> mail.activity; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What fields does ir.actions.actions have? or What computed fields exist in ir.actions.actions?

Response: The ir.actions.actions model has 14 fields. Field types distribution: char: 5, html: 1, many2one: 3, selection: 1, integer: 1, datetime: 3. Computed fields: 3. Field details: name (char) [required] [module: base]; type (char) [required] [module: base]; xml_id (char) [readonly] [compute: _compute_xml_id] [not stored] [module: base]; help (html) [module: base]; binding_model_id (many2one) -> ir.model [module: base]; binding_type (selection) [required] [module: base]; binding_view_types (char) [module: base]; 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 queue_jobs_to_done? or List all columns in queue_jobs_to_done.

Response: Columns in queue_jobs_to_done: id (integer) [NOT NULL] [DEFAULT: nextval('queue_jobs_to_done_id_seq'::regclass)] [PRECISION: 32]; 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: 5. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


What indexes exist on bus_presence? or Tell me about the bus_presence table.

Response: The bus_presence table has 5 columns and 1 foreign key relationships. It stores data related to bus presence in the system. The table has 3 indexes for performance optimization. Column types: integer: 2, timestamp without time zone: 2, character varying: 1. Nullable columns: 3, columns with defaults: 1.


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

Response: The limit_request_product_brand_rel table has 2 columns and 2 foreign key relationships. It stores data related to limit request product brand rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


How to query receipt.payment.line.debit data? or What are common use cases for receipt.payment.line.debit?

Response: To use the receipt.payment.line.debit model, you need to provide values for required fields: none. Readonly fields: line_id, invoice_id, account_id, invoice_date, invoice_date_due, original_amount, base_amount, original_unreconcile, base_unreconcile, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: line_id [readonly]; invoice_id [readonly]; account_id [readonly]; invoice_date [readonly]; invoice_date_due [readonly]; original_amount [readonly]; base_amount [readonly]; original_unreconcile [readonly]; base_unreconcile [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What are the foreign keys in product_sale_details_report? or Describe the relational structure of product_sale_details_report.

Response: Foreign keys in product_sale_details_report: create_uid -> res_users.id [constraint: product_sale_details_report_create_uid_fkey]; details_id -> sh_sale_details_report_wizard.id [constraint: product_sale_details_report_details_id_fkey]; product_id -> product_product.id [constraint: product_sale_details_report_product_id_fkey]; write_uid -> res_users.id [constraint: product_sale_details_report_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: product_product, sh_sale_details_report_wizard, res_users.


What fields are readonly in sh.purchase.product.indent.wizard? or What operations can I perform on sh.purchase.product.indent.wizard?

Response: To use the sh.purchase.product.indent.wizard model, you need to provide values for required fields: sh_start_date, sh_end_date, sh_partner_ids, sh_category_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: sh_start_date [required] [has_default]; sh_end_date [required] [has_default]; sh_partner_ids [required]; sh_category_ids [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 mailing.contact model? or Tell me about the mailing.contact model.

Response: The mailing.contact model represents Mailing Contact in the ERP system. It contains 34 fields and is used to manage mailing contact data. Defined in module: mass_mailing. Key fields include: name, company_name, title_id, email, list_ids, subscription_list_ids, country_id, tag_ids, opt_out, email_normalized, is_blacklisted, message_bounce, 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.


Can you explain the purpose of bi.product.pack? or What does the bi.product.pack model represent?

Response: The bi.product.pack model represents bi.product.pack in the ERP system. It contains 14 fields and is used to manage bi.product.pack data. Defined in module: dynamic_product_bundle. Key fields include: product_id, qty_uom, bi_product_template, bi_image, price, uom_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does sh.notification.logger have? or Which fields are required in sh.notification.logger?

Response: The sh.notification.logger model has 12 fields. Field types distribution: char: 3, datetime: 4, many2one: 3, selection: 1, integer: 1. Computed fields: 2. Field details: name (char) [module: sh_backmate_theme_adv]; error (char) [module: sh_backmate_theme_adv]; datetime (datetime) [module: sh_backmate_theme_adv]; base_config_id (many2one) -> sh.send.notification [module: sh_backmate_theme_adv]; status (selection) [module: sh_backmate_theme_adv]; 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 can be stored in res.partner.type? or What are the available fields for res.partner.type?

Response: The res.partner.type model has 10 fields. Field types distribution: char: 2, float: 2, integer: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: equip3_pos_masterdata]; from_amount_total_orders (float) [module: equip3_pos_masterdata]; to_amount_total_orders (float) [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].


What field types are used in pos.login.history? or Show me the fields of pos.login.history.

Response: The pos.login.history model has 13 fields. Field types distribution: many2one: 6, datetime: 5, integer: 1, char: 1. Computed fields: 2. Field details: user_id (many2one) -> res.users [module: equip3_pos_report]; pos_config_id (many2one) -> pos.config [module: equip3_pos_report]; pos_branch_id (many2one) -> res.branch [module: equip3_pos_report]; checkin_datetime (datetime) [module: equip3_pos_report]; checkout_datetime (datetime) [module: equip3_pos_report]; company_id (many2one) -> res.company [module: equip3_pos_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].


What tables are connected to hr_employee_pos_config_rel? or How does hr_employee_pos_config_rel relate to other tables?

Response: Foreign keys in hr_employee_pos_config_rel: hr_employee_id -> hr_employee.id [constraint: hr_employee_pos_config_rel_hr_employee_id_fkey]; pos_config_id -> pos_config.id [constraint: hr_employee_pos_config_rel_pos_config_id_fkey]. Total foreign key relationships: 2. Referenced tables: hr_employee, pos_config.


Tell me about the account.cash.rounding model. or Describe the account.cash.rounding model in Odoo.

Response: The account.cash.rounding model represents Account Cash Rounding in the ERP system. It contains 14 fields and is used to manage account cash rounding data. Defined in module: account. Key fields include: name, rounding, strategy, profit_account_id, loss_account_id, rounding_method, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Columns in ir_ui_view_custom: id (integer) [NOT NULL] [DEFAULT: nextval('ir_ui_view_custom_id_seq'::regclass)] [PRECISION: 32]; ref_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Original View]; user_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: User]; arch (text) [NOT NULL] [COMMENT: View Architecture]; 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: 4 nullable, 1 with defaults, 0 with length constraints.


What computed fields exist in ks_dashboard_ninja.board? or What are the available fields for ks_dashboard_ninja.board?

Response: The ks_dashboard_ninja.board model has 30 fields. Field types distribution: char: 7, one2many: 4, many2one: 6, boolean: 1, many2many: 1, datetime: 5, selection: 4, integer: 2. Computed fields: 2. Field details: name (char) [required] [module: ks_dashboard_ninja]; ks_dashboard_items_ids (one2many) -> ks_dashboard_ninja.item [module: ks_dashboard_ninja]; ks_dashboard_menu_name (char) [module: ks_dashboard_ninja]; ks_dashboard_top_menu_id (many2one) -> ir.ui.menu [module: ks_dashboard_ninja]; ks_dashboard_client_action_id (many2one) -> ir.actions.client [module: ks_dashboard_ninja]; ks_dashboard_menu_id (many2one) -> ir.ui.menu [module: ks_dashboard_ninja]; ks_dashboard_state (char) [module: ks_dashboard_ninja]; ks_dashboard_active (boolean) [module: ks_dashboard_ninja]; ks_dashboard_group_access (many2many) -> res.groups [module: ks_dashboard_ninja]; ks_dashboard_start_date (datetime) [module: ks_dashboard_ninja]; ks_dashboard_end_date (datetime) [module: ks_dashboard_ninja]; ks_date_filter_selection (selection) [module: ks_dashboard_ninja]; ks_data_formatting (selection) [module: ks_dashboard_ninja]; ks_gridstack_config (char) [module: ks_dashboard_ninja]; ks_dashboard_default_template (many2one) -> ks_dashboard_ninja.board_template [module: ks_dashboard_ninja]; ks_set_interval (selection) [module: ks_dashboard_ninja]; ks_dashboard_menu_sequence (integer) [module: ks_dashboard_ninja]; ks_child_dashboard_ids (one2many) -> ks_dashboard_ninja.child_board [module: ks_dashboard_ninja]; ks_dashboard_defined_filters_ids (one2many) -> ks_dashboard_ninja.board_defined_filters [module: ks_dashboard_ninja]; ks_dashboard_custom_filters_ids (one2many) -> ks_dashboard_ninja.board_custom_filters [module: ks_dashboard_ninja]; ks_croessel_speed (selection) [module: ks_dn_advance]; ks_dashboard_icon_budget (char) [module: equip3_accounting_reports]; ks_dashboard_menu_icon_class (char) [module: equip3_pos_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].


How to query pos.generate.efaktur.other data? or What business logic is in pos.generate.efaktur.other?

Response: To use the pos.generate.efaktur.other 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.


Show me the foreign key constraints of budget_change_req. or What are the foreign keys in budget_change_req?

Response: Foreign keys in budget_change_req: approval_matrix -> approval_matrix_accounting.id [constraint: budget_change_req_approval_matrix_fkey]; branch_id -> res_branch.id [constraint: budget_change_req_branch_id_fkey]; budget_std_id -> crossovered_budget.id [constraint: budget_change_req_budget_std_id_fkey]; company_id -> res_company.id [constraint: budget_change_req_company_id_fkey]; create_uid -> res_users.id [constraint: budget_change_req_create_uid_fkey]; currency_id -> res_currency.id [constraint: budget_change_req_currency_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: budget_change_req_message_main_attachment_id_fkey]; request_partner_id -> res_partner.id [constraint: budget_change_req_request_partner_id_fkey]; requested_id -> res_users.id [constraint: budget_change_req_requested_id_fkey]; write_uid -> res_users.id [constraint: budget_change_req_write_uid_fkey]. Total foreign key relationships: 10. Referenced tables: crossovered_budget, res_partner, res_company, ir_attachment, res_currency, res_users, res_branch, approval_matrix_accounting.


Show me the foreign key constraints of do_matrix_reject. or What relationships exist for do_matrix_reject?

Response: Foreign keys in do_matrix_reject: create_uid -> res_users.id [constraint: do_matrix_reject_create_uid_fkey]; write_uid -> res_users.id [constraint: do_matrix_reject_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


What computed fields exist in mailing.list.merge? or Describe the field structure of mailing.list.merge.

Response: The mailing.list.merge model has 12 fields. Field types distribution: many2many: 1, many2one: 3, selection: 1, char: 2, boolean: 1, integer: 1, datetime: 3. Computed fields: 2. Field details: src_list_ids (many2many) -> mailing.list [module: mass_mailing]; dest_list_id (many2one) -> mailing.list [module: mass_mailing]; merge_options (selection) [required] [module: mass_mailing]; new_list_name (char) [module: mass_mailing]; archive_src_lists (boolean) [module: mass_mailing]; 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 foreign key constraints of digest_digest_res_users_rel. or How does digest_digest_res_users_rel relate to other tables?

Response: Foreign keys in digest_digest_res_users_rel: digest_digest_id -> digest_digest.id [constraint: digest_digest_res_users_rel_digest_digest_id_fkey]; res_users_id -> res_users.id [constraint: digest_digest_res_users_rel_res_users_id_fkey]. Total foreign key relationships: 2. Referenced tables: digest_digest, res_users.


Show me the foreign key constraints of stock_rule. or What tables does stock_rule reference?

Response: Foreign keys in stock_rule: company_id -> res_company.id [constraint: stock_rule_company_id_fkey]; create_uid -> res_users.id [constraint: stock_rule_create_uid_fkey]; group_id -> procurement_group.id [constraint: stock_rule_group_id_fkey]; location_id -> stock_location.id [constraint: stock_rule_location_id_fkey]; location_src_id -> stock_location.id [constraint: stock_rule_location_src_id_fkey]; partner_address_id -> res_partner.id [constraint: stock_rule_partner_address_id_fkey]; picking_type_id -> stock_picking_type.id [constraint: stock_rule_picking_type_id_fkey]; propagate_warehouse_id -> stock_warehouse.id [constraint: stock_rule_propagate_warehouse_id_fkey]; route_id -> stock_location_route.id [constraint: stock_rule_route_id_fkey]; warehouse_id -> stock_warehouse.id [constraint: stock_rule_warehouse_id_fkey]; write_uid -> res_users.id [constraint: stock_rule_write_uid_fkey]. Total foreign key relationships: 11. Referenced tables: stock_warehouse, stock_picking_type, res_partner, stock_location, res_company, stock_location_route, res_users, procurement_group.


What field types are used in website.snippet.filter? or Which fields are required in website.snippet.filter?

Response: The website.snippet.filter model has 17 fields. Field types distribution: char: 4, many2one: 5, integer: 2, boolean: 3, datetime: 3. Computed fields: 5. Field details: name (char) [required] [module: website]; action_server_id (many2one) -> ir.actions.server [module: website]; field_names (char) [required] [module: website]; filter_id (many2one) -> ir.filters [module: website]; limit (integer) [required] [module: website]; website_id (many2one) [required] -> website [module: website]; website_published (boolean) [compute: _compute_website_published] [not stored] [module: website] [inverse: _inverse_website_published]; is_published (boolean) [module: website]; can_publish (boolean) [readonly] [compute: _compute_can_publish] [not stored] [module: website]; website_url (char) [readonly] [compute: _compute_website_url] [not stored] [module: website]; 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 stock.location.route model? or How to create records in stock.location.route?

Response: To use the stock.location.route model, you need to provide values for required fields: name. Readonly fields: warehouse_domain_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; warehouse_domain_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 methods are available in report.sh_inventory_mrp_qc.quality_alert_doc? or Which fields are stored computed fields in report.sh_inventory_mrp_qc.quality_alert_doc?

Response: The report.sh_inventory_mrp_qc.quality_alert_doc 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: _get_report_values.


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

Response: Columns in approval_matrix_purchase_request_line: id (integer) [NOT NULL] [DEFAULT: nextval('approval_matrix_purchase_request_line_id_seq'::regclass)] [PRECISION: 32]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; minimum_approver (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Minimum Approver]; approval_matrix_purchase_request (integer) [PRECISION: 32] [COMMENT: Approval Matrix]; request_id (integer) [PRECISION: 32] [COMMENT: Purchase Request]; state_char (text) [COMMENT: Approval Status]; time_stamp (timestamp without time zone) [COMMENT: TimeStamp]; feedback (character varying) [COMMENT: Feedback]; last_approved (integer) [PRECISION: 32] [COMMENT: Users]; approved (boolean) [COMMENT: Approved]; sequence2 (integer) [PRECISION: 32] [COMMENT: No.]; approver_state (character varying) [COMMENT: State]; 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: 14 nullable, 1 with defaults, 0 with length constraints.


Tell me about the orderwizline.orderwizline model. or Describe the orderwizline.orderwizline model in Odoo.

Response: The orderwizline.orderwizline model represents Sale Blanket Wizard Order line in the ERP system. It contains 17 fields and is used to manage sale blanket wizard order line data. Defined in module: blanket_sale_order_app. Key fields include: reverse_id, product_id, partner_id, remaining_quantity, new_quatation_quantity, unit_of_measure_id, unit_price, taxes_id, subtotal, blanket_order_line_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields are available in mail_activity_type_mail_template_rel? or Show me the column structure of mail_activity_type_mail_template_rel.

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


Which fields are required in res.users.access.report.record? or Show me the fields of res.users.access.report.record.

Response: The res.users.access.report.record model has 26 fields. Field types distribution: integer: 2, many2one: 3, char: 2, boolean: 16, datetime: 3. Computed fields: 2. Field details: sl_no (integer) [readonly] [module: report_user_access_right]; user_id (many2one) [readonly] -> res.users [module: report_user_access_right]; login (char) [readonly] [module: report_user_access_right]; user_active (boolean) [readonly] [module: report_user_access_right]; column1 (boolean) [readonly] [module: report_user_access_right]; column2 (boolean) [readonly] [module: report_user_access_right]; column3 (boolean) [readonly] [module: report_user_access_right]; column4 (boolean) [readonly] [module: report_user_access_right]; column5 (boolean) [readonly] [module: report_user_access_right]; column6 (boolean) [readonly] [module: report_user_access_right]; column7 (boolean) [readonly] [module: report_user_access_right]; column8 (boolean) [readonly] [module: report_user_access_right]; column9 (boolean) [readonly] [module: report_user_access_right]; column10 (boolean) [readonly] [module: report_user_access_right]; column11 (boolean) [readonly] [module: report_user_access_right]; column12 (boolean) [readonly] [module: report_user_access_right]; column13 (boolean) [readonly] [module: report_user_access_right]; column14 (boolean) [readonly] [module: report_user_access_right]; column15 (boolean) [readonly] [module: report_user_access_right]; 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 is uom.category implemented technically? or What are the technical details of uom.category?

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


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

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


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

Response: The pos_sessions table has 2 columns and 2 foreign key relationships. It stores data related to pos sessions 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 fields of account.multipayment. or List all fields in the account.multipayment model.

Response: The account.multipayment model has 90 fields. Field types distribution: char: 10, many2one: 21, monetary: 5, date: 7, one2many: 8, selection: 7, integer: 6, datetime: 3, boolean: 19, many2many: 3, text: 1. Computed fields: 46. Field details: name (char) [readonly] [module: equip3_accounting_operation]; partner_id (many2one) [required] -> res.partner [module: equip3_accounting_operation]; amount (monetary) [required] [module: equip3_accounting_operation]; journal_id (many2one) [required] -> account.journal [module: equip3_accounting_operation]; currency_id (many2one) [required] -> res.currency [module: equip3_accounting_operation]; date (date) [required] [module: equip3_accounting_operation]; ref (char) [module: equip3_accounting_operation]; memo (char) [module: equip3_accounting_operation]; line_credit_ids (one2many) -> account.multipayment.credit [module: equip3_accounting_operation]; line_debit_ids (one2many) -> account.multipayment.debit [module: equip3_accounting_operation]; diff_amount (monetary) [readonly] [compute: _compute_diff_amount] [stored] [module: equip3_accounting_operation]; partner_type (selection) [module: equip3_accounting_operation]; total_amount_credit (monetary) [readonly] [compute: _calculate_credit_amount_total] [stored] [module: equip3_accounting_operation]; total_amount_debit (monetary) [readonly] [compute: _calculate_credit_amount_total] [stored] [module: equip3_accounting_operation]; payment_id_count (integer) [readonly] [compute: _calculate_credit_amount_total] [not stored] [module: equip3_accounting_operation]; company_id (many2one) [readonly] -> res.company [module: equip3_accounting_operation]; branch_id (many2one) -> res.branch [module: equip3_accounting_operation]; create_uid (many2one) [readonly] -> res.users [module: equip3_accounting_operation]; create_date (datetime) [readonly] [module: equip3_accounting_operation]; different_move_id (many2one) [readonly] -> account.move [module: equip3_accounting_operation]; request_partner_id (many2one) -> res.partner [module: equip3_accounting_operation]; payment_method (many2one) -> account.journal [module: equip3_accounting_operation]; multipul_payment_approval_matrix_id (many2one) [readonly] -> approval.matrix.accounting [compute: _get_multi_payment_approval_matrix] [not stored] [module: equip3_accounting_operation]; is_multi_payment_approval_matrix (boolean) [readonly] [compute: _get_multi_payment_approve_button_from_config] [not stored] [module: equip3_accounting_operation]; is_approve_button (boolean) [readonly] [compute: _get_approve_button_multi_receipt] [not stored] [module: equip3_accounting_operation]; approved_matrix_ids (one2many) -> approval.matrix.accounting.lines [module: equip3_accounting_operation]; approval_matrix_line_id (many2one) [readonly] -> approval.matrix.accounting.lines [compute: _get_approve_button_multi_receipt] [not stored] [module: equip3_accounting_operation]; action_validate_boolean (boolean) [readonly] [compute: _get_default_invisible] [not stored] [module: equip3_accounting_operation]; action_draft_boolean (boolean) [readonly] [compute: _get_default_invisible] [not stored] [module: equip3_accounting_operation]; action_cancel_boolean (boolean) [module: equip3_accounting_operation]; request_for_approval_boolean (boolean) [readonly] [compute: _get_default_invisible] [not stored] [module: equip3_accounting_operation]; action_approved_rp_boolean (boolean) [readonly] [compute: _get_default_invisible] [not stored] [module: equip3_accounting_operation]; rp_reject_boolean (boolean) [readonly] [compute: _get_default_invisible] [not stored] [module: equip3_accounting_operation]; state_boolean (boolean) [readonly] [compute: _get_default_invisible] [not stored] [module: equip3_accounting_operation]; state1_boolean (boolean) [readonly] [compute: _get_default_invisible] [not stored] [module: equip3_accounting_operation]; state2_boolean (boolean) [readonly] [compute: _get_default_invisible] [not stored] [module: equip3_accounting_operation]; difference_ids (one2many) -> account.multipayment.difference [module: equip3_accounting_operation]; payment_difference_amount (monetary) [readonly] [compute: _compute_payment_difference_amount] [not stored] [module: equip3_accounting_operation]; writeoff_account_id (many2one) -> account.account [module: equip3_accounting_operation]; writeoff_label (char) [module: equip3_accounting_operation]; payment_type (selection) [module: equip3_accounting_operation]; clearing_account_id (many2one) -> account.account [module: equip3_accounting_operation]; move_id (many2one) [readonly] -> account.move [module: equip3_accounting_operation]; due_date (date) [module: equip3_accounting_operation]; receive_date (date) [module: equip3_accounting_operation]; clearing_date (date) [module: equip3_accounting_operation]; is_vendor (boolean) [readonly] [compute: _compute_partner_type] [not stored] [module: equip3_accounting_operation]; state (selection) [module: equip3_accounting_operation]; state1 (selection) [readonly] [compute: <bound method Field._compute_related of account.multipayment.state1>] [not stored] [module: equip3_accounting_operation] [related: state]; state2 (selection) [readonly] [compute: <bound method Field._compute_related of account.multipayment.state2>] [not stored] [module: equip3_accounting_operation] [related: state]; payment_ids (many2many) [readonly] -> account.payment [compute: _getpayment_ids] [not stored] [module: equip3_accounting_operation]; invoice_cutoff_date (date) [module: equip3_accounting_operation]; is_cutoff_date (boolean) [readonly] [compute: _get_cut_off_date_config] [not stored] [module: equip3_accounting_operation]; is_check_all (boolean) [module: allfresh_mod_account_move]; campaign_id (many2one) -> utm.campaign [module: utm]; source_id (many2one) -> utm.source [module: utm]; medium_id (many2one) -> utm.medium [module: utm]; 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 account.multipayment.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of account.multipayment.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of account.multipayment.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of account.multipayment.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of account.multipayment.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 account.multipayment.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of account.multipayment.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]; access_url (char) [readonly] [compute: _compute_access_url] [not stored] [module: portal]; access_token (char) [module: portal]; access_warning (text) [readonly] [compute: _compute_access_warning] [not stored] [module: portal]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [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 base_update_translations. or List all columns in base_update_translations.

Response: Columns in base_update_translations: id (integer) [NOT NULL] [DEFAULT: nextval('base_update_translations_id_seq'::regclass)] [PRECISION: 32]; lang (character varying) [NOT NULL] [COMMENT: Language]; 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: 6. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


How to work with product.template.barcode fields? or How to create records in product.template.barcode?

Response: To use the product.template.barcode model, you need to provide values for required fields: name. Readonly fields: product_uom_category_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; product_uom_category_id [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 foreign keys exist in sparse_fields.test? or What models are connected to sparse_fields.test?

Response: The sparse_fields.test model has 3 relational fields: partner -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: Columns in approved_users_limit_patner_rel: limit_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.


What computed fields exist in service.work.order? or What fields does service.work.order have?

Response: The service.work.order model has 26 fields. Field types distribution: char: 4, many2one: 8, many2many: 1, datetime: 5, one2many: 2, selection: 1, float: 2, boolean: 1, integer: 2. Computed fields: 5. Field details: name (char) [readonly] [module: equip3_purchase_operation]; partner_id (many2one) [readonly] -> res.partner [module: equip3_purchase_operation]; account_analytic_tag_ids (many2many) [readonly] -> account.analytic.tag [module: equip3_purchase_operation]; date_planned (datetime) [readonly] [module: equip3_purchase_operation]; deadline_date (datetime) [module: equip3_purchase_operation]; origin (char) [module: equip3_purchase_operation]; company_id (many2one) [readonly] -> res.company [module: equip3_purchase_operation]; branch_id (many2one) [readonly] -> res.branch [module: equip3_purchase_operation]; order_line (one2many) -> service.work.order.line [module: equip3_purchase_operation]; state (selection) [module: equip3_purchase_operation]; purchase_order_id (many2one) -> purchase.order [module: equip3_purchase_operation]; checklist_ids (one2many) [readonly] -> service.work.order.checklist [module: equip3_purchase_operation]; purchase_line_milestone_id (many2one) -> milestone.contract.template.purchase [module: equip3_purchase_operation]; milestone_name (char) [readonly] [compute: <bound method Field._compute_related of service.work.order.milestone_name>] [not stored] [module: equip3_purchase_operation] [related: purchase_line_milestone_id.name]; contract_term (float) [readonly] [compute: <bound method Field._compute_related of service.work.order.contract_term>] [not stored] [module: equip3_purchase_operation] [related: purchase_line_milestone_id.contract_term]; progress_paid (float) [module: equip3_purchase_operation]; move_id (many2one) [readonly] -> account.move [module: equip3_purchase_operation]; invoiced (boolean) [module: equip3_purchase_operation]; account_move_count (integer) [readonly] [compute: <function ServiceWorkOrder._compute_account_moves at 0x30a9821f0>] [not stored] [module: equip3_purchase_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What is the user_calendar_rel table? or What columns does user_calendar_rel have?

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


Describe the pos_promotion table structure. or What indexes exist on pos_promotion?

Response: The pos_promotion table has 71 columns and 7 foreign key relationships. It stores data related to pos promotion in the system. The table has 1 indexes for performance optimization. Column types: integer: 12, character varying: 16, boolean: 18, date: 1, timestamp without time zone: 3, double precision: 19, text: 2. Nullable columns: 65, columns with defaults: 1.


What methods are available in mr.approval.matrix.line? or How is mr.approval.matrix.line implemented technically?

Response: The mr.approval.matrix.line model is defined in module: equip3_inventory_masterdata. It has 14 computed fields: sequence2, 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: sequence2. Related fields: sequence2 -> sequence. Original module methods: default_get, check_approver_sequence.


What fields are readonly in receivable.opening.balance? or What operations can I perform on receivable.opening.balance?

Response: To use the receivable.opening.balance 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 columns have default values in mail_wizard_invite_res_partner_rel? or List all columns in mail_wizard_invite_res_partner_rel.

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


Describe the stock.package.destination model in Odoo. or How is stock.package.destination used in the system?

Response: The stock.package.destination model represents Stock Package Destination in the ERP system. It contains 11 fields and is used to manage stock package destination data. Defined in module: stock. Key fields include: picking_id, move_line_ids, location_dest_id, filtered_location, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the relationships in pos.promotion.discount.apply? or Show me the relational structure of pos.promotion.discount.apply.

Response: The pos.promotion.discount.apply model has 4 relational fields: product_id -> product.product; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What indexes exist on config_discount_rel? or What is the config_discount_rel table?

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


What are the technical details of pos.bus.log? or What methods are available in pos.bus.log?

Response: The pos.bus.log model is defined in module: equip3_pos_general. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


What are the available fields for asset.depreciation.confirmation.wizard? or What data can be stored in asset.depreciation.confirmation.wizard?

Response: The asset.depreciation.confirmation.wizard model has 8 fields. Field types distribution: date: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: date (date) [required] [module: om_account_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 fields are available in ir_module_module? or What are the column types in ir_module_module?

Response: Columns in ir_module_module: id (integer) [NOT NULL] [DEFAULT: nextval('ir_module_module_id_seq'::regclass)] [PRECISION: 32]; create_uid (integer) [PRECISION: 32]; create_date (timestamp without time zone); write_date (timestamp without time zone); write_uid (integer) [PRECISION: 32]; website (character varying); summary (character varying); name (character varying) [NOT NULL]; author (character varying); icon (character varying); state (character varying) [LENGTH: 16]; latest_version (character varying); shortdesc (character varying); category_id (integer) [PRECISION: 32]; description (text); application (boolean) [DEFAULT: false]; demo (boolean) [DEFAULT: false]; web (boolean) [DEFAULT: false]; license (character varying) [LENGTH: 32]; sequence (integer) [DEFAULT: 100] [PRECISION: 32]; auto_install (boolean) [DEFAULT: false]; to_buy (boolean) [DEFAULT: false]; maintainer (character varying) [COMMENT: Maintainer]; contributors (text) [COMMENT: Contributors]; published_version (character varying) [COMMENT: Published Version]; url (character varying) [COMMENT: URL]; menus_by_module (text) [COMMENT: Menus]; reports_by_module (text) [COMMENT: Reports]; views_by_module (text) [COMMENT: Views]; version_status (character varying) [COMMENT: Version Status]; local_updatable (boolean) [COMMENT: Local updatable]; imported (boolean) [COMMENT: Imported Module]. Total columns: 32. Statistics: 30 nullable, 7 with defaults, 2 with length constraints.


Describe the columns of setu_inventory_fsn_analysis_report_stock_warehouse_rel. or What data types are used in setu_inventory_fsn_analysis_report_stock_warehouse_rel?

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


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

Response: Foreign keys in product_price_quantity: create_uid -> res_users.id [constraint: product_price_quantity_create_uid_fkey]; product_tmpl_id -> product_template.id [constraint: product_price_quantity_product_tmpl_id_fkey]; write_uid -> res_users.id [constraint: product_price_quantity_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, product_template.


Show me the relational structure of payable.opening.balance. or What one2many fields are in payable.opening.balance?

Response: The payable.opening.balance model has 4 relational fields: partner_opening_bal_id -> partner.opening.balance; vendor_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What is the module hierarchy for hide.field? or What methods are available in hide.field?

Response: The hide.field model is defined in module: simplify_access_management. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: load_views, fields_view_get, _get_access_management_domain_record, _check_access_management_right, _display_access_management_error, unlink, write, create.


What indexes exist on auditlog_rule? or Describe the auditlog_rule table structure.

Response: The auditlog_rule table has 17 columns and 4 foreign key relationships. It stores data related to auditlog rule in the system. The table has 3 indexes for performance optimization. Column types: integer: 5, character varying: 5, boolean: 5, timestamp without time zone: 2. Nullable columns: 13, columns with defaults: 1.


What indexes exist on rel_sh_sale_details_report_wizard_crm_team? or Tell me about the rel_sh_sale_details_report_wizard_crm_team table.

Response: The rel_sh_sale_details_report_wizard_crm_team table has 2 columns and 2 foreign key relationships. It stores data related to rel sh sale details report wizard crm team 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 stock_scrap_request_matrix_reject? or What is stored in stock_scrap_request_matrix_reject?

Response: The stock_scrap_request_matrix_reject table has 6 columns and 2 foreign key relationships. It stores data related to stock scrap request matrix reject in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, text: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


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

Response: Columns in auditlog_http_request: id (integer) [NOT NULL] [DEFAULT: nextval('auditlog_http_request_id_seq'::regclass)] [PRECISION: 32]; display_name (character varying) [COMMENT: Name]; name (character varying) [COMMENT: Path]; root_url (character varying) [COMMENT: Root URL]; user_id (integer) [PRECISION: 32] [COMMENT: User]; http_session_id (integer) [PRECISION: 32] [COMMENT: Session]; user_context (character varying) [COMMENT: Context]; 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: 10 nullable, 1 with defaults, 0 with length constraints.


What one2many fields are in stock.inventory.line? or What models are connected to stock.inventory.line?

Response: The stock.inventory.line model has 21 relational fields: inventory_id -> stock.inventory; partner_id -> res.partner; product_id -> product.product; product_uom_id -> uom.uom; categ_id -> product.category; package_id -> stock.quant.package; prod_lot_id -> stock.production.lot; company_id -> res.company; location_id -> stock.location; adjustment_account_id -> account.account; filtered_adjustment_account_id -> account.account; analytic_tag_ids -> account.analytic.tag; uom_id -> uom.uom; category_uom_id -> uom.category; wizard_id -> stock.inventory.wizard; currency_id -> res.currency; user_id_1 -> res.users; user_id_2 -> res.users; current_user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: filtered_adjustment_account_id, analytic_tag_ids. One2many fields: none.


What are the technical details of account.move? or What methods are available in account.move?

Response: The account.move model is defined in module: account. It has 129 computed fields: highest_name, type_name, suitable_journal_ids, company_id, country_code, user_id, payment_state, preferred_payment_method_id, debit_note_count, edi_state, edi_error_count, edi_web_services_to_process, edi_show_cancel_button, edi_show_abandon_cancel_button, edi_error_message, edi_blocking_level, payment_fields_boolean, tax_pay_seprately_amount, name, authorized_transaction_ids, period_id, fiscal_year, l10n_id_csv_created, l10n_id_need_kode_transaksi, landed_costs_visible, website_id, discount_amt, amount_untaxed, discount_amt_line, discount_account_id, commission_count, down_payment_amount, total_down_payment_amount, report_template_id1, amount_to_text, timesheet_count, approval_matrix_id, is_invoice_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, to_approve_state_payment_count, company_currency_id, commercial_partner_id, amount_tax, amount_tax2, subtotal_amount, amount_total, amount_untaxed_signed, amount_tax_signed, amount_total_signed, amount_residual_signed, amount_by_group, display_qr_code, invoice_outstanding_credits_debits_widget, invoice_has_outstanding, invoice_payments_widget, invoice_partner_display_name, invoice_filter_type_domain, bank_partner_id, invoice_has_matching_suspense_amount, tax_lock_date_message, has_reconciled_entries, show_reset_to_draft_button, restrict_mode_hash_table, string_to_hash, mr_show_analytic_account, analytic_tag_dynamic, reversal_avail, is_record_created, count_merged_invoice, is_button_update_invisible, status_code, code, check, check_invisible, total_tax_ppn, total_inv_ppn, subtotal_inv_ppn, check_invisible_ebupot, ebupot_template, hide_button_upload, hide_button_upload_cn, nomor_seri_domain, amount_residual, taxes_base_price, sales_times_tax_rate, tax_applies_on, currency_revaluation_count, filter_sale_order_reference_ids, exchange_stage, exchange_date, exchange_status, purchase_order_id, amount_swo, is_services_orders, filter_sale_order_ids, filter_purchase_order_ids, filter_picking_ids, receiving_note_names, receiving_note_dates, sequence, 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, sequence_prefix, sequence_number, display_name, __last_update. Stored computed fields: company_id, payment_state, preferred_payment_method_id, edi_state, payment_fields_boolean, tax_pay_seprately_amount, name, period_id, fiscal_year, website_id, discount_amt, amount_untaxed, discount_amt_line, discount_account_id, down_payment_amount, total_down_payment_amount, commercial_partner_id, amount_tax, amount_tax2, subtotal_amount, amount_total, amount_untaxed_signed, amount_tax_signed, amount_total_signed, amount_residual_signed, invoice_partner_display_name, total_tax_ppn, total_inv_ppn, subtotal_inv_ppn, amount_residual, sales_times_tax_rate, purchase_order_id, amount_swo, is_services_orders, sequence_prefix, sequence_number. Related fields: country_code -> company_id.country_id.code, user_id -> invoice_user_id, fiscal_year -> period_id.fiscal_year_id, website_id -> partner_id.website_id, state1 -> state, state2 -> state, company_currency_id -> company_id.currency_id, display_qr_code -> company_id.qr_code, restrict_mode_hash_table -> journal_id.restrict_mode_hash_table, mr_show_analytic_account -> company_id.mr_show_analytic_account, taxes_base_price -> amount_untaxed, exchange_stage -> exchange_id.stage, exchange_date -> exchange_id.date, 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: _search_default_journal, _get_default_journal, _get_default_invoice_date, _get_default_currency, _get_default_invoice_incoterm, _field_will_change, _cleanup_write_orm_values, _onchange_invoice_date, _onchange_journal, _onchange_partner_id, _onchange_currency, _onchange_payment_reference, _onchange_invoice_vendor_bill, _onchange_type, _onchange_invoice_line_ids, _onchange_recompute_dynamic_lines, _get_tax_grouping_key_from_tax_line, _get_tax_grouping_key_from_base_line, _get_tax_force_sign, _recompute_tax_lines, _get_base_amount_to_display, update_lines_tax_exigibility, _recompute_cash_rounding_lines, _recompute_payment_terms_lines, _recompute_dynamic_lines, _compute_company_id, _get_lines_onchange_currency, onchange, _compute_suitable_journal_ids, _compute_name, _compute_highest_name, _onchange_name_warning, _get_last_sequence_domain, _get_starting_sequence, _compute_type_name, _compute_invoice_filter_type_domain, _compute_commercial_partner_id, _compute_bank_partner_id, _get_invoice_in_payment_state, _compute_amount, _inverse_amount_total, _get_domain_matching_suspense_moves, _compute_has_matching_suspense_amount, _compute_invoice_partner_display_info, _compute_payments_widget_to_reconcile_info, _get_reconciled_info_JSON_values, _compute_payments_widget_reconciled_info, _compute_invoice_taxes_by_group, _get_tax_key_for_group_add_base, _compute_tax_lock_date_message, _compute_show_reset_to_draft_button, _synchronize_business_models, _check_unique_sequence_number, _check_duplicate_supplier_reference, _check_balanced, _check_fiscalyear_lock_date, _check_journal_type, _move_autocomplete_invoice_lines_values, _move_autocomplete_invoice_lines_create, _move_autocomplete_invoice_lines_write, copy, create, write, unlink, name_get, _creation_subtype, _track_subtype, _creation_message, _collect_tax_cash_basis_values, get_invoice_types, is_invoice, get_sale_types, is_sale_document, get_purchase_types, is_purchase_document, get_inbound_types, is_inbound, get_outbound_types, is_outbound, _affect_tax_report, _get_invoice_reference_euro_invoice, _get_invoice_reference_euro_partner, _get_invoice_reference_odoo_invoice, _get_invoice_reference_odoo_partner, _get_invoice_computed_reference, _get_move_display_name, _get_invoice_delivery_partner_id, _get_reconciled_payments, _get_reconciled_statement_lines, _get_reconciled_invoices, _get_reconciled_invoices_partials, _reverse_move_vals, _reverse_moves, open_reconcile_view, message_new, post, _post, _auto_compute_invoice_reference, action_reverse, action_post, js_assign_outstanding_line, js_remove_outstanding_partial, setting_upload_bill_wizard, button_draft, button_cancel, action_invoice_sent, _get_new_hash, _compute_hash, _compute_string_to_hash, action_invoice_print, action_invoice_paid, action_register_payment, action_switch_invoice_into_refund_credit_note, _get_report_base_filename, _get_name_invoice_report, preview_invoice, _compute_access_url, _compute_has_reconciled_entries, action_view_reverse_entry, _autopost_draft_entries, action_duplicate, _move_dict_to_preview_vals, generate_qr_code, _message_post_after_hook, _get_create_invoice_from_attachment_decoders, _get_update_invoice_from_attachment_decoders, _message_post_process_attachments, init, _constrains_date_sequence, _compute_split_sequence, _deduce_sequence_number_reset, _get_last_sequence, _get_sequence_format_param, _set_next_sequence.


Describe the columns of account_move_dev_rma_rma_rel. or What data types are used in account_move_dev_rma_rma_rel?

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


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

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


What fields are readonly in sh.split.rfq.wizard? or What are common use cases for sh.split.rfq.wizard?

Response: To use the sh.split.rfq.wizard model, you need to provide values for required fields: split_by. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: split_by [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.


Describe the project.profitability.report model in Odoo. or What does the project.profitability.report model represent?

Response: The project.profitability.report model represents Project Profitability Report in the ERP system. It contains 23 fields and is used to manage project profitability report data. Defined in module: sale_timesheet. Key fields include: analytic_account_id, project_id, currency_id, company_id, user_id, partner_id, line_date, timesheet_unit_amount, timesheet_cost, expense_cost, order_confirmation_date, sale_line_id, sale_order_id, product_id, amount_untaxed_to_invoice, amount_untaxed_invoiced, expense_amount_untaxed_to_invoice, expense_amount_untaxed_invoiced, other_revenues, margin, id, display_name, __last_update.


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

Response: The sh_sale_product_profit_xls table has 6 columns and 2 foreign key relationships. It stores data related to sh sale product profit xls in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, character varying: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


What relationships exist for pos_combo_limit_product_product_rel? or What tables are connected to pos_combo_limit_product_product_rel?

Response: Foreign keys in pos_combo_limit_product_product_rel: combo_limit_id -> pos_combo_limit.id [constraint: pos_combo_limit_product_product_rel_combo_limit_id_fkey]; product_id -> product_product.id [constraint: pos_combo_limit_product_product_rel_product_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, pos_combo_limit.


What field types are used in mail.alias.mixin? or What are the available fields for mail.alias.mixin?

Response: The mail.alias.mixin model has 18 fields. Field types distribution: many2one: 6, integer: 3, char: 3, datetime: 3, text: 1, html: 1, selection: 1. Computed fields: 16. Field details: alias_id (many2one) [required] [readonly] -> mail.alias [module: mail]; 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]; alias_name (char) [readonly] [compute: <bound method Field._compute_related of mail.alias.mixin.alias_name>] [not stored] [module: None] [related: alias_id.alias_name] [inverse: <bound method Field._inverse_related of mail.alias.mixin.alias_name>]; alias_model_id (many2one) [required] [readonly] -> ir.model [compute: <bound method Field._compute_related of mail.alias.mixin.alias_model_id>] [not stored] [module: None] [related: alias_id.alias_model_id] [inverse: <bound method Field._inverse_related of mail.alias.mixin.alias_model_id>]; alias_user_id (many2one) [readonly] -> res.users [compute: <bound method Field._compute_related of mail.alias.mixin.alias_user_id>] [not stored] [module: None] [related: alias_id.alias_user_id] [inverse: <bound method Field._inverse_related of mail.alias.mixin.alias_user_id>]; alias_defaults (text) [required] [readonly] [compute: <bound method Field._compute_related of mail.alias.mixin.alias_defaults>] [not stored] [module: None] [related: alias_id.alias_defaults] [inverse: <bound method Field._inverse_related of mail.alias.mixin.alias_defaults>]; alias_force_thread_id (integer) [readonly] [compute: <bound method Field._compute_related of mail.alias.mixin.alias_force_thread_id>] [not stored] [module: None] [related: alias_id.alias_force_thread_id] [inverse: <bound method Field._inverse_related of mail.alias.mixin.alias_force_thread_id>]; alias_domain (char) [readonly] [compute: <bound method Field._compute_related of mail.alias.mixin.alias_domain>] [not stored] [module: None] [related: alias_id.alias_domain] [inverse: <bound method Field._inverse_related of mail.alias.mixin.alias_domain>]; alias_parent_model_id (many2one) [readonly] -> ir.model [compute: <bound method Field._compute_related of mail.alias.mixin.alias_parent_model_id>] [not stored] [module: None] [related: alias_id.alias_parent_model_id] [inverse: <bound method Field._inverse_related of mail.alias.mixin.alias_parent_model_id>]; alias_parent_thread_id (integer) [readonly] [compute: <bound method Field._compute_related of mail.alias.mixin.alias_parent_thread_id>] [not stored] [module: None] [related: alias_id.alias_parent_thread_id] [inverse: <bound method Field._inverse_related of mail.alias.mixin.alias_parent_thread_id>]; alias_bounced_content (html) [readonly] [compute: <bound method Field._compute_related of mail.alias.mixin.alias_bounced_content>] [not stored] [module: None] [related: alias_id.alias_bounced_content] [inverse: <bound method Field._inverse_related of mail.alias.mixin.alias_bounced_content>]; alias_contact (selection) [required] [readonly] [compute: <bound method Field._compute_related of mail.alias.mixin.alias_contact>] [not stored] [module: None] [related: alias_id.alias_contact] [inverse: <bound method Field._inverse_related of mail.alias.mixin.alias_contact>]; create_uid (many2one) [readonly] -> res.users [compute: <bound method Field._compute_related of mail.alias.mixin.create_uid>] [not stored] [module: None] [related: alias_id.create_uid] [inverse: <bound method Field._inverse_related of mail.alias.mixin.create_uid>]; create_date (datetime) [readonly] [compute: <bound method Field._compute_related of mail.alias.mixin.create_date>] [not stored] [module: None] [related: alias_id.create_date] [inverse: <bound method Field._inverse_related of mail.alias.mixin.create_date>]; write_uid (many2one) [readonly] -> res.users [compute: <bound method Field._compute_related of mail.alias.mixin.write_uid>] [not stored] [module: None] [related: alias_id.write_uid] [inverse: <bound method Field._inverse_related of mail.alias.mixin.write_uid>]; write_date (datetime) [readonly] [compute: <bound method Field._compute_related of mail.alias.mixin.write_date>] [not stored] [module: None] [related: alias_id.write_date] [inverse: <bound method Field._inverse_related of mail.alias.mixin.write_date>].


Describe the field structure of sh.target.commision.new. or What fields does sh.target.commision.new have?

Response: The sh.target.commision.new model has 18 fields. Field types distribution: many2one: 4, char: 2, float: 4, selection: 3, date: 1, integer: 1, datetime: 3. Computed fields: 2. Field details: commission_id (many2one) -> sh.target.commision [module: equip3_sale_team_commission]; name (char) [readonly] [module: equip3_sale_team_commission]; user_id (many2one) -> res.users [module: equip3_sale_team_commission]; main_target (float) [module: equip3_sale_team_commission]; current_achievement (float) [module: equip3_sale_team_commission]; current_achievement_formula (float) [module: equip3_sale_team_commission]; curr_achieve (float) [module: equip3_sale_team_commission]; target_based_on (selection) [module: equip3_sale_team_commission]; target_on (selection) [module: equip3_sale_team_commission]; to_date (date) [module: equip3_sale_team_commission]; type (selection) [module: equip3_sale_team_commission]; 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 many columns are in sale_order? or What is stored in sale_order?

Response: The sale_order table has 154 columns and 47 foreign key relationships. It stores data related to sale order in the system. The table has 10 indexes for performance optimization. Column types: integer: 54, character varying: 34, timestamp without time zone: 8, date: 2, boolean: 35, text: 1, numeric: 11, double precision: 9. Nullable columns: 142, columns with defaults: 1.


How to create records in ai.agent.config? or What business logic is in ai.agent.config?

Response: To use the ai.agent.config model, you need to provide values for required fields: name, provider. Readonly fields: model, model_info, full_system_prompt, total_sessions, total_messages, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; provider [required] [has_default]; model [readonly]; model_info [readonly] [computed] [no_copy]; full_system_prompt [readonly] [computed] [no_copy]; total_sessions [readonly] [computed] [no_copy]; total_messages [readonly] [computed] [no_copy]; max_input_tokens [computed]; max_output_tokens [computed]; is_support_vision [computed]; is_support_pdf_input [computed]; mode [computed]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

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


How does sh_purchase_bill_summary_xls relate to other tables? or Show me the foreign key constraints of sh_purchase_bill_summary_xls.

Response: Foreign keys in sh_purchase_bill_summary_xls: create_uid -> res_users.id [constraint: sh_purchase_bill_summary_xls_create_uid_fkey]; write_uid -> res_users.id [constraint: sh_purchase_bill_summary_xls_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


How do I use the product.quantity.available.report model? or What fields are readonly in product.quantity.available.report?

Response: To use the product.quantity.available.report model, you need to provide values for required fields: none. Readonly fields: product_barcode, product_default_code, location_id, product_id, qty_available, in_date, sale_qty, id, display_name, __last_update. Field usage details: product_barcode [readonly]; product_default_code [readonly]; location_id [readonly]; product_id [readonly]; qty_available [readonly]; in_date [readonly]; sale_qty [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: The account_account_type_account_partner_ledger_rel table has 2 columns and 2 foreign key relationships. It stores data related to account account type 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.


Which fields are required in product.warehouse.cost? or Show me the fields of product.warehouse.cost.

Response: The product.warehouse.cost model has 10 fields. Field types distribution: many2one: 4, one2many: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: product_id (many2one) [readonly] -> product.product [module: equip3_accounting_stockoperation]; product_cost_line_ids (one2many) [readonly] -> product.warehouse.cost.line [module: equip3_accounting_stockoperation]; company_id (many2one) -> res.company [module: equip3_accounting_stockoperation]; 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 customer.deposit? or How is customer.deposit implemented technically?

Response: The customer.deposit model is defined in module: equip3_accounting_deposit. It has 34 computed fields: filter_deposit_account_ids, is_show_cancel, invoice_count, reconcile_count, approval_matrix_id, is_customer_deposit_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, 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: invoice_count, reconcile_count. Related fields: state1 -> state, state2 -> 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: action_approve, _get_approval_matrix, action_reject, action_add_amount_deposit, search_read, read_group, _compute_approving_matrix_lines, action_request_for_approval, _send_whatsapp_message, _get_approve_button, _get_approve_button_from_config, currency, onchange_name, _compute_deposit_account_ids, _compute_show_cancel, create, customer_deposit_post, convert_revenue, button_cancel_customer_deposit, button_draft_customer_deposit, _check_values_of_amount, _compute_invoice, _compute_reconcile, action_view_invoice, action_view_reconcile, _get_street, _get_address_details.


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

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


Describe the implementation of website.mass_mailing.popup. or What methods are defined in website.mass_mailing.popup original module?

Response: The website.mass_mailing.popup model is defined in module: website_mass_mailing. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _default_popup_content.


Show me the fields of kitchen.cooking.list. or What are the available fields for kitchen.cooking.list?

Response: The kitchen.cooking.list model has 12 fields. Field types distribution: date: 2, many2one: 4, one2many: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: from_date (date) [module: equip3_kitchen_operations]; to_date (date) [module: equip3_kitchen_operations]; company_id (many2one) -> res.company [module: equip3_kitchen_operations]; warehouse_id (many2one) -> stock.warehouse [module: equip3_kitchen_operations]; product_ids (one2many) -> kitchen.cooking.list.line [module: equip3_kitchen_operations]; 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 account_tour_upload_bill table. or What columns does account_tour_upload_bill have?

Response: The account_tour_upload_bill table has 7 columns and 3 foreign key relationships. It stores data related to account tour upload bill in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, character varying: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.


How does change_password_user relate to other tables? or What are the foreign keys in change_password_user?

Response: Foreign keys in change_password_user: create_uid -> res_users.id [constraint: change_password_user_create_uid_fkey]; user_id -> res_users.id [constraint: change_password_user_user_id_fkey]; wizard_id -> change_password_wizard.id [constraint: change_password_user_wizard_id_fkey]; write_uid -> res_users.id [constraint: change_password_user_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_users, change_password_wizard.


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

Response: Columns in sh_wqm_quick_menu: id (integer) [NOT NULL] [DEFAULT: nextval('sh_wqm_quick_menu_id_seq'::regclass)] [PRECISION: 32]; menu_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Menu]; user_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: User]; parent_menu_id (integer) [PRECISION: 32] [COMMENT: Parent Menu ID]; 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: 5 nullable, 1 with defaults, 0 with length constraints.


What fields are readonly in im_livechat.channel.rule? or How do I use the im_livechat.channel.rule model?

Response: To use the im_livechat.channel.rule model, you need to provide values for required fields: action. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: action [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 is the finish.good.rework model? or What does the finish.good.rework model represent?

Response: The finish.good.rework model represents Kitchen Production Record in the ERP system. It contains 86 fields and is used to manage kitchen production record data. Defined in module: allfresh_mod_kitchen_operation. Key fields include: type_finished_goods, product_tmpl_ids, product_ids, name, company_id, is_branch_required, product_qty, rejected_qty, product_uom_id, product_uom_category_id, bom_id, branch_id, confirm_date, state, move_raw_ids, move_finished_ids, move_byproduct_ids, location_src_id, location_dest_id, picking_type_id, date_planned_start, date_planned_finished, date_deadline, procurement_group_id, move_dest_ids, production_location_id, warehouse_id, product_tracking, account_move_ids, purchase_request_ids, internal_transfer_count, expiry_days, product_use_expiration_date, finished_lot_ids, byproduct_lot_ids, rejected_lot_ids, show_submit_button, is_autogenerate, default_finished_lot_qty, default_rejected_lot_qty, show_byproduct_lot_tab, byproduct_manual_product_ids, default_byproduct_lot_qty, default_next_byproduct_product_id, any_byproduct_is_autogenerate, all_byproduct_is_autogenerate, total_bom_cost, total_bom_sub_total, total_bom_quantity, total_product_cost, total_product_sub_total, total_product_quantity, total_overall, total_overall_sub_total, 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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields are readonly in rating.mixin? or How do I use the rating.mixin model?

Response: To use the rating.mixin model, you need to provide values for required fields: none. Readonly fields: rating_ids, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, id, display_name, __last_update. Field usage details: rating_ids [readonly] [no_copy]; rating_last_value [readonly] [computed] [no_copy]; rating_last_feedback [readonly] [computed] [no_copy]; rating_last_image [readonly] [computed] [no_copy]; rating_count [readonly] [computed] [no_copy]; rating_avg [readonly] [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 is stored in sh_sale_pro_attr_ids_rel_comp_table? or What is the sh_sale_pro_attr_ids_rel_comp_table table?

Response: The sh_sale_pro_attr_ids_rel_comp_table table has 2 columns and 2 foreign key relationships. It stores data related to sh sale pro attr ids rel comp table in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.