Dataset Preview
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
[{'expected': SplitInfo(name='train', num_bytes=0, num_examples=9066, shard_lengths=None, dataset_name=None), 'recorded': SplitInfo(name='train', num_bytes=11027216, num_examples=11346, shard_lengths=None, dataset_name='hashmicro-allfresh')}, {'expected': SplitInfo(name='validation', num_bytes=0, num_examples=4999, shard_lengths=None, dataset_name=None), 'recorded': SplitInfo(name='validation', num_bytes=2578763, num_examples=2719, shard_lengths=None, dataset_name='hashmicro-allfresh')}]
Error code:   UnexpectedError

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

text
string
response
string
source
string
category
string
complexity_level
string
model_name
string
table_name
string
What tables are connected to pos_promotion_specific_product? or Describe the relational structure of pos_promotion_specific_product.
Foreign keys in pos_promotion_specific_product: create_uid -> res_users.id [constraint: pos_promotion_specific_product_create_uid_fkey]; product_id -> product_product.id [constraint: pos_promotion_specific_product_product_id_fkey]; promotion_id -> pos_promotion.id [constraint: pos_promotion_specific_product_promotion_id_fkey]; write_uid -> res_users.id [constraint: pos_promotion_specific_product_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: product_product, res_users, pos_promotion.
sql_introspection
relationships
intermediate
pos_promotion_specific_product
What is the approval.matrix.blanket.order model? or Describe the approval.matrix.blanket.order model in Odoo.
The approval.matrix.blanket.order model represents Approval Matrix Blanket Order in the ERP system. It contains 44 fields and is used to manage approval matrix blanket order data. Defined in module: equip3_purchase_other_operation. Key fields include: name, company_id, branch_id, approval_matrix_blanket_order_line_ids, is_good_services_order, order_type, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.
orm_introspection
basic_info
basic
approval.matrix.blanket.order
What fields does account.tax have? or Describe the field structure of account.tax.
The account.tax model has 58 fields. Field types distribution: many2one: 11, boolean: 13, char: 7, selection: 6, many2many: 3, integer: 6, float: 1, one2many: 6, date: 2, datetime: 3. Computed fields: 25. Field details: tax_paid_account (many2one) -> account.account [module: equip3_accounting_taxoperation]; price_include_total (boolean) [module: equip3_accounting_taxoperation]; pay_separately (boolean) [module: equip3_accounting_taxoperation]; name (char) [required] [module: equip3_accounting_masterdata]; type_tax_use (selection) [required] [module: equip3_accounting_masterdata]; tax_scope (selection) [module: equip3_accounting_masterdata]; amount_type (selection) [required] [module: equip3_accounting_masterdata]; active (boolean) [module: equip3_accounting_masterdata]; company_id (many2one) [required] [readonly] -> res.company [module: equip3_accounting_masterdata]; children_tax_ids (many2many) -> account.tax [module: equip3_accounting_masterdata]; sequence (integer) [required] [module: equip3_accounting_masterdata]; amount (float) [required] [module: equip3_accounting_masterdata]; description (char) [module: equip3_accounting_masterdata]; price_include (boolean) [module: equip3_accounting_masterdata]; include_base_amount (boolean) [module: equip3_accounting_masterdata]; analytic (boolean) [module: equip3_accounting_masterdata]; tax_group_id (many2one) [required] -> account.tax.group [module: equip3_accounting_masterdata]; hide_tax_exigibility (boolean) [readonly] [compute: <bound method Field._compute_related of account.tax.hide_tax_exigibility>] [not stored] [module: equip3_accounting_masterdata] [related: company_id.tax_exigibility]; tax_exigibility (selection) [module: equip3_accounting_masterdata]; cash_basis_transition_account_id (many2one) -> account.account [module: equip3_accounting_masterdata]; invoice_repartition_line_ids (one2many) -> account.tax.repartition.line [module: equip3_accounting_masterdata]; refund_repartition_line_ids (one2many) -> account.tax.repartition.line [module: equip3_accounting_masterdata]; tax_fiscal_country_id (many2one) [readonly] -> res.country [compute: <bound method Field._compute_related of account.tax.tax_fiscal_country_id>] [not stored] [module: equip3_accounting_masterdata] [related: company_id.account_tax_fiscal_country_id]; country_code (char) [readonly] [compute: <bound method Field._compute_related of account.tax.country_code>] [not stored] [module: equip3_accounting_masterdata] [related: company_id.country_id.code]; branch_id (many2one) -> res.branch [module: equip3_accounting_masterdata]; is_ppn (boolean) [module: equip3_accounting_efaktur]; 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.tax.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of account.tax.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of account.tax.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of account.tax.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of account.tax.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.tax.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of account.tax.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; 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].
orm_introspection
field_inquiry
basic
account.tax
Describe the free.product.lines model in Odoo. or Tell me about the free.product.lines model.
The free.product.lines model represents Free Product Lines in the ERP system. It contains 12 fields and is used to manage free product lines data. Defined in module: equip3_sale_loyalty. Key fields include: product_id, description, quantity, uom_id, customer_target_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.
orm_introspection
basic_info
basic
free.product.lines
What field types are used in account.report.general.ledger? or What are the available fields for account.report.general.ledger?
The account.report.general.ledger model has 16 fields. Field types distribution: boolean: 1, selection: 3, many2many: 1, date: 2, many2one: 4, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: initial_balance (boolean) [module: accounting_pdf_reports]; sortby (selection) [required] [module: accounting_pdf_reports]; journal_ids (many2many) [required] -> account.journal [module: accounting_pdf_reports]; display_account (selection) [required] [module: accounting_pdf_reports]; date_from (date) [module: account]; date_to (date) [module: account]; target_move (selection) [required] [module: account]; report_currency_id (many2one) -> res.currency [module: equip3_accounting_reports]; company_id (many2one) [required] -> res.company [module: equip3_accounting_reports]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].
orm_introspection
field_inquiry
basic
account.report.general.ledger
How do I use the account.trial.balance model? or What operations can I perform on account.trial.balance?
To use the account.trial.balance model, you need to provide values for required fields: journal_ids, display_account, consolidate, all_account, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: journal_ids [required] [has_default]; display_account [required] [has_default]; consolidate [required] [has_default]; all_account [required] [has_default]; target_move [required] [has_default]; company_id [required] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.
orm_introspection
usage
intermediate
account.trial.balance
How do I use the approval.matrix.vendor model? or What operations can I perform on approval.matrix.vendor?
To use the approval.matrix.vendor model, you need to provide values for required fields: name, company_id, branch_id. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; company_id [required] [readonly] [has_default]; branch_id [required] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.
orm_introspection
usage
intermediate
approval.matrix.vendor
Which columns are nullable in sms_template_preview? or What data types are used in sms_template_preview?
Columns in sms_template_preview: id (integer) [NOT NULL] [DEFAULT: nextval('sms_template_preview_id_seq'::regclass)] [PRECISION: 32]; sms_template_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Sms Template]; lang (character varying) [COMMENT: Template Preview Language]; resource_ref (character varying) [COMMENT: Record reference]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
sms_template_preview
Tell me about the sh_sale_category_xls table. or Explain the sh_sale_category_xls table schema.
The sh_sale_category_xls table has 6 columns and 2 foreign key relationships. It stores data related to sh sale category 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.
sql_introspection
structure
basic
sh_sale_category_xls
How does pos.payment.report relate to other models? or Show me the relational structure of pos.payment.report.
The pos.payment.report model has 8 relational fields: payment_method_id -> pos.payment.method; config_id -> pos.config; order_id -> pos.order; session_id -> pos.session; company_id -> res.company; pos_branch_id -> res.branch; currency_id -> res.currency; partner_id -> res.partner. Many2many fields: none. One2many fields: none.
orm_introspection
relationship
intermediate
pos.payment.report
Describe the implementation of partial.quantity.done. or What modules define partial.quantity.done?
The partial.quantity.done 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: action_confirm_partial_quantity.
orm_introspection
technical
advanced
partial.quantity.done
What are the foreign keys in stock_valuation_layer? or What tables does stock_valuation_layer reference?
Foreign keys in stock_valuation_layer: account_move_id -> account_move.id [constraint: stock_valuation_layer_account_move_id_fkey]; company_id -> res_company.id [constraint: stock_valuation_layer_company_id_fkey]; create_uid -> res_users.id [constraint: stock_valuation_layer_create_uid_fkey]; location_id -> stock_location.id [constraint: stock_valuation_layer_location_id_fkey]; new_inventory_id -> stock_inventory.id [constraint: stock_valuation_layer_new_inventory_id_fkey]; new_location_id -> stock_location.id [constraint: stock_valuation_layer_new_location_id_fkey]; new_warehouse_id -> stock_warehouse.id [constraint: stock_valuation_layer_new_warehouse_id_fkey]; product_id -> product_product.id [constraint: stock_valuation_layer_product_id_fkey]; stock_landed_cost_id -> stock_landed_cost.id [constraint: stock_valuation_layer_stock_landed_cost_id_fkey]; stock_move_id -> stock_move.id [constraint: stock_valuation_layer_stock_move_id_fkey]; stock_valuation_layer_id -> stock_valuation_layer.id [constraint: stock_valuation_layer_stock_valuation_layer_id_fkey]; warehouse_id -> stock_warehouse.id [constraint: stock_valuation_layer_warehouse_id_fkey]; write_uid -> res_users.id [constraint: stock_valuation_layer_write_uid_fkey]. Total foreign key relationships: 13. Referenced tables: stock_warehouse, product_product, stock_valuation_layer, stock_inventory, stock_move, stock_location, res_company, res_users, stock_landed_cost, account_move.
sql_introspection
relationships
intermediate
stock_valuation_layer
What columns have default values in stock_rules_report_stock_warehouse_rel? or What are the length constraints in stock_rules_report_stock_warehouse_rel?
Columns in stock_rules_report_stock_warehouse_rel: stock_rules_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.
sql_introspection
columns
basic
stock_rules_report_stock_warehouse_rel
Can you explain the purpose of vendor.deposit.amount.wizard? or What does the vendor.deposit.amount.wizard model represent?
The vendor.deposit.amount.wizard model represents vendor deposit amount wizard in the ERP system. It contains 13 fields and is used to manage vendor deposit amount wizard data. Defined in module: equip3_accounting_deposit. Key fields include: currency_id, deposit_amount, final_amount, final_remaining_amount, is_vendor_deposit_approval_matrix, approve_vendor_deposit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.
orm_introspection
basic_info
basic
vendor.deposit.amount.wizard
What are the length constraints in pos_loyalty_point_product_product_rel? or What are the column types in pos_loyalty_point_product_product_rel?
Columns in pos_loyalty_point_product_product_rel: loyalty_point_id (integer) [NOT NULL] [PRECISION: 32]; product_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.
sql_introspection
columns
basic
pos_loyalty_point_product_product_rel
What are the available fields for target.activity.line? or Which fields are required in target.activity.line?
The target.activity.line model has 13 fields. Field types distribution: many2one: 5, integer: 2, float: 2, char: 1, datetime: 3. Computed fields: 5. Field details: user_id (many2one) [readonly] -> res.users [compute: <bound method Field._compute_related of target.activity.line.user_id>] [not stored] [module: equip3_crm_operation] [related: activity_id.user_id]; activity_id (many2one) -> target.activity [module: equip3_crm_operation]; activity_type (many2one) -> mail.activity.type [module: equip3_crm_operation]; activity_target (integer) [module: equip3_crm_operation]; achieved_target (float) [readonly] [compute: _compute_target] [not stored] [module: equip3_crm_operation]; remaining_target (float) [readonly] [compute: _compute_target] [not stored] [module: equip3_crm_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].
orm_introspection
field_inquiry
basic
target.activity.line
What methods are available in wizard.product.bundle.bi? or Describe the implementation of wizard.product.bundle.bi.
The wizard.product.bundle.bi model is defined in module: dynamic_product_bundle. It has 3 computed fields: bi_pack_ids, display_name, __last_update. Stored computed fields: none. Related fields: bi_pack_ids -> product_id.bi_pack_ids. Original module methods: button_add_product_bundle_bi.
orm_introspection
technical
advanced
wizard.product.bundle.bi
What data can be stored in purchase.order? or What field types are used in purchase.order?
The purchase.order model has 266 fields. Field types distribution: selection: 19, char: 30, datetime: 11, many2one: 49, one2many: 15, text: 5, integer: 19, many2many: 13, float: 21, boolean: 72, binary: 1, monetary: 7, html: 2, date: 2. Computed fields: 117. Field details: priority (selection) [module: purchase]; origin (char) [module: purchase]; partner_ref (char) [module: purchase]; date_approve (datetime) [readonly] [module: purchase]; dest_address_id (many2one) -> res.partner [module: purchase]; order_line (one2many) -> purchase.order.line [module: purchase]; notes (text) [module: purchase]; invoice_count (integer) [readonly] [compute: _compute_invoice] [stored] [module: purchase]; invoice_ids (many2many) [readonly] -> account.move [compute: _compute_invoice] [stored] [module: purchase]; invoice_status (selection) [readonly] [compute: _get_invoiced] [stored] [module: purchase]; date_calendar_start (datetime) [readonly] [compute: _compute_date_calendar_start] [stored] [module: purchase]; fiscal_position_id (many2one) -> account.fiscal.position [module: purchase]; payment_term_id (many2one) -> account.payment.term [module: purchase]; product_id (many2one) -> product.product [compute: <bound method Field._compute_related of purchase.order.product_id>] [not stored] [module: purchase] [related: order_line.product_id] [inverse: <bound method Field._inverse_related of purchase.order.product_id>]; user_id (many2one) -> res.users [module: purchase]; currency_rate (float) [readonly] [compute: _compute_currency_rate] [stored] [module: purchase]; mail_reminder_confirmed (boolean) [readonly] [module: purchase]; mail_reception_confirmed (boolean) [readonly] [module: purchase]; receipt_reminder_email (boolean) [compute: <bound method Field._compute_related of purchase.order.receipt_reminder_email>] [not stored] [module: purchase] [related: partner_id.receipt_reminder_email] [inverse: <bound method Field._inverse_related of purchase.order.receipt_reminder_email>]; reminder_date_before_receipt (integer) [compute: <bound method Field._compute_related of purchase.order.reminder_date_before_receipt>] [not stored] [module: purchase] [related: partner_id.reminder_date_before_receipt] [inverse: <bound method Field._inverse_related of purchase.order.reminder_date_before_receipt>]; team_id (many2one) -> dev.purchase.team [module: dev_purchase_team]; report_grids (boolean) [module: purchase_product_matrix]; grid_product_tmpl_id (many2one) -> product.template [module: purchase_product_matrix]; grid_update (boolean) [module: purchase_product_matrix]; grid (char) [module: purchase_product_matrix]; requisition_id (many2one) -> purchase.requisition [module: purchase_requisition]; is_quantity_copy (selection) [compute: <bound method Field._compute_related of purchase.order.is_quantity_copy>] [not stored] [module: purchase_requisition] [related: requisition_id.is_quantity_copy]; incoterm_id (many2one) -> account.incoterms [module: purchase_stock]; picking_count (integer) [readonly] [compute: _compute_picking] [stored] [module: purchase_stock]; picking_ids (many2many) [readonly] -> stock.picking [compute: _compute_picking] [stored] [module: purchase_stock]; picking_type_id (many2one) [required] -> stock.picking.type [module: purchase_stock]; default_location_dest_id_usage (selection) [readonly] [compute: <bound method Field._compute_related of purchase.order.default_location_dest_id_usage>] [not stored] [module: purchase_stock] [related: picking_type_id.default_location_dest_id.usage]; group_id (many2one) -> procurement.group [module: purchase_stock]; is_shipped (boolean) [readonly] [compute: _compute_is_shipped] [not stored] [module: purchase_stock]; effective_date (datetime) [readonly] [compute: _compute_effective_date] [stored] [module: purchase_stock]; on_time_rate (float) [readonly] [compute: <bound method Field._compute_related of purchase.order.on_time_rate>] [not stored] [module: purchase_stock] [related: partner_id.on_time_rate]; active (boolean) [module: sh_all_in_one_purchase_tools]; complete_state (selection) [readonly] [compute: _compute_complete_check] [not stored] [module: sh_all_in_one_purchase_tools]; custom_checklist_ids (one2many) -> purchase.custom.checklist.line [module: sh_all_in_one_purchase_tools]; custom_checklist (float) [readonly] [compute: _compute_custom_checklist] [not stored] [module: sh_all_in_one_purchase_tools]; product_template_id (many2one) -> purchase.product.template [module: sh_all_in_one_purchase_tools]; digital_sign (binary) [module: sh_all_in_one_purchase_tools]; purchase_show_signature (boolean) [readonly] [compute: <bound method Field._compute_related of purchase.order.purchase_show_signature>] [not stored] [module: sh_all_in_one_purchase_tools] [related: company_id.purchase_show_signature]; chk_sign_confirm (boolean) [readonly] [compute: <bound method Field._compute_related of purchase.order.chk_sign_confirm>] [not stored] [module: sh_all_in_one_purchase_tools] [related: company_id.chk_sign_confirm]; purchase_show_enable_other_sign (boolean) [readonly] [compute: <bound method Field._compute_related of purchase.order.purchase_show_enable_other_sign>] [not stored] [module: sh_all_in_one_purchase_tools] [related: company_id.purchase_enable_other_sign_option]; sign_by (char) [module: sh_all_in_one_purchase_tools]; designation (char) [module: sh_all_in_one_purchase_tools]; sign_on (datetime) [module: sh_all_in_one_purchase_tools]; document_count (integer) [readonly] [compute: _compute_document_count] [not stored] [module: sh_all_in_one_purchase_tools]; order_history_line (one2many) -> purchase.order.history [module: sh_all_in_one_purchase_tools]; order_report_id (many2one) -> sh.report.template [module: sh_all_in_one_purchase_tools]; rfq_report_id (many2one) -> sh.report.template [module: sh_all_in_one_purchase_tools]; purchase_tag_ids (many2many) -> sh.purchase.tags [module: sh_all_in_one_purchase_tools]; purchase_url (text) [module: sh_all_in_one_purchase_tools]; report_token (char) [module: sh_all_in_one_purchase_tools]; text_message (text) [readonly] [compute: _compute_get_message_detail_po] [not stored] [module: sh_all_in_one_purchase_tools]; po_extract_id (many2one) [readonly] -> purchase.order [module: sh_all_in_one_purchase_tools]; po_split_id (many2one) [readonly] -> purchase.order [module: sh_all_in_one_purchase_tools]; po_extract_count (integer) [readonly] [compute: _compute_po_extract_count] [not stored] [module: sh_all_in_one_purchase_tools]; po_split_count (integer) [readonly] [compute: _compute_po_split_count] [not stored] [module: sh_all_in_one_purchase_tools]; sh_fully_ship (boolean) [readonly] [module: sh_po_status]; sh_partially_ship (boolean) [readonly] [module: sh_po_status]; sh_fully_paid (boolean) [readonly] [module: sh_po_status]; sh_partially_paid (boolean) [readonly] [module: sh_po_status]; sh_hidden_compute_field (boolean) [readonly] [compute: _compute_shipment] [not stored] [module: sh_po_status]; agreement_id (many2one) -> purchase.agreement [module: sh_po_tender_management]; cancel_lines (boolean) [readonly] [compute: _compute_cancel_lines] [stored] [module: sh_po_tender_management]; selected_order (boolean) [module: sh_po_tender_management]; sh_msg (char) [readonly] [compute: _compute_sh_msg] [not stored] [module: sh_po_tender_management]; sh_po_number (integer) [module: sh_purchase_revisions]; sh_purchase_order_id (many2one) -> purchase.order [module: sh_purchase_revisions]; sh_revision_po_id (many2many) -> purchase.order [module: sh_purchase_revisions]; po_count (integer) [readonly] [compute: _compute_get_po_count] [not stored] [module: sh_purchase_revisions]; sh_purchase_revision_config (boolean) [readonly] [compute: <bound method Field._compute_related of purchase.order.sh_purchase_revision_config>] [not stored] [module: sh_purchase_revisions] [related: company_id.sh_purchase_revision]; visible_eval (selection) [readonly] [compute: _calculate_eval] [not stored] [module: vendor_evaluation]; mrp_production_count (integer) [readonly] [compute: _compute_mrp_production_count] [not stored] [module: purchase_mrp]; sale_order_count (integer) [readonly] [compute: _compute_sale_order_count] [not stored] [module: sale_purchase]; internal_id (many2one) -> inter.transfer.company [module: bi_inter_company_transfer]; inter_transfer_count (integer) [readonly] [compute: _compute_internal] [stored] [module: bi_inter_company_transfer]; client_order_id (many2one) -> sale.order [module: bi_inter_company_transfer]; discount_method (selection) [module: bi_sale_purchase_discount_with_tax]; discount_amount (float) [module: bi_sale_purchase_discount_with_tax]; discount_amt (monetary) [readonly] [compute: _amount_all] [stored] [module: bi_sale_purchase_discount_with_tax]; discount_amt_line (float) [readonly] [compute: _amount_all] [stored] [module: bi_sale_purchase_discount_with_tax]; merged (boolean) [module: merge_picking]; sh_purchase_barcode_mobile (char) [module: sh_all_in_one_mbs]; sh_purchase_bm_is_cont_scan (char) [readonly] [module: sh_all_in_one_mbs]; sh_sale_order_id (many2one) [readonly] -> sale.order [module: sh_so_po]; apply_manual_currency_exchange (boolean) [module: sr_manual_currency_exchange_rate]; manual_currency_exchange_rate (float) [module: sr_manual_currency_exchange_rate]; active_manual_currency_rate (boolean) [module: sr_manual_currency_exchange_rate]; total_invoices_amount (float) [readonly] [compute: get_purchase_total_invoices_amount] [not stored] [module: dev_purchase_down_payment]; down_payment_by (selection) [module: dev_purchase_down_payment]; amount (float) [module: dev_purchase_down_payment]; dp_journal_id (many2one) -> account.journal [module: dev_purchase_down_payment]; hide_create_bill (boolean) [readonly] [compute: hide_create_bill_status] [not stored] [module: dev_purchase_down_payment]; payment_status (selection) [readonly] [compute: _compute_payment_status] [not stored] [module: dev_purchase_down_payment]; down_payment_amount (float) [readonly] [compute: _compute_down_payment_amount] [stored] [module: dev_purchase_down_payment]; total_down_payment_amount (float) [readonly] [compute: _compute_amount] [stored] [module: dev_purchase_down_payment]; is_down_payment (boolean) [module: dev_purchase_down_payment]; report_template_id1 (many2one) [readonly] -> ir.actions.report [compute: _default_report_template1] [not stored] [module: general_template]; report_template_id (many2one) -> ir.actions.report [module: general_template]; amount_to_text (char) [readonly] [compute: _amount_in_words] [not stored] [module: general_template]; is_vendor_pricelist (boolean) [readonly] [compute: _compute_vendor_pricelist_po] [not stored] [module: equip3_purchase_masterdata]; name (char) [required] [module: equip3_inventory_control]; currency_id (many2one) [required] -> res.currency [module: equip3_purchase_operation]; po_expiry_date (datetime) [module: equip3_purchase_operation]; po (boolean) [module: equip3_purchase_operation]; exp_po (boolean) [module: equip3_purchase_operation]; sent (boolean) [module: equip3_purchase_operation]; is_goods_orders (boolean) [module: equip3_purchase_operation]; is_services_orders (boolean) [module: equip3_purchase_operation]; is_hold_purchase_order (boolean) [readonly] [compute: _compute_hold_purchase_order] [not stored] [module: equip3_purchase_operation]; approval_matrix_id (many2one) [readonly] -> approval.matrix.purchase.order [compute: _compute_approval_matrix_id] [stored] [module: equip3_purchase_operation]; is_approval_matrix (boolean) [readonly] [compute: _compute_approval_matrix] [not stored] [module: equip3_purchase_operation]; state1 (selection) [readonly] [compute: <bound method Field._compute_related of purchase.order.state1>] [not stored] [module: equip3_purchase_operation] [related: state]; po_state (selection) [readonly] [compute: <bound method Field._compute_related of purchase.order.po_state>] [not stored] [module: equip3_purchase_operation] [related: state]; approved_matrix_ids (one2many) [readonly] -> approval.matrix.purchase.order.line [compute: _compute_approving_matrix_lines] [stored] [module: equip3_purchase_operation]; is_approve_button (boolean) [readonly] [compute: _get_approve_button] [not stored] [module: equip3_purchase_operation]; approval_matrix_line_id (many2one) [readonly] -> approval.matrix.purchase.order.line [compute: _get_approve_button] [not stored] [module: equip3_purchase_operation]; analytic_account_group_ids (many2many) -> account.analytic.tag [module: equip3_purchase_operation]; company_id (many2one) [required] [readonly] -> res.company [module: equip3_purchase_operation]; branch_id (many2one) [required] -> res.branch [module: equip3_purchase_operation]; destination_location_id (many2one) -> stock.location [module: equip3_purchase_operation]; is_delivery_receipt (boolean) [module: equip3_purchase_operation]; destination_warehouse_id (many2one) -> stock.warehouse [module: equip3_purchase_operation]; discount_type (selection) [module: equip3_purchase_operation]; is_single_delivery_destination (boolean) [module: equip3_purchase_operation]; analytic_accounting (boolean) [readonly] [compute: get_analytic_accounting] [stored] [module: equip3_purchase_operation]; is_revision_po (boolean) [module: equip3_purchase_operation]; is_revision_created (boolean) [module: equip3_purchase_operation]; revision_order_id (many2one) -> purchase.order [module: equip3_purchase_operation]; custom_checklist_template_ids (many2many) -> purchase.custom.checklist.template [module: equip3_purchase_operation]; readonly_price (boolean) [readonly] [compute: compute_retail] [not stored] [module: equip3_purchase_operation]; timezone_date (char) [readonly] [compute: _compute_timezone_date] [stored] [module: equip3_purchase_operation]; request_partner_id (many2one) -> res.partner [module: equip3_purchase_operation]; date_order_assets (datetime) [module: equip3_purchase_operation]; name2 (char) [readonly] [module: equip3_purchase_operation]; date_order (datetime) [required] [module: equip3_purchase_operation]; milestone_template_id (many2one) -> milestone.contract.template [module: equip3_purchase_operation]; milestone_purchase_ids (one2many) -> milestone.contract.template.purchase [module: equip3_purchase_operation]; is_group_good_services_order (boolean) [readonly] [compute: _compute_is_group_good_services_order] [not stored] [module: equip3_purchase_operation]; have_product_service (boolean) [readonly] [compute: _compute_have_product_service] [not stored] [module: equip3_purchase_operation]; swo_ids (one2many) -> service.work.order [module: equip3_purchase_operation]; swo_count (integer) [readonly] [compute: _compute_swo_count] [not stored] [module: equip3_purchase_operation]; is_taxes (boolean) [readonly] [compute: _compute_taxes] [not stored] [module: equip3_purchase_operation]; actual_progress (char) [readonly] [compute: _compute_swo_progress] [stored] [module: equip3_purchase_operation]; remaining_progress (char) [readonly] [compute: _compute_swo_progress] [stored] [module: equip3_purchase_operation]; progress_paid (float) [readonly] [compute: _compute_swo_progress] [stored] [module: equip3_purchase_operation]; paid_swo (float) [module: equip3_purchase_operation]; partner_invoice_id (many2one) [required] -> res.partner [module: equip3_purchase_operation]; available_partner_invoice_ids (many2many) [readonly] -> res.partner [compute: _compute_available_partner_invoice_ids] [not stored] [module: equip3_purchase_operation]; product_brand_ids (many2many) -> product.brand [module: equip3_purchase_operation]; is_product_brand_filter (boolean) [readonly] [compute: _compute_is_product_brand_filter] [not stored] [module: equip3_purchase_operation]; is_service_work_order (boolean) [readonly] [compute: _compute_is_service_work_order] [not stored] [module: equip3_purchase_operation]; is_purchase_vendor_rating_warning (boolean) [readonly] [compute: _compute_vendor_rating_warning] [not stored] [module: equip3_purchase_operation]; is_product_service_operation_receiving (boolean) [readonly] [compute: _compute_service_receiving] [stored] [module: equip3_purchase_operation]; is_service (boolean) [module: equip3_purchase_operation]; show_analytic_tags (boolean) [readonly] [compute: compute_analytic_tags] [stored] [module: equip3_purchase_operation]; amount_untaxed (monetary) [readonly] [compute: _amount_all] [stored] [module: equip3_purchase_operation]; amount_tax (monetary) [readonly] [compute: _amount_all] [stored] [module: equip3_purchase_operation]; amount_total (monetary) [readonly] [compute: _amount_all] [stored] [module: equip3_purchase_operation]; discount_amt_before (monetary) [readonly] [compute: <bound method Field._compute_related of purchase.order.discount_amt_before>] [stored] [module: equip3_purchase_operation] [related: discount_amt]; discount_amt_line_before (float) [readonly] [compute: <bound method Field._compute_related of purchase.order.discount_amt_line_before>] [stored] [module: equip3_purchase_operation] [related: discount_amt_line]; amount_subtotal (monetary) [readonly] [compute: _amount_all] [stored] [module: equip3_purchase_operation]; tax_discount_policy (char) [module: equip3_purchase_operation]; list_available_products (char) [module: equip3_purchase_operation]; from_purchase_request (boolean) [module: equip3_purchase_operation]; term_condition (many2one) -> term.condition [module: equip3_purchase_operation]; term_condition_box (html) [module: equip3_purchase_operation]; bo_count (integer) [readonly] [compute: _compute_purchase_bo_count] [not stored] [module: equip3_purchase_operation]; blanket_ids (one2many) -> purchase.requisition [module: equip3_purchase_operation]; multilevel_disc (boolean) [readonly] [compute: _compute_multilevel_disc] [not stored] [module: equip3_purchase_operation]; multi_discount (char) [module: equip3_purchase_operation]; vendor_payment_terms (char) [module: equip3_purchase_operation]; service_level_agreement_id (many2one) -> service.level.agreement [module: equip3_purchase_operation]; service_level_agreement_box (html) [module: equip3_purchase_operation]; user_request_ids (many2many) -> res.users [module: equip3_purchase_operation]; vendor_invoice_documents_count (integer) [readonly] [compute: _compute_vendor_invoice_documents_count] [not stored] [module: equip3_purchase_operation]; down_payment_discount_amount (float) [module: equip3_purchase_operation]; tender_scope (selection) [readonly] [compute: <bound method Field._compute_related of purchase.order.tender_scope>] [stored] [module: equip3_purchase_other_operation] [related: agreement_id.tender_scope]; is_submit_quotation (boolean) [module: equip3_purchase_other_operation]; price_rating (char) [readonly] [compute: _compute_price_rating] [not stored] [module: equip3_purchase_other_operation]; not_editable (boolean) [module: equip3_purchase_other_operation]; is_editable (boolean) [module: equip3_purchase_other_operation]; tender_order_line (one2many) -> purchase.order.line [module: equip3_purchase_other_operation]; from_bo (boolean) [module: equip3_purchase_other_operation]; is_btn_approval_matrix (boolean) [readonly] [compute: _compute_btn_approval_matrix] [not stored] [module: equip3_purchase_other_operation]; state (selection) [readonly] [module: equip3_purchase_other_operation]; is_blanket_cancel (boolean) [readonly] [compute: _compute_blanket_cancel] [not stored] [module: equip3_purchase_other_operation]; open_tender (boolean) [module: equip3_purchase_other_operation]; days_to_approve (float) [readonly] [compute: _compute_data] [stored] [module: equip3_purchase_report]; purchase_order_duration_to_confirm (float) [module: equip3_purchase_report]; amount_saved_from_cost_savings (float) [module: equip3_purchase_report]; number_of_successful_cost_savings (float) [module: equip3_purchase_report]; partner_id (many2one) [required] -> res.partner [module: fresh_mod_undomain]; dp (boolean) [module: equip3_purchase_other_operation_cont]; journal_id (many2one) -> account.journal [module: equip3_purchase_other_operation_cont]; name_dp (char) [module: equip3_purchase_other_operation_cont]; direct_approval_matrix_id (many2one) [readonly] -> approval.matrix.direct.purchase [module: equip3_purchase_other_operation_cont]; is_approval_matrix_direct (boolean) [readonly] [compute: _compute_approval_matrix_direct] [not stored] [module: equip3_purchase_other_operation_cont]; approved_matrix_direct_ids (one2many) [readonly] -> approval.matrix.direct.purchase.line [compute: _compute_approving_direct_matrix_lines] [stored] [module: equip3_purchase_other_operation_cont]; approved_matrix_direct_id (many2one) [readonly] -> approval.matrix.direct.purchase.line [compute: _compute_is_approve_button] [not stored] [module: equip3_purchase_other_operation_cont]; state_direct_on (selection) [readonly] [compute: <bound method Field._compute_related of purchase.order.state_direct_on>] [not stored] [module: equip3_purchase_other_operation_cont] [related: state]; state_direct_off (selection) [readonly] [compute: <bound method Field._compute_related of purchase.order.state_direct_off>] [not stored] [module: equip3_purchase_other_operation_cont] [related: state]; is_approve_button_direct (boolean) [readonly] [compute: _compute_is_approve_button] [not stored] [module: equip3_purchase_other_operation_cont]; control (boolean) [module: equip3_purchase_other_operation_cont]; qty_limit (float) [module: equip3_purchase_other_operation_cont]; budget_limit (float) [module: equip3_purchase_other_operation_cont]; is_valid_coupon (boolean) [module: equip3_purchase_promo_coupon]; applied_coupon_ids (one2many) -> coupon.coupon [module: equip3_purchase_promo_coupon]; generated_coupon_ids (one2many) -> coupon.coupon [module: equip3_purchase_promo_coupon]; no_code_promo_program_ids (many2many) -> coupon.program [module: equip3_purchase_promo_coupon]; code_promo_program_id (many2one) -> coupon.program [module: equip3_purchase_promo_coupon]; promo_code (char) [compute: <bound method Field._compute_related of purchase.order.promo_code>] [not stored] [module: equip3_purchase_promo_coupon] [related: code_promo_program_id.promo_code] [inverse: <bound method Field._inverse_related of purchase.order.promo_code>]; client_order_ref (char) [readonly] [compute: _compute_customer_reference] [stored] [module: equip3_sale_purchase]; is_dropship (boolean) [readonly] [module: equip3_sale_purchase]; is_sale_order (boolean) [readonly] [module: equip3_sale_purchase]; customer_partner_id (many2one) [readonly] -> res.partner [module: equip3_sale_purchase]; customer_location_partner_id (many2one) [readonly] -> res.partner [module: equip3_sale_purchase]; branch_ids (many2many) [readonly] -> res.branch [compute: compute_branch_ids] [stored] [module: equip3_sale_purchase]; is_assets_orders (boolean) [module: equip3_purchase_asset]; import_reference (char) [module: import_data_modifier]; is_report_purchaseorder_printed (boolean) [module: allfresh_mod_purchase]; is_report_purchasequotation_printed (boolean) [module: allfresh_mod_purchase]; remark (text) [module: allfresh_mod_purchase]; rfq_type (selection) [module: allfresh_mod_purchase]; discount_promotions_amount (monetary) [module: allfresh_mod_purchase]; date_planned (datetime) [compute: _compute_date_planned] [stored] [module: allfresh_mod_purchase] [inverse: _inverse_date_planned]; persentase_antar_badan (float) [readonly] [compute: <bound method Field._compute_related of purchase.order.persentase_antar_badan>] [not stored] [module: allfresh_mod_purchase] [related: partner_id.persentase_antar_badan]; form_view_opened (boolean) [readonly] [compute: _compute_form_view_opened] [not stored] [module: allfresh_mod_purchase]; 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 purchase.order.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of purchase.order.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of purchase.order.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of purchase.order.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of purchase.order.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 purchase.order.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of purchase.order.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]; 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].
orm_introspection
field_inquiry
basic
purchase.order
How many columns are in x_report_wizard? or What columns does x_report_wizard have?
The x_report_wizard table has 8 columns and 4 foreign key relationships. It stores data related to x report wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.
sql_introspection
structure
basic
x_report_wizard
Show me the column structure of account_move_invoice_printout_editor_rel. or List all columns in account_move_invoice_printout_editor_rel.
Columns in account_move_invoice_printout_editor_rel: invoice_printout_editor_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.
sql_introspection
columns
basic
account_move_invoice_printout_editor_rel
Tell me about the website_sale_payment_acquirer_onboarding_wizard table. or How many columns are in website_sale_payment_acquirer_onboarding_wizard?
The website_sale_payment_acquirer_onboarding_wizard table has 16 columns and 2 foreign key relationships. It stores data related to website sale payment acquirer onboarding wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, character varying: 10, text: 1, timestamp without time zone: 2. Nullable columns: 15, columns with defaults: 1.
sql_introspection
structure
basic
website_sale_payment_acquirer_onboarding_wizard
What computed fields exist in report.eq_scrap_order_report.scrap_order_report? or Show me the fields of report.eq_scrap_order_report.scrap_order_report.
The report.eq_scrap_order_report.scrap_order_report model has 3 fields. Field types distribution: integer: 1, char: 1, datetime: 1. Computed fields: 2. Field details: id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].
orm_introspection
field_inquiry
basic
report.eq_scrap_order_report.scrap_order_report
Describe the product.template.barcode model in Odoo. or Can you explain the purpose of product.template.barcode?
The product.template.barcode model represents Product Barcode in the ERP system. It contains 13 fields and is used to manage product barcode data. Defined in module: sh_product_multi_barcode. Key fields include: product_id, name, product_uom_id, product_uom_category_id, uom_id, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.
orm_introspection
basic_info
basic
product.template.barcode
Tell me about the internal_location_matrix_rel table. or What indexes exist on internal_location_matrix_rel?
The internal_location_matrix_rel table has 2 columns and 2 foreign key relationships. It stores data related to internal location matrix rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.
sql_introspection
structure
basic
internal_location_matrix_rel
What fields are available in print_prenumbered_checks? or What data types are used in print_prenumbered_checks?
Columns in print_prenumbered_checks: id (integer) [NOT NULL] [DEFAULT: nextval('print_prenumbered_checks_id_seq'::regclass)] [PRECISION: 32]; next_check_number (character varying) [NOT NULL] [COMMENT: Next Check Number]; 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.
sql_introspection
columns
basic
print_prenumbered_checks
List all constraint names in acrux_chat_message_wizard. or What relationships exist for acrux_chat_message_wizard?
Foreign keys in acrux_chat_message_wizard: connector_id -> acrux_chat_connector.id [constraint: acrux_chat_message_wizard_connector_id_fkey]; conversation_id -> acrux_chat_conversation.id [constraint: acrux_chat_message_wizard_conversation_id_fkey]; create_uid -> res_users.id [constraint: acrux_chat_message_wizard_create_uid_fkey]; crm_message_mass_id -> crm_send_message_mass.id [constraint: acrux_chat_message_wizard_crm_message_mass_id_fkey]; message_mass_id -> send_message_mass.id [constraint: acrux_chat_message_wizard_message_mass_id_fkey]; opportunity_id -> crm_lead.id [constraint: acrux_chat_message_wizard_opportunity_id_fkey]; partner_id -> res_partner.id [constraint: acrux_chat_message_wizard_partner_id_fkey]; sale_id -> sale_order.id [constraint: acrux_chat_message_wizard_sale_id_fkey]; whatsapp_template_id -> whatsapp_template.id [constraint: acrux_chat_message_wizard_whatsapp_template_id_fkey]; write_uid -> res_users.id [constraint: acrux_chat_message_wizard_write_uid_fkey]. Total foreign key relationships: 10. Referenced tables: crm_send_message_mass, send_message_mass, res_partner, sale_order, acrux_chat_conversation, acrux_chat_connector, res_users, whatsapp_template, crm_lead.
sql_introspection
relationships
intermediate
acrux_chat_message_wizard
List all constraint names in utm_tag_rel. or What relationships exist for utm_tag_rel?
Foreign keys in utm_tag_rel: campaign_id -> utm_tag.id [constraint: utm_tag_rel_campaign_id_fkey]; tag_id -> utm_campaign.id [constraint: utm_tag_rel_tag_id_fkey]. Total foreign key relationships: 2. Referenced tables: utm_tag, utm_campaign.
sql_introspection
relationships
intermediate
utm_tag_rel
How to work with update.qty fields? or How to create records in update.qty?
To use the update.qty model, you need to provide values for required fields: sh_qty. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: sh_qty [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.
orm_introspection
usage
intermediate
update.qty
What fields are readonly in access.rights.profile? or How to create records in access.rights.profile?
To use the access.rights.profile 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.
orm_introspection
usage
intermediate
access.rights.profile
What is the purchase_order_sh_purchase_update_mass_tag_wizard_rel table? or Tell me about the purchase_order_sh_purchase_update_mass_tag_wizard_rel table.
The purchase_order_sh_purchase_update_mass_tag_wizard_rel table has 2 columns and 2 foreign key relationships. It stores data related to purchase order sh purchase update mass tag wizard rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.
sql_introspection
structure
basic
purchase_order_sh_purchase_update_mass_tag_wizard_rel
What are the column types in repair_tags? or What data types are used in repair_tags?
Columns in repair_tags: id (integer) [NOT NULL] [DEFAULT: nextval('repair_tags_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Tag Name]; color (integer) [PRECISION: 32] [COMMENT: Color Index]; 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.
sql_introspection
columns
basic
repair_tags
Describe the field structure of base_import.tests.models.complex. or What fields does base_import.tests.models.complex have?
The base_import.tests.models.complex model has 13 fields. Field types distribution: float: 1, monetary: 1, char: 2, many2one: 3, date: 1, datetime: 4, integer: 1. Computed fields: 2. Field details: f (float) [readonly] [module: base_import]; m (monetary) [readonly] [module: base_import]; c (char) [readonly] [module: base_import]; currency_id (many2one) [readonly] -> res.currency [module: base_import]; d (date) [readonly] [module: base_import]; dt (datetime) [readonly] [module: base_import]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].
orm_introspection
field_inquiry
basic
base_import.tests.models.complex
What business logic is in convert.revenue? or What are common use cases for convert.revenue?
To use the convert.revenue 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.
orm_introspection
usage
intermediate
convert.revenue
Which columns are nullable in restore_lead_type? or Describe the columns of restore_lead_type.
Columns in restore_lead_type: id (integer) [NOT NULL] [DEFAULT: nextval('restore_lead_type_id_seq'::regclass)] [PRECISION: 32]; lead_type_id (integer) [PRECISION: 32] [COMMENT: Lead Type]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 6. Statistics: 5 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
restore_lead_type
Describe the implementation of pos.profit.and.loss. or How is pos.profit.and.loss implemented technically?
The pos.profit.and.loss model is defined in module: equip3_pos_report. It has 3 computed fields: product_uom_id, display_name, __last_update. Stored computed fields: none. Related fields: product_uom_id -> pos_order_line_id.product_uom_id. Original module methods: init.
orm_introspection
technical
advanced
pos.profit.and.loss
Describe the relational structure of vendor_pricelist_approval_matrix. or List all constraint names in vendor_pricelist_approval_matrix.
Foreign keys in vendor_pricelist_approval_matrix: branch_id -> res_branch.id [constraint: vendor_pricelist_approval_matrix_branch_id_fkey]; company_id -> res_company.id [constraint: vendor_pricelist_approval_matrix_company_id_fkey]; create_uid -> res_users.id [constraint: vendor_pricelist_approval_matrix_create_uid_fkey]; created_by -> res_users.id [constraint: vendor_pricelist_approval_matrix_created_by_fkey]; department_id -> hr_department.id [constraint: vendor_pricelist_approval_matrix_department_id_fkey]; write_uid -> res_users.id [constraint: vendor_pricelist_approval_matrix_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: hr_department, res_company, res_users, res_branch.
sql_introspection
relationships
intermediate
vendor_pricelist_approval_matrix
Tell me about the mrp_bom_tools table. or What is stored in mrp_bom_tools?
The mrp_bom_tools table has 13 columns and 9 foreign key relationships. It stores data related to mrp bom tools in the system. The table has 2 indexes for performance optimization. Column types: integer: 10, numeric: 1, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1.
sql_introspection
structure
basic
mrp_bom_tools
Which columns are nullable in account_journal_customer_deposit_rel? or What data types are used in account_journal_customer_deposit_rel?
Columns in account_journal_customer_deposit_rel: customer_deposit_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.
sql_introspection
columns
basic
account_journal_customer_deposit_rel
Describe the columns of account_bank_statement_integrate. or List all columns in account_bank_statement_integrate.
Columns in account_bank_statement_integrate: id (integer) [NOT NULL] [DEFAULT: nextval('account_bank_statement_integrate_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Number]; journal_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Bank Journal]; date_from (date) [NOT NULL] [COMMENT: Start Date]; date_to (date) [NOT NULL] [COMMENT: Date To]; status (character varying) [COMMENT: Status]; created_by (integer) [PRECISION: 32] [COMMENT: Created By]; created_date (date) [COMMENT: Created Date]; 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: 13. Statistics: 9 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
account_bank_statement_integrate
What relationships exist for stock_return_picking_inter_company? or What are the foreign keys in stock_return_picking_inter_company?
Foreign keys in stock_return_picking_inter_company: create_uid -> res_users.id [constraint: stock_return_picking_inter_company_create_uid_fkey]; move_id -> stock_move.id [constraint: stock_return_picking_inter_company_move_id_fkey]; product_id -> product_product.id [constraint: stock_return_picking_inter_company_product_id_fkey]; wizard_id -> return_inter_transfer_company.id [constraint: stock_return_picking_inter_company_wizard_id_fkey]; write_uid -> res_users.id [constraint: stock_return_picking_inter_company_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: product_product, return_inter_transfer_company, stock_move, res_users.
sql_introspection
relationships
intermediate
stock_return_picking_inter_company
What are the column types in website_visitor? or What fields are available in website_visitor?
Columns in website_visitor: id (integer) [NOT NULL] [DEFAULT: nextval('website_visitor_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Name]; access_token (character varying) [NOT NULL] [COMMENT: Access Token]; active (boolean) [COMMENT: Active]; website_id (integer) [PRECISION: 32] [COMMENT: Website]; partner_id (integer) [PRECISION: 32] [COMMENT: Linked Partner]; country_id (integer) [PRECISION: 32] [COMMENT: Country]; lang_id (integer) [PRECISION: 32] [COMMENT: Language]; timezone (character varying) [COMMENT: Timezone]; visit_count (integer) [PRECISION: 32] [COMMENT: Number of visits]; create_date (timestamp without time zone) [COMMENT: First connection date]; last_connection_datetime (timestamp without time zone) [COMMENT: Last Connection]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; livechat_operator_id (integer) [PRECISION: 32] [COMMENT: Speaking with]. Total columns: 16. Statistics: 14 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
website_visitor
Describe the many2many relations for account.balance.report. or What foreign keys exist in account.balance.report?
The account.balance.report model has 5 relational fields: journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: journal_ids. One2many fields: none.
orm_introspection
relationship
intermediate
account.balance.report
What relationships exist for account_reconcile_model_line? or Describe the relational structure of account_reconcile_model_line.
Foreign keys in account_reconcile_model_line: account_id -> account_account.id [constraint: account_reconcile_model_line_account_id_fkey]; analytic_account_id -> account_analytic_account.id [constraint: account_reconcile_model_line_analytic_account_id_fkey]; company_id -> res_company.id [constraint: account_reconcile_model_line_company_id_fkey]; create_uid -> res_users.id [constraint: account_reconcile_model_line_create_uid_fkey]; journal_id -> account_journal.id [constraint: account_reconcile_model_line_journal_id_fkey]; model_id -> account_reconcile_model.id [constraint: account_reconcile_model_line_model_id_fkey]; write_uid -> res_users.id [constraint: account_reconcile_model_line_write_uid_fkey]. Total foreign key relationships: 7. Referenced tables: account_reconcile_model, res_company, account_account, res_users, account_analytic_account, account_journal.
sql_introspection
relationships
intermediate
account_reconcile_model_line
What foreign keys exist in website? or How does website relate to other models?
The website model has 24 relational fields: country_group_ids -> res.country.group; company_id -> res.company; language_ids -> res.lang; default_lang_id -> res.lang; user_id -> res.users; partner_id -> res.partner; menu_id -> website.menu; homepage_id -> website.page; theme_id -> ir.module.module; channel_id -> im_livechat.channel; user_ids -> res.users; crm_default_team_id -> crm.team; crm_default_user_id -> res.users; pricelist_id -> product.pricelist; currency_id -> res.currency; salesperson_id -> res.users; salesteam_id -> crm.team; pricelist_ids -> product.pricelist; all_pricelist_ids -> product.pricelist; cart_recovery_mail_template_id -> mail.template; shop_extra_field_ids -> website.sale.extra.field; warehouse_id -> stock.warehouse; create_uid -> res.users; write_uid -> res.users. Many2many fields: country_group_ids, language_ids, user_ids. One2many fields: pricelist_ids, all_pricelist_ids, shop_extra_field_ids.
orm_introspection
relationship
intermediate
website
What is the account.deposit.reconcile model? or What does the account.deposit.reconcile model represent?
The account.deposit.reconcile model represents account.deposit.reconcile in the ERP system. It contains 9 fields and is used to manage account.deposit.reconcile data. Defined in module: equip3_accounting_deposit. Key fields include: date, allocation_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.
orm_introspection
basic_info
basic
account.deposit.reconcile
What fields are available in ir_demo_failure_wizard? or Which columns are nullable in ir_demo_failure_wizard?
Columns in ir_demo_failure_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('ir_demo_failure_wizard_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.
sql_introspection
columns
basic
ir_demo_failure_wizard
List all fields in the account.aged.trial.balance model. or What fields does account.aged.trial.balance have?
The account.aged.trial.balance model has 15 fields. Field types distribution: integer: 2, many2many: 1, date: 2, selection: 2, many2one: 4, char: 1, datetime: 3. Computed fields: 2. Field details: period_length (integer) [required] [module: accounting_pdf_reports]; journal_ids (many2many) [required] -> account.journal [module: accounting_pdf_reports]; date_from (date) [module: accounting_pdf_reports]; result_selection (selection) [required] [module: accounting_pdf_reports]; date_to (date) [module: account]; target_move (selection) [required] [module: account]; report_currency_id (many2one) -> res.currency [module: equip3_accounting_reports]; company_id (many2one) [required] -> res.company [module: equip3_accounting_reports]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].
orm_introspection
field_inquiry
basic
account.aged.trial.balance
What are the length constraints in account_resequence_wizard? or What columns have default values in account_resequence_wizard?
Columns in account_resequence_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('account_resequence_wizard_id_seq'::regclass)] [PRECISION: 32]; first_date (date) [COMMENT: First Date]; end_date (date) [COMMENT: End Date]; first_name (character varying) [NOT NULL] [COMMENT: First New Sequence]; ordering (character varying) [NOT NULL] [COMMENT: Ordering]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
account_resequence_wizard
What is the pos_account_cashbox_line table? or Explain the pos_account_cashbox_line table schema.
The pos_account_cashbox_line table has 8 columns and 3 foreign key relationships. It stores data related to pos account cashbox line in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, numeric: 1, timestamp without time zone: 2. Nullable columns: 6, columns with defaults: 1.
sql_introspection
structure
basic
pos_account_cashbox_line
Explain the bi_product_pack table schema. or Describe the bi_product_pack table structure.
The bi_product_pack table has 8 columns and 4 foreign key relationships. It stores data related to bi product pack in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, double precision: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1.
sql_introspection
structure
basic
bi_product_pack
Show me the relational structure of pos.voucher.report. or What foreign keys exist in pos.voucher.report?
The pos.voucher.report model has 5 relational fields: pos_order_id -> pos.order; config_id -> pos.config; session_id -> pos.session; pos_branch_id -> res.branch; company_id -> res.company. Many2many fields: none. One2many fields: none.
orm_introspection
relationship
intermediate
pos.voucher.report
What business logic is in pos.generate.efaktur? or What fields are readonly in pos.generate.efaktur?
To use the pos.generate.efaktur model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required] [has_default] [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.
orm_introspection
usage
intermediate
pos.generate.efaktur
How to create records in internal.transfer? or What business logic is in internal.transfer?
To use the internal.transfer model, you need to provide values for required fields: requested_by, scheduled_date. Readonly fields: name, source_document, state1, state2, state3, operation_type_in_id, operation_type_out_id, operation_count, internal_transfer_line_total, itr_approval_matrix_id, is_itr_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, is_reset_to_draft, is_product_lines, company_id, filter_source_warehouse_id, filter_destination_warehouse_id, get_warehouse, is_mbs_on_transfer_operations, branch_id, domain_warehouse_source_id, domain_warehouse_destination_id, sh_it_bm_is_cont_scan, source_location_id, destination_location_id, create_date, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, write_uid, write_date, __last_update. Field usage details: name [readonly] [has_default]; source_document [readonly]; state1 [readonly] [computed] [no_copy]; state2 [readonly] [computed] [no_copy]; state3 [readonly] [computed] [no_copy]; operation_type_in_id [readonly]; operation_type_out_id [readonly]; operation_count [readonly] [computed] [no_copy]; internal_transfer_line_total [readonly] [computed] [no_copy]; itr_approval_matrix_id [readonly] [computed] [no_copy]; is_itr_approval_matrix [readonly] [computed] [no_copy]; approved_matrix_ids [readonly] [computed] [no_copy]; approval_matrix_line_id [readonly] [computed] [no_copy]; is_approve_button [readonly] [computed] [no_copy]; is_reset_to_draft [readonly] [computed] [no_copy]; is_product_lines [readonly] [computed] [no_copy]; company_id [readonly] [computed] [no_copy]; filter_source_warehouse_id [readonly] [computed] [no_copy]; filter_destination_warehouse_id [readonly] [computed] [no_copy]; requested_by [required] [has_default]; get_warehouse [readonly] [computed] [no_copy]; is_mbs_on_transfer_operations [readonly] [computed] [no_copy]; branch_id [readonly] [computed] [has_default] [has_states] [no_copy]; domain_warehouse_source_id [readonly] [computed] [no_copy]; domain_warehouse_destination_id [readonly] [computed] [no_copy]; sh_it_bm_is_cont_scan [readonly] [has_default]; source_location_id [readonly] [computed] [no_copy]; destination_location_id [readonly] [computed] [no_copy]; scheduled_date [required] [has_default]; create_date [readonly] [has_default]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; access_url [readonly] [computed] [no_copy]; access_warning [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.
orm_introspection
usage
intermediate
internal.transfer
What operations can I perform on ir.default? or What are common use cases for ir.default?
To use the ir.default model, you need to provide values for required fields: field_id, json_value. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: field_id [required]; json_value [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.
orm_introspection
usage
intermediate
ir.default
How does accounting_flow_wizard relate to other tables? or What tables are connected to accounting_flow_wizard?
Foreign keys in accounting_flow_wizard: create_uid -> res_users.id [constraint: accounting_flow_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: accounting_flow_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.
sql_introspection
relationships
intermediate
accounting_flow_wizard
What columns have default values in account_analytic_tag_invoice_recurring_rel? or What are the length constraints in account_analytic_tag_invoice_recurring_rel?
Columns in account_analytic_tag_invoice_recurring_rel: invoice_recurring_id (integer) [NOT NULL] [PRECISION: 32]; account_analytic_tag_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.
sql_introspection
columns
basic
account_analytic_tag_invoice_recurring_rel
What are the foreign keys in sh_fiscal_year? or What tables does sh_fiscal_year reference?
Foreign keys in sh_fiscal_year: branch_id -> res_branch.id [constraint: sh_fiscal_year_branch_id_fkey]; company_id -> res_company.id [constraint: sh_fiscal_year_company_id_fkey]; create_uid -> res_users.id [constraint: sh_fiscal_year_create_uid_fkey]; move_id -> account_move.id [constraint: sh_fiscal_year_move_id_fkey]; summary_move_id -> account_move.id [constraint: sh_fiscal_year_summary_move_id_fkey]; write_uid -> res_users.id [constraint: sh_fiscal_year_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: res_company, res_users, account_move, res_branch.
sql_introspection
relationships
intermediate
sh_fiscal_year
What are the foreign keys in account_report_partner_ledger? or What tables does account_report_partner_ledger reference?
Foreign keys in account_report_partner_ledger: company_id -> res_company.id [constraint: account_report_partner_ledger_company_id_fkey]; create_uid -> res_users.id [constraint: account_report_partner_ledger_create_uid_fkey]; report_currency_id -> res_currency.id [constraint: account_report_partner_ledger_report_currency_id_fkey]; write_uid -> res_users.id [constraint: account_report_partner_ledger_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_currency, res_users, res_company.
sql_introspection
relationships
intermediate
account_report_partner_ledger
What operations can I perform on account.common.account.report? or What fields are readonly in account.common.account.report?
To use the account.common.account.report model, you need to provide values for required fields: display_account, journal_ids, target_move, company_id. Readonly fields: display_account, journal_ids, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: display_account [required] [readonly] [has_default]; journal_ids [required] [readonly] [has_default]; date_from [readonly]; date_to [readonly]; target_move [required] [readonly] [has_default]; report_currency_id [readonly]; company_id [required] [readonly] [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.
orm_introspection
usage
intermediate
account.common.account.report
How to create records in analytic.sale.order.line? or What business logic is in analytic.sale.order.line?
To use the analytic.sale.order.line model, you need to provide values for required fields: product_id, product_uom_qty, product_uom. Readonly fields: name, product_uom, price_subtotal, price_tax, price_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [readonly] [computed] [no_copy]; product_id [required]; product_uom_qty [required] [has_default]; product_uom [required] [readonly] [computed] [no_copy]; price_subtotal [readonly] [computed] [no_copy]; price_tax [readonly] [computed] [no_copy]; price_total [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.
orm_introspection
usage
intermediate
analytic.sale.order.line
What fields are available in sale_order_repair? or Describe the columns of sale_order_repair.
Columns in sale_order_repair: id (integer) [NOT NULL] [DEFAULT: nextval('sale_order_repair_id_seq'::regclass)] [PRECISION: 32]; repair_type (character varying) [COMMENT: Repair Type]; is_return_required (boolean) [COMMENT: Return the repaired parts ]; return_sale_order_id (integer) [PRECISION: 32] [COMMENT: Return Sale Order]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
sale_order_repair
List all fields in the approval.reject model. or What field types are used in approval.reject?
The approval.reject model has 8 fields. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: reason (text) [required] [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].
orm_introspection
field_inquiry
basic
approval.reject
What are the foreign keys in purchase_target_based_on_target_kpi_rel? or Describe the relational structure of purchase_target_based_on_target_kpi_rel.
Foreign keys in purchase_target_based_on_target_kpi_rel: purchase_target_based_on_id -> purchase_target_based_on.id [constraint: purchase_target_based_on_targe_purchase_target_based_on_id_fkey]; target_kpi_id -> target_kpi.id [constraint: purchase_target_based_on_target_kpi_rel_target_kpi_id_fkey]. Total foreign key relationships: 2. Referenced tables: purchase_target_based_on, target_kpi.
sql_introspection
relationships
intermediate
purchase_target_based_on_target_kpi_rel
How to work with sh.base.send.whatsapp.number.wizard fields? or What business logic is in sh.base.send.whatsapp.number.wizard?
To use the sh.base.send.whatsapp.number.wizard model, you need to provide values for required fields: whatsapp_mobile, message. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: whatsapp_mobile [required]; message [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.
orm_introspection
usage
intermediate
sh.base.send.whatsapp.number.wizard
Explain the account_analytic_tag_purchase_requisition_line_rel table schema. or What columns does account_analytic_tag_purchase_requisition_line_rel have?
The account_analytic_tag_purchase_requisition_line_rel table has 2 columns and 2 foreign key relationships. It stores data related to account analytic tag purchase requisition line rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.
sql_introspection
structure
basic
account_analytic_tag_purchase_requisition_line_rel
What tables are connected to locattion_matrix_rel_id? or What tables does locattion_matrix_rel_id reference?
Foreign keys in locattion_matrix_rel_id: loc_id -> rn_approval_matrix.id [constraint: locattion_matrix_rel_id_loc_id_fkey]; stock_location_id -> stock_location.id [constraint: locattion_matrix_rel_id_stock_location_id_fkey]. Total foreign key relationships: 2. Referenced tables: rn_approval_matrix, stock_location.
sql_introspection
relationships
intermediate
locattion_matrix_rel_id
Show me the fields of account.tax.template. or List all fields in the account.tax.template model.
The account.tax.template model has 25 fields. Field types distribution: many2one: 5, selection: 4, boolean: 4, many2many: 1, integer: 2, float: 1, one2many: 2, char: 3, datetime: 3. Computed fields: 2. Field details: chart_template_id (many2one) [required] -> account.chart.template [module: account]; type_tax_use (selection) [required] [module: account]; tax_scope (selection) [module: account]; amount_type (selection) [required] [module: account]; active (boolean) [module: account]; children_tax_ids (many2many) -> account.tax.template [module: account]; sequence (integer) [required] [module: account]; amount (float) [required] [module: account]; price_include (boolean) [module: account]; include_base_amount (boolean) [module: account]; analytic (boolean) [module: account]; invoice_repartition_line_ids (one2many) -> account.tax.repartition.line.template [module: account]; refund_repartition_line_ids (one2many) -> account.tax.repartition.line.template [module: account]; tax_group_id (many2one) -> account.tax.group [module: account]; tax_exigibility (selection) [module: account]; cash_basis_transition_account_id (many2one) -> account.account.template [module: account]; name (char) [required] [module: l10n_multilang]; description (char) [module: l10n_multilang]; 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].
orm_introspection
field_inquiry
basic
account.tax.template
What computed fields exist in account.user.reminder.lines? or Describe the field structure of account.user.reminder.lines.
The account.user.reminder.lines model has 11 fields. Field types distribution: many2one: 3, many2many: 1, integer: 3, char: 1, datetime: 3. Computed fields: 3. Field details: account_line_id (many2one) -> account.user.reminder [module: equip3_accounting_masterdata]; user_ids (many2many) [required] -> res.users [module: equip3_accounting_masterdata]; sequence (integer) [module: equip3_accounting_masterdata]; sequence2 (integer) [readonly] [compute: <bound method Field._compute_related of account.user.reminder.lines.sequence2>] [stored] [module: equip3_accounting_masterdata] [related: sequence]; 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].
orm_introspection
field_inquiry
basic
account.user.reminder.lines
Describe the many2many relations for calendar.attendee. or What are the relationships in calendar.attendee?
The calendar.attendee model has 5 relational fields: event_id -> calendar.event; partner_id -> res.partner; recurrence_id -> calendar.recurrence; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.
orm_introspection
relationship
intermediate
calendar.attendee
What models are connected to ks.sales.forecast.result? or How does ks.sales.forecast.result relate to other models?
The ks.sales.forecast.result model has 5 relational fields: ks_forecast_id -> ks.sales.forecast; ks_product_id -> product.product; ks_partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.
orm_introspection
relationship
intermediate
ks.sales.forecast.result
How is mail.followers used in the system? or Tell me about the mail.followers model.
The mail.followers model represents Document Followers in the ERP system. It contains 11 fields and is used to manage document followers data. Defined in module: mail. Key fields include: res_model, res_id, partner_id, channel_id, subtype_ids, name, email, is_active, id, display_name, __last_update.
orm_introspection
basic_info
basic
mail.followers
List all constraint names in assign_pr_wizard_purchase_request_line_rel. or What tables does assign_pr_wizard_purchase_request_line_rel reference?
Foreign keys in assign_pr_wizard_purchase_request_line_rel: assign_pr_wizard_id -> assign_pr_wizard.id [constraint: assign_pr_wizard_purchase_request_line_assign_pr_wizard_id_fkey]; purchase_request_line_id -> purchase_request_line.id [constraint: assign_pr_wizard_purchase_request_purchase_request_line_id_fkey]. Total foreign key relationships: 2. Referenced tables: purchase_request_line, assign_pr_wizard.
sql_introspection
relationships
intermediate
assign_pr_wizard_purchase_request_line_rel
How do I use the itr.approval.matrix model? or What operations can I perform on itr.approval.matrix?
To use the itr.approval.matrix model, you need to provide values for required fields: name, company_id, warehouse_id. Readonly fields: company_id, approval_line_count, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; company_id [required] [readonly] [has_default]; warehouse_id [required]; approval_line_count [readonly] [computed] [no_copy]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; access_url [readonly] [computed] [no_copy]; access_warning [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.
orm_introspection
usage
intermediate
itr.approval.matrix
List all columns in pos_generate_efaktur_invoice. or What fields are available in pos_generate_efaktur_invoice?
Columns in pos_generate_efaktur_invoice: id (integer) [NOT NULL] [DEFAULT: nextval('pos_generate_efaktur_invoice_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]; gen_efaktur_id (integer) [PRECISION: 32] [COMMENT: Generate E-Faktur]; partner_id (integer) [PRECISION: 32] [COMMENT: Member]; account_move_id (integer) [PRECISION: 32] [COMMENT: Invoice]. Total columns: 8. Statistics: 7 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
pos_generate_efaktur_invoice
What computed fields exist in snailmail.letter.format.error? or What data can be stored in snailmail.letter.format.error?
The snailmail.letter.format.error model has 9 fields. Field types distribution: many2one: 3, boolean: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: message_id (many2one) -> mail.message [module: snailmail]; snailmail_cover (boolean) [module: snailmail]; 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].
orm_introspection
field_inquiry
basic
snailmail.letter.format.error
What are common use cases for sh.pwa.config? or What fields are readonly in sh.pwa.config?
To use the sh.pwa.config model, you need to provide values for required fields: name, short_name, display. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required] [has_default]; short_name [required] [has_default]; display [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.
orm_introspection
usage
intermediate
sh.pwa.config
Show me the column structure of do_matrix_reject. or What columns have default values in do_matrix_reject?
Columns in do_matrix_reject: id (integer) [NOT NULL] [DEFAULT: nextval('do_matrix_reject_id_seq'::regclass)] [PRECISION: 32]; reason (text) [COMMENT: Reason]; 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: 5 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
do_matrix_reject
List all relational fields in reset.view.arch.wizard. or What one2many fields are in reset.view.arch.wizard?
The reset.view.arch.wizard model has 4 relational fields: view_id -> ir.ui.view; compare_view_id -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.
orm_introspection
relationship
intermediate
reset.view.arch.wizard
What modules define pos.cashbox.history? or Which fields in pos.cashbox.history are computed?
The pos.cashbox.history model is defined in module: equip3_pos_cashbox. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: save_balance_history.
orm_introspection
technical
advanced
pos.cashbox.history
What is stored in cust_deposit_history_rel? or Tell me about the cust_deposit_history_rel table.
The cust_deposit_history_rel table has 2 columns and 2 foreign key relationships. It stores data related to cust deposit history rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.
sql_introspection
structure
basic
cust_deposit_history_rel
What are the column types in theme_ir_ui_view? or List all columns in theme_ir_ui_view.
Columns in theme_ir_ui_view: id (integer) [NOT NULL] [DEFAULT: nextval('theme_ir_ui_view_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; key (character varying) [COMMENT: Key]; type (character varying) [COMMENT: Type]; priority (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Priority]; mode (character varying) [COMMENT: Mode]; active (boolean) [COMMENT: Active]; arch (text) [COMMENT: Arch]; arch_fs (character varying) [COMMENT: Arch Fs]; inherit_id (character varying) [COMMENT: Inherit]; customize_show (boolean) [COMMENT: Customize Show]; 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: 15. Statistics: 12 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
theme_ir_ui_view
What operations can I perform on crm.lead2opportunity.partner? or What are common use cases for crm.lead2opportunity.partner?
To use the crm.lead2opportunity.partner model, you need to provide values for required fields: lead_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [computed]; action [computed]; lead_id [required]; duplicated_lead_ids [computed]; partner_id [computed]; user_id [computed]; team_id [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.
orm_introspection
usage
intermediate
crm.lead2opportunity.partner
List all columns in project_project. or What are the column types in project_project?
Columns in project_project: id (integer) [NOT NULL] [DEFAULT: nextval('project_project_id_seq'::regclass)] [PRECISION: 32]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; access_token (character varying) [COMMENT: Security Token]; name (character varying) [NOT NULL] [COMMENT: Name]; description (text) [COMMENT: Description]; active (boolean) [COMMENT: Active]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; partner_id (integer) [PRECISION: 32] [COMMENT: Customer]; partner_email (character varying) [COMMENT: Email]; partner_phone (character varying) [COMMENT: Phone]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; analytic_account_id (integer) [PRECISION: 32] [COMMENT: Analytic Account]; label_tasks (character varying) [COMMENT: Use Tasks as]; color (integer) [PRECISION: 32] [COMMENT: Color Index]; user_id (integer) [PRECISION: 32] [COMMENT: Project Manager]; alias_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Alias]; privacy_visibility (character varying) [NOT NULL] [COMMENT: Visibility]; date_start (date) [COMMENT: Start Date]; date (date) [COMMENT: Expiration Date]; subtask_project_id (integer) [PRECISION: 32] [COMMENT: Sub-task Project]; allow_subtasks (boolean) [COMMENT: Sub-tasks]; allow_recurring_tasks (boolean) [COMMENT: Recurring Tasks]; rating_request_deadline (timestamp without time zone) [COMMENT: Rating Request Deadline]; rating_active (boolean) [COMMENT: Customer Ratings]; rating_status (character varying) [NOT NULL] [COMMENT: Customer Ratings Status]; rating_status_period (character varying) [NOT NULL] [COMMENT: Rating Frequency]; 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]; allow_timesheets (boolean) [COMMENT: Timesheets]; sale_line_id (integer) [PRECISION: 32] [COMMENT: Sales Order Item]; sale_order_id (integer) [PRECISION: 32] [COMMENT: Sales Order]; bill_type (character varying) [COMMENT: Invoice Tasks to]; pricing_type (character varying) [COMMENT: Pricing]; allow_billable (boolean) [COMMENT: Billable]; timesheet_product_id (integer) [PRECISION: 32] [COMMENT: Timesheet Product]. Total columns: 37. Statistics: 30 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
project_project
What operations can I perform on pos.payment.method.key? or What business logic is in pos.payment.method.key?
To use the pos.payment.method.key 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.
orm_introspection
usage
intermediate
pos.payment.method.key
What are the relationships in mrp.workorder? or What one2many fields are in mrp.workorder?
The mrp.workorder model has 28 relational fields: workcenter_id -> mrp.workcenter; product_id -> product.product; product_uom_id -> uom.uom; production_id -> mrp.production; production_bom_id -> mrp.bom; company_id -> res.company; leave_id -> resource.calendar.leaves; operation_id -> mrp.routing.workcenter; move_raw_ids -> stock.move; move_finished_ids -> stock.move; move_line_ids -> stock.move.line; finished_lot_id -> stock.production.lot; time_ids -> mrp.workcenter.productivity; working_user_ids -> res.users; last_working_user_id -> res.users; next_work_order_id -> mrp.workorder; scrap_ids -> stock.scrap; sh_mrp_workorder_quality_check_ids -> sh.mrp.quality.check; sh_mrp_workorder_quality_alert_ids -> sh.mrp.quality.alert; sh_mrp_workorder_pass_fail_ids -> sh.mrp.pass.fail; sh_mrp_workorder_pics_ids -> sh.mrp.pics; sh_mrp_workorder_measurement_ids -> sh.mrp.measurement; sh_mrp_workorder_qc_measurement_ids -> sh.mrp.qc.measurement; sh_workorder_quality_point_id -> sh.qc.point; attachment_ids -> ir.attachment; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids. One2many fields: move_raw_ids, move_finished_ids, move_line_ids, time_ids, working_user_ids, last_working_user_id, scrap_ids, sh_mrp_workorder_quality_check_ids, sh_mrp_workorder_quality_alert_ids, sh_mrp_workorder_pass_fail_ids, sh_mrp_workorder_pics_ids, sh_mrp_workorder_measurement_ids, sh_mrp_workorder_qc_measurement_ids.
orm_introspection
relationship
intermediate
mrp.workorder
What business logic is in website.seo.metadata? or How to query website.seo.metadata data?
To use the website.seo.metadata model, you need to provide values for required fields: none. Readonly fields: is_seo_optimized, id, display_name, __last_update. Field usage details: is_seo_optimized [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.
orm_introspection
usage
intermediate
website.seo.metadata
Describe the columns of ks_message_wizard. or What are the column types in ks_message_wizard?
Columns in ks_message_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('ks_message_wizard_id_seq'::regclass)] [PRECISION: 32]; name (text) [COMMENT: Message]; 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: 5 nullable, 1 with defaults, 0 with length constraints.
sql_introspection
columns
basic
ks_message_wizard
What are the length constraints in pos_category_branch_rel? or Show me the column structure of pos_category_branch_rel.
Columns in pos_category_branch_rel: categ_id (integer) [NOT NULL] [PRECISION: 32]; branch_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints.
sql_introspection
columns
basic
pos_category_branch_rel
Which fields are required in product.attribute.custom.value? or What computed fields exist in product.attribute.custom.value?
The product.attribute.custom.value model has 11 fields. Field types distribution: char: 3, many2one: 4, integer: 1, datetime: 3. Computed fields: 3. Field details: name (char) [readonly] [compute: _compute_name] [not stored] [module: product]; custom_product_template_attribute_value_id (many2one) [required] -> product.template.attribute.value [module: product]; custom_value (char) [module: product]; sale_order_line_id (many2one) [required] -> sale.order.line [module: sale]; 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].
orm_introspection
field_inquiry
basic
product.attribute.custom.value
What modules define cancel.tender.memory? or What is the module hierarchy for cancel.tender.memory?
The cancel.tender.memory model is defined in module: equip3_purchase_other_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_cancel_tender.
orm_introspection
technical
advanced
cancel.tender.memory
How does setu_inventory_xyz_analysis_bi_report relate to other tables? or Describe the relational structure of setu_inventory_xyz_analysis_bi_report.
Foreign keys in setu_inventory_xyz_analysis_bi_report: company_id -> res_company.id [constraint: setu_inventory_xyz_analysis_bi_report_company_id_fkey]; create_uid -> res_users.id [constraint: setu_inventory_xyz_analysis_bi_report_create_uid_fkey]; product_category_id -> product_category.id [constraint: setu_inventory_xyz_analysis_bi_report_product_category_id_fkey]; product_id -> product_product.id [constraint: setu_inventory_xyz_analysis_bi_report_product_id_fkey]; wizard_id -> setu_inventory_xyz_analysis_report.id [constraint: setu_inventory_xyz_analysis_bi_report_wizard_id_fkey]; write_uid -> res_users.id [constraint: setu_inventory_xyz_analysis_bi_report_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: product_product, product_category, res_company, res_users, setu_inventory_xyz_analysis_report.
sql_introspection
relationships
intermediate
setu_inventory_xyz_analysis_bi_report
How to query stock.warehouse.orderpoint data? or What fields are readonly in stock.warehouse.orderpoint?
To use the stock.warehouse.orderpoint model, you need to provide values for required fields: product_id, product_min_qty, product_max_qty, qty_multiple, name, trigger, company_id, warehouse_id. Readonly fields: product_tmpl_id, product_category_id, product_uom, product_uom_name, allowed_location_ids, rule_ids, json_lead_days_popover, lead_days_date, allowed_route_ids, qty_on_hand, qty_forecast, show_bom, show_supplier, name, branch_id, average_quantity_last_year, lead_days_last_year, average_quantity_run_rate_days, lead_days_run_rate_days, company_id, filter_warehouse_id, pr_status, rfq_status, itr_status, mr_status, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: product_tmpl_id [readonly] [computed] [no_copy]; product_id [required]; product_category_id [readonly] [computed] [no_copy]; product_uom [readonly] [computed] [no_copy]; product_uom_name [readonly] [computed] [no_copy]; product_min_qty [required] [has_default]; product_max_qty [required] [has_default]; qty_multiple [required] [has_default]; allowed_location_ids [readonly] [computed] [no_copy]; rule_ids [readonly] [computed] [no_copy]; json_lead_days_popover [readonly] [computed] [no_copy]; lead_days_date [readonly] [computed] [no_copy]; allowed_route_ids [readonly] [computed] [no_copy]; qty_on_hand [readonly] [computed] [no_copy]; qty_forecast [readonly] [computed] [no_copy]; qty_to_order [computed]; show_bom [readonly] [computed] [no_copy]; show_supplier [readonly] [computed] [no_copy]; name [required] [readonly] [has_default] [no_copy]; trigger [required] [has_default]; branch_id [readonly] [computed] [no_copy]; average_quantity_last_year [readonly] [computed] [no_copy]; lead_days_last_year [readonly] [computed] [no_copy]; average_quantity_run_rate_days [readonly] [computed] [no_copy]; lead_days_run_rate_days [readonly] [computed] [no_copy]; company_id [required] [readonly] [has_default]; warehouse_id [required]; filter_warehouse_id [readonly] [computed] [no_copy]; pr_status [readonly] [computed] [no_copy]; rfq_status [readonly] [computed] [no_copy]; itr_status [readonly] [computed] [no_copy]; mr_status [readonly] [computed] [no_copy]; quantity_restock [computed] [no_copy]; activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; access_url [readonly] [computed] [no_copy]; access_warning [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.
orm_introspection
usage
intermediate
stock.warehouse.orderpoint
What modules define report.equip3_pos_report.report_pos_payment? or What methods are available in report.equip3_pos_report.report_pos_payment?
The report.equip3_pos_report.report_pos_payment model is defined in module: equip3_pos_report. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _get_report_values.
orm_introspection
technical
advanced
report.equip3_pos_report.report_pos_payment
Show me the foreign key constraints of product_template_attribute_line. or Describe the relational structure of product_template_attribute_line.
Foreign keys in product_template_attribute_line: attribute_id -> product_attribute.id [constraint: product_template_attribute_line_attribute_id_fkey]; create_uid -> res_users.id [constraint: product_template_attribute_line_create_uid_fkey]; product_tmpl_id -> product_template.id [constraint: product_template_attribute_line_product_tmpl_id_fkey]; write_uid -> res_users.id [constraint: product_template_attribute_line_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_users, product_attribute, product_template.
sql_introspection
relationships
intermediate
product_template_attribute_line
What indexes exist on stock_inventory_wizard_line? or Tell me about the stock_inventory_wizard_line table.
The stock_inventory_wizard_line table has 20 columns and 9 foreign key relationships. It stores data related to stock inventory wizard line in the system. The table has 1 indexes for performance optimization. Column types: integer: 11, character varying: 2, double precision: 3, boolean: 2, timestamp without time zone: 2. Nullable columns: 19, columns with defaults: 1.
sql_introspection
structure
basic
stock_inventory_wizard_line
What are the technical details of pos.promotion.tebus.murah? or How is pos.promotion.tebus.murah implemented technically?
The pos.promotion.tebus.murah model is defined in module: equip3_pos_masterdata. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: create, write.
orm_introspection
technical
advanced
pos.promotion.tebus.murah
What are the foreign keys in website_track? or List all constraint names in website_track.
Foreign keys in website_track: page_id -> website_page.id [constraint: website_track_page_id_fkey]; product_id -> product_product.id [constraint: website_track_product_id_fkey]; visitor_id -> website_visitor.id [constraint: website_track_visitor_id_fkey]. Total foreign key relationships: 3. Referenced tables: product_product, website_page, website_visitor.
sql_introspection
relationships
intermediate
website_track
How to create records in theme.website.page? or What business logic is in theme.website.page?
To use the theme.website.page model, you need to provide values for required fields: view_id. Readonly fields: copy_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: view_id [required]; copy_ids [readonly] [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.
orm_introspection
usage
intermediate
theme.website.page
What one2many fields are in kitchen.cooking.list? or How does kitchen.cooking.list relate to other models?
The kitchen.cooking.list model has 5 relational fields: company_id -> res.company; warehouse_id -> stock.warehouse; product_ids -> kitchen.cooking.list.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: product_ids.
orm_introspection
relationship
intermediate
kitchen.cooking.list
What are common use cases for account.deposit.return? or How to create records in account.deposit.return?
To use the account.deposit.return model, you need to provide values for required fields: return_amount, journal_id. Readonly fields: payment_difference, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: return_amount [required]; journal_id [required]; payment_difference [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.
orm_introspection
usage
intermediate
account.deposit.return
End of preview.

Odoo/HashMicro Training Dataset

This dataset contains question-answer pairs generated from Odoo/HashMicro ERP system for training conversational AI models.

Dataset Details

Dataset Description

This synthetic dataset was automatically generated from Odoo/HashMicro ERP system database schema and model introspection. It contains 14065 examples covering various aspects of the ERP system including models, fields, relationships, and database structure.

  • Curated by: Odoo/HashMicro Training Data Generator
  • Language(s): English
  • License: MIT

Dataset Sources

  • Repository: Generated from Odoo/HashMicro ERP system
  • Generator: AI Chat Agent Training Data Wizard

Uses

Direct Use

This dataset is designed for:

  • Training conversational AI models about Odoo/HashMicro ERP systems
  • Fine-tuning language models for ERP-specific question answering
  • Creating chatbots that can assist with Odoo/HashMicro system queries

Out-of-Scope Use

This dataset should not be used for:

  • General purpose question answering outside of ERP domain
  • Production systems without proper validation
  • Any use case requiring real user data

Dataset Structure

The dataset contains the following fields:

  • text: The input question about Odoo/HashMicro system
  • response: The corresponding answer
  • source: Data source (orm_introspection or sql_introspection)
  • category: Question category (basic_info, field_inquiry, relationship, technical, usage)
  • complexity_level: Complexity level (basic, intermediate, advanced)
  • model_name: Odoo model name (for ORM-based examples)
  • table_name: Database table name (for SQL-based examples)

Data Splits

  • Train: 9066 examples
  • Validation: 4999 examples

Categories

The dataset covers the following categories: Various ERP-related topics

Sources

Data was generated from: Odoo/HashMicro system introspection

Complexity Levels

Basic to advanced levels

Dataset Creation

Curation Rationale

This dataset was created to enable AI models to understand and respond to questions about Odoo/HashMicro ERP systems. The synthetic generation ensures comprehensive coverage of system components while maintaining consistency and accuracy.

Source Data

Data Collection and Processing

Data was automatically generated through:

  1. ORM introspection of Odoo models and fields
  2. SQL schema analysis of database tables and relationships
  3. Automated question-answer pair generation using predefined patterns
  4. Quality scoring and filtering based on relevance and completeness

Who are the source data producers?

The source data comes from the Odoo/HashMicro ERP system itself through automated introspection and schema analysis.

Bias, Risks, and Limitations

  • Dataset is synthetically generated and may not cover all real-world use cases
  • Limited to the specific Odoo/HashMicro system configuration used for generation
  • May contain technical jargon specific to ERP systems
  • Quality depends on the underlying system's data completeness

Recommendations

Users should:

  • Validate model outputs against actual system behavior
  • Consider fine-tuning on domain-specific data for production use
  • Be aware that synthetic data may not capture all nuances of real user queries

Citation

BibTeX:

@dataset{odoo_hashmicro_training_dataset,
  title={Odoo/HashMicro Training Dataset},
  author={AI Chat Agent Training Data Generator},
  year={2024},
  url={Generated from Odoo/HashMicro ERP system}
}

Dataset Card Contact

Generated by Odoo/HashMicro AI Chat Agent Training Data Wizard

Downloads last month
25