diff --git "a/validation.jsonl" "b/validation.jsonl"
new file mode 100644--- /dev/null
+++ "b/validation.jsonl"
@@ -0,0 +1,5000 @@
+{"text": "What models are connected to purchase.line.wiz?", "response": "The purchase.line.wiz model has 3 relational fields: purchase_order_line_id -> purchase.order.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.line.wiz", "table_name": ""}
+{"text": "Show me the relational structure of measure.for.packaging.", "response": "The measure.for.packaging model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "measure.for.packaging", "table_name": ""}
+{"text": "What operations can I perform on report.equip3_pos_general.pos_sale_report_template?", "response": "To use the report.equip3_pos_general.pos_sale_report_template model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_pos_general.pos_sale_report_template", "table_name": ""}
+{"text": "How to query account.bank.statement.closebalance data?", "response": "To use the account.bank.statement.closebalance 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.bank.statement.closebalance", "table_name": ""}
+{"text": "Show me the relational structure of kitchen.cooking.list.line.", "response": "The kitchen.cooking.list.line model has 5 relational fields: list_id -> kitchen.cooking.list; product_id -> product.product; uom_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kitchen.cooking.list.line", "table_name": ""}
+{"text": "How do I use the phone.validation.mixin model?", "response": "To use the phone.validation.mixin model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "phone.validation.mixin", "table_name": ""}
+{"text": "Describe the many2many relations for account.asset.category.fiscal.", "response": "The account.asset.category.fiscal model has 3 relational fields: asset_category_id -> account.asset.category; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.asset.category.fiscal", "table_name": ""}
+{"text": "How to query product.sale.details.report data?", "response": "To use the product.sale.details.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.sale.details.report", "table_name": ""}
+{"text": "How to create records in approval.matrix.purchase.agreement.line?", "response": "To use the approval.matrix.purchase.agreement.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: sequence2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.purchase.agreement.line", "table_name": ""}
+{"text": "What methods are available in remove.action?", "response": "The remove.action model is defined in module: simplify_access_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "remove.action", "table_name": ""}
+{"text": "How does ir.actions.todo relate to other models?", "response": "The ir.actions.todo model has 3 relational fields: action_id -> ir.actions.actions; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.actions.todo", "table_name": ""}
+{"text": "Describe the payment.sale.details.report model in Odoo.", "response": "The payment.sale.details.report model represents payment.sale.details.report in the ERP system. It contains 10 fields and is used to manage payment.sale.details.report data. Key fields include: name, total, details_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "payment.sale.details.report", "table_name": ""}
+{"text": "Describe the field structure of report.equip3_kitchen_reports.report_kitchen_production.", "response": "The report.equip3_kitchen_reports.report_kitchen_production model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_kitchen_reports.report_kitchen_production", "table_name": ""}
+{"text": "How do I use the product.ribbon model?", "response": "To use the product.ribbon model, you need to provide values for required fields: html, html_class. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.ribbon", "table_name": ""}
+{"text": "List all fields in the purchase.request.allocation model.", "response": "The purchase.request.allocation model has 17 fields: purchase_request_line_id, company_id, stock_move_id, purchase_line_id, product_id, product_uom_id, requested_product_uom_qty, allocated_product_qty, open_product_qty, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, float: 3, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.request.allocation", "table_name": ""}
+{"text": "What business logic is in ir.logging?", "response": "To use the ir.logging model, you need to provide values for required fields: name, type, message, path, func, line. Readonly fields: create_uid, create_date, write_uid, write_date, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.logging", "table_name": ""}
+{"text": "Can you explain the purpose of account.analytic.default?", "response": "The account.analytic.default model represents Analytic Distribution in the ERP system. It contains 43 fields and is used to manage analytic distribution data. Key fields include: sequence, analytic_id, analytic_tag_ids, product_id, user_id, company_id, date_start, partner_id, account_id, date_stop, branch_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.analytic.default", "table_name": ""}
+{"text": "Show me the fields of pos.loyalty.history.update.point.", "response": "The pos.loyalty.history.update.point model has 12 fields: type_apply, total_orders, total_point, pos_order_ids, parent_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, float: 2, many2many: 1, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.loyalty.history.update.point", "table_name": ""}
+{"text": "What are the relationships in base.partner.merge.line?", "response": "The base.partner.merge.line model has 3 relational fields: wizard_id -> base.partner.merge.automatic.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.partner.merge.line", "table_name": ""}
+{"text": "What data can be stored in report.excel.fields.sql?", "response": "The report.excel.fields.sql model has 15 fields: sequence, active, cell, column_index, show, formulas, report_excel_section_id, root_model_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 4, boolean: 2, char: 2, text: 1, many2one: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.excel.fields.sql", "table_name": ""}
+{"text": "What are the relationships in sh.purchase.details.report.wizard?", "response": "The sh.purchase.details.report.wizard model has 4 relational fields: company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids, branch_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.details.report.wizard", "table_name": ""}
+{"text": "What data can be stored in mail.blacklist?", "response": "The mail.blacklist model has 24 fields: email, active, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 6, one2many: 3, many2many: 2, integer: 5, many2one: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.blacklist", "table_name": ""}
+{"text": "What does the pos.order model represent?", "response": "The pos.order model represents Point of Sale Orders in the ERP system. It contains 162 fields and is used to manage point of sale orders data. Key fields include: name, date_order, user_id, amount_tax, amount_total, amount_paid, amount_return, lines, company_id, pricelist_id, partner_id, sequence_number, session_id, config_id, invoice_group, account_move, picking_ids, picking_count, failed_pickings, note, nb_print, pos_reference, sale_journal, fiscal_position_id, payment_ids, session_move_id, to_invoice, is_invoiced, is_tipped, tip_amount, consignment_move_id, employee_id, cashier, table_id, customer_count, multiprint_resume, currency_rate, crm_team_id, pos_order_day, pos_order_hour, hour_group_id, promotion_ids, total_mdr_amount_customer, total_mdr_amount_company, is_self_picking, rounding_payment, voucher_id, voucher_amount, active, is_payment_method_with_receivable, receivable_invoice_count, payment_paid, zone_id, is_home_delivery, is_pre_order, estimated_order_pre_order, total_before_discount, total_discount, total_after_discount, total_after_discount_w_o_tax, is_use_pos_coupon, pos_coupon_id, is_past_date, is_corrected, self_order_id, take_away_order, delivery_date, delivered_date, delivery_address, delivery_phone, shipping_id, statement_ids, expire_date, is_return, is_returned, email, email_invoice, signature, parent_id, sale_id, margin, partial_payment, booking_id, so_pickup_id, payment_journal_id, pos_branch_id, is_paid_full, currency_id, analytic_account_id, state, removed_user_id, is_quotation, paid_date, picking_type_id, receipt_count, employeemeal_employee_id, cashier_id, void_order_id, void_state, rounding_multiplier, is_return_order, return_order_id, return_status, return_order_state, cron_picking, ean13, is_multiple_warehouse, is_show_pos_payment, exchange_amount, is_exchange_order, customer_deposit_id, customer_deposit_amount, point_ids, plus_point, redeem_point, redeem_point_refund, build_plus_point_rules, is_repair_member_point, is_payment_edc, payment_edc_id, location_id, date_order_str, import_reference, is_mdr_fixed, total_disc_manual_global, amount_sales, amount_discount, amount_payment, amount_ppn, amount_nett_sales, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.order", "table_name": ""}
+{"text": "What are the relationships in auditlog.log.line?", "response": "The auditlog.log.line model has 8 relational fields: field_id -> ir.model.fields; log_id -> auditlog.log; model_id -> ir.model; user_id -> res.users; http_session_id -> auditlog.http.session; http_request_id -> auditlog.http.request; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "auditlog.log.line", "table_name": ""}
+{"text": "Which fields in whatsapp.template.message.variable are computed?", "response": "The whatsapp.template.message.variable model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "whatsapp.template.message.variable", "table_name": ""}
+{"text": "How is ir.ui.view used in the system?", "response": "The ir.ui.view model represents View in the ERP system. It contains 41 fields and is used to manage view data. Key fields include: name, model, key, priority, arch, arch_base, arch_db, arch_fs, arch_updated, arch_prev, inherit_id, inherit_children_ids, field_parent, model_data_id, xml_id, groups_id, mode, active, customize_show, is_seo_optimized, website_meta_title, website_meta_description, website_meta_keywords, website_meta_og_img, seo_name, website_id, page_ids, first_page_id, track, visibility, visibility_password, visibility_password_display, theme_template_id, type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.ui.view", "table_name": ""}
+{"text": "What are the relationships in sale.payment.acquirer.onboarding.wizard?", "response": "The sale.payment.acquirer.onboarding.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "Tell me about the intrawarehouse.transfer model.", "response": "The intrawarehouse.transfer model represents Intrawarehouse Transfer in the ERP system. It contains 8 fields and is used to manage intrawarehouse transfer data. Key fields include: interawarehouse_transfer_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "Describe the implementation of blacklist.partner.wiz.", "response": "The blacklist.partner.wiz model is defined in module: equip3_purchase_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "blacklist.partner.wiz", "table_name": ""}
+{"text": "What does the invoice.recurring.line model represent?", "response": "The invoice.recurring.line model represents Invoice Recurring Line in the ERP system. It contains 22 fields and is used to manage invoice recurring line data. Key fields include: invoice_recurring_id, product_id, account_id, tax_ids, product_uom_category_id, product_uom_id, name, price_unit, discount, quantity, company_id, journal_id, analytic_group_ids, subtotal, price_tax, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "invoice.recurring.line", "table_name": ""}
+{"text": "Describe the base_import.tests.models.o2m.child model in Odoo.", "response": "The base_import.tests.models.o2m.child model represents Tests : Base Import Model, One to Many child in the ERP system. It contains 9 fields and is used to manage tests : base import model, one to many child data. Key fields include: parent_id, value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.o2m.child", "table_name": ""}
+{"text": "Describe the implementation of project.task.type.", "response": "The project.task.type model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "project.task.type", "table_name": ""}
+{"text": "How is quality.check.report implemented technically?", "response": "The quality.check.report model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "quality.check.report", "table_name": ""}
+{"text": "Tell me about the send.message.mass model.", "response": "The send.message.mass model represents Send Message Mass in the ERP system. It contains 10 fields and is used to manage send message mass data. Key fields include: message_chat_ids, conversation_id, connector_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "send.message.mass", "table_name": ""}
+{"text": "List all fields in the pos.sync.session.log model.", "response": "The pos.sync.session.log model has 17 fields: order_uid, create_date, send_from_session_id, send_to_session_id, user_id, user_receive_id, action, logs, state, branch_id, company_id, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: char: 2, datetime: 3, many2one: 8, selection: 2, text: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.sync.session.log", "table_name": ""}
+{"text": "How to create records in update.historical.data?", "response": "To use the update.historical.data model, you need to provide values for required fields: action. Readonly fields: list_data_double_count, picking_return_count, list_data_issue_count, list_data_quant_count, list_data_je_count, list_data_product_count, list_data_issue_svl_double_create_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "update.historical.data", "table_name": ""}
+{"text": "What business logic is in pos.receipt.template?", "response": "To use the pos.receipt.template model, you need to provide values for required fields: none. Readonly fields: preview_receipt, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.receipt.template", "table_name": ""}
+{"text": "What fields does sh.purchase.product.profit.wizard have?", "response": "The sh.purchase.product.profit.wizard model has 14 fields: sh_start_date, sh_end_date, sh_partner_ids, report_by, sh_product_ids, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2many: 4, selection: 1, integer: 1, char: 1, many2one: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.purchase.product.profit.wizard", "table_name": ""}
+{"text": "What are the relationships in decimal.precision?", "response": "The decimal.precision model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "decimal.precision", "table_name": ""}
+{"text": "Tell me about the ir.server.object.lines model.", "response": "The ir.server.object.lines model represents Server Action value mapping in the ERP system. It contains 12 fields and is used to manage server action value mapping data. Key fields include: server_id, col1, value, evaluation_type, resource_ref, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.server.object.lines", "table_name": ""}
+{"text": "How is account.tax.digunggung used in the system?", "response": "The account.tax.digunggung model represents Account Tax Digunggung in the ERP system. It contains 12 fields and is used to manage account tax digunggung data. Key fields include: tax_report, start_date_digunggung, end_date_digunggung, partner_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.tax.digunggung", "table_name": ""}
+{"text": "How is purchase.agreement.type used in the system?", "response": "The purchase.agreement.type model represents Purchase Agreement Type in the ERP system. It contains 8 fields and is used to manage purchase agreement type data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.agreement.type", "table_name": ""}
+{"text": "What are the technical details of purchase.change.request.line?", "response": "The purchase.change.request.line model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.change.request.line", "table_name": ""}
+{"text": "How to query invoice.printout.editor.lines data?", "response": "To use the invoice.printout.editor.lines model, you need to provide values for required fields: none. Readonly fields: field_description, name, ttype, model, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "invoice.printout.editor.lines", "table_name": ""}
+{"text": "How do I use the report.dynamic_accounts_report.cash_flow model?", "response": "To use the report.dynamic_accounts_report.cash_flow model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.cash_flow", "table_name": ""}
+{"text": "What operations can I perform on assets.approval.matrix.line?", "response": "To use the assets.approval.matrix.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: sequence2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assets.approval.matrix.line", "table_name": ""}
+{"text": "What models are connected to stock.picking.to.batch?", "response": "The stock.picking.to.batch model has 4 relational fields: batch_id -> stock.picking.batch; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.picking.to.batch", "table_name": ""}
+{"text": "How is report.account.report_journal implemented technically?", "response": "The report.account.report_journal model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.account.report_journal", "table_name": ""}
+{"text": "How is crm.salesperson.tracking.report implemented technically?", "response": "The crm.salesperson.tracking.report model is defined in module: equip3_crm_tracking. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.salesperson.tracking.report", "table_name": ""}
+{"text": "What are the technical details of invoice.printout.editor.lines?", "response": "The invoice.printout.editor.lines model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.printout.editor.lines", "table_name": ""}
+{"text": "What are the technical details of invoice.payment.report.xls?", "response": "The invoice.payment.report.xls model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.payment.report.xls", "table_name": ""}
+{"text": "What modules define pos.backup.orders?", "response": "The pos.backup.orders model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.backup.orders", "table_name": ""}
+{"text": "Which fields in account.edi.document are computed?", "response": "The account.edi.document model is defined in module: account_edi. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.edi.document", "table_name": ""}
+{"text": "What modules define analytic.priority?", "response": "The analytic.priority model is defined in module: equip3_accounting_analytical. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "analytic.priority", "table_name": ""}
+{"text": "What are the relationships in ir.exports?", "response": "The ir.exports model has 3 relational fields: export_fields -> ir.exports.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.exports", "table_name": ""}
+{"text": "How is pos.loyalty.rule implemented technically?", "response": "The pos.loyalty.rule model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.loyalty.rule", "table_name": ""}
+{"text": "What fields does sale.adv.wizard.product.line have?", "response": "The sale.adv.wizard.product.line model has 13 fields: sale_adv_wizard_id, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, float: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.adv.wizard.product.line", "table_name": ""}
+{"text": "What fields does sh.mrp.pics have?", "response": "The sh.mrp.pics model has 13 fields: product_id, sh_message, sh_quality_point_id, mrp_id, workorder_id, attachment_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, text: 1, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.mrp.pics", "table_name": ""}
+{"text": "How to query purchase.request.line.make.purchase.order.item data?", "response": "To use the purchase.request.line.make.purchase.order.item model, you need to provide values for required fields: wiz_id, name, product_uom_id. Readonly fields: wiz_id, rem_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.request.line.make.purchase.order.item", "table_name": ""}
+{"text": "What fields does account.partner.ageing have?", "response": "The account.partner.ageing model has 18 fields: period_length, date_from, result_selection, partner_ids, partner_category_ids, section_num, journal_ids, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 3, date: 2, selection: 2, many2many: 3, many2one: 4, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.partner.ageing", "table_name": ""}
+{"text": "How is account.analytic.line implemented technically?", "response": "The account.analytic.line model is defined in module: analytic. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.analytic.line", "table_name": ""}
+{"text": "What are common use cases for hide.field?", "response": "To use the hide.field 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "hide.field", "table_name": ""}
+{"text": "Can you explain the purpose of approval.reject?", "response": "The approval.reject model represents approval.reject in the ERP system. It contains 8 fields and is used to manage approval.reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.reject", "table_name": ""}
+{"text": "What are the technical details of payment.voucher?", "response": "The payment.voucher model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "payment.voucher", "table_name": ""}
+{"text": "List all fields in the ks_dashboard_ninja.item_action model.", "response": "The ks_dashboard_ninja.item_action model has 17 fields: ks_item_action_field, ks_item_action_field_type, ks_item_action_date_groupby, ks_chart_type, ks_dashboard_item_id, ks_model_id, sequence, ks_record_limit, ks_sort_by_field, ks_sort_by_order, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, char: 2, selection: 3, integer: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.item_action", "table_name": ""}
+{"text": "Show me the fields of sale.summary.commission.report.", "response": "The sale.summary.commission.report model has 13 fields: start_date, end_date, sales_persons, commision_type, company_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, many2many: 2, selection: 1, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.summary.commission.report", "table_name": ""}
+{"text": "What does the approval.matrix.direct.purchase model represent?", "response": "The approval.matrix.direct.purchase model represents Approval Matrix Direct Purchase in the ERP system. It contains 46 fields and is used to manage approval matrix direct purchase data. Key fields include: name, company_id, branch_id, minimum_amt, maximum_amt, approval_matrix_direct_purchase_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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.direct.purchase", "table_name": ""}
+{"text": "What are the technical details of sh.top.customers.xls?", "response": "The sh.top.customers.xls model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.top.customers.xls", "table_name": ""}
+{"text": "What are common use cases for rn.matrix.reject?", "response": "To use the rn.matrix.reject 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "rn.matrix.reject", "table_name": ""}
+{"text": "What fields does project.task.type have?", "response": "The project.task.type model has 21 fields: active, name, description, sequence, project_ids, legend_blocked, legend_done, legend_normal, mail_template_id, fold, rating_template_id, auto_validation_kanban_state, is_closed, disabled_rating_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 4, char: 5, text: 2, integer: 2, many2many: 1, many2one: 4, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.task.type", "table_name": ""}
+{"text": "What models are connected to receipt.voucher.line?", "response": "The receipt.voucher.line model has 5 relational fields: receipt_voucher_id -> receipt.voucher; invoice_id -> account.move; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "receipt.voucher.line", "table_name": ""}
+{"text": "What operations can I perform on customer.deposit?", "response": "To use the customer.deposit model, you need to provide values for required fields: none. Readonly fields: name, return_deposit, filter_deposit_account_ids, deposit_move_id, is_show_cancel, invoice_count, reconcile_count, approval_matrix_id, is_customer_deposit_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, deposit_history, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "customer.deposit", "table_name": ""}
+{"text": "What data can be stored in purchase.order.split?", "response": "The purchase.order.split model has 19 fields: tick, sequence, product_template_id, name, date_planned, product_qty, price_unit, destination_warehouse_id, split_id, purchase_line_id, product_uom, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, char: 2, many2one: 8, text: 1, datetime: 4, float: 2, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.order.split", "table_name": ""}
+{"text": "What modules define acrux.chat.default.answer?", "response": "The acrux.chat.default.answer model is defined in module: acrux_chat. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "acrux.chat.default.answer", "table_name": ""}
+{"text": "How is stock.return.picking.line implemented technically?", "response": "The stock.return.picking.line model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.return.picking.line", "table_name": ""}
+{"text": "What data can be stored in setu.inventory.age.report?", "response": "The setu.inventory.age.report model has 13 fields: stock_file_data, company_ids, product_category_ids, product_ids, warehouse_id, warehouse_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, many2many: 4, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.age.report", "table_name": ""}
+{"text": "Show me the relational structure of whatsapp.template.message.", "response": "The whatsapp.template.message model has 13 relational fields: broadcast_template_id -> qiscus.wa.template.content; wa_variable_ids -> whatsapp.template.message.variable; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "whatsapp.template.message", "table_name": ""}
+{"text": "What are the available fields for pos.zone?", "response": "The pos.zone model has 9 fields: name, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.zone", "table_name": ""}
+{"text": "How to query sale.product.configurator data?", "response": "To use the sale.product.configurator model, you need to provide values for required fields: product_template_id. Readonly fields: pricelist_id, product_template_attribute_value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.product.configurator", "table_name": ""}
+{"text": "Describe the implementation of report.accounting_pdf_reports.report_journal.", "response": "The report.accounting_pdf_reports.report_journal model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.accounting_pdf_reports.report_journal", "table_name": ""}
+{"text": "What fields does report.sh_po_tender_management.report_analyze_quotations have?", "response": "The report.sh_po_tender_management.report_analyze_quotations model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_po_tender_management.report_analyze_quotations", "table_name": ""}
+{"text": "What are the technical details of change.production.qty?", "response": "The change.production.qty model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "change.production.qty", "table_name": ""}
+{"text": "What is the product.ratio.line model?", "response": "The product.ratio.line model represents Product Ratio Line in the ERP system. It contains 16 fields and is used to manage product ratio line data. Key fields include: active, uom_id, product_id, product_tmpl_id, description, ratio, uom_ref_id, product_variant_ids, is_custom_uom, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.ratio.line", "table_name": ""}
+{"text": "List all fields in the crossovered.budget.wizard model.", "response": "The crossovered.budget.wizard model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crossovered.budget.wizard", "table_name": ""}
+{"text": "What business logic is in account.pettycash.voucher.wizard?", "response": "To use the account.pettycash.voucher.wizard model, you need to provide values for required fields: name, number, date. Readonly fields: name, number, fund, ba_ca_journal_id, currency_id, company_id, state, total, narration, voucher_type, tax_amount, expense_account_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.pettycash.voucher.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for account.move.template.", "response": "The account.move.template model has 22 relational fields: journal_id -> account.journal; suitable_journal_ids -> account.journal; company_id -> res.company; company_currency_id -> res.currency; currency_id -> res.currency; line_ids -> account.move.template.line; partner_id -> res.partner; payment_id -> account.payment; statement_line_id -> account.bank.statement.line; reversed_entry_id -> account.move.template; reversal_move_id -> account.move.template; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: suitable_journal_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.move.template", "table_name": ""}
+{"text": "Describe the field structure of sh.send.notification.", "response": "The sh.send.notification model has 16 fields: name, title, message, redirect_url, logo, state, message_to, specific_ids, log_historys, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 2, char: 3, binary: 1, selection: 2, many2many: 1, one2many: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.send.notification", "table_name": ""}
+{"text": "What methods are available in account.invoice.to.draft?", "response": "The account.invoice.to.draft model is defined in module: aos_base_account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.invoice.to.draft", "table_name": ""}
+{"text": "What are the relationships in pos.promotion.multilevel.gift?", "response": "The pos.promotion.multilevel.gift model has 4 relational fields: product_id -> product.product; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.promotion.multilevel.gift", "table_name": ""}
+{"text": "What are the relationships in report.mrp.report_bom_structure?", "response": "The report.mrp.report_bom_structure model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.mrp.report_bom_structure", "table_name": ""}
+{"text": "What are the technical details of sh.purchase.tags?", "response": "The sh.purchase.tags model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.tags", "table_name": ""}
+{"text": "What are the available fields for close.fiscal.year?", "response": "The close.fiscal.year model has 8 fields: fiscal_year_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "close.fiscal.year", "table_name": ""}
+{"text": "Show me the relational structure of remove.action.", "response": "The remove.action model has 8 relational fields: access_management_id -> access.management; model_id -> ir.model; view_data_ids -> view.data; server_action_ids -> action.data; report_action_ids -> action.data; view_ids -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: view_data_ids, server_action_ids, report_action_ids, view_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "remove.action", "table_name": ""}
+{"text": "How to query stock.warehouse.orderpoint data?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.warehouse.orderpoint", "table_name": ""}
+{"text": "What is the report.equip3_inventory_masterdata.report_product_tmpl_forecast model?", "response": "The report.equip3_inventory_masterdata.report_product_tmpl_forecast model represents Equip Stock Replenishment Report in the ERP system. It contains 3 fields and is used to manage equip stock replenishment report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_inventory_masterdata.report_product_tmpl_forecast", "table_name": ""}
+{"text": "Show me the relational structure of ir.module.module.", "response": "The ir.module.module model has 6 relational fields: category_id -> ir.module.category; dependencies_id -> ir.module.module.dependency; exclusion_ids -> ir.module.module.exclusion; image_ids -> ir.attachment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.module.module", "table_name": ""}
+{"text": "What business logic is in purchase.order.line.extract?", "response": "To use the purchase.order.line.extract 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.order.line.extract", "table_name": ""}
+{"text": "Tell me about the base_import.mapping model.", "response": "The base_import.mapping model represents Base Import Mapping in the ERP system. It contains 10 fields and is used to manage base import mapping data. Key fields include: res_model, column_name, field_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.mapping", "table_name": ""}
+{"text": "Show me the relational structure of remove.pos.order.", "response": "The remove.pos.order model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "remove.pos.order", "table_name": ""}
+{"text": "Which fields in stock.day.average.line are computed?", "response": "The stock.day.average.line model is defined in module: equip3_inventory_control. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.day.average.line", "table_name": ""}
+{"text": "List all fields in the pos.generate.efaktur model.", "response": "The pos.generate.efaktur model has 18 fields: name, other_name, state, start_date, end_date, invoice_ids, digunggung_ids, gabungan_ids, other_ids, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, selection: 1, date: 2, one2many: 4, many2one: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.generate.efaktur", "table_name": ""}
+{"text": "Describe the cancel.supplier.memory model in Odoo.", "response": "The cancel.supplier.memory model represents cancel.supplier.memory in the ERP system. It contains 9 fields and is used to manage cancel.supplier.memory data. Key fields include: supplier_id, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "cancel.supplier.memory", "table_name": ""}
+{"text": "How to create records in sh.commision.detail?", "response": "To use the sh.commision.detail 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.commision.detail", "table_name": ""}
+{"text": "Describe the auditlog.http.session model in Odoo.", "response": "The auditlog.http.session model represents Auditlog - HTTP User session log in the ERP system. It contains 10 fields and is used to manage auditlog - http user session log data. Key fields include: display_name, name, user_id, http_request_ids, id, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "auditlog.http.session", "table_name": ""}
+{"text": "What operations can I perform on account.common.account.report?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.common.account.report", "table_name": ""}
+{"text": "What foreign keys exist in website.sale.payment.acquirer.onboarding.wizard?", "response": "The website.sale.payment.acquirer.onboarding.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.sale.payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "What foreign keys exist in approval.matrix.sale.order.lines?", "response": "The approval.matrix.sale.order.lines model has 8 relational fields: approval_matrix -> approval.matrix.sale.order; order_id -> sale.order; user_name_ids -> res.users; last_approved -> res.users; approved_users -> res.users; bo_order_id -> saleblanket.saleblanket; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_name_ids, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.sale.order.lines", "table_name": ""}
+{"text": "Can you explain the purpose of pos.bus.log?", "response": "The pos.bus.log model represents Transactions of Point Sync in the ERP system. It contains 7 fields and is used to manage transactions of point sync data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.bus.log", "table_name": ""}
+{"text": "What models are connected to customer.degree.trust?", "response": "The customer.degree.trust model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "customer.degree.trust", "table_name": ""}
+{"text": "Show me the fields of res.partner.title.", "response": "The res.partner.title model has 9 fields: name, shortcut, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.partner.title", "table_name": ""}
+{"text": "What operations can I perform on mrp.bom.operation?", "response": "To use the mrp.bom.operation model, you need to provide values for required fields: sequence, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mrp.bom.operation", "table_name": ""}
+{"text": "What are the technical details of restaurant.printer?", "response": "The restaurant.printer model is defined in module: pos_restaurant. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "restaurant.printer", "table_name": ""}
+{"text": "What are the available fields for ir.qweb.field.image?", "response": "The ir.qweb.field.image model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.image", "table_name": ""}
+{"text": "What methods are available in tax.report?", "response": "The tax.report model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "tax.report", "table_name": ""}
+{"text": "Tell me about the assembly.production.record model.", "response": "The assembly.production.record model represents Assembly Production Record in the ERP system. It contains 84 fields and is used to manage assembly production record data. Key fields include: name, company_id, is_branch_required, product_id, product_tmpl_id, product_qty, rejected_qty, product_uom_id, product_uom_category_id, assembly_bom_id, branch_id, confirm_date, state, move_raw_ids, move_finished_ids, move_byproduct_ids, location_src_id, location_dest_id, picking_type_id, date_planned_start, date_planned_finished, date_deadline, procurement_group_id, move_dest_ids, production_location_id, warehouse_id, product_tracking, account_move_ids, purchase_request_ids, internal_transfer_count, disassembly_record_ids, expiry_days, product_use_expiration_date, finished_lot_ids, byproduct_lot_ids, rejected_lot_ids, show_submit_button, is_autogenerate, default_finished_lot_qty, default_rejected_lot_qty, show_byproduct_lot_tab, byproduct_manual_product_ids, default_byproduct_lot_qty, default_next_byproduct_product_id, any_byproduct_is_autogenerate, all_byproduct_is_autogenerate, component_consumed_qty, svl_value, bom_id, record_type, assembly_record_id, disassembly_remaining_qty, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assembly.production.record", "table_name": ""}
+{"text": "Show me the relational structure of saleblanket.saleblanket.", "response": "The saleblanket.saleblanket model has 32 relational fields: partner_id -> res.partner; pricelist_id -> product.pricelist; payment_term_id -> account.payment.term; current_user -> res.users; user_id -> res.users; currency_id -> res.currency; company_id -> res.company; current_company -> res.company; branch_id -> res.branch; analytic_tag_ids -> account.analytic.tag; order_line_ids -> orderline.orderline; approving_matrix_bo_sale_id -> approval.matrix.sale.order; approval_matrix_line_id -> approval.matrix.sale.order.lines; approved_matrix_ids -> approval.matrix.sale.order.lines; invoice_address -> res.partner; delivery_address -> res.partner; report_template_id1 -> ir.actions.report; report_template_id -> ir.actions.report; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "saleblanket.saleblanket", "table_name": ""}
+{"text": "What data can be stored in product.removal?", "response": "The product.removal model has 9 fields: name, method, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.removal", "table_name": ""}
+{"text": "What operations can I perform on delivery.price.rule?", "response": "To use the delivery.price.rule model, you need to provide values for required fields: sequence, carrier_id, variable, operator, max_value, list_base_price, list_price, variable_factor. Readonly fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "delivery.price.rule", "table_name": ""}
+{"text": "What are the available fields for sale.adv.wizard.product.line?", "response": "The sale.adv.wizard.product.line model has 13 fields: sale_adv_wizard_id, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, float: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.adv.wizard.product.line", "table_name": ""}
+{"text": "Tell me about the base.import.module model.", "response": "The base.import.module model represents Import Module in the ERP system. It contains 11 fields and is used to manage import module data. Key fields include: module_file, state, import_message, force, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.import.module", "table_name": ""}
+{"text": "Can you explain the purpose of sale.order.option?", "response": "The sale.order.option model represents Sale Options in the ERP system. It contains 18 fields and is used to manage sale options data. Key fields include: is_present, order_id, line_id, name, product_id, price_unit, discount, uom_id, product_uom_category_id, quantity, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.order.option", "table_name": ""}
+{"text": "How to create records in account.account.type?", "response": "To use the account.account.type model, you need to provide values for required fields: name, type, company_id. Readonly fields: company_id, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.account.type", "table_name": ""}
+{"text": "What business logic is in pos.promotion.multilevel.condition?", "response": "To use the pos.promotion.multilevel.condition model, you need to provide values for required fields: product_id, minimum_quantity, promotion_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion.multilevel.condition", "table_name": ""}
+{"text": "Describe the implementation of account.fiscal.position.tax.template.", "response": "The account.fiscal.position.tax.template model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.fiscal.position.tax.template", "table_name": ""}
+{"text": "Describe the batch.shipping.line model in Odoo.", "response": "The batch.shipping.line model represents Batch Shipping Line in the ERP system. It contains 12 fields and is used to manage batch shipping line data. Key fields include: serial_number, picking_id, warehouse_id, batch_shipping_id, used_picking_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "batch.shipping.line", "table_name": ""}
+{"text": "What are the relationships in pos.loyalty.category?", "response": "The pos.loyalty.category model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.loyalty.category", "table_name": ""}
+{"text": "What data can be stored in queue.job.channel?", "response": "The queue.job.channel model has 12 fields: name, complete_name, parent_id, job_function_ids, removal_interval, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 3, one2many: 1, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "queue.job.channel", "table_name": ""}
+{"text": "Can you explain the purpose of approval.matrix.vendor.line?", "response": "The approval.matrix.vendor.line model represents Approval Matrix Vendor Line in the ERP system. It contains 22 fields and is used to manage approval matrix vendor line data. Key fields include: sequence, approval_matrix, company_id, branch_id, user_ids, minimum_approver, approved_users, state_char, time_stamp, feedback, last_approved, approved, app_matrix_id, sequence2, approver_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.vendor.line", "table_name": ""}
+{"text": "What operations can I perform on sh.announcement?", "response": "To use the sh.announcement 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.announcement", "table_name": ""}
+{"text": "What is the mr_line.pr.wizard_line model?", "response": "The mr_line.pr.wizard_line model represents mr_line.pr.wizard_line in the ERP system. It contains 17 fields and is used to manage mr_line.pr.wizard_line data. Key fields include: mr_id, mr_line_id, no, product_id, description, uom_id, qty_purchase, request_date, dest_warehouse_id, mr_pr_wizard, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mr_line.pr.wizard_line", "table_name": ""}
+{"text": "Show me the relational structure of sale.report.", "response": "The sale.report model has 22 relational fields: product_id -> product.product; product_uom -> uom.uom; partner_id -> res.partner; company_id -> res.company; user_id -> res.users; product_tmpl_id -> product.template; categ_id -> product.category; pricelist_id -> product.pricelist; analytic_account_id -> account.analytic.account; team_id -> crm.team; country_id -> res.country; industry_id -> res.partner.industry; commercial_partner_id -> res.partner; campaign_id -> utm.campaign; medium_id -> utm.medium; source_id -> utm.source; order_id -> sale.order; warehouse_id -> stock.warehouse; website_id -> website; branch_id -> res.branch; city_id -> res.country.city; state_id -> res.country.state. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.report", "table_name": ""}
+{"text": "What are the relationships in res.users.apikeys.show?", "response": "The res.users.apikeys.show model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.users.apikeys.show", "table_name": ""}
+{"text": "How to query bo.approval.matrix.sale.reject data?", "response": "To use the bo.approval.matrix.sale.reject 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "bo.approval.matrix.sale.reject", "table_name": ""}
+{"text": "Describe the implementation of pos.report.category.", "response": "The pos.report.category model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.report.category", "table_name": ""}
+{"text": "Show me the fields of stock.move.", "response": "The stock.move model has 237 fields: name, sequence, priority, create_date, date, date_deadline, company_id, description_picking, product_qty, product_uom_qty, product_uom, product_uom_category_id, product_tmpl_id, location_id, location_dest_id, partner_id, move_dest_ids, move_orig_ids, picking_partner_id, note, state, price_unit, backorder_id, origin, procure_method, scrapped, scrap_ids, group_id, rule_id, propagate_cancel, delay_alert_date, picking_type_id, inventory_id, move_line_ids, move_line_nosuggest_ids, origin_returned_move_id, returned_move_ids, availability, restrict_partner_id, route_ids, warehouse_id, has_tracking, show_operations, show_details_visible, show_reserved_availability, additional, is_locked, is_initial_demand_editable, is_quantity_done_editable, reference, has_move_lines, package_level_id, picking_type_entire_packs, display_assign_serial, next_serial_count, orderpoint_id, forecast_availability, forecast_expected_date, lot_ids, created_production_id, production_id, raw_material_production_id, unbuild_id, consume_unbuild_id, allowed_operation_ids, operation_id, workorder_id, bom_line_id, byproduct_id, unit_factor, is_done, order_finished_lot_ids, should_consume_qty, use_expiration_date, to_refund, account_move_ids, stock_valuation_layer_ids, is_reconstruct_svl, scrap_return_move_id, purchase_line_id, created_purchase_line_id, sh_quality_point, sh_quality_point_id, sh_last_qc_date, sh_last_qc_state, number_of_test, created_purchase_request_line_id, purchase_request_allocation_ids, purchase_request_ids, requisition_line_ids, sale_line_id, branch_id, weight, product_description, qty_pack, is_pack, repair_id, sh_stock_move_barcode_mobile, sh_stock_move_bm_is_cont_scan, length, width, height, product_id, is_adjustable_picking, package_measure_selection, picking_state, is_existing_package, move_package_id, filter_move_package_ids, mr_line_id, move_line_sequence, serial_no, export_file, export_name, next_serial, next_serial_not_autogenerate, next_lot_not_autogenerate, is_import, is_record_confirm, product_type, is_serial_number, next_lot, qty_per_lot, is_autogenerate, picking_code, is_product_service_operation, is_product_service_operation_delivery, is_product_service_operation_receiving, serial, initial_demand, move_progress, analytic_account_group_ids, remaining, fulfillment, current_qty, scheduled_date, responsible, late_time, late_time_hours, process_status, process_time, process_time_hours, package_type, qty_in_pack, packaging_ids, package_quant_ids, measure_ids, product_id_domain, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, created_assembly_id, assembly_finished_id, assembly_component_id, assembly_unit_factor, assembly_should_consume_qty, assembly_product_free_qty, description, created_kitchen_id, kitchen_finished_id, kitchen_component_id, kitchen_unit_factor, kitchen_should_consume_qty, kitchen_product_free_qty, asp_asm_stock_id, bom_product_uom_qty, sub_total, finish_good_rework_id, type_product_bom, finish_good_rework_finished_id, finish_good_rework_created_kitchen_id, finish_good_rework_by_product_id, assembly_record_type, assembly_confirm_date, assembly_product_id, assembly_bom_id, assembly_svl_value, assembly_difference, exp_date, qty_bundle, id_bundle, package_barcode, kitchen_confirm_date, kitchen_product_id, kitchen_bom_id, kitchen_svl_value, kitchen_difference, product_warehouse, product_location, expired_date, product_barcode, vendor_id, state_expired, state_check, picking_type_code, reserved_by_id, reserved_availability, is_reserved, picking_id, origin_src_location, origin_dest_location, picking_reference, is_transit, date_done, return_reason, action, is_transfer_in, is_transfer_out, quantity_done, volume, movement_type, cost, combo_item_id, pos_branch_id, pos_order_line_id, so_antar_badan, po_antar_badan, sale_order_id, purchase_order_id, date_done_real, taxes_id, price_subtotal, price_tax, price_total, price_untaxed_amount, discount_amount, price_discount, currency_id, returned_qty, remaining_checked_qty, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: char: 23, integer: 10, selection: 17, datetime: 14, many2one: 71, text: 2, float: 39, many2many: 12, boolean: 34, one2many: 9, binary: 1, date: 1, monetary: 4.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.move", "table_name": ""}
+{"text": "How does theme.website.menu relate to other models?", "response": "The theme.website.menu model has 5 relational fields: page_id -> theme.website.page; parent_id -> theme.website.menu; copy_ids -> website.menu; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "theme.website.menu", "table_name": ""}
+{"text": "What are common use cases for purchase.line.wiz?", "response": "To use the purchase.line.wiz 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.line.wiz", "table_name": ""}
+{"text": "Tell me about the purchase.request.wizard.line model.", "response": "The purchase.request.wizard.line model represents purchase.request.wizard.line in the ERP system. It contains 17 fields and is used to manage purchase.request.wizard.line data. Key fields include: mr_id, no, product_id, description, uom_id, qty_purchase, request_date, mr_pr_wizard, mr_line_id, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.request.wizard.line", "table_name": ""}
+{"text": "Describe the implementation of pos.qrcode.", "response": "The pos.qrcode model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.qrcode", "table_name": ""}
+{"text": "Tell me about the sale.order.deduction model.", "response": "The sale.order.deduction model represents Sale Order Deduction in the ERP system. It contains 13 fields and is used to manage sale order deduction data. Key fields include: product_id, sale_id, description, product_qty, product_price, product_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.order.deduction", "table_name": ""}
+{"text": "How is mail.channel.partner implemented technically?", "response": "The mail.channel.partner model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.channel.partner", "table_name": ""}
+{"text": "Show me the relational structure of pos.pack.operation.lot.", "response": "The pos.pack.operation.lot model has 6 relational fields: pos_order_line_id -> pos.order.line; order_id -> pos.order; product_id -> product.product; lot_id -> stock.production.lot; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.pack.operation.lot", "table_name": ""}
+{"text": "What does the procurement.group model represent?", "response": "The procurement.group model represents Procurement Group in the ERP system. It contains 13 fields and is used to manage procurement group data. Key fields include: partner_id, name, move_type, stock_move_ids, mrp_production_ids, sale_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "procurement.group", "table_name": ""}
+{"text": "What methods are available in pos.payment.installment.tenor?", "response": "The pos.payment.installment.tenor model is defined in module: equip3_pos_payment_edc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.payment.installment.tenor", "table_name": ""}
+{"text": "Describe the account.asset.asset model in Odoo.", "response": "The account.asset.asset model represents Asset/Revenue Recognition in the ERP system. It contains 86 fields and is used to manage asset/revenue recognition data. Key fields include: entry_count, name, code, value, currency_id, note, category_id, date, active, partner_id, method_number, method_period, method_end, method_progress_factor, value_residual, method_time, prorata, depreciation_line_ids, salvage_value, invoice_id, type, account_analytic_id, analytic_tag_ids, first_depreciation_manual_date, user_id, is_monthly_depreciation, is_reset_january, months_remaining, method, cut_off_asset_date, date_first_depreciation, fiscal_category_id, method_fiscal, asset_type, asset_type_1, sub_asset_type, non_building_type, is_monthly_depreciation_fiscal, is_reset_january_fiscal, months_remaining_fiscal, method_number_fiscal, method_period_fiscal, method_end_fiscal, depreciation_line_ids_fiscal, asset_history_lines_ids, asset_value_residual, account_cip_id, state, state1, state2, approval_matrix_id, approved_matrix_ids, is_approval_matrix, is_approve_button, approval_matrix_line_id, request_partner_id, company_id, branch_id, asset_sequence, product_id, fiscal_prorata_temporis, location, po_ref, asset_post_entries_count, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.asset.asset", "table_name": ""}
+{"text": "What does the report.equip3_inventory_reports.expiring_product_calendar model represent?", "response": "The report.equip3_inventory_reports.expiring_product_calendar model represents Expiring Product Calendar Report in the ERP system. It contains 3 fields and is used to manage expiring product calendar report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_inventory_reports.expiring_product_calendar", "table_name": ""}
+{"text": "Describe the field structure of mail.shortcode.", "response": "The mail.shortcode model has 11 fields: source, substitution, description, message_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, text: 1, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.shortcode", "table_name": ""}
+{"text": "What fields does website.published.mixin have?", "response": "The website.published.mixin model has 7 fields: website_published, is_published, can_publish, website_url, id, display_name, __last_update. Field types distribution: boolean: 3, char: 2, integer: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "website.published.mixin", "table_name": ""}
+{"text": "Which fields in calendar.event.reschedule.wizard are computed?", "response": "The calendar.event.reschedule.wizard model is defined in module: equip3_crm_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "calendar.event.reschedule.wizard", "table_name": ""}
+{"text": "How to query setu.inventory.overstock.report data?", "response": "To use the setu.inventory.overstock.report model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.overstock.report", "table_name": ""}
+{"text": "What business logic is in store.filters.groups?", "response": "To use the store.filters.groups model, you need to provide values for required fields: model_id, node_option, attribute_string. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "store.filters.groups", "table_name": ""}
+{"text": "How to create records in report.sh_purchase_reports.sh_top_purchasing_product_doc?", "response": "To use the report.sh_purchase_reports.sh_top_purchasing_product_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_top_purchasing_product_doc", "table_name": ""}
+{"text": "What foreign keys exist in res.config?", "response": "The res.config model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.config", "table_name": ""}
+{"text": "What are the available fields for stock.warehouse.orderpoint?", "response": "The stock.warehouse.orderpoint model has 114 fields: active, snoozed_until, product_tmpl_id, product_id, product_category_id, product_uom, product_uom_name, product_min_qty, product_max_qty, qty_multiple, group_id, allowed_location_ids, rule_ids, json_lead_days_popover, lead_days_date, allowed_route_ids, route_id, qty_on_hand, qty_forecast, qty_to_order, show_bom, bom_id, show_supplier, location_id, name, source_location_id, action_to_take, trigger, start_date, start_month, end_date, end_month, is_replenish_document_created, purchase_request_id, purchase_order_id, material_request_id, internal_transfer_id, replenish_document_status, is_mo_created, periods, run_rate_days, safety_stock, safety_stock_select, stock_days, responsible_id, branch_id, average_quantity_last_year, lead_days_last_year, average_quantity_run_rate_days, lead_days_run_rate_days, run_rate_type, company_id, warehouse_id, filter_warehouse_id, is_minimum_quantity, is_safety_stock_quantity, select_period, notification_user_ids, pr_status, rfq_status, itr_status, mr_status, from_days_before, run_rate_qty, lead_days, period_date, period_month, run_rate_period_before, run_rate_period_after, qty_check, is_low_stock, path, quantity_restock, is_quantity_restock, qty_restock, supplier_id, 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. Field types distribution: boolean: 17, date: 5, many2one: 25, char: 13, float: 16, one2many: 5, many2many: 7, selection: 16, integer: 6, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.warehouse.orderpoint", "table_name": ""}
+{"text": "What foreign keys exist in purchase.request.line.make.purchase.order.item?", "response": "The purchase.request.line.make.purchase.order.item model has 9 relational fields: wiz_id -> purchase.request.line.make.purchase.order; line_id -> purchase.request.line; request_id -> purchase.request; product_id -> product.product; product_uom_id -> uom.uom; destination_location_id -> stock.location; dest_loc_id -> stock.warehouse; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.request.line.make.purchase.order.item", "table_name": ""}
+{"text": "Can you explain the purpose of resource.calendar.attendance?", "response": "The resource.calendar.attendance model represents Work Detail in the ERP system. It contains 20 fields and is used to manage work detail data. Key fields include: name, dayofweek, date_from, date_to, hour_from, hour_to, calendar_id, day_period, resource_id, week_type, two_weeks_calendar, display_type, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "resource.calendar.attendance", "table_name": ""}
+{"text": "Tell me about the mailing.list model.", "response": "The mailing.list model represents Mailing List in the ERP system. It contains 15 fields and is used to manage mailing list data. Key fields include: name, active, contact_nbr, contact_ids, subscription_ids, is_public, website_popup_ids, toast_content, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mailing.list", "table_name": ""}
+{"text": "Tell me about the ir.qweb.field.html model.", "response": "The ir.qweb.field.html model represents Qweb Field HTML in the ERP system. It contains 3 fields and is used to manage qweb field html data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb.field.html", "table_name": ""}
+{"text": "What are the relationships in pos.product.bom?", "response": "The pos.product.bom model has 8 relational fields: product_id -> product.product; product_tmpl_id -> product.template; product_uom_id -> uom.uom; product_bom_line_ids -> pos.product.bom.line; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.product.bom", "table_name": ""}
+{"text": "What does the report.sale.report_saleproforma model represent?", "response": "The report.sale.report_saleproforma model represents Proforma Report in the ERP system. It contains 3 fields and is used to manage proforma report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sale.report_saleproforma", "table_name": ""}
+{"text": "What are common use cases for payable.flow.wizard?", "response": "To use the payable.flow.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "payable.flow.wizard", "table_name": ""}
+{"text": "What is the restaurant.table model?", "response": "The restaurant.table model represents Restaurant Table in the ERP system. It contains 17 fields and is used to manage restaurant table data. Key fields include: name, floor_id, shape, position_h, position_v, width, height, seats, color, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "restaurant.table", "table_name": ""}
+{"text": "Describe the implementation of ir.model.constraint.", "response": "The ir.model.constraint model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.model.constraint", "table_name": ""}
+{"text": "How do I use the res.partner.industry model?", "response": "To use the res.partner.industry 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.partner.industry", "table_name": ""}
+{"text": "How does convert.revenue relate to other models?", "response": "The convert.revenue model has 4 relational fields: revenue_account_id -> account.account; expenses_account_id -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "convert.revenue", "table_name": ""}
+{"text": "How is report.sh_purchase_reports.sh_po_product_indent_doc used in the system?", "response": "The report.sh_purchase_reports.sh_po_product_indent_doc model represents Purchase product indent report abstract model in the ERP system. It contains 3 fields and is used to manage purchase product indent report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_po_product_indent_doc", "table_name": ""}
+{"text": "Show me the fields of purchase.requisition.", "response": "The purchase.requisition model has 79 fields: name, origin, order_count, ordering_date, user_id, description, company_id, purchase_ids, line_ids, product_id, is_quantity_copy, currency_id, warehouse_id, picking_type_id, purchase_id, type_id, purchase_request_id, branch_id, account_tag_ids, analytic_accounting, destination_warehouse, date_end, schedule_date, set_single_delivery_date, set_single_delivery_destination, approval_matrix_id, is_blanket_order_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state, bo_state, bo_state1, state1, state2, bo_state2, state_blanket_order, partner_id, is_bo_confirm, vendor_id, show_analytic_tags, is_goods_orders, is_services_orders, is_assets_orders, 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. Field types distribution: char: 8, integer: 6, date: 4, many2one: 20, text: 2, one2many: 7, selection: 10, many2many: 3, boolean: 15, datetime: 4.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.requisition", "table_name": ""}
+{"text": "What are the available fields for sh.purchase.product.indent.xls?", "response": "The sh.purchase.product.indent.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.purchase.product.indent.xls", "table_name": ""}
+{"text": "What methods are available in _unknown?", "response": "The _unknown model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "_unknown", "table_name": ""}
+{"text": "What does the purchase.order.line.extract model represent?", "response": "The purchase.order.line.extract model represents Purchase Order Line Extract in the ERP system. It contains 18 fields and is used to manage purchase order line extract data. Key fields include: sequence, tick, product_template_id, name, date_planned, product_qty, price_unit, destination_warehouse_id, extract_id, product_id, product_uom, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order.line.extract", "table_name": ""}
+{"text": "How is mr_line.pr.wizard_line implemented technically?", "response": "The mr_line.pr.wizard_line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mr_line.pr.wizard_line", "table_name": ""}
+{"text": "Describe the many2many relations for ir.qweb.field.date.", "response": "The ir.qweb.field.date model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb.field.date", "table_name": ""}
+{"text": "What operations can I perform on hr.job?", "response": "To use the hr.job model, you need to provide values for required fields: name, state. Readonly fields: expected_employees, no_of_employee, state, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "hr.job", "table_name": ""}
+{"text": "Describe the account.journal model in Odoo.", "response": "The account.journal model represents Journal in the ERP system. It contains 92 fields and is used to manage journal data. Key fields include: kanban_dashboard, kanban_dashboard_graph, json_activity_data, show_on_dashboard, color, check_manual_sequencing, check_sequence_id, check_next_number, check_printing_payment_method_selected, edi_format_ids, compatible_edi_ids, sequence_id, sequence_number_next, refund_sequence_id, refund_sequence_number_next, pos_payment_method_ids, name, code, active, type_control_ids, account_control_ids, default_account_type, default_account_id, payment_debit_account_id, payment_credit_account_id, suspense_account_id, restrict_mode_hash_table, sequence, invoice_reference_type, invoice_reference_model, currency_id, company_id, country_code, refund_sequence, sequence_override_regex, inbound_payment_method_ids, outbound_payment_method_ids, at_least_one_inbound, at_least_one_outbound, profit_account_id, loss_account_id, company_partner_id, bank_account_id, bank_statements_source, bank_acc_number, bank_id, sale_activity_type_id, sale_activity_user_id, sale_activity_note, alias_id, alias_domain, alias_name, journal_group_ids, secure_sequence_id, use_reconcile, branch_id, type, is_fiscal_book_exclude, pos_method_type, decimal_rounding, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.journal", "table_name": ""}
+{"text": "What data can be stored in payment.transaction?", "response": "The payment.transaction model has 40 fields: date, acquirer_id, provider, type, state, state_message, amount, fees, currency_id, reference, acquirer_reference, partner_id, partner_name, partner_lang, partner_email, partner_zip, partner_address, partner_city, partner_country_id, partner_phone, html_3ds, callback_model_id, callback_res_id, callback_method, callback_hash, return_url, is_processed, payment_token_id, payment_id, invoice_ids, invoice_ids_nbr, sale_order_ids, sale_order_ids_nbr, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 4, many2one: 9, selection: 4, text: 1, monetary: 2, char: 13, integer: 4, boolean: 1, many2many: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "payment.transaction", "table_name": ""}
+{"text": "Can you explain the purpose of gamification.goal.definition?", "response": "The gamification.goal.definition model represents Gamification Goal Definition in the ERP system. It contains 26 fields and is used to manage gamification goal definition data. Key fields include: name, description, monetary, suffix, full_suffix, computation_mode, display_mode, model_id, model_inherited_ids, field_id, field_date_id, domain, batch_mode, batch_distinctive_field, batch_user_expression, compute_code, condition, action_id, res_id_field, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "gamification.goal.definition", "table_name": ""}
+{"text": "What are the available fields for ir.qweb.field.html?", "response": "The ir.qweb.field.html model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.html", "table_name": ""}
+{"text": "What business logic is in warranty.settings?", "response": "To use the warranty.settings model, you need to provide values for required fields: company_id, currency_id, show_line_subtotals_tax_selection, default_picking_policy. Readonly fields: company_count, active_user_count, language_count, company_name, company_informations, geoloc_provider_techname, fail_counter, has_accounting_entries, has_chart_of_accounts, country_code, website_language_count, is_encode_uom_days, company_currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "warranty.settings", "table_name": ""}
+{"text": "What are the available fields for purchase.tender.create.lines.wizard?", "response": "The purchase.tender.create.lines.wizard model has 18 fields: purchase_tender_lines, product_id, product_description, remaning_qty, tender_qty, uom, pr_line_id, request_id, destination_warehouse, analytics_tag_ids, schedule_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, char: 2, float: 2, many2many: 1, date: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.tender.create.lines.wizard", "table_name": ""}
+{"text": "What business logic is in account.loan.post?", "response": "To use the account.loan.post model, you need to provide values for required fields: loan_id, journal_id, account_id. Readonly fields: loan_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.loan.post", "table_name": ""}
+{"text": "Describe the implementation of create.purchase.request.direct.lines.", "response": "The create.purchase.request.direct.lines model is defined in module: equip3_purchase_other_operation_cont. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "create.purchase.request.direct.lines", "table_name": ""}
+{"text": "How is acrux.chat.base.message used in the system?", "response": "The acrux.chat.base.message model represents Base Message in the ERP system. It contains 7 fields and is used to manage base message data. Key fields include: text, ttype, res_model, res_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "acrux.chat.base.message", "table_name": ""}
+{"text": "What fields does account.tax.map.sales.line have?", "response": "The account.tax.map.sales.line model has 17 fields: company_id, sales_tax_id, target_company, target_sales_tax, map_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, line_ids, child_company_id, ownership, sales_line_ids, purchase_line_ids. Field types distribution: many2one: 8, integer: 1, char: 1, datetime: 3, one2many: 3, float: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.tax.map.sales.line", "table_name": ""}
+{"text": "Show me the fields of acrux.chat.message.", "response": "The acrux.chat.message model has 23 fields: name, msgid, contact_id, connector_id, date_message, from_me, company_id, error_msg, user_id, ttype, event, template_id, is_direct, text, res_model, res_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 7, datetime: 4, boolean: 2, selection: 2, text: 1, integer: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "acrux.chat.message", "table_name": ""}
+{"text": "What modules define res.users.apikeys?", "response": "The res.users.apikeys model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.apikeys", "table_name": ""}
+{"text": "What operations can I perform on restaurant.printer?", "response": "To use the restaurant.printer 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "restaurant.printer", "table_name": ""}
+{"text": "What are the available fields for sales.margin.xls?", "response": "The sales.margin.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sales.margin.xls", "table_name": ""}
+{"text": "What business logic is in account.edi.format?", "response": "To use the account.edi.format model, you need to provide values for required fields: code. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.edi.format", "table_name": ""}
+{"text": "What is the report.equip3_pos_report.report_open_session model?", "response": "The report.equip3_pos_report.report_open_session model represents Point of Sale Details in the ERP system. It contains 3 fields and is used to manage point of sale details data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_pos_report.report_open_session", "table_name": ""}
+{"text": "What is the mr.internal_transfer_line model?", "response": "The mr.internal_transfer_line model represents mr.internal_transfer_line in the ERP system. It contains 22 fields and is used to manage mr.internal_transfer_line data. Key fields include: mr_id, no, product_id, description, uom_id, source_location, source_warehouse_id, current_qty, virtual_available, qty_transfer, mr_ir_wizard, mr_line_id, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mr.internal_transfer_line", "table_name": ""}
+{"text": "What are the available fields for res.users.tag?", "response": "The res.users.tag model has 8 fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.users.tag", "table_name": ""}
+{"text": "Describe the implementation of hr.employee.base.", "response": "The hr.employee.base model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hr.employee.base", "table_name": ""}
+{"text": "Describe the implementation of product.removal.", "response": "The product.removal model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.removal", "table_name": ""}
+{"text": "How do I use the sh.base.send.whatsapp.number.wizard model?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.base.send.whatsapp.number.wizard", "table_name": ""}
+{"text": "Describe the ks_dashboard_ninja.board_template model in Odoo.", "response": "The ks_dashboard_ninja.board_template model represents Dashboard Ninja Template in the ERP system. It contains 13 fields and is used to manage dashboard ninja template data. Key fields include: name, ks_gridstack_config, ks_item_count, ks_template_type, ks_dashboard_item_ids, ks_dashboard_board_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.board_template", "table_name": ""}
+{"text": "What fields does stock.warehouse have?", "response": "The stock.warehouse model has 98 fields: active, partner_id, view_location_id, lot_stock_id, route_ids, wh_input_stock_loc_id, wh_qc_stock_loc_id, wh_output_stock_loc_id, wh_pack_stock_loc_id, mto_pull_id, pick_type_id, pack_type_id, out_type_id, in_type_id, int_type_id, crossdock_route_id, reception_route_id, delivery_route_id, warehouse_count, resupply_wh_ids, resupply_route_ids, show_resupply, sequence, manufacture_to_resupply, manufacture_pull_id, manufacture_mto_pull_id, pbm_mto_pull_id, sam_rule_id, manu_type_id, pbm_type_id, sam_type_id, manufacture_steps, pbm_route_id, pbm_loc_id, sam_loc_id, spacex, spacey, spacez, planimetry_image, count_sl, pos_type_id, buy_to_resupply, buy_pull_id, default_delivery_location_id, driver_ids, name, code, company_id, branch_id, lot_scrap_id, lot_expired_id, street, street2, zip, city, state_id, country_id, phone, responsible_users, reception_steps, delivery_steps, default_receipt_location_id, is_external_link, stock_count_cycle, pos_branch_id, analytic_tag_ids, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 10, many2one: 42, many2many: 6, integer: 12, one2many: 6, selection: 5, binary: 1, char: 11, date: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.warehouse", "table_name": ""}
+{"text": "What operations can I perform on invoice.recurring?", "response": "To use the invoice.recurring model, you need to provide values for required fields: name, partner_id, start_date, type, journal_id, state, recurring_interval, recurring_interval_unit, stop_recurring_interval_unit. Readonly fields: name, journal_id, stop_recurring_interval_unit, online_signature, invoice_filter_type_domain, sh_invoice_recurring_count, sh_bill_recurring_count, sh_cust_credit_recurring_count, sh_vendor_credit_recurring_count, sh_sale_receipt_recurring_count, sh_purchase_receipt_recurring_count, sh_journal_entry_recurring_count, subtotal, total, total_taxes, invoice_ids, remaining_journal_entry, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "invoice.recurring", "table_name": ""}
+{"text": "Show me the relational structure of sh.purchase.tags.", "response": "The sh.purchase.tags model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.tags", "table_name": ""}
+{"text": "What is the limit.request.wizard model?", "response": "The limit.request.wizard model represents Limit Request Wizard in the ERP system. It contains 7 fields and is used to manage limit request wizard data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "limit.request.wizard", "table_name": ""}
+{"text": "What are the available fields for product.expire.report?", "response": "The product.expire.report model has 8 fields: report_selection, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.expire.report", "table_name": ""}
+{"text": "List all fields in the project.delete.wizard model.", "response": "The project.delete.wizard model has 10 fields: project_ids, task_count, projects_archived, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, integer: 2, boolean: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.delete.wizard", "table_name": ""}
+{"text": "List all fields in the receipt.payment.line.debit model.", "response": "The receipt.payment.line.debit model has 20 fields: line_id, currency_id, invoice_id, account_id, invoice_date, invoice_date_due, original_amount, base_amount, original_unreconcile, base_unreconcile, is_full_reconcile, amount, payment_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, date: 2, monetary: 5, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "receipt.payment.line.debit", "table_name": ""}
+{"text": "What foreign keys exist in auth_totp.wizard?", "response": "The auth_totp.wizard model has 3 relational fields: user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "auth_totp.wizard", "table_name": ""}
+{"text": "Show me the relational structure of base_import.import.", "response": "The base_import.import model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.import", "table_name": ""}
+{"text": "Show me the fields of account.payment.register.payment.difference.line.", "response": "The account.payment.register.payment.difference.line model has 14 fields: name, payment_register_id, account_id, payment_amount, currency_id, payment_difference, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 6, monetary: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.payment.register.payment.difference.line", "table_name": ""}
+{"text": "Tell me about the asset.cip.line model.", "response": "The asset.cip.line model represents asset.cip.line in the ERP system. It contains 15 fields and is used to manage asset.cip.line data. Key fields include: product_id, label, account_id, amount, cip_id, move_id, move_check, move_posted_check, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "asset.cip.line", "table_name": ""}
+{"text": "Show me the relational structure of purchase.price.history.", "response": "The purchase.price.history model has 7 relational fields: name -> purchase.order.line; partner_id -> res.partner; variant_id -> product.product; purchase_order_id -> purchase.order; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.price.history", "table_name": ""}
+{"text": "What is the checklist.reason model?", "response": "The checklist.reason model represents checklist.reason in the ERP system. It contains 8 fields and is used to manage checklist.reason data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "checklist.reason", "table_name": ""}
+{"text": "How to create records in list.order?", "response": "To use the list.order 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "list.order", "table_name": ""}
+{"text": "What are the relationships in report.equip3_purchase_other_operation.report_analyze_quot?", "response": "The report.equip3_purchase_other_operation.report_analyze_quot model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_purchase_other_operation.report_analyze_quot", "table_name": ""}
+{"text": "What are the available fields for ks.sales.forecast?", "response": "The ks.sales.forecast model has 69 fields: ks_name, ks_is_file, ks_file_type, ks_import_file, ks_file_name, ks_is_method_change, ks_forecast_method, ks_default_forecast_method, ks_predicted_forecast_method, ks_model, ks_start_date, ks_end_date, ks_forecast_base, ks_product_ids, ks_p, ks_d, ks_q, ks_P, ks_D, ks_Q, ks_m, ks_trend, ks_forecast_unit, ks_forecast_period, ks_is_predicted, ks_is_predicted_method, ks_chart_data, ks_report_data, ks_graph_view, ks_outcome, ks_danger_outcome, ks_resp, ks_resd, ks_resq, ks_sp, ks_sd, ks_sq, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 7, boolean: 11, selection: 8, binary: 1, many2one: 6, datetime: 5, many2many: 3, integer: 20, text: 2, one2many: 4, date: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks.sales.forecast", "table_name": ""}
+{"text": "Describe the many2many relations for sh.purchase.product.indent.wizard.", "response": "The sh.purchase.product.indent.wizard model has 6 relational fields: sh_partner_ids -> res.partner; sh_category_ids -> product.category; company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_partner_ids, sh_category_ids, company_ids, branch_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.product.indent.wizard", "table_name": ""}
+{"text": "What does the report.equip3_accounting_reports.journal_entry_report model represent?", "response": "The report.equip3_accounting_reports.journal_entry_report model represents report.equip3_accounting_reports.journal_entry_report in the ERP system. It contains 3 fields and is used to manage report.equip3_accounting_reports.journal_entry_report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.journal_entry_report", "table_name": ""}
+{"text": "What are the available fields for crm.stage?", "response": "The crm.stage model has 17 fields: name, sequence, is_won, requirements, team_id, fold, team_count, color, change_probability, probability, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 4, boolean: 3, text: 1, many2one: 3, float: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.stage", "table_name": ""}
+{"text": "What are common use cases for sh.fiscal.year?", "response": "To use the sh.fiscal.year model, you need to provide values for required fields: name, code, date_start, date_end, company_id. Readonly fields: name, code, date_start, date_end, period_ids, company_id, hide_button, move_id, summary_move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.fiscal.year", "table_name": ""}
+{"text": "What are the available fields for sale.report.salesperson.xls?", "response": "The sale.report.salesperson.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.report.salesperson.xls", "table_name": ""}
+{"text": "What is the milestone.contract.template.checklist model?", "response": "The milestone.contract.template.checklist model represents Checklist Milestone Contract Term Template in the ERP system. It contains 10 fields and is used to manage checklist milestone contract term template data. Key fields include: template_id, name, desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "milestone.contract.template.checklist", "table_name": ""}
+{"text": "What are common use cases for assets.approval.matrix.line?", "response": "To use the assets.approval.matrix.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: sequence2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assets.approval.matrix.line", "table_name": ""}
+{"text": "How to create records in report.sh_purchase_reports.sh_po_product_indent_doc?", "response": "To use the report.sh_purchase_reports.sh_po_product_indent_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_po_product_indent_doc", "table_name": ""}
+{"text": "Tell me about the account.tax.group model.", "response": "The account.tax.group model represents Tax Group in the ERP system. It contains 12 fields and is used to manage tax group data. Key fields include: name, sequence, property_tax_payable_account_id, property_tax_receivable_account_id, property_advance_tax_payment_account_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.tax.group", "table_name": ""}
+{"text": "What are the relationships in base_import.tests.models.preview?", "response": "The base_import.tests.models.preview model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.preview", "table_name": ""}
+{"text": "What are the available fields for stock.return.picking.inter.company?", "response": "The stock.return.picking.inter.company model has 12 fields: product_id, quantity, uom_id, wizard_id, move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.return.picking.inter.company", "table_name": ""}
+{"text": "Tell me about the purchase.agreement model.", "response": "The purchase.agreement model represents Purchase Agreement in the ERP system. It contains 100 fields and is used to manage purchase agreement data. Key fields include: name, rfq_count, order_count, sh_vender_id, user_id, sh_agreement_deadline, sh_source, sh_purchase_agreement_line_ids, compute_custom_boolean, sh_manage_tender_document, document_count, is_goods_orders, is_services_orders, purchase_request_id, sh_purchase_user_id, sh_agreement_type, partner_ids, days_left, analytic_accounting, account_tag_ids, branch_id, destination_warehouse_id, set_single_delivery_destination, set_single_delivery_date, comparison_ids, tender_scope, tender_name, company_id, currency_id, amount_total, is_price_ratting_rfq_tender, show_analytic_tags, sh_order_date, sh_delivery_date, state, state1, state4, state2, pt_state, state3, state5, approval_matrix, amount, approval_matrix_line_ids, user_approval_ids, current_user, partner_id, approver, line_approve, is_approve_button, approval_matrix_line_id, sh_bid_agreement_deadline, sh_bid_selection_agreement_deadline, is_purchase_tender_approval_matrix, term_condition, term_condition_box, sh_notes, sh_partner_id, vendor_names, purchase_order_ids, is_assets_orders, legal_documents_ids, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.agreement", "table_name": ""}
+{"text": "How to create records in purchase.tender.create.wizard?", "response": "To use the purchase.tender.create.wizard model, you need to provide values for required fields: company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.tender.create.wizard", "table_name": ""}
+{"text": "How is ks_dashboard_ninja.board used in the system?", "response": "The ks_dashboard_ninja.board model represents Dashboard Ninja in the ERP system. It contains 30 fields and is used to manage dashboard ninja data. Key fields include: name, ks_dashboard_items_ids, ks_dashboard_menu_name, ks_dashboard_top_menu_id, ks_dashboard_client_action_id, ks_dashboard_menu_id, ks_dashboard_state, ks_dashboard_active, ks_dashboard_group_access, ks_dashboard_start_date, ks_dashboard_end_date, ks_date_filter_selection, ks_data_formatting, ks_gridstack_config, ks_dashboard_default_template, ks_set_interval, ks_dashboard_menu_sequence, ks_child_dashboard_ids, ks_dashboard_defined_filters_ids, ks_dashboard_custom_filters_ids, ks_croessel_speed, ks_dashboard_icon_budget, ks_dashboard_menu_icon_class, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.board", "table_name": ""}
+{"text": "Can you explain the purpose of account.fiscal.position.account.template?", "response": "The account.fiscal.position.account.template model represents Accounts Mapping Template of Fiscal Position in the ERP system. It contains 10 fields and is used to manage accounts mapping template of fiscal position data. Key fields include: position_id, account_src_id, account_dest_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.fiscal.position.account.template", "table_name": ""}
+{"text": "What operations can I perform on sale.order.cancel?", "response": "To use the sale.order.cancel model, you need to provide values for required fields: order_id. Readonly fields: display_invoice_alert, display_delivery_alert, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.cancel", "table_name": ""}
+{"text": "Tell me about the report.sh_inventory_mrp_qc.mrp_quality_alert_doc model.", "response": "The report.sh_inventory_mrp_qc.mrp_quality_alert_doc model represents MRP quality alert report abstract model in the ERP system. It contains 3 fields and is used to manage mrp quality alert report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_inventory_mrp_qc.mrp_quality_alert_doc", "table_name": ""}
+{"text": "Describe the many2many relations for receipt.payment.line.debit.", "response": "The receipt.payment.line.debit model has 7 relational fields: line_id -> receipt.payment; currency_id -> res.currency; invoice_id -> account.move; account_id -> account.account; payment_id -> account.payment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "receipt.payment.line.debit", "table_name": ""}
+{"text": "Describe the many2many relations for website.rewrite.", "response": "The website.rewrite model has 4 relational fields: website_id -> website; route_id -> website.route; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.rewrite", "table_name": ""}
+{"text": "Describe the field structure of bve.view.line.", "response": "The bve.view.line model has 27 fields: name, sequence, bve_view_id, model_id, model_name, table_alias, join_model_id, field_id, field_name, ttype, description, relation, join_node, left_join, row, column, measure, in_list, list_attr, view_field_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 10, integer: 2, many2one: 6, boolean: 5, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "bve.view.line", "table_name": ""}
+{"text": "What does the ir.default model represent?", "response": "The ir.default model represents Default Values in the ERP system. It contains 12 fields and is used to manage default values data. Key fields include: field_id, user_id, company_id, condition, json_value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.default", "table_name": ""}
+{"text": "How is pos.voucher.use.history used in the system?", "response": "The pos.voucher.use.history model represents Histories use voucher of customer in the ERP system. It contains 13 fields and is used to manage histories use voucher of customer data. Key fields include: pos_order_id, payment_id, voucher_id, value, used_date, cashier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.voucher.use.history", "table_name": ""}
+{"text": "What foreign keys exist in ir.qweb.field.barcode?", "response": "The ir.qweb.field.barcode model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb.field.barcode", "table_name": ""}
+{"text": "Tell me about the sh.top.selling.products model.", "response": "The sh.top.selling.products model represents Top Selling XLS in the ERP system. It contains 9 fields and is used to manage top selling xls data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.top.selling.products", "table_name": ""}
+{"text": "How is sale.adv.wizard.product.line implemented technically?", "response": "The sale.adv.wizard.product.line model is defined in module: equip3_sale_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.adv.wizard.product.line", "table_name": ""}
+{"text": "How is base_import.tests.models.o2m.child implemented technically?", "response": "The base_import.tests.models.o2m.child model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.o2m.child", "table_name": ""}
+{"text": "How to query pos.account.cashbox.line data?", "response": "To use the pos.account.cashbox.line model, you need to provide values for required fields: coin_value. Readonly fields: subtotal, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.account.cashbox.line", "table_name": ""}
+{"text": "What does the account.setup.bank.manual.config model represent?", "response": "The account.setup.bank.manual.config model represents Bank setup manual config in the ERP system. It contains 30 fields and is used to manage bank setup manual config data. Key fields include: res_partner_bank_id, new_journal_name, linked_journal_id, bank_bic, num_journals_without_account, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, active, acc_type, acc_number, sanitized_acc_number, acc_holder_name, partner_id, bank_id, bank_name, sequence, currency_id, company_id, journal_id, aba_routing, acc_holder_email, acc_holder_type, acc_holder_resident, acc_holder_address.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.setup.bank.manual.config", "table_name": ""}
+{"text": "What models are connected to report.dynamic_accounts_report.trial_balance?", "response": "The report.dynamic_accounts_report.trial_balance model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.trial_balance", "table_name": ""}
+{"text": "Describe the many2many relations for utm.source.", "response": "The utm.source model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "utm.source", "table_name": ""}
+{"text": "Describe the implementation of account.pettycash.analysis.", "response": "The account.pettycash.analysis model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.pettycash.analysis", "table_name": ""}
+{"text": "Which fields in report.reordering are computed?", "response": "The report.reordering model is defined in module: allfresh_mod_report_reordering. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.reordering", "table_name": ""}
+{"text": "How is sh.correct.qc.measurement implemented technically?", "response": "The sh.correct.qc.measurement model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.correct.qc.measurement", "table_name": ""}
+{"text": "How do I use the res.partner.title model?", "response": "To use the res.partner.title 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.partner.title", "table_name": ""}
+{"text": "What business logic is in portal.wizard?", "response": "To use the portal.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "portal.wizard", "table_name": ""}
+{"text": "What methods are available in report.equip3_pos_general.pos_sale_report_template?", "response": "The report.equip3_pos_general.pos_sale_report_template model is defined in module: equip3_pos_general. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_pos_general.pos_sale_report_template", "table_name": ""}
+{"text": "Describe the payable.opening.balance model in Odoo.", "response": "The payable.opening.balance model represents payable.opening.balance in the ERP system. It contains 14 fields and is used to manage payable.opening.balance data. Key fields include: partner_opening_bal_id, vendor_id, invoice, date, description, due_date, amount_due, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "payable.opening.balance", "table_name": ""}
+{"text": "What modules define mrp.labor.group?", "response": "The mrp.labor.group model is defined in module: equip3_manuf_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.labor.group", "table_name": ""}
+{"text": "What does the ir.qweb.field.html model represent?", "response": "The ir.qweb.field.html model represents Qweb Field HTML in the ERP system. It contains 3 fields and is used to manage qweb field html data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb.field.html", "table_name": ""}
+{"text": "Describe the reset.view.arch.wizard model in Odoo.", "response": "The reset.view.arch.wizard model represents Reset View Architecture Wizard in the ERP system. It contains 14 fields and is used to manage reset view architecture wizard data. Key fields include: view_id, view_name, has_diff, arch_diff, reset_mode, compare_view_id, arch_to_compare, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "reset.view.arch.wizard", "table_name": ""}
+{"text": "How is customer.deposit.wizard implemented technically?", "response": "The customer.deposit.wizard model is defined in module: equip3_accounting_deposit. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "customer.deposit.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for service.work.order.checklist.", "response": "The service.work.order.checklist model has 3 relational fields: swo_id -> service.work.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "service.work.order.checklist", "table_name": ""}
+{"text": "How does crm.team relate to other models?", "response": "The crm.team model has 20 relational fields: currency_id -> res.currency; favorite_user_ids -> res.users; alias_id -> mail.alias; website_ids -> website; rma_ids -> dev.rma.rma; pos_config_ids -> pos.config; user_id -> res.users; company_id -> res.company; member_ids -> res.users; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users; alias_model_id -> ir.model; alias_user_id -> res.users; alias_parent_model_id -> ir.model. Many2many fields: favorite_user_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.team", "table_name": ""}
+{"text": "What are common use cases for payment.acquirer.onboarding.wizard?", "response": "To use the payment.acquirer.onboarding.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "List all fields in the repair.fee model.", "response": "The repair.fee model has 20 fields: repair_id, company_id, currency_id, name, product_id, product_uom_qty, price_unit, product_uom, product_uom_category_id, price_subtotal, tax_id, invoice_line_id, invoiced, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, text: 1, float: 3, many2many: 1, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "repair.fee", "table_name": ""}
+{"text": "What is the field.conditional.access model?", "response": "The field.conditional.access model represents Fields Conditional Access in the ERP system. It contains 18 fields and is used to manage fields conditional access data. Key fields include: access_management_id, model_id, model_name, attrs_field_id, domain_field_id, domain_field_relation, attrs_type, field_attrs, field_domain, apply_attrs, apply_field_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "field.conditional.access", "table_name": ""}
+{"text": "What does the ir.qweb.field.selection model represent?", "response": "The ir.qweb.field.selection model represents Qweb Field Selection in the ERP system. It contains 3 fields and is used to manage qweb field selection data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb.field.selection", "table_name": ""}
+{"text": "What is the account.tax.template model?", "response": "The account.tax.template model represents Templates for Taxes in the ERP system. It contains 25 fields and is used to manage templates for taxes data. Key fields include: chart_template_id, type_tax_use, tax_scope, amount_type, active, children_tax_ids, sequence, amount, price_include, include_base_amount, analytic, invoice_repartition_line_ids, refund_repartition_line_ids, tax_group_id, tax_exigibility, cash_basis_transition_account_id, name, description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.tax.template", "table_name": ""}
+{"text": "What methods are available in limit.approval.matrix?", "response": "The limit.approval.matrix model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "limit.approval.matrix", "table_name": ""}
+{"text": "What operations can I perform on sale.advance.payment.inv?", "response": "To use the sale.advance.payment.inv model, you need to provide values for required fields: advance_payment_method. Readonly fields: has_down_payments, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.advance.payment.inv", "table_name": ""}
+{"text": "Describe the many2many relations for resource.mixin.", "response": "The resource.mixin model has 3 relational fields: resource_id -> resource.resource; company_id -> res.company; resource_calendar_id -> resource.calendar. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "resource.mixin", "table_name": ""}
+{"text": "What models are connected to view.data?", "response": "The view.data model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "view.data", "table_name": ""}
+{"text": "How does purchase.request.allocation relate to other models?", "response": "The purchase.request.allocation model has 8 relational fields: purchase_request_line_id -> purchase.request.line; company_id -> res.company; stock_move_id -> stock.move; purchase_line_id -> purchase.order.line; product_id -> product.product; product_uom_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.request.allocation", "table_name": ""}
+{"text": "What is the all.redeem.rule model?", "response": "The all.redeem.rule model represents all redeem rule in the ERP system. It contains 12 fields and is used to manage all redeem rule data. Key fields include: name, min_amt, max_amt, reward_amt, loyality_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "all.redeem.rule", "table_name": ""}
+{"text": "How is account.bank.statement.line.wizard used in the system?", "response": "The account.bank.statement.line.wizard model represents Account Bank Statement Line Wizard in the ERP system. It contains 7 fields and is used to manage account bank statement line wizard data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.bank.statement.line.wizard", "table_name": ""}
+{"text": "What are the available fields for product.ratio.line?", "response": "The product.ratio.line model has 16 fields: active, uom_id, product_id, product_tmpl_id, description, ratio, uom_ref_id, product_variant_ids, is_custom_uom, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 2, many2one: 6, char: 2, float: 1, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.ratio.line", "table_name": ""}
+{"text": "How do I use the pos.payment.report model?", "response": "To use the pos.payment.report model, you need to provide values for required fields: none. Readonly fields: date, payment_date, payment_method_id, config_id, order_id, session_id, company_id, pos_branch_id, amount, currency_id, partner_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.payment.report", "table_name": ""}
+{"text": "What models are connected to rn.approval_matrix_line?", "response": "The rn.approval_matrix_line model has 7 relational fields: approver -> res.users; last_approved -> res.users; rn_approval_matrix_id1 -> rn.approval.matrix; picking_id -> stock.picking; approved_users -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: approver, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "rn.approval_matrix_line", "table_name": ""}
+{"text": "How is product.cancel implemented technically?", "response": "The product.cancel model is defined in module: equip3_pos_general. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.cancel", "table_name": ""}
+{"text": "Can you explain the purpose of snailmail.letter.missing.required.fields?", "response": "The snailmail.letter.missing.required.fields model represents Update address of partner in the ERP system. It contains 15 fields and is used to manage update address of partner data. Key fields include: partner_id, letter_id, street, street2, zip, city, state_id, country_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "snailmail.letter.missing.required.fields", "table_name": ""}
+{"text": "What modules define account.debit.note?", "response": "The account.debit.note model is defined in module: account_debit_note. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.debit.note", "table_name": ""}
+{"text": "Show me the fields of receipt.payment.matrix.reject.", "response": "The receipt.payment.matrix.reject model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "receipt.payment.matrix.reject", "table_name": ""}
+{"text": "How do I use the pos.loyalty.reward model?", "response": "To use the pos.loyalty.reward model, you need to provide values for required fields: name, type, coefficient, redeem_coefficient. Readonly fields: coefficient_note, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.loyalty.reward", "table_name": ""}
+{"text": "Describe the field structure of mailing.trace.", "response": "The mailing.trace model has 28 fields: trace_type, display_name, mail_mail_id, mail_mail_id_int, email, message_id, model, res_id, mass_mailing_id, campaign_id, ignored, scheduled, sent, exception, opened, replied, bounced, links_click_ids, clicked, state, failure_type, state_update, id, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 3, char: 4, many2one: 5, integer: 3, datetime: 12, one2many: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mailing.trace", "table_name": ""}
+{"text": "How do I use the report.equip3_accounting_reports.tax_report model?", "response": "To use the report.equip3_accounting_reports.tax_report model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.tax_report", "table_name": ""}
+{"text": "What modules define res.currency.rate?", "response": "The res.currency.rate model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.currency.rate", "table_name": ""}
+{"text": "List all fields in the account.cash.rounding model.", "response": "The account.cash.rounding model has 14 fields: name, rounding, strategy, profit_account_id, loss_account_id, rounding_method, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, float: 1, selection: 2, many2one: 5, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.cash.rounding", "table_name": ""}
+{"text": "What modules define account.payment.method?", "response": "The account.payment.method model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.payment.method", "table_name": ""}
+{"text": "What models are connected to pos.report.payment?", "response": "The pos.report.payment model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.report.payment", "table_name": ""}
+{"text": "Describe the account.budget.post model in Odoo.", "response": "The account.budget.post model represents Budgetary Position in the ERP system. It contains 11 fields and is used to manage budgetary position data. Key fields include: name, account_ids, company_id, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.budget.post", "table_name": ""}
+{"text": "Show me the relational structure of base.module.update.", "response": "The base.module.update model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.module.update", "table_name": ""}
+{"text": "What methods are available in product.warehouse.cost.wizard?", "response": "The product.warehouse.cost.wizard model is defined in module: equip3_accounting_stockoperation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.warehouse.cost.wizard", "table_name": ""}
+{"text": "What fields does meetings.salespersons have?", "response": "The meetings.salespersons model has 11 fields: salesperson_id, weightage, status, calendar_event_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 1, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "meetings.salespersons", "table_name": ""}
+{"text": "How does extract.rfq.wizard relate to other models?", "response": "The extract.rfq.wizard model has 3 relational fields: purchase_order_extract_ids -> purchase.order.line.extract; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "extract.rfq.wizard", "table_name": ""}
+{"text": "What foreign keys exist in change.password.wizard?", "response": "The change.password.wizard model has 3 relational fields: user_ids -> change.password.user; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "change.password.wizard", "table_name": ""}
+{"text": "What are the technical details of sh.top.purchasing.excel.extended?", "response": "The sh.top.purchasing.excel.extended model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.top.purchasing.excel.extended", "table_name": ""}
+{"text": "List all fields in the untaken.stock model.", "response": "The untaken.stock model has 18 fields: name, warehouse_id, location_ids, company_id, branch_id, create_sc, state, date_checked, untaken_stock_line_ids, stock_count, domain_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 6, many2many: 1, boolean: 1, selection: 1, datetime: 4, one2many: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "untaken.stock", "table_name": ""}
+{"text": "What business logic is in assets.approval.matrix?", "response": "To use the assets.approval.matrix model, you need to provide values for required fields: name, company_id, branch_id. Readonly fields: company_id, is_assets_approval, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assets.approval.matrix", "table_name": ""}
+{"text": "What foreign keys exist in account.loan.line?", "response": "The account.loan.line model has 6 relational fields: loan_id -> account.loan; long_term_loan_account_id -> account.account; currency_id -> res.currency; move_ids -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.loan.line", "table_name": ""}
+{"text": "Can you explain the purpose of pos.generate.efaktur.invoice?", "response": "The pos.generate.efaktur.invoice model represents Pos Generate Efaktur Invoice in the ERP system. It contains 11 fields and is used to manage pos generate efaktur invoice data. Key fields include: gen_efaktur_id, partner_id, account_move_id, l10n_id_tax_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.generate.efaktur.invoice", "table_name": ""}
+{"text": "How do I use the pmps.adv.wizard.product.line model?", "response": "To use the pmps.adv.wizard.product.line model, you need to provide values for required fields: none. Readonly fields: default_code, standard_price, uom_po_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pmps.adv.wizard.product.line", "table_name": ""}
+{"text": "Show me the fields of asset.asset.report.", "response": "The asset.asset.report model has 21 fields: name, date, depreciation_date, asset_id, asset_category_id, partner_id, state, installment_value, move_check, installment_nbr, depreciation_nbr, gross_value, posted_value, unposted_value, company_id, depreciation_value, salvage_value, value_residual, id, display_name, __last_update. Field types distribution: char: 2, date: 2, many2one: 4, selection: 1, float: 7, boolean: 1, integer: 3, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "asset.asset.report", "table_name": ""}
+{"text": "Tell me about the pos.sync.session.order.line model.", "response": "The pos.sync.session.order.line model represents Pos Sync Session Order Line in the ERP system. It contains 14 fields and is used to manage pos sync session order line data. Key fields include: uid, data, name, parent_id, product_int, qty, pos_session_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.sync.session.order.line", "table_name": ""}
+{"text": "Show me the fields of pos.cashier.change.wizard.", "response": "The pos.cashier.change.wizard model has 10 fields: start_datetime, end_datetime, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2one: 3, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.cashier.change.wizard", "table_name": ""}
+{"text": "What are common use cases for purchase.order.line?", "response": "To use the purchase.order.line model, you need to provide values for required fields: name, product_qty, price_unit, order_id, product_template_id. Readonly fields: product_uom_qty, product_uom_category_id, price_tax, company_id, invoice_lines, qty_invoiced, qty_to_invoice, currency_id, date_order, is_configurable_product, product_template_attribute_value_ids, qty_received_method, move_ids, agreement_id, cancel_lines, purchase_request_lines, sale_order_id, discount_type, purchase_req_budget, realized_amount, is_vendor_pricelist_line, branch_ids, gross_total, price_unit_uom, last_purchased_price, last_customer_purchase_price, destination_warehouse_id, date_planned, delivery_ref, vendor_bills_ref, readonly_price, actual_progress, remaining_progress, progress_paid, reference_purchase_price, purchase_line_cost_saving, total_cost_saving, cost_saving_percentage, partner_id, price_subtotal, price_total, total_price, discounted_value, state_delivery, product_type, virtual_available_at_date, scheduled_date, forecast_expected_date, free_qty_today, qty_available_today, qty_to_deliver, is_mto, display_qty_widget, cost_saving, payment_term_id, base_price, lead_time, feedback, company_size, capital_revenue, product_template_id, is_goods_orders, is_services_orders, dp_line, price_reduce, is_assets_orders, persentase_antar_badan, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.order.line", "table_name": ""}
+{"text": "What data can be stored in auditlog.autovacuum?", "response": "The auditlog.autovacuum model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "auditlog.autovacuum", "table_name": ""}
+{"text": "Tell me about the crm.send.message.mass model.", "response": "The crm.send.message.mass model represents Send Message Mass in the ERP system. It contains 10 fields and is used to manage send message mass data. Key fields include: message_chat_ids, conversation_id, connector_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.send.message.mass", "table_name": ""}
+{"text": "What does the ai.chat.session model represent?", "response": "The ai.chat.session model represents AI Chat Session in the ERP system. It contains 34 fields and is used to manage ai chat session data. Key fields include: name, user_id, config_id, state, session_summary, session_summary_message_count, session_summary_last_updated, auto_compress_enabled, compression_threshold, trim_ratio, message_count, last_activity, total_tokens_used, last_tokens_used, message_ids, job_ids, last_job_id, has_running_job, is_ai_renamed, is_quick_chat, quick_chat_model, quick_chat_res_id, cached_user_message_hash, cached_relevant_memories, cached_system_prompt, thinking_chain, last_frequent_actions_query, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ai.chat.session", "table_name": ""}
+{"text": "Can you explain the purpose of pos.coupon?", "response": "The pos.coupon model represents POS Coupon in the ERP system. It contains 32 fields and is used to manage pos coupon data. Key fields include: active, name, number, code, type_apply, product_ids, minimum_purchase_quantity, sequence_generate_method, manual_input_sequence, start_date, end_date, no_of_usage, no_of_used, coupon_program_id, company_id, state, reward_type, reward_product_ids, reward_quantity, reward_discount_type, reward_discount_amount, reward_max_discount_amount, use_history_ids, product_display_name, reward_product_display_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.coupon", "table_name": ""}
+{"text": "What methods are available in pos.global.discount?", "response": "The pos.global.discount model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.global.discount", "table_name": ""}
+{"text": "What are the relationships in sh.qc.measurement?", "response": "The sh.qc.measurement model has 3 relational fields: measurement_ids -> sh.qc.measurement.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.qc.measurement", "table_name": ""}
+{"text": "What are the available fields for acrux.chat.conversation?", "response": "The acrux.chat.conversation model has 31 fields: name, number, number_format, image_128, image_url, connector_id, res_partner_id, status, chat_message_ids, sellman_id, last_sent, last_received, last_received_first, company_id, team_id, border_color, crm_lead_id, sale_order_id, partner_sellman_id, room_id, room_name, session_status, team_ids, is_external_link, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 9, binary: 1, many2one: 10, selection: 1, one2many: 1, datetime: 6, many2many: 1, boolean: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "acrux.chat.conversation", "table_name": ""}
+{"text": "Which fields in account.cashbox.wizard.validate are computed?", "response": "The account.cashbox.wizard.validate model is defined in module: equip3_pos_cashbox. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.cashbox.wizard.validate", "table_name": ""}
+{"text": "Describe the implementation of account.payment.reconcile.", "response": "The account.payment.reconcile model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.payment.reconcile", "table_name": ""}
+{"text": "Describe the field structure of purchase.agreement.approval.matrix.", "response": "The purchase.agreement.approval.matrix model has 46 fields: name, company_id, branch_id, minimum_amt, maximum_amt, approval_matrix_purchase_agreement_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. Field types distribution: char: 7, many2one: 10, float: 2, one2many: 5, boolean: 6, selection: 3, date: 2, many2many: 2, integer: 5, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.agreement.approval.matrix", "table_name": ""}
+{"text": "What fields does change.password.wizard have?", "response": "The change.password.wizard model has 8 fields: user_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "change.password.wizard", "table_name": ""}
+{"text": "What data can be stored in base.language.import?", "response": "The base.language.import model has 12 fields: name, code, data, filename, overwrite, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, binary: 1, boolean: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.language.import", "table_name": ""}
+{"text": "Describe the field structure of purchase.order.history.", "response": "The purchase.order.history model has 18 fields: purchase_reorder, name, order_id, po_id, product_id, price_unit, product_qty, product_uom, currency_id, price_subtotal, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 7, char: 2, float: 2, monetary: 1, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.order.history", "table_name": ""}
+{"text": "Tell me about the sale.order model.", "response": "The sale.order model represents Sales Order in the ERP system. It contains 289 fields and is used to manage sales order data. Key fields include: origin, client_order_ref, reference, is_expired, require_signature, require_payment, create_date, user_id, pricelist_id, currency_id, invoice_count, invoice_ids, invoice_status, amount_by_group, currency_rate, fiscal_position_id, team_id, signature, signed_by, signed_on, amount_undiscounted, type_name, transaction_ids, authorized_transaction_ids, show_update_pricelist, tag_ids, applied_coupon_ids, generated_coupon_ids, reward_amount, no_code_promo_program_ids, code_promo_program_id, promo_code, sale_order_option_ids, purchase_order_count, incoterm, picking_policy, picking_ids, delivery_count, procurement_group_id, effective_date, expected_date, json_popover, show_json_popover, website_order_line, cart_quantity, only_services, is_abandoned_cart, cart_recovery_email_sent, website_id, conversation_id, internal_id, inter_transfer_count, client_order_id, discount_amt, discount_amt_line, warranty_sale, recurring_rule_type, recurring_interval, delivery_message, delivery_rating_success, delivery_set, recompute_delivery_price, is_all_service, is_process_rma, merged, name, parent_saleorder_id, order_revised_count, so_number, margin, margin_percent, mrp_production_count, note, report_grids, grid_product_tmpl_id, grid_update, grid, tasks_ids, tasks_count, visible_project, project_ids, sh_sale_barcode_mobile, sh_sale_bm_is_cont_scan, partner_credit_conform, sh_purchase_count, sh_so_po_is_show_so_to_po_btn_flag, apply_manual_currency_exchange, manual_currency_exchange_rate, company_currency_id, active_manual_currency_rate, warning_stock, opportunity_id, report_template_id1, report_template_id, amount_to_text, timesheet_ids, timesheet_count, project_id, timesheet_encode_uom_id, timesheet_total_duration, rfm_segment_id, amount_delivery, order_credit_points, order_redeem_points, redeem_value, is_from_website, loyalty_point_credit, order_source, driver_id, order_driver_message_ids, payment_status_with_driver, latitude, longitude, distance_btn_2_loc, sale_order_comm_ids, commission_calc, commission_pay_on, stage_id, order_line_count, date_order, validity_date, payment_term_id, sale_order_template_id, sale_state, delivered_state, sale_state_1, state_2, revised_state, approval_matrix_state, approval_matrix_state_1, branch_id, account_tag, account_tag_ids, analytic_account_id, approving_matrix_sale_id, approved_matrix_ids, is_customer_approval_matrix, hide_proforma, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, is_quotation_cancel, company_id, deduction_ids, analytic_accounting, terms_conditions_id, group_multi_do, is_single_warehouse, is_single_delivery_date, commitment_date, revised_sale_order_ids, revised_sale_order_id, is_revision_so, is_print_report, qty_delivered, count_delivered, multilevel_disc, multi_discount, discount_method, discount_amount, date_confirm, is_sale_order, partner_name, is_hidden_button, lock_sale_order, readonly_disc, readonly_multi, brand, partner_invoice_id, partner_shipping_id, reject_reason, sale_fully_delivered, sale_partially_delivery, sale_fully_paid, sale_partially_paid, sale_hidden_compute_field, date_kanban, is_down_payment, down_payment_amount, total_amount_without_dp, carrier_id, amount_untaxed, amount_tax, amount_total, order_line, discount_type, city_id, state_id, show_mobile, is_external_link, tax_discount_policy, discount_amt_before, discount_amt_line_before, amount_subtotal, warehouse_id, warehouse_new_id, delivery_state, payment_status_driver, approving_matrix_limit_id, approved_matrix_limit_ids, is_over_limit_validation, is_limit_matrix_filled, is_direct_confirm, limit_approval_matrix_line_id, is_approve_button_limit, limit_matrix_state, limit_matrix_state_1, limit_matrix_state_2, sale_limit_state, sale_limit_state_1, sale_limit_state_2, sale_limit_state_3, sale_limit_state_4, sale_limit_state_5, approval_matrix_state_2, approval_matrix_state_3, approval_matrix_state_4, approval_matrix_state_5, approval_matrix_state_6, approval_matrix_state_7, approval_matrix_state_8, approval_matrix_state_9, creditlim, hide_button_revise, lock_order_line, have_available_customer_voucher, customer_voucher_used_ids, cashback_line_ids, show_cashback, cn_cashback_ids, cn_cashback_count, title, partner_id, book_order, ean13, pos_config_id, pos_location_id, delivery_date, delivered_date, delivery_address, delivery_phone, payment_partial_amount, payment_partial_method_id, insert, state, pos_branch_id, pos_order_id, is_self_pickup, is_dropship, purchase_request_ids, purchase_request_count, remark, 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, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.order", "table_name": ""}
+{"text": "How to create records in purchase.order.history?", "response": "To use the purchase.order.history model, you need to provide values for required fields: none. Readonly fields: order_id, product_id, price_unit, product_qty, product_uom, currency_id, price_subtotal, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.order.history", "table_name": ""}
+{"text": "Describe the field structure of access.rights.profile.", "response": "The access.rights.profile model has 9 fields: name, group_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2many: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "access.rights.profile", "table_name": ""}
+{"text": "How does group.card relate to other models?", "response": "The group.card model has 12 relational fields: company_id -> res.company; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "group.card", "table_name": ""}
+{"text": "What models are connected to sh.product.barcode.mobile.wizard.line?", "response": "The sh.product.barcode.mobile.wizard.line model has 7 relational fields: location_id -> stock.location; product_uom_id -> uom.uom; currency_id -> res.currency; company_id -> res.company; sh_product_barcode_id -> sh.product.barcode.mobile.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.product.barcode.mobile.wizard.line", "table_name": ""}
+{"text": "Tell me about the account.payment.term.line model.", "response": "The account.payment.term.line model represents Payment Terms Line in the ERP system. It contains 14 fields and is used to manage payment terms line data. Key fields include: value, value_amount, days, day_of_the_month, option, payment_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.payment.term.line", "table_name": ""}
+{"text": "Can you explain the purpose of ir.http?", "response": "The ir.http model represents HTTP Routing in the ERP system. It contains 3 fields and is used to manage http routing data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.http", "table_name": ""}
+{"text": "What operations can I perform on mail.bot?", "response": "To use the mail.bot model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.bot", "table_name": ""}
+{"text": "Describe the field structure of sequence.mixin.", "response": "The sequence.mixin model has 5 fields: sequence_prefix, sequence_number, id, display_name, __last_update. Field types distribution: char: 2, integer: 2, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sequence.mixin", "table_name": ""}
+{"text": "What are the technical details of link.tracker?", "response": "The link.tracker model is defined in module: link_tracker. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "link.tracker", "table_name": ""}
+{"text": "What are common use cases for sh.tc.top.customer.wizard?", "response": "To use the sh.tc.top.customer.wizard model, you need to provide values for required fields: date_to, no_of_top_item, currency_id, date_from. Readonly fields: sale_currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.tc.top.customer.wizard", "table_name": ""}
+{"text": "What does the sh.mrp.pics model represent?", "response": "The sh.mrp.pics model represents MRP Quality Measurement Pictures in the ERP system. It contains 13 fields and is used to manage mrp quality measurement pictures data. Key fields include: product_id, sh_message, sh_quality_point_id, mrp_id, workorder_id, attachment_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.mrp.pics", "table_name": ""}
+{"text": "What data can be stored in list.product?", "response": "The list.product model has 21 fields: order_dic_id, salesperson, order_number, order_date, product_name, price, qty, discount, tax, subtotal, sale_currency_id, uom, total, categ_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 5, datetime: 4, float: 6, integer: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "list.product", "table_name": ""}
+{"text": "Show me the relational structure of res.partner.bank.", "response": "The res.partner.bank model has 7 relational fields: partner_id -> res.partner; bank_id -> res.bank; currency_id -> res.currency; company_id -> res.company; journal_id -> account.journal; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.partner.bank", "table_name": ""}
+{"text": "Describe the overhead.material model in Odoo.", "response": "The overhead.material model represents Overhead Material Management in the ERP system. It contains 12 fields and is used to manage overhead material management data. Key fields include: product, product_price, consumed, consumed_uom, mrp_wc_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "overhead.material", "table_name": ""}
+{"text": "What is the crm.lead2opportunity.partner model?", "response": "The crm.lead2opportunity.partner model represents Convert Lead to Opportunity (not in mass) in the ERP system. It contains 15 fields and is used to manage convert lead to opportunity (not in mass) data. Key fields include: name, action, lead_id, duplicated_lead_ids, partner_id, user_id, team_id, force_assignment, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.lead2opportunity.partner", "table_name": ""}
+{"text": "Tell me about the ir.exports.line model.", "response": "The ir.exports.line model represents Exports Line in the ERP system. It contains 9 fields and is used to manage exports line data. Key fields include: name, export_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.exports.line", "table_name": ""}
+{"text": "What models are connected to pos.cache.database?", "response": "The pos.cache.database model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.cache.database", "table_name": ""}
+{"text": "Describe the field structure of calendar.event.", "response": "The calendar.event model has 99 fields: name, attendee_status, display_time, start, stop, allday, start_date, stop_date, duration, description, privacy, location, show_as, res_id, res_model_id, res_model, activity_ids, message_ids, user_id, partner_id, active, categ_ids, attendee_ids, partner_ids, alarm_ids, is_highlighted, recurrency, recurrence_id, follow_recurrence, recurrence_update, rrule, rrule_type, event_tz, end_type, interval, count, mo, tu, we, th, fr, sa, su, month_by, day, weekday, byday, until, opportunity_id, phonecall_id, sign_in_location, sign_out_location, sign_in_date, sign_out_date, sign_in, sign_out, note_field, team_id, state, state_1, state_2, cancel_reason, opportunity_name, res_name, res_loc, meeting_salesperson_ids, is_hide_salesperson, dummy_boolean, user_ids, mandatory, partner_attendees_ids, reasons_reschedule, cancelled_reasons, meeting_overview, stage_id, meeting_count, quotation, final_quotation, message_is_follower, message_follower_ids, 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_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 13, selection: 14, datetime: 7, boolean: 22, date: 3, float: 1, text: 2, integer: 11, many2one: 12, one2many: 5, many2many: 8, html: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "calendar.event", "table_name": ""}
+{"text": "How to query stock.package.destination data?", "response": "To use the stock.package.destination model, you need to provide values for required fields: picking_id, move_line_ids, location_dest_id. Readonly fields: move_line_ids, filtered_location, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.package.destination", "table_name": ""}
+{"text": "What models are connected to sh.product.qrcode.generator.wizard?", "response": "The sh.product.qrcode.generator.wizard model has 4 relational fields: product_tmpl_ids -> product.template; product_var_ids -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_tmpl_ids, product_var_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.product.qrcode.generator.wizard", "table_name": ""}
+{"text": "Describe the field structure of asset.asset.revalue.wizard.", "response": "The asset.asset.revalue.wizard model has 18 fields: reason, remaining_value, amount, journal_id, method_number, method_period, company_id, company_currency_id, currency_id, salvage_value, asset_depreciation_manual_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, monetary: 2, many2one: 6, integer: 3, float: 1, date: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "asset.asset.revalue.wizard", "table_name": ""}
+{"text": "How do I use the crm.salesperson.tracking.report model?", "response": "To use the crm.salesperson.tracking.report model, you need to provide values for required fields: sales_person, current_datetime. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.salesperson.tracking.report", "table_name": ""}
+{"text": "What are the technical details of remove.pos.order?", "response": "The remove.pos.order model is defined in module: equip3_pos_general. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "remove.pos.order", "table_name": ""}
+{"text": "What modules define blanket.quotation?", "response": "The blanket.quotation model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "blanket.quotation", "table_name": ""}
+{"text": "What are the technical details of crm.lead.lost?", "response": "The crm.lead.lost model is defined in module: crm. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.lead.lost", "table_name": ""}
+{"text": "What fields does mr.approval.matrix.line have?", "response": "The mr.approval.matrix.line model has 34 fields: sequence, user_ids, minimum_approver, mr_approval_matrix, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, mr_matrix_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 8, many2many: 4, many2one: 6, text: 1, datetime: 4, char: 2, boolean: 6, one2many: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mr.approval.matrix.line", "table_name": ""}
+{"text": "Describe the field structure of mrp.routing.workcenter.", "response": "The mrp.routing.workcenter model has 30 fields: name, sequence, bom_id, company_id, worksheet_type, note, worksheet, worksheet_google_slide, time_mode, time_mode_batch, time_cycle_manual, time_cycle, workorder_count, workorder_ids, new_sequence, branch_id, workcenter_id, workcenter_ids, location_id, workcenter_type, is_branch_filled, workcenter_group_id, operation_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, integer: 5, many2one: 8, selection: 3, text: 1, binary: 1, float: 2, one2many: 1, many2many: 1, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.routing.workcenter", "table_name": ""}
+{"text": "Show me the fields of purchase.custom.checklist.", "response": "The purchase.custom.checklist model has 10 fields: name, description, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.custom.checklist", "table_name": ""}
+{"text": "List all fields in the purchase.agreement.type model.", "response": "The purchase.agreement.type model has 8 fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.agreement.type", "table_name": ""}
+{"text": "Show me the fields of stock.production.lot.", "response": "The stock.production.lot model has 79 fields: name, ref, product_id, product_uom_id, quant_ids, product_qty, note, display_complete, use_expiration_date, expiration_date, use_date, removal_date, alert_date, product_expiry_alert, product_expiry_reminded, purchase_order_ids, purchase_order_count, sale_order_ids, sale_order_count, expiry_state, state_check, product_expiry_reminder, company_id, start_date_warranty, end_date_warranty, renewal_times, assembly_production_finished_id, assembly_production_byproduct_id, assembly_production_rejected_id, assembly_expiration_date, assembly_qty, assembly_is_autogenerate, assembly_product_tracking, kitchen_production_finished_id, kitchen_production_byproduct_id, kitchen_production_rejected_id, kitchen_expiration_date, kitchen_qty, kitchen_is_autogenerate, kitchen_product_tracking, finish_good_rework_byproduct_id, finish_good_rework_finished_id, finish_good_rework_rejected_id, active, barcode, replace_product_public_price, public_price, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 7, many2one: 17, one2many: 5, float: 4, html: 1, boolean: 14, datetime: 9, many2many: 4, integer: 8, selection: 6, date: 4.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.production.lot", "table_name": ""}
+{"text": "Can you explain the purpose of generate.closing.entries?", "response": "The generate.closing.entries model represents Generate Opening Entries in the ERP system. It contains 13 fields and is used to manage generate opening entries data. Key fields include: fiscal_year_id, closing_entry_date, journal_id, description, summary_account_id, retained_earnings_account_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "generate.closing.entries", "table_name": ""}
+{"text": "How is report.stock.demand used in the system?", "response": "The report.stock.demand model represents Stock Demand in the ERP system. It contains 10 fields and is used to manage stock demand data. Key fields include: date_datetime, quantity, forecast, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.stock.demand", "table_name": ""}
+{"text": "What does the queue.job.dashboard model represent?", "response": "The queue.job.dashboard model represents Queue Job Dashboard in the ERP system. It contains 3 fields and is used to manage queue job dashboard data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "queue.job.dashboard", "table_name": ""}
+{"text": "Show me the fields of calendar.event.cancel.wizard.", "response": "The calendar.event.cancel.wizard model has 8 fields: cancel_reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "calendar.event.cancel.wizard", "table_name": ""}
+{"text": "Show me the relational structure of update.customer.segment.", "response": "The update.customer.segment model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "update.customer.segment", "table_name": ""}
+{"text": "What fields does asset.asset.revalue.wizard have?", "response": "The asset.asset.revalue.wizard model has 18 fields: reason, remaining_value, amount, journal_id, method_number, method_period, company_id, company_currency_id, currency_id, salvage_value, asset_depreciation_manual_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, monetary: 2, many2one: 6, integer: 3, float: 1, date: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "asset.asset.revalue.wizard", "table_name": ""}
+{"text": "Can you explain the purpose of report.sh_purchase_reports.sh_po_by_category_doc?", "response": "The report.sh_purchase_reports.sh_po_by_category_doc model represents Purchase by category report abstract model in the ERP system. It contains 3 fields and is used to manage purchase by category report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_po_by_category_doc", "table_name": ""}
+{"text": "Can you explain the purpose of auditlog.log?", "response": "The auditlog.log model represents Auditlog - Log in the ERP system. It contains 18 fields and is used to manage auditlog - log data. Key fields include: name, model_id, model_name, model_model, res_id, user_id, method, line_ids, http_session_id, http_request_id, log_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "auditlog.log", "table_name": ""}
+{"text": "Show me the relational structure of calendar.contacts.", "response": "The calendar.contacts model has 4 relational fields: user_id -> res.users; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "calendar.contacts", "table_name": ""}
+{"text": "What operations can I perform on pos.promotion.gift.free?", "response": "To use the pos.promotion.gift.free model, you need to provide values for required fields: quantity_free, promotion_id, type_apply. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion.gift.free", "table_name": ""}
+{"text": "Describe the implementation of report_excel_gen.", "response": "The report_excel_gen model is defined in module: report_excel. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report_excel_gen", "table_name": ""}
+{"text": "Describe the implementation of budget.purchase.", "response": "The budget.purchase model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "budget.purchase", "table_name": ""}
+{"text": "How to create records in purchase.detail.excel.extended?", "response": "To use the purchase.detail.excel.extended 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.detail.excel.extended", "table_name": ""}
+{"text": "Can you explain the purpose of crm.send.message.mass?", "response": "The crm.send.message.mass model represents Send Message Mass in the ERP system. It contains 10 fields and is used to manage send message mass data. Key fields include: message_chat_ids, conversation_id, connector_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.send.message.mass", "table_name": ""}
+{"text": "What methods are available in mail.wizard.invite?", "response": "The mail.wizard.invite model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.wizard.invite", "table_name": ""}
+{"text": "What operations can I perform on cancel.credit.limit?", "response": "To use the cancel.credit.limit model, you need to provide values for required fields: limit_id, reason. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cancel.credit.limit", "table_name": ""}
+{"text": "Show me the relational structure of setu.inventory.fsn.analysis.report.", "response": "The setu.inventory.fsn.analysis.report model has 7 relational fields: product_category_ids -> product.category; product_ids -> product.product; warehouse_ids -> stock.warehouse; company_id -> res.company; company_ids -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_category_ids, product_ids, warehouse_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.fsn.analysis.report", "table_name": ""}
+{"text": "Which fields in resource.resource are computed?", "response": "The resource.resource model is defined in module: resource. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "resource.resource", "table_name": ""}
+{"text": "Describe the field structure of im_livechat.channel.rule.", "response": "The im_livechat.channel.rule model has 13 fields: regex_url, action, auto_popup_timer, channel_id, country_ids, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, selection: 1, integer: 3, many2one: 3, many2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "im_livechat.channel.rule", "table_name": ""}
+{"text": "What are common use cases for queue.job?", "response": "To use the queue.job model, you need to provide values for required fields: uuid, state. Readonly fields: uuid, graph_uuid, name, model_name, method_name, record_ids, records, dependencies, dependency_graph, graph_jobs_count, args, kwargs, func_string, state, exc_name, exc_message, exc_info, result, date_created, date_started, date_enqueued, date_done, date_cancelled, channel_method_name, job_function_id, identity_key, worker_pid, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "queue.job", "table_name": ""}
+{"text": "What are common use cases for theme.utils?", "response": "To use the theme.utils model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "theme.utils", "table_name": ""}
+{"text": "What models are connected to approval.matrix.accounting.lines?", "response": "The approval.matrix.accounting.lines model has 18 relational fields: user_ids -> res.users; approval_matrix_id -> approval.matrix.accounting; approved_users -> res.users; last_approved -> res.users; move_id -> account.move; receipt_id -> account.payment; multi_receipt_id -> account.multipayment; voucher_id -> account.voucher; payment_voc_id -> payment.voucher; acc_internal_transfer_id -> account.internal.transfer; account_budget_request_id -> budget.change.req; account_budget_id -> crossovered.budget; budget_purchase_id -> budget.purchase; account_budget_req_id -> purchase.change.request; customer_deposit_id -> customer.deposit; acc_vendor_deposit_id -> vendor.deposit; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.accounting.lines", "table_name": ""}
+{"text": "How is vendor.deposit.amount.wizard used in the system?", "response": "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. 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "vendor.deposit.amount.wizard", "table_name": ""}
+{"text": "Tell me about the sh.mrp.quality.alert model.", "response": "The sh.mrp.quality.alert model represents Mrp Quality Alert in the ERP system. It contains 47 fields and is used to manage mrp quality alert data. Key fields include: name, title, product_id, lot_id, user_id, team_id, sh_priority, tag_ids, color, sh_description, partner_id, stage_id, mrp_id, workorder_id, company_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.mrp.quality.alert", "table_name": ""}
+{"text": "What methods are available in project.create.sale.order?", "response": "The project.create.sale.order model is defined in module: sale_timesheet. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "project.create.sale.order", "table_name": ""}
+{"text": "What is the all.loyalty.history model?", "response": "The all.loyalty.history model represents all loyalty history in the ERP system. It contains 19 fields and is used to manage all loyalty history data. Key fields include: order_id, pos_order_id, partner_id, date, generated_from, transaction_type, points, amount, currency_id, company_id, check_state, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "all.loyalty.history", "table_name": ""}
+{"text": "What operations can I perform on report.extra.content?", "response": "To use the report.extra.content model, you need to provide values for required fields: model_id, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.extra.content", "table_name": ""}
+{"text": "Which fields in x.report.wizard are computed?", "response": "The x.report.wizard model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "x.report.wizard", "table_name": ""}
+{"text": "What business logic is in ir.mail_server?", "response": "To use the ir.mail_server model, you need to provide values for required fields: name, smtp_host, smtp_port, smtp_encryption. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.mail_server", "table_name": ""}
+{"text": "How do I use the snailmail.letter model?", "response": "To use the snailmail.letter model, you need to provide values for required fields: model, res_id, partner_id, company_id, state. Readonly fields: company_id, attachment_datas, attachment_fname, state, display_name, reference, id, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "snailmail.letter", "table_name": ""}
+{"text": "Show me the fields of product.expire.report.", "response": "The product.expire.report model has 8 fields: report_selection, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.expire.report", "table_name": ""}
+{"text": "How is stock.valuation.adjustment.lines used in the system?", "response": "The stock.valuation.adjustment.lines model represents Valuation Adjustment Lines in the ERP system. It contains 19 fields and is used to manage valuation adjustment lines data. Key fields include: name, cost_id, cost_line_id, move_id, product_id, quantity, weight, volume, former_cost, additional_landed_cost, final_cost, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.valuation.adjustment.lines", "table_name": ""}
+{"text": "How is do.matrix.reject used in the system?", "response": "The do.matrix.reject model represents do.matrix.reject in the ERP system. It contains 8 fields and is used to manage do.matrix.reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "do.matrix.reject", "table_name": ""}
+{"text": "What are the relationships in internal.transfer?", "response": "The internal.transfer model has 32 relational fields: product_line_ids -> internal.transfer.line; operation_type_in_id -> stock.picking.type; operation_type_out_id -> stock.picking.type; itr_approval_matrix_id -> itr.approval.matrix; approved_matrix_ids -> itr.approval.matrix.line; approval_matrix_line_id -> itr.approval.matrix.line; source_warehouse_id -> stock.warehouse; destination_warehouse_id -> stock.warehouse; company_id -> res.company; filter_source_warehouse_id -> stock.location; filter_destination_warehouse_id -> stock.location; requested_by -> res.users; branch_id -> res.branch; mr_id -> material.request; average_id -> stock.day.average; analytic_account_group_ids -> account.analytic.tag; source_location_id -> stock.location; destination_location_id -> stock.location; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_source_warehouse_id, filter_destination_warehouse_id, mr_id, analytic_account_group_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "internal.transfer", "table_name": ""}
+{"text": "Show me the relational structure of account.multipayment.debit.", "response": "The account.multipayment.debit model has 7 relational fields: line_id -> account.multipayment; currency_id -> res.currency; invoice_id -> account.move; account_id -> account.account; payment_id -> account.payment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.multipayment.debit", "table_name": ""}
+{"text": "What are the technical details of report.accounting_pdf_reports.report_trialbalance?", "response": "The report.accounting_pdf_reports.report_trialbalance model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.accounting_pdf_reports.report_trialbalance", "table_name": ""}
+{"text": "How to query assign.pr.line.wizard data?", "response": "To use the assign.pr.line.wizard model, you need to provide values for required fields: none. Readonly fields: name, user_id, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assign.pr.line.wizard", "table_name": ""}
+{"text": "What modules define auditlog.log?", "response": "The auditlog.log model is defined in module: auditlog. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "auditlog.log", "table_name": ""}
+{"text": "What are common use cases for bo.request.matrix.reject?", "response": "To use the bo.request.matrix.reject 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "bo.request.matrix.reject", "table_name": ""}
+{"text": "What methods are available in pos.gift.card.exchange.history?", "response": "The pos.gift.card.exchange.history model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.gift.card.exchange.history", "table_name": ""}
+{"text": "What models are connected to purchase.request.warning?", "response": "The purchase.request.warning model has 3 relational fields: warning_line_ids -> purchase.request.warning.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.request.warning", "table_name": ""}
+{"text": "What are the available fields for stock.production.lot?", "response": "The stock.production.lot model has 79 fields: name, ref, product_id, product_uom_id, quant_ids, product_qty, note, display_complete, use_expiration_date, expiration_date, use_date, removal_date, alert_date, product_expiry_alert, product_expiry_reminded, purchase_order_ids, purchase_order_count, sale_order_ids, sale_order_count, expiry_state, state_check, product_expiry_reminder, company_id, start_date_warranty, end_date_warranty, renewal_times, assembly_production_finished_id, assembly_production_byproduct_id, assembly_production_rejected_id, assembly_expiration_date, assembly_qty, assembly_is_autogenerate, assembly_product_tracking, kitchen_production_finished_id, kitchen_production_byproduct_id, kitchen_production_rejected_id, kitchen_expiration_date, kitchen_qty, kitchen_is_autogenerate, kitchen_product_tracking, finish_good_rework_byproduct_id, finish_good_rework_finished_id, finish_good_rework_rejected_id, active, barcode, replace_product_public_price, public_price, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 7, many2one: 17, one2many: 5, float: 4, html: 1, boolean: 14, datetime: 9, many2many: 4, integer: 8, selection: 6, date: 4.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.production.lot", "table_name": ""}
+{"text": "Can you explain the purpose of stock.move.line?", "response": "The stock.move.line model represents Product Moves (Stock Move Line) in the ERP system. It contains 64 fields and is used to manage product moves (stock move line) data. Key fields include: picking_id, move_id, company_id, product_id, product_uom_id, product_uom_category_id, product_qty, product_uom_qty, qty_done, package_id, package_level_id, lot_id, lot_name, date, owner_id, location_id, location_dest_id, lots_visible, picking_code, picking_type_use_create_lots, picking_type_use_existing_lots, state, is_initial_demand_editable, is_locked, consume_line_ids, produce_line_ids, reference, tracking, origin, picking_type_entire_packs, description_picking, workorder_id, production_id, expiration_date, scrap_return_move_id, is_double_product_usage, sale_price, sequence, move_line_sequence, product_type, quant_package_ids, result_package_id, is_quant_update, force_to_reserve_qty, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, assembly_id, scrap_sale_price, is_low_stock, description, kitchen_id, finish_good_rework_id, exp_date, remark, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.move.line", "table_name": ""}
+{"text": "What modules define account.tax.map.sales.line?", "response": "The account.tax.map.sales.line model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.tax.map.sales.line", "table_name": ""}
+{"text": "Describe the ir.filters model in Odoo.", "response": "The ir.filters model represents Filters in the ERP system. It contains 16 fields and is used to manage filters data. Key fields include: name, user_id, domain, context, sort, model_id, is_default, action_id, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.filters", "table_name": ""}
+{"text": "Describe the account.group.template model in Odoo.", "response": "The account.group.template model represents Template for Account Groups in the ERP system. It contains 12 fields and is used to manage template for account groups data. Key fields include: parent_id, code_prefix_start, code_prefix_end, chart_template_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.group.template", "table_name": ""}
+{"text": "What fields does ir.exports.line have?", "response": "The ir.exports.line model has 9 fields: name, export_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.exports.line", "table_name": ""}
+{"text": "What operations can I perform on report_excel_export_wizard?", "response": "To use the report_excel_export_wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report_excel_export_wizard", "table_name": ""}
+{"text": "What are the technical details of customer.category?", "response": "The customer.category model is defined in module: equip3_sale_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "customer.category", "table_name": ""}
+{"text": "What modules define cancel.picking?", "response": "The cancel.picking model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "cancel.picking", "table_name": ""}
+{"text": "What is the account.cashbox.wizard.line model?", "response": "The account.cashbox.wizard.line model represents account.cashbox.wizard.line in the ERP system. It contains 16 fields and is used to manage account.cashbox.wizard.line data. Key fields include: account_cashbox_wizard_id, coin_value, number, subtotal, cashbox_id, currency_id, pos_config_id, pos_session_id, is_closing_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.cashbox.wizard.line", "table_name": ""}
+{"text": "Describe the implementation of report.sh_purchase_reports.rpt_purchase_order_day_wise.", "response": "The report.sh_purchase_reports.rpt_purchase_order_day_wise model is defined in module: equip3_purchase_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_purchase_reports.rpt_purchase_order_day_wise", "table_name": ""}
+{"text": "How to query crm.phonecall2phonecall data?", "response": "To use the crm.phonecall2phonecall model, you need to provide values for required fields: name, action. Readonly fields: name, user_id, contact_name, phone, tag_ids, date, team_id, action, partner_id, note, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.phonecall2phonecall", "table_name": ""}
+{"text": "What are the relationships in store.filters.groups?", "response": "The store.filters.groups model has 3 relational fields: model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "store.filters.groups", "table_name": ""}
+{"text": "What foreign keys exist in access.rights.profile?", "response": "The access.rights.profile model has 3 relational fields: group_ids -> res.groups; create_uid -> res.users; write_uid -> res.users. Many2many fields: group_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "access.rights.profile", "table_name": ""}
+{"text": "What foreign keys exist in ai.memory?", "response": "The ai.memory model has 4 relational fields: session_id -> ai.chat.session; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ai.memory", "table_name": ""}
+{"text": "What modules define acrux.chat.select.conversation.wizard?", "response": "The acrux.chat.select.conversation.wizard model is defined in module: acrux_chat_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "acrux.chat.select.conversation.wizard", "table_name": ""}
+{"text": "What are the relationships in account.trial.balance?", "response": "The account.trial.balance 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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.trial.balance", "table_name": ""}
+{"text": "How to query rfm.yearly.analysis.by.segment data?", "response": "To use the rfm.yearly.analysis.by.segment model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "rfm.yearly.analysis.by.segment", "table_name": ""}
+{"text": "How is report.product.report_pricelist implemented technically?", "response": "The report.product.report_pricelist model is defined in module: product. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.product.report_pricelist", "table_name": ""}
+{"text": "What modules define account.setup.bank.manual.config?", "response": "The account.setup.bank.manual.config model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.setup.bank.manual.config", "table_name": ""}
+{"text": "How does pos.sync.session.log relate to other models?", "response": "The pos.sync.session.log model has 8 relational fields: send_from_session_id -> pos.session; send_to_session_id -> pos.session; user_id -> res.users; user_receive_id -> res.users; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.sync.session.log", "table_name": ""}
+{"text": "What business logic is in sh.purchase.report.representative.wizard?", "response": "To use the sh.purchase.report.representative.wizard model, you need to provide values for required fields: date_start, date_end. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.purchase.report.representative.wizard", "table_name": ""}
+{"text": "What are the technical details of project.project?", "response": "The project.project model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "project.project", "table_name": ""}
+{"text": "How does sh.tsp.top.purchasing.product.wizard relate to other models?", "response": "The sh.tsp.top.purchasing.product.wizard model has 3 relational fields: company_ids -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.tsp.top.purchasing.product.wizard", "table_name": ""}
+{"text": "What is the vendor.evaluation.template.eval model?", "response": "The vendor.evaluation.template.eval model represents Vendor Evaluation Template Evaluation in the ERP system. It contains 13 fields and is used to manage vendor evaluation template evaluation data. Key fields include: evaluation_id, state, name, eval_factor, eval_rate, eval_comment, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "vendor.evaluation.template.eval", "table_name": ""}
+{"text": "What models are connected to product.ribbon?", "response": "The product.ribbon model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.ribbon", "table_name": ""}
+{"text": "What is the snailmail.letter.cancel model?", "response": "The snailmail.letter.cancel model represents Dismiss notification for resend by model in the ERP system. It contains 9 fields and is used to manage dismiss notification for resend by model data. Key fields include: model, help_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "snailmail.letter.cancel", "table_name": ""}
+{"text": "List all fields in the report.accounting_pdf_reports.report_tax model.", "response": "The report.accounting_pdf_reports.report_tax model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.accounting_pdf_reports.report_tax", "table_name": ""}
+{"text": "What foreign keys exist in im_livechat.channel.rule?", "response": "The im_livechat.channel.rule model has 4 relational fields: channel_id -> im_livechat.channel; country_ids -> res.country; create_uid -> res.users; write_uid -> res.users. Many2many fields: country_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "im_livechat.channel.rule", "table_name": ""}
+{"text": "Describe the field structure of report.sh_purchase_reports.sh_po_product_indent_doc.", "response": "The report.sh_purchase_reports.sh_po_product_indent_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_po_product_indent_doc", "table_name": ""}
+{"text": "How do I use the restaurant.table model?", "response": "To use the restaurant.table model, you need to provide values for required fields: name, shape. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "restaurant.table", "table_name": ""}
+{"text": "How to query repair.order.make_invoice data?", "response": "To use the repair.order.make_invoice 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "repair.order.make_invoice", "table_name": ""}
+{"text": "What operations can I perform on report.sale.report_saleproforma?", "response": "To use the report.sale.report_saleproforma model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sale.report_saleproforma", "table_name": ""}
+{"text": "What fields does pos.session.log.cashier have?", "response": "The pos.session.log.cashier model has 12 fields: name, user_id, login_date, logout_date, session_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, datetime: 5, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.session.log.cashier", "table_name": ""}
+{"text": "What methods are available in account.balance.report?", "response": "The account.balance.report model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.balance.report", "table_name": ""}
+{"text": "What are the relationships in ir.actions.act_window_close?", "response": "The ir.actions.act_window_close model has 3 relational fields: binding_model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.actions.act_window_close", "table_name": ""}
+{"text": "Describe the implementation of list.customer.", "response": "The list.customer model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "list.customer", "table_name": ""}
+{"text": "What foreign keys exist in wizard.quotation.agreement?", "response": "The wizard.quotation.agreement model has 5 relational fields: agreement_id -> purchase.agreement; partner_ids -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "wizard.quotation.agreement", "table_name": ""}
+{"text": "What does the analytic.priority model represent?", "response": "The analytic.priority model represents analytic.priority in the ERP system. It contains 9 fields and is used to manage analytic.priority data. Key fields include: priority, object_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "analytic.priority", "table_name": ""}
+{"text": "What methods are available in product.ribbon?", "response": "The product.ribbon model is defined in module: website_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.ribbon", "table_name": ""}
+{"text": "What is the purchase.order model?", "response": "The purchase.order model represents Purchase Report Template in the ERP system. It contains 266 fields and is used to manage purchase report template data. Key fields include: priority, origin, partner_ref, date_approve, dest_address_id, order_line, notes, invoice_count, invoice_ids, invoice_status, date_calendar_start, fiscal_position_id, payment_term_id, product_id, user_id, currency_rate, mail_reminder_confirmed, mail_reception_confirmed, receipt_reminder_email, reminder_date_before_receipt, team_id, report_grids, grid_product_tmpl_id, grid_update, grid, requisition_id, is_quantity_copy, incoterm_id, picking_count, picking_ids, picking_type_id, default_location_dest_id_usage, group_id, is_shipped, effective_date, on_time_rate, active, complete_state, custom_checklist_ids, custom_checklist, product_template_id, digital_sign, purchase_show_signature, chk_sign_confirm, purchase_show_enable_other_sign, sign_by, designation, sign_on, document_count, order_history_line, order_report_id, rfq_report_id, purchase_tag_ids, purchase_url, report_token, text_message, po_extract_id, po_split_id, po_extract_count, po_split_count, sh_fully_ship, sh_partially_ship, sh_fully_paid, sh_partially_paid, sh_hidden_compute_field, agreement_id, cancel_lines, selected_order, sh_msg, sh_po_number, sh_purchase_order_id, sh_revision_po_id, po_count, sh_purchase_revision_config, visible_eval, mrp_production_count, sale_order_count, internal_id, inter_transfer_count, client_order_id, discount_method, discount_amount, discount_amt, discount_amt_line, merged, sh_purchase_barcode_mobile, sh_purchase_bm_is_cont_scan, sh_sale_order_id, apply_manual_currency_exchange, manual_currency_exchange_rate, active_manual_currency_rate, total_invoices_amount, down_payment_by, amount, dp_journal_id, hide_create_bill, payment_status, down_payment_amount, total_down_payment_amount, is_down_payment, report_template_id1, report_template_id, amount_to_text, is_vendor_pricelist, name, currency_id, po_expiry_date, po, exp_po, sent, is_goods_orders, is_services_orders, is_hold_purchase_order, approval_matrix_id, is_approval_matrix, state1, po_state, approved_matrix_ids, is_approve_button, approval_matrix_line_id, analytic_account_group_ids, company_id, branch_id, destination_location_id, is_delivery_receipt, destination_warehouse_id, discount_type, is_single_delivery_destination, analytic_accounting, is_revision_po, is_revision_created, revision_order_id, custom_checklist_template_ids, readonly_price, timezone_date, request_partner_id, date_order_assets, name2, date_order, milestone_template_id, milestone_purchase_ids, is_group_good_services_order, have_product_service, swo_ids, swo_count, is_taxes, actual_progress, remaining_progress, progress_paid, paid_swo, partner_invoice_id, available_partner_invoice_ids, product_brand_ids, is_product_brand_filter, is_service_work_order, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, is_service, show_analytic_tags, amount_untaxed, amount_tax, amount_total, discount_amt_before, discount_amt_line_before, amount_subtotal, tax_discount_policy, list_available_products, from_purchase_request, term_condition, term_condition_box, bo_count, blanket_ids, multilevel_disc, multi_discount, vendor_payment_terms, service_level_agreement_id, service_level_agreement_box, user_request_ids, vendor_invoice_documents_count, down_payment_discount_amount, tender_scope, is_submit_quotation, price_rating, not_editable, is_editable, tender_order_line, from_bo, is_btn_approval_matrix, state, is_blanket_cancel, open_tender, days_to_approve, purchase_order_duration_to_confirm, amount_saved_from_cost_savings, number_of_successful_cost_savings, partner_id, dp, journal_id, name_dp, direct_approval_matrix_id, is_approval_matrix_direct, approved_matrix_direct_ids, approved_matrix_direct_id, state_direct_on, state_direct_off, is_approve_button_direct, control, qty_limit, budget_limit, is_valid_coupon, applied_coupon_ids, generated_coupon_ids, no_code_promo_program_ids, code_promo_program_id, promo_code, client_order_ref, is_dropship, is_sale_order, customer_partner_id, customer_location_partner_id, branch_ids, is_assets_orders, import_reference, is_report_purchaseorder_printed, is_report_purchasequotation_printed, remark, rfq_type, discount_promotions_amount, date_planned, persentase_antar_badan, form_view_opened, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order", "table_name": ""}
+{"text": "How do I use the budget.budget.budget.line model?", "response": "To use the budget.budget.budget.line model, you need to provide values for required fields: budget_budget_id, date_from, date_to, planned_amount. Readonly fields: name, analytic_group_id, currency_id, practical_amount, theoritical_amount, percentage, company_id, is_above_budget, budget_budget_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "budget.budget.budget.line", "table_name": ""}
+{"text": "What models are connected to combo.option?", "response": "The combo.option model has 3 relational fields: item_ids -> combo.option.item; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "combo.option", "table_name": ""}
+{"text": "What foreign keys exist in ir.model.fields.selection?", "response": "The ir.model.fields.selection model has 3 relational fields: field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.model.fields.selection", "table_name": ""}
+{"text": "Describe the implementation of cash.box.out.", "response": "The cash.box.out model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "cash.box.out", "table_name": ""}
+{"text": "What methods are available in sh.mrp.pass.fail?", "response": "The sh.mrp.pass.fail model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.mrp.pass.fail", "table_name": ""}
+{"text": "What does the rma.reject.reason model represent?", "response": "The rma.reject.reason model represents Reject Reason in the ERP system. It contains 8 fields and is used to manage reject reason data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "rma.reject.reason", "table_name": ""}
+{"text": "How do I use the report.stock.quantity.new model?", "response": "To use the report.stock.quantity.new model, you need to provide values for required fields: none. Readonly fields: date, product_tmpl_id, product_id, state, product_qty, move_ids, company_id, warehouse_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.stock.quantity.new", "table_name": ""}
+{"text": "How to query pos.service.charge data?", "response": "To use the pos.service.charge model, you need to provide values for required fields: name, product_id, type, amount. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.service.charge", "table_name": ""}
+{"text": "What operations can I perform on customer.degree.trust?", "response": "To use the customer.degree.trust model, you need to provide values for required fields: name, company_id. Readonly fields: index, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "customer.degree.trust", "table_name": ""}
+{"text": "What operations can I perform on ir.actions.todo?", "response": "To use the ir.actions.todo model, you need to provide values for required fields: action_id, state. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.actions.todo", "table_name": ""}
+{"text": "How is report_excel_import_wizard used in the system?", "response": "The report_excel_import_wizard model represents report_excel_import Wizard in the ERP system. It contains 8 fields and is used to manage report_excel_import wizard data. Key fields include: data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report_excel_import_wizard", "table_name": ""}
+{"text": "List all fields in the account.common.partner.report model.", "response": "The account.common.partner.report model has 14 fields: result_selection, 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 types distribution: selection: 2, many2many: 1, date: 2, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.common.partner.report", "table_name": ""}
+{"text": "How does auditlog.http.session relate to other models?", "response": "The auditlog.http.session model has 4 relational fields: user_id -> res.users; http_request_ids -> auditlog.http.request; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "auditlog.http.session", "table_name": ""}
+{"text": "Show me the fields of report.sh_purchase_reports.sh_vend_po_analysis_doc.", "response": "The report.sh_purchase_reports.sh_vend_po_analysis_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_vend_po_analysis_doc", "table_name": ""}
+{"text": "What operations can I perform on budget.change.req?", "response": "To use the budget.change.req model, you need to provide values for required fields: requested_id, budget_std_id, date, state, company_id. Readonly fields: name, state, approval_matrix, is_allowed_to_approval_matrix, approval_matrix_line_id, is_approve_button, company_id, currency_id, state1, state2, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "budget.change.req", "table_name": ""}
+{"text": "What are common use cases for fast.financial.report.query?", "response": "To use the fast.financial.report.query model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "fast.financial.report.query", "table_name": ""}
+{"text": "What are the technical details of website.cover_properties.mixin?", "response": "The website.cover_properties.mixin model is defined in module: website. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.cover_properties.mixin", "table_name": ""}
+{"text": "What data can be stored in sale.summary.commission.report?", "response": "The sale.summary.commission.report model has 13 fields: start_date, end_date, sales_persons, commision_type, company_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, many2many: 2, selection: 1, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.summary.commission.report", "table_name": ""}
+{"text": "What are common use cases for pos.generate.efaktur.digunggung?", "response": "To use the pos.generate.efaktur.digunggung model, you need to provide values for required fields: none. Readonly fields: no_of_invoice, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.generate.efaktur.digunggung", "table_name": ""}
+{"text": "What methods are available in sale.order.template?", "response": "The sale.order.template model is defined in module: sale_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.order.template", "table_name": ""}
+{"text": "What foreign keys exist in cash.box.out?", "response": "The cash.box.out model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "cash.box.out", "table_name": ""}
+{"text": "What models are connected to res.users.apikeys.description?", "response": "The res.users.apikeys.description model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.users.apikeys.description", "table_name": ""}
+{"text": "How to query delivery.price.rule data?", "response": "To use the delivery.price.rule model, you need to provide values for required fields: sequence, carrier_id, variable, operator, max_value, list_base_price, list_price, variable_factor. Readonly fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "delivery.price.rule", "table_name": ""}
+{"text": "Show me the fields of res.country.state.", "response": "The res.country.state model has 11 fields: country_id, code, name, city_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.country.state", "table_name": ""}
+{"text": "What methods are available in mr.internal_transfer_line?", "response": "The mr.internal_transfer_line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mr.internal_transfer_line", "table_name": ""}
+{"text": "How is approval.request.reject used in the system?", "response": "The approval.request.reject model represents approval.request.reject in the ERP system. It contains 8 fields and is used to manage approval.request.reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.request.reject", "table_name": ""}
+{"text": "What data can be stored in report.sh_inventory_mrp_qc.mrp_quality_check_doc?", "response": "The report.sh_inventory_mrp_qc.mrp_quality_check_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_inventory_mrp_qc.mrp_quality_check_doc", "table_name": ""}
+{"text": "What does the asset.cip model represent?", "response": "The asset.cip model represents Asset CIP in the ERP system. It contains 19 fields and is used to manage asset cip data. Key fields include: name, asset_name, asset_category, cip_account, state, lines, currency, entry_count, move_id, asset_count, amount_total, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "asset.cip", "table_name": ""}
+{"text": "Which fields in global.search.fields are computed?", "response": "The global.search.fields model is defined in module: sh_backmate_theme_adv. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "global.search.fields", "table_name": ""}
+{"text": "What fields does report.eq_scrap_order_report.scrap_order_report have?", "response": "The report.eq_scrap_order_report.scrap_order_report model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.eq_scrap_order_report.scrap_order_report", "table_name": ""}
+{"text": "Show me the relational structure of sale.order.pricelist.wizard.", "response": "The sale.order.pricelist.wizard model has 4 relational fields: shs_pricelist_id -> product.pricelist; pricelist_line -> sale.order.pricelist.wizard.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.pricelist.wizard", "table_name": ""}
+{"text": "Describe the field structure of mail.activity.", "response": "The mail.activity model has 31 fields: res_model_id, res_model, res_id, res_name, activity_type_id, activity_category, activity_decoration, icon, summary, note, date_deadline, automated, user_id, request_partner_id, state, recommended_activity_type_id, previous_activity_type_id, has_recommended_activities, mail_template_ids, force_next, can_write, calendar_event_id, attachment_ids, is_attachment_required, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, char: 5, many2one_reference: 1, selection: 3, html: 1, date: 1, boolean: 5, many2many: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.activity", "table_name": ""}
+{"text": "What foreign keys exist in sms.template.preview?", "response": "The sms.template.preview model has 4 relational fields: sms_template_id -> sms.template; model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sms.template.preview", "table_name": ""}
+{"text": "What foreign keys exist in hide.chatter?", "response": "The hide.chatter model has 4 relational fields: access_management_id -> access.management; model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hide.chatter", "table_name": ""}
+{"text": "Tell me about the ir.model.constraint model.", "response": "The ir.model.constraint model represents Model Constraint in the ERP system. It contains 13 fields and is used to manage model constraint data. Key fields include: name, definition, message, model, module, type, write_date, create_date, id, display_name, create_uid, write_uid, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.model.constraint", "table_name": ""}
+{"text": "Which fields in mrp.bom.line are computed?", "response": "The mrp.bom.line model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.bom.line", "table_name": ""}
+{"text": "How to query crm.team data?", "response": "To use the crm.team model, you need to provide values for required fields: name, alias_id, alias_model_id, alias_defaults, alias_contact. Readonly fields: currency_id, dashboard_button_name, dashboard_graph_data, lead_unassigned_count, lead_all_assigned_month_count, opportunities_count, opportunities_amount, opportunities_overdue_count, opportunities_overdue_amount, invoiced, quotations_count, quotations_amount, sales_to_invoice_count, abandoned_carts_count, abandoned_carts_amount, rma_draft_count, rma_confirm_count, rma_process_count, rma_close_count, rma_reject_count, pos_sessions_open_count, pos_order_amount_total, company_id, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, alias_domain. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.team", "table_name": ""}
+{"text": "What business logic is in sh.top.customers.xls?", "response": "To use the sh.top.customers.xls 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.top.customers.xls", "table_name": ""}
+{"text": "Tell me about the ir.demo model.", "response": "The ir.demo model represents Demo in the ERP system. It contains 7 fields and is used to manage demo data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.demo", "table_name": ""}
+{"text": "What business logic is in forecast.quantity?", "response": "To use the forecast.quantity model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "forecast.quantity", "table_name": ""}
+{"text": "Describe the many2many relations for ir.qweb.field.relative.", "response": "The ir.qweb.field.relative model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb.field.relative", "table_name": ""}
+{"text": "What methods are available in show.material.done.popup?", "response": "The show.material.done.popup model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "show.material.done.popup", "table_name": ""}
+{"text": "What business logic is in itr.matrix.reject?", "response": "To use the itr.matrix.reject 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "itr.matrix.reject", "table_name": ""}
+{"text": "What modules define report.sh_purchase_reports.sh_tv_top_vendors_doc?", "response": "The report.sh_purchase_reports.sh_tv_top_vendors_doc model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_purchase_reports.sh_tv_top_vendors_doc", "table_name": ""}
+{"text": "Show me the fields of opening.balance.line.", "response": "The opening.balance.line model has 15 fields: move_id, company_id, account_id, partner_id, company_currency_id, debit, credit, date_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, monetary: 2, date: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "opening.balance.line", "table_name": ""}
+{"text": "What models are connected to ai.data.cleanup?", "response": "The ai.data.cleanup model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ai.data.cleanup", "table_name": ""}
+{"text": "What data can be stored in export.retur.pajak.masukan?", "response": "The export.retur.pajak.masukan model has 12 fields: partner_id, date_from, date_to, tax_report_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, date: 2, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "export.retur.pajak.masukan", "table_name": ""}
+{"text": "Which fields in intrawarehouse.transfer are computed?", "response": "The intrawarehouse.transfer model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "Show me the relational structure of pos.call.log.", "response": "The pos.call.log model has 4 relational fields: branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.call.log", "table_name": ""}
+{"text": "Can you explain the purpose of base_import.tests.models.m2o.required.related?", "response": "The base_import.tests.models.m2o.required.related model represents Tests : Base Import Model, Many to One required related in the ERP system. It contains 8 fields and is used to manage tests : base import model, many to one required related data. Key fields include: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.m2o.required.related", "table_name": ""}
+{"text": "What are the relationships in stock.inventory.approval.matrix?", "response": "The stock.inventory.approval.matrix model has 18 relational fields: company_id -> res.company; branch_id -> res.branch; warehouse_id -> stock.warehouse; si_approval_matrix_line_ids -> stock.inventory.approval.matrix.line; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.inventory.approval.matrix", "table_name": ""}
+{"text": "What are common use cases for purchase.bill.union?", "response": "To use the purchase.bill.union model, you need to provide values for required fields: none. Readonly fields: name, reference, partner_id, date, amount, currency_id, company_id, vendor_bill_id, purchase_order_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.bill.union", "table_name": ""}
+{"text": "What does the pos.payment.edc model represent?", "response": "The pos.payment.edc model represents Pos Payment EDC in the ERP system. It contains 44 fields and is used to manage pos payment edc data. Key fields include: name, payment_state, payment_type, order_number, resp_data, pos_order_id, edc_type, version, trans_type, trans_amount, other_amount, pan, expiry_date, resp_code, rrn, approval_code, date, time, merchant_id, terminal_id, offline_flag, cardholder_name, pan_cashier_card, invoice_number, batch_number, issuer_id, installment_flag, dcc_flag, reedem_flag, info_amount, dcc_decimal_place, dcc_currency_name, dcc_exchange_rate, coupon_flag, filler, pos_branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.payment.edc", "table_name": ""}
+{"text": "What modules define mrp.workcenter?", "response": "The mrp.workcenter model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.workcenter", "table_name": ""}
+{"text": "Describe the field structure of account.asset.fiscal.line.", "response": "The account.asset.fiscal.line model has 14 fields: name, sequence, asset_id, amount_fiscal, remaining_value_fiscal, depreciated_value_fiscal, depreciation_date_fiscal, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 3, float: 3, date: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.asset.fiscal.line", "table_name": ""}
+{"text": "How is whatsapp.template implemented technically?", "response": "The whatsapp.template model is defined in module: equip3_crm_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "whatsapp.template", "table_name": ""}
+{"text": "What operations can I perform on qiscus.template?", "response": "To use the qiscus.template model, you need to provide values for required fields: none. Readonly fields: activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "qiscus.template", "table_name": ""}
+{"text": "What are common use cases for create.purchase.request.direct.lines?", "response": "To use the create.purchase.request.direct.lines model, you need to provide values for required fields: wiz_id, name, product_uom_id. Readonly fields: wiz_id, rem_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "create.purchase.request.direct.lines", "table_name": ""}
+{"text": "What are the available fields for forecast.quantity?", "response": "The forecast.quantity model has 11 fields: schedule_date, reference, product_id, source_location, destination_location, forecast_qty, product_uom, state, id, display_name, __last_update. Field types distribution: datetime: 2, many2one: 2, char: 4, float: 1, selection: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "forecast.quantity", "table_name": ""}
+{"text": "What models are connected to checklist.reason?", "response": "The checklist.reason model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "checklist.reason", "table_name": ""}
+{"text": "What are the available fields for resource.test?", "response": "The resource.test model has 12 fields: name, resource_id, company_id, resource_calendar_id, tz, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 5, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "resource.test", "table_name": ""}
+{"text": "Tell me about the account.ebupot model.", "response": "The account.ebupot model represents Account E-Bupot in the ERP system. It contains 18 fields and is used to manage account e-bupot data. Key fields include: year, name, is_used, invoice_ids, tax_report_id, date_from, date_to, partner_id, company_id, ebupot_template, tahun_pajak, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.ebupot", "table_name": ""}
+{"text": "What is the base.geo_provider model?", "response": "The base.geo_provider model represents Geo Provider in the ERP system. It contains 9 fields and is used to manage geo provider data. Key fields include: tech_name, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.geo_provider", "table_name": ""}
+{"text": "What are the available fields for pos.global.discount?", "response": "The pos.global.discount model has 14 fields: name, amount, product_id, reason, type, branch_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, float: 1, many2one: 4, selection: 1, many2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.global.discount", "table_name": ""}
+{"text": "How does pos.generate.efaktur relate to other models?", "response": "The pos.generate.efaktur model has 8 relational fields: invoice_ids -> pos.generate.efaktur.invoice; digunggung_ids -> pos.generate.efaktur.digunggung; gabungan_ids -> pos.generate.efaktur.gabungan; other_ids -> pos.generate.efaktur.other; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.generate.efaktur", "table_name": ""}
+{"text": "What are common use cases for res.city?", "response": "To use the res.city model, you need to provide values for required fields: name, country_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.city", "table_name": ""}
+{"text": "How is purchase.order.split implemented technically?", "response": "The purchase.order.split model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.order.split", "table_name": ""}
+{"text": "Describe the report.equip3_pos_general.pos_sale_report_template model in Odoo.", "response": "The report.equip3_pos_general.pos_sale_report_template model represents Template Report of sale in the ERP system. It contains 3 fields and is used to manage template report of sale data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_pos_general.pos_sale_report_template", "table_name": ""}
+{"text": "Tell me about the account.multipayment.credit model.", "response": "The account.multipayment.credit model represents   in the ERP system. It contains 22 fields and is used to manage   data. Key fields include: line_id, currency_id, invoice_id, account_id, invoice_date, invoice_date_due, original_amount, base_amount, original_unreconcile, base_unreconcile, is_full_reconcile, amount, payment_id, account_reverse_ids, account_reverse_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.multipayment.credit", "table_name": ""}
+{"text": "How is stock.picking.type used in the system?", "response": "The stock.picking.type model represents Picking Type in the ERP system. It contains 43 fields and is used to manage picking type data. Key fields include: name, color, sequence, sequence_id, sequence_code, default_location_src_id, default_location_dest_id, return_picking_type_id, show_entire_packs, warehouse_id, active, use_create_lots, use_existing_lots, show_operations, show_reserved, count_picking_draft, count_picking_ready, count_picking, count_picking_waiting, count_picking_late, count_picking_backorders, rate_picking_late, rate_picking_backorders, barcode, company_id, code, count_mo_todo, count_mo_waiting, count_mo_late, use_create_components_lots, branch_id, is_transit, filter_location_ids, stock_picking_dasboard_id, picking_ids, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.picking.type", "table_name": ""}
+{"text": "How does delivery.carrier relate to other models?", "response": "The delivery.carrier model has 8 relational fields: company_id -> res.company; product_id -> product.product; country_ids -> res.country; state_ids -> res.country.state; price_rule_ids -> delivery.price.rule; website_id -> website; create_uid -> res.users; write_uid -> res.users. Many2many fields: country_ids, state_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "delivery.carrier", "table_name": ""}
+{"text": "How does sh.mrp.pass.fail relate to other models?", "response": "The sh.mrp.pass.fail model has 6 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; mrp_id -> mrp.production; workorder_id -> mrp.workorder; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.mrp.pass.fail", "table_name": ""}
+{"text": "What business logic is in res.users.qiscuss?", "response": "To use the res.users.qiscuss model, you need to provide values for required fields: email, password. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.users.qiscuss", "table_name": ""}
+{"text": "Tell me about the vendor.payment.request model.", "response": "The vendor.payment.request model represents Vendor Payment Request in the ERP system. It contains 16 fields and is used to manage vendor payment request data. Key fields include: name, user_id, description, company_id, branch_id, component_line_id, state, amount_total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "vendor.payment.request", "table_name": ""}
+{"text": "What are the technical details of stock.warn.insufficient.qty.repair?", "response": "The stock.warn.insufficient.qty.repair model is defined in module: repair. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.warn.insufficient.qty.repair", "table_name": ""}
+{"text": "Show me the relational structure of stock.scrap.approval.matrix.", "response": "The stock.scrap.approval.matrix model has 18 relational fields: company_id -> res.company; warehouse_id -> stock.warehouse; branch_id -> res.branch; sc_approval_matrix_line_ids -> stock.scrap.approval.matrix.line; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.scrap.approval.matrix", "table_name": ""}
+{"text": "What modules define currency.log.api?", "response": "The currency.log.api model is defined in module: equip3_accounting_multicurrency. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "currency.log.api", "table_name": ""}
+{"text": "What operations can I perform on ir.module.module.exclusion?", "response": "To use the ir.module.module.exclusion model, you need to provide values for required fields: none. Readonly fields: exclusion_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.module.module.exclusion", "table_name": ""}
+{"text": "What models are connected to sh.tc.top.customer.wizard?", "response": "The sh.tc.top.customer.wizard model has 11 relational fields: team_id -> crm.team; currency_id -> res.currency; company_ids -> res.company; company_id -> res.company; top_customer_ids -> list.customer; top_customer_compare_ids -> list.customer.compare; lost_cust_ids -> lost.customer; new_cust_ids -> new.customer; sale_currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.tc.top.customer.wizard", "table_name": ""}
+{"text": "What modules define res.company?", "response": "The res.company model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.company", "table_name": ""}
+{"text": "How does report.equip3_pos_report.report_pos_payment relate to other models?", "response": "The report.equip3_pos_report.report_pos_payment model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_pos_report.report_pos_payment", "table_name": ""}
+{"text": "How to query change.production.qty data?", "response": "To use the change.production.qty model, you need to provide values for required fields: mo_id, product_qty. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "change.production.qty", "table_name": ""}
+{"text": "What operations can I perform on pos.order?", "response": "To use the pos.order model, you need to provide values for required fields: name, amount_tax, amount_total, amount_paid, amount_return, company_id, pricelist_id, session_id. Readonly fields: name, date_order, amount_tax, amount_total, amount_paid, amount_return, lines, company_id, pricelist_id, session_id, account_move, picking_count, failed_pickings, nb_print, pos_reference, sale_journal, fiscal_position_id, payment_ids, session_move_id, is_invoiced, is_tipped, tip_amount, cashier, currency_rate, receivable_invoice_count, payment_paid, total_before_discount, total_discount, total_after_discount, total_after_discount_w_o_tax, pos_coupon_id, is_past_date, self_order_id, statement_ids, signature, parent_id, sale_id, margin, booking_id, pos_branch_id, is_paid_full, currency_id, state, removed_user_id, receipt_count, return_order_id, return_order_state, ean13, is_show_pos_payment, customer_deposit_amount, plus_point, redeem_point, redeem_point_refund, location_id, date_order_str, amount_sales, amount_discount, amount_payment, amount_ppn, amount_nett_sales, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.order", "table_name": ""}
+{"text": "List all fields in the asset.asset.revalue model.", "response": "The asset.asset.revalue model has 22 fields: reason, asset_id, remaining_value, amount, journal_id, method_number, method_period, user_id, date, prev_method_number, prev_method_period, dispose_price, company_id, company_currency_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 8, monetary: 2, integer: 5, date: 1, float: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "asset.asset.revalue", "table_name": ""}
+{"text": "How to create records in product.removal?", "response": "To use the product.removal model, you need to provide values for required fields: name, method. Readonly fields: name, method, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.removal", "table_name": ""}
+{"text": "What fields does account.loan.post have?", "response": "The account.loan.post model has 10 fields: loan_id, journal_id, account_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.loan.post", "table_name": ""}
+{"text": "What are common use cases for stock.scrap?", "response": "To use the stock.scrap model, you need to provide values for required fields: name, company_id, product_id, scrap_location_id, product_uom_id, location_id, scrap_qty. Readonly fields: name, product_uom_category_id, tracking, move_id, state, filter_location_ids, filter_product_ids, product_usage_state, analytic_tag_ids, filter_lot_ids, filter_package_ids, filter_owner_ids, product_state, usage_type, warehouse_id, date_done, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.scrap", "table_name": ""}
+{"text": "Describe the field structure of stock.location.tag.", "response": "The stock.location.tag model has 10 fields: name, color, opacity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 3, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.location.tag", "table_name": ""}
+{"text": "How is bus.bus used in the system?", "response": "The bus.bus model represents Communication Bus in the ERP system. It contains 9 fields and is used to manage communication bus data. Key fields include: channel, message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "bus.bus", "table_name": ""}
+{"text": "How to query sale.order.option data?", "response": "To use the sale.order.option model, you need to provide values for required fields: name, product_id, price_unit, uom_id, quantity. Readonly fields: is_present, product_uom_category_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.option", "table_name": ""}
+{"text": "What models are connected to approval.request.reject?", "response": "The approval.request.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.request.reject", "table_name": ""}
+{"text": "What are the relationships in mail.blacklist.remove?", "response": "The mail.blacklist.remove model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.blacklist.remove", "table_name": ""}
+{"text": "How does auth_totp.wizard relate to other models?", "response": "The auth_totp.wizard model has 3 relational fields: user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "auth_totp.wizard", "table_name": ""}
+{"text": "How to query warehouse.capacity.excel.report data?", "response": "To use the warehouse.capacity.excel.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "warehouse.capacity.excel.report", "table_name": ""}
+{"text": "Can you explain the purpose of sh.payment.report.wizard?", "response": "The sh.payment.report.wizard model represents payment report wizard model in the ERP system. It contains 17 fields and is used to manage payment report wizard model data. Key fields include: date_start, date_end, state, user_ids, company_ids, company_id, currency_precision, user_data_dic, grand_journal_dic, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.payment.report.wizard", "table_name": ""}
+{"text": "What business logic is in ir.server.object.lines?", "response": "To use the ir.server.object.lines model, you need to provide values for required fields: col1, value, evaluation_type. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.server.object.lines", "table_name": ""}
+{"text": "Describe the field structure of pos.product.bom.line.", "response": "The pos.product.bom.line model has 11 fields: pos_bom_id, product_id, product_qty, product_uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.product.bom.line", "table_name": ""}
+{"text": "Describe the list.pay model in Odoo.", "response": "The list.pay model represents list.pay in the ERP system. It contains 16 fields and is used to manage list.pay data. Key fields include: order_dic_id, cash, bank, total, invoice, customer, invoice_date, payments_date, salesperson, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "list.pay", "table_name": ""}
+{"text": "Show me the relational structure of mail.template.", "response": "The mail.template model has 10 relational fields: model_id -> ir.model; attachment_ids -> ir.attachment; report_template -> ir.actions.report; mail_server_id -> ir.mail_server; ref_ir_act_window -> ir.actions.act_window; model_object_field -> ir.model.fields; sub_object -> ir.model; sub_model_object_field -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.template", "table_name": ""}
+{"text": "What foreign keys exist in project.sale.line.employee.map?", "response": "The project.sale.line.employee.map model has 8 relational fields: project_id -> project.project; employee_id -> hr.employee; sale_line_id -> sale.order.line; company_id -> res.company; timesheet_product_id -> product.product; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "project.sale.line.employee.map", "table_name": ""}
+{"text": "What does the website model represent?", "response": "The website model represents Website in the ERP system. It contains 64 fields and is used to manage website data. Key fields include: name, domain, country_group_ids, company_id, language_ids, default_lang_id, auto_redirect_lang, cookies_bar, logo, social_twitter, social_facebook, social_github, social_linkedin, social_youtube, social_instagram, social_default_image, has_social_default_image, google_analytics_key, google_management_client_id, google_management_client_secret, google_search_console, google_maps_api_key, user_id, cdn_activated, cdn_url, cdn_filters, partner_id, menu_id, homepage_id, custom_code_head, custom_code_footer, robots_txt, favicon, theme_id, specific_user_account, auth_signup_uninvited, channel_id, is_enable_vendor_notification, user_ids, is_enable_auto_portal_user, is_enable_company_portal_user, is_enable_company_contact_portal_user, crm_default_team_id, crm_default_user_id, karma_profile_min, pricelist_id, currency_id, salesperson_id, salesteam_id, pricelist_ids, all_pricelist_ids, cart_recovery_mail_template_id, cart_abandoned_delay, shop_ppg, shop_ppr, shop_extra_field_ids, warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "website", "table_name": ""}
+{"text": "What are the relationships in ir.qweb.field.date?", "response": "The ir.qweb.field.date model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb.field.date", "table_name": ""}
+{"text": "Describe the implementation of base.language.install.", "response": "The base.language.install model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base.language.install", "table_name": ""}
+{"text": "How to create records in apply.voucher?", "response": "To use the apply.voucher model, you need to provide values for required fields: none. Readonly fields: voucher_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "apply.voucher", "table_name": ""}
+{"text": "What are the technical details of mail.moderation?", "response": "The mail.moderation model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.moderation", "table_name": ""}
+{"text": "Tell me about the limit.approval.matrix model.", "response": "The limit.approval.matrix model represents Limit Approval Matrix in the ERP system. It contains 45 fields and is used to manage limit approval matrix data. Key fields include: name, company_id, branch_id, config, minimum_amt, maximum_amt, approver_matrix_line_ids, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "limit.approval.matrix", "table_name": ""}
+{"text": "How does product.supplierinfo relate to other models?", "response": "The product.supplierinfo model has 36 relational fields: purchase_requisition_id -> purchase.requisition; purchase_requisition_line_id -> purchase.requisition.line; name -> res.partner; product_uom -> uom.uom; product_uom_category_id -> uom.category; product_uom_new -> uom.uom; company_id -> res.company; currency_id -> res.currency; product_id -> product.product; product_tmpl_id -> product.template; request_partner_id -> res.partner; vendor_pricelist_approval_matrix -> vendor.pricelist.approval.matrix; approval_ids -> product.supplierinfo.approval; user_approval_ids -> res.users; current_user -> res.users; branch_id -> res.branch; approval_matrix_line_id -> product.supplierinfo.approval; name_old -> res.partner; branch_id_old -> res.branch; product_id_old -> product.product; product_tmpl_id_old -> product.template; product_uom_old -> uom.uom; company_id_old -> res.company; currency_id_old -> res.currency; vendor_pricelist_approval_matrix_old -> vendor.pricelist.approval.matrix; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_approval_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.supplierinfo", "table_name": ""}
+{"text": "What modules define coupon.coupon?", "response": "The coupon.coupon model is defined in module: coupon. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "coupon.coupon", "table_name": ""}
+{"text": "What are the technical details of bill.payment.report.xls?", "response": "The bill.payment.report.xls model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "bill.payment.report.xls", "table_name": ""}
+{"text": "What data can be stored in invoice.template.table?", "response": "The invoice.template.table model has 10 fields: template_id, field_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "invoice.template.table", "table_name": ""}
+{"text": "What methods are available in crm.salesperson.tracking?", "response": "The crm.salesperson.tracking model is defined in module: equip3_crm_tracking. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.salesperson.tracking", "table_name": ""}
+{"text": "How is account.asset.asset used in the system?", "response": "The account.asset.asset model represents Asset/Revenue Recognition in the ERP system. It contains 86 fields and is used to manage asset/revenue recognition data. Key fields include: entry_count, name, code, value, currency_id, note, category_id, date, active, partner_id, method_number, method_period, method_end, method_progress_factor, value_residual, method_time, prorata, depreciation_line_ids, salvage_value, invoice_id, type, account_analytic_id, analytic_tag_ids, first_depreciation_manual_date, user_id, is_monthly_depreciation, is_reset_january, months_remaining, method, cut_off_asset_date, date_first_depreciation, fiscal_category_id, method_fiscal, asset_type, asset_type_1, sub_asset_type, non_building_type, is_monthly_depreciation_fiscal, is_reset_january_fiscal, months_remaining_fiscal, method_number_fiscal, method_period_fiscal, method_end_fiscal, depreciation_line_ids_fiscal, asset_history_lines_ids, asset_value_residual, account_cip_id, state, state1, state2, approval_matrix_id, approved_matrix_ids, is_approval_matrix, is_approve_button, approval_matrix_line_id, request_partner_id, company_id, branch_id, asset_sequence, product_id, fiscal_prorata_temporis, location, po_ref, asset_post_entries_count, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.asset.asset", "table_name": ""}
+{"text": "Tell me about the website.mass_mailing.popup model.", "response": "The website.mass_mailing.popup model represents Mailing list popup in the ERP system. It contains 10 fields and is used to manage mailing list popup data. Key fields include: mailing_list_id, website_id, popup_content, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "website.mass_mailing.popup", "table_name": ""}
+{"text": "How do I use the base.geo_provider model?", "response": "To use the base.geo_provider model, you need to provide values for required fields: none. Readonly fields: tech_name, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.geo_provider", "table_name": ""}
+{"text": "What business logic is in account.internal.transfer?", "response": "To use the account.internal.transfer model, you need to provide values for required fields: none. Readonly fields: currency_id, create_date, create_uid, filter_branch_ids, approval_matrix_id, is_internal_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, analytic_group_ids, name, 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, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.internal.transfer", "table_name": ""}
+{"text": "What fields does base_import.tests.models.char.stillreadonly have?", "response": "The base_import.tests.models.char.stillreadonly model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.char.stillreadonly", "table_name": ""}
+{"text": "What data can be stored in account.journal?", "response": "The account.journal model has 92 fields: kanban_dashboard, kanban_dashboard_graph, json_activity_data, show_on_dashboard, color, check_manual_sequencing, check_sequence_id, check_next_number, check_printing_payment_method_selected, edi_format_ids, compatible_edi_ids, sequence_id, sequence_number_next, refund_sequence_id, refund_sequence_number_next, pos_payment_method_ids, name, code, active, type_control_ids, account_control_ids, default_account_type, default_account_id, payment_debit_account_id, payment_credit_account_id, suspense_account_id, restrict_mode_hash_table, sequence, invoice_reference_type, invoice_reference_model, currency_id, company_id, country_code, refund_sequence, sequence_override_regex, inbound_payment_method_ids, outbound_payment_method_ids, at_least_one_inbound, at_least_one_outbound, profit_account_id, loss_account_id, company_partner_id, bank_account_id, bank_statements_source, bank_acc_number, bank_id, sale_activity_type_id, sale_activity_user_id, sale_activity_note, alias_id, alias_domain, alias_name, journal_group_ids, secure_sequence_id, use_reconcile, branch_id, type, is_fiscal_book_exclude, pos_method_type, decimal_rounding, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 5, boolean: 15, integer: 10, many2one: 25, char: 11, many2many: 9, one2many: 5, selection: 7, date: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.journal", "table_name": ""}
+{"text": "What operations can I perform on ir.model.access?", "response": "To use the ir.model.access model, you need to provide values for required fields: name, model_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.model.access", "table_name": ""}
+{"text": "What are the technical details of report.equip3_pos_report.report_open_session?", "response": "The report.equip3_pos_report.report_open_session model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_pos_report.report_open_session", "table_name": ""}
+{"text": "How to create records in crm.phonecall2phonecall?", "response": "To use the crm.phonecall2phonecall model, you need to provide values for required fields: name, action. Readonly fields: name, user_id, contact_name, phone, tag_ids, date, team_id, action, partner_id, note, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.phonecall2phonecall", "table_name": ""}
+{"text": "Describe the many2many relations for account.deposit.reconcile.", "response": "The account.deposit.reconcile model has 3 relational fields: allocation_line_ids -> invoice.deposit.line.reconcile; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.deposit.reconcile", "table_name": ""}
+{"text": "How to query report.equip3_inventory_masterdata.report_product_tmpl_forecast data?", "response": "To use the report.equip3_inventory_masterdata.report_product_tmpl_forecast model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_inventory_masterdata.report_product_tmpl_forecast", "table_name": ""}
+{"text": "How to query website.mass_mailing.popup data?", "response": "To use the website.mass_mailing.popup 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "website.mass_mailing.popup", "table_name": ""}
+{"text": "What are common use cases for budget.change.req?", "response": "To use the budget.change.req model, you need to provide values for required fields: requested_id, budget_std_id, date, state, company_id. Readonly fields: name, state, approval_matrix, is_allowed_to_approval_matrix, approval_matrix_line_id, is_approve_button, company_id, currency_id, state1, state2, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "budget.change.req", "table_name": ""}
+{"text": "Describe the hr.employee.public model in Odoo.", "response": "The hr.employee.public model represents Public Employee in the ERP system. It contains 42 fields and is used to manage public employee data. Key fields include: create_date, name, active, department_id, job_id, job_title, company_id, address_id, mobile_phone, work_phone, work_email, work_location, user_id, resource_id, resource_calendar_id, tz, color, child_ids, image_1920, image_1024, image_512, image_256, image_128, parent_id, coach_id, user_partner_id, subordinate_ids, hr_presence_state, last_activity, last_activity_time, hr_icon_display, goal_ids, badge_ids, has_badges, direct_badge_ids, child_all_count, id, display_name, create_uid, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "hr.employee.public", "table_name": ""}
+{"text": "What methods are available in z.report.wizard?", "response": "The z.report.wizard model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "z.report.wizard", "table_name": ""}
+{"text": "What operations can I perform on account.payment.reconcile.line?", "response": "To use the account.payment.reconcile.line model, you need to provide values for required fields: currency_id, payment_type. Readonly fields: currency_id, payment_type, partner_id, amount_due, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.payment.reconcile.line", "table_name": ""}
+{"text": "Show me the fields of report.accounting_pdf_reports.report_journal.", "response": "The report.accounting_pdf_reports.report_journal model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.accounting_pdf_reports.report_journal", "table_name": ""}
+{"text": "What models are connected to cancel.supplier.memory?", "response": "The cancel.supplier.memory model has 3 relational fields: supplier_id -> product.supplierinfo; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "cancel.supplier.memory", "table_name": ""}
+{"text": "What are common use cases for ir.model.access?", "response": "To use the ir.model.access model, you need to provide values for required fields: name, model_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.model.access", "table_name": ""}
+{"text": "What foreign keys exist in mrp.document?", "response": "The mrp.document model has 8 relational fields: ir_attachment_id -> ir.attachment; create_uid -> res.users; write_uid -> res.users; company_id -> res.company; original_id -> ir.attachment; website_id -> website; theme_template_id -> theme.ir.attachment; partner -> res.partner. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.document", "table_name": ""}
+{"text": "What is the mail.message.subtype model?", "response": "The mail.message.subtype model represents Message subtypes in the ERP system. It contains 16 fields and is used to manage message subtypes data. Key fields include: name, description, internal, parent_id, relation_field, res_model, default, sequence, hidden, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.message.subtype", "table_name": ""}
+{"text": "Which fields in gamification.goal.definition are computed?", "response": "The gamification.goal.definition model is defined in module: gamification. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "gamification.goal.definition", "table_name": ""}
+{"text": "What foreign keys exist in purchase.agreement.approval.matrix?", "response": "The purchase.agreement.approval.matrix model has 17 relational fields: company_id -> res.company; branch_id -> res.branch; approval_matrix_purchase_agreement_line_ids -> approval.matrix.purchase.agreement.line; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.agreement.approval.matrix", "table_name": ""}
+{"text": "What foreign keys exist in report.stock.quantity?", "response": "The report.stock.quantity model has 5 relational fields: product_tmpl_id -> product.template; product_id -> product.product; move_ids -> stock.move; company_id -> res.company; warehouse_id -> stock.warehouse. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.stock.quantity", "table_name": ""}
+{"text": "Describe the account.invoice.report model in Odoo.", "response": "The account.invoice.report model represents Invoices Statistics in the ERP system. It contains 28 fields and is used to manage invoices statistics data. Key fields include: move_id, journal_id, company_id, company_currency_id, partner_id, commercial_partner_id, country_id, invoice_user_id, move_type, state, payment_state, fiscal_position_id, invoice_date, quantity, product_id, product_uom_id, product_categ_id, invoice_date_due, account_id, analytic_account_id, price_subtotal, price_average, team_id, branch_id, pos_branch_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.invoice.report", "table_name": ""}
+{"text": "What methods are available in warehouse.capacity.report?", "response": "The warehouse.capacity.report model is defined in module: equip3_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "warehouse.capacity.report", "table_name": ""}
+{"text": "Tell me about the ctm.dynamic.balance.sheet.report model.", "response": "The ctm.dynamic.balance.sheet.report model represents ctm.dynamic.balance.sheet.report in the ERP system. It contains 29 fields and is used to manage ctm.dynamic.balance.sheet.report data. Key fields include: company_id, journal_ids, account_ids, account_tag_ids, analytic_ids, analytic_tag_ids, display_account, target_move, date_from, date_to, analytic_group_ids, comparison, previous, report_currency_id, book, consolidate, comp_detail, filter_budget, budget, debit_credit, entities_comparison, all_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ctm.dynamic.balance.sheet.report", "table_name": ""}
+{"text": "What are the technical details of mrp.bom.tools?", "response": "The mrp.bom.tools model is defined in module: equip3_manuf_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.bom.tools", "table_name": ""}
+{"text": "What foreign keys exist in return.approval.matrix.line?", "response": "The return.approval.matrix.line model has 8 relational fields: approver -> res.users; last_approved -> res.users; return_approval_matrix_id1 -> return.approval.matrix; picking_id -> stock.picking; approved_users -> res.users; dev_rma_id -> dev.rma.rma; create_uid -> res.users; write_uid -> res.users. Many2many fields: approver, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "return.approval.matrix.line", "table_name": ""}
+{"text": "What modules define image.mixin?", "response": "The image.mixin model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "image.mixin", "table_name": ""}
+{"text": "What data can be stored in account.cash.flow.statement?", "response": "The account.cash.flow.statement model has 21 fields: date_from, date_to, today, levels, account_ids, company_ids, comparison, previous, comp_detail, type_report, journal_ids, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 3, selection: 4, many2many: 3, integer: 2, boolean: 1, many2one: 4, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.cash.flow.statement", "table_name": ""}
+{"text": "What is the pos.payment.method model?", "response": "The pos.payment.method model represents Point of Sale Payment Methods in the ERP system. It contains 54 fields and is used to manage point of sale payment methods data. Key fields include: name, receivable_account_id, is_cash_count, cash_journal_id, split_transactions, open_session_ids, config_ids, company_id, use_payment_terminal, hide_use_payment_terminal, active, apply_charges, fees_amount, fees_type, fees_product_id, optional, shortcut_key, jr_use_for, fullfill_amount, shortcut_keyboard, cheque_bank_information, discount, discount_type, discount_amount, discount_product_id, is_bank, generate_invoice, invoice_partner_id, able_use_card, is_mdr, is_mdr_discount, mdr_paid_by, mdr_intermediary_account_id, mdr_ids, is_receivables, account_journal_id, is_receivables_show, is_deposit_payment, is_edc_bca, is_edc_manual_input, edc_port, trans_type, trans_type_code, is_payment_edc, payment_edc_url, installment_tenor_ids, installment_plan, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.payment.method", "table_name": ""}
+{"text": "How do I use the stock.warn.insufficient.qty model?", "response": "To use the stock.warn.insufficient.qty model, you need to provide values for required fields: product_id, location_id, quantity, product_uom_name. Readonly fields: product_id, location_id, quant_ids, quantity, product_uom_name, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.warn.insufficient.qty", "table_name": ""}
+{"text": "What are the available fields for repair.line?", "response": "The repair.line model has 26 fields: name, repair_id, company_id, currency_id, type, product_id, invoiced, price_unit, price_subtotal, tax_id, product_uom_qty, product_uom, product_uom_category_id, invoice_line_id, location_id, location_dest_id, move_id, lot_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2one: 13, selection: 2, boolean: 1, float: 3, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "repair.line", "table_name": ""}
+{"text": "Describe the many2many relations for product.margin.", "response": "The product.margin model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.margin", "table_name": ""}
+{"text": "What are the relationships in gamification.challenge.line?", "response": "The gamification.challenge.line model has 4 relational fields: challenge_id -> gamification.challenge; definition_id -> gamification.goal.definition; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "gamification.challenge.line", "table_name": ""}
+{"text": "Show me the fields of sh.custom.model.tab.", "response": "The sh.custom.model.tab model has 18 fields: name, label, groups, sequence, view_id, tab_list, invisible_tab, sh_position, parent_view_id, parent_model, parent_model_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2many: 1, integer: 2, many2one: 4, selection: 2, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.custom.model.tab", "table_name": ""}
+{"text": "Describe the warranty.settings model in Odoo.", "response": "The warranty.settings model represents Warranty Settings in the ERP system. It contains 854 fields and is used to manage warranty settings data. Key fields include: renew_notif, setting_desc, warranty_tmpl, renew_tmpl, company_id, create_warranty_from_saleorder, user_default_rights, external_email_server_default, module_base_import, module_google_calendar, module_microsoft_calendar, module_google_drive, module_google_spreadsheet, module_auth_oauth, module_auth_ldap, module_base_gengo, module_account_inter_company_rules, module_pad, module_voip, module_web_unsplash, module_partner_autocomplete, module_base_geolocalize, module_google_recaptcha, report_footer, group_multi_currency, paperformat_id, external_report_layout_id, show_effect, company_count, active_user_count, language_count, company_name, company_informations, app_default_superbar_lazy_search, geoloc_provider_id, geoloc_provider_techname, geoloc_provider_googlemap_key, recaptcha_public_key, recaptcha_private_key, recaptcha_min_score, fail_counter, alias_domain, unsplash_access_key, app_system_name, app_show_lang, app_show_debug, app_show_documentation, app_show_documentation_dev, app_show_support, app_show_account, app_show_enterprise, app_show_share, app_show_poweredby, group_show_author_in_apps, module_odoo_referral, app_documentation_url, app_documentation_dev_url, app_support_url, app_account_title, app_account_url, app_enterprise_url, app_ribbon_name, auth_signup_reset_password, auth_signup_template_user_id, resource_calendar_id, module_hr_presence, module_hr_skills, hr_presence_control_login, hr_presence_control_email, hr_presence_control_ip, module_hr_attendance, hr_presence_control_email_amount, hr_presence_control_ip_list, hr_employee_self_edit, kpi_company_id, kpi_history_tolerance, show_kpi_help, group_discount_per_so_line, group_uom, group_product_variant, module_sale_product_configurator, module_sale_product_matrix, group_stock_packaging, group_product_pricelist, group_sale_pricelist, product_pricelist_setting, product_weight_in_lbs, product_volume_volume_in_cubic_feet, enable_menu_search, enable_web_push_notification, api_key, vapid, config_details, sh_multi_barcode_unique, is_sh_product_qrcode_generator_when_create, snailmail_color, snailmail_cover, snailmail_duplex, digest_emails, digest_id, sh_product_stock, sh_product_attribute, sh_product_image, sh_product_category, sh_product_code, sh_product_barcode, sh_product_sale_price, sh_product_sale_description, sh_touch_kyboard, sh_welcome_message, sh_message, sh_company_logo, sh_display, sh_display_view, sh_display_landscape, sh_display_portrait, sh_delay_screen, has_accounting_entries, currency_id, has_chart_of_accounts, chart_template_id, purchase_tax_id, tax_calculation_rounding_method, module_account_accountant, group_analytic_accounting, group_warning_account, group_cash_rounding, group_show_line_subtotals_tax_excluded, group_show_line_subtotals_tax_included, group_show_sale_receipts, group_show_purchase_receipts, show_line_subtotals_tax_selection, module_account_budget, module_account_payment, module_account_reports, module_account_check_printing, module_account_batch_payment, module_account_sepa, module_account_sepa_direct_debit, module_account_plaid, module_account_yodlee, module_account_bank_statement_import_qif, module_account_bank_statement_import_ofx, module_account_bank_statement_import_csv, module_account_bank_statement_import_camt, module_currency_rate_live, module_account_intrastat, module_product_margin, module_l10n_eu_service, module_account_taxcloud, module_account_invoice_extract, module_snailmail_account, tax_exigibility, tax_cash_basis_journal_id, account_cash_basis_base_account_id, qr_code, invoice_is_print, invoice_is_email, incoterm_id, invoice_terms, use_invoice_terms, country_code, crm_alias_prefix, generate_lead_from_alias, group_use_lead, group_use_recurring_revenues, module_crm_iap_lead, module_crm_iap_lead_website, module_crm_iap_lead_enrich, module_mail_client_extension, lead_enrich_auto, lead_mining_in_pipeline, predictive_lead_scoring_start_date, predictive_lead_scoring_start_date_str, predictive_lead_scoring_fields, predictive_lead_scoring_fields_str, group_mass_mailing_campaign, mass_mailing_outgoing_mail_server, mass_mailing_mail_server_id, show_blacklist_buttons, module_project_forecast, module_hr_timesheet, group_subtask_project, group_project_rating, group_project_recurring_tasks, module_product_expiry, group_stock_production_lot, group_lot_on_delivery_slip, group_stock_tracking_lot, group_stock_tracking_owner, group_stock_adv_location, group_warning_stock, group_stock_sign_delivery, module_stock_picking_batch, module_stock_barcode, stock_move_email_validation, stock_mail_confirmation_template_id, module_stock_sms, group_stock_multi_locations, website_id, website_name, website_domain, website_country_group_ids, website_company_id, website_logo, language_ids, website_language_count, website_default_lang_id, website_default_lang_code, specific_user_account, website_cookies_bar, google_analytics_key, google_management_client_id, google_management_client_secret, google_search_console, cdn_activated, cdn_url, cdn_filters, social_twitter, social_facebook, social_github, social_linkedin, social_youtube, social_instagram, has_social_network, favicon, social_default_image, google_maps_api_key, group_multi_website, has_google_analytics, has_google_analytics_dashboard, has_google_maps, has_google_search_console, has_default_share_image, account_check_printing_layout, account_check_printing_date_label, account_check_printing_multi_stub, account_check_printing_margin_top, account_check_printing_margin_left, account_check_printing_margin_right, vat_check_vies, group_show_form_view, picking_operation_type, sh_it_barcode_mobile_type, sh_it_bm_is_cont_scan, sh_it_bm_is_notify_on_success, sh_it_bm_is_notify_on_fail, sh_it_bm_is_sound_on_success, sh_it_bm_is_sound_on_fail, sh_it_bm_is_add_product, module_project_timesheet_synchro, module_project_timesheet_holidays, project_time_mode_id, timesheet_encode_uom_id, timesheet_min_duration, timesheet_rounding, is_encode_uom_days, manufacturing_lead, use_manufacturing_lead, group_mrp_byproducts, module_mrp_mps, module_mrp_plm, module_mrp_workorder, module_quality_control, module_mrp_subcontracting, group_mrp_routings, group_locked_by_default, group_expiry_date_on_delivery_slip, lock_confirmed_po, po_lock, po_order_approval, po_double_validation, po_double_validation_amount, company_currency_id, default_purchase_method, group_warning_purchase, module_account_3way_match, module_purchase_requisition, module_purchase_product_matrix, po_lead, use_po_lead, group_send_reminder, module_sg_bank_reconcile, module_sg_dbs_giro, sh_invoice_online_signature, sh_enable_approval, sh_restrict_for_close_period, invoice_is_snailmail, module_stock_landed_costs, stock_qty_forecast_method, stock_qty_forecast_interval, stock_qty_predicted_periods, stock_move_sms_validation, stock_sms_confirmation_template_id, channel_id, group_enable_discuss, group_disable_poll, app_stop_subscribe, inv_cost, is_cost_price_per_warehouse, fiscalyear_last_day, fiscalyear_last_month, period_lock_date, fiscalyear_lock_date, group_fiscal_year, sale_tax_id, module_pos_mercury, module_pos_adyen, module_pos_six, update_stock_quantities, module_stock_dropshipping, days_to_purchase, is_installed_sale, group_auto_done_setting, module_sale_margin, quotation_validity_days, use_quotation_validity_days, group_warning_sale, portal_confirmation_sign, portal_confirmation_pay, group_sale_delivery_address, group_proforma_sales, default_invoice_policy, deposit_default_product_id, auth_signup_uninvited, module_delivery, module_delivery_dhl, module_delivery_fedex, module_delivery_ups, module_delivery_usps, module_delivery_bpost, module_delivery_easypost, module_product_email_template, module_sale_coupon, module_sale_amazon, automatic_invoice, template_id, confirmation_template_id, sh_group_enable_report_section, group_enable_merge_purchase_order, po_operation_type, cancel_receipt, cancel_bill, group_enable_purchase_checklist, group_enable_purchase_custom_product_template, purchase_show_signature, chk_sign_confirm, purchase_enable_other_sign_option, sh_expiry_notification, sh_is_notify_vendor, sh_on_date_notify, enter_before_first_notify, enter_before_second_notify, enter_before_third_notify, enter_after_first_notify, enter_after_second_notify, enter_after_third_notify, attachment_email, group_enable_purchase_multi_product_adv, sh_purchase_configuration_limit, group_enable_purchase_order_history, item_limit_purchase, record_based_on_purchase, group_enable_purchase_price_history, purchase_order_information_in_message, purchase_product_detail_in_message, purchase_signature, purchase_display_in_message, po_send_pdf_in_message, sh_auto_add_followers, sh_portal_user_create, sh_tender_document_manage, sh_purchase_revision, is_enable_vendor_notification, user_ids, is_enable_auto_portal_user, is_enable_company_portal_user, is_enable_company_contact_portal_user, crm_default_team_id, crm_default_user_id, l10n_id_tax_address, l10n_id_tax_name, reminder_frequency, group_sale_order_template, company_so_template_id, module_sale_quotation_builder, security_lead, group_display_incoterm, group_lot_on_invoice, use_security_lead, default_picking_policy, sh_manage_tender_doc_portal, lc_journal_id, salesperson_id, salesteam_id, module_website_sale_delivery, sale_delivery_settings, group_delivery_invoice_address, module_website_sale_digital, module_website_sale_wishlist, module_website_sale_comparison, module_website_sale_stock, module_account, cart_recovery_mail_template, cart_abandoned_delay, mailsend_check, email_notification_days, res_user_ids, validate_picking, create_invoice, validate_invoice, allow_auto_intercompany, ks_forecast_method, use_sale_order_note, sale_order_note, keep_name_so, sh_sale_barcode_mobile_type, sh_sale_bm_is_cont_scan, sh_sale_bm_is_notify_on_success, sh_sale_bm_is_notify_on_fail, sh_sale_bm_is_sound_on_success, sh_sale_bm_is_sound_on_fail, sh_purchase_barcode_mobile_type, sh_purchase_bm_is_cont_scan, sh_purchase_bm_is_notify_on_success, sh_purchase_bm_is_notify_on_fail, sh_purchase_bm_is_sound_on_success, sh_purchase_bm_is_sound_on_fail, sh_invoice_barcode_mobile_type, sh_invoice_bm_is_cont_scan, sh_invoice_bm_is_notify_on_success, sh_invoice_bm_is_notify_on_fail, sh_invoice_bm_is_sound_on_success, sh_invoice_bm_is_sound_on_fail, sh_bom_barcode_mobile_type, sh_bom_bm_is_cont_scan, sh_bom_bm_is_notify_on_success, sh_bom_bm_is_notify_on_fail, sh_bom_bm_is_sound_on_success, sh_bom_bm_is_sound_on_fail, sh_stock_barcode_mobile_type, sh_stock_bm_is_cont_scan, sh_stock_bm_is_notify_on_success, sh_stock_bm_is_notify_on_fail, sh_stock_bm_is_sound_on_success, sh_stock_bm_is_sound_on_fail, sh_stock_bm_is_add_product, sh_inventory_adjt_barcode_mobile_type, sh_inventory_adjt_bm_is_cont_scan, sh_inventory_adjt_bm_is_notify_on_success, sh_inventory_adjt_bm_is_notify_on_fail, sh_inventory_adjt_bm_is_sound_on_success, sh_inventory_adjt_bm_is_sound_on_fail, sh_product_barcode_mobile_type, sh_product_bm_is_cont_scan, sh_product_bm_is_notify_on_success, sh_product_bm_is_notify_on_fail, sh_product_bm_is_sound_on_success, sh_product_bm_is_sound_on_fail, sh_product_bm_is_default_code, sh_product_bm_is_lst_price, sh_product_bm_is_qty_available, sh_product_bm_is_virtual_available, sh_global_document_search_is_enable, sh_global_document_search_is_sale, sh_global_document_search_is_purchase, sh_global_document_search_is_picking, sh_global_document_search_is_invoice, sh_global_document_search_is_product, sh_global_document_search_is_lot, sh_global_document_search_is_location, sh_global_document_search_action_target_type, sale_credit_limit_email_alerts, sale_email_specific_user_id, quot_to_po, so_to_po, inventory_availability, available_threshold, website_warehouse_id, down_payment_product_id, implementor_setting, general, purchase, sales, inventory, manufacturing, central_kitchen, human_resource, pos, simple_manufacturing, assembly, cutting, mining, agriculture, show_branch, past_x_days_sales, currency_exchange_journal_id, income_currency_exchange_account_id, expense_currency_exchange_account_id, unrealized_exchange_journal_id, income_unrealized_exchange_account_id, expense_unrealized_exchange_account_id, is_inverse_rate, is_taxes_rate, tax_discount_policy, sale_account_id, purchase_account_id, interest_income, interest_expense, deposit_reconcile_journal_id, journal_id, deposit_account_id, petty_cash_expense_account_id, overdue_template, tax_rounding_type, accounting, is_credit_note_approval_matrix, is_refund_approval_matrix, is_customer_deposit_approval_matrix, is_vendor_deposit_approval_matrix, is_receipt_giro_approval_matrix, is_payment_giro_approval_matrix, is_purchase_currency_approval_matrix, is_budget_approval_matrix, is_budget_change_req_approval_matrix, is_purchase_budget_approval_matrix, is_purchase_budget_change_req_approval_matrix, is_internal_transaction, is_analytic_groups_balance_sheet, is_assets_approving_matrix, is_cash_advance_approving_matrix, is_invoice_approval_matrix, is_bill_approval_matrix, is_other_income_approval_matrix, is_other_expense_approval_matrix, is_customer_multi_receipt_approval_matrix, is_vendor_multipayment_approval_matrix, is_receipt_approval_matrix, is_payment_approval_matrix, is_payment_voucher_approval_matrix, group_is_credit_note_approval_matrix, group_is_refund_approval_matrix, group_is_customer_deposit_approval_matrix, group_is_vendor_deposit_approval_matrix, group_is_receipt_giro_approval_matrix, group_is_payment_giro_approval_matrix, group_is_internal_transfer_approval_matrix, group_is_purchase_currency_approval_matrix, group_is_budget_approval_matrix, group_is_budget_change_req_approval_matrix, group_is_purchase_budget_approval_matrix, group_is_purchase_budget_change_req_approval_matrix, group_account_asset_category_fiscal, group_assets_approving_matrix, group_cash_advance_approval_matrix, group_is_invoice_approval_matrix, group_is_bill_approval_matrix, group_is_other_income_approval_matrix, group_is_other_expense_approval_matrix, group_is_customer_multi_receipt_approval_matrix, group_is_vendor_multipayment_approval_matrix, group_is_receipt_approval_matrix, group_is_payment_approval_matrix, group_is_payment_voucher_approval_matrix, module_om_account_budget, Use_received_date, customer_availability, automated_invoice_followup, followup_sending_date, reminder_interval_before, reminder_interval_before_unit, reminder_notification_before, reminder_interval_after, reminder_interval_after_unit, reminder_notification_after, invoice_bill_reminder, reminder_interval_before_invoice, reminder_interval_after_invoice, reminder_interval_before_unit_invoice, eminder_interval_after_unit_invoice, reminder_notification_before_invoice, reminder_notification_after_invoice, days_bill_before, days_bill_after, days_invoice_before, days_invoice_after, sending_date_bill_before, sending_date_bill_after, sending_date_invoice_before, sending_date_invoice_after, date_last_reminder_due_date, date_last_reminder_after_due_date, date_last_reminder_bill_due_date, date_last_reminder_bill_after_due_date, date_last_reminder_bill_before_due_date, is_invoice_cutoff_date, invoice_cutoff_date, post_discount_account, prefix_limit, is_material_request_approval_matrix, is_internal_transfer_approval_matrix, is_stock_count_approval, is_product_usage_approval, is_return_orders, return_type, is_inventory_adjustment_with_value, putaway_max_capacity, set_warehouse_sublevel, warehouse_sublevel_zone, warehouse_sublevel_shelf, warehouse_sublevel_rack, warehouse_sublevel_bin, group_is_three_dimension_warehouse, is_mbs_on_transfer_operations, is_mbs_on_product_usage, is_mbs_on_stock_count_and_inventory_adjustment, outgoing_routing_strategy, sort_quants_by, routing_order, is_receiving_notes_approval_matrix, is_adj_picking, is_delivery_order_approval_matrix, brand_setting, is_manufacturing_plan, allow_submit_purchase_request, allow_submit_material_request, mo_force_done, manufacturing_plan_conf, manufacturing_order_conf, mrp_plan_partial_availability, mp_auto_reserve_availability_materials, mo_auto_reserve_availability_materials, production_record_conf, mrp_production_partial_availability, mrp_submit_purchase_request, mrp_submit_material_request, mrp_force_done, manufacturing_mps, manufacturing_period, manufacturing_period_to_display, autogenerated_based_methods, send_wa_approval_notification_mrp, send_wa_approval_notification_mp, send_wa_approval_notification_mpr, is_vendor_approval_matrix, is_purchase_order_approval_matrix, is_purchase_request_approval_matrix, is_vendor_pricelist_approval_matrix, is_purchase_tender_approval_matrix, purchase_approval_matrix, is_blanket_order_approval_matrix, is_good_services_order, is_purchase_tender, is_blanket_order, is_direct_purchase_approval_matrix, is_pr_department, is_price_ratting_rfq_tender, retail, module_equip3_purchase_rental, is_product_brand_filter, is_product_vendor_pricelist_filter, is_service_work_order, is_purchase_request_assign_user, group_create_purchase_request_direct, is_customer_approval_matrix, is_customer_limit_matrix, is_over_limit_validation, is_bo_approval_matrix, show_sale_barcode_mobile_type, sh_sale_barcode_mobile_type_new, group_om_account_budget, credit_note_expiry_date, bom_tools, sale_order_multiple_pricelist, automatic_confirm_saleorder, automatic_invoice_create, is_delivery_acknowledgement, is_broadcast_order, module_pragmatic_portal_user, module_pragmatic_delivery_acknowledgement, module_pragmatic_website_cash_on_delivery, commission_pay_on, commission_calc, commission_pay_by, is_message_rn, send_notification_users_ids, bank_integrate_url, bank_integrate_username, bank_integrate_password, validate_api, accounting_budget_use_theoretical_achievement, is_pajak_express_integration, pajak_express_url, pajak_express_transaction_url, pajak_express_username, pajak_express_password, validate_api_first, validate_api_express, validate_api_express_fail, group_is_pajak_express_integration, is_call_bi_api, is_call_kemenkeu_api, token_kemenkeu_api, internal_type, ex_period, material_request, is_product_service_operation, is_product_service_operation_delivery, mr_expiry_days, itr_expiry_days, is_return_limit_policy, return_policy_days, is_display_warehouse_address, module_procurement_jit, is_warehouse_shipments, qty_can_minus, is_vendor_approval_email, is_vendor_approval_whatsapp, is_vendor_pricelist_approval_email, is_vendor_pricelist_approval_whatsapp, sale_matrix_config, is_total_amount, total_sequence, total_sequence_select, is_margin_amount, margin_sequence, margin_sequence_select, is_discount_amount, discount_sequence, discount_sequence_select, expired_date, multilevel_disc_sale, is_wa_so_approval, is_email_so_approval, show_select_product_button, lock_sale_order, product_pricelist_default, auto_mail, group_multi_do, whatsapp_instance_id, whatsapp_token, qr_code_image, whatsapp_authenticate, product_expiry, expiry_days_select, group_analytic_tags, pu_barcode_mobile_type, pu_bm_is_cont_scan, pu_bm_is_notify_on_success, pu_bm_is_notify_on_fail, pu_bm_is_sound_on_success, pu_bm_is_sound_on_fail, pu_bm_is_add_product, pr_expiry_notification, pr_on_date_notify, pr_enter_before_first_notify, pr_enter_after_first_notify, pr_expiry_date, pr_expiry_date_goods, pr_expiry_date_services, rfq_exp_date, po_exp_date, rfq_exp_date_goods, rfq_exp_date_services, po_exp_date_goods, po_exp_date_services, max_percentage, pr_qty_limit, multilevel_disc, is_email_notification_req, is_whatsapp_notification_req, vendor_purchase_limit, is_email_notification, is_whatsapp_notification, pr_order_average_price, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, customer_credit_limit, customer_max_invoice_overdue_days, customer_open_invoice_limit, is_over_credit_limit, over_credit_limit_sequence, over_credit_limit_sequence_select, is_invoice_overdue, invoice_overdue_sequence, invoice_overdue_sequence_select, open_invoice_limit, open_invoice_limit_sequence, open_invoice_limit_sequence_select, is_wa_overlimit_approval, is_email_overlimit_approval, is_email_notification_customer_credit, is_whatsapp_notification_customer_credit, group_use_multi_salesperson_on_leads, is_auto_follow_up, interval_number, interval_type, number_of_repetition, expired_lot_serial_no, is_auto_validate, scrap_income_id, scrap_expense_id, pt_expiry_notification, pt_on_date_notify, pt_enter_before_first_notify, pt_enter_after_first_notify, pt_expiry_date, bo_expiry_notification, bo_enter_before_first_notify, bo_enter_after_first_notify, pt_goods_order_expiry_date, pt_service_order_expiry_date, bo_goods_order_expiry_date, bo_service_order_expiry_date, is_email_notification_tender, is_whatsapp_notification_tender, is_email_notification_bo, is_whatsapp_notification_bo, notifications_expiry_voucher, notifications_time, bo_expiry_date, bo_before_exp_notify, bo_days_before_exp_notify, bo_on_date_notify, bo_approval_email_notify, bo_approval_wa_notify, is_order_rounding, order_rounding_type, rounding_multiplier, pos_product_discount1_id, apply_rounding_type, rounding_method_id, pos_def_receipt_template_id, is_pos_receivable, direct_control, qty_limit, budget_limit, is_email_notification_direct_purchase, is_whatsapp_notification_direct_purchase, is_post_closing_cashbox_value_in_session, allow_create_member_in_pos_screen, pkp_customer, membership_pluspoint_rounding, membership_pluspoint_rounding_type, membership_pluspoint_rounding_multiplier, is_pos_use_deposit, is_return_request_approval_matrix, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "warranty.settings", "table_name": ""}
+{"text": "What is the payment.voucher.line model?", "response": "The payment.voucher.line model represents Payment voucher Line in the ERP system. It contains 18 fields and is used to manage payment voucher line data. Key fields include: invoice_number_id, invoice_date, currency_id, untaxed_amount, tax_amount, total_invoice_amount, amount_due, amount, voucher_id, state, voucher_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "payment.voucher.line", "table_name": ""}
+{"text": "How does res.branch relate to other models?", "response": "The res.branch model has 18 relational fields: analytic_tag_ids -> account.analytic.tag; company_id -> res.company; state_id -> res.country.state; country_id -> res.country; user_id -> res.users; user_ids -> res.users; config_ids -> pos.config; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, user_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.branch", "table_name": ""}
+{"text": "What does the web_editor.converter.test model represent?", "response": "The web_editor.converter.test model represents Web Editor Converter Test in the ERP system. It contains 18 fields and is used to manage web editor converter test data. Key fields include: char, integer, float, numeric, many2one, binary, date, datetime, selection_str, html, text, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "web_editor.converter.test", "table_name": ""}
+{"text": "What modules define uom.category?", "response": "The uom.category model is defined in module: uom. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "uom.category", "table_name": ""}
+{"text": "How to create records in list.category?", "response": "To use the list.category 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "list.category", "table_name": ""}
+{"text": "What are the technical details of stock.warehouse?", "response": "The stock.warehouse model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.warehouse", "table_name": ""}
+{"text": "Tell me about the stock.scrap.approval.matrix model.", "response": "The stock.scrap.approval.matrix model represents Stock Scrap Approval Matrix in the ERP system. It contains 44 fields and is used to manage stock scrap approval matrix data. Key fields include: name, company_id, warehouse_id, branch_id, approval_line_count, sc_approval_matrix_line_ids, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.scrap.approval.matrix", "table_name": ""}
+{"text": "How do I use the service.work.order.line model?", "response": "To use the service.work.order.line model, you need to provide values for required fields: product_id. Readonly fields: sequence2, product_id, description, initial_demand, remaining, quantity_done, account_analytic_tag_ids, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "service.work.order.line", "table_name": ""}
+{"text": "How is asset.cip.line used in the system?", "response": "The asset.cip.line model represents asset.cip.line in the ERP system. It contains 15 fields and is used to manage asset.cip.line data. Key fields include: product_id, label, account_id, amount, cip_id, move_id, move_check, move_posted_check, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "asset.cip.line", "table_name": ""}
+{"text": "List all fields in the replace.product.wizard model.", "response": "The replace.product.wizard model has 11 fields: product_id, replace_product_id, replace_qty, is_same_product, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 1, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "replace.product.wizard", "table_name": ""}
+{"text": "What does the res.users.apikeys.show model represent?", "response": "The res.users.apikeys.show model represents res.users.apikeys.show in the ERP system. It contains 4 fields and is used to manage res.users.apikeys.show data. Key fields include: key, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.users.apikeys.show", "table_name": ""}
+{"text": "What are the technical details of sale.summary.commission.report?", "response": "The sale.summary.commission.report model is defined in module: equip3_sale_team_commission. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.summary.commission.report", "table_name": ""}
+{"text": "What models are connected to field.conditional.access?", "response": "The field.conditional.access model has 6 relational fields: access_management_id -> access.management; model_id -> ir.model; attrs_field_id -> ir.model.fields; domain_field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "field.conditional.access", "table_name": ""}
+{"text": "What are the available fields for vendor.evaluation?", "response": "The vendor.evaluation model has 108 fields: name, state, vendor, period_start, period_end, manager, is_manager, user_id, price_check, price_factor, price, price_cmt, delivery_check, delivery_factor, delivery, delivery_cmt, quality_check, quality_factor, quality, quality_cmt, document_check, document_factor, document, document_cmt, commitment_check, commitment_factor, commitment, commitment_cmt, dependability_check, dependability_factor, dependability, dependability_cmt, skill_check, skill_factor, skill, skill_cmt, support_check, support_factor, support, support_cmt, relation_check, relation_factor, relation, relation_cmt, other_check, other_factor, other, other_cmt, final_point, final_rate, on_time_rate, on_time_rate_check, on_time_rate_factor, on_time_rate_star, on_time_rate_cmt, fulfillment, fulfillment_check, fulfillment_factor, fulfillment_star, fulfillment_cmt, fulfillment_avg, on_time_rate_avg, final_point_avg, vendor_evaluation_count, evaluation_template_id, evaluation_eval_ids, email, business, date, final_cmt, branch_id, company_id, on_time_rate_res, fulfillment_res, vendor_res, final_point_res, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 20, selection: 16, many2one: 12, date: 5, boolean: 18, integer: 18, float: 9, one2many: 5, many2many: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "vendor.evaluation", "table_name": ""}
+{"text": "What operations can I perform on purchase.request.line.make.purchase.order?", "response": "To use the purchase.request.line.make.purchase.order model, you need to provide values for required fields: supplier_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.request.line.make.purchase.order", "table_name": ""}
+{"text": "Tell me about the mailing.contact.subscription model.", "response": "The mailing.contact.subscription model represents Mass Mailing Subscription Information in the ERP system. It contains 13 fields and is used to manage mass mailing subscription information data. Key fields include: contact_id, list_id, opt_out, unsubscription_date, message_bounce, is_blacklisted, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mailing.contact.subscription", "table_name": ""}
+{"text": "Describe the account.move.reversal model in Odoo.", "response": "The account.move.reversal model represents Account Move Reversal in the ERP system. It contains 18 fields and is used to manage account move reversal data. Key fields include: move_ids, new_move_ids, date_mode, date, reason, refund_method, journal_id, company_id, residual, currency_id, move_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.move.reversal", "table_name": ""}
+{"text": "How does analytic.sale.order.line relate to other models?", "response": "The analytic.sale.order.line model has 9 relational fields: product_id -> product.product; product_uom -> uom.uom; analytic_tag_ids -> account.analytic.tag; tax_ids -> account.tax; subscription_product_line_id -> account.analytic.account; not_subscription_product_line_id -> account.analytic.account; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, tax_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "analytic.sale.order.line", "table_name": ""}
+{"text": "Show me the fields of pos.remote.session.", "response": "The pos.remote.session model has 10 fields: message, config_ids, action, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2many: 1, selection: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.remote.session", "table_name": ""}
+{"text": "What foreign keys exist in ks.sales.forecast.report?", "response": "The ks.sales.forecast.report model has 3 relational fields: binding_model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks.sales.forecast.report", "table_name": ""}
+{"text": "Show me the relational structure of ir.http.", "response": "The ir.http model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.http", "table_name": ""}
+{"text": "How do I use the report.equip3_accounting_reports.debt_collection model?", "response": "To use the report.equip3_accounting_reports.debt_collection model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.debt_collection", "table_name": ""}
+{"text": "How do I use the hide.filters.groups model?", "response": "To use the hide.filters.groups model, you need to provide values for required fields: model_id. Readonly fields: model_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "hide.filters.groups", "table_name": ""}
+{"text": "Describe the implementation of limit.request.", "response": "The limit.request model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "limit.request", "table_name": ""}
+{"text": "What are the relationships in dev.credit.note.wizard?", "response": "The dev.credit.note.wizard model has 8 relational fields: rma_id -> dev.rma.rma; product_line_ids -> credit.note.product.lines; sale_id -> sale.order; purchase_id -> purchase.order; purchase_ids -> purchase.order; sale_ids -> sale.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_ids, sale_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "dev.credit.note.wizard", "table_name": ""}
+{"text": "List all fields in the acrux.chat.message model.", "response": "The acrux.chat.message model has 23 fields: name, msgid, contact_id, connector_id, date_message, from_me, company_id, error_msg, user_id, ttype, event, template_id, is_direct, text, res_model, res_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 7, datetime: 4, boolean: 2, selection: 2, text: 1, integer: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "acrux.chat.message", "table_name": ""}
+{"text": "What are the technical details of sh.mrp.text?", "response": "The sh.mrp.text model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.mrp.text", "table_name": ""}
+{"text": "What business logic is in acrux.chat.default.answer?", "response": "To use the acrux.chat.default.answer model, you need to provide values for required fields: name, default_answer_type, ttype. Readonly fields: res_model, res_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "acrux.chat.default.answer", "table_name": ""}
+{"text": "What fields does dev.credit.note.wizard have?", "response": "The dev.credit.note.wizard model has 14 fields: rma_id, product_line_ids, picking_type_code, sale_id, purchase_id, purchase_ids, sale_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, one2many: 1, selection: 1, many2many: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "dev.credit.note.wizard", "table_name": ""}
+{"text": "List all fields in the sh.top.customers.xls model.", "response": "The sh.top.customers.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.top.customers.xls", "table_name": ""}
+{"text": "What operations can I perform on acrux.chat.connector?", "response": "To use the acrux.chat.connector model, you need to provide values for required fields: name, sequence, company_id, endpoint, apikey, uuid, border_color, sale_report_id, connector_type, qc_channel. Readonly fields: qc_webhook_url, connection_status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "acrux.chat.connector", "table_name": ""}
+{"text": "How does budget.purchase.lines relate to other models?", "response": "The budget.purchase.lines model has 12 relational fields: purchase_budget_id -> budget.purchase; analytic_account_id -> account.analytic.account; analytic_group_id -> account.analytic.group; product_budget -> account.budget.post; currency_id -> res.currency; company_id -> res.company; parent_analytic_account_id -> account.analytic.account; account_tag_ids -> account.analytic.tag; product_id -> product.product; purchase_order_line_budget_id -> purchase.order.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: account_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "budget.purchase.lines", "table_name": ""}
+{"text": "What foreign keys exist in report.sh_po_tender_management.report_analyze_quotations?", "response": "The report.sh_po_tender_management.report_analyze_quotations model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_po_tender_management.report_analyze_quotations", "table_name": ""}
+{"text": "How to create records in mail.alias.mixin?", "response": "To use the mail.alias.mixin model, you need to provide values for required fields: alias_id, alias_model_id, alias_defaults, alias_contact. Readonly fields: alias_id, id, display_name, __last_update, alias_name, alias_model_id, alias_user_id, alias_defaults, alias_force_thread_id, alias_domain, alias_parent_model_id, alias_parent_thread_id, alias_bounced_content, alias_contact, create_uid, create_date, write_uid, write_date. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.alias.mixin", "table_name": ""}
+{"text": "What fields does blanket.approval.matrix.lines have?", "response": "The blanket.approval.matrix.lines model has 20 fields: approval_matrix, user_name_ids, sequence, sequence2, order_id, minimum_approver, state_char, time_stamp, feedback, last_approved, approved, approved_users, approval_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, many2many: 2, integer: 4, text: 1, datetime: 4, char: 2, boolean: 1, selection: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "blanket.approval.matrix.lines", "table_name": ""}
+{"text": "What foreign keys exist in crm.phonecall2phonecall?", "response": "The crm.phonecall2phonecall model has 6 relational fields: user_id -> res.users; tag_ids -> crm.tag; team_id -> crm.team; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.phonecall2phonecall", "table_name": ""}
+{"text": "How does account.balance.report relate to other models?", "response": "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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.balance.report", "table_name": ""}
+{"text": "Describe the many2many relations for kpi.category.", "response": "The kpi.category model has 11 relational fields: parent_id -> kpi.category; child_ids -> kpi.category; company_id -> res.company; user_ids -> res.users; user_group_ids -> res.groups; access_user_ids -> res.users; edit_user_ids -> res.users; edit_user_group_ids -> res.groups; edit_access_user_ids -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, user_group_ids, access_user_ids, edit_user_ids, edit_user_group_ids, edit_access_user_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kpi.category", "table_name": ""}
+{"text": "Describe the implementation of account.bank.statement.import.", "response": "The account.bank.statement.import model is defined in module: om_account_bank_statement_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.bank.statement.import", "table_name": ""}
+{"text": "What are common use cases for approval.matrix.purchase.request?", "response": "To use the approval.matrix.purchase.request model, you need to provide values for required fields: name, company_id, branch_id, minimum_amt, maximum_amt. Readonly fields: company_id, is_purchase_request_department, is_good_services_order, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.purchase.request", "table_name": ""}
+{"text": "What does the purchase.request.allocation model represent?", "response": "The purchase.request.allocation model represents Purchase Request Allocation in the ERP system. It contains 17 fields and is used to manage purchase request allocation data. Key fields include: purchase_request_line_id, company_id, stock_move_id, purchase_line_id, product_id, product_uom_id, requested_product_uom_qty, allocated_product_qty, open_product_qty, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.request.allocation", "table_name": ""}
+{"text": "How is kpi.category implemented technically?", "response": "The kpi.category model is defined in module: kpi_scorecard. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kpi.category", "table_name": ""}
+{"text": "Which fields in sh.top.selling.products are computed?", "response": "The sh.top.selling.products model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.top.selling.products", "table_name": ""}
+{"text": "What modules define warranty.claim.stage?", "response": "The warranty.claim.stage model is defined in module: bi_warranty_registration. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "warranty.claim.stage", "table_name": ""}
+{"text": "List all fields in the repair.line model.", "response": "The repair.line model has 26 fields: name, repair_id, company_id, currency_id, type, product_id, invoiced, price_unit, price_subtotal, tax_id, product_uom_qty, product_uom, product_uom_category_id, invoice_line_id, location_id, location_dest_id, move_id, lot_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2one: 13, selection: 2, boolean: 1, float: 3, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "repair.line", "table_name": ""}
+{"text": "Show me the fields of pos.order.log.", "response": "The pos.order.log model has 45 fields: name, order_json, action, create_date, write_date, config_id, session_id, branch_id, company_id, 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, write_uid, __last_update. Field types distribution: char: 8, text: 2, datetime: 3, many2one: 12, one2many: 4, selection: 2, date: 2, boolean: 5, many2many: 2, integer: 5.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.order.log", "table_name": ""}
+{"text": "What fields does stock.location.route have?", "response": "The stock.location.route model has 22 fields: name, active, sequence, rule_ids, product_selectable, product_categ_selectable, warehouse_selectable, supplied_wh_id, supplier_wh_id, company_id, product_ids, categ_ids, warehouse_domain_ids, warehouse_ids, sale_selectable, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 5, integer: 2, one2many: 2, many2one: 5, many2many: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.location.route", "table_name": ""}
+{"text": "What are the available fields for replenishment.history.wizard?", "response": "The replenishment.history.wizard model has 8 fields: html_field, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: html: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "replenishment.history.wizard", "table_name": ""}
+{"text": "What are common use cases for assign.pr.line.wizard?", "response": "To use the assign.pr.line.wizard model, you need to provide values for required fields: none. Readonly fields: name, user_id, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assign.pr.line.wizard", "table_name": ""}
+{"text": "Describe the field structure of ai.chat.session.", "response": "The ai.chat.session model has 34 fields: name, user_id, config_id, state, session_summary, session_summary_message_count, session_summary_last_updated, auto_compress_enabled, compression_threshold, trim_ratio, message_count, last_activity, total_tokens_used, last_tokens_used, message_ids, job_ids, last_job_id, has_running_job, is_ai_renamed, is_quick_chat, quick_chat_model, quick_chat_res_id, cached_user_message_hash, cached_relevant_memories, cached_system_prompt, thinking_chain, last_frequent_actions_query, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 5, selection: 1, text: 5, integer: 7, datetime: 5, boolean: 4, float: 1, one2many: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ai.chat.session", "table_name": ""}
+{"text": "Which fields in report.dynamic_accounts_report.cash_flow are computed?", "response": "The report.dynamic_accounts_report.cash_flow model is defined in module: dynamic_accounts_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.dynamic_accounts_report.cash_flow", "table_name": ""}
+{"text": "How do I use the acrux.chat.pop.message model?", "response": "To use the acrux.chat.pop.message 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "acrux.chat.pop.message", "table_name": ""}
+{"text": "Show me the relational structure of account.bank.statement.line.", "response": "The account.bank.statement.line model has 133 relational fields: move_id -> account.move; statement_id -> account.bank.statement; foreign_currency_id -> res.currency; currency_id -> res.currency; partner_id -> res.partner; payment_ids -> account.payment; branch_id -> res.branch; pos_branch_id -> res.branch; voucher_id -> pos.voucher; pos_session_id -> pos.session; pos_statement_id -> pos.order; create_uid -> res.users; write_uid -> res.users; suitable_journal_ids -> account.journal; company_id -> res.company; user_id -> res.users; invoice_user_id -> res.users; preferred_payment_method_id -> account.payment.method; debit_origin_id -> account.move; debit_note_ids -> account.move; edi_document_ids -> account.edi.document; loan_line_id -> account.loan.line; loan_id -> account.loan; journal_bank_id -> account.journal; tax_payment_move_id -> account.move; asset_depreciation_ids -> account.asset.depreciation.line; transaction_ids -> payment.transaction; authorized_transaction_ids -> payment.transaction; purchase_vendor_bill_id -> purchase.bill.union; purchase_id -> purchase.order; sh_invoice_recurring_order_id -> invoice.recurring; period_id -> sh.account.period; fiscal_year -> sh.fiscal.year; stock_move_id -> stock.move; stock_valuation_layer_ids -> stock.valuation.layer; auto_reverse_journal_id -> account.journal; pos_order_ids -> pos.order; team_id -> crm.team; partner_shipping_id -> res.partner; consignment_pos_ids -> pos.order; l10n_id_attachment_id -> ir.attachment; landed_costs_ids -> stock.landed.cost; website_id -> website; discount_account_id -> account.account; warranty_reg_id -> product.warranty; related_project_id -> account.analytic.account; repair_ids -> repair.order; target_commission_id -> sh.target.commision; down_payment_purchase_id -> purchase.order; report_template_id1 -> ir.actions.report; report_template_id -> ir.actions.report; timesheet_ids -> account.analytic.line; approval_matrix_id -> approval.matrix.accounting; approved_matrix_ids -> approval.matrix.accounting.lines; approval_matrix_line_id -> approval.matrix.accounting.lines; analytic_group_ids -> account.analytic.tag; invoice_origin_id -> account.move; request_partner_id -> res.partner; journal_id -> account.journal; company_currency_id -> res.currency; line_ids -> account.move.line; commercial_partner_id -> res.partner; partner_bank_id -> res.partner.bank; payment_id -> account.payment; statement_line_id -> account.bank.statement.line; tax_cash_basis_rec_id -> account.partial.reconcile; tax_cash_basis_move_id -> account.move; reversed_entry_id -> account.move; reversal_move_id -> account.move; fiscal_position_id -> account.fiscal.position; invoice_payment_term_id -> account.payment.term; invoice_line_ids -> account.move.line; invoice_incoterm_id -> account.incoterms; invoice_vendor_bill_id -> account.move; invoice_cash_rounding_id -> account.cash.rounding; bank_partner_id -> res.partner; journal_entries_template -> account.move.template; analytic_tag_dynamic -> account.analytic.tag; approvers_ids -> res.users; approved_user_ids -> res.users; internal_tf_id -> account.internal.transfer; new_invoice_id -> account.move; account_asset_id -> account.asset.asset; customer_deposit_ids -> customer.deposit; vendor_deposit_ids -> vendor.deposit; nomor_seri -> account.efaktur; ebupot_id -> account.ebupot; nomor_seri_bupot -> account.ebupot; l10n_id_replace_invoice_id -> account.move; keterangan_tambahan -> account.keterangan.tambahan; signature_country_id -> res.country; signature_city_id -> res.country.city; currency_revaluation_id -> account.move; children_ids -> account.move; currency_revaluation_ref_id -> account.move; pettycash_id -> account.pettycash; sale_order_reference_id -> sale.order; filter_sale_order_reference_ids -> sale.order; exchange_id -> account.invoice.exchange; assembly_id -> assembly.production.record; stock_scrap_id -> stock.scrap.request; kitchen_id -> kitchen.production.record; purchase_order_id -> purchase.order; swo_ids -> service.work.order; finish_good_rework_id -> finish.good.rework; sale_order_ids -> sale.order; filter_sale_order_ids -> sale.order; purchase_order_ids -> purchase.order; filter_purchase_order_ids -> purchase.order; picking_ids -> stock.picking; filter_picking_ids -> stock.picking; cashback_line_ids -> cashback.line; so_cashback_id -> sale.order; return_picking_ids -> stock.picking; picking_id -> stock.picking; rma_id -> dev.rma.rma; account_invoice_ids -> account.invoice.exchange; pos_order_id -> pos.order; deposit_account_journal_id -> account.journal; create_from_session_id -> pos.session; inventory_id -> stock.inventory; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message. Many2many fields: payment_ids, suitable_journal_ids, transaction_ids, authorized_transaction_ids, analytic_group_ids, analytic_tag_dynamic, approvers_ids, approved_user_ids, customer_deposit_ids, vendor_deposit_ids, filter_sale_order_reference_ids, sale_order_ids, filter_sale_order_ids, purchase_order_ids, filter_purchase_order_ids, picking_ids, filter_picking_ids, return_picking_ids, account_invoice_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.bank.statement.line", "table_name": ""}
+{"text": "What are common use cases for ms.query?", "response": "To use the ms.query model, you need to provide values for required fields: name. Readonly fields: message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ms.query", "table_name": ""}
+{"text": "Show me the relational structure of stock.orderpoint.snooze.", "response": "The stock.orderpoint.snooze model has 3 relational fields: orderpoint_ids -> stock.warehouse.orderpoint; create_uid -> res.users; write_uid -> res.users. Many2many fields: orderpoint_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.orderpoint.snooze", "table_name": ""}
+{"text": "How do I use the generate.pos.voucher.wizard model?", "response": "To use the generate.pos.voucher.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "generate.pos.voucher.wizard", "table_name": ""}
+{"text": "How to create records in link.tracker.code?", "response": "To use the link.tracker.code model, you need to provide values for required fields: code, link_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "link.tracker.code", "table_name": ""}
+{"text": "How to query report.equip3_accounting_reports.journal_entry_report data?", "response": "To use the report.equip3_accounting_reports.journal_entry_report model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.journal_entry_report", "table_name": ""}
+{"text": "How to create records in crm.lead.product?", "response": "To use the crm.lead.product 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.lead.product", "table_name": ""}
+{"text": "What are the relationships in efaktur.export?", "response": "The efaktur.export model has 4 relational fields: partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "efaktur.export", "table_name": ""}
+{"text": "Describe the field structure of account.loan.generate.wizard.", "response": "The account.loan.generate.wizard model has 9 fields: date, loan_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, selection: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.loan.generate.wizard", "table_name": ""}
+{"text": "List all fields in the pos.profit.loss.wizard model.", "response": "The pos.profit.loss.wizard model has 10 fields: start_dt, end_dt, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.profit.loss.wizard", "table_name": ""}
+{"text": "How is sh.mrp.qc.alert used in the system?", "response": "The sh.mrp.qc.alert model represents MRP Quality Alert Wizard in the ERP system. It contains 11 fields and is used to manage mrp quality alert wizard data. Key fields include: team_id, user_id, sh_priority, alert_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.mrp.qc.alert", "table_name": ""}
+{"text": "What fields does crm.lead.lost have?", "response": "The crm.lead.lost model has 8 fields: lost_reason_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.lead.lost", "table_name": ""}
+{"text": "What models are connected to account.petty.cash.report?", "response": "The account.petty.cash.report model has 6 relational fields: custodian_id -> res.users; main_cash_account_id -> account.account; journal_id -> account.journal; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.petty.cash.report", "table_name": ""}
+{"text": "What modules define queue.jobs.to.done?", "response": "The queue.jobs.to.done model is defined in module: queue_job. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "queue.jobs.to.done", "table_name": ""}
+{"text": "How is salesperson.tracking.history implemented technically?", "response": "The salesperson.tracking.history model is defined in module: equip3_crm_tracking. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "salesperson.tracking.history", "table_name": ""}
+{"text": "Describe the many2many relations for mailing.mailing.", "response": "The mailing.mailing model has 24 relational fields: attachment_ids -> ir.attachment; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; user_id -> res.users; mailing_model_id -> ir.model; mail_server_id -> ir.mail_server; contact_list_ids -> mailing.list; mailing_trace_ids -> mailing.trace; rfm_segment_id -> setu.rfm.segment; model_object_field -> ir.model.fields; sub_object -> ir.model; sub_model_object_field -> ir.model.fields; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids, contact_list_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mailing.mailing", "table_name": ""}
+{"text": "Can you explain the purpose of sale.order.line?", "response": "The sale.order.line model represents Sales Order Line in the ERP system. It contains 161 fields and is used to manage sales order line data. Key fields include: order_id, sequence, invoice_lines, invoice_status, price_tax, price_reduce, price_reduce_taxinc, price_reduce_taxexcl, discount, product_updatable, product_uom_category_id, product_uom_readonly, product_custom_attribute_value_ids, product_no_variant_attribute_value_ids, qty_delivered, qty_delivered_manual, qty_to_invoice, qty_invoiced, untaxed_amount_invoiced, untaxed_amount_to_invoice, salesman_id, currency_id, order_partner_id, analytic_tag_ids, is_expense, is_downpayment, state, display_type, is_reward_line, sale_order_option_ids, is_configurable_product, product_template_attribute_value_ids, purchase_line_ids, purchase_line_count, product_packaging, route_id, move_ids, product_type, virtual_available_at_date, scheduled_date, forecast_expected_date, free_qty_today, qty_available_today, warehouse_id, qty_to_deliver, is_mto, display_qty_widget, name_short, linked_line_id, option_line_ids, is_apply_on_discount_amount, discount_type, discount_amt, is_delivery, product_qty, recompute_delivery_price, is_process_rma, margin, margin_percent, purchase_price, project_id, task_id, is_service, location_id, tick, warning_stock, qty_delivered_method, analytic_line_ids, remaining_hours_available, remaining_hours, discount_line, redeem_points, redeem_value, setting, is_single_warehouse, product_template_id_domain, customer_id, user_id, sequence_no, product_id, product_uom_qty, price_unit, customer_lead, company_id, name, last_sale_price, last_customer_sale_price, account_tag_ids, analytic_account_id, net_amount, location_dest_id, line_warehouse_id, line_warehouse_id_new, branch_id, delivery_address_id, multiple_do_date, multiple_do_date_new, multi_discount, discount_method, discount_amount, filter_delivery_address_id, hide_button_qa_sale, trigger, is_down_payment, product_template_id, product_uom, tax_id, res_product_uom, brand_ids, price_subtotal, price_total, tax_discount_policy, discounted_value, sale_line_sequence, reward_quantity, customer_voucher_id, bo_id, insert, parent_id, lot_id, pos_note, pos_branch_id, barcode, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.order.line", "table_name": ""}
+{"text": "What models are connected to account.tax.report?", "response": "The account.tax.report model has 7 relational fields: country_id -> res.country; line_ids -> account.tax.report.line; root_line_ids -> account.tax.report.line; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.tax.report", "table_name": ""}
+{"text": "Describe the many2many relations for ir.property.", "response": "The ir.property model has 4 relational fields: company_id -> res.company; fields_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.property", "table_name": ""}
+{"text": "What models are connected to purchase.report?", "response": "The purchase.report model has 16 relational fields: product_id -> product.product; partner_id -> res.partner; product_uom -> uom.uom; company_id -> res.company; currency_id -> res.currency; user_id -> res.users; category_id -> product.category; product_tmpl_id -> product.template; country_id -> res.country; fiscal_position_id -> account.fiscal.position; account_analytic_id -> account.analytic.account; commercial_partner_id -> res.partner; order_id -> purchase.order; team_id -> dev.purchase.team; picking_type_id -> stock.warehouse; branch_id -> res.branch. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.report", "table_name": ""}
+{"text": "What operations can I perform on mail.mail?", "response": "To use the mail.mail model, you need to provide values for required fields: mail_message_id, message_type. Readonly fields: references, state, failure_reason, fetchmail_server_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, description, needaction, has_error, starred, message_id, need_moderation, rating_value, has_sms_error, snailmail_error. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.mail", "table_name": ""}
+{"text": "What are common use cases for recurring.move.line?", "response": "To use the recurring.move.line model, you need to provide values for required fields: recurring_id, account_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "recurring.move.line", "table_name": ""}
+{"text": "How to create records in ir.actions.server?", "response": "To use the ir.actions.server model, you need to provide values for required fields: name, type, model_id, activity_user_type, usage, state, binding_type. Readonly fields: model_name, crud_model_name, mass_edit_apply_domain_in_lines, xml_id, website_url, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.actions.server", "table_name": ""}
+{"text": "What models are connected to report.equip3_pos_report.report_pos_payment?", "response": "The report.equip3_pos_report.report_pos_payment model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_pos_report.report_pos_payment", "table_name": ""}
+{"text": "How to query ir.actions.todo data?", "response": "To use the ir.actions.todo model, you need to provide values for required fields: action_id, state. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.actions.todo", "table_name": ""}
+{"text": "Describe the implementation of project.task.recurrence.", "response": "The project.task.recurrence model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "project.task.recurrence", "table_name": ""}
+{"text": "What methods are available in confirm.stock.sms?", "response": "The confirm.stock.sms model is defined in module: stock_sms. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "confirm.stock.sms", "table_name": ""}
+{"text": "How does stock.warehouse.orderpoint relate to other models?", "response": "The stock.warehouse.orderpoint model has 37 relational fields: product_tmpl_id -> product.template; product_id -> product.product; product_category_id -> product.category; product_uom -> uom.uom; group_id -> procurement.group; allowed_location_ids -> stock.location; rule_ids -> stock.rule; allowed_route_ids -> stock.location.route; route_id -> stock.location.route; bom_id -> mrp.bom; location_id -> stock.location; source_location_id -> stock.location; purchase_request_id -> purchase.request; purchase_order_id -> purchase.order; material_request_id -> material.request; internal_transfer_id -> internal.transfer; responsible_id -> res.users; branch_id -> res.branch; company_id -> res.company; warehouse_id -> stock.warehouse; filter_warehouse_id -> stock.location; notification_user_ids -> res.users; supplier_id -> res.partner; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: rule_ids, allowed_route_ids, responsible_id, filter_warehouse_id, notification_user_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.warehouse.orderpoint", "table_name": ""}
+{"text": "How do I use the ks.sales.forecast model?", "response": "To use the ks.sales.forecast model, you need to provide values for required fields: ks_start_date, ks_end_date, ks_forecast_unit, ks_forecast_period. Readonly fields: ks_name, ks_default_forecast_method, ks_model, ks_is_predicted_method, ks_resp, ks_resd, ks_resq, ks_sp, ks_sd, ks_sq, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks.sales.forecast", "table_name": ""}
+{"text": "Tell me about the export.efaktur model.", "response": "The export.efaktur model represents export.efaktur in the ERP system. It contains 12 fields and is used to manage export.efaktur data. Key fields include: partner_id, tax_report_id, date_from, date_to, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "export.efaktur", "table_name": ""}
+{"text": "What are the available fields for mail.render.mixin?", "response": "The mail.render.mixin model has 9 fields: lang, model_object_field, sub_object, sub_model_object_field, null_value, copyvalue, id, display_name, __last_update. Field types distribution: char: 4, many2one: 3, integer: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.render.mixin", "table_name": ""}
+{"text": "What operations can I perform on ir.cron?", "response": "To use the ir.cron model, you need to provide values for required fields: ir_actions_server_id, user_id, nextcall, name, type, model_id, activity_user_type, usage, state, binding_type. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update, model_name, crud_model_name, mass_edit_apply_domain_in_lines, xml_id, website_url. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.cron", "table_name": ""}
+{"text": "Which fields in account.fiscal.position.tax.template are computed?", "response": "The account.fiscal.position.tax.template model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.fiscal.position.tax.template", "table_name": ""}
+{"text": "What foreign keys exist in account.keterangan.tambahan?", "response": "The account.keterangan.tambahan model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.keterangan.tambahan", "table_name": ""}
+{"text": "How is itr.approval.matrix.line used in the system?", "response": "The itr.approval.matrix.line model represents Internal Approval Matrix Line in the ERP system. It contains 34 fields and is used to manage internal approval matrix line data. Key fields include: sequence, user_ids, minimum_approver, itr_approval_matrix, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, transfer_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "itr.approval.matrix.line", "table_name": ""}
+{"text": "Tell me about the gamification.karma.rank model.", "response": "The gamification.karma.rank model represents Rank based on karma in the ERP system. It contains 18 fields and is used to manage rank based on karma data. Key fields include: name, description, description_motivational, karma_min, user_ids, rank_users_count, image_1920, image_1024, image_512, image_256, image_128, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "gamification.karma.rank", "table_name": ""}
+{"text": "What methods are available in account.payment.method?", "response": "The account.payment.method model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.payment.method", "table_name": ""}
+{"text": "What modules define stock.return.move.line?", "response": "The stock.return.move.line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.return.move.line", "table_name": ""}
+{"text": "Can you explain the purpose of ir.actions.report?", "response": "The ir.actions.report model represents Report Action in the ERP system. It contains 30 fields and is used to manage report action data. Key fields include: name, type, binding_type, model, model_id, report_type, report_name, report_file, groups_id, multi, paperformat_id, print_report_name, attachment_use, attachment, encrypt, encrypt_type, manual_password, password_fields, password_sub_field, xml_id, help, binding_model_id, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.report", "table_name": ""}
+{"text": "How is sh.qc.team.type implemented technically?", "response": "The sh.qc.team.type model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.qc.team.type", "table_name": ""}
+{"text": "Show me the fields of report.equip3_pos_report.report_profit_loss.", "response": "The report.equip3_pos_report.report_profit_loss model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_pos_report.report_profit_loss", "table_name": ""}
+{"text": "Describe the field structure of account.move.reversal.", "response": "The account.move.reversal model has 18 fields: move_ids, new_move_ids, date_mode, date, reason, refund_method, journal_id, company_id, residual, currency_id, move_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, selection: 2, date: 1, char: 3, many2one: 5, monetary: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.move.reversal", "table_name": ""}
+{"text": "What are the technical details of replace.product.wizard?", "response": "The replace.product.wizard model is defined in module: dev_rma. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "replace.product.wizard", "table_name": ""}
+{"text": "What are common use cases for project.task.type?", "response": "To use the project.task.type model, you need to provide values for required fields: name, legend_blocked, legend_done, legend_normal. Readonly fields: disabled_rating_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.task.type", "table_name": ""}
+{"text": "What fields does pos.gift.card.type have?", "response": "The pos.gift.card.type model has 9 fields: name, code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.gift.card.type", "table_name": ""}
+{"text": "Describe the field structure of mailing.mailing.", "response": "The mailing.mailing model has 90 fields: active, subject, preview, email_from, sent_date, schedule_date, body_arch, body_html, attachment_ids, keep_archives, campaign_id, source_id, medium_id, state, color, user_id, mailing_type, reply_to_mode, reply_to, mailing_model_real, mailing_model_id, mailing_model_name, mailing_domain, mail_server_id, contact_list_ids, contact_ab_pc, unique_ab_testing, kpi_mail_required, mailing_trace_ids, total, scheduled, expected, ignored, sent, delivered, opened, clicked, replied, bounced, failed, received_ratio, opened_ratio, replied_ratio, bounced_ratio, clicks_ratio, next_departure, use_leads, crm_lead_count, sale_quotation_count, sale_invoiced_amount, rfm_segment_id, lang, model_object_field, sub_object, sub_model_object_field, null_value, copyvalue, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, name. Field types distribution: boolean: 10, char: 15, datetime: 6, html: 2, many2many: 4, many2one: 15, selection: 5, integer: 26, one2many: 5, date: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mailing.mailing", "table_name": ""}
+{"text": "What is the pos.cashier.change.wizard model?", "response": "The pos.cashier.change.wizard model represents POS Cashier Change Wizard in the ERP system. It contains 10 fields and is used to manage pos cashier change wizard data. Key fields include: start_datetime, end_datetime, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.cashier.change.wizard", "table_name": ""}
+{"text": "What are the relationships in base.module.uninstall?", "response": "The base.module.uninstall model has 5 relational fields: module_id -> ir.module.module; module_ids -> ir.module.module; model_ids -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: module_ids, model_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.module.uninstall", "table_name": ""}
+{"text": "What is the usage.type model?", "response": "The usage.type model represents Usage Type in the ERP system. It contains 48 fields and is used to manage usage type data. Key fields include: company_id, branch_id, name, account_id, filter_account_ids, usage_type, income_account_id, product_category_id, inv_val_account_id, filter_income_account_ids, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "usage.type", "table_name": ""}
+{"text": "What methods are available in kpi.item?", "response": "The kpi.item model is defined in module: kpi_scorecard. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kpi.item", "table_name": ""}
+{"text": "Describe the field structure of account.journal.group.", "response": "The account.journal.group model has 11 fields: name, company_id, excluded_journal_ids, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, many2many: 1, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.journal.group", "table_name": ""}
+{"text": "What are the technical details of report.equip3_pos_report.report_sales_summary?", "response": "The report.equip3_pos_report.report_sales_summary model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_pos_report.report_sales_summary", "table_name": ""}
+{"text": "Tell me about the account.move.template.line model.", "response": "The account.move.template.line model represents Journal Item Template in the ERP system. It contains 62 fields and is used to manage journal item template data. Key fields include: move_id, move_name, date, ref, parent_state, journal_id, company_id, company_currency_id, tax_fiscal_country_id, account_id, account_internal_type, account_internal_group, account_root_id, sequence, name, quantity, price_unit, discount, debit, credit, balance, cumulated_balance, amount_currency, price_subtotal, price_total, reconciled, blocked, date_maturity, currency_id, partner_id, product_uom_id, product_id, product_uom_category_id, reconcile_model_id, payment_id, statement_line_id, statement_id, tax_ids, tax_line_id, tax_group_id, tax_base_amount, tax_exigible, tax_repartition_line_id, tax_tag_ids, tax_audit, amount_residual, amount_residual_currency, full_reconcile_id, matching_number, analytic_account_id, analytic_tag_ids, recompute_tax_line, display_type, is_rounding_line, exclude_from_invoice_tab, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.move.template.line", "table_name": ""}
+{"text": "List all fields in the acrux.chat.default.answer model.", "response": "The acrux.chat.default.answer model has 17 fields: name, sequence, file_attach, file_attach_name, template_id, default_answer_type, text, ttype, res_model, res_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, integer: 3, binary: 1, many2one: 3, selection: 2, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "acrux.chat.default.answer", "table_name": ""}
+{"text": "Describe the many2many relations for account.pettycash.", "response": "The account.pettycash model has 24 relational fields: cash_journal -> account.journal; custodian -> res.users; main_cash_account_id -> account.account; journal -> account.journal; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; move_id -> account.move; voucher_id -> account.pettycash.voucher.wizard; paid_voucher_ids -> account.pettycash.voucher.wizard; custodian_partner -> res.partner; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.pettycash", "table_name": ""}
+{"text": "What methods are available in sh.account.period?", "response": "The sh.account.period model is defined in module: sh_sync_fiscal_year. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.account.period", "table_name": ""}
+{"text": "Can you explain the purpose of intrawarehouse.transfer?", "response": "The intrawarehouse.transfer model represents Intrawarehouse Transfer in the ERP system. It contains 8 fields and is used to manage intrawarehouse transfer data. Key fields include: interawarehouse_transfer_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "What business logic is in sh.top.vendor.excel.extended?", "response": "To use the sh.top.vendor.excel.extended 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.top.vendor.excel.extended", "table_name": ""}
+{"text": "Describe the partner.opening.balance model in Odoo.", "response": "The partner.opening.balance model represents partner.opening.balance in the ERP system. It contains 12 fields and is used to manage partner.opening.balance data. Key fields include: partner_id, account_receivable_id, account_payable_id, payable_opening_balance_ids, receivable_opening_balance_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "partner.opening.balance", "table_name": ""}
+{"text": "What foreign keys exist in ai.memory.export.import.wizard?", "response": "The ai.memory.export.import.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ai.memory.export.import.wizard", "table_name": ""}
+{"text": "How to create records in pos.voucher?", "response": "To use the pos.voucher model, you need to provide values for required fields: start_date, end_date. Readonly fields: user_id, pos_order_id, pos_order_line_id, use_history_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.voucher", "table_name": ""}
+{"text": "Describe the many2many relations for ks_ninja_dashboard.item_action.", "response": "The ks_ninja_dashboard.item_action model has 5 relational fields: ks_dashboard_item_ids -> ks_dashboard_ninja.item; ks_dashboard_ninja_id -> ks_dashboard_ninja.board; ks_dashboard_ninja_ids -> ks_dashboard_ninja.board; create_uid -> res.users; write_uid -> res.users. Many2many fields: ks_dashboard_item_ids, ks_dashboard_ninja_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks_ninja_dashboard.item_action", "table_name": ""}
+{"text": "What business logic is in payment.icon?", "response": "To use the payment.icon 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "payment.icon", "table_name": ""}
+{"text": "Which fields in sh.mrp.qc.alert are computed?", "response": "The sh.mrp.qc.alert model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.mrp.qc.alert", "table_name": ""}
+{"text": "What modules define kpi.period.value?", "response": "The kpi.period.value model is defined in module: kpi_scorecard. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kpi.period.value", "table_name": ""}
+{"text": "What is the purchase.agreement.legal.document model?", "response": "The purchase.agreement.legal.document model represents Purchase Agreement Legal Document in the ERP system. It contains 15 fields and is used to manage purchase agreement legal document data. Key fields include: legal_document_id, partner_id, nomor_induk_berusaha, salinan_anggaran_dasar, surat_persetujuan_dirjen_ahu, akta_perubahan_pengurus_terakhir, surat_keterangan_tidak_kena_pajak, surat_pernyataan_dan_kuasa, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.agreement.legal.document", "table_name": ""}
+{"text": "How is customer.degree.trust used in the system?", "response": "The customer.degree.trust model represents Customer Degree Trust in the ERP system. It contains 12 fields and is used to manage customer degree trust data. Key fields include: name, overdue_day, no_of_overdue_invoices, index, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "customer.degree.trust", "table_name": ""}
+{"text": "How does hr.employee.base relate to other models?", "response": "The hr.employee.base model has 12 relational fields: department_id -> hr.department; job_id -> hr.job; company_id -> res.company; address_id -> res.partner; user_id -> res.users; resource_id -> resource.resource; resource_calendar_id -> resource.calendar; parent_id -> hr.employee; coach_id -> hr.employee; goal_ids -> gamification.goal; badge_ids -> gamification.badge.user; direct_badge_ids -> gamification.badge.user. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hr.employee.base", "table_name": ""}
+{"text": "What are the relationships in sh.send.notification?", "response": "The sh.send.notification model has 4 relational fields: specific_ids -> sh.push.notification; log_historys -> sh.notification.logger; create_uid -> res.users; write_uid -> res.users. Many2many fields: specific_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.send.notification", "table_name": ""}
+{"text": "What foreign keys exist in create.purchase.request.direct?", "response": "The create.purchase.request.direct model has 6 relational fields: supplier_id -> res.partner; item_ids -> create.purchase.request.direct.lines; journal_id -> account.journal; purchase_order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "create.purchase.request.direct", "table_name": ""}
+{"text": "What methods are available in stock.scrap?", "response": "The stock.scrap model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.scrap", "table_name": ""}
+{"text": "How is account.voucher.line used in the system?", "response": "The account.voucher.line model represents Accounting Voucher Line in the ERP system. It contains 21 fields and is used to manage accounting voucher line data. Key fields include: name, sequence, voucher_id, product_id, uom_id, account_id, price_unit, price_subtotal, quantity, account_analytic_id, analytic_tag_ids, company_id, tax_ids, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.voucher.line", "table_name": ""}
+{"text": "What are common use cases for pos.combo.item?", "response": "To use the pos.combo.item model, you need to provide values for required fields: product_id, product_combo_id, quantity. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.combo.item", "table_name": ""}
+{"text": "What business logic is in restaurant.table?", "response": "To use the restaurant.table model, you need to provide values for required fields: name, shape. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "restaurant.table", "table_name": ""}
+{"text": "What models are connected to report.sh_purchase_reports.sh_po_product_indent_doc?", "response": "The report.sh_purchase_reports.sh_po_product_indent_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_po_product_indent_doc", "table_name": ""}
+{"text": "What are the available fields for ir.actions.todo?", "response": "The ir.actions.todo model has 11 fields: action_id, sequence, state, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 2, selection: 1, char: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.actions.todo", "table_name": ""}
+{"text": "How is snailmail.letter.format.error implemented technically?", "response": "The snailmail.letter.format.error model is defined in module: snailmail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "snailmail.letter.format.error", "table_name": ""}
+{"text": "What are the relationships in ks_ninja_dashboard.item_action?", "response": "The ks_ninja_dashboard.item_action model has 5 relational fields: ks_dashboard_item_ids -> ks_dashboard_ninja.item; ks_dashboard_ninja_id -> ks_dashboard_ninja.board; ks_dashboard_ninja_ids -> ks_dashboard_ninja.board; create_uid -> res.users; write_uid -> res.users. Many2many fields: ks_dashboard_item_ids, ks_dashboard_ninja_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks_ninja_dashboard.item_action", "table_name": ""}
+{"text": "Describe the implementation of purchase.quotation.excel.extended.", "response": "The purchase.quotation.excel.extended model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.quotation.excel.extended", "table_name": ""}
+{"text": "How do I use the generate.closing.entries model?", "response": "To use the generate.closing.entries model, you need to provide values for required fields: fiscal_year_id, closing_entry_date, journal_id, description, summary_account_id, retained_earnings_account_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "generate.closing.entries", "table_name": ""}
+{"text": "Can you explain the purpose of ir.qweb.field.float?", "response": "The ir.qweb.field.float model represents Qweb Field Float in the ERP system. It contains 3 fields and is used to manage qweb field float data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb.field.float", "table_name": ""}
+{"text": "How to query pos.bus.log data?", "response": "To use the pos.bus.log 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.bus.log", "table_name": ""}
+{"text": "How is pos.tag implemented technically?", "response": "The pos.tag model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.tag", "table_name": ""}
+{"text": "What business logic is in purchase.agreement.approval.matrix?", "response": "To use the purchase.agreement.approval.matrix model, you need to provide values for required fields: name, company_id, branch_id. Readonly fields: company_id, is_good_services_order, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.agreement.approval.matrix", "table_name": ""}
+{"text": "What methods are available in restaurant.floor?", "response": "The restaurant.floor model is defined in module: pos_restaurant. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "restaurant.floor", "table_name": ""}
+{"text": "What foreign keys exist in milestone.contract.template.line?", "response": "The milestone.contract.template.line model has 4 relational fields: template_id -> milestone.contract.template; checklist_template_id -> purchase.custom.checklist.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "milestone.contract.template.line", "table_name": ""}
+{"text": "What operations can I perform on choose.delivery.package?", "response": "To use the choose.delivery.package model, you need to provide values for required fields: none. Readonly fields: weight_uom_name, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "choose.delivery.package", "table_name": ""}
+{"text": "Which fields in wizard.product.bundle.bi are computed?", "response": "The wizard.product.bundle.bi model is defined in module: dynamic_product_bundle. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "wizard.product.bundle.bi", "table_name": ""}
+{"text": "Describe the stock.scrap.request.matrix.reject model in Odoo.", "response": "The stock.scrap.request.matrix.reject model represents Stock scrap Matrix Reject in the ERP system. It contains 8 fields and is used to manage stock scrap matrix reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.scrap.request.matrix.reject", "table_name": ""}
+{"text": "Which fields in sh.qc.team are computed?", "response": "The sh.qc.team model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.qc.team", "table_name": ""}
+{"text": "What business logic is in report.accounting_pdf_reports.report_general_ledger?", "response": "To use the report.accounting_pdf_reports.report_general_ledger model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.accounting_pdf_reports.report_general_ledger", "table_name": ""}
+{"text": "What data can be stored in asset.modify?", "response": "The asset.modify model has 12 fields: name, method_number, method_period, method_end, asset_method_time, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 3, date: 1, char: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "asset.modify", "table_name": ""}
+{"text": "What is the purchase.request.wizard.line model?", "response": "The purchase.request.wizard.line model represents purchase.request.wizard.line in the ERP system. It contains 17 fields and is used to manage purchase.request.wizard.line data. Key fields include: mr_id, no, product_id, description, uom_id, qty_purchase, request_date, mr_pr_wizard, mr_line_id, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.request.wizard.line", "table_name": ""}
+{"text": "What methods are available in budget.change.req.wizard?", "response": "The budget.change.req.wizard model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "budget.change.req.wizard", "table_name": ""}
+{"text": "What are the available fields for setu.inventory.xyz.analysis.bi.report?", "response": "The setu.inventory.xyz.analysis.bi.report model has 16 fields: product_id, product_category_id, company_id, current_stock, stock_value, stock_value_per, cum_stock_value_per, analysis_category, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, float: 4, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.xyz.analysis.bi.report", "table_name": ""}
+{"text": "How to query restaurant.floor data?", "response": "To use the restaurant.floor 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "restaurant.floor", "table_name": ""}
+{"text": "Tell me about the journal.entry.report model.", "response": "The journal.entry.report model represents journal.entry.report in the ERP system. It contains 15 fields and is used to manage journal.entry.report data. Key fields include: company_id, journal_ids, account_ids, display_account, target_move, date_from, date_to, move_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "journal.entry.report", "table_name": ""}
+{"text": "What modules define pos.category?", "response": "The pos.category model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.category", "table_name": ""}
+{"text": "What is the stock.day.average model?", "response": "The stock.day.average model represents Stock Day Average in the ERP system. It contains 45 fields and is used to manage stock day average data. Key fields include: name, product_id, action_type, branch_id, company_id, users_ids, start_date, end_date, periode, cluster_id, is_itr_created, transfer_count, warehouse_line, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.day.average", "table_name": ""}
+{"text": "What fields does assembly.safety.stock.line have?", "response": "The assembly.safety.stock.line model has 10 fields: stock_id, product_id, product_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "assembly.safety.stock.line", "table_name": ""}
+{"text": "How is report.equip3_accounting_reports.debt_collection implemented technically?", "response": "The report.equip3_accounting_reports.debt_collection model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_accounting_reports.debt_collection", "table_name": ""}
+{"text": "What modules define digest.tip?", "response": "The digest.tip model is defined in module: digest. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "digest.tip", "table_name": ""}
+{"text": "What data can be stored in lost.customer?", "response": "The lost.customer model has 9 fields: name, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "lost.customer", "table_name": ""}
+{"text": "List all fields in the website.published.mixin model.", "response": "The website.published.mixin model has 7 fields: website_published, is_published, can_publish, website_url, id, display_name, __last_update. Field types distribution: boolean: 3, char: 2, integer: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "website.published.mixin", "table_name": ""}
+{"text": "What operations can I perform on project.tags?", "response": "To use the project.tags 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.tags", "table_name": ""}
+{"text": "Show me the relational structure of account.invoice.exchange.approval.wizard.", "response": "The account.invoice.exchange.approval.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.invoice.exchange.approval.wizard", "table_name": ""}
+{"text": "Show me the relational structure of ks.message.wizard.", "response": "The ks.message.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks.message.wizard", "table_name": ""}
+{"text": "How is gamification.karma.tracking used in the system?", "response": "The gamification.karma.tracking model represents Track Karma Changes in the ERP system. It contains 12 fields and is used to manage track karma changes data. Key fields include: user_id, old_value, new_value, consolidated, tracking_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "gamification.karma.tracking", "table_name": ""}
+{"text": "Describe the implementation of account.tax.map.purchase.line.", "response": "The account.tax.map.purchase.line model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.tax.map.purchase.line", "table_name": ""}
+{"text": "Tell me about the assign.pr.wizard model.", "response": "The assign.pr.wizard model represents Assign PR Wizard in the ERP system. It contains 9 fields and is used to manage assign pr wizard data. Key fields include: pr_ids, line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assign.pr.wizard", "table_name": ""}
+{"text": "How does account.pettycash.voucher.wizard relate to other models?", "response": "The account.pettycash.voucher.wizard model has 10 relational fields: fund -> account.pettycash; partner_id -> res.users; ba_ca_journal_id -> account.journal; submitter_id -> res.users; currency_id -> res.currency; company_id -> res.company; voucher_line -> account.pettycash.voucher.wizard.line; move_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.pettycash.voucher.wizard", "table_name": ""}
+{"text": "What fields does account.common.journal.report have?", "response": "The account.common.journal.report model has 14 fields: amount_currency, 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 types distribution: boolean: 1, many2many: 1, date: 2, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.common.journal.report", "table_name": ""}
+{"text": "How to query purchase.detail.excel.extended data?", "response": "To use the purchase.detail.excel.extended 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.detail.excel.extended", "table_name": ""}
+{"text": "What data can be stored in account.journal.group?", "response": "The account.journal.group model has 11 fields: name, company_id, excluded_journal_ids, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, many2many: 1, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.journal.group", "table_name": ""}
+{"text": "Show me the relational structure of report.equip3_accounting_reports.debt_collection.", "response": "The report.equip3_accounting_reports.debt_collection model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.debt_collection", "table_name": ""}
+{"text": "How is mrp.workcenter.group used in the system?", "response": "The mrp.workcenter.group model represents Work Center Group in the ERP system. It contains 28 fields and is used to manage work center group data. Key fields include: code, name, company_id, branch_id, workcenter_ids, is_branch_required, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.workcenter.group", "table_name": ""}
+{"text": "Show me the fields of efaktur.export.", "response": "The efaktur.export model has 13 fields: partner_id, tax_report_id, date_from, date_to, company_id, unduh, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, selection: 1, date: 2, binary: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "efaktur.export", "table_name": ""}
+{"text": "Tell me about the product.template.attribute.value model.", "response": "The product.template.attribute.value model represents Product Template Attribute Value in the ERP system. It contains 20 fields and is used to manage product template attribute value data. Key fields include: ptav_active, name, product_attribute_value_id, attribute_line_id, price_extra, currency_id, exclude_for, product_tmpl_id, attribute_id, ptav_product_variant_ids, html_color, is_custom, display_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.template.attribute.value", "table_name": ""}
+{"text": "What foreign keys exist in account.reconcile.model.line?", "response": "The account.reconcile.model.line model has 9 relational fields: model_id -> account.reconcile.model; company_id -> res.company; account_id -> account.account; journal_id -> account.journal; tax_ids -> account.tax; analytic_account_id -> account.analytic.account; analytic_tag_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_ids, analytic_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.reconcile.model.line", "table_name": ""}
+{"text": "Show me the relational structure of res.partner.type.", "response": "The res.partner.type model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.partner.type", "table_name": ""}
+{"text": "What foreign keys exist in mrp.production?", "response": "The mrp.production model has 43 relational fields: product_id -> product.product; allowed_product_ids -> product.product; product_tmpl_id -> product.template; product_uom_id -> uom.uom; lot_producing_id -> stock.production.lot; product_uom_category_id -> uom.category; picking_type_id -> stock.picking.type; location_src_id -> stock.location; location_dest_id -> stock.location; bom_id -> mrp.bom; move_raw_ids -> stock.move; move_finished_ids -> stock.move; move_byproduct_ids -> stock.move; finished_move_line_ids -> stock.move.line; workorder_ids -> mrp.workorder; move_dest_ids -> stock.move; user_id -> res.users; company_id -> res.company; procurement_group_id -> procurement.group; orderpoint_id -> stock.warehouse.orderpoint; scrap_ids -> stock.scrap; production_location_id -> stock.location; picking_ids -> stock.picking; sh_mrp_quality_check_ids -> sh.mrp.quality.check; sh_mrp_quality_alert_ids -> sh.mrp.quality.alert; sh_mrp_pass_fail_ids -> sh.mrp.pass.fail; sh_mrp_pics_ids -> sh.mrp.pics; sh_mrp_measurement_ids -> sh.mrp.measurement; sh_mrp_qc_measurement_ids -> sh.mrp.qc.measurement; attachment_ids -> ir.attachment; sh_mrp_quality_point_id -> sh.qc.point; partner_id -> res.partner; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: allowed_product_ids, picking_ids, attachment_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.production", "table_name": ""}
+{"text": "What operations can I perform on pos.promotion.gift.condition?", "response": "To use the pos.promotion.gift.condition model, you need to provide values for required fields: product_id, minimum_quantity, promotion_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion.gift.condition", "table_name": ""}
+{"text": "What business logic is in mail.thread.phone?", "response": "To use the mail.thread.phone model, you need to provide values for required fields: none. Readonly fields: phone_sanitized, phone_sanitized_blacklisted, phone_blacklisted, mobile_blacklisted, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.thread.phone", "table_name": ""}
+{"text": "What methods are available in mail.followers?", "response": "The mail.followers model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.followers", "table_name": ""}
+{"text": "Which fields in ir.ui.menu.category are computed?", "response": "The ir.ui.menu.category model is defined in module: equip3_hashmicro_ui. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.ui.menu.category", "table_name": ""}
+{"text": "Describe the field structure of approval.matrix.direct.purchase.", "response": "The approval.matrix.direct.purchase model has 46 fields: name, company_id, branch_id, minimum_amt, maximum_amt, approval_matrix_direct_purchase_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. Field types distribution: char: 7, many2one: 10, float: 2, one2many: 5, boolean: 6, selection: 3, date: 2, many2many: 2, integer: 5, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.direct.purchase", "table_name": ""}
+{"text": "How is return.reason used in the system?", "response": "The return.reason model represents Return Reason in the ERP system. It contains 8 fields and is used to manage return reason data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "return.reason", "table_name": ""}
+{"text": "How is pos.loyalty.category implemented technically?", "response": "The pos.loyalty.category model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.loyalty.category", "table_name": ""}
+{"text": "What foreign keys exist in uom.conversion.history?", "response": "The uom.conversion.history model has 10 relational fields: product_id -> product.product; location_id -> stock.location; prod_lot_id -> stock.production.lot; package_id -> stock.quant.package; partner_id -> res.partner; uom_id -> uom.uom; uom_conversion -> uom.uom; si_uom_id -> stock.inventory; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "uom.conversion.history", "table_name": ""}
+{"text": "What is the service.work.order.checklist model?", "response": "The service.work.order.checklist model represents Service Work Order Checklist in the ERP system. It contains 12 fields and is used to manage service work order checklist data. Key fields include: swo_id, name, desc, state, state2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "service.work.order.checklist", "table_name": ""}
+{"text": "What are common use cases for base_import.tests.models.m2o.required.related?", "response": "To use the base_import.tests.models.m2o.required.related 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base_import.tests.models.m2o.required.related", "table_name": ""}
+{"text": "Describe the many2many relations for generate.closing.entries.", "response": "The generate.closing.entries model has 6 relational fields: fiscal_year_id -> sh.fiscal.year; journal_id -> account.journal; summary_account_id -> account.account; retained_earnings_account_id -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "generate.closing.entries", "table_name": ""}
+{"text": "What methods are available in product.template.attribute.line?", "response": "The product.template.attribute.line model is defined in module: product. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.template.attribute.line", "table_name": ""}
+{"text": "Describe the field structure of account.common.journal.report.", "response": "The account.common.journal.report model has 14 fields: amount_currency, 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 types distribution: boolean: 1, many2many: 1, date: 2, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.common.journal.report", "table_name": ""}
+{"text": "Show me the fields of split.pr.line.wizard.", "response": "The split.pr.line.wizard model has 14 fields: wizard_id, pr_line_id, name, user_id, new_user_id, product_id, product_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, char: 2, float: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "split.pr.line.wizard", "table_name": ""}
+{"text": "What are the technical details of untaken.stock?", "response": "The untaken.stock model is defined in module: equip3_inventory_control. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "untaken.stock", "table_name": ""}
+{"text": "What does the product.brand model represent?", "response": "The product.brand model represents Product Brand in the ERP system. It contains 42 fields and is used to manage product brand data. Key fields include: brand_name, short_name, product_count, active, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.brand", "table_name": ""}
+{"text": "How is sh.commision.detail implemented technically?", "response": "The sh.commision.detail model is defined in module: sh_sales_commission_target. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.commision.detail", "table_name": ""}
+{"text": "Show me the relational structure of mail.thread.phone.", "response": "The mail.thread.phone model has 6 relational fields: message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.thread.phone", "table_name": ""}
+{"text": "What methods are available in monthly.account.budget?", "response": "The monthly.account.budget model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "monthly.account.budget", "table_name": ""}
+{"text": "How do I use the product.supplierinfo model?", "response": "To use the product.supplierinfo model, you need to provide values for required fields: name, min_qty, price, currency_id, product_tmpl_id, delay. Readonly fields: access_url, access_warning, product_uom, product_uom_category_id, product_variant_count, state1, state2, vendor_pricelist_approval_matrix, current_user, is_vendor_pricelist_approval_matrix, approval_matrix_line_id, is_approve_button, product_uom_old, edit_button_state, last_price, last_update_price, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.supplierinfo", "table_name": ""}
+{"text": "Describe the budget.purchase.wizard model in Odoo.", "response": "The budget.purchase.wizard model represents Purchase Change Request Wizard in the ERP system. It contains 8 fields and is used to manage purchase change request wizard data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "budget.purchase.wizard", "table_name": ""}
+{"text": "Describe the implementation of credit.limit.approval.", "response": "The credit.limit.approval model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "credit.limit.approval", "table_name": ""}
+{"text": "What are the available fields for purchase.excel.extended?", "response": "The purchase.excel.extended model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.excel.extended", "table_name": ""}
+{"text": "Show me the fields of pos.config.", "response": "The pos.config model has 493 fields: name, is_installed_account_accountant, journal_id, invoice_journal_id, currency_id, iface_cashdrawer, iface_electronic_scale, iface_vkeyboard, iface_customer_facing_display, iface_print_via_proxy, iface_scan_via_proxy, iface_big_scrollbars, iface_print_auto, iface_print_skip_screen, iface_tax_included, iface_start_categ_id, selectable_categ_ids, iface_display_categ_images, restrict_price_control, cash_control, receipt_header, receipt_footer, proxy_ip, active, uuid, sequence_id, sequence_line_id, session_ids, current_session_id, current_session_state, last_session_closing_cash, last_session_closing_date, last_session_closing_cashbox, pos_session_username, pos_session_state, pos_session_duration, pricelist_id, available_pricelist_ids, allowed_pricelist_ids, company_id, barcode_nomenclature_id, iface_tipproduct, tip_product_id, fiscal_position_ids, default_fiscal_position_id, default_cashbox_id, use_pricelist, tax_regime, tax_regime_selection, start_category, module_account, module_pos_discount, module_pos_loyalty, module_pos_mercury, manage_orders, product_configurator, is_posbox, is_header_or_footer, module_pos_hr, amount_authorized_diff, payment_method_ids, company_has_template, current_user_id, other_devices, rounding_method, cash_rounding, only_round_cash_method, has_active_session, show_allow_invoicing_alert, manual_discount, iface_discount, discount_pc, discount_product_id, epson_printer_ip, employee_ids, iface_splitbill, iface_printbill, iface_orderline_notes, floor_ids, printer_ids, is_table_management, is_order_printer, set_tip_after_payment, module_pos_restaurant, crm_team_id, group_pos_manager_id, group_pos_user_id, pos_receipt_template_id, order_loading_options, number_of_days, weight_scale_barcode_format_id, bnk_cash_control, restaurant_order, restaurant_order_login, restaurant_order_password, pos_config_cashbox_lines_ids, pos_config_cashbox_clsosing_line_ids, cashbox_lines_ids, pos_cashbox_lines_ids, printer_id, load_coupon_program, coupon_program_apply_type, coupon_program_ids, coupon_giftcard_ids, coupon_giftcard_create, user_id, allow_change_pos_profile, allow_numpad, allow_discount, allow_qty, allow_price, allow_remove_line, allow_minus, allow_payment, allow_customer, allow_add_order, allow_remove_order, allow_add_product, allow_payment_zero, allow_closing_session, allow_closing_all_sessions_online, allow_duplicate_session, allow_otp, twilio_acc_sid, twilio_auth_token, pos_otp_reset_time, pos_otp_msg, tax_affect_compliment, sale_order, sale_order_auto_confirm, sale_order_auto_invoice, sale_order_auto_delivery, sale_order_required_signature, pos_orders_management, pos_order_tracking, pos_order_tracking_remove_when_closing_session, shipping_order, pos_orders_load_orders_another_pos, pos_orders_filter_by_branch, pos_order_period_return_days, pos_allowed_return_category_ids, required_reason_return, display_return_days_receipt, display_onhand, allow_order_out_of_stock, allow_pos_categories_out_of_stock, hide_product_when_outof_stock, print_voucher, voucher_sequence_id, expired_days_voucher, sync_multi_session, sync_play_sound, sync_multi_session_with, sync_multi_session_manual_stop, sync_multi_session_alert_remove_order, sync_multi_session_offline, sync_to_pos_config_ids, sync_tracking_activities_user, display_person_add_line, internal_transfer, internal_transfer_picking_type_id, discount, discount_ids, delay, discount_limit, discount_limit_type, discount_limit_amount, return_products, return_method_id, return_covert_to_coupon, return_coupon_program_id, return_duplicate, return_viva_scan_barcode, validate_payment, validate_remove_order, validate_new_order, validate_change_minus, validate_quantity_change, validate_quantity_change_type, validate_price_change, validate_price_change_type, validate_discount_change, validate_discount_change_type, validate_remove_line, validate_return, validate_coupon, product_operation, note_order, signature_order, booking_orders, load_booked_orders_type, booking_orders_load_orders_another_pos, booking_orders_alert, booking_allow_confirm_sale, booking_orders_display_shipping_receipt, display_tax_orderline, display_tax_receipt, display_image_orderline, display_amount_discount, display_barcode, quickly_look_up_product, management_invoice, load_invoices_type, invoice_offline, wallet, payment_journal_ids, send_invoice_email, customer_default_id, auto_invoice, auto_invoice_with_customer_default, invoice_without_download, fiscal_position_auto_detect, display_sale_price_within_tax, display_cost_price, display_product_ref, display_product_detail, allow_remove_product, allow_edit_product, display_product_name_without_product_code, product_virtual_keyboard, hide_product_image, multi_location, update_stock_onhand, multi_stock_operation_type, multi_stock_operation_type_ids, product_view, update_tax, update_tax_ids, check_duplicate_email, check_duplicate_phone, check_required_phone, check_required_email, check_required_vat, add_sale_person, default_seller_id, seller_ids, force_seller, backup_orders, backup_orders_automatic, save_orders_removed, management_session, default_set_cash_open, default_set_cash_amount, default_set_cash_notes, cash_inout_reason_ids, barcode_receipt, qrcode_receipt, qrcode_ids, receipt_template, hide_mobile, hide_phone, hide_email, update_client, add_client, archive_client, remove_client, report_signature, report_product_summary, report_product_summary_auto_check_product, report_product_summary_auto_check_category, report_product_summary_auto_check_location, report_product_summary_auto_check_payment, report_order_summary, report_order_summary_auto_check_order, report_order_summary_auto_check_category, report_order_summary_auto_check_payment, report_order_summary_default_state, report_payment_summary, report_sale_summary, report_sale_summary_show_profit, default_product_sort_by, hide_order_screen, add_customer_before_products_already_in_shopping_cart, allow_cashier_select_pricelist, sale_with_package, allow_set_price_smaller_min_price, create_lots, fullfill_lots_type, fullfill_lots, stock_location_ids, validate_by_manager, discount_unlock_by_manager, assigned_user_ids, manager_ids, stock_location_id, stock_location_dest_id, discount_value, discount_value_limit, discount_global_id, posbox_save_orders, posbox_save_orders_server_ip, posbox_save_orders_server_port, analytic_account_id, limit_categories, iface_available_categ_ids, barcode_scan_timeout, rounding_automatic, rounding_type, service_charge_ids, service_charge_type, service_shipping_automatic, google_map_api_key, payment_reference, display_margin, start_session_oneclick, translate_products_name, set_product_name_from_field, replace_partners_name, set_partner_name_from_field, create_quotation, assign_orders_to_config_ids, product_generic_option, mrp, last_save_cache, category_ancestors, point_of_sale_update_stock_quantities, multi_session, display_filter_product_categories, product_category_ids, sessions_opened, search_query_only_start_when_enter, create_category_direct, create_product_direct, customer_facing_screen, customer_facing_screen_width, customer_facing_screen_height, rounding, rounding_factor, decimal_places, font_family, price_tag_color, header_background_color, cart_box_style, buttons_box_style, background, product_screen_background, cart_background, payment_screen_background, numpad_background, product_categories_height, product_width, product_height, product_margin, product_image_width, product_image_height, product_name_font_size, display_mobile_mode, display_mobile_screen_size, display_product_image, cart_width, whatsapp_api, whatsapp_token, whatsapp_send_type, whatsapp_message_receipt, checkin_screen, hidden_product_ids, warning_closing_session, warning_odoo_offline, pos_title, sync_partners_realtime, cache, local_network_printer, local_network_printer_ip_address, local_network_printer_port, product_recommendation, product_recommendation_number, show_session_information, tip_percent, tip_percent_max, categ_dislay_type, custom_sale, custom_sale_product_id, multi_currency, multi_currency_ids, allowed_employee_ids, fire_appetizer, fire_main_course, fire_dessert, enable_fire_appetizer, enable_fire_main_course, enable_fire_dessert, enable_seat_time, seat_time, show_product_template, available_product_domain, promotion_manual_select, promotion_auto_add, promotion_ids, is_manual_sync_for_sync_between_session, is_manual_sync_masterdata, is_manual_sync_member, is_auto_sync_product_stock, is_auto_sync_product_price, is_auto_sync_product, is_auto_sync_pricelist, is_auto_sync_promotion, is_auto_sync_coupon, is_monitor_auto_sync, is_force_sync_promotion, is_force_sync_pricelist, filter_load_pos_order, zone_id, product_voucher_service_id, product_coupon_service_id, display_table, display_all_product, product_categ_ids, product_categ_display_names, set_lines_to_done, order_receipt_tickets, qr_orders, login_title, login_required, login_create_partner, qrcode_order_screen, qrcode_order_auto_alert, customer_facing_display_html, user_ids, sync_manual_button, period_minutes_warning, enable_void_time, void_time, void_order_pin_ids, void_order_pins, void_order_line_pin_ids, void_order_line_pins, advertisement_image_ids, marquee_type, marquee_text, marque_color, marque_bg_color, marque_font_size, mute_video_sound, ac_width, ac_height, ac_qrcod, ac_qr_link, warehouse_id, is_order_rounding, order_rounding_type, picking_type_id, pos_branch_id, pos_branch_name, branch_telephone, branch_address, branch_street, branch_street_2, enable_gift_card, gift_card_account_id, gift_card_product_id, gift_payment_method_id, manual_card_number, msg_before_card_pay, is_difference_value_opening_control_validation, is_cash_management_with_validation, cashbox_payment_method_id, pos_cashbox_product_services, cashbox_line_amount, screen_type, is_allow_product_exchange, product_exchange_pin_ids, product_exchange_line_pins, is_save_order_history_local, save_order_history_local_days, is_save_order_to_pos_cache_service, link_pos_cache_service, select_shortcut, enable_shortcuts, display_point_receipt, pos_loyalty_id, pos_loyalty_ids, loyalty_combine_promotion, loyalty_redeem_in_pos_screen, is_allow_redeem_in_pos_screen, is_allow_create_member_in_pos_screen, customer_deposit_account_id, customer_deposit_reconcile_journal_id, order_summery, product_summery, product_categ_summery, loc_summery, payment_summery, pos_code, is_hide_pos_order_button, analytic_group_ids, is_pos_load_data_from_pos_cache_sdk, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 48, boolean: 267, many2one: 51, selection: 29, many2many: 39, text: 12, one2many: 7, float: 16, date: 1, integer: 19, html: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.config", "table_name": ""}
+{"text": "Describe the many2many relations for cancel.tender.memory.", "response": "The cancel.tender.memory model has 3 relational fields: tender_id -> purchase.agreement; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "cancel.tender.memory", "table_name": ""}
+{"text": "What methods are available in purchase.request?", "response": "The purchase.request model is defined in module: purchase_request. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.request", "table_name": ""}
+{"text": "Can you explain the purpose of report.sh_sale_reports.sh_payment_report_doc?", "response": "The report.sh_sale_reports.sh_payment_report_doc model represents payment report abstract model in the ERP system. It contains 3 fields and is used to manage payment report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_sale_reports.sh_payment_report_doc", "table_name": ""}
+{"text": "What are the available fields for res.users.identitycheck?", "response": "The res.users.identitycheck model has 8 fields: password, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.users.identitycheck", "table_name": ""}
+{"text": "How do I use the approval.matrix.vendor.line model?", "response": "To use the approval.matrix.vendor.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: company_id, branch_id, sequence2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.vendor.line", "table_name": ""}
+{"text": "How does approval.matrix.accounting relate to other models?", "response": "The approval.matrix.accounting model has 18 relational fields: company_id -> res.company; branch_id -> res.branch; filter_branch_ids -> res.branch; approval_matrix_line_ids -> approval.matrix.accounting.lines; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_branch_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.accounting", "table_name": ""}
+{"text": "What are common use cases for efaktur.export?", "response": "To use the efaktur.export model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "efaktur.export", "table_name": ""}
+{"text": "How is ir.qweb.field.image used in the system?", "response": "The ir.qweb.field.image model represents Qweb Field Image in the ERP system. It contains 3 fields and is used to manage qweb field image data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb.field.image", "table_name": ""}
+{"text": "List all fields in the base.import.module model.", "response": "The base.import.module model has 11 fields: module_file, state, import_message, force, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, selection: 1, text: 1, boolean: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.import.module", "table_name": ""}
+{"text": "Show me the relational structure of coupon.coupon.", "response": "The coupon.coupon model has 14 relational fields: partner_id -> res.partner; program_id -> coupon.program; discount_line_product_id -> product.product; order_id -> sale.order; sales_order_id -> sale.order; pos_order_id -> pos.order; redeem_history_ids -> pos.order.line; pos_create_uid -> res.users; pos_config_id -> pos.config; pos_orderline_id -> pos.order.line; purchase_id -> purchase.order; purchases_order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "coupon.coupon", "table_name": ""}
+{"text": "Describe the field structure of purchase.detail.excel.extended.", "response": "The purchase.detail.excel.extended model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.detail.excel.extended", "table_name": ""}
+{"text": "Show me the fields of sh.tv.top.vendor.wizard.", "response": "The sh.tv.top.vendor.wizard model has 17 fields: type, date_from, date_to, date_compare_from, date_compare_to, no_of_top_item, amount_total, currency_id, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, datetime: 7, integer: 2, monetary: 1, many2one: 3, many2many: 2, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.tv.top.vendor.wizard", "table_name": ""}
+{"text": "What does the mr.internal_transfer_line model represent?", "response": "The mr.internal_transfer_line model represents mr.internal_transfer_line in the ERP system. It contains 22 fields and is used to manage mr.internal_transfer_line data. Key fields include: mr_id, no, product_id, description, uom_id, source_location, source_warehouse_id, current_qty, virtual_available, qty_transfer, mr_ir_wizard, mr_line_id, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mr.internal_transfer_line", "table_name": ""}
+{"text": "Show me the fields of budget.carry.over.lines.", "response": "The budget.carry.over.lines model has 27 fields: budget_carry_over_id, date_from, date_to, analytic_account_id, paid_date, parent_analytic_account_id, general_budget_id, reserve_amount, currency_id, account_tag_ids, filtered_budget_line, company_id, practical_amount, theoritical_amount, planned_amount, practical_budget_amount, percentage, is_above_budget, carry_over_amount, final_planned_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, date: 3, monetary: 7, many2many: 2, float: 1, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "budget.carry.over.lines", "table_name": ""}
+{"text": "Show me the relational structure of account.deposit.reconcile.", "response": "The account.deposit.reconcile model has 3 relational fields: allocation_line_ids -> invoice.deposit.line.reconcile; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.deposit.reconcile", "table_name": ""}
+{"text": "What business logic is in inter.transfer.company?", "response": "To use the inter.transfer.company model, you need to provide values for required fields: none. Readonly fields: sale_count, invoice_count, bill_count, purchase_count, return_count, name, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "inter.transfer.company", "table_name": ""}
+{"text": "What models are connected to purchase.report.representative.xls?", "response": "The purchase.report.representative.xls model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.report.representative.xls", "table_name": ""}
+{"text": "What does the asset.asset.report model represent?", "response": "The asset.asset.report model represents Assets Analysis in the ERP system. It contains 21 fields and is used to manage assets analysis data. Key fields include: name, date, depreciation_date, asset_id, asset_category_id, partner_id, state, installment_value, move_check, installment_nbr, depreciation_nbr, gross_value, posted_value, unposted_value, company_id, depreciation_value, salvage_value, value_residual, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "asset.asset.report", "table_name": ""}
+{"text": "How do I use the debt.collection.report model?", "response": "To use the debt.collection.report model, you need to provide values for required fields: journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "debt.collection.report", "table_name": ""}
+{"text": "What operations can I perform on stock.track.line?", "response": "To use the stock.track.line model, you need to provide values for required fields: none. Readonly fields: product_id, tracking, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.track.line", "table_name": ""}
+{"text": "Can you explain the purpose of stock.return.move.line?", "response": "The stock.return.move.line model represents Stock Return Move Line in the ERP system. It contains 12 fields and is used to manage stock return move line data. Key fields include: product_id, return_id, lot_id, qty, uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.return.move.line", "table_name": ""}
+{"text": "Show me the fields of purchase.agreement.legal.document.", "response": "The purchase.agreement.legal.document model has 15 fields: legal_document_id, partner_id, nomor_induk_berusaha, salinan_anggaran_dasar, surat_persetujuan_dirjen_ahu, akta_perubahan_pengurus_terakhir, surat_keterangan_tidak_kena_pajak, surat_pernyataan_dan_kuasa, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, boolean: 6, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.agreement.legal.document", "table_name": ""}
+{"text": "How to create records in approval.matrix.sale.order.lines?", "response": "To use the approval.matrix.sale.order.lines model, you need to provide values for required fields: user_name_ids, sequence, minimum_approver. Readonly fields: sequence2, signature, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.sale.order.lines", "table_name": ""}
+{"text": "Describe the export.retur.pajak.masukan model in Odoo.", "response": "The export.retur.pajak.masukan model represents export.retur.pajak.masukan in the ERP system. It contains 12 fields and is used to manage export.retur.pajak.masukan data. Key fields include: partner_id, date_from, date_to, tax_report_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "export.retur.pajak.masukan", "table_name": ""}
+{"text": "What data can be stored in account.move.line?", "response": "The account.move.line model has 140 fields: asset_category_id, asset_start_date, asset_end_date, asset_mrr, purchase_line_id, purchase_order_id, period_id, fiscal_year, is_anglo_saxon_line, product_type, is_landed_costs_line, discount_method, discount_type, discount_amount, discount_amt, branch_id, repair_line_ids, repair_fee_ids, is_down_payment, move_id, move_name, date, ref, parent_state, journal_id, company_id, company_currency_id, tax_fiscal_country_id, account_id, account_internal_type, account_internal_group, account_root_id, sequence, name, quantity, price_unit, discount, debit, credit, balance, cumulated_balance, amount_currency, price_subtotal, price_total, reconciled, blocked, date_maturity, currency_id, partner_id, product_uom_id, product_id, product_uom_category_id, reconcile_model_id, payment_id, statement_line_id, statement_id, tax_ids, tax_line_id, tax_group_id, tax_base_amount, tax_exigible, tax_repartition_line_id, tax_tag_ids, tax_audit, amount_residual, amount_residual_currency, full_reconcile_id, matched_debit_ids, matched_credit_ids, matching_number, analytic_line_ids, analytic_account_id, analytic_tag_ids, recompute_tax_line, display_type, is_rounding_line, exclude_from_invoice_tab, is_fiscal_book_exclude, price_tax_discount, is_update_disc_line, price_tax, unit_price_fnct, disc_percentage_rel, date_id, is_discount_line, is_interest_line, is_analytic_tags, total_qty_price_unit, multi_discount, is_intercompany_transaction, customer_deposit_id, vendor_deposit_id, tax_ids_ppn, price_total_ppn, amount_ppn, taxes_ppn, sale_line_ids, is_down_payment_discount, res_dp_amount, is_purchase_order, is_sales_order, sequence2, pos_branch_id, approval_code, check_reconcile, check_reconcile_done, check_reconcile_flag, check_payment, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 35, date: 7, float: 9, boolean: 26, selection: 9, one2many: 9, char: 11, integer: 7, monetary: 16, many2many: 7, html: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.move.line", "table_name": ""}
+{"text": "How does account.trial.balance relate to other models?", "response": "The account.trial.balance 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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.trial.balance", "table_name": ""}
+{"text": "How do I use the x.report.wizard model?", "response": "To use the x.report.wizard model, you need to provide values for required fields: pos_session_ids. Readonly fields: report_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "x.report.wizard", "table_name": ""}
+{"text": "What does the uom.uom model represent?", "response": "The uom.uom model represents Product Unit of Measure in the ERP system. It contains 19 fields and is used to manage product unit of measure data. Key fields include: name, category_id, factor, factor_inv, rounding, active, uom_type, timesheet_widget, is_pos_groupable, is_custom_uom, product_ratio_line, is_external_link, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "uom.uom", "table_name": ""}
+{"text": "Describe the field structure of board.board.", "response": "The board.board model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "board.board", "table_name": ""}
+{"text": "What are the relationships in pos.order.location?", "response": "The pos.order.location model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.order.location", "table_name": ""}
+{"text": "Describe the account.ebupot model in Odoo.", "response": "The account.ebupot model represents Account E-Bupot in the ERP system. It contains 18 fields and is used to manage account e-bupot data. Key fields include: year, name, is_used, invoice_ids, tax_report_id, date_from, date_to, partner_id, company_id, ebupot_template, tahun_pajak, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.ebupot", "table_name": ""}
+{"text": "Describe the many2many relations for inter.transfer.company.", "response": "The inter.transfer.company model has 11 relational fields: sale_id -> sale.order; invoice_id -> account.move; purchase_id -> purchase.order; return_id -> return.inter.transfer.company; from_warehouse -> stock.warehouse; currency_id -> res.currency; to_warehouse -> stock.warehouse; pricelist_id -> product.pricelist; product_lines -> inter.transfer.company.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: invoice_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "inter.transfer.company", "table_name": ""}
+{"text": "What modules define project.task.type.delete.wizard?", "response": "The project.task.type.delete.wizard model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "project.task.type.delete.wizard", "table_name": ""}
+{"text": "How to query stock.immediate.transfer data?", "response": "To use the stock.immediate.transfer 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.immediate.transfer", "table_name": ""}
+{"text": "Show me the relational structure of mrp.bom.line.", "response": "The mrp.bom.line model has 19 relational fields: product_tmpl_id -> product.template; company_id -> res.company; product_uom_category_id -> uom.category; bom_id -> mrp.bom; parent_product_tmpl_id -> product.template; possible_bom_product_template_attribute_value_ids -> product.template.attribute.value; bom_product_template_attribute_value_ids -> product.template.attribute.value; allowed_operation_ids -> mrp.routing.workcenter; operation_id -> mrp.routing.workcenter; child_bom_id -> mrp.bom; child_line_ids -> mrp.bom.line; branch_id -> res.branch; product_id -> product.product; alternative_component_ids -> product.product; operation_two_ids -> mrp.bom.operation; operation_two_id -> mrp.bom.operation; product_uom_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: possible_bom_product_template_attribute_value_ids, bom_product_template_attribute_value_ids, allowed_operation_ids, alternative_component_ids, operation_two_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.bom.line", "table_name": ""}
+{"text": "How is picking.return.line used in the system?", "response": "The picking.return.line model represents picking.return.line in the ERP system. It contains 14 fields and is used to manage picking.return.line data. Key fields include: name, product_id, picking_id, purchase_id, sale_id, currency_id, price, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "picking.return.line", "table_name": ""}
+{"text": "Show me the fields of sh.tsp.top.purchasing.product.", "response": "The sh.tsp.top.purchasing.product model has 9 fields: product_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.tsp.top.purchasing.product", "table_name": ""}
+{"text": "What does the product.expire.report model represent?", "response": "The product.expire.report model represents product.expire.report in the ERP system. It contains 8 fields and is used to manage product.expire.report data. Key fields include: report_selection, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.expire.report", "table_name": ""}
+{"text": "Tell me about the ai.data.cleanup model.", "response": "The ai.data.cleanup model represents AI Data Cleanup Scheduler in the ERP system. It contains 23 fields and is used to manage ai data cleanup scheduler data. Key fields include: name, active, cleanup_interval_days, last_run, next_run, cleanup_old_sessions, session_age_days, cleanup_few_message_sessions, few_message_session_age_days, cleanup_orphaned_messages, cleanup_uploaded_attachments, uploaded_attachments_age_days, cleanup_old_generated_files, generated_files_age_days, cleanup_old_sandbox_folders, sandbox_folders_age_days, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ai.data.cleanup", "table_name": ""}
+{"text": "What foreign keys exist in sh.mrp.qc.alert.line?", "response": "The sh.mrp.qc.alert.line model has 5 relational fields: alert_id -> sh.mrp.qc.alert; product_id -> product.product; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.mrp.qc.alert.line", "table_name": ""}
+{"text": "What business logic is in sh.sale.product.profit.xls?", "response": "To use the sh.sale.product.profit.xls model, you need to provide values for required fields: none. Readonly fields: file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.sale.product.profit.xls", "table_name": ""}
+{"text": "What are the technical details of sh.stock.move.pics?", "response": "The sh.stock.move.pics model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.stock.move.pics", "table_name": ""}
+{"text": "How is ir.model.constraint implemented technically?", "response": "The ir.model.constraint model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.model.constraint", "table_name": ""}
+{"text": "What methods are available in sh.purchase.bill.summary.wizard?", "response": "The sh.purchase.bill.summary.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.bill.summary.wizard", "table_name": ""}
+{"text": "How to create records in pos.payment.wizard?", "response": "To use the pos.payment.wizard model, you need to provide values for required fields: start_dt, end_dt. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.payment.wizard", "table_name": ""}
+{"text": "Which fields in warehouse.capacity.excel.report are computed?", "response": "The warehouse.capacity.excel.report model is defined in module: equip3_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "warehouse.capacity.excel.report", "table_name": ""}
+{"text": "What models are connected to pos.gift.card.type?", "response": "The pos.gift.card.type model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.gift.card.type", "table_name": ""}
+{"text": "How is product.ratio.line implemented technically?", "response": "The product.ratio.line model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.ratio.line", "table_name": ""}
+{"text": "What operations can I perform on mrp.bom.tools?", "response": "To use the mrp.bom.tools model, you need to provide values for required fields: bom_id, product_id, quantity, uom_id. Readonly fields: company_id, workorder_id, allowed_operation_ids, operation_two_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mrp.bom.tools", "table_name": ""}
+{"text": "What operations can I perform on acrux.chat.select.conversation.wizard?", "response": "To use the acrux.chat.select.conversation.wizard model, you need to provide values for required fields: conversation_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "acrux.chat.select.conversation.wizard", "table_name": ""}
+{"text": "Show me the relational structure of pos.promotion.multi.buy.", "response": "The pos.promotion.multi.buy model has 4 relational fields: product_ids -> product.product; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.promotion.multi.buy", "table_name": ""}
+{"text": "What models are connected to blacklist.partner.wiz?", "response": "The blacklist.partner.wiz model has 4 relational fields: partner_id -> res.partner; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "blacklist.partner.wiz", "table_name": ""}
+{"text": "Show me the fields of accounting.report.", "response": "The accounting.report model has 20 fields: enable_filter, account_report_id, label_filter, filter_cmp, date_from_cmp, date_to_cmp, debit_credit, 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 types distribution: boolean: 2, many2one: 5, char: 2, selection: 2, date: 4, many2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "accounting.report", "table_name": ""}
+{"text": "What methods are available in account.common.journal.report?", "response": "The account.common.journal.report model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.common.journal.report", "table_name": ""}
+{"text": "How is approval.matrix.direct.purchase.line implemented technically?", "response": "The approval.matrix.direct.purchase.line model is defined in module: equip3_purchase_other_operation_cont. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "approval.matrix.direct.purchase.line", "table_name": ""}
+{"text": "Show me the relational structure of format.address.mixin.", "response": "The format.address.mixin model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "format.address.mixin", "table_name": ""}
+{"text": "Can you explain the purpose of vendor.evaluation.rating?", "response": "The vendor.evaluation.rating model represents vendor.evaluation.rating in the ERP system. It contains 9 fields and is used to manage vendor.evaluation.rating data. Key fields include: partner_id, fulfillment_avg, on_time_rate_avg, final_point_avg, vendor_evaluation_count, branch_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "vendor.evaluation.rating", "table_name": ""}
+{"text": "What are the available fields for sale.order.alternative.product?", "response": "The sale.order.alternative.product model has 11 fields: alter_product_ids, product_id, sale_line_id, selected_product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, many2one: 5, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.order.alternative.product", "table_name": ""}
+{"text": "Describe the field structure of all.loyalty.history.", "response": "The all.loyalty.history model has 19 fields: order_id, pos_order_id, partner_id, date, generated_from, transaction_type, points, amount, currency_id, company_id, check_state, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, datetime: 4, selection: 3, integer: 2, char: 2, boolean: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "all.loyalty.history", "table_name": ""}
+{"text": "What models are connected to sh.purchase.tags?", "response": "The sh.purchase.tags model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.tags", "table_name": ""}
+{"text": "What fields does stock.move have?", "response": "The stock.move model has 237 fields: name, sequence, priority, create_date, date, date_deadline, company_id, description_picking, product_qty, product_uom_qty, product_uom, product_uom_category_id, product_tmpl_id, location_id, location_dest_id, partner_id, move_dest_ids, move_orig_ids, picking_partner_id, note, state, price_unit, backorder_id, origin, procure_method, scrapped, scrap_ids, group_id, rule_id, propagate_cancel, delay_alert_date, picking_type_id, inventory_id, move_line_ids, move_line_nosuggest_ids, origin_returned_move_id, returned_move_ids, availability, restrict_partner_id, route_ids, warehouse_id, has_tracking, show_operations, show_details_visible, show_reserved_availability, additional, is_locked, is_initial_demand_editable, is_quantity_done_editable, reference, has_move_lines, package_level_id, picking_type_entire_packs, display_assign_serial, next_serial_count, orderpoint_id, forecast_availability, forecast_expected_date, lot_ids, created_production_id, production_id, raw_material_production_id, unbuild_id, consume_unbuild_id, allowed_operation_ids, operation_id, workorder_id, bom_line_id, byproduct_id, unit_factor, is_done, order_finished_lot_ids, should_consume_qty, use_expiration_date, to_refund, account_move_ids, stock_valuation_layer_ids, is_reconstruct_svl, scrap_return_move_id, purchase_line_id, created_purchase_line_id, sh_quality_point, sh_quality_point_id, sh_last_qc_date, sh_last_qc_state, number_of_test, created_purchase_request_line_id, purchase_request_allocation_ids, purchase_request_ids, requisition_line_ids, sale_line_id, branch_id, weight, product_description, qty_pack, is_pack, repair_id, sh_stock_move_barcode_mobile, sh_stock_move_bm_is_cont_scan, length, width, height, product_id, is_adjustable_picking, package_measure_selection, picking_state, is_existing_package, move_package_id, filter_move_package_ids, mr_line_id, move_line_sequence, serial_no, export_file, export_name, next_serial, next_serial_not_autogenerate, next_lot_not_autogenerate, is_import, is_record_confirm, product_type, is_serial_number, next_lot, qty_per_lot, is_autogenerate, picking_code, is_product_service_operation, is_product_service_operation_delivery, is_product_service_operation_receiving, serial, initial_demand, move_progress, analytic_account_group_ids, remaining, fulfillment, current_qty, scheduled_date, responsible, late_time, late_time_hours, process_status, process_time, process_time_hours, package_type, qty_in_pack, packaging_ids, package_quant_ids, measure_ids, product_id_domain, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, created_assembly_id, assembly_finished_id, assembly_component_id, assembly_unit_factor, assembly_should_consume_qty, assembly_product_free_qty, description, created_kitchen_id, kitchen_finished_id, kitchen_component_id, kitchen_unit_factor, kitchen_should_consume_qty, kitchen_product_free_qty, asp_asm_stock_id, bom_product_uom_qty, sub_total, finish_good_rework_id, type_product_bom, finish_good_rework_finished_id, finish_good_rework_created_kitchen_id, finish_good_rework_by_product_id, assembly_record_type, assembly_confirm_date, assembly_product_id, assembly_bom_id, assembly_svl_value, assembly_difference, exp_date, qty_bundle, id_bundle, package_barcode, kitchen_confirm_date, kitchen_product_id, kitchen_bom_id, kitchen_svl_value, kitchen_difference, product_warehouse, product_location, expired_date, product_barcode, vendor_id, state_expired, state_check, picking_type_code, reserved_by_id, reserved_availability, is_reserved, picking_id, origin_src_location, origin_dest_location, picking_reference, is_transit, date_done, return_reason, action, is_transfer_in, is_transfer_out, quantity_done, volume, movement_type, cost, combo_item_id, pos_branch_id, pos_order_line_id, so_antar_badan, po_antar_badan, sale_order_id, purchase_order_id, date_done_real, taxes_id, price_subtotal, price_tax, price_total, price_untaxed_amount, discount_amount, price_discount, currency_id, returned_qty, remaining_checked_qty, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: char: 23, integer: 10, selection: 17, datetime: 14, many2one: 71, text: 2, float: 39, many2many: 12, boolean: 34, one2many: 9, binary: 1, date: 1, monetary: 4.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.move", "table_name": ""}
+{"text": "What data can be stored in kitchen.production.record?", "response": "The kitchen.production.record model has 79 fields: name, company_id, is_branch_required, product_id, product_tmpl_id, product_qty, rejected_qty, product_uom_id, product_uom_category_id, bom_id, branch_id, confirm_date, state, move_raw_ids, move_finished_ids, move_byproduct_ids, location_src_id, location_dest_id, picking_type_id, date_planned_start, date_planned_finished, date_deadline, procurement_group_id, move_dest_ids, production_location_id, warehouse_id, product_tracking, account_move_ids, purchase_request_ids, internal_transfer_count, expiry_days, product_use_expiration_date, finished_lot_ids, byproduct_lot_ids, rejected_lot_ids, show_submit_button, is_autogenerate, default_finished_lot_qty, default_rejected_lot_qty, show_byproduct_lot_tab, byproduct_manual_product_ids, default_byproduct_lot_qty, default_next_byproduct_product_id, any_byproduct_is_autogenerate, all_byproduct_is_autogenerate, component_consumed_qty, svl_value, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 19, boolean: 12, float: 6, datetime: 7, selection: 4, one2many: 13, integer: 7, many2many: 3, text: 1, date: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "kitchen.production.record", "table_name": ""}
+{"text": "Describe the many2many relations for crm.phonecall.", "response": "The crm.phonecall model has 17 relational fields: team_id -> crm.team; user_id -> res.users; partner_id -> res.partner; company_id -> res.company; tag_ids -> crm.tag; opportunity_id -> crm.lead; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.phonecall", "table_name": ""}
+{"text": "Describe the account.group model in Odoo.", "response": "The account.group model represents Account Group in the ERP system. It contains 13 fields and is used to manage account group data. Key fields include: parent_id, parent_path, code_prefix_start, code_prefix_end, company_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.group", "table_name": ""}
+{"text": "How do I use the pos.payment.edc model?", "response": "To use the pos.payment.edc model, you need to provide values for required fields: none. Readonly fields: pos_branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.payment.edc", "table_name": ""}
+{"text": "Can you explain the purpose of res.users.tag?", "response": "The res.users.tag model represents User Tag in the ERP system. It contains 8 fields and is used to manage user tag data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.users.tag", "table_name": ""}
+{"text": "What are the relationships in product.pricelist.change?", "response": "The product.pricelist.change model has 4 relational fields: pricelist_id -> product.pricelist; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.pricelist.change", "table_name": ""}
+{"text": "How does account.invoice.exchange.approval.wizard relate to other models?", "response": "The account.invoice.exchange.approval.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.invoice.exchange.approval.wizard", "table_name": ""}
+{"text": "What is the dynamic.balance.sheet.report model?", "response": "The dynamic.balance.sheet.report model represents Balance Sheet Report in the ERP system. It contains 17 fields and is used to manage balance sheet report data. Key fields include: company_id, journal_ids, account_ids, account_tag_ids, analytic_ids, analytic_tag_ids, display_account, target_move, date_from, date_to, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "dynamic.balance.sheet.report", "table_name": ""}
+{"text": "Describe the close.fiscal.year model in Odoo.", "response": "The close.fiscal.year model represents Close Fiscal Year in the ERP system. It contains 8 fields and is used to manage close fiscal year data. Key fields include: fiscal_year_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "close.fiscal.year", "table_name": ""}
+{"text": "What fields does product.template.attribute.exclusion have?", "response": "The product.template.attribute.exclusion model has 10 fields: product_template_attribute_value_id, product_tmpl_id, value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.template.attribute.exclusion", "table_name": ""}
+{"text": "How to create records in bus.bus?", "response": "To use the bus.bus model, you need to provide values for required fields: none. Readonly fields: channel, message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "bus.bus", "table_name": ""}
+{"text": "List all fields in the account.resequence.wizard model.", "response": "The account.resequence.wizard model has 15 fields: sequence_number_reset, first_date, end_date, first_name, ordering, move_ids, new_values, preview_moves, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, date: 2, selection: 1, many2many: 1, text: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.resequence.wizard", "table_name": ""}
+{"text": "What are common use cases for setu.inventory.overstock.bi.report?", "response": "To use the setu.inventory.overstock.bi.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.overstock.bi.report", "table_name": ""}
+{"text": "Can you explain the purpose of im_livechat.channel?", "response": "The im_livechat.channel model represents Livechat Channel in the ERP system. It contains 30 fields and is used to manage livechat channel data. Key fields include: name, button_text, default_message, input_placeholder, header_background_color, title_color, button_background_color, button_text_color, web_page, are_you_inside, script_external, nbr_channel, image_128, user_ids, channel_ids, rule_ids, website_published, is_published, can_publish, website_url, website_description, rating_ids, rating_percentage_satisfaction, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "im_livechat.channel", "table_name": ""}
+{"text": "Describe the ir.http model in Odoo.", "response": "The ir.http model represents HTTP Routing in the ERP system. It contains 3 fields and is used to manage http routing data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.http", "table_name": ""}
+{"text": "What data can be stored in account.fiscal.position.tax?", "response": "The account.fiscal.position.tax model has 11 fields: position_id, company_id, tax_src_id, tax_dest_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.fiscal.position.tax", "table_name": ""}
+{"text": "What methods are available in sh_barcode_scanner_adv.search.document?", "response": "The sh_barcode_scanner_adv.search.document model is defined in module: sh_all_in_one_mbs. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh_barcode_scanner_adv.search.document", "table_name": ""}
+{"text": "Tell me about the closing.balance.confirm.wizard model.", "response": "The closing.balance.confirm.wizard model represents This wizard is used to display a warning message if the manager wants to close a session with a too high difference between real and expected closing balance in the ERP system. It contains 9 fields and is used to manage this wizard is used to display a warning message if the manager wants to close a session with a too high difference between real and expected closing balance data. Key fields include: cash_closing_balance_char, cash_register_difference_char, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "closing.balance.confirm.wizard", "table_name": ""}
+{"text": "Which fields in account.journal.group are computed?", "response": "The account.journal.group model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.journal.group", "table_name": ""}
+{"text": "What is the assembly.safety.stock.line model?", "response": "The assembly.safety.stock.line model represents Assembly Safety Stock Management Line in the ERP system. It contains 10 fields and is used to manage assembly safety stock management line data. Key fields include: stock_id, product_id, product_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assembly.safety.stock.line", "table_name": ""}
+{"text": "Can you explain the purpose of report.account.report_journal?", "response": "The report.account.report_journal model represents Account Journal Report in the ERP system. It contains 3 fields and is used to manage account journal report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.account.report_journal", "table_name": ""}
+{"text": "What fields does receivable.opening.balance have?", "response": "The receivable.opening.balance model has 14 fields: partner_opening_bal_id, customer_id, purchase_order, date, description, due_date, amount_due, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 3, date: 2, float: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "receivable.opening.balance", "table_name": ""}
+{"text": "What fields does stock.track.confirmation have?", "response": "The stock.track.confirmation model has 9 fields: tracking_line_ids, inventory_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.track.confirmation", "table_name": ""}
+{"text": "What does the calendar.contacts model represent?", "response": "The calendar.contacts model represents Calendar Contacts in the ERP system. It contains 10 fields and is used to manage calendar contacts data. Key fields include: user_id, partner_id, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "calendar.contacts", "table_name": ""}
+{"text": "What business logic is in monthly.account.budget.lines?", "response": "To use the monthly.account.budget.lines model, you need to provide values for required fields: none. Readonly fields: jan_actual, feb_actual, march_actual, april_actual, may_actual, june_actual, july_actual, august_actual, sep_actual, oct_actual, nov_actual, dec_actual, planned_amount, actual_amount, over_budget, account_plan_id, year_id, year_name, date_start, date_end, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "monthly.account.budget.lines", "table_name": ""}
+{"text": "What foreign keys exist in account.fiscal.year?", "response": "The account.fiscal.year model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.fiscal.year", "table_name": ""}
+{"text": "Describe the product.packaging model in Odoo.", "response": "The product.packaging model represents Product Packaging in the ERP system. It contains 33 fields and is used to manage product packaging data. Key fields include: name, sequence, qty, barcode, product_uom_id, company_id, height, width, packaging_length, max_weight, shipper_package_code, package_carrier_type, weight_uom_name, length_uom_name, product_id, maximum_height, maximum_length, maximum_width, maximum_volume, packages_barcode_prefix, digits, current_sequence, filter_value_ids, measure_ids, volume_calculation, volume_formula, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.packaging", "table_name": ""}
+{"text": "What fields does vendor.pricelist.approval.matrix have?", "response": "The vendor.pricelist.approval.matrix model has 14 fields: name, company_id, branch_id, department_id, created_by, created_date, approval_matrix_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 6, date: 1, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "vendor.pricelist.approval.matrix", "table_name": ""}
+{"text": "What is the website.menu model?", "response": "The website.menu model represents Website Menu in the ERP system. It contains 25 fields and is used to manage website menu data. Key fields include: name, url, page_id, new_window, sequence, website_id, parent_id, child_id, parent_path, is_visible, group_ids, is_mega_menu, mega_menu_content, mega_menu_classes, theme_template_id, is_display_in_delivery_control_app, user_logged, user_not_logged, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "website.menu", "table_name": ""}
+{"text": "What foreign keys exist in pos.make.payment?", "response": "The pos.make.payment model has 5 relational fields: config_id -> pos.config; payment_method_id -> pos.payment.method; pos_order_id -> pos.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.make.payment", "table_name": ""}
+{"text": "What are the technical details of sale.coupon.apply.code?", "response": "The sale.coupon.apply.code model is defined in module: sale_coupon. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.coupon.apply.code", "table_name": ""}
+{"text": "Describe the implementation of account.internal.transfer.", "response": "The account.internal.transfer model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.internal.transfer", "table_name": ""}
+{"text": "What are the technical details of pos.payment.wizard?", "response": "The pos.payment.wizard model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.payment.wizard", "table_name": ""}
+{"text": "What are the available fields for sequence.mixin?", "response": "The sequence.mixin model has 5 fields: sequence_prefix, sequence_number, id, display_name, __last_update. Field types distribution: char: 2, integer: 2, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sequence.mixin", "table_name": ""}
+{"text": "List all fields in the phone.blacklist model.", "response": "The phone.blacklist model has 24 fields: number, active, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 6, one2many: 3, many2many: 2, integer: 5, many2one: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "phone.blacklist", "table_name": ""}
+{"text": "What fields does res.users.access.report.record have?", "response": "The res.users.access.report.record model has 26 fields: sl_no, user_id, login, user_active, column1, column2, column3, column4, column5, column6, column7, column8, column9, column10, column11, column12, column13, column14, column15, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 3, char: 2, boolean: 16, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.users.access.report.record", "table_name": ""}
+{"text": "Describe the field structure of base_import.mapping.", "response": "The base_import.mapping model has 10 fields: res_model, column_name, field_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.mapping", "table_name": ""}
+{"text": "What fields does report.accounting_pdf_reports.report_trialbalance have?", "response": "The report.accounting_pdf_reports.report_trialbalance model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.accounting_pdf_reports.report_trialbalance", "table_name": ""}
+{"text": "What business logic is in mr.approval.matrix.line?", "response": "To use the mr.approval.matrix.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: sequence2, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mr.approval.matrix.line", "table_name": ""}
+{"text": "How is product.warehouse.cost used in the system?", "response": "The product.warehouse.cost model represents Product Warehouse Cost in the ERP system. It contains 10 fields and is used to manage product warehouse cost data. Key fields include: product_id, product_cost_line_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.warehouse.cost", "table_name": ""}
+{"text": "What fields does ir.filters have?", "response": "The ir.filters model has 16 fields: name, user_id, domain, context, sort, model_id, is_default, action_id, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, text: 3, selection: 1, boolean: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.filters", "table_name": ""}
+{"text": "What foreign keys exist in report.equip3_accounting_operation.report_statement_temp?", "response": "The report.equip3_accounting_operation.report_statement_temp model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_operation.report_statement_temp", "table_name": ""}
+{"text": "What data can be stored in coupon.coupon?", "response": "The coupon.coupon model has 29 fields: code, expiration_date, partner_id, program_id, discount_line_product_id, order_id, sales_order_id, pos_order_id, origin, is_gift_card, is_returned_order, redeem_history_ids, state, pos_create_date, pos_create_uid, pos_config_id, base_amount, redeem_amount, balance_amount, pos_orderline_id, purchase_id, purchases_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, date: 1, many2one: 13, boolean: 2, one2many: 1, selection: 1, datetime: 4, float: 3, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "coupon.coupon", "table_name": ""}
+{"text": "How do I use the pos.loyalty.rule model?", "response": "To use the pos.loyalty.rule model, you need to provide values for required fields: name, loyalty_id, coefficient, type, min_amount. Readonly fields: categories, coefficient_note, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.loyalty.rule", "table_name": ""}
+{"text": "Describe the many2many relations for store.filters.groups.", "response": "The store.filters.groups model has 3 relational fields: model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "store.filters.groups", "table_name": ""}
+{"text": "What data can be stored in website.rewrite?", "response": "The website.rewrite model has 15 fields: name, website_id, active, url_from, route_id, url_to, redirect_type, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 4, boolean: 1, selection: 1, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "website.rewrite", "table_name": ""}
+{"text": "What operations can I perform on report.excel.section?", "response": "To use the report.excel.section model, you need to provide values for required fields: name, type_data, section_start, section_end. Readonly fields: report_id, report_excel_param_content, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.excel.section", "table_name": ""}
+{"text": "How to create records in ir.model.data?", "response": "To use the ir.model.data model, you need to provide values for required fields: name, model, module. Readonly fields: complete_name, reference, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.model.data", "table_name": ""}
+{"text": "How does pos.coupon.program relate to other models?", "response": "The pos.coupon.program model has 5 relational fields: base_on_product_id -> product.product; company_id -> res.company; reward_product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.coupon.program", "table_name": ""}
+{"text": "What operations can I perform on vendor.deposit.line.reconcile?", "response": "To use the vendor.deposit.line.reconcile model, you need to provide values for required fields: none. Readonly fields: filter_move_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "vendor.deposit.line.reconcile", "table_name": ""}
+{"text": "What fields does report.sh_inventory_mrp_qc.mrp_quality_alert_doc have?", "response": "The report.sh_inventory_mrp_qc.mrp_quality_alert_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_inventory_mrp_qc.mrp_quality_alert_doc", "table_name": ""}
+{"text": "Describe the many2many relations for utm.medium.", "response": "The utm.medium model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "utm.medium", "table_name": ""}
+{"text": "How does ir.module.module relate to other models?", "response": "The ir.module.module model has 6 relational fields: category_id -> ir.module.category; dependencies_id -> ir.module.module.dependency; exclusion_ids -> ir.module.module.exclusion; image_ids -> ir.attachment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.module.module", "table_name": ""}
+{"text": "Show me the fields of approval.matrix.purchase.request.", "response": "The approval.matrix.purchase.request model has 48 fields: name, company_id, branch_id, department_id, minimum_amt, maximum_amt, is_purchase_request_department, approval_matrix_purchase_request_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. Field types distribution: char: 7, many2one: 11, float: 2, boolean: 7, one2many: 5, selection: 3, date: 2, many2many: 2, integer: 5, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.purchase.request", "table_name": ""}
+{"text": "What models are connected to milestone.contract.template.purchase?", "response": "The milestone.contract.template.purchase model has 4 relational fields: purchase_order_id -> purchase.order; checklist_template_id -> purchase.custom.checklist.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "milestone.contract.template.purchase", "table_name": ""}
+{"text": "Show me the fields of debt.collection.report.", "response": "The debt.collection.report model has 16 fields: partner_ids, user_ids, journal_ids, state, 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 types distribution: many2many: 3, selection: 2, date: 2, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "debt.collection.report", "table_name": ""}
+{"text": "How is mrp.bom.line used in the system?", "response": "The mrp.bom.line model represents Bill of Material Line in the ERP system. It contains 28 fields and is used to manage bill of material line data. Key fields include: product_tmpl_id, company_id, product_qty, product_uom_category_id, sequence, bom_id, parent_product_tmpl_id, possible_bom_product_template_attribute_value_ids, bom_product_template_attribute_value_ids, allowed_operation_ids, operation_id, child_bom_id, child_line_ids, attachments_count, branch_id, cost, product_id, alternative_component_ids, operation_two_ids, operation_two_id, product_uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.bom.line", "table_name": ""}
+{"text": "What fields does report.dynamic_accounts_report.trial_balance have?", "response": "The report.dynamic_accounts_report.trial_balance model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.dynamic_accounts_report.trial_balance", "table_name": ""}
+{"text": "How is sh.sale.product.indent.wizard implemented technically?", "response": "The sh.sale.product.indent.wizard model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.sale.product.indent.wizard", "table_name": ""}
+{"text": "Describe the mrp.unbuild model in Odoo.", "response": "The mrp.unbuild model represents Unbuild Order in the ERP system. It contains 48 fields and is used to manage unbuild order data. Key fields include: name, product_id, company_id, product_qty, product_uom_id, bom_id, mo_id, mo_bom_id, lot_id, has_tracking, location_id, location_dest_id, consume_line_ids, produce_line_ids, state, allowed_mo_ids, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.unbuild", "table_name": ""}
+{"text": "What modules define account.report.general.ledger?", "response": "The account.report.general.ledger model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.report.general.ledger", "table_name": ""}
+{"text": "Describe the field structure of resource.mixin.", "response": "The resource.mixin model has 7 fields: resource_id, company_id, resource_calendar_id, tz, id, display_name, __last_update. Field types distribution: many2one: 3, selection: 1, integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "resource.mixin", "table_name": ""}
+{"text": "What business logic is in multiple.rfq?", "response": "To use the multiple.rfq 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "multiple.rfq", "table_name": ""}
+{"text": "Describe the purchase.request.wizard.line model in Odoo.", "response": "The purchase.request.wizard.line model represents purchase.request.wizard.line in the ERP system. It contains 17 fields and is used to manage purchase.request.wizard.line data. Key fields include: mr_id, no, product_id, description, uom_id, qty_purchase, request_date, mr_pr_wizard, mr_line_id, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.request.wizard.line", "table_name": ""}
+{"text": "How to create records in free.product.lines?", "response": "To use the free.product.lines model, you need to provide values for required fields: product_id, description, quantity, uom_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "free.product.lines", "table_name": ""}
+{"text": "What business logic is in void.order.line?", "response": "To use the void.order.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "void.order.line", "table_name": ""}
+{"text": "Show me the fields of account.pettycash.fund.close.", "response": "The account.pettycash.fund.close model has 11 fields: fund, receivable_account, effective_date, close_balance, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, date: 1, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.pettycash.fund.close", "table_name": ""}
+{"text": "What models are connected to term.condition?", "response": "The term.condition model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "term.condition", "table_name": ""}
+{"text": "What are the available fields for milestone.contract.template.purchase?", "response": "The milestone.contract.template.purchase model has 12 fields: purchase_order_id, name, checklist_template_id, contract_term, progress_paid, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 2, float: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "milestone.contract.template.purchase", "table_name": ""}
+{"text": "Describe the field structure of mrp.production.backorder.line.", "response": "The mrp.production.backorder.line model has 10 fields: mrp_production_backorder_id, mrp_production_id, to_backorder, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.production.backorder.line", "table_name": ""}
+{"text": "What are the technical details of warranty.claim.category?", "response": "The warranty.claim.category model is defined in module: bi_warranty_registration. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "warranty.claim.category", "table_name": ""}
+{"text": "What data can be stored in mrp.workorder?", "response": "The mrp.workorder model has 71 fields: name, workcenter_id, working_state, product_id, product_tracking, product_uom_id, use_create_components_lots, production_id, production_availability, production_state, production_bom_id, qty_production, company_id, qty_producing, qty_remaining, qty_produced, is_produced, state, leave_id, date_planned_start, date_planned_finished, date_start, date_finished, duration_expected, duration, duration_unit, duration_percent, progress, operation_id, worksheet, worksheet_type, worksheet_google_slide, operation_note, move_raw_ids, move_finished_ids, move_line_ids, finished_lot_id, time_ids, is_user_working, working_user_ids, last_working_user_id, next_work_order_id, scrap_ids, scrap_count, production_date, json_popover, show_json_popover, consumption, 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, qc_count, qc_alert_count, sh_workorder_quality_point_id, need_qc, pending_qc, qc_fail, qc_pass, attachment_ids, partner_id, is_mandatory, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 14, selection: 7, boolean: 9, float: 8, datetime: 8, integer: 5, binary: 1, text: 1, one2many: 13, many2many: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.workorder", "table_name": ""}
+{"text": "Tell me about the acrux.chat.message.wizard model.", "response": "The acrux.chat.message.wizard model represents ChatRoom Message in the ERP system. It contains 20 fields and is used to manage chatroom message data. Key fields include: text, partner_id, conversation_id, connector_id, sale_id, message_mass_id, phone, is_crm, opportunity_id, whatsapp_template_id, crm_message_mass_id, mobile, attachment_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "acrux.chat.message.wizard", "table_name": ""}
+{"text": "How does base_import.tests.models.m2o relate to other models?", "response": "The base_import.tests.models.m2o model has 3 relational fields: value -> base_import.tests.models.m2o.related; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.m2o", "table_name": ""}
+{"text": "What are common use cases for purchase.request.line.make.purchase.order.item?", "response": "To use the purchase.request.line.make.purchase.order.item model, you need to provide values for required fields: wiz_id, name, product_uom_id. Readonly fields: wiz_id, rem_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.request.line.make.purchase.order.item", "table_name": ""}
+{"text": "What operations can I perform on target.activity.line.res?", "response": "To use the target.activity.line.res 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "target.activity.line.res", "table_name": ""}
+{"text": "Tell me about the res.partner.rfm.segment.history model.", "response": "The res.partner.rfm.segment.history model represents \n    Customer RFM segment history table will automatically add records in the table when the customer RFM score will be changed to another one and if the segment value has been changed\n     in the ERP system. It contains 16 fields and is used to manage \n    customer rfm segment history table will automatically add records in the table when the customer rfm score will be changed to another one and if the segment value has been changed\n     data. Key fields include: partner_id, history_date, old_rfm_segment_id, new_rfm_segment_id, old_rfm_score_id, new_rfm_score_id, old_segment_rank, new_segment_rank, engagement_direction, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.partner.rfm.segment.history", "table_name": ""}
+{"text": "What modules define theme.utils?", "response": "The theme.utils model is defined in module: website. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "theme.utils", "table_name": ""}
+{"text": "What are common use cases for mr.internal_transfer_line?", "response": "To use the mr.internal_transfer_line model, you need to provide values for required fields: qty_transfer. Readonly fields: no, virtual_available, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mr.internal_transfer_line", "table_name": ""}
+{"text": "What business logic is in customer.deposit?", "response": "To use the customer.deposit model, you need to provide values for required fields: none. Readonly fields: name, return_deposit, filter_deposit_account_ids, deposit_move_id, is_show_cancel, invoice_count, reconcile_count, approval_matrix_id, is_customer_deposit_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, deposit_history, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "customer.deposit", "table_name": ""}
+{"text": "What are the technical details of setu.inventory.age.report?", "response": "The setu.inventory.age.report model is defined in module: setu_advance_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "setu.inventory.age.report", "table_name": ""}
+{"text": "What data can be stored in pos.session?", "response": "The pos.session model has 101 fields: company_id, config_id, name, user_id, currency_id, start_at, stop_at, sequence_number, cash_control, cash_journal_id, cash_register_id, cash_register_balance_start, cash_register_balance_end, cash_register_difference, cash_real_difference, cash_real_transaction, cash_real_expected, order_ids, order_count, statement_ids, failed_pickings, picking_count, picking_ids, rescue, move_id, payment_method_ids, total_payments_amount, is_in_company_currency, update_stock_at_closing, move_id_old, orderline_checked, crm_team_id, required_reinstall_cache, backup_session, pos_branch_id, employee_id, lock_state, order_log_ids, opened_at, opened_uid, last_login_time, login_number, state, cash_opening_balance, cash_closing_balance, is_closing_wizard, pos_config_cashbox_lines_ids, pos_config_cashbox_clsosing_line_ids, cash_register_balance_end_real, cashier_id, total_invoice_count, total_faktur_count, log_cashier_ids, is_multi_session, order_with_receivable_invoice_ids, pos_config_uuid, pos_session_cashbox_wizard_ids, cash_management_ids, cash_history_ids, gain_loss_move_id, is_pos_config_save_order_history_local, scheduler_invoice_finish_date, void_ids, bank_register_total_entry_encoding, cash_register_total_entry_encoding, bank_closing_balance, pos_session_bank_cashbox_wizard_ids, to_recompute, is_invoice_recreate, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 19, char: 6, datetime: 8, integer: 11, boolean: 18, monetary: 12, one2many: 17, many2many: 3, float: 1, selection: 4, date: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.session", "table_name": ""}
+{"text": "Can you explain the purpose of sale.commission.excel.report?", "response": "The sale.commission.excel.report model represents Sale Commission Excel Report in the ERP system. It contains 9 fields and is used to manage sale commission excel report data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.commission.excel.report", "table_name": ""}
+{"text": "What is the orderline.orderline model?", "response": "The orderline.orderline model represents Sale Blanket Order line in the ERP system. It contains 25 fields and is used to manage sale blanket order line data. Key fields include: reverse_id, product_id, name, quantity, remaining_quantity, product_uom, price_unit, tax_id, price_subtotal, ordered_qty, delivered_qty, qty_invoiced, undelivered_qty, sequence, sequence2, company_id, analytic_tag_ids, price_tax, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "orderline.orderline", "table_name": ""}
+{"text": "What business logic is in apps.installation.activity.log?", "response": "To use the apps.installation.activity.log model, you need to provide values for required fields: none. Readonly fields: activity_date, module_name, technical_name, latest_version, activity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "apps.installation.activity.log", "table_name": ""}
+{"text": "What operations can I perform on report.accounting_pdf_reports.report_partnerledger?", "response": "To use the report.accounting_pdf_reports.report_partnerledger model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.accounting_pdf_reports.report_partnerledger", "table_name": ""}
+{"text": "What data can be stored in account_edi_proxy_client.user?", "response": "The account_edi_proxy_client.user model has 15 fields: active, id_client, company_id, edi_format_id, edi_format_code, edi_identification, private_key, refresh_token, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, char: 5, many2one: 4, binary: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account_edi_proxy_client.user", "table_name": ""}
+{"text": "Show me the relational structure of sh.sale.report.salesperson.wizard.", "response": "The sh.sale.report.salesperson.wizard model has 6 relational fields: user_ids -> res.users; company_ids -> res.company; company_id -> res.company; user_order_dic -> user.order.dic; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.sale.report.salesperson.wizard", "table_name": ""}
+{"text": "What does the pos.promotion.tebus.murah model represent?", "response": "The pos.promotion.tebus.murah model represents Promotion for Tebus Murah in the ERP system. It contains 13 fields and is used to manage promotion for tebus murah data. Key fields include: active, promotion_id, product_id, price, quantity, product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.promotion.tebus.murah", "table_name": ""}
+{"text": "Show me the fields of mail.blacklist.remove.", "response": "The mail.blacklist.remove model has 9 fields: email, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.blacklist.remove", "table_name": ""}
+{"text": "How does res.users.tag relate to other models?", "response": "The res.users.tag model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.users.tag", "table_name": ""}
+{"text": "How is setu.inventory.overstock.report used in the system?", "response": "The setu.inventory.overstock.report model represents \n        Inventory Overtsock Report / Excess Inventory Report\n        ===================================================================\n        Excess Inventory Report is used to capture all products which are having overstock than needed.  \n        \n        Report will be downloaded in excel file, following data will be exported to excel file.\n        -   Company\n        -   Warehouse\n        -   Product\n        -   Product Category \n        -   Warehouse \n        -   Sales Qty,\n        -   Average Daily Sale\n        -   Available Stock\n        -   Outgoing Stock\n        -   Incoming Stock\n        -   Forecasted Stock\n        -   Demanded Qty\n        -   Coverage Days\n        -   Overstock Qty\n        -   Overstock Value\n        -   Last Purchase Date\n        -   Last Purchase Qty\n        -   Last Purchase Price\n        -   Purchase Currency\n        -   Vendor Name\n        -   Warehouse Wise Overstock Qty Percentage\n        -   Warehouse Wise Overstock Value Percentage\n        -   Company Wise Overstock Qty Percentage\n        -   Company Wise Overstock Value Percentage\n     in the ERP system. It contains 16 fields and is used to manage \n        inventory overtsock report / excess inventory report\n        ===================================================================\n        excess inventory report is used to capture all products which are having overstock than needed.  \n        \n        report will be downloaded in excel file, following data will be exported to excel file.\n        -   company\n        -   warehouse\n        -   product\n        -   product category \n        -   warehouse \n        -   sales qty,\n        -   average daily sale\n        -   available stock\n        -   outgoing stock\n        -   incoming stock\n        -   forecasted stock\n        -   demanded qty\n        -   coverage days\n        -   overstock qty\n        -   overstock value\n        -   last purchase date\n        -   last purchase qty\n        -   last purchase price\n        -   purchase currency\n        -   vendor name\n        -   warehouse wise overstock qty percentage\n        -   warehouse wise overstock value percentage\n        -   company wise overstock qty percentage\n        -   company wise overstock value percentage\n     data. Key fields include: advance_stock_days, stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "setu.inventory.overstock.report", "table_name": ""}
+{"text": "Show me the relational structure of purchase.change.request.", "response": "The purchase.change.request model has 13 relational fields: requested_id -> res.users; budget_std_id -> budget.purchase; company_id -> res.company; branch_id -> res.branch; pur_change_req_ids -> purchase.change.request.line; budget_line -> budget.change.req.line; approval_matrix -> approval.matrix.accounting; approved_matrix_ids -> approval.matrix.accounting.lines; approval_matrix_line_id -> approval.matrix.accounting.lines; currency_id -> res.currency; request_partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.change.request", "table_name": ""}
+{"text": "What are the relationships in pos.promotion.special.category?", "response": "The pos.promotion.special.category model has 7 relational fields: category_id -> pos.category; product_ids -> product.product; category_ids -> pos.category; promotion_id -> pos.promotion; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, category_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.promotion.special.category", "table_name": ""}
+{"text": "What business logic is in product.attribute.custom.value?", "response": "To use the product.attribute.custom.value model, you need to provide values for required fields: custom_product_template_attribute_value_id, sale_order_line_id. Readonly fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.attribute.custom.value", "table_name": ""}
+{"text": "How is bi.product.pack used in the system?", "response": "The bi.product.pack model represents bi.product.pack in the ERP system. It contains 14 fields and is used to manage bi.product.pack data. Key fields include: product_id, qty_uom, bi_product_template, bi_image, price, uom_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "bi.product.pack", "table_name": ""}
+{"text": "What foreign keys exist in ir.qweb.field.relative?", "response": "The ir.qweb.field.relative model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb.field.relative", "table_name": ""}
+{"text": "How to create records in invoice.printout.editor?", "response": "To use the invoice.printout.editor model, you need to provide values for required fields: none. Readonly fields: name, preview, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "invoice.printout.editor", "table_name": ""}
+{"text": "What are the technical details of stock.scheduler.compute?", "response": "The stock.scheduler.compute model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.scheduler.compute", "table_name": ""}
+{"text": "Tell me about the account.financial.year.op model.", "response": "The account.financial.year.op model represents Opening Balance of Financial Year in the ERP system. It contains 12 fields and is used to manage opening balance of financial year data. Key fields include: company_id, opening_move_posted, opening_date, fiscalyear_last_day, fiscalyear_last_month, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.financial.year.op", "table_name": ""}
+{"text": "Describe the implementation of customer.degree.trust.", "response": "The customer.degree.trust model is defined in module: equip3_sale_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "customer.degree.trust", "table_name": ""}
+{"text": "Tell me about the pos.gift.card.exchange.history model.", "response": "The pos.gift.card.exchange.history model represents Used to Store Gift Card Exchange History. in the ERP system. It contains 10 fields and is used to manage used to store gift card exchange history. data. Key fields include: customer_id, old_card_no, new_card_no, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.gift.card.exchange.history", "table_name": ""}
+{"text": "Show me the relational structure of do.approval.matrix.", "response": "The do.approval.matrix model has 17 relational fields: company_id -> res.company; branch_id -> res.branch; warehouse_id -> stock.warehouse; create_uid -> res.users; do_approval_matrix_line_ids -> do.approval_matrix_line; do_approval_matrix_details_id -> do.approval_matrix_detail; location_child_ids -> stock.location; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; write_uid -> res.users. Many2many fields: location_child_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "do.approval.matrix", "table_name": ""}
+{"text": "What fields does crm.lead.salesperson.lines have?", "response": "The crm.lead.salesperson.lines model has 11 fields: salesperson_id, weightage, status, lead_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 1, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.lead.salesperson.lines", "table_name": ""}
+{"text": "What models are connected to kpi.help?", "response": "The kpi.help model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kpi.help", "table_name": ""}
+{"text": "Tell me about the purchase.quotation.report model.", "response": "The purchase.quotation.report model represents Puechase Quotation Report in the ERP system. It contains 8 fields and is used to manage puechase quotation report data. Key fields include: purchase_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.quotation.report", "table_name": ""}
+{"text": "Can you explain the purpose of setu.inventory.overstock.bi.report?", "response": "The setu.inventory.overstock.bi.report model represents setu.inventory.overstock.bi.report in the ERP system. It contains 31 fields and is used to manage setu.inventory.overstock.bi.report data. Key fields include: product_id, product_category_id, warehouse_id, company_id, sales, ads, qty_available, incoming, outgoing, forecasted_stock, demanded_qty, coverage_days, overstock_qty, overstock_value, wh_overstock_qty_per, wh_overstock_value_per, turnover_ratio, stock_movement, last_purchase_date, last_purchase_qty, last_purchase_price, currency_name, vendor_name, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "setu.inventory.overstock.bi.report", "table_name": ""}
+{"text": "What are the relationships in purchase.report?", "response": "The purchase.report model has 16 relational fields: product_id -> product.product; partner_id -> res.partner; product_uom -> uom.uom; company_id -> res.company; currency_id -> res.currency; user_id -> res.users; category_id -> product.category; product_tmpl_id -> product.template; country_id -> res.country; fiscal_position_id -> account.fiscal.position; account_analytic_id -> account.analytic.account; commercial_partner_id -> res.partner; order_id -> purchase.order; team_id -> dev.purchase.team; picking_type_id -> stock.warehouse; branch_id -> res.branch. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.report", "table_name": ""}
+{"text": "What data can be stored in account.analytic.line?", "response": "The account.analytic.line model has 61 fields: product_uom_category_id, tag_ids, currency_id, general_account_id, code, task_id, project_id, user_id, employee_id, department_id, encoding_uom_id, timesheet_invoice_type, timesheet_invoice_id, non_allow_billable, so_line, name, unit_amount, product_uom_id, account_id, partner_id, company_id, group_id, product_id, ref, move_id, date, amount, is_so_line_edited, branch_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 24, many2many: 3, char: 7, selection: 3, boolean: 7, float: 1, date: 3, monetary: 1, one2many: 4, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.analytic.line", "table_name": ""}
+{"text": "What is the crm.lead.salesperson.lines model?", "response": "The crm.lead.salesperson.lines model represents Salesperson in the ERP system. It contains 11 fields and is used to manage salesperson data. Key fields include: salesperson_id, weightage, status, lead_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.lead.salesperson.lines", "table_name": ""}
+{"text": "Which fields in purchase.flow.asset are computed?", "response": "The purchase.flow.asset model is defined in module: equip3_purchase_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.flow.asset", "table_name": ""}
+{"text": "List all fields in the sh.stock.move.pass.fail model.", "response": "The sh.stock.move.pass.fail model has 11 fields: product_id, sh_message, sh_quality_point_id, picking_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, text: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.stock.move.pass.fail", "table_name": ""}
+{"text": "How is account.pettycash implemented technically?", "response": "The account.pettycash model is defined in module: equip3_accounting_pettycash. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.pettycash", "table_name": ""}
+{"text": "How to create records in report.accounting_pdf_reports.report_financial?", "response": "To use the report.accounting_pdf_reports.report_financial model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.accounting_pdf_reports.report_financial", "table_name": ""}
+{"text": "What are the technical details of coupon.coupon?", "response": "The coupon.coupon model is defined in module: coupon. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "coupon.coupon", "table_name": ""}
+{"text": "What models are connected to report.stock.quantity?", "response": "The report.stock.quantity model has 5 relational fields: product_tmpl_id -> product.template; product_id -> product.product; move_ids -> stock.move; company_id -> res.company; warehouse_id -> stock.warehouse. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.stock.quantity", "table_name": ""}
+{"text": "What are the available fields for repair.order.make_invoice?", "response": "The repair.order.make_invoice model has 8 fields: group, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "repair.order.make_invoice", "table_name": ""}
+{"text": "Which fields in pmps.adv.wizard are computed?", "response": "The pmps.adv.wizard model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pmps.adv.wizard", "table_name": ""}
+{"text": "What are the technical details of limit.approval.matrix?", "response": "The limit.approval.matrix model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "limit.approval.matrix", "table_name": ""}
+{"text": "What methods are available in internal.transfer?", "response": "The internal.transfer model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "internal.transfer", "table_name": ""}
+{"text": "What is the mr_line.internal_transfer model?", "response": "The mr_line.internal_transfer model represents mr_line.internal_transfer in the ERP system. It contains 8 fields and is used to manage mr_line.internal_transfer data. Key fields include: ir_wizard_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mr_line.internal_transfer", "table_name": ""}
+{"text": "What foreign keys exist in queue.job?", "response": "The queue.job model has 12 relational fields: user_id -> res.users; company_id -> res.company; job_function_id -> queue.job.function; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "queue.job", "table_name": ""}
+{"text": "Tell me about the ks_dashboard_item.multiplier model.", "response": "The ks_dashboard_item.multiplier model represents Dashboard Ninja Items Multiplier Lines in the ERP system. It contains 11 fields and is used to manage dashboard ninja items multiplier lines data. Key fields include: ks_dashboard_item_id, ks_model_id, ks_multiplier_value, ks_multiplier_fields, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks_dashboard_item.multiplier", "table_name": ""}
+{"text": "How does pos.gift.card.type relate to other models?", "response": "The pos.gift.card.type model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.gift.card.type", "table_name": ""}
+{"text": "How does account.pettycash.fund.change relate to other models?", "response": "The account.pettycash.fund.change model has 7 relational fields: fund -> account.pettycash; custodian -> res.users; payable_account -> account.account; receivable_account -> account.account; move -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.pettycash.fund.change", "table_name": ""}
+{"text": "How to create records in account.internal.transfer?", "response": "To use the account.internal.transfer model, you need to provide values for required fields: none. Readonly fields: currency_id, create_date, create_uid, filter_branch_ids, approval_matrix_id, is_internal_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, analytic_group_ids, name, 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, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.internal.transfer", "table_name": ""}
+{"text": "How is ks_ninja_dashboard.item_action implemented technically?", "response": "The ks_ninja_dashboard.item_action model is defined in module: ks_dashboard_ninja. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks_ninja_dashboard.item_action", "table_name": ""}
+{"text": "What are the relationships in crm.merge.opportunity?", "response": "The crm.merge.opportunity model has 5 relational fields: opportunity_ids -> crm.lead; user_id -> res.users; team_id -> crm.team; create_uid -> res.users; write_uid -> res.users. Many2many fields: opportunity_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.merge.opportunity", "table_name": ""}
+{"text": "What modules define kpi.measure.item?", "response": "The kpi.measure.item model is defined in module: kpi_scorecard. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kpi.measure.item", "table_name": ""}
+{"text": "What are common use cases for stock.location?", "response": "To use the stock.location model, you need to provide values for required fields: name, usage, capacity_type. Readonly fields: complete_name, warehouse_id, is_expired_stock_location, occupied_unit, to_trigger_occupied_unit, is_putaway_max_capacity, occupied_weight, occupied_volume, occupied_length, occupied_width, occupied_height, occupied_percent, location_complete_name, warehouse_delivery_steps, location_display_name, quantity_validate, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.location", "table_name": ""}
+{"text": "How does debt.collection.report relate to other models?", "response": "The debt.collection.report model has 7 relational fields: partner_ids -> res.partner; user_ids -> res.users; journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, user_ids, journal_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "debt.collection.report", "table_name": ""}
+{"text": "Describe the stock.move model in Odoo.", "response": "The stock.move model represents Stock Move in the ERP system. It contains 237 fields and is used to manage stock move data. Key fields include: name, sequence, priority, create_date, date, date_deadline, company_id, description_picking, product_qty, product_uom_qty, product_uom, product_uom_category_id, product_tmpl_id, location_id, location_dest_id, partner_id, move_dest_ids, move_orig_ids, picking_partner_id, note, state, price_unit, backorder_id, origin, procure_method, scrapped, scrap_ids, group_id, rule_id, propagate_cancel, delay_alert_date, picking_type_id, inventory_id, move_line_ids, move_line_nosuggest_ids, origin_returned_move_id, returned_move_ids, availability, restrict_partner_id, route_ids, warehouse_id, has_tracking, show_operations, show_details_visible, show_reserved_availability, additional, is_locked, is_initial_demand_editable, is_quantity_done_editable, reference, has_move_lines, package_level_id, picking_type_entire_packs, display_assign_serial, next_serial_count, orderpoint_id, forecast_availability, forecast_expected_date, lot_ids, created_production_id, production_id, raw_material_production_id, unbuild_id, consume_unbuild_id, allowed_operation_ids, operation_id, workorder_id, bom_line_id, byproduct_id, unit_factor, is_done, order_finished_lot_ids, should_consume_qty, use_expiration_date, to_refund, account_move_ids, stock_valuation_layer_ids, is_reconstruct_svl, scrap_return_move_id, purchase_line_id, created_purchase_line_id, sh_quality_point, sh_quality_point_id, sh_last_qc_date, sh_last_qc_state, number_of_test, created_purchase_request_line_id, purchase_request_allocation_ids, purchase_request_ids, requisition_line_ids, sale_line_id, branch_id, weight, product_description, qty_pack, is_pack, repair_id, sh_stock_move_barcode_mobile, sh_stock_move_bm_is_cont_scan, length, width, height, product_id, is_adjustable_picking, package_measure_selection, picking_state, is_existing_package, move_package_id, filter_move_package_ids, mr_line_id, move_line_sequence, serial_no, export_file, export_name, next_serial, next_serial_not_autogenerate, next_lot_not_autogenerate, is_import, is_record_confirm, product_type, is_serial_number, next_lot, qty_per_lot, is_autogenerate, picking_code, is_product_service_operation, is_product_service_operation_delivery, is_product_service_operation_receiving, serial, initial_demand, move_progress, analytic_account_group_ids, remaining, fulfillment, current_qty, scheduled_date, responsible, late_time, late_time_hours, process_status, process_time, process_time_hours, package_type, qty_in_pack, packaging_ids, package_quant_ids, measure_ids, product_id_domain, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, created_assembly_id, assembly_finished_id, assembly_component_id, assembly_unit_factor, assembly_should_consume_qty, assembly_product_free_qty, description, created_kitchen_id, kitchen_finished_id, kitchen_component_id, kitchen_unit_factor, kitchen_should_consume_qty, kitchen_product_free_qty, asp_asm_stock_id, bom_product_uom_qty, sub_total, finish_good_rework_id, type_product_bom, finish_good_rework_finished_id, finish_good_rework_created_kitchen_id, finish_good_rework_by_product_id, assembly_record_type, assembly_confirm_date, assembly_product_id, assembly_bom_id, assembly_svl_value, assembly_difference, exp_date, qty_bundle, id_bundle, package_barcode, kitchen_confirm_date, kitchen_product_id, kitchen_bom_id, kitchen_svl_value, kitchen_difference, product_warehouse, product_location, expired_date, product_barcode, vendor_id, state_expired, state_check, picking_type_code, reserved_by_id, reserved_availability, is_reserved, picking_id, origin_src_location, origin_dest_location, picking_reference, is_transit, date_done, return_reason, action, is_transfer_in, is_transfer_out, quantity_done, volume, movement_type, cost, combo_item_id, pos_branch_id, pos_order_line_id, so_antar_badan, po_antar_badan, sale_order_id, purchase_order_id, date_done_real, taxes_id, price_subtotal, price_tax, price_total, price_untaxed_amount, discount_amount, price_discount, currency_id, returned_qty, remaining_checked_qty, id, display_name, create_uid, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.move", "table_name": ""}
+{"text": "Can you explain the purpose of sh.qc.measurement.line?", "response": "The sh.qc.measurement.line model represents Quality Measurement Line in the ERP system. It contains 14 fields and is used to manage quality measurement line data. Key fields include: measurement_id, product_id, sh_measure, sh_text, state, quality_point_id, type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.qc.measurement.line", "table_name": ""}
+{"text": "What models are connected to opening.balance.line?", "response": "The opening.balance.line model has 7 relational fields: move_id -> opening.balance; company_id -> res.company; account_id -> account.account; partner_id -> res.partner; company_currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "opening.balance.line", "table_name": ""}
+{"text": "How to query auth_totp.wizard data?", "response": "To use the auth_totp.wizard model, you need to provide values for required fields: user_id, secret. Readonly fields: user_id, secret, url, qrcode, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "auth_totp.wizard", "table_name": ""}
+{"text": "How is sh.top.purchasing.excel.extended used in the system?", "response": "The sh.top.purchasing.excel.extended model represents Excel Extended in the ERP system. It contains 9 fields and is used to manage excel extended data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.top.purchasing.excel.extended", "table_name": ""}
+{"text": "Describe the implementation of list.top.product.compare.", "response": "The list.top.product.compare model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "list.top.product.compare", "table_name": ""}
+{"text": "Describe the many2many relations for mrp.labor.group.", "response": "The mrp.labor.group model has 6 relational fields: head_id -> hr.employee; labor_ids -> hr.employee; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: labor_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.labor.group", "table_name": ""}
+{"text": "List all fields in the res.config.installer model.", "response": "The res.config.installer model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.config.installer", "table_name": ""}
+{"text": "How to query report.reordering.view data?", "response": "To use the report.reordering.view model, you need to provide values for required fields: none. Readonly fields: on_hand_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.reordering.view", "table_name": ""}
+{"text": "Tell me about the account.debt.collection model.", "response": "The account.debt.collection model represents Debt Collection in the ERP system. It contains 51 fields and is used to manage debt collection data. Key fields include: name, partner_id, date, person_in_charge, currency_id, amount, start_date, end_date, deadline_date, branch_id, create_uid, create_date, line_debt_collection, state, is_pic, 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, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.debt.collection", "table_name": ""}
+{"text": "How to create records in project.task?", "response": "To use the project.task model, you need to provide values for required fields: name, kanban_state, company_id. Readonly fields: kanban_state_label, create_date, write_date, date_assign, date_last_stage_update, subtask_planned_hours, partner_is_company, commercial_partner_id, ribbon_message, manager_id, user_email, attachment_ids, legend_blocked, legend_done, legend_normal, is_closed, subtask_project_id, allow_subtasks, subtask_count, project_privacy_visibility, working_hours_open, working_hours_close, working_days_open, working_days_close, allow_recurring_tasks, recurring_count, recurrence_message, repeat_show_dow, repeat_show_day, repeat_show_week, repeat_show_month, analytic_account_active, allow_timesheets, remaining_hours, effective_hours, total_hours_spent, progress, overtime, subtask_effective_hours, encode_uom_in_days, project_sale_order_id, invoice_count, task_to_invoice, analytic_account_id, bill_type, pricing_type, is_project_map_empty, has_multi_sol, allow_billable, display_create_order, remaining_hours_so, remaining_hours_available, 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, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, access_url, access_warning, id, display_name, create_uid, write_uid, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.task", "table_name": ""}
+{"text": "How is report.sh_inventory_mrp_qc.quality_alert_doc implemented technically?", "response": "The report.sh_inventory_mrp_qc.quality_alert_doc model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_inventory_mrp_qc.quality_alert_doc", "table_name": ""}
+{"text": "What methods are available in vendor.pricelist.approval.matrix?", "response": "The vendor.pricelist.approval.matrix model is defined in module: equip3_purchase_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "vendor.pricelist.approval.matrix", "table_name": ""}
+{"text": "What data can be stored in pos.gift.card.recharge?", "response": "The pos.gift.card.recharge model has 12 fields: card_id, customer_id, recharge_date, user_id, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.gift.card.recharge", "table_name": ""}
+{"text": "Describe the pos.cache.database model in Odoo.", "response": "The pos.cache.database model represents Management POS database in the ERP system. It contains 10 fields and is used to manage management pos database data. Key fields include: res_id, res_model, deleted, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.cache.database", "table_name": ""}
+{"text": "What foreign keys exist in asset.asset.revalue?", "response": "The asset.asset.revalue model has 8 relational fields: asset_id -> account.asset.asset; journal_id -> account.journal; user_id -> res.users; company_id -> res.company; company_currency_id -> res.currency; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "asset.asset.revalue", "table_name": ""}
+{"text": "Describe the many2many relations for acrux.chat.connector.", "response": "The acrux.chat.connector model has 6 relational fields: company_id -> res.company; team_id -> crm.team; sale_report_id -> ir.actions.report; qc_template_ids -> qiscus.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "acrux.chat.connector", "table_name": ""}
+{"text": "What are the relationships in utm.source?", "response": "The utm.source model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "utm.source", "table_name": ""}
+{"text": "Show me the fields of approval.matrix.blanket.order.line.", "response": "The approval.matrix.blanket.order.line model has 20 fields: sequence, user_ids, minimum_approver, approval_matrix_blanket_order, bo_matrix_id, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, approver_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 4, many2many: 2, many2one: 5, text: 1, datetime: 4, char: 2, boolean: 1, selection: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.blanket.order.line", "table_name": ""}
+{"text": "What are common use cases for weight.scale.barcode.format.line?", "response": "To use the weight.scale.barcode.format.line model, you need to provide values for required fields: digit, data. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "weight.scale.barcode.format.line", "table_name": ""}
+{"text": "List all fields in the base_import.tests.models.o2m model.", "response": "The base_import.tests.models.o2m model has 9 fields: name, value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, one2many: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.o2m", "table_name": ""}
+{"text": "List all fields in the sh.send.notification model.", "response": "The sh.send.notification model has 16 fields: name, title, message, redirect_url, logo, state, message_to, specific_ids, log_historys, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 2, char: 3, binary: 1, selection: 2, many2many: 1, one2many: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.send.notification", "table_name": ""}
+{"text": "What models are connected to cust.credit.limit.data.line?", "response": "The cust.credit.limit.data.line model has 4 relational fields: cust_credit_id -> cust.credit.limit.data; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "cust.credit.limit.data.line", "table_name": ""}
+{"text": "What does the sale.advance.payment.inv model represent?", "response": "The sale.advance.payment.inv model represents Sales Advance Payment Invoice in the ERP system. It contains 20 fields and is used to manage sales advance payment invoice data. Key fields include: advance_payment_method, deduct_down_payments, has_down_payments, product_id, count, amount, currency_id, fixed_amount, deposit_account_id, deposit_taxes_id, date_start_invoice_timesheet, date_end_invoice_timesheet, invoicing_timesheet_enabled, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.advance.payment.inv", "table_name": ""}
+{"text": "How is receipt.payment.line.debit used in the system?", "response": "The receipt.payment.line.debit model represents   in the ERP system. It contains 20 fields and is used to manage   data. Key fields include: line_id, currency_id, invoice_id, account_id, invoice_date, invoice_date_due, original_amount, base_amount, original_unreconcile, base_unreconcile, is_full_reconcile, amount, payment_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "receipt.payment.line.debit", "table_name": ""}
+{"text": "What methods are available in account.user.reminder.lines?", "response": "The account.user.reminder.lines model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.user.reminder.lines", "table_name": ""}
+{"text": "Show me the fields of account.tour.upload.bill.", "response": "The account.tour.upload.bill model has 41 fields: composer_id, selection, sample_bill_preview, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, subject, body, parent_id, template_id, attachment_ids, layout, add_sign, email_from, author_id, composition_mode, model, res_id, record_name, use_active_domain, active_domain, message_type, subtype_id, mail_activity_type_id, reply_to, no_auto_thread, is_log, partner_ids, notify, auto_delete, auto_delete_message, mail_server_id, mass_mailing_id, campaign_id, mass_mailing_name, mailing_list_ids, is_wp. Field types distribution: many2one: 11, selection: 3, binary: 1, integer: 2, char: 8, datetime: 3, html: 1, many2many: 3, boolean: 8, text: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.tour.upload.bill", "table_name": ""}
+{"text": "How is pos.sync.session.order.line implemented technically?", "response": "The pos.sync.session.order.line model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.sync.session.order.line", "table_name": ""}
+{"text": "How is res.groups used in the system?", "response": "The res.groups model represents Access Groups in the ERP system. It contains 20 fields and is used to manage access groups data. Key fields include: name, users, model_access, rule_groups, menu_access, view_access, comment, category_id, color, full_name, share, implied_ids, trans_implied_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.groups", "table_name": ""}
+{"text": "What does the account.user.reminder model represent?", "response": "The account.user.reminder model represents Account USer Reminder in the ERP system. It contains 12 fields and is used to manage account user reminder data. Key fields include: name, company_id, branch_id, account_line_ids, reminder_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.user.reminder", "table_name": ""}
+{"text": "Show me the fields of setu.inventory.fsn.xyz.analysis.report.", "response": "The setu.inventory.fsn.xyz.analysis.report model has 17 fields: stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, stock_movement_type, inventory_analysis_type, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, date: 2, many2many: 4, selection: 2, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.fsn.xyz.analysis.report", "table_name": ""}
+{"text": "What methods are available in ir.actions.todo?", "response": "The ir.actions.todo model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.actions.todo", "table_name": ""}
+{"text": "Describe the many2many relations for gamification.goal.", "response": "The gamification.goal model has 6 relational fields: definition_id -> gamification.goal.definition; user_id -> res.users; line_id -> gamification.challenge.line; challenge_id -> gamification.challenge; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "gamification.goal", "table_name": ""}
+{"text": "Describe the many2many relations for qiscus.wa.template.content.", "response": "The qiscus.wa.template.content model has 3 relational fields: template_id -> qiscus.wa.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "qiscus.wa.template.content", "table_name": ""}
+{"text": "What are common use cases for expiring.product.calendar?", "response": "To use the expiring.product.calendar 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "expiring.product.calendar", "table_name": ""}
+{"text": "Tell me about the pos.global.discount model.", "response": "The pos.global.discount model represents Management Global Discount in the ERP system. It contains 14 fields and is used to manage management global discount data. Key fields include: name, amount, product_id, reason, type, branch_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.global.discount", "table_name": ""}
+{"text": "How is export.product.csv implemented technically?", "response": "The export.product.csv model is defined in module: equip3_accounting_efaktur. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "export.product.csv", "table_name": ""}
+{"text": "Describe the implementation of calendar.alarm.", "response": "The calendar.alarm model is defined in module: calendar. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "calendar.alarm", "table_name": ""}
+{"text": "Which fields in budget.change.req.wizard are computed?", "response": "The budget.change.req.wizard model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "budget.change.req.wizard", "table_name": ""}
+{"text": "Can you explain the purpose of stock.scheduler.compute?", "response": "The stock.scheduler.compute model represents Run Scheduler Manually in the ERP system. It contains 7 fields and is used to manage run scheduler manually data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.scheduler.compute", "table_name": ""}
+{"text": "What fields does create.purchase.request.direct.lines have?", "response": "The create.purchase.request.direct.lines model has 17 fields: wiz_id, line_id, request_id, product_id, name, product_qty, product_uom_id, destination_location_id, rem_qty, keep_description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, char: 2, float: 2, boolean: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "create.purchase.request.direct.lines", "table_name": ""}
+{"text": "What data can be stored in purchase.order.line.wizard?", "response": "The purchase.order.line.wizard model has 14 fields: name, wizard_id, product_id, product_qty, price_unit, product_uom, price_subtotal, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2one: 5, float: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.order.line.wizard", "table_name": ""}
+{"text": "Show me the relational structure of sh.purchase.analysis.xls.", "response": "The sh.purchase.analysis.xls model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.analysis.xls", "table_name": ""}
+{"text": "What modules define sh.mpo.merge.purchase.order.wizard?", "response": "The sh.mpo.merge.purchase.order.wizard model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.mpo.merge.purchase.order.wizard", "table_name": ""}
+{"text": "How is base_import.tests.models.float used in the system?", "response": "The base_import.tests.models.float model represents Tests: Base Import Model Float in the ERP system. It contains 10 fields and is used to manage tests: base import model float data. Key fields include: value, value2, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.float", "table_name": ""}
+{"text": "Show me the fields of bve.view.", "response": "The bve.view model has 22 fields: name, model_name, note, state, data, line_ids, field_ids, relation_ids, action_id, view_id, group_ids, user_ids, query, over_condition, er_diagram_image, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, text: 3, selection: 1, one2many: 3, many2one: 4, many2many: 2, binary: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "bve.view", "table_name": ""}
+{"text": "What are the technical details of res.partner.rfm.segment.history?", "response": "The res.partner.rfm.segment.history model is defined in module: setu_rfm_analysis. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.partner.rfm.segment.history", "table_name": ""}
+{"text": "What methods are available in mr_line.internal_transfer_line?", "response": "The mr_line.internal_transfer_line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mr_line.internal_transfer_line", "table_name": ""}
+{"text": "What foreign keys exist in account.loan.pay.amount?", "response": "The account.loan.pay.amount model has 4 relational fields: loan_id -> account.loan; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.loan.pay.amount", "table_name": ""}
+{"text": "What are the available fields for approval.matrix.sale.reject?", "response": "The approval.matrix.sale.reject model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.sale.reject", "table_name": ""}
+{"text": "Can you explain the purpose of ir.exports.line?", "response": "The ir.exports.line model represents Exports Line in the ERP system. It contains 9 fields and is used to manage exports line data. Key fields include: name, export_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.exports.line", "table_name": ""}
+{"text": "How to query order.driver.message data?", "response": "To use the order.driver.message model, you need to provide values for required fields: none. Readonly fields: order_id, message, send_to_driver, partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "order.driver.message", "table_name": ""}
+{"text": "What operations can I perform on res.country?", "response": "To use the res.country model, you need to provide values for required fields: name. Readonly fields: image_url, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.country", "table_name": ""}
+{"text": "What are the available fields for stock.backorder.confirmation?", "response": "The stock.backorder.confirmation model has 10 fields: pick_ids, show_transfers, backorder_confirmation_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, boolean: 1, one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.backorder.confirmation", "table_name": ""}
+{"text": "What foreign keys exist in group.card?", "response": "The group.card model has 12 relational fields: company_id -> res.company; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "group.card", "table_name": ""}
+{"text": "What methods are available in report.equip3_pos_report.report_sales_summary?", "response": "The report.equip3_pos_report.report_sales_summary model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_pos_report.report_sales_summary", "table_name": ""}
+{"text": "What fields does mail.channel have?", "response": "The mail.channel model has 71 fields: name, active, is_chat, description, uuid, email_send, channel_last_seen_partner_ids, channel_partner_ids, channel_message_ids, is_member, public, group_public_id, group_ids, image_128, is_subscribed, moderation, moderator_ids, is_moderator, moderation_ids, moderation_count, moderation_notify, moderation_notify_msg, moderation_guidelines, moderation_guidelines_msg, subscription_department_ids, rating_ids, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, anonymous_name, channel_type, livechat_active, livechat_channel_id, livechat_operator_id, country_id, livechat_visitor_id, alias_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, alias_name, alias_model_id, alias_user_id, alias_defaults, alias_force_thread_id, alias_domain, alias_parent_model_id, alias_parent_thread_id, alias_bounced_content, alias_contact. Field types distribution: char: 6, boolean: 15, text: 5, one2many: 6, many2many: 7, selection: 3, many2one: 12, binary: 2, integer: 9, float: 2, datetime: 3, html: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.channel", "table_name": ""}
+{"text": "Show me the relational structure of sh.purchase.details.report.wizard.", "response": "The sh.purchase.details.report.wizard model has 4 relational fields: company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids, branch_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.details.report.wizard", "table_name": ""}
+{"text": "What operations can I perform on untaken.stock.line?", "response": "To use the untaken.stock.line model, you need to provide values for required fields: none. Readonly fields: quantity, product_unit_measure, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "untaken.stock.line", "table_name": ""}
+{"text": "Describe the field structure of invoice.template.header.", "response": "The invoice.template.header model has 10 fields: template_id, field_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "invoice.template.header", "table_name": ""}
+{"text": "What are the technical details of pos.backup.orders?", "response": "The pos.backup.orders model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.backup.orders", "table_name": ""}
+{"text": "How is res.users.apikeys.description used in the system?", "response": "The res.users.apikeys.description model represents res.users.apikeys.description in the ERP system. It contains 8 fields and is used to manage res.users.apikeys.description data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.users.apikeys.description", "table_name": ""}
+{"text": "Show me the fields of account.setup.bank.manual.config.", "response": "The account.setup.bank.manual.config model has 30 fields: res_partner_bank_id, new_journal_name, linked_journal_id, bank_bic, num_journals_without_account, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, active, acc_type, acc_number, sanitized_acc_number, acc_holder_name, partner_id, bank_id, bank_name, sequence, currency_id, company_id, journal_id, aba_routing, acc_holder_email, acc_holder_type, acc_holder_resident, acc_holder_address. Field types distribution: many2one: 9, char: 10, integer: 3, datetime: 3, boolean: 1, selection: 3, one2many: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.setup.bank.manual.config", "table_name": ""}
+{"text": "What methods are available in calendar.alarm_manager?", "response": "The calendar.alarm_manager model is defined in module: calendar. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "calendar.alarm_manager", "table_name": ""}
+{"text": "Describe the field structure of account.fiscal.position.template.", "response": "The account.fiscal.position.template model has 20 fields: sequence, chart_template_id, account_ids, tax_ids, auto_apply, vat_required, country_id, country_group_id, state_ids, zip_from, zip_to, name, note, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 5, one2many: 2, boolean: 2, many2many: 1, char: 4, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.fiscal.position.template", "table_name": ""}
+{"text": "Describe the many2many relations for base_import.tests.models.char.readonly.", "response": "The base_import.tests.models.char.readonly model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.char.readonly", "table_name": ""}
+{"text": "How to create records in pos.generate.efaktur.invoice?", "response": "To use the pos.generate.efaktur.invoice model, you need to provide values for required fields: none. Readonly fields: l10n_id_tax_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.generate.efaktur.invoice", "table_name": ""}
+{"text": "What are the relationships in account.payment.term.line?", "response": "The account.payment.term.line model has 3 relational fields: payment_id -> account.payment.term; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.payment.term.line", "table_name": ""}
+{"text": "How does snailmail.confirm.invoice relate to other models?", "response": "The snailmail.confirm.invoice model has 3 relational fields: invoice_send_id -> account.invoice.send; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "snailmail.confirm.invoice", "table_name": ""}
+{"text": "Tell me about the crm.tag model.", "response": "The crm.tag model represents CRM Tag in the ERP system. It contains 10 fields and is used to manage crm tag data. Key fields include: name, color, is_external_link, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.tag", "table_name": ""}
+{"text": "What is the stock.warehouse.orderpoint model?", "response": "The stock.warehouse.orderpoint model represents Minimum Inventory Rule in the ERP system. It contains 114 fields and is used to manage minimum inventory rule data. Key fields include: active, snoozed_until, product_tmpl_id, product_id, product_category_id, product_uom, product_uom_name, product_min_qty, product_max_qty, qty_multiple, group_id, allowed_location_ids, rule_ids, json_lead_days_popover, lead_days_date, allowed_route_ids, route_id, qty_on_hand, qty_forecast, qty_to_order, show_bom, bom_id, show_supplier, location_id, name, source_location_id, action_to_take, trigger, start_date, start_month, end_date, end_month, is_replenish_document_created, purchase_request_id, purchase_order_id, material_request_id, internal_transfer_id, replenish_document_status, is_mo_created, periods, run_rate_days, safety_stock, safety_stock_select, stock_days, responsible_id, branch_id, average_quantity_last_year, lead_days_last_year, average_quantity_run_rate_days, lead_days_run_rate_days, run_rate_type, company_id, warehouse_id, filter_warehouse_id, is_minimum_quantity, is_safety_stock_quantity, select_period, notification_user_ids, pr_status, rfq_status, itr_status, mr_status, from_days_before, run_rate_qty, lead_days, period_date, period_month, run_rate_period_before, run_rate_period_after, qty_check, is_low_stock, path, quantity_restock, is_quantity_restock, qty_restock, supplier_id, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.warehouse.orderpoint", "table_name": ""}
+{"text": "Describe the product.variant.attribute.value model in Odoo.", "response": "The product.variant.attribute.value model represents Product Variant Attribute Value in the ERP system. It contains 10 fields and is used to manage product variant attribute value data. Key fields include: template_id, brand_value_ids, attribute_value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.variant.attribute.value", "table_name": ""}
+{"text": "How to create records in product.product?", "response": "To use the product.product model, you need to provide values for required fields: product_tmpl_id, name, uom_id, uom_po_id, product_variant_ids, tracking, purchase_line_warn, sale_line_warn, type. Readonly fields: price_extra, code, partner_ref, combination_indices, is_product_variant, pricelist_item_count, image_variant_1024, image_variant_512, image_variant_256, image_variant_128, can_image_variant_1024_be_zoomed, image_1024, image_512, image_256, image_128, can_image_1024_be_zoomed, sh_qr_code_img, qty_available, virtual_available, free_qty, incoming_qty, outgoing_qty, nbr_reordering_rules, reordering_min_qty, reordering_max_qty, image_chat, bom_count, used_in_bom_count, mrp_product_qty, date_from, date_to, invoice_state, sale_avg_price, purchase_avg_price, sale_num_invoiced, purchase_num_invoiced, sales_gap, purchase_gap, turnover, total_cost, sale_expected, normal_cost, total_margin, expected_margin, total_margin_rate, expected_margin_rate, purchased_product_qty, value_svl, quantity_svl, valuation, cost_method, product_cost_ids, sales_count, purchase_price_history_line_ids, website_url, near_expire, expired, id, warranty_sale_config, cart_qty, is_generate_product, category_prefix_preference, is_secret_product, variant_short_name, is_variants, purchase_price, purchase_price_totals, assembly_inventory_quantity, assembly_safety_stock_qty, assembly_to_produce_qty, assembly_outgoing_qty, product_display_name, kitchen_inventory_quantity, kitchen_safety_stock_qty, kitchen_to_produce_qty, kitchen_outgoing_qty, is_pos_bom, purchase_req_line_ids, is_gift_product, warehouse_price_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, display_name, create_uid, create_date, write_uid, write_date, __last_update, currency_id, cost_currency_id, volume_uom_name, weight_uom_name, uom_name, valid_product_template_attribute_line_ids, product_variant_id, product_variant_count, has_configurable_attributes, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, has_available_route_ids, is_seo_optimized, can_publish, categ_costing_method, visible_expense_policy, visible_qty_configurator, brand_attribute_id, company_id_domain, group_stock_ids, reordering_rules_ids, hide, brand_setting, uom_categ_id, is_approve, template_purchase_price_history_line_ids, is_vendor_pricelist, is_from_assembly, url_pic, is_from_kitchen, combo_option_items, uom_ids, is_cost_per_warehouse. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.product", "table_name": ""}
+{"text": "List all fields in the untaken.stock.line model.", "response": "The untaken.stock.line model has 11 fields: product_id, quantity, product_unit_measure, untaken_stock_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "untaken.stock.line", "table_name": ""}
+{"text": "Describe the field structure of sale.data.margin.line.", "response": "The sale.data.margin.line model has 12 fields: margin_id, product_id, product_qty, price_subtotal, margin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.data.margin.line", "table_name": ""}
+{"text": "What are the relationships in asset.cip?", "response": "The asset.cip model has 8 relational fields: asset_category -> account.asset.category; cip_account -> account.account; lines -> asset.cip.line; currency -> res.currency; move_id -> account.move; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "asset.cip", "table_name": ""}
+{"text": "Describe the field structure of report.dynamic_accounts_report.general_ledger.", "response": "The report.dynamic_accounts_report.general_ledger model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.dynamic_accounts_report.general_ledger", "table_name": ""}
+{"text": "Show me the fields of account.asset.depreciation.line.", "response": "The account.asset.depreciation.line model has 19 fields: name, sequence, asset_id, parent_state, amount, remaining_value, depreciated_value, depreciation_date, move_id, move_check, move_posted_check, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 5, selection: 1, float: 3, date: 1, boolean: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.asset.depreciation.line", "table_name": ""}
+{"text": "How do I use the product.cancel model?", "response": "To use the product.cancel model, you need to provide values for required fields: none. Readonly fields: pos_order_id, company_id, branch_id, last_supplier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.cancel", "table_name": ""}
+{"text": "What foreign keys exist in qiscus.wa.template?", "response": "The qiscus.wa.template model has 12 relational fields: content_ids -> qiscus.wa.template.content; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "qiscus.wa.template", "table_name": ""}
+{"text": "How to create records in project.task.recurrence?", "response": "To use the project.task.recurrence 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.task.recurrence", "table_name": ""}
+{"text": "What are the relationships in base.update.translations?", "response": "The base.update.translations model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.update.translations", "table_name": ""}
+{"text": "Describe the field structure of budget.purchase.wizard.", "response": "The budget.purchase.wizard model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "budget.purchase.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for sale.terms.and.conditions.", "response": "The sale.terms.and.conditions model has 11 relational fields: activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.terms.and.conditions", "table_name": ""}
+{"text": "What operations can I perform on product.variant.attribute.value?", "response": "To use the product.variant.attribute.value 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.variant.attribute.value", "table_name": ""}
+{"text": "What data can be stored in untaken.stock?", "response": "The untaken.stock model has 18 fields: name, warehouse_id, location_ids, company_id, branch_id, create_sc, state, date_checked, untaken_stock_line_ids, stock_count, domain_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 6, many2many: 1, boolean: 1, selection: 1, datetime: 4, one2many: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "untaken.stock", "table_name": ""}
+{"text": "Tell me about the account.report.partner.ledger model.", "response": "The account.report.partner.ledger model represents Account Partner Ledger in the ERP system. It contains 16 fields and is used to manage account partner ledger data. Key fields include: amount_currency, reconciled, result_selection, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.report.partner.ledger", "table_name": ""}
+{"text": "What does the report.product.report_pricelist model represent?", "response": "The report.product.report_pricelist model represents Pricelist Report in the ERP system. It contains 3 fields and is used to manage pricelist report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.product.report_pricelist", "table_name": ""}
+{"text": "What modules define acrux.chat.connector?", "response": "The acrux.chat.connector model is defined in module: acrux_chat. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "acrux.chat.connector", "table_name": ""}
+{"text": "Show me the relational structure of sh.model.fields.global.selection.", "response": "The sh.model.fields.global.selection model has 3 relational fields: sh_field_id -> sh.custom.field.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.model.fields.global.selection", "table_name": ""}
+{"text": "What methods are available in report.stock.quantity.new?", "response": "The report.stock.quantity.new model is defined in module: equip3_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.stock.quantity.new", "table_name": ""}
+{"text": "What operations can I perform on website.mass_mailing.popup?", "response": "To use the website.mass_mailing.popup 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "website.mass_mailing.popup", "table_name": ""}
+{"text": "What fields does ir.qweb.field.datetime have?", "response": "The ir.qweb.field.datetime model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.datetime", "table_name": ""}
+{"text": "Tell me about the acrux.chat.conversation model.", "response": "The acrux.chat.conversation model represents Chat Conversation in the ERP system. It contains 31 fields and is used to manage chat conversation data. Key fields include: name, number, number_format, image_128, image_url, connector_id, res_partner_id, status, chat_message_ids, sellman_id, last_sent, last_received, last_received_first, company_id, team_id, border_color, crm_lead_id, sale_order_id, partner_sellman_id, room_id, room_name, session_status, team_ids, is_external_link, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "acrux.chat.conversation", "table_name": ""}
+{"text": "How does product.category relate to other models?", "response": "The product.category model has 22 relational fields: parent_id -> product.category; child_id -> product.category; property_account_income_categ_id -> account.account; property_account_expense_categ_id -> account.account; route_ids -> stock.location.route; removal_strategy_id -> product.removal; total_route_ids -> stock.location.route; putaway_rule_ids -> stock.putaway.rule; property_account_creditor_price_difference_categ -> account.account; property_stock_journal -> account.journal; property_stock_account_input_categ_id -> account.account; property_stock_account_output_categ_id -> account.account; property_stock_valuation_account_id -> account.account; analytic_tag_ids -> account.analytic.tag; property_account_debitor_price_difference_categ -> account.account; product_ids -> product.product; property_service_account_id -> account.account; stock_transfer_transit_account_id -> account.account; stock_scrap_account -> account.account; wip_manufacturing_account_id -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: route_ids, total_route_ids, analytic_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.category", "table_name": ""}
+{"text": "How do I use the purchase.excel.extended model?", "response": "To use the purchase.excel.extended 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.excel.extended", "table_name": ""}
+{"text": "Describe the many2many relations for snailmail.letter.missing.required.fields.", "response": "The snailmail.letter.missing.required.fields model has 6 relational fields: partner_id -> res.partner; letter_id -> snailmail.letter; state_id -> res.country.state; country_id -> res.country; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "snailmail.letter.missing.required.fields", "table_name": ""}
+{"text": "What modules define setu.inventory.age.report?", "response": "The setu.inventory.age.report model is defined in module: setu_advance_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "setu.inventory.age.report", "table_name": ""}
+{"text": "What operations can I perform on base.module.upgrade?", "response": "To use the base.module.upgrade model, you need to provide values for required fields: none. Readonly fields: module_info, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.module.upgrade", "table_name": ""}
+{"text": "How is ir.actions.client used in the system?", "response": "The ir.actions.client model represents Client Action in the ERP system. It contains 20 fields and is used to manage client action data. Key fields include: name, type, tag, target, res_model, context, params, params_store, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.client", "table_name": ""}
+{"text": "Show me the relational structure of sale.order.template.", "response": "The sale.order.template model has 7 relational fields: sale_order_template_line_ids -> sale.order.template.line; sale_order_template_option_ids -> sale.order.template.option; mail_template_id -> mail.template; company_id -> res.company; customer_ids -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: customer_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.template", "table_name": ""}
+{"text": "What are the technical details of pos.loyalty.point?", "response": "The pos.loyalty.point model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.loyalty.point", "table_name": ""}
+{"text": "Describe the field structure of receipt.voucher.line.", "response": "The receipt.voucher.line model has 17 fields: receipt_voucher_id, invoice_id, invoice_date, untaxed_amount, tax_amount, total_invoice_amount, currency_id, amount_due, amount, total_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, monetary: 6, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "receipt.voucher.line", "table_name": ""}
+{"text": "What models are connected to pos.loyalty.category?", "response": "The pos.loyalty.category model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.loyalty.category", "table_name": ""}
+{"text": "What data can be stored in ir.model.constraint?", "response": "The ir.model.constraint model has 13 fields: name, definition, message, model, module, type, write_date, create_date, id, display_name, create_uid, write_uid, __last_update. Field types distribution: char: 5, many2one: 4, datetime: 3, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.model.constraint", "table_name": ""}
+{"text": "What data can be stored in product.uom.price?", "response": "The product.uom.price model has 9 fields: uom_id, product_tmpl_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.uom.price", "table_name": ""}
+{"text": "List all fields in the pos.session.log.cashier model.", "response": "The pos.session.log.cashier model has 12 fields: name, user_id, login_date, logout_date, session_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, datetime: 5, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.session.log.cashier", "table_name": ""}
+{"text": "Can you explain the purpose of limit.approval.matrix.sale.reject?", "response": "The limit.approval.matrix.sale.reject model represents limit.approval.matrix.sale.reject in the ERP system. It contains 8 fields and is used to manage limit.approval.matrix.sale.reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "limit.approval.matrix.sale.reject", "table_name": ""}
+{"text": "How do I use the mailing.list.merge model?", "response": "To use the mailing.list.merge model, you need to provide values for required fields: merge_options. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mailing.list.merge", "table_name": ""}
+{"text": "What are the available fields for queue.requeue.job?", "response": "The queue.requeue.job model has 8 fields: job_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "queue.requeue.job", "table_name": ""}
+{"text": "Describe the base_import.tests.models.char.states model in Odoo.", "response": "The base_import.tests.models.char.states model represents Tests : Base Import Model, Character states in the ERP system. It contains 8 fields and is used to manage tests : base import model, character states data. Key fields include: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.char.states", "table_name": ""}
+{"text": "What is the mrp.workcenter.productivity.loss.type model?", "response": "The mrp.workcenter.productivity.loss.type model represents MRP Workorder productivity losses in the ERP system. It contains 8 fields and is used to manage mrp workorder productivity losses data. Key fields include: loss_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.workcenter.productivity.loss.type", "table_name": ""}
+{"text": "What are the relationships in mrp.workcenter.productivity.loss?", "response": "The mrp.workcenter.productivity.loss model has 3 relational fields: loss_id -> mrp.workcenter.productivity.loss.type; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.workcenter.productivity.loss", "table_name": ""}
+{"text": "Tell me about the barcode.labels model.", "response": "The barcode.labels model represents Barcode Labels in the ERP system. It contains 8 fields and is used to manage barcode labels data. Key fields include: product_get_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "barcode.labels", "table_name": ""}
+{"text": "What models are connected to wizard.report.menu.create?", "response": "The wizard.report.menu.create model has 3 relational fields: menu_id -> ir.ui.menu; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "wizard.report.menu.create", "table_name": ""}
+{"text": "What modules define pos.details.wizard?", "response": "The pos.details.wizard model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.details.wizard", "table_name": ""}
+{"text": "How is product.pricelist used in the system?", "response": "The product.pricelist model represents Pricelist in the ERP system. It contains 25 fields and is used to manage pricelist data. Key fields include: name, active, item_ids, currency_id, sequence, country_group_ids, discount_policy, website_id, code, selectable, pricelist_history_ids, from_date, to_date, customer_category, company_id, barcode, is_external_link, pos_config_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.pricelist", "table_name": ""}
+{"text": "How to query repair.order data?", "response": "To use the repair.order model, you need to provide values for required fields: name, product_id, product_qty, product_uom, location_id, invoice_method, company_id. Readonly fields: product_id, product_qty, product_uom, product_uom_category_id, default_address_id, state, location_id, operations, currency_id, invoice_method, invoice_id, move_id, fees_lines, company_id, invoiced, repaired, amount_untaxed, amount_tax, amount_total, invoice_state, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "repair.order", "table_name": ""}
+{"text": "What modules define res.users.tag?", "response": "The res.users.tag model is defined in module: report_user_access_right. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.tag", "table_name": ""}
+{"text": "Describe the implementation of sh.sale.details.report.wizard.", "response": "The sh.sale.details.report.wizard model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.sale.details.report.wizard", "table_name": ""}
+{"text": "How to create records in stock.inventory.request.matrix.reject?", "response": "To use the stock.inventory.request.matrix.reject 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.inventory.request.matrix.reject", "table_name": ""}
+{"text": "How is account.reconcile.model.partner.mapping implemented technically?", "response": "The account.reconcile.model.partner.mapping model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.reconcile.model.partner.mapping", "table_name": ""}
+{"text": "How is stock.backorder.confirmation.line implemented technically?", "response": "The stock.backorder.confirmation.line model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.backorder.confirmation.line", "table_name": ""}
+{"text": "What are the technical details of create.purchase.request.direct?", "response": "The create.purchase.request.direct model is defined in module: equip3_purchase_other_operation_cont. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "create.purchase.request.direct", "table_name": ""}
+{"text": "Describe the field structure of approval.matrix.direct.purchase.line.", "response": "The approval.matrix.direct.purchase.line model has 20 fields: sequence, user_ids, minimum_approver, approval_matrix_direct_purchase, sequence2, approved_users, state_char, time_stamp, feedback, last_approved, approved, order_id, approver_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 4, many2many: 2, many2one: 5, text: 1, datetime: 4, char: 2, boolean: 1, selection: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.direct.purchase.line", "table_name": ""}
+{"text": "List all fields in the ai.chat.session model.", "response": "The ai.chat.session model has 34 fields: name, user_id, config_id, state, session_summary, session_summary_message_count, session_summary_last_updated, auto_compress_enabled, compression_threshold, trim_ratio, message_count, last_activity, total_tokens_used, last_tokens_used, message_ids, job_ids, last_job_id, has_running_job, is_ai_renamed, is_quick_chat, quick_chat_model, quick_chat_res_id, cached_user_message_hash, cached_relevant_memories, cached_system_prompt, thinking_chain, last_frequent_actions_query, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 5, selection: 1, text: 5, integer: 7, datetime: 5, boolean: 4, float: 1, one2many: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ai.chat.session", "table_name": ""}
+{"text": "What fields does pos.generate.efaktur.other have?", "response": "The pos.generate.efaktur.other model has 11 fields: gen_efaktur_id, partner_id, account_move_id, l10n_id_tax_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.generate.efaktur.other", "table_name": ""}
+{"text": "Describe the implementation of mrp.quality.alert.report.", "response": "The mrp.quality.alert.report model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.quality.alert.report", "table_name": ""}
+{"text": "List all fields in the stock.change.product.qty model.", "response": "The stock.change.product.qty model has 11 fields: product_id, product_tmpl_id, product_variant_count, new_quantity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 2, float: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.change.product.qty", "table_name": ""}
+{"text": "What models are connected to approval.matrix.blanket.order.line?", "response": "The approval.matrix.blanket.order.line model has 7 relational fields: user_ids -> res.users; approval_matrix_blanket_order -> approval.matrix.blanket.order; bo_matrix_id -> purchase.requisition; approved_users -> res.users; last_approved -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.blanket.order.line", "table_name": ""}
+{"text": "What are common use cases for stock.traceability.report?", "response": "To use the stock.traceability.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.traceability.report", "table_name": ""}
+{"text": "What methods are available in service.work.order.line?", "response": "The service.work.order.line model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "service.work.order.line", "table_name": ""}
+{"text": "Describe the field structure of account.analytic.account.", "response": "The account.analytic.account model has 57 fields: code, active, line_ids, partner_id, balance, debit, credit, currency_id, project_ids, project_count, name, crossovered_budget_line, subscription_product_line_ids, not_subscription_product_line_ids, terms_and_conditions, start_date, end_date, recurring_interval, recurring_next_date, journal_id, invoice_count, number_of_days, contract_lock, recurring_rule_type, stage, sub_amount_untaxed, sub_amount_tax, sub_amount_total, sale_amount_untaxed, sale_amount_tax, sale_amount_total, order_invoice_currency_id, group_id, company_id, branch_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, boolean: 7, one2many: 8, many2one: 10, monetary: 9, integer: 9, html: 1, date: 3, selection: 2, many2many: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.analytic.account", "table_name": ""}
+{"text": "Describe the crm.send.message.mass model in Odoo.", "response": "The crm.send.message.mass model represents Send Message Mass in the ERP system. It contains 10 fields and is used to manage send message mass data. Key fields include: message_chat_ids, conversation_id, connector_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.send.message.mass", "table_name": ""}
+{"text": "How do I use the account.keterangan.tambahan model?", "response": "To use the account.keterangan.tambahan 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.keterangan.tambahan", "table_name": ""}
+{"text": "How is hide.view.nodes implemented technically?", "response": "The hide.view.nodes model is defined in module: simplify_access_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hide.view.nodes", "table_name": ""}
+{"text": "What are the technical details of sh.back.theme.config.settings?", "response": "The sh.back.theme.config.settings model is defined in module: sh_backmate_theme_adv. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.back.theme.config.settings", "table_name": ""}
+{"text": "What operations can I perform on report.equip3_accounting_reports.journal_entry_report?", "response": "To use the report.equip3_accounting_reports.journal_entry_report model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.journal_entry_report", "table_name": ""}
+{"text": "What methods are available in cust.credit.limit.report.wizard?", "response": "The cust.credit.limit.report.wizard model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "cust.credit.limit.report.wizard", "table_name": ""}
+{"text": "What business logic is in weight.scale.barcode.format?", "response": "To use the weight.scale.barcode.format model, you need to provide values for required fields: none. Readonly fields: total_digit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "weight.scale.barcode.format", "table_name": ""}
+{"text": "How to create records in base.language.export?", "response": "To use the base.language.export model, you need to provide values for required fields: lang, format. Readonly fields: name, data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.language.export", "table_name": ""}
+{"text": "What is the return.approval.matrix model?", "response": "The return.approval.matrix model represents Return Request Approval Matrix in the ERP system. It contains 12 fields and is used to manage return request approval matrix data. Key fields include: name, company_id, branch_id, create_date, create_uid, return_approval_matrix_line_ids, warehouse_id, id, display_name, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "return.approval.matrix", "table_name": ""}
+{"text": "How is ir.actions.client implemented technically?", "response": "The ir.actions.client model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.actions.client", "table_name": ""}
+{"text": "List all fields in the report.equip3_accounting_reports.journal_entry_report model.", "response": "The report.equip3_accounting_reports.journal_entry_report model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.journal_entry_report", "table_name": ""}
+{"text": "What is the account.setup.bank.manual.config model?", "response": "The account.setup.bank.manual.config model represents Bank setup manual config in the ERP system. It contains 30 fields and is used to manage bank setup manual config data. Key fields include: res_partner_bank_id, new_journal_name, linked_journal_id, bank_bic, num_journals_without_account, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, active, acc_type, acc_number, sanitized_acc_number, acc_holder_name, partner_id, bank_id, bank_name, sequence, currency_id, company_id, journal_id, aba_routing, acc_holder_email, acc_holder_type, acc_holder_resident, acc_holder_address.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.setup.bank.manual.config", "table_name": ""}
+{"text": "Show me the relational structure of sh.mrp.quality.alert.", "response": "The sh.mrp.quality.alert model has 21 relational fields: product_id -> product.product; lot_id -> stock.production.lot; user_id -> res.users; team_id -> sh.qc.team; tag_ids -> sh.qc.alert.tags; partner_id -> res.partner; stage_id -> sh.qc.alert.stage; mrp_id -> mrp.production; workorder_id -> mrp.workorder; company_id -> res.company; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.mrp.quality.alert", "table_name": ""}
+{"text": "How does do.matrix.reject relate to other models?", "response": "The do.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "do.matrix.reject", "table_name": ""}
+{"text": "Can you explain the purpose of ks.sales.forecast.result?", "response": "The ks.sales.forecast.result model represents Predicted Results in the ERP system. It contains 12 fields and is used to manage predicted results data. Key fields include: ks_forecast_id, ks_date, ks_value, ks_product_id, ks_partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks.sales.forecast.result", "table_name": ""}
+{"text": "What data can be stored in crossovered.budget?", "response": "The crossovered.budget model has 45 fields: name, user_id, date_from, date_to, crossovered_budget_line, company_id, approval_matrix, request_partner_id, is_allowed_to_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, currency_id, state, complete_name, parent_id, branch_id, is_parent_budget, state1, state2, account_tag_ids, date_today, is_use_theoretical_achievement, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 11, date: 3, one2many: 5, boolean: 9, selection: 3, many2many: 3, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crossovered.budget", "table_name": ""}
+{"text": "How to query website.seo.metadata data?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "website.seo.metadata", "table_name": ""}
+{"text": "Tell me about the mailing.mailing model.", "response": "The mailing.mailing model represents Mass Mailing in the ERP system. It contains 90 fields and is used to manage mass mailing data. Key fields include: active, subject, preview, email_from, sent_date, schedule_date, body_arch, body_html, attachment_ids, keep_archives, campaign_id, source_id, medium_id, state, color, user_id, mailing_type, reply_to_mode, reply_to, mailing_model_real, mailing_model_id, mailing_model_name, mailing_domain, mail_server_id, contact_list_ids, contact_ab_pc, unique_ab_testing, kpi_mail_required, mailing_trace_ids, total, scheduled, expected, ignored, sent, delivered, opened, clicked, replied, bounced, failed, received_ratio, opened_ratio, replied_ratio, bounced_ratio, clicks_ratio, next_departure, use_leads, crm_lead_count, sale_quotation_count, sale_invoiced_amount, rfm_segment_id, lang, model_object_field, sub_object, sub_model_object_field, null_value, copyvalue, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, name.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mailing.mailing", "table_name": ""}
+{"text": "What are common use cases for report.accounting_pdf_reports.report_general_ledger?", "response": "To use the report.accounting_pdf_reports.report_general_ledger model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.accounting_pdf_reports.report_general_ledger", "table_name": ""}
+{"text": "Can you explain the purpose of uom.conversion.history?", "response": "The uom.conversion.history model represents uom.conversion.history in the ERP system. It contains 17 fields and is used to manage uom.conversion.history data. Key fields include: product_id, location_id, prod_lot_id, package_id, partner_id, product_qty, uom_id, counted_qty, uom_conversion, si_uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "uom.conversion.history", "table_name": ""}
+{"text": "Describe the many2many relations for resource.calendar.attendance.", "response": "The resource.calendar.attendance model has 4 relational fields: calendar_id -> resource.calendar; resource_id -> resource.resource; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "resource.calendar.attendance", "table_name": ""}
+{"text": "How is mailing.mailing.schedule.date implemented technically?", "response": "The mailing.mailing.schedule.date model is defined in module: mass_mailing. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mailing.mailing.schedule.date", "table_name": ""}
+{"text": "What fields does account.day.book have?", "response": "The account.day.book model has 13 fields: company_id, journal_ids, account_ids, date_from, date_to, target_move, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 2, date: 2, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.day.book", "table_name": ""}
+{"text": "What foreign keys exist in ir.qweb?", "response": "The ir.qweb model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb", "table_name": ""}
+{"text": "What business logic is in report.stock.report_stock_rule?", "response": "To use the report.stock.report_stock_rule model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.stock.report_stock_rule", "table_name": ""}
+{"text": "What methods are available in account.payment.term?", "response": "The account.payment.term model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.payment.term", "table_name": ""}
+{"text": "What are common use cases for account.asset.category.fiscal?", "response": "To use the account.asset.category.fiscal model, you need to provide values for required fields: asset_category_id. Readonly fields: is_fiscal_asset_type, method_number_fiscal, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.asset.category.fiscal", "table_name": ""}
+{"text": "How do I use the base_import.tests.models.char.required model?", "response": "To use the base_import.tests.models.char.required model, you need to provide values for required fields: value. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base_import.tests.models.char.required", "table_name": ""}
+{"text": "How does kpi.scorecard.line relate to other models?", "response": "The kpi.scorecard.line model has 6 relational fields: kpi_id -> kpi.item; category_id -> kpi.category; period_id -> kpi.period; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kpi.scorecard.line", "table_name": ""}
+{"text": "What are the available fields for access.management?", "response": "The access.management model has 37 fields: name, user_ids, readonly, active, hide_menu_ids, hide_field_ids, remove_action_ids, access_domain_ah_ids, hide_view_nodes_ids, self_module_menu_ids, self_model_ids, total_rules, hide_chatter_ids, hide_chatter, hide_send_mail, hide_log_notes, hide_schedule_activity, hide_export, hide_import, disable_login, disable_debug_mode, company_ids, hide_filters_groups_ids, is_all_users, hide_custom_filter, hide_custom_group, field_conditional_access_ids, apply_by_group, access_group_ids, access_res_group_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2many: 7, boolean: 14, one2many: 7, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "access.management", "table_name": ""}
+{"text": "What are the relationships in snailmail.letter?", "response": "The snailmail.letter model has 11 relational fields: user_id -> res.users; partner_id -> res.partner; company_id -> res.company; report_template -> ir.actions.report; attachment_id -> ir.attachment; message_id -> mail.message; notification_ids -> mail.notification; state_id -> res.country.state; country_id -> res.country; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "snailmail.letter", "table_name": ""}
+{"text": "How to query account.payment.register.payment.difference.line data?", "response": "To use the account.payment.register.payment.difference.line model, you need to provide values for required fields: name, account_id, payment_amount, company_id. Readonly fields: currency_id, payment_difference, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.payment.register.payment.difference.line", "table_name": ""}
+{"text": "What operations can I perform on bill.payment.report.xls?", "response": "To use the bill.payment.report.xls model, you need to provide values for required fields: none. Readonly fields: file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "bill.payment.report.xls", "table_name": ""}
+{"text": "How to create records in sh.quality.alert?", "response": "To use the sh.quality.alert model, you need to provide values for required fields: product_id, user_id, team_id. Readonly fields: name, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.quality.alert", "table_name": ""}
+{"text": "Show me the relational structure of ks.parameter.tuning.wizard.", "response": "The ks.parameter.tuning.wizard model has 3 relational fields: ks_forecast -> ks.sales.forecast; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks.parameter.tuning.wizard", "table_name": ""}
+{"text": "Show me the fields of stock.warehouse.", "response": "The stock.warehouse model has 98 fields: active, partner_id, view_location_id, lot_stock_id, route_ids, wh_input_stock_loc_id, wh_qc_stock_loc_id, wh_output_stock_loc_id, wh_pack_stock_loc_id, mto_pull_id, pick_type_id, pack_type_id, out_type_id, in_type_id, int_type_id, crossdock_route_id, reception_route_id, delivery_route_id, warehouse_count, resupply_wh_ids, resupply_route_ids, show_resupply, sequence, manufacture_to_resupply, manufacture_pull_id, manufacture_mto_pull_id, pbm_mto_pull_id, sam_rule_id, manu_type_id, pbm_type_id, sam_type_id, manufacture_steps, pbm_route_id, pbm_loc_id, sam_loc_id, spacex, spacey, spacez, planimetry_image, count_sl, pos_type_id, buy_to_resupply, buy_pull_id, default_delivery_location_id, driver_ids, name, code, company_id, branch_id, lot_scrap_id, lot_expired_id, street, street2, zip, city, state_id, country_id, phone, responsible_users, reception_steps, delivery_steps, default_receipt_location_id, is_external_link, stock_count_cycle, pos_branch_id, analytic_tag_ids, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 10, many2one: 42, many2many: 6, integer: 12, one2many: 6, selection: 5, binary: 1, char: 11, date: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.warehouse", "table_name": ""}
+{"text": "How is sh.tsp.top.purchasing.product.wizard implemented technically?", "response": "The sh.tsp.top.purchasing.product.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.tsp.top.purchasing.product.wizard", "table_name": ""}
+{"text": "How is report.layout used in the system?", "response": "The report.layout model represents Report Layout in the ERP system. It contains 12 fields and is used to manage report layout data. Key fields include: view_id, image, pdf, sequence, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.layout", "table_name": ""}
+{"text": "Describe the implementation of ai.agent.config.", "response": "The ai.agent.config model is defined in module: ai_chat_agent. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ai.agent.config", "table_name": ""}
+{"text": "What modules define picking.order.line?", "response": "The picking.order.line model is defined in module: pragmatic_odoo_delivery_boy. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "picking.order.line", "table_name": ""}
+{"text": "How is account.move.template.line implemented technically?", "response": "The account.move.template.line model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.move.template.line", "table_name": ""}
+{"text": "What does the sh.edit.title model represent?", "response": "The sh.edit.title model represents Report Template in the ERP system. It contains 8 fields and is used to manage report template data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.edit.title", "table_name": ""}
+{"text": "Show me the fields of stock.picking.to.batch.", "response": "The stock.picking.to.batch model has 10 fields: batch_id, mode, user_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.picking.to.batch", "table_name": ""}
+{"text": "How does create.purchase.request.direct relate to other models?", "response": "The create.purchase.request.direct model has 6 relational fields: supplier_id -> res.partner; item_ids -> create.purchase.request.direct.lines; journal_id -> account.journal; purchase_order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "create.purchase.request.direct", "table_name": ""}
+{"text": "Describe the many2many relations for account.cash.flow.statement.", "response": "The account.cash.flow.statement model has 7 relational fields: account_ids -> account.account; company_ids -> res.company; journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: account_ids, company_ids, journal_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.cash.flow.statement", "table_name": ""}
+{"text": "Show me the relational structure of sh.sale.details.report.wizard.", "response": "The sh.sale.details.report.wizard model has 8 relational fields: team_ids -> crm.team; company_ids -> res.company; company_id -> res.company; payments -> payment.sale.details.report; taxes -> tax.sale.details.report; products -> product.sale.details.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: team_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.sale.details.report.wizard", "table_name": ""}
+{"text": "Describe the field structure of sale.adv.settings.", "response": "The sale.adv.settings model has 11 fields: company_id, name, sh_sale_pro_field_ids, sh_sale_pro_attr_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 2, many2many: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.adv.settings", "table_name": ""}
+{"text": "What are the technical details of uom.uom?", "response": "The uom.uom model is defined in module: uom. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "uom.uom", "table_name": ""}
+{"text": "What are the relationships in pos.backup.orders?", "response": "The pos.backup.orders model has 5 relational fields: config_id -> pos.config; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.backup.orders", "table_name": ""}
+{"text": "Which fields in mr_line.internal_transfer_line are computed?", "response": "The mr_line.internal_transfer_line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mr_line.internal_transfer_line", "table_name": ""}
+{"text": "What business logic is in dev.rma.line?", "response": "To use the dev.rma.line model, you need to provide values for required fields: product_id, delivered_qty. Readonly fields: is_po, account_move_id, tax_number, tax_number_new, grand_total, partner_id, branch_id, tax_amount, grand_total_untaxed, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "dev.rma.line", "table_name": ""}
+{"text": "Show me the fields of pos.query.log.", "response": "The pos.query.log model has 9 fields: name, results, write_date, id, display_name, create_uid, create_date, write_uid, __last_update. Field types distribution: text: 1, char: 2, datetime: 3, integer: 1, many2one: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.query.log", "table_name": ""}
+{"text": "What modules define batch.shipping.line?", "response": "The batch.shipping.line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "batch.shipping.line", "table_name": ""}
+{"text": "What models are connected to blanket.quotation.line?", "response": "The blanket.quotation.line model has 7 relational fields: bq_id -> blanket.quotation; product_id -> product.product; vendor_id -> res.partner; blanket_order_line_id -> purchase.requisition.line; unit_of_measure_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "blanket.quotation.line", "table_name": ""}
+{"text": "How does pick.product.replenish relate to other models?", "response": "The pick.product.replenish model has 4 relational fields: product_id -> product.product; product_tmpl_id -> product.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pick.product.replenish", "table_name": ""}
+{"text": "What operations can I perform on report.dynamic_accounts_report.general_ledger?", "response": "To use the report.dynamic_accounts_report.general_ledger model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.general_ledger", "table_name": ""}
+{"text": "What data can be stored in field.conditional.access?", "response": "The field.conditional.access model has 18 fields: access_management_id, model_id, model_name, attrs_field_id, domain_field_id, domain_field_relation, attrs_type, field_attrs, field_domain, apply_attrs, apply_field_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, char: 5, selection: 1, boolean: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "field.conditional.access", "table_name": ""}
+{"text": "List all fields in the base_import.tests.models.m2o model.", "response": "The base_import.tests.models.m2o model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.m2o", "table_name": ""}
+{"text": "Can you explain the purpose of base_import.mapping?", "response": "The base_import.mapping model represents Base Import Mapping in the ERP system. It contains 10 fields and is used to manage base import mapping data. Key fields include: res_model, column_name, field_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.mapping", "table_name": ""}
+{"text": "What modules define mrp.production.backorder.line?", "response": "The mrp.production.backorder.line model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.production.backorder.line", "table_name": ""}
+{"text": "What are the available fields for stock.inventory.wizard.line?", "response": "The stock.inventory.wizard.line model has 22 fields: inv_line_id, s_no, user_id_1, user_id_2, barcode, product_id, product_uom_id, user1_count, user2_count, final_count, is_user_id_1, is_user_id_2, current_user_id, accept_count, inventory_wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, integer: 2, char: 2, float: 3, boolean: 2, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.inventory.wizard.line", "table_name": ""}
+{"text": "Show me the relational structure of pos.promotion.discount.order.", "response": "The pos.promotion.discount.order model has 3 relational fields: promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.promotion.discount.order", "table_name": ""}
+{"text": "Show me the fields of pmps.adv.wizard.product.line.", "response": "The pmps.adv.wizard.product.line model has 13 fields: pmps_adv_wizard_id, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, float: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pmps.adv.wizard.product.line", "table_name": ""}
+{"text": "How is base.geo_provider used in the system?", "response": "The base.geo_provider model represents Geo Provider in the ERP system. It contains 9 fields and is used to manage geo provider data. Key fields include: tech_name, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.geo_provider", "table_name": ""}
+{"text": "Tell me about the project.create.sale.order model.", "response": "The project.create.sale.order model represents Create SO from project in the ERP system. It contains 16 fields and is used to manage create so from project data. Key fields include: project_id, company_id, partner_id, commercial_partner_id, pricing_type, link_selection, sale_order_id, line_ids, info_invoice, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "project.create.sale.order", "table_name": ""}
+{"text": "Tell me about the stock.picking.batch.line model.", "response": "The stock.picking.batch.line model represents stock.picking.batch.line in the ERP system. It contains 18 fields and is used to manage stock.picking.batch.line data. Key fields include: sequence, transfer_id, product_id, name, location_id, demand_qty, reserved_qty, done_qty, uom_id, picking_batch_id, origin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.picking.batch.line", "table_name": ""}
+{"text": "What is the merchendise.code model?", "response": "The merchendise.code model represents merchendise.code in the ERP system. It contains 9 fields and is used to manage merchendise.code data. Key fields include: name, short_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "merchendise.code", "table_name": ""}
+{"text": "Can you explain the purpose of account.bank.statement.integrate?", "response": "The account.bank.statement.integrate model represents account.bank.statement.integrate in the ERP system. It contains 15 fields and is used to manage account.bank.statement.integrate data. Key fields include: name, journal_id, date_from, date_to, status, created_by, created_date, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.bank.statement.integrate", "table_name": ""}
+{"text": "Describe the many2many relations for mail.thread.blacklist.", "response": "The mail.thread.blacklist model has 6 relational fields: message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.thread.blacklist", "table_name": ""}
+{"text": "What operations can I perform on ir.model.constraint?", "response": "To use the ir.model.constraint model, you need to provide values for required fields: name, model, module, type. Readonly fields: id, display_name, create_uid, write_uid, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.model.constraint", "table_name": ""}
+{"text": "What are the technical details of assign.pr.wizard?", "response": "The assign.pr.wizard model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "assign.pr.wizard", "table_name": ""}
+{"text": "What foreign keys exist in ir.demo_failure?", "response": "The ir.demo_failure model has 4 relational fields: module_id -> ir.module.module; wizard_id -> ir.demo_failure.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.demo_failure", "table_name": ""}
+{"text": "What operations can I perform on report.sh_purchase_reports.sh_po_product_profit_doc?", "response": "To use the report.sh_purchase_reports.sh_po_product_profit_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_po_product_profit_doc", "table_name": ""}
+{"text": "What does the validate.account.move model represent?", "response": "The validate.account.move model represents Validate Account Move in the ERP system. It contains 8 fields and is used to manage validate account move data. Key fields include: force_post, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "validate.account.move", "table_name": ""}
+{"text": "What methods are available in kpi.period.value?", "response": "The kpi.period.value model is defined in module: kpi_scorecard. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kpi.period.value", "table_name": ""}
+{"text": "What are the relationships in ir.qweb.field.barcode?", "response": "The ir.qweb.field.barcode model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb.field.barcode", "table_name": ""}
+{"text": "What are the technical details of access.domain.ah?", "response": "The access.domain.ah model is defined in module: simplify_access_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "access.domain.ah", "table_name": ""}
+{"text": "Show me the fields of payment.acquirer.onboarding.wizard.", "response": "The payment.acquirer.onboarding.wizard model has 19 fields: payment_method, paypal_user_type, paypal_email_account, paypal_seller_account, paypal_pdt_token, stripe_secret_key, stripe_publishable_key, manual_name, journal_name, acc_number, manual_post_msg, _data_fetched, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 2, char: 9, html: 1, boolean: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "How does repair.order.make_invoice relate to other models?", "response": "The repair.order.make_invoice model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "repair.order.make_invoice", "table_name": ""}
+{"text": "What are the available fields for ir.qweb.field.float?", "response": "The ir.qweb.field.float model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.float", "table_name": ""}
+{"text": "What foreign keys exist in setu.inventory.xyz.analysis.bi.report?", "response": "The setu.inventory.xyz.analysis.bi.report model has 6 relational fields: product_id -> product.product; product_category_id -> product.category; company_id -> res.company; wizard_id -> setu.inventory.xyz.analysis.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.xyz.analysis.bi.report", "table_name": ""}
+{"text": "How to query acrux.chat.message.wizard data?", "response": "To use the acrux.chat.message.wizard model, you need to provide values for required fields: text, partner_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "acrux.chat.message.wizard", "table_name": ""}
+{"text": "How is link.tracker.click used in the system?", "response": "The link.tracker.click model represents Link Tracker Click in the ERP system. It contains 13 fields and is used to manage link tracker click data. Key fields include: campaign_id, link_id, ip, country_id, mailing_trace_id, mass_mailing_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "link.tracker.click", "table_name": ""}
+{"text": "Describe the many2many relations for sh.mrp.allow.qc.measurement.", "response": "The sh.mrp.allow.qc.measurement model has 5 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; mrp_id -> mrp.production; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.mrp.allow.qc.measurement", "table_name": ""}
+{"text": "What does the purchase.change.request.wizard model represent?", "response": "The purchase.change.request.wizard model represents Purchase Change Request Wizard in the ERP system. It contains 8 fields and is used to manage purchase change request wizard data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.change.request.wizard", "table_name": ""}
+{"text": "What fields does crm.salesperson.tracking.history have?", "response": "The crm.salesperson.tracking.history model has 11 fields: sales_person_name, history_date, track_lan_lng, track_hist, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, html: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.salesperson.tracking.history", "table_name": ""}
+{"text": "Describe the implementation of pos.report.payment.", "response": "The pos.report.payment model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.report.payment", "table_name": ""}
+{"text": "What operations can I perform on account.pettycash?", "response": "To use the account.pettycash model, you need to provide values for required fields: cash_journal, name, custodian, journal, amount. Readonly fields: number, name, custodian, main_cash_account_id, journal, balance, virtual_balance, company_id, create_uid, create_date, move_id, is_custodian_user, custodian_partner, is_replenished, 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, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.pettycash", "table_name": ""}
+{"text": "How does base_import.tests.models.o2m.child relate to other models?", "response": "The base_import.tests.models.o2m.child model has 3 relational fields: parent_id -> base_import.tests.models.o2m; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.o2m.child", "table_name": ""}
+{"text": "What are the available fields for stock.quant.queue?", "response": "The stock.quant.queue model has 10 fields: product_id, quant_id, datas, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 2, text: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.quant.queue", "table_name": ""}
+{"text": "Show me the relational structure of approval.reject.", "response": "The approval.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.reject", "table_name": ""}
+{"text": "Describe the field structure of account.user.reminder.", "response": "The account.user.reminder model has 12 fields: name, company_id, branch_id, account_line_ids, reminder_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, one2many: 1, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.user.reminder", "table_name": ""}
+{"text": "What are common use cases for crm.send.message.mass?", "response": "To use the crm.send.message.mass 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.send.message.mass", "table_name": ""}
+{"text": "How does pos.payment.wizard relate to other models?", "response": "The pos.payment.wizard model has 4 relational fields: branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.payment.wizard", "table_name": ""}
+{"text": "How is stock.track.line implemented technically?", "response": "The stock.track.line model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.track.line", "table_name": ""}
+{"text": "How is mrp.workorder used in the system?", "response": "The mrp.workorder model represents Work Order in the ERP system. It contains 71 fields and is used to manage work order data. Key fields include: name, workcenter_id, working_state, product_id, product_tracking, product_uom_id, use_create_components_lots, production_id, production_availability, production_state, production_bom_id, qty_production, company_id, qty_producing, qty_remaining, qty_produced, is_produced, state, leave_id, date_planned_start, date_planned_finished, date_start, date_finished, duration_expected, duration, duration_unit, duration_percent, progress, operation_id, worksheet, worksheet_type, worksheet_google_slide, operation_note, move_raw_ids, move_finished_ids, move_line_ids, finished_lot_id, time_ids, is_user_working, working_user_ids, last_working_user_id, next_work_order_id, scrap_ids, scrap_count, production_date, json_popover, show_json_popover, consumption, 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, qc_count, qc_alert_count, sh_workorder_quality_point_id, need_qc, pending_qc, qc_fail, qc_pass, attachment_ids, partner_id, is_mandatory, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.workorder", "table_name": ""}
+{"text": "What fields does digest.tip have?", "response": "The digest.tip model has 12 fields: sequence, name, user_ids, tip_description, group_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, char: 2, many2many: 1, html: 1, many2one: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "digest.tip", "table_name": ""}
+{"text": "What are the technical details of res.users.access.report.wizard?", "response": "The res.users.access.report.wizard model is defined in module: report_user_access_right. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.access.report.wizard", "table_name": ""}
+{"text": "How to create records in sh.custom.model.tab?", "response": "To use the sh.custom.model.tab model, you need to provide values for required fields: none. Readonly fields: invisible_tab, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.custom.model.tab", "table_name": ""}
+{"text": "Describe the many2many relations for journal.payment.report.", "response": "The journal.payment.report model has 3 relational fields: report_id -> sh.payment.report.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "journal.payment.report", "table_name": ""}
+{"text": "Describe the many2many relations for mail.notification.", "response": "The mail.notification model has 5 relational fields: mail_message_id -> mail.message; mail_id -> mail.mail; res_partner_id -> res.partner; sms_id -> sms.sms; letter_id -> snailmail.letter. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.notification", "table_name": ""}
+{"text": "How does account.bank.statement.line relate to other models?", "response": "The account.bank.statement.line model has 133 relational fields: move_id -> account.move; statement_id -> account.bank.statement; foreign_currency_id -> res.currency; currency_id -> res.currency; partner_id -> res.partner; payment_ids -> account.payment; branch_id -> res.branch; pos_branch_id -> res.branch; voucher_id -> pos.voucher; pos_session_id -> pos.session; pos_statement_id -> pos.order; create_uid -> res.users; write_uid -> res.users; suitable_journal_ids -> account.journal; company_id -> res.company; user_id -> res.users; invoice_user_id -> res.users; preferred_payment_method_id -> account.payment.method; debit_origin_id -> account.move; debit_note_ids -> account.move; edi_document_ids -> account.edi.document; loan_line_id -> account.loan.line; loan_id -> account.loan; journal_bank_id -> account.journal; tax_payment_move_id -> account.move; asset_depreciation_ids -> account.asset.depreciation.line; transaction_ids -> payment.transaction; authorized_transaction_ids -> payment.transaction; purchase_vendor_bill_id -> purchase.bill.union; purchase_id -> purchase.order; sh_invoice_recurring_order_id -> invoice.recurring; period_id -> sh.account.period; fiscal_year -> sh.fiscal.year; stock_move_id -> stock.move; stock_valuation_layer_ids -> stock.valuation.layer; auto_reverse_journal_id -> account.journal; pos_order_ids -> pos.order; team_id -> crm.team; partner_shipping_id -> res.partner; consignment_pos_ids -> pos.order; l10n_id_attachment_id -> ir.attachment; landed_costs_ids -> stock.landed.cost; website_id -> website; discount_account_id -> account.account; warranty_reg_id -> product.warranty; related_project_id -> account.analytic.account; repair_ids -> repair.order; target_commission_id -> sh.target.commision; down_payment_purchase_id -> purchase.order; report_template_id1 -> ir.actions.report; report_template_id -> ir.actions.report; timesheet_ids -> account.analytic.line; approval_matrix_id -> approval.matrix.accounting; approved_matrix_ids -> approval.matrix.accounting.lines; approval_matrix_line_id -> approval.matrix.accounting.lines; analytic_group_ids -> account.analytic.tag; invoice_origin_id -> account.move; request_partner_id -> res.partner; journal_id -> account.journal; company_currency_id -> res.currency; line_ids -> account.move.line; commercial_partner_id -> res.partner; partner_bank_id -> res.partner.bank; payment_id -> account.payment; statement_line_id -> account.bank.statement.line; tax_cash_basis_rec_id -> account.partial.reconcile; tax_cash_basis_move_id -> account.move; reversed_entry_id -> account.move; reversal_move_id -> account.move; fiscal_position_id -> account.fiscal.position; invoice_payment_term_id -> account.payment.term; invoice_line_ids -> account.move.line; invoice_incoterm_id -> account.incoterms; invoice_vendor_bill_id -> account.move; invoice_cash_rounding_id -> account.cash.rounding; bank_partner_id -> res.partner; journal_entries_template -> account.move.template; analytic_tag_dynamic -> account.analytic.tag; approvers_ids -> res.users; approved_user_ids -> res.users; internal_tf_id -> account.internal.transfer; new_invoice_id -> account.move; account_asset_id -> account.asset.asset; customer_deposit_ids -> customer.deposit; vendor_deposit_ids -> vendor.deposit; nomor_seri -> account.efaktur; ebupot_id -> account.ebupot; nomor_seri_bupot -> account.ebupot; l10n_id_replace_invoice_id -> account.move; keterangan_tambahan -> account.keterangan.tambahan; signature_country_id -> res.country; signature_city_id -> res.country.city; currency_revaluation_id -> account.move; children_ids -> account.move; currency_revaluation_ref_id -> account.move; pettycash_id -> account.pettycash; sale_order_reference_id -> sale.order; filter_sale_order_reference_ids -> sale.order; exchange_id -> account.invoice.exchange; assembly_id -> assembly.production.record; stock_scrap_id -> stock.scrap.request; kitchen_id -> kitchen.production.record; purchase_order_id -> purchase.order; swo_ids -> service.work.order; finish_good_rework_id -> finish.good.rework; sale_order_ids -> sale.order; filter_sale_order_ids -> sale.order; purchase_order_ids -> purchase.order; filter_purchase_order_ids -> purchase.order; picking_ids -> stock.picking; filter_picking_ids -> stock.picking; cashback_line_ids -> cashback.line; so_cashback_id -> sale.order; return_picking_ids -> stock.picking; picking_id -> stock.picking; rma_id -> dev.rma.rma; account_invoice_ids -> account.invoice.exchange; pos_order_id -> pos.order; deposit_account_journal_id -> account.journal; create_from_session_id -> pos.session; inventory_id -> stock.inventory; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message. Many2many fields: payment_ids, suitable_journal_ids, transaction_ids, authorized_transaction_ids, analytic_group_ids, analytic_tag_dynamic, approvers_ids, approved_user_ids, customer_deposit_ids, vendor_deposit_ids, filter_sale_order_reference_ids, sale_order_ids, filter_sale_order_ids, purchase_order_ids, filter_purchase_order_ids, picking_ids, filter_picking_ids, return_picking_ids, account_invoice_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.bank.statement.line", "table_name": ""}
+{"text": "What data can be stored in snailmail.confirm?", "response": "The snailmail.confirm model has 4 fields: model_name, id, display_name, __last_update. Field types distribution: char: 2, integer: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "snailmail.confirm", "table_name": ""}
+{"text": "What is the uom.uom model?", "response": "The uom.uom model represents Product Unit of Measure in the ERP system. It contains 19 fields and is used to manage product unit of measure data. Key fields include: name, category_id, factor, factor_inv, rounding, active, uom_type, timesheet_widget, is_pos_groupable, is_custom_uom, product_ratio_line, is_external_link, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "uom.uom", "table_name": ""}
+{"text": "What does the utm.mixin model represent?", "response": "The utm.mixin model represents UTM Mixin in the ERP system. It contains 6 fields and is used to manage utm mixin data. Key fields include: campaign_id, source_id, medium_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "utm.mixin", "table_name": ""}
+{"text": "What foreign keys exist in account.tax.map.sales.line?", "response": "The account.tax.map.sales.line model has 11 relational fields: company_id -> res.company; sales_tax_id -> account.tax; target_company -> res.company; target_sales_tax -> account.tax; map_id -> account.account.map; create_uid -> res.users; write_uid -> res.users; line_ids -> account.account.map.line; child_company_id -> res.company; sales_line_ids -> account.tax.map.sales.line; purchase_line_ids -> account.tax.map.purchase.line. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.tax.map.sales.line", "table_name": ""}
+{"text": "What are the technical details of account.financial.ratio?", "response": "The account.financial.ratio model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.financial.ratio", "table_name": ""}
+{"text": "Tell me about the stock.location.tag model.", "response": "The stock.location.tag model represents Location Tags in the ERP system. It contains 10 fields and is used to manage location tags data. Key fields include: name, color, opacity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.location.tag", "table_name": ""}
+{"text": "What fields does account.asset.asset have?", "response": "The account.asset.asset model has 86 fields: entry_count, name, code, value, currency_id, note, category_id, date, active, partner_id, method_number, method_period, method_end, method_progress_factor, value_residual, method_time, prorata, depreciation_line_ids, salvage_value, invoice_id, type, account_analytic_id, analytic_tag_ids, first_depreciation_manual_date, user_id, is_monthly_depreciation, is_reset_january, months_remaining, method, cut_off_asset_date, date_first_depreciation, fiscal_category_id, method_fiscal, asset_type, asset_type_1, sub_asset_type, non_building_type, is_monthly_depreciation_fiscal, is_reset_january_fiscal, months_remaining_fiscal, method_number_fiscal, method_period_fiscal, method_end_fiscal, depreciation_line_ids_fiscal, asset_history_lines_ids, asset_value_residual, account_cip_id, state, state1, state2, approval_matrix_id, approved_matrix_ids, is_approval_matrix, is_approve_button, approval_matrix_line_id, request_partner_id, company_id, branch_id, asset_sequence, product_id, fiscal_prorata_temporis, location, po_ref, asset_post_entries_count, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 14, char: 6, float: 5, many2one: 17, text: 1, date: 4, boolean: 14, selection: 12, one2many: 7, many2many: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.asset.asset", "table_name": ""}
+{"text": "What methods are available in report.accounting_pdf_reports.report_journal?", "response": "The report.accounting_pdf_reports.report_journal model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.accounting_pdf_reports.report_journal", "table_name": ""}
+{"text": "Describe the qiscus.template model in Odoo.", "response": "The qiscus.template model represents qiscus.template in the ERP system. It contains 37 fields and is used to manage qiscus.template data. Key fields include: name, namespace, qiscus_template_id, content_ids, connector_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "qiscus.template", "table_name": ""}
+{"text": "How do I use the sale.order.deduction model?", "response": "To use the sale.order.deduction model, you need to provide values for required fields: none. Readonly fields: product_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.deduction", "table_name": ""}
+{"text": "Tell me about the cancel.supplier.memory model.", "response": "The cancel.supplier.memory model represents cancel.supplier.memory in the ERP system. It contains 9 fields and is used to manage cancel.supplier.memory data. Key fields include: supplier_id, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "cancel.supplier.memory", "table_name": ""}
+{"text": "Describe the kitchen.production.record model in Odoo.", "response": "The kitchen.production.record model represents Kitchen Production Record in the ERP system. It contains 79 fields and is used to manage kitchen production record data. Key fields include: name, company_id, is_branch_required, product_id, product_tmpl_id, product_qty, rejected_qty, product_uom_id, product_uom_category_id, bom_id, branch_id, confirm_date, state, move_raw_ids, move_finished_ids, move_byproduct_ids, location_src_id, location_dest_id, picking_type_id, date_planned_start, date_planned_finished, date_deadline, procurement_group_id, move_dest_ids, production_location_id, warehouse_id, product_tracking, account_move_ids, purchase_request_ids, internal_transfer_count, expiry_days, product_use_expiration_date, finished_lot_ids, byproduct_lot_ids, rejected_lot_ids, show_submit_button, is_autogenerate, default_finished_lot_qty, default_rejected_lot_qty, show_byproduct_lot_tab, byproduct_manual_product_ids, default_byproduct_lot_qty, default_next_byproduct_product_id, any_byproduct_is_autogenerate, all_byproduct_is_autogenerate, component_consumed_qty, svl_value, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kitchen.production.record", "table_name": ""}
+{"text": "How to create records in account.financial.report?", "response": "To use the account.financial.report model, you need to provide values for required fields: name, sign. Readonly fields: level, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.financial.report", "table_name": ""}
+{"text": "What business logic is in account.account?", "response": "To use the account.account model, you need to provide values for required fields: name, code, user_type_id, company_id. Readonly fields: balance, credit, debit, initial_balance, used, internal_type, internal_group, company_id, group_id, root_id, opening_balance, is_off_balance, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.account", "table_name": ""}
+{"text": "What data can be stored in digest.digest?", "response": "The digest.digest model has 40 fields: name, user_ids, periodicity, next_run_date, currency_id, company_id, available_fields, is_subscribed, state, kpi_res_users_connected, kpi_res_users_connected_value, kpi_mail_message_total, kpi_mail_message_total_value, kpi_account_total_revenue, kpi_account_total_revenue_value, kpi_crm_lead_created, kpi_crm_lead_created_value, kpi_crm_opportunities_won, kpi_crm_opportunities_won_value, kpi_livechat_rating, kpi_livechat_rating_value, kpi_livechat_conversations, kpi_livechat_conversations_value, kpi_livechat_response, kpi_livechat_response_value, kpi_project_task_opened, kpi_project_task_opened_value, kpi_pos_total, kpi_pos_total_value, kpi_all_sale_total, kpi_all_sale_total_value, kpi_website_sale_total, kpi_website_sale_total_value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2many: 1, selection: 2, date: 1, many2one: 4, boolean: 13, integer: 7, monetary: 4, float: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "digest.digest", "table_name": ""}
+{"text": "What is the account.ebupot model?", "response": "The account.ebupot model represents Account E-Bupot in the ERP system. It contains 18 fields and is used to manage account e-bupot data. Key fields include: year, name, is_used, invoice_ids, tax_report_id, date_from, date_to, partner_id, company_id, ebupot_template, tahun_pajak, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.ebupot", "table_name": ""}
+{"text": "What operations can I perform on web_editor.converter.test?", "response": "To use the web_editor.converter.test 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "web_editor.converter.test", "table_name": ""}
+{"text": "What are the available fields for website.track?", "response": "The website.track model has 8 fields: visitor_id, page_id, url, visit_datetime, product_id, id, display_name, __last_update. Field types distribution: many2one: 3, text: 1, datetime: 2, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "website.track", "table_name": ""}
+{"text": "Describe the implementation of cancel.credit.limit.", "response": "The cancel.credit.limit model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "cancel.credit.limit", "table_name": ""}
+{"text": "List all fields in the customer.order.dic model.", "response": "The customer.order.dic model has 10 fields: report_id, list_order, saleperson, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, one2many: 1, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "customer.order.dic", "table_name": ""}
+{"text": "What are the technical details of ks_dashboard_ninja.board_template?", "response": "The ks_dashboard_ninja.board_template model is defined in module: ks_dashboard_ninja. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks_dashboard_ninja.board_template", "table_name": ""}
+{"text": "What business logic is in lost.product?", "response": "To use the lost.product 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "lost.product", "table_name": ""}
+{"text": "How does pos.top.selling.wizard relate to other models?", "response": "The pos.top.selling.wizard model has 4 relational fields: branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.top.selling.wizard", "table_name": ""}
+{"text": "Which fields in stock.inventory.approval.matrix.line are computed?", "response": "The stock.inventory.approval.matrix.line model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.inventory.approval.matrix.line", "table_name": ""}
+{"text": "Describe the mrp.workcenter.productivity model in Odoo.", "response": "The mrp.workcenter.productivity model represents Workcenter Productivity Log in the ERP system. It contains 19 fields and is used to manage workcenter productivity log data. Key fields include: production_id, workcenter_id, company_id, workorder_id, user_id, loss_id, loss_type, description, date_start, date_end, duration, cost_already_recorded, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.workcenter.productivity", "table_name": ""}
+{"text": "What foreign keys exist in ir.logging?", "response": "The ir.logging model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.logging", "table_name": ""}
+{"text": "What are the relationships in stock.change.product.qty?", "response": "The stock.change.product.qty model has 4 relational fields: product_id -> product.product; product_tmpl_id -> product.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.change.product.qty", "table_name": ""}
+{"text": "Describe the queue.jobs.cancel model in Odoo.", "response": "The queue.jobs.cancel model represents Cancel selected jobs in the ERP system. It contains 8 fields and is used to manage cancel selected jobs data. Key fields include: job_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "queue.jobs.cancel", "table_name": ""}
+{"text": "What foreign keys exist in stock.warn.insufficient.qty.repair?", "response": "The stock.warn.insufficient.qty.repair model has 6 relational fields: repair_id -> repair.order; product_id -> product.product; location_id -> stock.location; quant_ids -> stock.quant; create_uid -> res.users; write_uid -> res.users. Many2many fields: quant_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.warn.insufficient.qty.repair", "table_name": ""}
+{"text": "What does the calendar.alarm_manager model represent?", "response": "The calendar.alarm_manager model represents Event Alarm Manager in the ERP system. It contains 3 fields and is used to manage event alarm manager data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "calendar.alarm_manager", "table_name": ""}
+{"text": "What data can be stored in report.sh_sale_reports.sh_sale_invoice_summary_doc?", "response": "The report.sh_sale_reports.sh_sale_invoice_summary_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_sale_reports.sh_sale_invoice_summary_doc", "table_name": ""}
+{"text": "Describe the many2many relations for acrux.chat.message.", "response": "The acrux.chat.message model has 7 relational fields: contact_id -> acrux.chat.conversation; connector_id -> acrux.chat.connector; company_id -> res.company; user_id -> res.users; template_id -> qiscus.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "acrux.chat.message", "table_name": ""}
+{"text": "Tell me about the crm.lead2opportunity.partner.mass model.", "response": "The crm.lead2opportunity.partner.mass model represents Convert Lead to Opportunity (in mass) in the ERP system. It contains 18 fields and is used to manage convert lead to opportunity (in mass) data. Key fields include: lead_id, lead_tomerge_ids, user_ids, deduplicate, action, force_assignment, name, duplicated_lead_ids, partner_id, user_id, team_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.lead2opportunity.partner.mass", "table_name": ""}
+{"text": "What are the relationships in account.invoice.report?", "response": "The account.invoice.report model has 17 relational fields: move_id -> account.move; journal_id -> account.journal; company_id -> res.company; company_currency_id -> res.currency; partner_id -> res.partner; commercial_partner_id -> res.partner; country_id -> res.country; invoice_user_id -> res.users; fiscal_position_id -> account.fiscal.position; product_id -> product.product; product_uom_id -> uom.uom; product_categ_id -> product.category; account_id -> account.account; analytic_account_id -> account.analytic.account; team_id -> crm.team; branch_id -> res.branch; pos_branch_id -> res.branch. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.invoice.report", "table_name": ""}
+{"text": "How does stock.warn.insufficient.qty.unbuild relate to other models?", "response": "The stock.warn.insufficient.qty.unbuild model has 6 relational fields: unbuild_id -> mrp.unbuild; product_id -> product.product; location_id -> stock.location; quant_ids -> stock.quant; create_uid -> res.users; write_uid -> res.users. Many2many fields: quant_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.warn.insufficient.qty.unbuild", "table_name": ""}
+{"text": "How do I use the dev.purchase.team model?", "response": "To use the dev.purchase.team model, you need to provide values for required fields: name, company_id. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "dev.purchase.team", "table_name": ""}
+{"text": "What is the sh.fiscal.year model?", "response": "The sh.fiscal.year model represents Fiscal Year in the ERP system. It contains 18 fields and is used to manage fiscal year data. Key fields include: name, code, date_start, date_end, period_ids, state, company_id, branch_id, hide_button, move_id, summary_move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.fiscal.year", "table_name": ""}
+{"text": "Tell me about the account.tax.report model.", "response": "The account.tax.report model represents Account Tax Report in the ERP system. It contains 13 fields and is used to manage account tax report data. Key fields include: name, country_id, line_ids, root_line_ids, company_id, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.tax.report", "table_name": ""}
+{"text": "Describe the mail.tracking.value model in Odoo.", "response": "The mail.tracking.value model represents Mail Tracking Value in the ERP system. It contains 25 fields and is used to manage mail tracking value data. Key fields include: field, field_desc, field_type, field_groups, old_value_integer, old_value_float, old_value_monetary, old_value_char, old_value_text, old_value_datetime, new_value_integer, new_value_float, new_value_monetary, new_value_char, new_value_text, new_value_datetime, mail_message_id, tracking_sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.tracking.value", "table_name": ""}
+{"text": "Describe the repair.order.make_invoice model in Odoo.", "response": "The repair.order.make_invoice model represents Create Mass Invoice (repair) in the ERP system. It contains 8 fields and is used to manage create mass invoice (repair) data. Key fields include: group, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "repair.order.make_invoice", "table_name": ""}
+{"text": "What operations can I perform on stock.picking.to.batch?", "response": "To use the stock.picking.to.batch 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.picking.to.batch", "table_name": ""}
+{"text": "What are common use cases for restaurant.printer?", "response": "To use the restaurant.printer 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "restaurant.printer", "table_name": ""}
+{"text": "What methods are available in report.reordering.view?", "response": "The report.reordering.view model is defined in module: allfresh_mod_report_reordering. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.reordering.view", "table_name": ""}
+{"text": "Show me the fields of pos.category.", "response": "The pos.category model has 23 fields: name, parent_id, child_id, sequence, image_128, Minimum_amount, amount_footer, is_category_combo, sale_limit_time, from_time, to_time, submit_all_pos, pos_branch_ids, pos_config_ids, category_type, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, one2many: 1, integer: 4, binary: 1, boolean: 3, float: 2, many2many: 2, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.category", "table_name": ""}
+{"text": "What is the product.template.create.variant model?", "response": "The product.template.create.variant model represents Product Template Create Variant in the ERP system. It contains 8 fields and is used to manage product template create variant data. Key fields include: variant_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.template.create.variant", "table_name": ""}
+{"text": "How to create records in gamification.karma.rank?", "response": "To use the gamification.karma.rank model, you need to provide values for required fields: name, karma_min. Readonly fields: rank_users_count, image_1024, image_512, image_256, image_128, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "gamification.karma.rank", "table_name": ""}
+{"text": "What methods are available in pos.promotion.tebus.murah?", "response": "The pos.promotion.tebus.murah model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.promotion.tebus.murah", "table_name": ""}
+{"text": "How does mrp.document relate to other models?", "response": "The mrp.document model has 8 relational fields: ir_attachment_id -> ir.attachment; create_uid -> res.users; write_uid -> res.users; company_id -> res.company; original_id -> ir.attachment; website_id -> website; theme_template_id -> theme.ir.attachment; partner -> res.partner. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.document", "table_name": ""}
+{"text": "What are the available fields for account.analytic.tag?", "response": "The account.analytic.tag model has 39 fields: color, active, active_analytic_distribution, analytic_distribution_ids, name, company_id, branch_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 6, boolean: 7, one2many: 5, char: 5, many2one: 7, selection: 2, date: 2, many2many: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.analytic.tag", "table_name": ""}
+{"text": "What modules define report.eq_scrap_order_report.scrap_order_report?", "response": "The report.eq_scrap_order_report.scrap_order_report model is defined in module: eq_scrap_order_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.eq_scrap_order_report.scrap_order_report", "table_name": ""}
+{"text": "What are the available fields for sale.order.template.option?", "response": "The sale.order.template.option model has 14 fields: sale_order_template_id, company_id, name, product_id, uom_id, product_uom_category_id, quantity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, text: 1, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.order.template.option", "table_name": ""}
+{"text": "Describe the field structure of base_import.tests.models.char.required.", "response": "The base_import.tests.models.char.required model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.char.required", "table_name": ""}
+{"text": "What are the technical details of pos.payment.installment.tenor?", "response": "The pos.payment.installment.tenor model is defined in module: equip3_pos_payment_edc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.payment.installment.tenor", "table_name": ""}
+{"text": "How is blanketwiz.blanketwiz used in the system?", "response": "The blanketwiz.blanketwiz model represents Sale Blanket Wizard in the ERP system. It contains 8 fields and is used to manage sale blanket wizard data. Key fields include: wiz_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "blanketwiz.blanketwiz", "table_name": ""}
+{"text": "Can you explain the purpose of customer.degree.trust?", "response": "The customer.degree.trust model represents Customer Degree Trust in the ERP system. It contains 12 fields and is used to manage customer degree trust data. Key fields include: name, overdue_day, no_of_overdue_invoices, index, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "customer.degree.trust", "table_name": ""}
+{"text": "What models are connected to lost.product?", "response": "The lost.product model has 3 relational fields: top_id -> sh.tsp.top.selling.product.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "lost.product", "table_name": ""}
+{"text": "What foreign keys exist in stock.inventory.request.matrix.reject?", "response": "The stock.inventory.request.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.inventory.request.matrix.reject", "table_name": ""}
+{"text": "Show me the relational structure of pick.product.replenish.", "response": "The pick.product.replenish model has 4 relational fields: product_id -> product.product; product_tmpl_id -> product.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pick.product.replenish", "table_name": ""}
+{"text": "Describe the pos.voucher.use.history model in Odoo.", "response": "The pos.voucher.use.history model represents Histories use voucher of customer in the ERP system. It contains 13 fields and is used to manage histories use voucher of customer data. Key fields include: pos_order_id, payment_id, voucher_id, value, used_date, cashier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.voucher.use.history", "table_name": ""}
+{"text": "Show me the relational structure of sh.back.theme.config.settings.", "response": "The sh.back.theme.config.settings model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.back.theme.config.settings", "table_name": ""}
+{"text": "What methods are available in crossovered.budget.lines?", "response": "The crossovered.budget.lines model is defined in module: om_account_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crossovered.budget.lines", "table_name": ""}
+{"text": "How does setu.inventory.age.bi.report relate to other models?", "response": "The setu.inventory.age.bi.report model has 6 relational fields: product_id -> product.product; product_category_id -> product.category; company_id -> res.company; wizard_id -> setu.inventory.age.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.age.bi.report", "table_name": ""}
+{"text": "Describe the field structure of payment.acquirer.", "response": "The payment.acquirer model has 45 fields: name, color, display_as, description, sequence, company_id, view_template_id, registration_view_template_id, state, capture_manually, journal_id, check_validity, country_ids, pre_msg, auth_msg, pending_msg, done_msg, cancel_msg, save_token, token_implemented, authorize_implemented, fees_implemented, fees_active, fees_dom_fixed, fees_dom_var, fees_int_fixed, fees_int_var, qr_code, module_id, module_state, module_to_buy, image_128, payment_icon_ids, payment_flow, inbound_payment_method_ids, provider, so_reference_type, website_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 3, html: 6, many2one: 8, selection: 6, boolean: 8, many2many: 3, float: 4, binary: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "payment.acquirer", "table_name": ""}
+{"text": "What methods are available in portal.wizard?", "response": "The portal.wizard model is defined in module: portal. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "portal.wizard", "table_name": ""}
+{"text": "How to create records in website.page?", "response": "To use the website.page model, you need to provide values for required fields: view_id, name, priority, mode. Readonly fields: is_visible, can_publish, website_url, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, model_data_id, xml_id, is_seo_optimized, first_page_id. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "website.page", "table_name": ""}
+{"text": "What business logic is in report.sh_purchase_reports.sh_vend_po_analysis_doc?", "response": "To use the report.sh_purchase_reports.sh_vend_po_analysis_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_vend_po_analysis_doc", "table_name": ""}
+{"text": "What is the crm.phonecall2phonecall model?", "response": "The crm.phonecall2phonecall model represents Phonecall To Phonecall in the ERP system. It contains 17 fields and is used to manage phonecall to phonecall data. Key fields include: name, user_id, contact_name, phone, tag_ids, date, team_id, action, partner_id, note, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.phonecall2phonecall", "table_name": ""}
+{"text": "How is account.edi.format implemented technically?", "response": "The account.edi.format model is defined in module: account_edi. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.edi.format", "table_name": ""}
+{"text": "What are common use cases for pos.promotion.selected.brand?", "response": "To use the pos.promotion.selected.brand model, you need to provide values for required fields: type_apply, gift_based_on, promotion_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion.selected.brand", "table_name": ""}
+{"text": "Show me the relational structure of ir.fields.converter.", "response": "The ir.fields.converter model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.fields.converter", "table_name": ""}
+{"text": "What models are connected to crm.salesperson.tracking.history?", "response": "The crm.salesperson.tracking.history model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.salesperson.tracking.history", "table_name": ""}
+{"text": "What operations can I perform on report_excel_import_wizard?", "response": "To use the report_excel_import_wizard model, you need to provide values for required fields: data. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report_excel_import_wizard", "table_name": ""}
+{"text": "Show me the relational structure of res.partner.title.", "response": "The res.partner.title model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.partner.title", "table_name": ""}
+{"text": "How to query setu.inventory.turnover.analysis.bi.report data?", "response": "To use the setu.inventory.turnover.analysis.bi.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.turnover.analysis.bi.report", "table_name": ""}
+{"text": "What business logic is in ks_dashboard_ninja.item?", "response": "To use the ks_dashboard_ninja.item model, you need to provide values for required fields: ks_layout, ks_date_filter_selection, ks_date_filter_selection_2, ks_dashboard_item_type, ks_list_view_type. Readonly fields: ks_model_name_2, ks_model_name, ks_record_count_2, ks_record_count, ks_chart_groupby_type, ks_chart_sub_groupby_type, ks_chart_data, ks_kpi_data, ks_list_view_data, ks_to_do_data, ks_query_result, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_dashboard_ninja.item", "table_name": ""}
+{"text": "What are the relationships in tax.report?", "response": "The tax.report model has 9 relational fields: account_ids -> account.account; tax_ids -> account.tax; company_ids -> res.company; branch_ids -> res.branch; journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: account_ids, tax_ids, company_ids, branch_ids, journal_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "tax.report", "table_name": ""}
+{"text": "What is the pos.promotion.discount.condition model?", "response": "The pos.promotion.discount.condition model represents Promotion discount condition in the ERP system. It contains 11 fields and is used to manage promotion discount condition data. Key fields include: active, product_id, minimum_quantity, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.promotion.discount.condition", "table_name": ""}
+{"text": "What operations can I perform on ir.property?", "response": "To use the ir.property model, you need to provide values for required fields: fields_id, type. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.property", "table_name": ""}
+{"text": "How does order.picking.lines relate to other models?", "response": "The order.picking.lines model has 5 relational fields: order_id -> order.picking; product_id -> product.product; picking_id -> stock.picking; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "order.picking.lines", "table_name": ""}
+{"text": "What are the technical details of mrp.production?", "response": "The mrp.production model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.production", "table_name": ""}
+{"text": "Show me the relational structure of website.multi.mixin.", "response": "The website.multi.mixin model has 1 relational fields: website_id -> website. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.multi.mixin", "table_name": ""}
+{"text": "How to create records in account.account.tag?", "response": "To use the account.account.tag model, you need to provide values for required fields: applicability, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.account.tag", "table_name": ""}
+{"text": "What foreign keys exist in stock.picking.type?", "response": "The stock.picking.type model has 13 relational fields: sequence_id -> ir.sequence; default_location_src_id -> stock.location; default_location_dest_id -> stock.location; return_picking_type_id -> stock.picking.type; warehouse_id -> stock.warehouse; company_id -> res.company; branch_id -> res.branch; filter_location_ids -> stock.location; stock_picking_dasboard_id -> stock.picking.type.dashboard; picking_ids -> stock.picking; pos_branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_location_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.picking.type", "table_name": ""}
+{"text": "What foreign keys exist in report.excel.aggregate?", "response": "The report.excel.aggregate model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.excel.aggregate", "table_name": ""}
+{"text": "How is acrux.chat.message used in the system?", "response": "The acrux.chat.message model represents Chat Message in the ERP system. It contains 23 fields and is used to manage chat message data. Key fields include: name, msgid, contact_id, connector_id, date_message, from_me, company_id, error_msg, user_id, ttype, event, template_id, is_direct, text, res_model, res_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "acrux.chat.message", "table_name": ""}
+{"text": "What methods are available in account.fiscal.position.tax?", "response": "The account.fiscal.position.tax model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.fiscal.position.tax", "table_name": ""}
+{"text": "Describe the field structure of sh.purchase.payment.report.wizard.", "response": "The sh.purchase.payment.report.wizard model has 13 fields: date_start, date_end, state, user_ids, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, selection: 1, many2many: 3, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.purchase.payment.report.wizard", "table_name": ""}
+{"text": "Which fields in account.bank.statement.line are computed?", "response": "The account.bank.statement.line model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.bank.statement.line", "table_name": ""}
+{"text": "How to create records in account.partial.reconcile?", "response": "To use the account.partial.reconcile model, you need to provide values for required fields: debit_move_id, credit_move_id. Readonly fields: company_currency_id, debit_currency_id, credit_currency_id, max_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.partial.reconcile", "table_name": ""}
+{"text": "What operations can I perform on account.cash.flow.statement?", "response": "To use the account.cash.flow.statement model, you need to provide values for required fields: levels, comp_detail, type_report, journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.cash.flow.statement", "table_name": ""}
+{"text": "Which fields in ir.demo_failure are computed?", "response": "The ir.demo_failure model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.demo_failure", "table_name": ""}
+{"text": "Describe the field structure of pos.report.category.", "response": "The pos.report.category model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.report.category", "table_name": ""}
+{"text": "Describe the many2many relations for meetings.salespersons.", "response": "The meetings.salespersons model has 4 relational fields: salesperson_id -> res.users; calendar_event_id -> calendar.event; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "meetings.salespersons", "table_name": ""}
+{"text": "Tell me about the mail.activity.type model.", "response": "The mail.activity.type model represents Activity Type in the ERP system. It contains 29 fields and is used to manage activity type data. Key fields include: name, summary, sequence, active, create_uid, delay_count, delay_unit, delay_label, delay_from, icon, decoration_type, res_model_id, default_next_type_id, force_next, next_type_ids, previous_type_ids, mail_template_ids, default_user_id, default_description, initial_res_model_id, res_model_change, category, attachment_required, id, display_name, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.activity.type", "table_name": ""}
+{"text": "What are common use cases for account.bank.cashbox.line?", "response": "To use the account.bank.cashbox.line model, you need to provide values for required fields: coin_value. Readonly fields: subtotal, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.bank.cashbox.line", "table_name": ""}
+{"text": "How does replenish.wizard relate to other models?", "response": "The replenish.wizard model has 4 relational fields: fund_id -> account.pettycash; replenish_account_id -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "replenish.wizard", "table_name": ""}
+{"text": "What data can be stored in vendor.pricelist.approval.matrix?", "response": "The vendor.pricelist.approval.matrix model has 14 fields: name, company_id, branch_id, department_id, created_by, created_date, approval_matrix_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 6, date: 1, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "vendor.pricelist.approval.matrix", "table_name": ""}
+{"text": "How does account.edi.format relate to other models?", "response": "The account.edi.format model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.edi.format", "table_name": ""}
+{"text": "What models are connected to sh.model.fields.global.selection?", "response": "The sh.model.fields.global.selection model has 3 relational fields: sh_field_id -> sh.custom.field.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.model.fields.global.selection", "table_name": ""}
+{"text": "What does the stock.location.route model represent?", "response": "The stock.location.route model represents Inventory Routes in the ERP system. It contains 22 fields and is used to manage inventory routes data. Key fields include: name, active, sequence, rule_ids, product_selectable, product_categ_selectable, warehouse_selectable, supplied_wh_id, supplier_wh_id, company_id, product_ids, categ_ids, warehouse_domain_ids, warehouse_ids, sale_selectable, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.location.route", "table_name": ""}
+{"text": "Describe the many2many relations for export.efaktur.", "response": "The export.efaktur model has 4 relational fields: partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "export.efaktur", "table_name": ""}
+{"text": "How to query cust.credit.limit.data.line data?", "response": "To use the cust.credit.limit.data.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cust.credit.limit.data.line", "table_name": ""}
+{"text": "What are common use cases for tax.sale.details.report?", "response": "To use the tax.sale.details.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "tax.sale.details.report", "table_name": ""}
+{"text": "Describe the generate.pos.voucher.use.history model in Odoo.", "response": "The generate.pos.voucher.use.history model represents Histories Generate use voucher of customer in the ERP system. It contains 13 fields and is used to manage histories generate use voucher of customer data. Key fields include: pos_order_id, payment_id, voucher_id, value, used_date, cashier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "generate.pos.voucher.use.history", "table_name": ""}
+{"text": "What operations can I perform on account.bank.statement?", "response": "To use the account.bank.statement model, you need to provide values for required fields: date, state, journal_id. Readonly fields: name, reference, state, currency_id, journal_type, company_id, total_entry_encoding, balance_end, difference, move_line_count, all_lines_reconciled, is_difference_zero, previous_statement_id, is_valid_balance_start, country_code, accounting_date, account_id, pos_branch_id, 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, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.bank.statement", "table_name": ""}
+{"text": "Show me the fields of ir.sequence.date_range.", "response": "The ir.sequence.date_range model has 12 fields: date_from, date_to, sequence_id, number_next, number_next_actual, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, many2one: 3, integer: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.sequence.date_range", "table_name": ""}
+{"text": "What operations can I perform on sh.pwa.config?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.pwa.config", "table_name": ""}
+{"text": "Describe the field structure of report.sh_purchase_reports.sh_top_purchasing_product_doc.", "response": "The report.sh_purchase_reports.sh_top_purchasing_product_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_top_purchasing_product_doc", "table_name": ""}
+{"text": "What are the relationships in sh.top.purchasing.excel.extended?", "response": "The sh.top.purchasing.excel.extended model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.top.purchasing.excel.extended", "table_name": ""}
+{"text": "Describe the field structure of mr_line.internal_transfer_line.", "response": "The mr_line.internal_transfer_line model has 22 fields: mr_id, mr_line_id, no, product_id, description, uom_id, source_location, source_warehouse_id, current_qty, virtual_available, qty_transfer, mr_ir_wizard, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 10, integer: 2, char: 2, float: 3, many2many: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mr_line.internal_transfer_line", "table_name": ""}
+{"text": "What is the portal.wizard model?", "response": "The portal.wizard model represents Grant Portal Access in the ERP system. It contains 9 fields and is used to manage grant portal access data. Key fields include: user_ids, welcome_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "portal.wizard", "table_name": ""}
+{"text": "How to query account.tax.group data?", "response": "To use the account.tax.group 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.tax.group", "table_name": ""}
+{"text": "How does sh.sale.details.report.wizard relate to other models?", "response": "The sh.sale.details.report.wizard model has 8 relational fields: team_ids -> crm.team; company_ids -> res.company; company_id -> res.company; payments -> payment.sale.details.report; taxes -> tax.sale.details.report; products -> product.sale.details.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: team_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.sale.details.report.wizard", "table_name": ""}
+{"text": "What are common use cases for sale.order.template?", "response": "To use the sale.order.template model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.template", "table_name": ""}
+{"text": "What foreign keys exist in product.attribute.custom.value?", "response": "The product.attribute.custom.value model has 4 relational fields: custom_product_template_attribute_value_id -> product.template.attribute.value; sale_order_line_id -> sale.order.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.attribute.custom.value", "table_name": ""}
+{"text": "Can you explain the purpose of pos.gift.card.use?", "response": "The pos.gift.card.use model represents Used to Store Gift Card Uses History. in the ERP system. It contains 12 fields and is used to manage used to store gift card uses history. data. Key fields include: card_id, customer_id, pos_order_id, order_date, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.gift.card.use", "table_name": ""}
+{"text": "What business logic is in sale.order.pricelist.wizard.line?", "response": "To use the sale.order.pricelist.wizard.line model, you need to provide values for required fields: sh_pricelist_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.pricelist.wizard.line", "table_name": ""}
+{"text": "How is product.supplierinfo used in the system?", "response": "The product.supplierinfo model represents Supplier Pricelist in the ERP system. It contains 88 fields and is used to manage supplier pricelist data. Key fields include: access_url, access_token, access_warning, purchase_requisition_id, purchase_requisition_line_id, name, product_name, product_code, sequence, product_uom, product_uom_category_id, product_uom_new, vendor_uom, min_qty, price, company_id, currency_id, date_start, date_end, product_id, product_tmpl_id, product_variant_count, delay, request_partner_id, state, state1, state2, vendor_pricelist_approval_matrix, approval_ids, user_approval_ids, current_user, is_vendor_pricelist_approval_matrix, branch_id, changes, changes_id, approval_matrix_line_id, is_approve_button, name_old, product_name_old, product_code_old, delay_old, branch_id_old, date_old, product_id_old, product_tmpl_id_old, product_uom_old, min_qty_old, price_old, company_id_old, currency_id_old, date_start_old, date_end_old, vendor_pricelist_approval_matrix_old, edit_button_state, last_price, last_update_price, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.supplierinfo", "table_name": ""}
+{"text": "Can you explain the purpose of report.sale.report_saleproforma?", "response": "The report.sale.report_saleproforma model represents Proforma Report in the ERP system. It contains 3 fields and is used to manage proforma report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sale.report_saleproforma", "table_name": ""}
+{"text": "Which fields in report.mrp.report_bom_structure are computed?", "response": "The report.mrp.report_bom_structure model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.mrp.report_bom_structure", "table_name": ""}
+{"text": "Describe the field structure of picking.order.wizard.", "response": "The picking.order.wizard model has 9 fields: delivery_boy, sale_order, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "picking.order.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for account.analytic.line.", "response": "The account.analytic.line model has 31 relational fields: product_uom_category_id -> uom.category; tag_ids -> account.analytic.tag; currency_id -> res.currency; general_account_id -> account.account; task_id -> project.task; project_id -> project.project; user_id -> res.users; employee_id -> hr.employee; department_id -> hr.department; encoding_uom_id -> uom.uom; timesheet_invoice_id -> account.move; so_line -> sale.order.line; product_uom_id -> uom.uom; account_id -> account.analytic.account; partner_id -> res.partner; company_id -> res.company; group_id -> account.analytic.group; product_id -> product.product; move_id -> account.move.line; branch_id -> res.branch; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.analytic.line", "table_name": ""}
+{"text": "Describe the many2many relations for account.payment.register.", "response": "The account.payment.register model has 25 relational fields: currency_id -> res.currency; journal_id -> account.journal; company_currency_id -> res.currency; line_ids -> account.move.line; source_currency_id -> res.currency; company_id -> res.company; partner_id -> res.partner; payment_method_id -> account.payment.method; available_payment_method_ids -> account.payment.method; writeoff_account_id -> account.account; prepayment_journal_id -> account.journal; revenue_account -> account.account; payment_token_id -> payment.token; suitable_payment_token_partner_ids -> res.partner; receipt_approval_matrix_id -> approval.matrix.accounting; difference_ids -> account.payment.register.payment.difference.line; partner_bank_id -> res.partner.bank; analytic_group_ids -> account.analytic.tag; administration_account -> account.account; validated_move_ids -> account.move; available_partner_bank_ids -> res.partner.bank; validated_line_ids -> account.move.line; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: line_ids, available_payment_method_ids, suitable_payment_token_partner_ids, analytic_group_ids, validated_move_ids, available_partner_bank_ids, validated_line_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.payment.register", "table_name": ""}
+{"text": "What methods are available in accounting.flow.wizard?", "response": "The accounting.flow.wizard model is defined in module: equip3_accounting_flow. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "accounting.flow.wizard", "table_name": ""}
+{"text": "How to create records in res.bank?", "response": "To use the res.bank 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.bank", "table_name": ""}
+{"text": "How to query report.equip3_purchase_other_operation.report_analyze_quot data?", "response": "To use the report.equip3_purchase_other_operation.report_analyze_quot model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_purchase_other_operation.report_analyze_quot", "table_name": ""}
+{"text": "Show me the relational structure of project.create.invoice.", "response": "The project.create.invoice model has 6 relational fields: project_id -> project.project; _candidate_orders -> sale.order; sale_order_id -> sale.order; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: _candidate_orders.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "project.create.invoice", "table_name": ""}
+{"text": "Describe the many2many relations for milestone.contract.template.purchase.", "response": "The milestone.contract.template.purchase model has 4 relational fields: purchase_order_id -> purchase.order; checklist_template_id -> purchase.custom.checklist.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "milestone.contract.template.purchase", "table_name": ""}
+{"text": "What are common use cases for sh.purchase.analysis.wizard?", "response": "To use the sh.purchase.analysis.wizard model, you need to provide values for required fields: sh_start_date, sh_end_date, sh_partner_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.purchase.analysis.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for mass.editing.wizard.", "response": "The mass.editing.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mass.editing.wizard", "table_name": ""}
+{"text": "What modules define account.asset.asset?", "response": "The account.asset.asset model is defined in module: om_account_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.asset.asset", "table_name": ""}
+{"text": "Tell me about the inter.transfer.company.line model.", "response": "The inter.transfer.company.line model represents inter.transfer.company.line in the ERP system. It contains 11 fields and is used to manage inter.transfer.company.line data. Key fields include: internal_id, product_id, quantity, price_unit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "inter.transfer.company.line", "table_name": ""}
+{"text": "What are the available fields for coupon.reward?", "response": "The coupon.reward model has 19 fields: reward_description, reward_product_id, reward_product_quantity, discount_type, discount_percentage, discount_apply_on, discount_specific_product_ids, discount_max_amount, discount_fixed_amount, reward_product_uom_id, discount_line_product_id, reward_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 5, integer: 2, selection: 3, float: 3, many2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "coupon.reward", "table_name": ""}
+{"text": "What is the account.general.ledger model?", "response": "The account.general.ledger model represents General Ledger Report in the ERP system. It contains 22 fields and is used to manage general ledger report data. Key fields include: journal_ids, account_ids, account_tag_ids, analytic_ids, analytic_tag_ids, display_account, titles, target_move, all_account, filter_detail, expand, date_from, date_to, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.general.ledger", "table_name": ""}
+{"text": "How do I use the sms.composer model?", "response": "To use the sms.composer model, you need to provide values for required fields: composition_mode, body. Readonly fields: res_ids_count, active_domain, active_domain_count, comment_single_recipient, recipient_valid_count, recipient_invalid_count, recipient_single_description, recipient_single_number, recipient_single_valid, sanitized_numbers, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sms.composer", "table_name": ""}
+{"text": "What foreign keys exist in bve.view?", "response": "The bve.view model has 9 relational fields: line_ids -> bve.view.line; field_ids -> bve.view.line; relation_ids -> bve.view.line; action_id -> ir.actions.act_window; view_id -> ir.ui.view; group_ids -> res.groups; user_ids -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: group_ids, user_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "bve.view", "table_name": ""}
+{"text": "Describe the implementation of report.sh_sale_reports.sh_sale_invoice_summary_doc.", "response": "The report.sh_sale_reports.sh_sale_invoice_summary_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_sale_invoice_summary_doc", "table_name": ""}
+{"text": "Which fields in update.historical.data are computed?", "response": "The update.historical.data model is defined in module: equip3_update_historical. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "update.historical.data", "table_name": ""}
+{"text": "How is report.dynamic_accounts_report.partner_ageing implemented technically?", "response": "The report.dynamic_accounts_report.partner_ageing model is defined in module: dynamic_accounts_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.dynamic_accounts_report.partner_ageing", "table_name": ""}
+{"text": "Tell me about the kitchen.production.record model.", "response": "The kitchen.production.record model represents Kitchen Production Record in the ERP system. It contains 79 fields and is used to manage kitchen production record data. Key fields include: name, company_id, is_branch_required, product_id, product_tmpl_id, product_qty, rejected_qty, product_uom_id, product_uom_category_id, bom_id, branch_id, confirm_date, state, move_raw_ids, move_finished_ids, move_byproduct_ids, location_src_id, location_dest_id, picking_type_id, date_planned_start, date_planned_finished, date_deadline, procurement_group_id, move_dest_ids, production_location_id, warehouse_id, product_tracking, account_move_ids, purchase_request_ids, internal_transfer_count, expiry_days, product_use_expiration_date, finished_lot_ids, byproduct_lot_ids, rejected_lot_ids, show_submit_button, is_autogenerate, default_finished_lot_qty, default_rejected_lot_qty, show_byproduct_lot_tab, byproduct_manual_product_ids, default_byproduct_lot_qty, default_next_byproduct_product_id, any_byproduct_is_autogenerate, all_byproduct_is_autogenerate, component_consumed_qty, svl_value, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kitchen.production.record", "table_name": ""}
+{"text": "What are common use cases for mailing.mailing.test?", "response": "To use the mailing.mailing.test model, you need to provide values for required fields: email_to, mass_mailing_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mailing.mailing.test", "table_name": ""}
+{"text": "Which fields in coupon.rule are computed?", "response": "The coupon.rule model is defined in module: coupon. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "coupon.rule", "table_name": ""}
+{"text": "How is finish.good.rework implemented technically?", "response": "The finish.good.rework model is defined in module: allfresh_mod_kitchen_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "finish.good.rework", "table_name": ""}
+{"text": "What business logic is in ai.chat.job?", "response": "To use the ai.chat.job model, you need to provide values for required fields: name, session_id, user_id, state, job_type. Readonly fields: state, current_step, error_message, queue_job_state, queue_job_exc_info, started_at, completed_at, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ai.chat.job", "table_name": ""}
+{"text": "Show me the relational structure of queue.jobs.to.done.", "response": "The queue.jobs.to.done model has 3 relational fields: job_ids -> queue.job; create_uid -> res.users; write_uid -> res.users. Many2many fields: job_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "queue.jobs.to.done", "table_name": ""}
+{"text": "What are the technical details of report_excel_import_wizard?", "response": "The report_excel_import_wizard model is defined in module: report_excel. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report_excel_import_wizard", "table_name": ""}
+{"text": "What are common use cases for account.print.journal?", "response": "To use the account.print.journal model, you need to provide values for required fields: sort_selection, journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.print.journal", "table_name": ""}
+{"text": "Which fields in sh.qc.alert.line are computed?", "response": "The sh.qc.alert.line model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.qc.alert.line", "table_name": ""}
+{"text": "What are the technical details of calendar.recurrence?", "response": "The calendar.recurrence model is defined in module: calendar. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "calendar.recurrence", "table_name": ""}
+{"text": "What are common use cases for restaurant.table?", "response": "To use the restaurant.table model, you need to provide values for required fields: name, shape. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "restaurant.table", "table_name": ""}
+{"text": "What data can be stored in overhead.material?", "response": "The overhead.material model has 12 fields: product, product_price, consumed, consumed_uom, mrp_wc_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "overhead.material", "table_name": ""}
+{"text": "What operations can I perform on setu.inventory.xyz.analysis.report?", "response": "To use the setu.inventory.xyz.analysis.report model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.xyz.analysis.report", "table_name": ""}
+{"text": "What foreign keys exist in account.loan.post?", "response": "The account.loan.post model has 5 relational fields: loan_id -> account.loan; journal_id -> account.journal; account_id -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.loan.post", "table_name": ""}
+{"text": "What are the relationships in target.activity?", "response": "The target.activity model has 21 relational fields: sales_team -> crm.team; head_team -> res.users; user_id -> res.users; company_id -> res.company; branch_id -> res.branch; activity_line -> target.activity.line; activity_line_res -> target.activity.line.res; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "target.activity", "table_name": ""}
+{"text": "Describe the implementation of purchase.agreement.approval.matrix.", "response": "The purchase.agreement.approval.matrix model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.agreement.approval.matrix", "table_name": ""}
+{"text": "What is the account.multipayment.difference model?", "response": "The account.multipayment.difference model represents Payment Difference Lines in the ERP system. It contains 13 fields and is used to manage payment difference lines data. Key fields include: name, payment_id, account_id, payment_amount, currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.multipayment.difference", "table_name": ""}
+{"text": "What are the technical details of account.pettycash.analysis?", "response": "The account.pettycash.analysis model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.pettycash.analysis", "table_name": ""}
+{"text": "How do I use the stock.rule model?", "response": "To use the stock.rule model, you need to provide values for required fields: name, location_id, route_id, procure_method, picking_type_id, auto, action. Readonly fields: route_company_id, picking_type_code_domain, rule_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.rule", "table_name": ""}
+{"text": "What data can be stored in pos.promotion.special.category?", "response": "The pos.promotion.special.category model has 19 fields: active, category_id, type, product_ids, category_ids, type_apply, count, discount, discount_fixed_amount, promotion_id, product_id, qty_free, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 5, selection: 2, many2many: 2, integer: 2, float: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.promotion.special.category", "table_name": ""}
+{"text": "What does the purchase.order model represent?", "response": "The purchase.order model represents Purchase Report Template in the ERP system. It contains 266 fields and is used to manage purchase report template data. Key fields include: priority, origin, partner_ref, date_approve, dest_address_id, order_line, notes, invoice_count, invoice_ids, invoice_status, date_calendar_start, fiscal_position_id, payment_term_id, product_id, user_id, currency_rate, mail_reminder_confirmed, mail_reception_confirmed, receipt_reminder_email, reminder_date_before_receipt, team_id, report_grids, grid_product_tmpl_id, grid_update, grid, requisition_id, is_quantity_copy, incoterm_id, picking_count, picking_ids, picking_type_id, default_location_dest_id_usage, group_id, is_shipped, effective_date, on_time_rate, active, complete_state, custom_checklist_ids, custom_checklist, product_template_id, digital_sign, purchase_show_signature, chk_sign_confirm, purchase_show_enable_other_sign, sign_by, designation, sign_on, document_count, order_history_line, order_report_id, rfq_report_id, purchase_tag_ids, purchase_url, report_token, text_message, po_extract_id, po_split_id, po_extract_count, po_split_count, sh_fully_ship, sh_partially_ship, sh_fully_paid, sh_partially_paid, sh_hidden_compute_field, agreement_id, cancel_lines, selected_order, sh_msg, sh_po_number, sh_purchase_order_id, sh_revision_po_id, po_count, sh_purchase_revision_config, visible_eval, mrp_production_count, sale_order_count, internal_id, inter_transfer_count, client_order_id, discount_method, discount_amount, discount_amt, discount_amt_line, merged, sh_purchase_barcode_mobile, sh_purchase_bm_is_cont_scan, sh_sale_order_id, apply_manual_currency_exchange, manual_currency_exchange_rate, active_manual_currency_rate, total_invoices_amount, down_payment_by, amount, dp_journal_id, hide_create_bill, payment_status, down_payment_amount, total_down_payment_amount, is_down_payment, report_template_id1, report_template_id, amount_to_text, is_vendor_pricelist, name, currency_id, po_expiry_date, po, exp_po, sent, is_goods_orders, is_services_orders, is_hold_purchase_order, approval_matrix_id, is_approval_matrix, state1, po_state, approved_matrix_ids, is_approve_button, approval_matrix_line_id, analytic_account_group_ids, company_id, branch_id, destination_location_id, is_delivery_receipt, destination_warehouse_id, discount_type, is_single_delivery_destination, analytic_accounting, is_revision_po, is_revision_created, revision_order_id, custom_checklist_template_ids, readonly_price, timezone_date, request_partner_id, date_order_assets, name2, date_order, milestone_template_id, milestone_purchase_ids, is_group_good_services_order, have_product_service, swo_ids, swo_count, is_taxes, actual_progress, remaining_progress, progress_paid, paid_swo, partner_invoice_id, available_partner_invoice_ids, product_brand_ids, is_product_brand_filter, is_service_work_order, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, is_service, show_analytic_tags, amount_untaxed, amount_tax, amount_total, discount_amt_before, discount_amt_line_before, amount_subtotal, tax_discount_policy, list_available_products, from_purchase_request, term_condition, term_condition_box, bo_count, blanket_ids, multilevel_disc, multi_discount, vendor_payment_terms, service_level_agreement_id, service_level_agreement_box, user_request_ids, vendor_invoice_documents_count, down_payment_discount_amount, tender_scope, is_submit_quotation, price_rating, not_editable, is_editable, tender_order_line, from_bo, is_btn_approval_matrix, state, is_blanket_cancel, open_tender, days_to_approve, purchase_order_duration_to_confirm, amount_saved_from_cost_savings, number_of_successful_cost_savings, partner_id, dp, journal_id, name_dp, direct_approval_matrix_id, is_approval_matrix_direct, approved_matrix_direct_ids, approved_matrix_direct_id, state_direct_on, state_direct_off, is_approve_button_direct, control, qty_limit, budget_limit, is_valid_coupon, applied_coupon_ids, generated_coupon_ids, no_code_promo_program_ids, code_promo_program_id, promo_code, client_order_ref, is_dropship, is_sale_order, customer_partner_id, customer_location_partner_id, branch_ids, is_assets_orders, import_reference, is_report_purchaseorder_printed, is_report_purchasequotation_printed, remark, rfq_type, discount_promotions_amount, date_planned, persentase_antar_badan, form_view_opened, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order", "table_name": ""}
+{"text": "How is pos.top.selling.wizard used in the system?", "response": "The pos.top.selling.wizard model represents POS Top Selling Wizard in the ERP system. It contains 14 fields and is used to manage pos top selling wizard data. Key fields include: start_dt, end_dt, report_type, no_product, top_selling, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.top.selling.wizard", "table_name": ""}
+{"text": "Describe the field structure of report.equip3_assembly_reports.report_assembly_production.", "response": "The report.equip3_assembly_reports.report_assembly_production model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_assembly_reports.report_assembly_production", "table_name": ""}
+{"text": "What is the res.config.installer model?", "response": "The res.config.installer model represents Config Installer in the ERP system. It contains 7 fields and is used to manage config installer data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.config.installer", "table_name": ""}
+{"text": "Tell me about the loyalty.wizard.reedem model.", "response": "The loyalty.wizard.reedem model represents Loyalty Redeem Wizard  in the ERP system. It contains 13 fields and is used to manage loyalty redeem wizard  data. Key fields include: order_credit_points, order_redeem_points, redeem_point, customer, loyalty_point, loyalty_balance, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "loyalty.wizard.reedem", "table_name": ""}
+{"text": "What methods are available in dev.rma.line?", "response": "The dev.rma.line model is defined in module: dev_rma. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "dev.rma.line", "table_name": ""}
+{"text": "How is choose.delivery.carrier implemented technically?", "response": "The choose.delivery.carrier model is defined in module: delivery. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "choose.delivery.carrier", "table_name": ""}
+{"text": "What are the technical details of pos.loyalty.reward?", "response": "The pos.loyalty.reward model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.loyalty.reward", "table_name": ""}
+{"text": "How to create records in ks.sales.forecast.result?", "response": "To use the ks.sales.forecast.result 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks.sales.forecast.result", "table_name": ""}
+{"text": "What business logic is in blacklist.partner.wiz?", "response": "To use the blacklist.partner.wiz 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "blacklist.partner.wiz", "table_name": ""}
+{"text": "Show me the relational structure of vendor.evaluation.", "response": "The vendor.evaluation model has 19 relational fields: vendor -> res.partner; manager -> res.users; user_id -> res.users; evaluation_template_id -> vendor.evaluation.template; evaluation_eval_ids -> vendor.evaluation.template.eval; branch_id -> res.branch; company_id -> res.company; vendor_res -> res.partner; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "vendor.evaluation", "table_name": ""}
+{"text": "Show me the relational structure of x.report.wizard.", "response": "The x.report.wizard model has 5 relational fields: pos_session_ids -> pos.session; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_session_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "x.report.wizard", "table_name": ""}
+{"text": "What are the available fields for product.template.barcode?", "response": "The product.template.barcode model has 13 fields: 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. Field types distribution: many2one: 6, char: 2, boolean: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.template.barcode", "table_name": ""}
+{"text": "What is the account.user.reminder model?", "response": "The account.user.reminder model represents Account USer Reminder in the ERP system. It contains 12 fields and is used to manage account user reminder data. Key fields include: name, company_id, branch_id, account_line_ids, reminder_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.user.reminder", "table_name": ""}
+{"text": "What foreign keys exist in account.pettycash.voucher.wizard?", "response": "The account.pettycash.voucher.wizard model has 10 relational fields: fund -> account.pettycash; partner_id -> res.users; ba_ca_journal_id -> account.journal; submitter_id -> res.users; currency_id -> res.currency; company_id -> res.company; voucher_line -> account.pettycash.voucher.wizard.line; move_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.pettycash.voucher.wizard", "table_name": ""}
+{"text": "How do I use the setu.inventory.overstock.report model?", "response": "To use the setu.inventory.overstock.report model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.overstock.report", "table_name": ""}
+{"text": "Show me the relational structure of replace.product.wizard.", "response": "The replace.product.wizard model has 4 relational fields: product_id -> product.product; replace_product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "replace.product.wizard", "table_name": ""}
+{"text": "How does website.track relate to other models?", "response": "The website.track model has 3 relational fields: visitor_id -> website.visitor; page_id -> website.page; product_id -> product.product. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.track", "table_name": ""}
+{"text": "Describe the many2many relations for account.payment.register.payment.difference.line.", "response": "The account.payment.register.payment.difference.line model has 6 relational fields: payment_register_id -> account.payment.register; account_id -> account.account; currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.payment.register.payment.difference.line", "table_name": ""}
+{"text": "Which fields in report.extra.content are computed?", "response": "The report.extra.content model is defined in module: general_template. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.extra.content", "table_name": ""}
+{"text": "Can you explain the purpose of ai.chat.message?", "response": "The ai.chat.message model represents AI Chat Message in the ERP system. It contains 30 fields and is used to manage ai chat message data. Key fields include: session_id, role, content, content_type, truncated_content, tokens_used, response_time, model_used, tools_used, tool_results, tool_call_id, message_metadata, user_id, is_thinking, thinking_data, is_user_message, is_compressed, content_compressed, is_not_processed, is_assistant_message, has_tools, finish_reason, quick_replies_cache, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ai.chat.message", "table_name": ""}
+{"text": "Tell me about the auditlog.rule model.", "response": "The auditlog.rule model represents Auditlog - Rule in the ERP system. It contains 20 fields and is used to manage auditlog - rule data. Key fields include: name, model_id, model_name, model_model, user_ids, log_read, log_write, log_unlink, log_create, log_type, state, action_id, capture_record, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "auditlog.rule", "table_name": ""}
+{"text": "What are common use cases for mrp.routing.workcenter?", "response": "To use the mrp.routing.workcenter model, you need to provide values for required fields: name, branch_id. Readonly fields: time_cycle, workorder_count, workcenter_ids, location_id, operation_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mrp.routing.workcenter", "table_name": ""}
+{"text": "Describe the account.open.chart model in Odoo.", "response": "The account.open.chart model represents Account Open chart in the ERP system. It contains 15 fields and is used to manage account open chart data. Key fields include: company_id, date_from, date_to, target_move, display_account, unfold, report_type, show_initial_balance, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.open.chart", "table_name": ""}
+{"text": "What methods are available in quotation.amount?", "response": "The quotation.amount model is defined in module: equip3_crm_meeting_overview. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "quotation.amount", "table_name": ""}
+{"text": "How is stock.rules.report used in the system?", "response": "The stock.rules.report model represents Stock Rules report in the ERP system. It contains 12 fields and is used to manage stock rules report data. Key fields include: product_id, product_tmpl_id, warehouse_ids, product_has_variants, so_route_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.rules.report", "table_name": ""}
+{"text": "Tell me about the account.asset.category model.", "response": "The account.asset.category model represents Asset category in the ERP system. It contains 41 fields and is used to manage asset category data. Key fields include: active, name, account_analytic_id, analytic_tag_ids, account_asset_id, account_depreciation_id, account_depreciation_expense_id, journal_id, company_id, method_number, method_period, method_progress_factor, method_time, method_end, prorata, open_asset, group_entries, type, branch_id, cut_off_asset_date, date_first_depreciation, account_sales_id, account_revaluation_surplus_id, account_revaluation_loss_id, method, is_monthly_depreciation, is_reset_january, account_sales_profit, account_sales_loss, dispose_account, sequence_id, set_sequence, sequence_number_next, is_fiscal_asset_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.asset.category", "table_name": ""}
+{"text": "List all fields in the blacklist.partner.wiz model.", "response": "The blacklist.partner.wiz model has 11 fields: partner_id, user_id, type, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, selection: 1, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "blacklist.partner.wiz", "table_name": ""}
+{"text": "What is the sh.purchase.product.profit.wizard model?", "response": "The sh.purchase.product.profit.wizard model represents Purchase Product Profit Wizard in the ERP system. It contains 14 fields and is used to manage purchase product profit wizard data. Key fields include: sh_start_date, sh_end_date, sh_partner_ids, report_by, sh_product_ids, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.purchase.product.profit.wizard", "table_name": ""}
+{"text": "Show me the fields of account.pettycash.fund.reconcile.", "response": "The account.pettycash.fund.reconcile model has 14 fields: fund, date, payable_account, reconciled_amount, move, vouchers, is_pettycash_voucher_approved, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, float: 1, many2many: 1, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.pettycash.fund.reconcile", "table_name": ""}
+{"text": "Tell me about the stock.scheduler.compute model.", "response": "The stock.scheduler.compute model represents Run Scheduler Manually in the ERP system. It contains 7 fields and is used to manage run scheduler manually data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.scheduler.compute", "table_name": ""}
+{"text": "What data can be stored in confirm.stock.sms?", "response": "The confirm.stock.sms model has 8 fields: pick_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "confirm.stock.sms", "table_name": ""}
+{"text": "Describe the implementation of approval.matrix.sale.reject.", "response": "The approval.matrix.sale.reject model is defined in module: equip3_sale_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "approval.matrix.sale.reject", "table_name": ""}
+{"text": "List all fields in the account.bank.statement.line.wizard model.", "response": "The account.bank.statement.line.wizard model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.bank.statement.line.wizard", "table_name": ""}
+{"text": "What models are connected to pos.sync.session.log?", "response": "The pos.sync.session.log model has 8 relational fields: send_from_session_id -> pos.session; send_to_session_id -> pos.session; user_id -> res.users; user_receive_id -> res.users; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.sync.session.log", "table_name": ""}
+{"text": "Can you explain the purpose of crm.activity.report?", "response": "The crm.activity.report model represents CRM Activity Analysis in the ERP system. It contains 21 fields and is used to manage crm activity analysis data. Key fields include: date, lead_create_date, date_conversion, date_deadline, date_closed, author_id, user_id, team_id, lead_id, body, subtype_id, mail_activity_type_id, country_id, company_id, stage_id, partner_id, lead_type, active, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.activity.report", "table_name": ""}
+{"text": "What modules define res.bank?", "response": "The res.bank model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.bank", "table_name": ""}
+{"text": "What modules define account.common.report?", "response": "The account.common.report model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.common.report", "table_name": ""}
+{"text": "Describe the many2many relations for coupon.program.", "response": "The coupon.program model has 22 relational fields: rule_id -> coupon.rule; reward_id -> coupon.reward; coupon_ids -> coupon.coupon; company_id -> res.company; currency_id -> res.currency; customer_category_ids -> customer.category; product_category_ids -> product.category; selected_customers_ids -> res.partner; selected_products_ids -> product.product; gift_product_id -> product.product; purchase_product_category_ids -> product.category; purchase_selected_customers_ids -> res.partner; purchase_selected_products_ids -> product.product; website_id -> website; create_uid -> res.users; write_uid -> res.users; applied_partner_ids -> res.partner; applied_product_ids -> product.product; reward_product_id -> product.product; discount_specific_product_ids -> product.product; reward_product_uom_id -> uom.uom; discount_line_product_id -> product.product. Many2many fields: customer_category_ids, product_category_ids, selected_customers_ids, selected_products_ids, purchase_product_category_ids, purchase_selected_customers_ids, purchase_selected_products_ids, applied_partner_ids, applied_product_ids, discount_specific_product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "coupon.program", "table_name": ""}
+{"text": "What business logic is in pos.zone?", "response": "To use the pos.zone 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.zone", "table_name": ""}
+{"text": "How is report.sh_sale_reports.sh_top_selling_product_doc used in the system?", "response": "The report.sh_sale_reports.sh_top_selling_product_doc model represents top selling product report abstract model in the ERP system. It contains 3 fields and is used to manage top selling product report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_sale_reports.sh_top_selling_product_doc", "table_name": ""}
+{"text": "How do I use the mail.thread.blacklist model?", "response": "To use the mail.thread.blacklist model, you need to provide values for required fields: none. Readonly fields: email_normalized, is_blacklisted, message_bounce, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.thread.blacklist", "table_name": ""}
+{"text": "What operations can I perform on force.done.memory?", "response": "To use the force.done.memory model, you need to provide values for required fields: blanket_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "force.done.memory", "table_name": ""}
+{"text": "Describe the stock.change.product.qty model in Odoo.", "response": "The stock.change.product.qty model represents Change Product Quantity in the ERP system. It contains 11 fields and is used to manage change product quantity data. Key fields include: product_id, product_tmpl_id, product_variant_count, new_quantity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.change.product.qty", "table_name": ""}
+{"text": "Which fields in account.fiscal.position.account are computed?", "response": "The account.fiscal.position.account model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.fiscal.position.account", "table_name": ""}
+{"text": "How to create records in material.request.matrix.reject?", "response": "To use the material.request.matrix.reject 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "material.request.matrix.reject", "table_name": ""}
+{"text": "Show me the fields of equip3.pos.membership.report.", "response": "The equip3.pos.membership.report model has 10 fields: name, member_code, company_id, date_joined, year_joined, member_point, total_order, id, display_name, __last_update. Field types distribution: char: 4, many2one: 1, datetime: 2, float: 1, integer: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "equip3.pos.membership.report", "table_name": ""}
+{"text": "Can you explain the purpose of utm.mixin?", "response": "The utm.mixin model represents UTM Mixin in the ERP system. It contains 6 fields and is used to manage utm mixin data. Key fields include: campaign_id, source_id, medium_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "utm.mixin", "table_name": ""}
+{"text": "Describe the report.sh_po_tender_management.report_analyze_quotations model in Odoo.", "response": "The report.sh_po_tender_management.report_analyze_quotations model represents analyze quotations report abstract model in the ERP system. It contains 3 fields and is used to manage analyze quotations report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_po_tender_management.report_analyze_quotations", "table_name": ""}
+{"text": "What business logic is in all.loyalty.setting?", "response": "To use the all.loyalty.setting model, you need to provide values for required fields: product_id, issue_date, expiry_date, loyalty_basis_on, company_id. Readonly fields: amount_footer, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "all.loyalty.setting", "table_name": ""}
+{"text": "How to create records in report.all.channels.sales?", "response": "To use the report.all.channels.sales model, you need to provide values for required fields: none. Readonly fields: name, partner_id, product_id, product_tmpl_id, date_order, user_id, categ_id, company_id, price_total, pricelist_id, country_id, price_subtotal, product_qty, analytic_account_id, team_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.all.channels.sales", "table_name": ""}
+{"text": "What are the technical details of ir.sequence?", "response": "The ir.sequence model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.sequence", "table_name": ""}
+{"text": "Describe the implementation of purchase.order.line.wizard.", "response": "The purchase.order.line.wizard model is defined in module: sh_so_po. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.order.line.wizard", "table_name": ""}
+{"text": "What are the available fields for product.price.quantity?", "response": "The product.price.quantity model has 10 fields: product_tmpl_id, price_unit, quantity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, float: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.price.quantity", "table_name": ""}
+{"text": "What are common use cases for access.group?", "response": "To use the access.group 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "access.group", "table_name": ""}
+{"text": "How is ir.qweb.field.many2many used in the system?", "response": "The ir.qweb.field.many2many model represents Qweb field many2many in the ERP system. It contains 3 fields and is used to manage qweb field many2many data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb.field.many2many", "table_name": ""}
+{"text": "Describe the ir.actions.todo model in Odoo.", "response": "The ir.actions.todo model represents Configuration Wizards in the ERP system. It contains 11 fields and is used to manage configuration wizards data. Key fields include: action_id, sequence, state, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.todo", "table_name": ""}
+{"text": "Describe the many2many relations for show.material.done.popup.", "response": "The show.material.done.popup model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "show.material.done.popup", "table_name": ""}
+{"text": "What methods are available in website.snippet.filter?", "response": "The website.snippet.filter model is defined in module: website. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.snippet.filter", "table_name": ""}
+{"text": "What methods are available in mrp.bom.operation?", "response": "The mrp.bom.operation model is defined in module: equip3_manuf_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.bom.operation", "table_name": ""}
+{"text": "Describe the field structure of report.dynamic_accounts_report.trial_balance.", "response": "The report.dynamic_accounts_report.trial_balance model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.dynamic_accounts_report.trial_balance", "table_name": ""}
+{"text": "How does material.request relate to other models?", "response": "The material.request model has 21 relational fields: create_uid -> res.users; requested_by -> res.users; destination_location_id -> stock.location; destination_warehouse_id -> stock.warehouse; company_id -> res.company; branch_id -> res.branch; product_line -> material.request.line; mr_approval_matrix_id -> mr.approval.matrix; approved_matrix_ids -> mr.approval.matrix.line; approval_matrix_line_id -> mr.approval.matrix.line; analytic_account_group_ids -> account.analytic.tag; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; write_uid -> res.users. Many2many fields: analytic_account_group_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "material.request", "table_name": ""}
+{"text": "What business logic is in approval.matrix.purchase.request?", "response": "To use the approval.matrix.purchase.request model, you need to provide values for required fields: name, company_id, branch_id, minimum_amt, maximum_amt. Readonly fields: company_id, is_purchase_request_department, is_good_services_order, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.purchase.request", "table_name": ""}
+{"text": "What fields does base.geo_provider have?", "response": "The base.geo_provider model has 9 fields: tech_name, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.geo_provider", "table_name": ""}
+{"text": "How to query sh.split.rfq.wizard data?", "response": "To use the sh.split.rfq.wizard model, you need to provide values for required fields: split_by. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.split.rfq.wizard", "table_name": ""}
+{"text": "Can you explain the purpose of report.excel.fields?", "response": "The report.excel.fields model represents Report Excel Fields in the ERP system. It contains 41 fields and is used to manage report excel fields data. Key fields include: sequence, active, show, cell, report_excel_section_id, group_by, aggregate, aggregate_ids, aggregate_id, having_operator, having_selection, having_param_ids, having_param_id, having_value_type, having_value_float, having_value_date, having_value_datetime, cumulative_having_field, sort_by, formula, formulas, check_root_model, root_model_id, root_model_name, model_field_selector, cumulative_model_field, field_type, image_bool, colOff, rowOff, cx, cy, locked_canvases_bool, description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.excel.fields", "table_name": ""}
+{"text": "What fields does sh.mrp.allow.qc.measurement have?", "response": "The sh.mrp.allow.qc.measurement model has 11 fields: product_id, sh_message, sh_quality_point_id, mrp_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, text: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.mrp.allow.qc.measurement", "table_name": ""}
+{"text": "What models are connected to format.address.mixin?", "response": "The format.address.mixin model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "format.address.mixin", "table_name": ""}
+{"text": "Tell me about the kpi.copy.template model.", "response": "The kpi.copy.template model represents Template Targets Replace in the ERP system. It contains 11 fields and is used to manage template targets replace data. Key fields include: period_id, template_id, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kpi.copy.template", "table_name": ""}
+{"text": "What is the sh.purchase.category.xls model?", "response": "The sh.purchase.category.xls model represents Purchase by Category Xls Report in the ERP system. It contains 9 fields and is used to manage purchase by category xls report data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.purchase.category.xls", "table_name": ""}
+{"text": "How is payment.sale.details.report used in the system?", "response": "The payment.sale.details.report model represents payment.sale.details.report in the ERP system. It contains 10 fields and is used to manage payment.sale.details.report data. Key fields include: name, total, details_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "payment.sale.details.report", "table_name": ""}
+{"text": "How is budget.change.req used in the system?", "response": "The budget.change.req model represents Budget Change Request in the ERP system. It contains 39 fields and is used to manage budget change request data. Key fields include: name, requested_id, budget_std_id, date, budget_line, state, approval_matrix, is_allowed_to_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, company_id, branch_id, currency_id, request_partner_id, state1, state2, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "budget.change.req", "table_name": ""}
+{"text": "What modules define pos.call.log?", "response": "The pos.call.log model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.call.log", "table_name": ""}
+{"text": "What models are connected to ks_dashboard_ninja.board?", "response": "The ks_dashboard_ninja.board model has 11 relational fields: ks_dashboard_items_ids -> ks_dashboard_ninja.item; ks_dashboard_top_menu_id -> ir.ui.menu; ks_dashboard_client_action_id -> ir.actions.client; ks_dashboard_menu_id -> ir.ui.menu; ks_dashboard_group_access -> res.groups; ks_dashboard_default_template -> ks_dashboard_ninja.board_template; ks_child_dashboard_ids -> ks_dashboard_ninja.child_board; ks_dashboard_defined_filters_ids -> ks_dashboard_ninja.board_defined_filters; ks_dashboard_custom_filters_ids -> ks_dashboard_ninja.board_custom_filters; create_uid -> res.users; write_uid -> res.users. Many2many fields: ks_dashboard_group_access.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks_dashboard_ninja.board", "table_name": ""}
+{"text": "What are the available fields for pos.call.log?", "response": "The pos.call.log model has 16 fields: min_id, max_id, call_domain, call_results, call_model, call_fields, active, write_date, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, __last_update. Field types distribution: integer: 3, char: 5, boolean: 1, datetime: 3, many2one: 4.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.call.log", "table_name": ""}
+{"text": "Describe the field structure of crm.phonecall.report.", "response": "The crm.phonecall.report model has 16 fields: user_id, team_id, priority, nbr_cases, state, create_date, delay_close, duration, delay_open, partner_id, company_id, opening_date, date_closed, id, display_name, __last_update. Field types distribution: many2one: 4, selection: 2, integer: 2, datetime: 4, float: 3, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.phonecall.report", "table_name": ""}
+{"text": "What does the sh.top.purchasing.excel.extended model represent?", "response": "The sh.top.purchasing.excel.extended model represents Excel Extended in the ERP system. It contains 9 fields and is used to manage excel extended data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.top.purchasing.excel.extended", "table_name": ""}
+{"text": "How is mrp.workcenter.productivity used in the system?", "response": "The mrp.workcenter.productivity model represents Workcenter Productivity Log in the ERP system. It contains 19 fields and is used to manage workcenter productivity log data. Key fields include: production_id, workcenter_id, company_id, workorder_id, user_id, loss_id, loss_type, description, date_start, date_end, duration, cost_already_recorded, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.workcenter.productivity", "table_name": ""}
+{"text": "What modules define pos.report.journal?", "response": "The pos.report.journal model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.report.journal", "table_name": ""}
+{"text": "What fields does setu.inventory.turnover.analysis.report have?", "response": "The setu.inventory.turnover.analysis.report model has 15 fields: stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, date: 2, many2many: 4, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.turnover.analysis.report", "table_name": ""}
+{"text": "What data can be stored in mailing.contact.subscription?", "response": "The mailing.contact.subscription model has 13 fields: contact_id, list_id, opt_out, unsubscription_date, message_bounce, is_blacklisted, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, boolean: 2, datetime: 4, integer: 2, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mailing.contact.subscription", "table_name": ""}
+{"text": "How to create records in invoice.payment.report.xls?", "response": "To use the invoice.payment.report.xls model, you need to provide values for required fields: none. Readonly fields: file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "invoice.payment.report.xls", "table_name": ""}
+{"text": "List all fields in the pos.report.category model.", "response": "The pos.report.category model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.report.category", "table_name": ""}
+{"text": "How does kpi.constant relate to other models?", "response": "The kpi.constant model has 4 relational fields: periods_ids -> kpi.period.value; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kpi.constant", "table_name": ""}
+{"text": "What are common use cases for sh.qc.alert?", "response": "To use the sh.qc.alert model, you need to provide values for required fields: team_id, user_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.qc.alert", "table_name": ""}
+{"text": "Describe the partner.blacklist.history model in Odoo.", "response": "The partner.blacklist.history model represents Partner Blacklist History in the ERP system. It contains 12 fields and is used to manage partner blacklist history data. Key fields include: user_id, type, reason, date, partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "partner.blacklist.history", "table_name": ""}
+{"text": "What methods are available in sh.mpo.merge.purchase.order.wizard?", "response": "The sh.mpo.merge.purchase.order.wizard model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.mpo.merge.purchase.order.wizard", "table_name": ""}
+{"text": "How is delivery.carrier used in the system?", "response": "The delivery.carrier model represents Shipping Methods in the ERP system. It contains 35 fields and is used to manage shipping methods data. Key fields include: name, active, sequence, integration_level, prod_environment, debug_logging, company_id, product_id, invoice_policy, country_ids, state_ids, zip_from, zip_to, margin, free_over, amount, can_generate_return, return_label_on_delivery, get_return_label_from_portal, fixed_price, price_rule_ids, website_description, delivery_type, website_published, website_id, is_published, can_publish, website_url, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "delivery.carrier", "table_name": ""}
+{"text": "What data can be stored in return.inter.transfer.company?", "response": "The return.inter.transfer.company model has 24 fields: sale_id, sale_count, invoice_count, bill_count, invoice_id, purchase_id, purchase_count, internal_id, internal_count, name, state, from_warehouse, currency_id, to_warehouse, pricelist_id, product_lines, product_return_moves, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, integer: 6, many2many: 1, char: 2, selection: 1, one2many: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "return.inter.transfer.company", "table_name": ""}
+{"text": "Which fields in base_import.tests.models.complex are computed?", "response": "The base_import.tests.models.complex model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.complex", "table_name": ""}
+{"text": "What fields does ir.qweb.field.integer have?", "response": "The ir.qweb.field.integer model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.integer", "table_name": ""}
+{"text": "How does journal.entries.report relate to other models?", "response": "The journal.entries.report model has 4 relational fields: account_id -> account.account; partner_id -> res.partner; analytic_account_id -> account.analytic.account; currency_id -> res.currency. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "journal.entries.report", "table_name": ""}
+{"text": "Can you explain the purpose of ir.actions.act_window.view?", "response": "The ir.actions.act_window.view model represents Action Window View in the ERP system. It contains 12 fields and is used to manage action window view data. Key fields include: sequence, view_id, act_window_id, multi, view_mode, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.act_window.view", "table_name": ""}
+{"text": "What foreign keys exist in base_import.tests.models.complex?", "response": "The base_import.tests.models.complex model has 3 relational fields: currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.complex", "table_name": ""}
+{"text": "Describe the implementation of ir.qweb.field.contact.", "response": "The ir.qweb.field.contact model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.qweb.field.contact", "table_name": ""}
+{"text": "Describe the implementation of product.packaging.", "response": "The product.packaging model is defined in module: product. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.packaging", "table_name": ""}
+{"text": "What fields does ks_custom_report.ks_column have?", "response": "The ks_custom_report.ks_column model has 25 fields: name, ks_cr_model_id, ks_model_field_chan, ks_model_name, ks_cr_field_id, ks_incl_search_filter, ks_incl_group_filter, sequence, ks_operator, ks_value, ks_visible_operator_fields, ks_visible_date_fields, ks_alter_values, ks_year, ks_month, ks_week, ks_day, ks_hour, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 4, boolean: 5, integer: 7, selection: 1, float: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks_custom_report.ks_column", "table_name": ""}
+{"text": "What are the technical details of sh.purchase.payment.report.wizard?", "response": "The sh.purchase.payment.report.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.payment.report.wizard", "table_name": ""}
+{"text": "What models are connected to account.payment.term?", "response": "The account.payment.term model has 15 relational fields: account_id -> account.account; line_ids -> account.payment.term.line; company_id -> res.company; branch_id -> res.branch; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.payment.term", "table_name": ""}
+{"text": "Describe the implementation of sh.sale.product.profit.xls.", "response": "The sh.sale.product.profit.xls model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.sale.product.profit.xls", "table_name": ""}
+{"text": "Show me the relational structure of assign.pr.line.wizard.", "response": "The assign.pr.line.wizard model has 7 relational fields: wizard_id -> assign.pr.wizard; pr_line_id -> purchase.request.line; user_id -> res.users; new_user_id -> res.users; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "assign.pr.line.wizard", "table_name": ""}
+{"text": "What fields does calendar.event.reschedule.wizard have?", "response": "The calendar.event.reschedule.wizard model has 10 fields: reschedule_date, reschedule_reason, have_reschedule_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 4, char: 2, boolean: 1, integer: 1, many2one: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "calendar.event.reschedule.wizard", "table_name": ""}
+{"text": "What operations can I perform on ir.ui.view.custom?", "response": "To use the ir.ui.view.custom model, you need to provide values for required fields: ref_id, user_id, arch. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.ui.view.custom", "table_name": ""}
+{"text": "How to query ir.ui.menu.category data?", "response": "To use the ir.ui.menu.category model, you need to provide values for required fields: sequence, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.ui.menu.category", "table_name": ""}
+{"text": "What are common use cases for sale.adv.wizard.product.line?", "response": "To use the sale.adv.wizard.product.line model, you need to provide values for required fields: none. Readonly fields: default_code, standard_price, uom_po_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.adv.wizard.product.line", "table_name": ""}
+{"text": "What are the relationships in res.users.access.report.wizard?", "response": "The res.users.access.report.wizard model has 4 relational fields: group_ids -> res.groups; user_tag_ids -> res.users.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: group_ids, user_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.users.access.report.wizard", "table_name": ""}
+{"text": "What operations can I perform on o2m.global.search.fields?", "response": "To use the o2m.global.search.fields model, you need to provide values for required fields: ttype. Readonly fields: related_model_id, ttype, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "o2m.global.search.fields", "table_name": ""}
+{"text": "How does kpi.help relate to other models?", "response": "The kpi.help model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kpi.help", "table_name": ""}
+{"text": "How is cust.credit.limit.xls implemented technically?", "response": "The cust.credit.limit.xls model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "cust.credit.limit.xls", "table_name": ""}
+{"text": "Tell me about the stock.warehouse model.", "response": "The stock.warehouse model represents Warehouse in the ERP system. It contains 98 fields and is used to manage warehouse data. Key fields include: active, partner_id, view_location_id, lot_stock_id, route_ids, wh_input_stock_loc_id, wh_qc_stock_loc_id, wh_output_stock_loc_id, wh_pack_stock_loc_id, mto_pull_id, pick_type_id, pack_type_id, out_type_id, in_type_id, int_type_id, crossdock_route_id, reception_route_id, delivery_route_id, warehouse_count, resupply_wh_ids, resupply_route_ids, show_resupply, sequence, manufacture_to_resupply, manufacture_pull_id, manufacture_mto_pull_id, pbm_mto_pull_id, sam_rule_id, manu_type_id, pbm_type_id, sam_type_id, manufacture_steps, pbm_route_id, pbm_loc_id, sam_loc_id, spacex, spacey, spacez, planimetry_image, count_sl, pos_type_id, buy_to_resupply, buy_pull_id, default_delivery_location_id, driver_ids, name, code, company_id, branch_id, lot_scrap_id, lot_expired_id, street, street2, zip, city, state_id, country_id, phone, responsible_users, reception_steps, delivery_steps, default_receipt_location_id, is_external_link, stock_count_cycle, pos_branch_id, analytic_tag_ids, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.warehouse", "table_name": ""}
+{"text": "Show me the relational structure of action.data.", "response": "The action.data model has 3 relational fields: action_id -> ir.actions.actions; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "action.data", "table_name": ""}
+{"text": "What fields does ir.ui.view.custom have?", "response": "The ir.ui.view.custom model has 10 fields: ref_id, user_id, arch, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, text: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.ui.view.custom", "table_name": ""}
+{"text": "Can you explain the purpose of mail.wizard.invite?", "response": "The mail.wizard.invite model represents Invite wizard in the ERP system. It contains 13 fields and is used to manage invite wizard data. Key fields include: res_model, res_id, partner_ids, channel_ids, message, send_mail, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.wizard.invite", "table_name": ""}
+{"text": "Which fields in report.sh_purchase_reports.sh_tv_top_vendors_doc are computed?", "response": "The report.sh_purchase_reports.sh_tv_top_vendors_doc model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_purchase_reports.sh_tv_top_vendors_doc", "table_name": ""}
+{"text": "What is the report.equip3_accounting_reports.debt_collection model?", "response": "The report.equip3_accounting_reports.debt_collection model represents Debt Collection Report in the ERP system. It contains 3 fields and is used to manage debt collection report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.debt_collection", "table_name": ""}
+{"text": "What models are connected to product.product?", "response": "The product.product model has 103 relational fields: product_tmpl_id -> product.template; product_template_attribute_value_ids -> product.template.attribute.value; barcode_line_ids -> product.template.barcode; stock_quant_ids -> stock.quant; stock_move_ids -> stock.move; orderpoint_ids -> stock.warehouse.orderpoint; putaway_rule_ids -> stock.putaway.rule; variant_bom_ids -> mrp.bom; bom_line_ids -> mrp.bom.line; stock_valuation_layer_ids -> stock.valuation.layer; product_cost_ids -> product.warehouse.cost; last_supplier_id -> res.partner; purchase_order_line_ids -> purchase.order.line; purchase_price_history_line_ids -> purchase.price.history; website_id -> website; product_variant_image_ids -> product.image; alternative_product_ids -> product.product; packaging_ids -> product.packaging; categ_id -> product.category; last_customer_id -> res.partner; product_lots_ids -> stock.production.lot; product_bom_id -> pos.product.bom; purchase_req_line_ids -> purchase.request.line; warehouse_price_ids -> product.warehouse.price; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users; currency_id -> res.currency; cost_currency_id -> res.currency; pricelist_id -> product.pricelist; uom_id -> uom.uom; uom_po_id -> uom.uom; seller_ids -> product.supplierinfo; variant_seller_ids -> product.supplierinfo; attribute_line_ids -> product.template.attribute.line; valid_product_template_attribute_line_ids -> product.template.attribute.line; product_variant_ids -> product.product; product_variant_id -> product.product; rating_ids -> rating.rating; taxes_id -> account.tax; property_account_income_id -> account.account; property_account_expense_id -> account.account; responsible_id -> res.users; property_stock_production -> stock.location; property_stock_inventory -> stock.location; location_id -> stock.location; warehouse_id -> stock.warehouse; route_from_categ_ids -> stock.location.route; bom_ids -> mrp.bom; deferred_revenue_category_id -> account.asset.category; email_template_id -> mail.template; property_account_creditor_price_difference -> account.account; pos_categ_id -> pos.category; route_ids -> stock.location.route; consignment_partner_id -> res.partner; optional_product_ids -> product.template; accessory_product_ids -> product.product; website_ribbon_id -> product.ribbon; public_categ_ids -> product.public.category; product_template_image_ids -> product.image; bi_pack_ids -> bi.product.pack; project_template_id -> project.project; multi_companies_all -> res.company; product_brand_id -> product.brand; project_id -> project.project; brand_attribute_id -> product.attribute; brand_ids -> product.brand; branch_id -> res.branch; secondary_uom_id -> uom.uom; multi_warehouses_all -> stock.warehouse; product_brand_ids -> product.brand; def_packaging_id -> product.packaging; group_stock_ids -> product.packaging; reordering_rules_ids -> stock.warehouse.orderpoint; variant_attribute_value_ids -> product.variant.attribute.value; product_ratio_line -> product.ratio.line; uom_categ_id -> uom.category; merchendise_id -> merchendise.code; asset_category_id -> account.asset.category; company_id -> res.company; sell_ids -> product.supplierinfo; template_purchase_price_history_line_ids -> purchase.price.history; combo_option_id -> combo.option; combo_option_items -> combo.option.item; pos_combo_item_ids -> pos.combo.item; pos_categ_ids -> pos.category; price_uom_ids -> product.uom.price; cross_ids -> product.cross; product_price_quantity_ids -> product.price.quantity; combo_limit_ids -> pos.combo.limit; uom_ids -> uom.uom; note_ids -> pos.note; tag_ids -> pos.tag; pos_branch_id -> res.branch; supplier_taxes_id -> account.tax. Many2many fields: product_template_attribute_value_ids, purchase_price_history_line_ids, alternative_product_ids, packaging_ids, message_partner_ids, message_channel_ids, valid_product_template_attribute_line_ids, taxes_id, route_from_categ_ids, route_ids, optional_product_ids, accessory_product_ids, public_categ_ids, multi_companies_all, brand_ids, multi_warehouses_all, product_brand_ids, group_stock_ids, template_purchase_price_history_line_ids, pos_categ_ids, uom_ids, note_ids, tag_ids, supplier_taxes_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.product", "table_name": ""}
+{"text": "What are common use cases for merchendise.code?", "response": "To use the merchendise.code 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "merchendise.code", "table_name": ""}
+{"text": "How is open.stock.series implemented technically?", "response": "The open.stock.series model is defined in module: stock_qty_forecast. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "open.stock.series", "table_name": ""}
+{"text": "Describe the field structure of material.request.matrix.reject.", "response": "The material.request.matrix.reject model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "material.request.matrix.reject", "table_name": ""}
+{"text": "How to query orderwizline.orderwizline data?", "response": "To use the orderwizline.orderwizline model, you need to provide values for required fields: product_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "orderwizline.orderwizline", "table_name": ""}
+{"text": "How is account.budget.post implemented technically?", "response": "The account.budget.post model is defined in module: om_account_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.budget.post", "table_name": ""}
+{"text": "Describe the website.published.multi.mixin model in Odoo.", "response": "The website.published.multi.mixin model represents Multi Website Published Mixin in the ERP system. It contains 8 fields and is used to manage multi website published mixin data. Key fields include: website_published, website_id, is_published, can_publish, website_url, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "website.published.multi.mixin", "table_name": ""}
+{"text": "How to query account.reconcile.model.template data?", "response": "To use the account.reconcile.model.template model, you need to provide values for required fields: chart_template_id, name, sequence, rule_type, match_nature. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.reconcile.model.template", "table_name": ""}
+{"text": "What models are connected to expiry.picking.confirmation?", "response": "The expiry.picking.confirmation model has 6 relational fields: lot_ids -> stock.production.lot; picking_ids -> stock.picking; production_ids -> mrp.production; workorder_id -> mrp.workorder; create_uid -> res.users; write_uid -> res.users. Many2many fields: lot_ids, picking_ids, production_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "expiry.picking.confirmation", "table_name": ""}
+{"text": "What does the blanket.quotation model represent?", "response": "The blanket.quotation model represents blanket.quotation in the ERP system. It contains 8 fields and is used to manage blanket.quotation data. Key fields include: wiz_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "blanket.quotation", "table_name": ""}
+{"text": "Which fields in asset.asset.revalue.wizard are computed?", "response": "The asset.asset.revalue.wizard model is defined in module: equip3_accounting_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "asset.asset.revalue.wizard", "table_name": ""}
+{"text": "What are the available fields for ir.module.module.exclusion?", "response": "The ir.module.module.exclusion model has 11 fields: name, module_id, exclusion_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.module.module.exclusion", "table_name": ""}
+{"text": "How to query sales.margin.xls data?", "response": "To use the sales.margin.xls 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sales.margin.xls", "table_name": ""}
+{"text": "What does the pos.payment.report model represent?", "response": "The pos.payment.report model represents POS Payment Report in the ERP system. It contains 14 fields and is used to manage pos payment report data. Key fields include: date, payment_date, payment_method_id, config_id, order_id, session_id, company_id, pos_branch_id, amount, currency_id, partner_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.payment.report", "table_name": ""}
+{"text": "What foreign keys exist in report.excel.fields.sql?", "response": "The report.excel.fields.sql model has 3 relational fields: report_excel_section_id -> report.excel.section; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.excel.fields.sql", "table_name": ""}
+{"text": "How is ir.qweb.field.date used in the system?", "response": "The ir.qweb.field.date model represents Qweb Field Date in the ERP system. It contains 3 fields and is used to manage qweb field date data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb.field.date", "table_name": ""}
+{"text": "Show me the fields of force.done.memory.", "response": "The force.done.memory model has 11 fields: blanket_id, qty, remaining_qty, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, float: 2, text: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "force.done.memory", "table_name": ""}
+{"text": "Describe the field structure of product.warehouse.cost.", "response": "The product.warehouse.cost model has 10 fields: product_id, product_cost_line_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.warehouse.cost", "table_name": ""}
+{"text": "Show me the relational structure of sale.order.option.", "response": "The sale.order.option model has 7 relational fields: order_id -> sale.order; line_id -> sale.order.line; product_id -> product.product; uom_id -> uom.uom; product_uom_category_id -> uom.category; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.option", "table_name": ""}
+{"text": "What are the available fields for resource.calendar.leaves?", "response": "The resource.calendar.leaves model has 14 fields: name, company_id, calendar_id, date_from, date_to, resource_id, time_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 5, datetime: 5, selection: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "resource.calendar.leaves", "table_name": ""}
+{"text": "What are the available fields for expiry.picking.confirmation?", "response": "The expiry.picking.confirmation model has 13 fields: lot_ids, picking_ids, description, show_lots, production_ids, workorder_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 3, char: 2, boolean: 1, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "expiry.picking.confirmation", "table_name": ""}
+{"text": "What foreign keys exist in account.common.journal.report?", "response": "The account.common.journal.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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.common.journal.report", "table_name": ""}
+{"text": "What data can be stored in stock.inventory.approval.matrix.line?", "response": "The stock.inventory.approval.matrix.line model has 34 fields: sequence, user_ids, minimum_approver, si_approval_matrix, st_inv_id, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 8, many2many: 4, many2one: 6, text: 1, datetime: 4, char: 2, boolean: 6, one2many: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.inventory.approval.matrix.line", "table_name": ""}
+{"text": "What are the technical details of portal.share?", "response": "The portal.share model is defined in module: portal. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "portal.share", "table_name": ""}
+{"text": "Which fields in change.password.user are computed?", "response": "The change.password.user model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "change.password.user", "table_name": ""}
+{"text": "What are the available fields for limit.request.wizard?", "response": "The limit.request.wizard model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "limit.request.wizard", "table_name": ""}
+{"text": "What are the technical details of sh.purchase.update.mass.tag.wizard?", "response": "The sh.purchase.update.mass.tag.wizard model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.update.mass.tag.wizard", "table_name": ""}
+{"text": "Describe the implementation of pos.gift.card.exchange.history.", "response": "The pos.gift.card.exchange.history model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.gift.card.exchange.history", "table_name": ""}
+{"text": "What are common use cases for base_import.tests.models.m2o?", "response": "To use the base_import.tests.models.m2o 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base_import.tests.models.m2o", "table_name": ""}
+{"text": "What fields does generate.closing.entries.confirmation.wizard have?", "response": "The generate.closing.entries.confirmation.wizard model has 14 fields: name, fiscal_year_id, closing_entry_date, journal_id, description, summary_account_id, retained_earnings_account_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 2, many2one: 6, date: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "generate.closing.entries.confirmation.wizard", "table_name": ""}
+{"text": "Describe the pos.category model in Odoo.", "response": "The pos.category model represents Point of Sale Category in the ERP system. It contains 23 fields and is used to manage point of sale category data. Key fields include: name, parent_id, child_id, sequence, image_128, Minimum_amount, amount_footer, is_category_combo, sale_limit_time, from_time, to_time, submit_all_pos, pos_branch_ids, pos_config_ids, category_type, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.category", "table_name": ""}
+{"text": "What models are connected to account.full.reconcile?", "response": "The account.full.reconcile model has 5 relational fields: partial_reconcile_ids -> account.partial.reconcile; reconciled_line_ids -> account.move.line; exchange_move_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.full.reconcile", "table_name": ""}
+{"text": "Describe the sh.custom.tab.purchase model in Odoo.", "response": "The sh.custom.tab.purchase model represents Custom Tab purchase in the ERP system. It contains 15 fields and is used to manage custom tab purchase data. Key fields include: name, label, groups, sequence, view_id, tab_list, invisible_tab, sh_position, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.custom.tab.purchase", "table_name": ""}
+{"text": "Describe the field structure of pos.coupon.program.", "response": "The pos.coupon.program model has 28 fields: active, name, coupon_name, type_apply, base_on_product_id, minimum_purchase_quantity, sequence_generate_method, manual_input_sequence, start_date, end_date, no_of_usage, no_of_used, company_id, state, reward_type, reward_product_id, reward_quantity, reward_discount_type, reward_discount_amount, reward_max_discount_amount, pos_coupon_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, char: 4, selection: 5, many2one: 5, integer: 7, datetime: 5, float: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.coupon.program", "table_name": ""}
+{"text": "Show me the relational structure of res.country.", "response": "The res.country model has 6 relational fields: address_view_id -> ir.ui.view; currency_id -> res.currency; country_group_ids -> res.country.group; state_ids -> res.country.state; create_uid -> res.users; write_uid -> res.users. Many2many fields: country_group_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.country", "table_name": ""}
+{"text": "Describe the budget.purchase.lines model in Odoo.", "response": "The budget.purchase.lines model represents Budget Line in the ERP system. It contains 30 fields and is used to manage budget line data. Key fields include: name, purchase_budget_id, analytic_account_id, analytic_group_id, product_budget, date_from, date_to, paid_date, currency_id, planned_amount, practical_amount, practical_amount_temp, remaining_amount, theoritical_amount, percentage, company_id, is_above_budget, purchase_budget_state, parent_analytic_account_id, account_tag_ids, product_id, purchase_order_line_budget_id, eer, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "budget.purchase.lines", "table_name": ""}
+{"text": "How to query ir.qweb.field.integer data?", "response": "To use the ir.qweb.field.integer model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.integer", "table_name": ""}
+{"text": "Show me the fields of account.debt.collection.line.", "response": "The account.debt.collection.line model has 28 fields: debt_collection_id, invoice_id, invoice_date, currency_id, amount_invoice, amount_residual, state, journal_id, date, amount, is_full_collect, payment_id, is_pic_line, user_id, partner_id, deadline_date, invoice_due_date, total_due_date, debt_coll_pic, invoice_week_number, invoice_week_start, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 10, date: 5, monetary: 3, selection: 1, boolean: 2, integer: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.debt.collection.line", "table_name": ""}
+{"text": "What modules define res.users.access.report.record?", "response": "The res.users.access.report.record model is defined in module: report_user_access_right. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.access.report.record", "table_name": ""}
+{"text": "How to create records in kitchen.cooking.list.line?", "response": "To use the kitchen.cooking.list.line model, you need to provide values for required fields: list_id. Readonly fields: uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "kitchen.cooking.list.line", "table_name": ""}
+{"text": "How to create records in sh.purchase.analysis.xls?", "response": "To use the sh.purchase.analysis.xls model, you need to provide values for required fields: none. Readonly fields: file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.purchase.analysis.xls", "table_name": ""}
+{"text": "What operations can I perform on account.fiscal.year?", "response": "To use the account.fiscal.year model, you need to provide values for required fields: name, date_from, date_to, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.fiscal.year", "table_name": ""}
+{"text": "List all fields in the mass.editing.line model.", "response": "The mass.editing.line model has 13 fields: sequence, server_action_id, model_id, field_id, widget_option, apply_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 5, char: 2, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mass.editing.line", "table_name": ""}
+{"text": "Describe the many2many relations for base_import.tests.models.preview.", "response": "The base_import.tests.models.preview model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.preview", "table_name": ""}
+{"text": "What modules define website.mass_mailing.popup?", "response": "The website.mass_mailing.popup model is defined in module: website_mass_mailing. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.mass_mailing.popup", "table_name": ""}
+{"text": "Show me the relational structure of base.geocoder.", "response": "The base.geocoder model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.geocoder", "table_name": ""}
+{"text": "Which fields in base_import.tests.models.char.states are computed?", "response": "The base_import.tests.models.char.states model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.char.states", "table_name": ""}
+{"text": "What modules define base_import.tests.models.complex?", "response": "The base_import.tests.models.complex model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.complex", "table_name": ""}
+{"text": "Which fields in stock.scrap.request are computed?", "response": "The stock.scrap.request model is defined in module: equip3_inventory_control. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.scrap.request", "table_name": ""}
+{"text": "Describe the ir.actions.client model in Odoo.", "response": "The ir.actions.client model represents Client Action in the ERP system. It contains 20 fields and is used to manage client action data. Key fields include: name, type, tag, target, res_model, context, params, params_store, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.client", "table_name": ""}
+{"text": "What business logic is in target.kpi?", "response": "To use the target.kpi model, you need to provide values for required fields: user_id, target_based_on_ids, from_date, to_date, target_on. Readonly fields: name, purchase_team_id, user_id, company_id, target_based_on_ids, main_target, from_date, to_date, target_on, target_left, kpi_progress, current_achievement, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "target.kpi", "table_name": ""}
+{"text": "Show me the relational structure of base_import.tests.models.preview.", "response": "The base_import.tests.models.preview model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.preview", "table_name": ""}
+{"text": "How do I use the payment.voucher.line model?", "response": "To use the payment.voucher.line model, you need to provide values for required fields: none. Readonly fields: invoice_date, currency_id, state, voucher_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "payment.voucher.line", "table_name": ""}
+{"text": "What does the account.bank.statement.import model represent?", "response": "The account.bank.statement.import model represents Import Bank Statement in the ERP system. It contains 8 fields and is used to manage import bank statement data. Key fields include: attachment_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.bank.statement.import", "table_name": ""}
+{"text": "How is account.tax used in the system?", "response": "The account.tax model represents Tax in the ERP system. It contains 58 fields and is used to manage tax data. Key fields include: tax_paid_account, price_include_total, pay_separately, name, type_tax_use, tax_scope, amount_type, active, company_id, children_tax_ids, sequence, amount, description, price_include, include_base_amount, analytic, tax_group_id, hide_tax_exigibility, tax_exigibility, cash_basis_transition_account_id, invoice_repartition_line_ids, refund_repartition_line_ids, tax_fiscal_country_id, country_code, branch_id, is_ppn, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.tax", "table_name": ""}
+{"text": "How do I use the pos.loyalty.point model?", "response": "To use the pos.loyalty.point model, you need to provide values for required fields: partner_id, type. Readonly fields: member_point, member_phone, member_type, member_type_code, is_return, remaining_point, company_id, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.loyalty.point", "table_name": ""}
+{"text": "Which fields in crm.activity.report are computed?", "response": "The crm.activity.report model is defined in module: crm. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.activity.report", "table_name": ""}
+{"text": "What is the ir.actions.act_window model?", "response": "The ir.actions.act_window model represents Action Window in the ERP system. It contains 29 fields and is used to manage action window data. Key fields include: name, type, view_id, domain, context, res_id, res_model, target, view_mode, usage, view_ids, views, limit, groups_id, search_view_id, filter, search_view, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.act_window", "table_name": ""}
+{"text": "What methods are available in account.automatic.entry.wizard?", "response": "The account.automatic.entry.wizard model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.automatic.entry.wizard", "table_name": ""}
+{"text": "What models are connected to product.template.attribute.exclusion?", "response": "The product.template.attribute.exclusion model has 5 relational fields: product_template_attribute_value_id -> product.template.attribute.value; product_tmpl_id -> product.template; value_ids -> product.template.attribute.value; create_uid -> res.users; write_uid -> res.users. Many2many fields: value_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.template.attribute.exclusion", "table_name": ""}
+{"text": "What are the available fields for snailmail.letter.missing.required.fields?", "response": "The snailmail.letter.missing.required.fields model has 15 fields: partner_id, letter_id, street, street2, zip, city, state_id, country_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, char: 5, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "snailmail.letter.missing.required.fields", "table_name": ""}
+{"text": "Show me the relational structure of report.stock.report_stock_rule.", "response": "The report.stock.report_stock_rule model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.stock.report_stock_rule", "table_name": ""}
+{"text": "What are the relationships in combo.option?", "response": "The combo.option model has 3 relational fields: item_ids -> combo.option.item; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "combo.option", "table_name": ""}
+{"text": "How to create records in report.point_of_sale.report_invoice?", "response": "To use the report.point_of_sale.report_invoice model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.point_of_sale.report_invoice", "table_name": ""}
+{"text": "What does the report.sh_purchase_reports.sh_representative_report_doc model represent?", "response": "The report.sh_purchase_reports.sh_representative_report_doc model represents purchase person report abstract model in the ERP system. It contains 3 fields and is used to manage purchase person report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_representative_report_doc", "table_name": ""}
+{"text": "What fields does purchase.team.analysis have?", "response": "The purchase.team.analysis model has 20 fields: days_to_approve, purchase_order_duration_to_confirm, amount_saved_from_cost_savings, number_of_successful_cost_savings, avg_amount_saved_from_cost_savings, avg_number_of_successful_cost_savings, user_id, purchase_ids, kpi_target, cost_saving_percentage, amount_purchased, cost_saving, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 10, many2one: 4, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.team.analysis", "table_name": ""}
+{"text": "What is the report.equip3_pos_general.pos_sale_report_template model?", "response": "The report.equip3_pos_general.pos_sale_report_template model represents Template Report of sale in the ERP system. It contains 3 fields and is used to manage template report of sale data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_pos_general.pos_sale_report_template", "table_name": ""}
+{"text": "What foreign keys exist in account.loan?", "response": "The account.loan model has 23 relational fields: partner_id -> res.partner; company_id -> res.company; line_ids -> account.loan.line; currency_id -> res.currency; journal_id -> account.journal; leased_asset_account_id -> account.account; product_id -> product.product; interests_product_id -> product.product; move_ids -> account.move; short_term_loan_account_id -> account.account; long_term_loan_account_id -> account.account; interest_expenses_account_id -> account.account; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.loan", "table_name": ""}
+{"text": "Describe the field structure of limit.request.", "response": "The limit.request model has 66 fields: name, partner_id, limit_type, limit_type_old, limit_type_new, credit_amount, last_credit_limit, open_inv_no, last_open_inv_no, new_max_invoice, last_max_invoice, description, state, state1, state2, branch_id, limit_approval_matrix, approval_ids, approval_matrix_line_id, user_approval_ids, current_user, approval, approval2, new_amount, last_amount, is_approve_button, user_id, is_credit_limit_brand, product_brand_ids, brand_ids, company_id, 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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 15, selection: 8, float: 8, text: 1, one2many: 6, many2many: 4, boolean: 9, date: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "limit.request", "table_name": ""}
+{"text": "How is wizard.asset.create implemented technically?", "response": "The wizard.asset.create model is defined in module: equip3_accounting_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "wizard.asset.create", "table_name": ""}
+{"text": "How does web_editor.converter.test relate to other models?", "response": "The web_editor.converter.test model has 3 relational fields: many2one -> web_editor.converter.test.sub; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "web_editor.converter.test", "table_name": ""}
+{"text": "What models are connected to new.product?", "response": "The new.product model has 3 relational fields: top_id -> sh.tsp.top.selling.product.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "new.product", "table_name": ""}
+{"text": "What are the technical details of stock.lot.serialize.line?", "response": "The stock.lot.serialize.line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.lot.serialize.line", "table_name": ""}
+{"text": "Describe the debt.collection.report model in Odoo.", "response": "The debt.collection.report model represents Debt Collection Report in the ERP system. It contains 16 fields and is used to manage debt collection report data. Key fields include: partner_ids, user_ids, journal_ids, state, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "debt.collection.report", "table_name": ""}
+{"text": "Describe the field structure of sale.order.", "response": "The sale.order model has 289 fields: origin, client_order_ref, reference, is_expired, require_signature, require_payment, create_date, user_id, pricelist_id, currency_id, invoice_count, invoice_ids, invoice_status, amount_by_group, currency_rate, fiscal_position_id, team_id, signature, signed_by, signed_on, amount_undiscounted, type_name, transaction_ids, authorized_transaction_ids, show_update_pricelist, tag_ids, applied_coupon_ids, generated_coupon_ids, reward_amount, no_code_promo_program_ids, code_promo_program_id, promo_code, sale_order_option_ids, purchase_order_count, incoterm, picking_policy, picking_ids, delivery_count, procurement_group_id, effective_date, expected_date, json_popover, show_json_popover, website_order_line, cart_quantity, only_services, is_abandoned_cart, cart_recovery_email_sent, website_id, conversation_id, internal_id, inter_transfer_count, client_order_id, discount_amt, discount_amt_line, warranty_sale, recurring_rule_type, recurring_interval, delivery_message, delivery_rating_success, delivery_set, recompute_delivery_price, is_all_service, is_process_rma, merged, name, parent_saleorder_id, order_revised_count, so_number, margin, margin_percent, mrp_production_count, note, report_grids, grid_product_tmpl_id, grid_update, grid, tasks_ids, tasks_count, visible_project, project_ids, sh_sale_barcode_mobile, sh_sale_bm_is_cont_scan, partner_credit_conform, sh_purchase_count, sh_so_po_is_show_so_to_po_btn_flag, apply_manual_currency_exchange, manual_currency_exchange_rate, company_currency_id, active_manual_currency_rate, warning_stock, opportunity_id, report_template_id1, report_template_id, amount_to_text, timesheet_ids, timesheet_count, project_id, timesheet_encode_uom_id, timesheet_total_duration, rfm_segment_id, amount_delivery, order_credit_points, order_redeem_points, redeem_value, is_from_website, loyalty_point_credit, order_source, driver_id, order_driver_message_ids, payment_status_with_driver, latitude, longitude, distance_btn_2_loc, sale_order_comm_ids, commission_calc, commission_pay_on, stage_id, order_line_count, date_order, validity_date, payment_term_id, sale_order_template_id, sale_state, delivered_state, sale_state_1, state_2, revised_state, approval_matrix_state, approval_matrix_state_1, branch_id, account_tag, account_tag_ids, analytic_account_id, approving_matrix_sale_id, approved_matrix_ids, is_customer_approval_matrix, hide_proforma, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, is_quotation_cancel, company_id, deduction_ids, analytic_accounting, terms_conditions_id, group_multi_do, is_single_warehouse, is_single_delivery_date, commitment_date, revised_sale_order_ids, revised_sale_order_id, is_revision_so, is_print_report, qty_delivered, count_delivered, multilevel_disc, multi_discount, discount_method, discount_amount, date_confirm, is_sale_order, partner_name, is_hidden_button, lock_sale_order, readonly_disc, readonly_multi, brand, partner_invoice_id, partner_shipping_id, reject_reason, sale_fully_delivered, sale_partially_delivery, sale_fully_paid, sale_partially_paid, sale_hidden_compute_field, date_kanban, is_down_payment, down_payment_amount, total_amount_without_dp, carrier_id, amount_untaxed, amount_tax, amount_total, order_line, discount_type, city_id, state_id, show_mobile, is_external_link, tax_discount_policy, discount_amt_before, discount_amt_line_before, amount_subtotal, warehouse_id, warehouse_new_id, delivery_state, payment_status_driver, approving_matrix_limit_id, approved_matrix_limit_ids, is_over_limit_validation, is_limit_matrix_filled, is_direct_confirm, limit_approval_matrix_line_id, is_approve_button_limit, limit_matrix_state, limit_matrix_state_1, limit_matrix_state_2, sale_limit_state, sale_limit_state_1, sale_limit_state_2, sale_limit_state_3, sale_limit_state_4, sale_limit_state_5, approval_matrix_state_2, approval_matrix_state_3, approval_matrix_state_4, approval_matrix_state_5, approval_matrix_state_6, approval_matrix_state_7, approval_matrix_state_8, approval_matrix_state_9, creditlim, hide_button_revise, lock_order_line, have_available_customer_voucher, customer_voucher_used_ids, cashback_line_ids, show_cashback, cn_cashback_ids, cn_cashback_count, title, partner_id, book_order, ean13, pos_config_id, pos_location_id, delivery_date, delivered_date, delivery_address, delivery_phone, payment_partial_amount, payment_partial_method_id, insert, state, pos_branch_id, pos_order_id, is_self_pickup, is_dropship, purchase_request_ids, purchase_request_count, remark, 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, write_uid, write_date, __last_update. Field types distribution: char: 32, boolean: 66, datetime: 10, many2one: 55, integer: 25, many2many: 15, selection: 37, binary: 2, float: 14, one2many: 18, date: 4, monetary: 9, text: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.order", "table_name": ""}
+{"text": "Tell me about the ir.ui.view model.", "response": "The ir.ui.view model represents View in the ERP system. It contains 41 fields and is used to manage view data. Key fields include: name, model, key, priority, arch, arch_base, arch_db, arch_fs, arch_updated, arch_prev, inherit_id, inherit_children_ids, field_parent, model_data_id, xml_id, groups_id, mode, active, customize_show, is_seo_optimized, website_meta_title, website_meta_description, website_meta_keywords, website_meta_og_img, seo_name, website_id, page_ids, first_page_id, track, visibility, visibility_password, visibility_password_display, theme_template_id, type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.ui.view", "table_name": ""}
+{"text": "What is the generate.pos.voucher model?", "response": "The generate.pos.voucher model represents Generate POS voucher in the ERP system. It contains 35 fields and is used to manage generate pos voucher data. Key fields include: customer_id, code, start_date, end_date, maximum_discount_amount, minimum_purchase_amount, limit_restrict_product_ids, pos_category_ids, state, value, apply_type, method, use_date, user_id, source, use_history_ids, name, company_id, no_of_usage, no_of_used, minimum_spend, is_customize_sequence, sequence_generate_method, manual_input_sequence, running_number_prefix, running_number_digit, running_number_current_sequence, brand_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "generate.pos.voucher", "table_name": ""}
+{"text": "What data can be stored in customer.statement?", "response": "The customer.statement model has 47 fields: name, partner_ids, overdue_template, company_ids, report_currency_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, sequence_prefix, sequence_number, journal_ids, date_from, date_to, target_move, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 3, many2many: 5, many2one: 7, one2many: 4, selection: 3, char: 7, date: 4, boolean: 5, integer: 6, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "customer.statement", "table_name": ""}
+{"text": "How to create records in pos.generate.efaktur.other?", "response": "To use the pos.generate.efaktur.other model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.generate.efaktur.other", "table_name": ""}
+{"text": "Show me the fields of account.fiscal.year.", "response": "The account.fiscal.year model has 11 fields: name, date_from, date_to, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, date: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.fiscal.year", "table_name": ""}
+{"text": "Describe the implementation of report.point_of_sale.report_invoice.", "response": "The report.point_of_sale.report_invoice model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.point_of_sale.report_invoice", "table_name": ""}
+{"text": "What are the available fields for nsfp.registration?", "response": "The nsfp.registration model has 15 fields: record_id, fiscal_year, start, end, last_number, registration_date, is_use, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 4, char: 5, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "nsfp.registration", "table_name": ""}
+{"text": "Describe the field structure of stock.package.destination.", "response": "The stock.package.destination model has 11 fields: picking_id, move_line_ids, location_dest_id, filtered_location, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, many2many: 1, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.package.destination", "table_name": ""}
+{"text": "How do I use the account.account.map.line model?", "response": "To use the account.account.map.line model, you need to provide values for required fields: map_id, child_company_id. Readonly fields: company_id, target_company, target_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.account.map.line", "table_name": ""}
+{"text": "What are the available fields for account.pettycash.fund.reconcile?", "response": "The account.pettycash.fund.reconcile model has 14 fields: fund, date, payable_account, reconciled_amount, move, vouchers, is_pettycash_voucher_approved, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, float: 1, many2many: 1, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.pettycash.fund.reconcile", "table_name": ""}
+{"text": "Describe the field structure of replenish.wizard.", "response": "The replenish.wizard model has 11 fields: fund_id, effective_date, replenish_account_id, replenish_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, date: 1, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "replenish.wizard", "table_name": ""}
+{"text": "Show me the fields of purchase.order.line.", "response": "The purchase.order.line model has 130 fields: name, product_qty, product_uom_qty, taxes_id, product_uom, product_uom_category_id, product_id, price_unit, price_tax, order_id, account_analytic_id, company_id, state, invoice_lines, qty_invoiced, qty_received, qty_received_manual, qty_to_invoice, currency_id, date_order, display_type, is_configurable_product, product_template_attribute_value_ids, product_no_variant_attribute_value_ids, qty_received_method, move_ids, orderpoint_id, move_dest_ids, product_description_variants, propagate_cancel, tick, status, agreement_id, cancel_lines, sh_tender_note, picking_type_id, purchase_request_lines, purchase_request_allocation_ids, sale_order_id, sale_line_id, discount_method, discount_type, discount_amount, discount_amt, branch_id, is_down_payment, purchase_req_budget, realized_amount, confirm_purchase_req_budget, confirm_realized_amount, confirm_budget_data, purchase_budget_lines, planned, is_vendor_pricelist_line, branch_ids, gross_total, price_unit_uom, available_product_ids, last_purchased_price, last_customer_purchase_price, destination_location_id, destination_warehouse_id, date_planned, delivery_ref, vendor_bills_ref, request_line_id, readonly_price, sequence, sequence2, avg_price, current_qty, incoming_stock, actual_progress, remaining_progress, progress_paid, date_received, reference_purchase_price, purchase_line_cost_saving, total_cost_saving, cost_saving_percentage, partner_id, price_subtotal, price_total, total_price, discounted_value, state_delivery, state_inv, multi_discount, product_type, virtual_available_at_date, scheduled_date, forecast_expected_date, free_qty_today, qty_available_today, qty_to_deliver, is_mto, display_qty_widget, route_id, analytic_tag_ids, bid, cost_saving, payment_term_id, base_price, update_base, lead_time, feedback, company_size, capital_revenue, base_quantity, product_template_id, purchase_order_id, is_goods_orders, is_services_orders, requisition_line_id, agreement_line_id, sh_product_description, dp_line, is_reward_line, price_reduce, is_assets_orders, barcode, merchendise_id, persentase_antar_badan, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 2, float: 40, many2many: 7, many2one: 26, selection: 9, one2many: 5, datetime: 8, boolean: 16, char: 10, date: 1, integer: 3, monetary: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.order.line", "table_name": ""}
+{"text": "What is the payment.token model?", "response": "The payment.token model represents Payment Token in the ERP system. It contains 16 fields and is used to manage payment token data. Key fields include: name, short_name, partner_id, acquirer_id, company_id, acquirer_ref, active, payment_ids, verified, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "payment.token", "table_name": ""}
+{"text": "Describe the mailing.trace.report model in Odoo.", "response": "The mailing.trace.report model represents Mass Mailing Statistics in the ERP system. It contains 15 fields and is used to manage mass mailing statistics data. Key fields include: name, mailing_type, campaign, scheduled_date, state, email_from, sent, delivered, opened, replied, clicked, bounced, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mailing.trace.report", "table_name": ""}
+{"text": "What are the technical details of overhead.material?", "response": "The overhead.material model is defined in module: equip3_manuf_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "overhead.material", "table_name": ""}
+{"text": "What models are connected to stock.assign.serial?", "response": "The stock.assign.serial model has 4 relational fields: product_id -> product.product; move_id -> stock.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.assign.serial", "table_name": ""}
+{"text": "What does the fast.financial.report.query model represent?", "response": "The fast.financial.report.query model represents Query for Financial Report in the ERP system. It contains 3 fields and is used to manage query for financial report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "fast.financial.report.query", "table_name": ""}
+{"text": "How do I use the asp.asm.stock model?", "response": "To use the asp.asm.stock model, you need to provide values for required fields: warehouse_id, company_id. Readonly fields: inv_ref, state, company_id, branch_id, domain_warehouse_id, product_ids, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "asp.asm.stock", "table_name": ""}
+{"text": "Describe the field structure of res.partner.rfm.segment.history.", "response": "The res.partner.rfm.segment.history model has 16 fields: partner_id, history_date, old_rfm_segment_id, new_rfm_segment_id, old_rfm_score_id, new_rfm_score_id, old_segment_rank, new_segment_rank, engagement_direction, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, date: 1, integer: 4, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.partner.rfm.segment.history", "table_name": ""}
+{"text": "Show me the relational structure of report.dynamic_accounts_report.cash_flow.", "response": "The report.dynamic_accounts_report.cash_flow model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.cash_flow", "table_name": ""}
+{"text": "Show me the relational structure of pos.gift.card.use.", "response": "The pos.gift.card.use model has 5 relational fields: card_id -> pos.gift.card; customer_id -> res.partner; pos_order_id -> pos.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.gift.card.use", "table_name": ""}
+{"text": "Tell me about the access.group model.", "response": "The access.group model represents Access Group in the ERP system. It contains 10 fields and is used to manage access group data. Key fields include: name, user_ids, access_management_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "access.group", "table_name": ""}
+{"text": "How does ir.cron relate to other models?", "response": "The ir.cron model has 18 relational fields: ir_actions_server_id -> ir.actions.server; user_id -> res.users; create_uid -> res.users; write_uid -> res.users; model_id -> ir.model; child_ids -> ir.actions.server; crud_model_id -> ir.model; link_field_id -> ir.model.fields; fields_lines -> ir.server.object.lines; groups_id -> res.groups; mass_edit_line_ids -> mass.editing.line; partner_ids -> res.partner; channel_ids -> mail.channel; template_id -> mail.template; activity_type_id -> mail.activity.type; activity_user_id -> res.users; sms_template_id -> sms.template; binding_model_id -> ir.model. Many2many fields: child_ids, groups_id, partner_ids, channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.cron", "table_name": ""}
+{"text": "What operations can I perform on account.account.map.line?", "response": "To use the account.account.map.line model, you need to provide values for required fields: map_id, child_company_id. Readonly fields: company_id, target_company, target_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.account.map.line", "table_name": ""}
+{"text": "Describe the bve.view.line model in Odoo.", "response": "The bve.view.line model represents BI View Editor Lines in the ERP system. It contains 27 fields and is used to manage bi view editor lines data. Key fields include: name, sequence, bve_view_id, model_id, model_name, table_alias, join_model_id, field_id, field_name, ttype, description, relation, join_node, left_join, row, column, measure, in_list, list_attr, view_field_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "bve.view.line", "table_name": ""}
+{"text": "List all fields in the stock.move model.", "response": "The stock.move model has 237 fields: name, sequence, priority, create_date, date, date_deadline, company_id, description_picking, product_qty, product_uom_qty, product_uom, product_uom_category_id, product_tmpl_id, location_id, location_dest_id, partner_id, move_dest_ids, move_orig_ids, picking_partner_id, note, state, price_unit, backorder_id, origin, procure_method, scrapped, scrap_ids, group_id, rule_id, propagate_cancel, delay_alert_date, picking_type_id, inventory_id, move_line_ids, move_line_nosuggest_ids, origin_returned_move_id, returned_move_ids, availability, restrict_partner_id, route_ids, warehouse_id, has_tracking, show_operations, show_details_visible, show_reserved_availability, additional, is_locked, is_initial_demand_editable, is_quantity_done_editable, reference, has_move_lines, package_level_id, picking_type_entire_packs, display_assign_serial, next_serial_count, orderpoint_id, forecast_availability, forecast_expected_date, lot_ids, created_production_id, production_id, raw_material_production_id, unbuild_id, consume_unbuild_id, allowed_operation_ids, operation_id, workorder_id, bom_line_id, byproduct_id, unit_factor, is_done, order_finished_lot_ids, should_consume_qty, use_expiration_date, to_refund, account_move_ids, stock_valuation_layer_ids, is_reconstruct_svl, scrap_return_move_id, purchase_line_id, created_purchase_line_id, sh_quality_point, sh_quality_point_id, sh_last_qc_date, sh_last_qc_state, number_of_test, created_purchase_request_line_id, purchase_request_allocation_ids, purchase_request_ids, requisition_line_ids, sale_line_id, branch_id, weight, product_description, qty_pack, is_pack, repair_id, sh_stock_move_barcode_mobile, sh_stock_move_bm_is_cont_scan, length, width, height, product_id, is_adjustable_picking, package_measure_selection, picking_state, is_existing_package, move_package_id, filter_move_package_ids, mr_line_id, move_line_sequence, serial_no, export_file, export_name, next_serial, next_serial_not_autogenerate, next_lot_not_autogenerate, is_import, is_record_confirm, product_type, is_serial_number, next_lot, qty_per_lot, is_autogenerate, picking_code, is_product_service_operation, is_product_service_operation_delivery, is_product_service_operation_receiving, serial, initial_demand, move_progress, analytic_account_group_ids, remaining, fulfillment, current_qty, scheduled_date, responsible, late_time, late_time_hours, process_status, process_time, process_time_hours, package_type, qty_in_pack, packaging_ids, package_quant_ids, measure_ids, product_id_domain, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, created_assembly_id, assembly_finished_id, assembly_component_id, assembly_unit_factor, assembly_should_consume_qty, assembly_product_free_qty, description, created_kitchen_id, kitchen_finished_id, kitchen_component_id, kitchen_unit_factor, kitchen_should_consume_qty, kitchen_product_free_qty, asp_asm_stock_id, bom_product_uom_qty, sub_total, finish_good_rework_id, type_product_bom, finish_good_rework_finished_id, finish_good_rework_created_kitchen_id, finish_good_rework_by_product_id, assembly_record_type, assembly_confirm_date, assembly_product_id, assembly_bom_id, assembly_svl_value, assembly_difference, exp_date, qty_bundle, id_bundle, package_barcode, kitchen_confirm_date, kitchen_product_id, kitchen_bom_id, kitchen_svl_value, kitchen_difference, product_warehouse, product_location, expired_date, product_barcode, vendor_id, state_expired, state_check, picking_type_code, reserved_by_id, reserved_availability, is_reserved, picking_id, origin_src_location, origin_dest_location, picking_reference, is_transit, date_done, return_reason, action, is_transfer_in, is_transfer_out, quantity_done, volume, movement_type, cost, combo_item_id, pos_branch_id, pos_order_line_id, so_antar_badan, po_antar_badan, sale_order_id, purchase_order_id, date_done_real, taxes_id, price_subtotal, price_tax, price_total, price_untaxed_amount, discount_amount, price_discount, currency_id, returned_qty, remaining_checked_qty, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: char: 23, integer: 10, selection: 17, datetime: 14, many2one: 71, text: 2, float: 39, many2many: 12, boolean: 34, one2many: 9, binary: 1, date: 1, monetary: 4.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.move", "table_name": ""}
+{"text": "How does setu.rfm.score relate to other models?", "response": "The setu.rfm.score model has 4 relational fields: rfm_segment_id -> setu.rfm.segment; partner_ids -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.rfm.score", "table_name": ""}
+{"text": "Which fields in sh.payment.report.wizard are computed?", "response": "The sh.payment.report.wizard model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.payment.report.wizard", "table_name": ""}
+{"text": "What operations can I perform on pos.promotion.discount.apply?", "response": "To use the pos.promotion.discount.apply model, you need to provide values for required fields: product_id, promotion_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion.discount.apply", "table_name": ""}
+{"text": "What business logic is in report.account.report_journal?", "response": "To use the report.account.report_journal model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.account.report_journal", "table_name": ""}
+{"text": "What data can be stored in base.geocoder?", "response": "The base.geocoder model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.geocoder", "table_name": ""}
+{"text": "What models are connected to mailing.list?", "response": "The mailing.list model has 5 relational fields: contact_ids -> mailing.contact; subscription_ids -> mailing.contact.subscription; website_popup_ids -> website.mass_mailing.popup; create_uid -> res.users; write_uid -> res.users. Many2many fields: contact_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mailing.list", "table_name": ""}
+{"text": "What are the available fields for payment.icon?", "response": "The payment.icon model has 11 fields: name, acquirer_ids, image, image_payment_form, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2many: 1, binary: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "payment.icon", "table_name": ""}
+{"text": "Can you explain the purpose of sh.stock.move.text?", "response": "The sh.stock.move.text model represents Stock Move Quality Measurement Text in the ERP system. It contains 12 fields and is used to manage stock move quality measurement text data. Key fields include: product_id, sh_message, sh_quality_point_id, picking_id, text_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.stock.move.text", "table_name": ""}
+{"text": "What are the technical details of vendor.pricelist.approval.matrix.line?", "response": "The vendor.pricelist.approval.matrix.line model is defined in module: equip3_purchase_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "vendor.pricelist.approval.matrix.line", "table_name": ""}
+{"text": "What is the weight.scale.barcode.format model?", "response": "The weight.scale.barcode.format model represents weight.scale.barcode.format in the ERP system. It contains 10 fields and is used to manage weight.scale.barcode.format data. Key fields include: name, line_ids, total_digit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "weight.scale.barcode.format", "table_name": ""}
+{"text": "What fields does pos.promotion.specific.product have?", "response": "The pos.promotion.specific.product model has 13 fields: active, type_apply, qty_free, product_id, product_ids, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, selection: 1, float: 1, many2one: 4, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.promotion.specific.product", "table_name": ""}
+{"text": "What are common use cases for report.sh_purchase_reports.sh_tv_top_vendors_doc?", "response": "To use the report.sh_purchase_reports.sh_tv_top_vendors_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_tv_top_vendors_doc", "table_name": ""}
+{"text": "What are the available fields for budget.budget?", "response": "The budget.budget model has 31 fields: name, complete_name, parent_id, user_id, date_from, date_to, state, budget_budget_line, company_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 6, date: 2, selection: 1, one2many: 4, boolean: 5, many2many: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "budget.budget", "table_name": ""}
+{"text": "How is budget.scurve used in the system?", "response": "The budget.scurve model represents budget.scurve in the ERP system. It contains 33 fields and is used to manage budget.scurve data. Key fields include: name, budget_to_analyze, crossovered_budget, budgetary_position, period_start_date, period_end_date, crossovered_purchase_budget, product_purchase_budget, crossovered_acount_budget, acount_account_budget, project_id, job_cost_sheet, work_orders_ids, account_tag_ids, start_date, end_date, contract_amount, method, ks_chart_data, ks_graph_view, crossovered_budget_line_ids, purchase_budget_line_ids, acount_account_budget_ids, crossovered_budget_line_count, from_menu, budget_scurve_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "budget.scurve", "table_name": ""}
+{"text": "What are common use cases for budget.budget.budget.line?", "response": "To use the budget.budget.budget.line model, you need to provide values for required fields: budget_budget_id, date_from, date_to, planned_amount. Readonly fields: name, analytic_group_id, currency_id, practical_amount, theoritical_amount, percentage, company_id, is_above_budget, budget_budget_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "budget.budget.budget.line", "table_name": ""}
+{"text": "What data can be stored in web.environment.ribbon.backend?", "response": "The web.environment.ribbon.backend model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "web.environment.ribbon.backend", "table_name": ""}
+{"text": "What are the relationships in budget.scurve.line?", "response": "The budget.scurve.line model has 3 relational fields: scurve_id -> budget.scurve; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "budget.scurve.line", "table_name": ""}
+{"text": "How is report.dynamic_accounts_report.general_ledger implemented technically?", "response": "The report.dynamic_accounts_report.general_ledger model is defined in module: dynamic_accounts_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.dynamic_accounts_report.general_ledger", "table_name": ""}
+{"text": "What methods are available in pos.promotion.discount.category?", "response": "The pos.promotion.discount.category model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.promotion.discount.category", "table_name": ""}
+{"text": "Can you explain the purpose of account.tax.map.sales.line?", "response": "The account.tax.map.sales.line model represents Account Tax Map Sales Line in the ERP system. It contains 17 fields and is used to manage account tax map sales line data. Key fields include: company_id, sales_tax_id, target_company, target_sales_tax, map_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, line_ids, child_company_id, ownership, sales_line_ids, purchase_line_ids.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.tax.map.sales.line", "table_name": ""}
+{"text": "List all fields in the order.driver.message model.", "response": "The order.driver.message model has 11 fields: order_id, message, send_to_driver, partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 2, boolean: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "order.driver.message", "table_name": ""}
+{"text": "What modules define crossovered.budget?", "response": "The crossovered.budget model is defined in module: om_account_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crossovered.budget", "table_name": ""}
+{"text": "How is report.sh_sale_reports.sh_sales_product_profit_doc implemented technically?", "response": "The report.sh_sale_reports.sh_sales_product_profit_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_sales_product_profit_doc", "table_name": ""}
+{"text": "Can you explain the purpose of pos.promotion.discount.condition?", "response": "The pos.promotion.discount.condition model represents Promotion discount condition in the ERP system. It contains 11 fields and is used to manage promotion discount condition data. Key fields include: active, product_id, minimum_quantity, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.promotion.discount.condition", "table_name": ""}
+{"text": "How is report.dynamic_accounts_report.cash_flow used in the system?", "response": "The report.dynamic_accounts_report.cash_flow model represents Cash Flow Report in the ERP system. It contains 3 fields and is used to manage cash flow report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.dynamic_accounts_report.cash_flow", "table_name": ""}
+{"text": "What does the acrux.chat.message.wizard model represent?", "response": "The acrux.chat.message.wizard model represents ChatRoom Message in the ERP system. It contains 20 fields and is used to manage chatroom message data. Key fields include: text, partner_id, conversation_id, connector_id, sale_id, message_mass_id, phone, is_crm, opportunity_id, whatsapp_template_id, crm_message_mass_id, mobile, attachment_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "acrux.chat.message.wizard", "table_name": ""}
+{"text": "What are the relationships in multiple.rfq?", "response": "The multiple.rfq model has 4 relational fields: vendor_ids -> res.partner; product_ids -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: vendor_ids, product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "multiple.rfq", "table_name": ""}
+{"text": "What modules define lost.product?", "response": "The lost.product model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "lost.product", "table_name": ""}
+{"text": "Describe the field structure of purchase.product.template.line.", "response": "The purchase.product.template.line model has 14 fields: name, description, ordered_qty, unit_price, product_uom, purchase_template_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, char: 2, float: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.product.template.line", "table_name": ""}
+{"text": "What is the equip3.pos.membership.report model?", "response": "The equip3.pos.membership.report model represents POS Membership Report in the ERP system. It contains 10 fields and is used to manage pos membership report data. Key fields include: name, member_code, company_id, date_joined, year_joined, member_point, total_order, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "equip3.pos.membership.report", "table_name": ""}
+{"text": "Show me the fields of sale.adv.wizard.product.line.", "response": "The sale.adv.wizard.product.line model has 13 fields: sale_adv_wizard_id, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, float: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.adv.wizard.product.line", "table_name": ""}
+{"text": "How is pos.gift.card.exchange.history implemented technically?", "response": "The pos.gift.card.exchange.history model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.gift.card.exchange.history", "table_name": ""}
+{"text": "Tell me about the assets.approval.matrix.line model.", "response": "The assets.approval.matrix.line model represents Assets Approval Matrix Line in the ERP system. It contains 19 fields and is used to manage assets approval matrix line data. Key fields include: sequence, user_ids, minimum_approver, assets_approval_matrix_id, sequence2, approved_users, state_char, time_stamp, feedback, last_approved, approved, assets_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assets.approval.matrix.line", "table_name": ""}
+{"text": "Describe the many2many relations for assign.pr.line.wizard.", "response": "The assign.pr.line.wizard model has 7 relational fields: wizard_id -> assign.pr.wizard; pr_line_id -> purchase.request.line; user_id -> res.users; new_user_id -> res.users; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "assign.pr.line.wizard", "table_name": ""}
+{"text": "How to create records in report.stock.demand?", "response": "To use the report.stock.demand model, you need to provide values for required fields: none. Readonly fields: quantity, forecast, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.stock.demand", "table_name": ""}
+{"text": "What operations can I perform on warranty.renew?", "response": "To use the warranty.renew model, you need to provide values for required fields: product_id, serial_no, partner_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "warranty.renew", "table_name": ""}
+{"text": "How to create records in intrawarehouse.transfer?", "response": "To use the intrawarehouse.transfer 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "Describe the field structure of purchase.order.", "response": "The purchase.order model has 266 fields: priority, origin, partner_ref, date_approve, dest_address_id, order_line, notes, invoice_count, invoice_ids, invoice_status, date_calendar_start, fiscal_position_id, payment_term_id, product_id, user_id, currency_rate, mail_reminder_confirmed, mail_reception_confirmed, receipt_reminder_email, reminder_date_before_receipt, team_id, report_grids, grid_product_tmpl_id, grid_update, grid, requisition_id, is_quantity_copy, incoterm_id, picking_count, picking_ids, picking_type_id, default_location_dest_id_usage, group_id, is_shipped, effective_date, on_time_rate, active, complete_state, custom_checklist_ids, custom_checklist, product_template_id, digital_sign, purchase_show_signature, chk_sign_confirm, purchase_show_enable_other_sign, sign_by, designation, sign_on, document_count, order_history_line, order_report_id, rfq_report_id, purchase_tag_ids, purchase_url, report_token, text_message, po_extract_id, po_split_id, po_extract_count, po_split_count, sh_fully_ship, sh_partially_ship, sh_fully_paid, sh_partially_paid, sh_hidden_compute_field, agreement_id, cancel_lines, selected_order, sh_msg, sh_po_number, sh_purchase_order_id, sh_revision_po_id, po_count, sh_purchase_revision_config, visible_eval, mrp_production_count, sale_order_count, internal_id, inter_transfer_count, client_order_id, discount_method, discount_amount, discount_amt, discount_amt_line, merged, sh_purchase_barcode_mobile, sh_purchase_bm_is_cont_scan, sh_sale_order_id, apply_manual_currency_exchange, manual_currency_exchange_rate, active_manual_currency_rate, total_invoices_amount, down_payment_by, amount, dp_journal_id, hide_create_bill, payment_status, down_payment_amount, total_down_payment_amount, is_down_payment, report_template_id1, report_template_id, amount_to_text, is_vendor_pricelist, name, currency_id, po_expiry_date, po, exp_po, sent, is_goods_orders, is_services_orders, is_hold_purchase_order, approval_matrix_id, is_approval_matrix, state1, po_state, approved_matrix_ids, is_approve_button, approval_matrix_line_id, analytic_account_group_ids, company_id, branch_id, destination_location_id, is_delivery_receipt, destination_warehouse_id, discount_type, is_single_delivery_destination, analytic_accounting, is_revision_po, is_revision_created, revision_order_id, custom_checklist_template_ids, readonly_price, timezone_date, request_partner_id, date_order_assets, name2, date_order, milestone_template_id, milestone_purchase_ids, is_group_good_services_order, have_product_service, swo_ids, swo_count, is_taxes, actual_progress, remaining_progress, progress_paid, paid_swo, partner_invoice_id, available_partner_invoice_ids, product_brand_ids, is_product_brand_filter, is_service_work_order, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, is_service, show_analytic_tags, amount_untaxed, amount_tax, amount_total, discount_amt_before, discount_amt_line_before, amount_subtotal, tax_discount_policy, list_available_products, from_purchase_request, term_condition, term_condition_box, bo_count, blanket_ids, multilevel_disc, multi_discount, vendor_payment_terms, service_level_agreement_id, service_level_agreement_box, user_request_ids, vendor_invoice_documents_count, down_payment_discount_amount, tender_scope, is_submit_quotation, price_rating, not_editable, is_editable, tender_order_line, from_bo, is_btn_approval_matrix, state, is_blanket_cancel, open_tender, days_to_approve, purchase_order_duration_to_confirm, amount_saved_from_cost_savings, number_of_successful_cost_savings, partner_id, dp, journal_id, name_dp, direct_approval_matrix_id, is_approval_matrix_direct, approved_matrix_direct_ids, approved_matrix_direct_id, state_direct_on, state_direct_off, is_approve_button_direct, control, qty_limit, budget_limit, is_valid_coupon, applied_coupon_ids, generated_coupon_ids, no_code_promo_program_ids, code_promo_program_id, promo_code, client_order_ref, is_dropship, is_sale_order, customer_partner_id, customer_location_partner_id, branch_ids, is_assets_orders, import_reference, is_report_purchaseorder_printed, is_report_purchasequotation_printed, remark, rfq_type, discount_promotions_amount, date_planned, persentase_antar_badan, form_view_opened, 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. 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.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.order", "table_name": ""}
+{"text": "What are common use cases for approval.matrix.sale.order.lines?", "response": "To use the approval.matrix.sale.order.lines model, you need to provide values for required fields: user_name_ids, sequence, minimum_approver. Readonly fields: sequence2, signature, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.sale.order.lines", "table_name": ""}
+{"text": "Show me the relational structure of pos.config.", "response": "The pos.config model has 97 relational fields: journal_id -> account.journal; invoice_journal_id -> account.journal; currency_id -> res.currency; iface_start_categ_id -> pos.category; selectable_categ_ids -> pos.category; sequence_id -> ir.sequence; sequence_line_id -> ir.sequence; session_ids -> pos.session; current_session_id -> pos.session; last_session_closing_cashbox -> account.bank.statement.cashbox; pricelist_id -> product.pricelist; available_pricelist_ids -> product.pricelist; allowed_pricelist_ids -> product.pricelist; company_id -> res.company; barcode_nomenclature_id -> barcode.nomenclature; tip_product_id -> product.product; fiscal_position_ids -> account.fiscal.position; default_fiscal_position_id -> account.fiscal.position; default_cashbox_id -> account.bank.statement.cashbox; payment_method_ids -> pos.payment.method; current_user_id -> res.users; rounding_method -> account.cash.rounding; discount_product_id -> product.product; employee_ids -> hr.employee; floor_ids -> restaurant.floor; printer_ids -> restaurant.printer; crm_team_id -> crm.team; group_pos_manager_id -> res.groups; group_pos_user_id -> res.groups; pos_receipt_template_id -> pos.receipt.template; weight_scale_barcode_format_id -> weight.scale.barcode.format; pos_config_cashbox_lines_ids -> account.cashbox.line; pos_config_cashbox_clsosing_line_ids -> account.cashbox.line; cashbox_lines_ids -> account.cashbox.line; pos_cashbox_lines_ids -> pos.account.cashbox.line; printer_id -> pos.epson; coupon_program_ids -> coupon.program; coupon_giftcard_ids -> coupon.program; user_id -> res.users; pos_allowed_return_category_ids -> pos.category; allow_pos_categories_out_of_stock -> pos.category; voucher_sequence_id -> ir.sequence; sync_to_pos_config_ids -> pos.config; internal_transfer_picking_type_id -> stock.picking.type; discount_ids -> pos.global.discount; return_method_id -> pos.payment.method; return_coupon_program_id -> coupon.program; payment_journal_ids -> account.journal; customer_default_id -> res.partner; multi_stock_operation_type_ids -> stock.picking.type; update_tax_ids -> account.tax; default_seller_id -> res.users; seller_ids -> res.users; qrcode_ids -> pos.qrcode; stock_location_ids -> stock.location; assigned_user_ids -> res.users; manager_ids -> res.users; stock_location_id -> stock.location; stock_location_dest_id -> stock.location; discount_global_id -> product.product; analytic_account_id -> account.analytic.account; iface_available_categ_ids -> pos.category; service_charge_ids -> pos.service.charge; assign_orders_to_config_ids -> pos.config; product_category_ids -> product.category; hidden_product_ids -> product.product; custom_sale_product_id -> product.product; multi_currency_ids -> res.currency; allowed_employee_ids -> hr.employee; fire_appetizer -> pos.category; fire_main_course -> pos.category; fire_dessert -> pos.category; promotion_ids -> pos.promotion; zone_id -> pos.zone; product_voucher_service_id -> product.product; product_coupon_service_id -> product.product; product_categ_ids -> pos.category; user_ids -> res.users; void_order_pin_ids -> res.users; void_order_line_pin_ids -> res.users; advertisement_image_ids -> advertisement.images; warehouse_id -> stock.warehouse; picking_type_id -> stock.picking.type; pos_branch_id -> res.branch; gift_card_account_id -> account.account; gift_card_product_id -> product.product; gift_payment_method_id -> pos.payment.method; cashbox_payment_method_id -> pos.payment.method; product_exchange_pin_ids -> res.users; select_shortcut -> pos.keyboard.shortcuts; pos_loyalty_id -> pos.loyalty; pos_loyalty_ids -> pos.loyalty; customer_deposit_account_id -> account.account; customer_deposit_reconcile_journal_id -> account.journal; analytic_group_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: selectable_categ_ids, available_pricelist_ids, allowed_pricelist_ids, fiscal_position_ids, payment_method_ids, employee_ids, printer_ids, coupon_program_ids, coupon_giftcard_ids, pos_allowed_return_category_ids, allow_pos_categories_out_of_stock, sync_to_pos_config_ids, discount_ids, payment_journal_ids, multi_stock_operation_type_ids, update_tax_ids, seller_ids, stock_location_ids, assigned_user_ids, manager_ids, iface_available_categ_ids, service_charge_ids, assign_orders_to_config_ids, product_category_ids, hidden_product_ids, multi_currency_ids, allowed_employee_ids, fire_appetizer, fire_main_course, fire_dessert, promotion_ids, product_categ_ids, user_ids, void_order_pin_ids, void_order_line_pin_ids, advertisement_image_ids, product_exchange_pin_ids, pos_loyalty_ids, analytic_group_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.config", "table_name": ""}
+{"text": "What foreign keys exist in tax.adjustments.wizard?", "response": "The tax.adjustments.wizard model has 8 relational fields: journal_id -> account.journal; debit_account_id -> account.account; credit_account_id -> account.account; tax_report_line_id -> account.tax.report.line; company_currency_id -> res.currency; report_id -> account.tax.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "tax.adjustments.wizard", "table_name": ""}
+{"text": "What foreign keys exist in sh.sale.category.wizard?", "response": "The sh.sale.category.wizard model has 6 relational fields: sh_category_ids -> product.category; company_ids -> res.company; company_id -> res.company; category_order_dic -> user.order.dic; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_category_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.sale.category.wizard", "table_name": ""}
+{"text": "How to query portal.wizard data?", "response": "To use the portal.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "portal.wizard", "table_name": ""}
+{"text": "What are the technical details of calendar.attendee?", "response": "The calendar.attendee model is defined in module: calendar. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "calendar.attendee", "table_name": ""}
+{"text": "How is portal.share used in the system?", "response": "The portal.share model represents Portal Sharing in the ERP system. It contains 13 fields and is used to manage portal sharing data. Key fields include: res_model, res_id, partner_ids, note, share_link, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "portal.share", "table_name": ""}
+{"text": "What operations can I perform on asset.depreciation.confirmation.wizard?", "response": "To use the asset.depreciation.confirmation.wizard model, you need to provide values for required fields: date. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "asset.depreciation.confirmation.wizard", "table_name": ""}
+{"text": "What operations can I perform on target.kpi?", "response": "To use the target.kpi model, you need to provide values for required fields: user_id, target_based_on_ids, from_date, to_date, target_on. Readonly fields: name, purchase_team_id, user_id, company_id, target_based_on_ids, main_target, from_date, to_date, target_on, target_left, kpi_progress, current_achievement, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "target.kpi", "table_name": ""}
+{"text": "What methods are available in account.move?", "response": "The account.move model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.move", "table_name": ""}
+{"text": "How is kitchen.safety.stock used in the system?", "response": "The kitchen.safety.stock model represents Safety Stock Management in the ERP system. It contains 13 fields and is used to manage safety stock management data. Key fields include: name, company_id, is_branch_required, branch_id, warehouse_id, stock_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kitchen.safety.stock", "table_name": ""}
+{"text": "What are common use cases for account.payment.register.payment.difference.line?", "response": "To use the account.payment.register.payment.difference.line model, you need to provide values for required fields: name, account_id, payment_amount, company_id. Readonly fields: currency_id, payment_difference, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.payment.register.payment.difference.line", "table_name": ""}
+{"text": "What are the available fields for pos.promotion.price?", "response": "The pos.promotion.price model has 12 fields: active, product_id, minimum_quantity, price_down, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 4, float: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.promotion.price", "table_name": ""}
+{"text": "What is the res.users.identitycheck model?", "response": "The res.users.identitycheck model represents Password Check Wizard in the ERP system. It contains 8 fields and is used to manage password check wizard data. Key fields include: password, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.users.identitycheck", "table_name": ""}
+{"text": "What modules define ks.sales.forecast?", "response": "The ks.sales.forecast model is defined in module: ks_sales_forecast. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks.sales.forecast", "table_name": ""}
+{"text": "What are common use cases for res.currency.rate?", "response": "To use the res.currency.rate model, you need to provide values for required fields: name, currency_id. Readonly fields: currency_id, rate, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.currency.rate", "table_name": ""}
+{"text": "What are the available fields for limit.request?", "response": "The limit.request model has 66 fields: name, partner_id, limit_type, limit_type_old, limit_type_new, credit_amount, last_credit_limit, open_inv_no, last_open_inv_no, new_max_invoice, last_max_invoice, description, state, state1, state2, branch_id, limit_approval_matrix, approval_ids, approval_matrix_line_id, user_approval_ids, current_user, approval, approval2, new_amount, last_amount, is_approve_button, user_id, is_credit_limit_brand, product_brand_ids, brand_ids, company_id, 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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 15, selection: 8, float: 8, text: 1, one2many: 6, many2many: 4, boolean: 9, date: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "limit.request", "table_name": ""}
+{"text": "Describe the field structure of base_import.tests.models.m2o.required.", "response": "The base_import.tests.models.m2o.required model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.m2o.required", "table_name": ""}
+{"text": "Describe the assets.approval.matrix.line model in Odoo.", "response": "The assets.approval.matrix.line model represents Assets Approval Matrix Line in the ERP system. It contains 19 fields and is used to manage assets approval matrix line data. Key fields include: sequence, user_ids, minimum_approver, assets_approval_matrix_id, sequence2, approved_users, state_char, time_stamp, feedback, last_approved, approved, assets_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assets.approval.matrix.line", "table_name": ""}
+{"text": "Show me the fields of product.public.category.", "response": "The product.public.category model has 29 fields: name, parent_id, parent_path, child_id, parents_and_self, sequence, website_description, product_tmpl_ids, Minimum_amount, amount_footer, image_1920, image_1024, image_512, image_256, image_128, is_seo_optimized, website_meta_title, website_meta_description, website_meta_keywords, website_meta_og_img, seo_name, website_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 7, many2one: 4, one2many: 1, many2many: 2, integer: 4, html: 1, binary: 5, boolean: 1, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.public.category", "table_name": ""}
+{"text": "What models are connected to customer.voucher?", "response": "The customer.voucher model has 7 relational fields: customer_id -> res.partner; customer_target_id -> customer.target; discount_line_product_id -> product.product; sale_order_line_ids -> sale.order.line; cashback_line_ids -> cashback.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "customer.voucher", "table_name": ""}
+{"text": "Tell me about the restaurant.printer model.", "response": "The restaurant.printer model represents Restaurant Printer in the ERP system. It contains 12 fields and is used to manage restaurant printer data. Key fields include: name, proxy_ip, product_categories_ids, printer_type, epson_printer_ip, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "restaurant.printer", "table_name": ""}
+{"text": "What are common use cases for membership.invoice?", "response": "To use the membership.invoice model, you need to provide values for required fields: product_id, member_price. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "membership.invoice", "table_name": ""}
+{"text": "What models are connected to hr.employee?", "response": "The hr.employee model has 32 relational fields: user_id -> res.users; user_partner_id -> res.partner; company_id -> res.company; address_home_id -> res.partner; country_id -> res.country; country_of_birth -> res.country; bank_account_id -> res.partner.bank; child_ids -> hr.employee; category_ids -> hr.employee.category; message_main_attachment_id -> ir.attachment; subordinate_ids -> hr.employee; currency_id -> res.currency; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; website_message_ids -> mail.message; department_id -> hr.department; job_id -> hr.job; address_id -> res.partner; resource_id -> resource.resource; resource_calendar_id -> resource.calendar; parent_id -> hr.employee; coach_id -> hr.employee; goal_ids -> gamification.goal; badge_ids -> gamification.badge.user; direct_badge_ids -> gamification.badge.user; create_uid -> res.users; write_uid -> res.users. Many2many fields: category_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hr.employee", "table_name": ""}
+{"text": "Show me the fields of x.report.wizard.", "response": "The x.report.wizard model has 11 fields: pos_session_ids, branch_id, company_id, report_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, many2one: 4, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "x.report.wizard", "table_name": ""}
+{"text": "What foreign keys exist in res.branch?", "response": "The res.branch model has 18 relational fields: analytic_tag_ids -> account.analytic.tag; company_id -> res.company; state_id -> res.country.state; country_id -> res.country; user_id -> res.users; user_ids -> res.users; config_ids -> pos.config; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, user_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.branch", "table_name": ""}
+{"text": "What does the repair.line model represent?", "response": "The repair.line model represents Repair Line (parts) in the ERP system. It contains 26 fields and is used to manage repair line (parts) data. Key fields include: name, repair_id, company_id, currency_id, type, product_id, invoiced, price_unit, price_subtotal, tax_id, product_uom_qty, product_uom, product_uom_category_id, invoice_line_id, location_id, location_dest_id, move_id, lot_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "repair.line", "table_name": ""}
+{"text": "Describe the many2many relations for report.sh_sale_reports.sh_sale_details_report_doc.", "response": "The report.sh_sale_reports.sh_sale_details_report_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_sale_details_report_doc", "table_name": ""}
+{"text": "What foreign keys exist in _unknown?", "response": "The _unknown model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "_unknown", "table_name": ""}
+{"text": "What foreign keys exist in mass.editing.wizard?", "response": "The mass.editing.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mass.editing.wizard", "table_name": ""}
+{"text": "What fields does payment.link.wizard have?", "response": "The payment.link.wizard model has 18 fields: res_model, res_id, amount, amount_max, currency_id, partner_id, partner_email, link, description, access_token, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 6, integer: 2, monetary: 2, many2one: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "payment.link.wizard", "table_name": ""}
+{"text": "What is the account.multipayment model?", "response": "The account.multipayment model represents Multipayment in the ERP system. It contains 90 fields and is used to manage multipayment data. Key fields include: name, partner_id, amount, journal_id, currency_id, date, ref, memo, line_credit_ids, line_debit_ids, diff_amount, partner_type, total_amount_credit, total_amount_debit, payment_id_count, company_id, branch_id, create_uid, create_date, different_move_id, request_partner_id, payment_method, multipul_payment_approval_matrix_id, is_multi_payment_approval_matrix, is_approve_button, approved_matrix_ids, approval_matrix_line_id, action_validate_boolean, action_draft_boolean, action_cancel_boolean, request_for_approval_boolean, action_approved_rp_boolean, rp_reject_boolean, state_boolean, state1_boolean, state2_boolean, difference_ids, payment_difference_amount, writeoff_account_id, writeoff_label, payment_type, clearing_account_id, move_id, due_date, receive_date, clearing_date, is_vendor, state, state1, state2, payment_ids, invoice_cutoff_date, is_cutoff_date, is_check_all, 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, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.multipayment", "table_name": ""}
+{"text": "Show me the fields of account.automatic.entry.wizard.", "response": "The account.automatic.entry.wizard model has 22 fields: action, move_data, preview_move_data, move_line_ids, date, company_id, company_currency_id, percentage, total_amount, journal_id, account_type, expense_accrual_account, revenue_accrual_account, destination_account_id, display_currency_helper, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 2, text: 2, many2many: 1, date: 1, many2one: 8, float: 1, monetary: 1, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.automatic.entry.wizard", "table_name": ""}
+{"text": "What models are connected to quotation.amount?", "response": "The quotation.amount model has 4 relational fields: order_id -> sale.order; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "quotation.amount", "table_name": ""}
+{"text": "List all fields in the auditlog.log.line model.", "response": "The auditlog.log.line model has 25 fields: field_id, log_id, old_value, new_value, old_value_text, new_value_text, field_name, field_description, name, model_id, model_name, model_model, res_id, user_id, method, http_session_id, http_request_id, log_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, text: 4, char: 7, integer: 2, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "auditlog.log.line", "table_name": ""}
+{"text": "What are the available fields for crossovered.budget.wizard?", "response": "The crossovered.budget.wizard model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crossovered.budget.wizard", "table_name": ""}
+{"text": "How to create records in sms.api?", "response": "To use the sms.api model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sms.api", "table_name": ""}
+{"text": "What business logic is in kpi.period.value?", "response": "To use the kpi.period.value model, you need to provide values for required fields: period_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "kpi.period.value", "table_name": ""}
+{"text": "What methods are available in account.incoterms?", "response": "The account.incoterms model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.incoterms", "table_name": ""}
+{"text": "Show me the fields of ir.autovacuum.", "response": "The ir.autovacuum model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.autovacuum", "table_name": ""}
+{"text": "Describe the field structure of sale.report.", "response": "The sale.report model has 45 fields: name, date, product_id, product_uom, product_uom_qty, qty_delivered, qty_to_invoice, qty_invoiced, partner_id, company_id, user_id, price_total, price_subtotal, untaxed_amount_to_invoice, untaxed_amount_invoiced, product_tmpl_id, categ_id, nbr, pricelist_id, analytic_account_id, team_id, country_id, industry_id, commercial_partner_id, weight, volume, discount, discount_amount, campaign_id, medium_id, source_id, order_id, warehouse_id, website_id, branch_id, state, margin, city_id, state_id, untaxed_amount, total_amount, grand_total_order, id, display_name, __last_update. Field types distribution: char: 2, datetime: 2, many2one: 22, float: 16, integer: 2, selection: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.report", "table_name": ""}
+{"text": "Can you explain the purpose of warehouse.capacity.excel.report?", "response": "The warehouse.capacity.excel.report model represents Warehouse Capacity Excel Report in the ERP system. It contains 9 fields and is used to manage warehouse capacity excel report data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "warehouse.capacity.excel.report", "table_name": ""}
+{"text": "Show me the fields of ks_dashboard_ninja.child_board.", "response": "The ks_dashboard_ninja.child_board model has 14 fields: name, ks_dashboard_ninja_id, ks_gridstack_config, ks_active, ks_dashboard_menu_name, board_type, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 4, boolean: 1, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.child_board", "table_name": ""}
+{"text": "Which fields in sale.report are computed?", "response": "The sale.report model is defined in module: sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.report", "table_name": ""}
+{"text": "How does account.cashbox.wizard relate to other models?", "response": "The account.cashbox.wizard model has 5 relational fields: pos_session_id -> pos.session; line_ids -> account.cashbox.wizard.line; line_bank_ids -> account.cashbox.wizard.bank.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.cashbox.wizard", "table_name": ""}
+{"text": "What modules define base.automation?", "response": "The base.automation model is defined in module: base_automation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base.automation", "table_name": ""}
+{"text": "How is ks_to.do.description implemented technically?", "response": "The ks_to.do.description model is defined in module: ks_dashboard_ninja. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks_to.do.description", "table_name": ""}
+{"text": "What modules define credit.note.product.lines?", "response": "The credit.note.product.lines model is defined in module: dev_rma. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "credit.note.product.lines", "table_name": ""}
+{"text": "What fields does setu.stock.movement.report have?", "response": "The setu.stock.movement.report model has 19 fields: get_report_from_beginning, stock_file_data, start_date, end_date, upto_date, company_ids, product_category_ids, product_ids, warehouse_ids, company_id, is_product_daily, is_movement_daily, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 3, binary: 1, date: 3, many2many: 4, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.stock.movement.report", "table_name": ""}
+{"text": "How to query mrp.quality.alert.report data?", "response": "To use the mrp.quality.alert.report model, you need to provide values for required fields: date_from, date_to, stage_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mrp.quality.alert.report", "table_name": ""}
+{"text": "Describe the field structure of report.stock.excel.", "response": "The report.stock.excel model has 12 fields: datas, datas_fname, product_ids, categ_ids, location_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, many2many: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.stock.excel", "table_name": ""}
+{"text": "What are common use cases for kpi.item?", "response": "To use the kpi.item model, you need to provide values for required fields: name, category_id, result_type, result_appearance. Readonly fields: formula_warning, all_parent_ids, measures_ids, constant_ids, kpi_ids, access_user_ids, edit_access_user_ids, help_notes, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "kpi.item", "table_name": ""}
+{"text": "What data can be stored in mrp.bom.byproduct?", "response": "The mrp.bom.byproduct model has 20 fields: product_id, company_id, product_qty, product_uom_id, bom_id, allowed_operation_ids, operation_id, allocated_cost, cost, operation_two_ids, operation_two_id, assembly_allocated_cost, kitchen_allocated_cost, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, float: 5, many2many: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.bom.byproduct", "table_name": ""}
+{"text": "What data can be stored in res.partner.bank?", "response": "The res.partner.bank model has 25 fields: active, acc_type, acc_number, sanitized_acc_number, acc_holder_name, partner_id, bank_id, bank_name, bank_bic, sequence, currency_id, company_id, journal_id, aba_routing, acc_holder_email, acc_holder_type, acc_holder_resident, acc_holder_address, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, selection: 3, char: 9, many2one: 6, integer: 2, one2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.partner.bank", "table_name": ""}
+{"text": "How does website.sale.payment.acquirer.onboarding.wizard relate to other models?", "response": "The website.sale.payment.acquirer.onboarding.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.sale.payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "What operations can I perform on sh.quality.alert?", "response": "To use the sh.quality.alert model, you need to provide values for required fields: product_id, user_id, team_id. Readonly fields: name, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.quality.alert", "table_name": ""}
+{"text": "What models are connected to crm.lost.reason?", "response": "The crm.lost.reason model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.lost.reason", "table_name": ""}
+{"text": "How to query base.module.upgrade data?", "response": "To use the base.module.upgrade model, you need to provide values for required fields: none. Readonly fields: module_info, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.module.upgrade", "table_name": ""}
+{"text": "Which fields in whatsapp.message.wizard are computed?", "response": "The whatsapp.message.wizard model is defined in module: ss_whatsapp_connector. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "whatsapp.message.wizard", "table_name": ""}
+{"text": "What are common use cases for res.users.apikeys?", "response": "To use the res.users.apikeys model, you need to provide values for required fields: name, user_id. Readonly fields: name, user_id, scope, create_date, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.users.apikeys", "table_name": ""}
+{"text": "What is the create.recurring.invoice model?", "response": "The create.recurring.invoice model represents Create Recurring Invoice in the ERP system. It contains 8 fields and is used to manage create recurring invoice data. Key fields include: start_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "create.recurring.invoice", "table_name": ""}
+{"text": "How does ks_dashboard_ninja.board_custom_filters relate to other models?", "response": "The ks_dashboard_ninja.board_custom_filters model has 5 relational fields: ks_dashboard_board_id -> ks_dashboard_ninja.board; ks_model_id -> ir.model; ks_domain_field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks_dashboard_ninja.board_custom_filters", "table_name": ""}
+{"text": "What are the available fields for wizard.scrap.order.report?", "response": "The wizard.scrap.order.report model has 13 fields: company_id, start_date, end_date, state, name, data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, date: 2, selection: 1, char: 2, binary: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "wizard.scrap.order.report", "table_name": ""}
+{"text": "What are the relationships in report.equip3_crm_tracking.crm_sales_tracking_visit_report?", "response": "The report.equip3_crm_tracking.crm_sales_tracking_visit_report model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_crm_tracking.crm_sales_tracking_visit_report", "table_name": ""}
+{"text": "Show me the fields of receipt.payment.", "response": "The receipt.payment model has 63 fields: name, partner_id, amount, journal_id, currency_id, clearing_account_id, move_id, date, payment_ref, memo, due_date, receive_date, clearing_date, company_id, branch_id, diff_amount, writeoff_acc_id, naration, create_uid, create_date, partner_type, line_credit_ids, line_debit_ids, state, total_amount_credit, total_amount_debit, payment_id_count, 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, write_uid, write_date, __last_update. Field types distribution: char: 9, many2one: 16, monetary: 4, date: 3, datetime: 6, text: 2, selection: 4, one2many: 6, integer: 6, boolean: 5, many2many: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "receipt.payment", "table_name": ""}
+{"text": "What are common use cases for res.partner.title?", "response": "To use the res.partner.title 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.partner.title", "table_name": ""}
+{"text": "Describe the field structure of ks_dashboard_ninja.board_defined_filters.", "response": "The ks_dashboard_ninja.board_defined_filters model has 16 fields: name, ks_dashboard_board_id, ks_model_id, ks_domain, ks_domain_temp, ks_model_name, display_type, sequence, ks_is_active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 4, selection: 1, integer: 2, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.board_defined_filters", "table_name": ""}
+{"text": "How do I use the sparse_fields.test model?", "response": "To use the sparse_fields.test 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sparse_fields.test", "table_name": ""}
+{"text": "Describe the field structure of ks_dashboard_item.multiplier.", "response": "The ks_dashboard_item.multiplier model has 11 fields: ks_dashboard_item_id, ks_model_id, ks_multiplier_value, ks_multiplier_fields, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks_dashboard_item.multiplier", "table_name": ""}
+{"text": "What data can be stored in wizard.vendor.deposit?", "response": "The wizard.vendor.deposit model has 9 fields: reason, add_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, boolean: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "wizard.vendor.deposit", "table_name": ""}
+{"text": "Show me the relational structure of ks_to.do.description.", "response": "The ks_to.do.description model has 3 relational fields: ks_to_do_header_id -> ks_to.do.headers; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks_to.do.description", "table_name": ""}
+{"text": "What business logic is in mr.approval.matrix?", "response": "To use the mr.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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mr.approval.matrix", "table_name": ""}
+{"text": "How is kitchen.production.record implemented technically?", "response": "The kitchen.production.record model is defined in module: equip3_kitchen_operations. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kitchen.production.record", "table_name": ""}
+{"text": "How is pos.order.log implemented technically?", "response": "The pos.order.log model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.order.log", "table_name": ""}
+{"text": "What modules define sh.purchase.analysis.wizard?", "response": "The sh.purchase.analysis.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.analysis.wizard", "table_name": ""}
+{"text": "Tell me about the portal.wizard model.", "response": "The portal.wizard model represents Grant Portal Access in the ERP system. It contains 9 fields and is used to manage grant portal access data. Key fields include: user_ids, welcome_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "portal.wizard", "table_name": ""}
+{"text": "What foreign keys exist in sh.report.section?", "response": "The sh.report.section model has 4 relational fields: type_id -> sh.report.template; check_ids -> sh.edit.title; create_uid -> res.users; write_uid -> res.users. Many2many fields: check_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.report.section", "table_name": ""}
+{"text": "How does account.aged.trial.balance relate to other models?", "response": "The account.aged.trial.balance 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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.aged.trial.balance", "table_name": ""}
+{"text": "What are common use cases for sh.tsp.top.purchasing.product?", "response": "To use the sh.tsp.top.purchasing.product 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.tsp.top.purchasing.product", "table_name": ""}
+{"text": "What data can be stored in stock.lot.serialize.line?", "response": "The stock.lot.serialize.line model has 13 fields: stock_move_id, sequence, move_id, product_id, demand_qty, qty_per_lot, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, float: 1, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.lot.serialize.line", "table_name": ""}
+{"text": "What modules define report.account.report_hash_integrity?", "response": "The report.account.report_hash_integrity model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.account.report_hash_integrity", "table_name": ""}
+{"text": "What models are connected to crm.lead2opportunity.partner.mass?", "response": "The crm.lead2opportunity.partner.mass model has 9 relational fields: lead_id -> crm.lead; lead_tomerge_ids -> crm.lead; user_ids -> res.users; duplicated_lead_ids -> crm.lead; partner_id -> res.partner; user_id -> res.users; team_id -> crm.team; create_uid -> res.users; write_uid -> res.users. Many2many fields: lead_tomerge_ids, user_ids, duplicated_lead_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.lead2opportunity.partner.mass", "table_name": ""}
+{"text": "What are the available fields for report.sh_purchase_reports.sh_po_product_indent_doc?", "response": "The report.sh_purchase_reports.sh_po_product_indent_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_po_product_indent_doc", "table_name": ""}
+{"text": "What are the available fields for res.currency?", "response": "The res.currency model has 51 fields: 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, display_rounding_warning, name, symbol, rate, conversion, rate_ids, rounding, decimal_places, active, position, date, currency_unit_label, currency_subunit_label, tax_rate_ids, tax_rate, tax_conversion, is_taxes_rate, company_id, converted_currency, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 6, selection: 3, many2one: 6, char: 8, date: 3, boolean: 8, many2many: 2, integer: 6, float: 6, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.currency", "table_name": ""}
+{"text": "What models are connected to approval.matrix.purchase.order.line?", "response": "The approval.matrix.purchase.order.line model has 7 relational fields: user_ids -> res.users; approval_matrix_purchase_order -> approval.matrix.purchase.order; approved_users -> res.users; last_approved -> res.users; order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.purchase.order.line", "table_name": ""}
+{"text": "What operations can I perform on budget.scurve.line?", "response": "To use the budget.scurve.line model, you need to provide values for required fields: none. Readonly fields: sr_no, contract_amount, method, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "budget.scurve.line", "table_name": ""}
+{"text": "Describe the field structure of sale.excel.report.", "response": "The sale.excel.report model has 10 fields: name, excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, binary: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.excel.report", "table_name": ""}
+{"text": "How is sh.stock.move.text implemented technically?", "response": "The sh.stock.move.text model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.stock.move.text", "table_name": ""}
+{"text": "How to query budget.purchase data?", "response": "To use the budget.purchase model, you need to provide values for required fields: name, date_from, date_to, state, company_id. Readonly fields: state, state1, state2, approval_matrix, is_allowed_to_approval_matrix, approval_matrix_line_id, is_approve_button, currency_id, purchase_line_subtotal, date_today, is_use_theoretical_achievement, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "budget.purchase", "table_name": ""}
+{"text": "What modules define account.bank.statement.integrate?", "response": "The account.bank.statement.integrate model is defined in module: equip3_accounting_bank_integration. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.bank.statement.integrate", "table_name": ""}
+{"text": "Which fields in sh.purchase.bill.summary.wizard are computed?", "response": "The sh.purchase.bill.summary.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.bill.summary.wizard", "table_name": ""}
+{"text": "What business logic is in account.payment.reconcile?", "response": "To use the account.payment.reconcile model, you need to provide values for required fields: payment_type. Readonly fields: payment_type, partner_id, payment_amount, limit_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.payment.reconcile", "table_name": ""}
+{"text": "What does the base.module.upgrade model represent?", "response": "The base.module.upgrade model represents Upgrade Module in the ERP system. It contains 8 fields and is used to manage upgrade module data. Key fields include: module_info, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.module.upgrade", "table_name": ""}
+{"text": "Which fields in stock.day.average are computed?", "response": "The stock.day.average model is defined in module: equip3_inventory_control. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.day.average", "table_name": ""}
+{"text": "What business logic is in stock.inventory.approval.matrix?", "response": "To use the stock.inventory.approval.matrix model, you need to provide values for required fields: name, company_id, warehouse_id. Readonly fields: company_id, branch_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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.inventory.approval.matrix", "table_name": ""}
+{"text": "Describe the portal.wizard.user model in Odoo.", "response": "The portal.wizard.user model represents Portal User Config in the ERP system. It contains 14 fields and is used to manage portal user config data. Key fields include: wizard_id, partner_id, email, in_portal, user_id, is_customer, is_vendor, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "portal.wizard.user", "table_name": ""}
+{"text": "Can you explain the purpose of product.warehouse.cost.wizard.line?", "response": "The product.warehouse.cost.wizard.line model represents Product Warehouse Cost in the ERP system. It contains 12 fields and is used to manage product warehouse cost data. Key fields include: prod_wh_cost_id, warehouse_id, cost, company_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.warehouse.cost.wizard.line", "table_name": ""}
+{"text": "How is bo.request.matrix.reject implemented technically?", "response": "The bo.request.matrix.reject model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "bo.request.matrix.reject", "table_name": ""}
+{"text": "What does the user.order.dic model represent?", "response": "The user.order.dic model represents user.order.dic in the ERP system. It contains 20 fields and is used to manage user.order.dic data. Key fields include: report_id, list_order, saleperson, payment_report_id, list_pay, list_product, sale_analysis_id, prduct_profit_id, product, sale_categ_id, categ, product_indent_id, category_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "user.order.dic", "table_name": ""}
+{"text": "What data can be stored in nsfp.registration?", "response": "The nsfp.registration model has 15 fields: record_id, fiscal_year, start, end, last_number, registration_date, is_use, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 4, char: 5, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "nsfp.registration", "table_name": ""}
+{"text": "How to query list.top.product data?", "response": "To use the list.top.product 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "list.top.product", "table_name": ""}
+{"text": "What are the relationships in base_import.tests.models.o2m?", "response": "The base_import.tests.models.o2m model has 3 relational fields: value -> base_import.tests.models.o2m.child; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.o2m", "table_name": ""}
+{"text": "Describe the field structure of ks.message.wizard.", "response": "The ks.message.wizard model has 8 fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks.message.wizard", "table_name": ""}
+{"text": "How is report.reordering implemented technically?", "response": "The report.reordering model is defined in module: allfresh_mod_report_reordering. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.reordering", "table_name": ""}
+{"text": "How is base.language.import used in the system?", "response": "The base.language.import model represents Language Import in the ERP system. It contains 12 fields and is used to manage language import data. Key fields include: name, code, data, filename, overwrite, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.language.import", "table_name": ""}
+{"text": "What operations can I perform on approval.matrix.vendor.reject?", "response": "To use the approval.matrix.vendor.reject 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.vendor.reject", "table_name": ""}
+{"text": "Tell me about the account.general.ledger model.", "response": "The account.general.ledger model represents General Ledger Report in the ERP system. It contains 22 fields and is used to manage general ledger report data. Key fields include: journal_ids, account_ids, account_tag_ids, analytic_ids, analytic_tag_ids, display_account, titles, target_move, all_account, filter_detail, expand, date_from, date_to, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.general.ledger", "table_name": ""}
+{"text": "What foreign keys exist in ir.actions.todo?", "response": "The ir.actions.todo model has 3 relational fields: action_id -> ir.actions.actions; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.actions.todo", "table_name": ""}
+{"text": "Can you explain the purpose of accounting.flow.wizard?", "response": "The accounting.flow.wizard model represents accounting.flow.wizard in the ERP system. It contains 8 fields and is used to manage accounting.flow.wizard data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "accounting.flow.wizard", "table_name": ""}
+{"text": "How to query pos.login.history data?", "response": "To use the pos.login.history 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.login.history", "table_name": ""}
+{"text": "Can you explain the purpose of payment.acquirer.onboarding.wizard?", "response": "The payment.acquirer.onboarding.wizard model represents Payment acquire onboarding wizard in the ERP system. It contains 19 fields and is used to manage payment acquire onboarding wizard data. Key fields include: payment_method, paypal_user_type, paypal_email_account, paypal_seller_account, paypal_pdt_token, stripe_secret_key, stripe_publishable_key, manual_name, journal_name, acc_number, manual_post_msg, _data_fetched, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "What does the repair.order.make_invoice model represent?", "response": "The repair.order.make_invoice model represents Create Mass Invoice (repair) in the ERP system. It contains 8 fields and is used to manage create mass invoice (repair) data. Key fields include: group, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "repair.order.make_invoice", "table_name": ""}
+{"text": "Tell me about the warranty.tag model.", "response": "The warranty.tag model represents Warranty Tag in the ERP system. It contains 9 fields and is used to manage warranty tag data. Key fields include: tag_name, tag_desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "warranty.tag", "table_name": ""}
+{"text": "What are common use cases for report.stock.report_product_template_replenishment?", "response": "To use the report.stock.report_product_template_replenishment model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.stock.report_product_template_replenishment", "table_name": ""}
+{"text": "Can you explain the purpose of qiscus.wa.template?", "response": "The qiscus.wa.template model represents qiscus.wa.template in the ERP system. It contains 37 fields and is used to manage qiscus.wa.template data. Key fields include: name, namespace, qiscus_template_id, content_ids, category, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "qiscus.wa.template", "table_name": ""}
+{"text": "How to create records in sh.purchase.payment.report.wizard?", "response": "To use the sh.purchase.payment.report.wizard model, you need to provide values for required fields: date_start, date_end. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.purchase.payment.report.wizard", "table_name": ""}
+{"text": "Which fields in base_import.tests.models.m2o.required are computed?", "response": "The base_import.tests.models.m2o.required model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.m2o.required", "table_name": ""}
+{"text": "List all fields in the res.partner.group model.", "response": "The res.partner.group model has 13 fields: name, pricelist_applied, pricelist_id, image, height, width, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 1, many2one: 3, binary: 1, integer: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.partner.group", "table_name": ""}
+{"text": "How to query void.order.line data?", "response": "To use the void.order.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "void.order.line", "table_name": ""}
+{"text": "Show me the relational structure of mailing.trace.", "response": "The mailing.trace model has 6 relational fields: mail_mail_id -> mail.mail; mass_mailing_id -> mailing.mailing; campaign_id -> utm.campaign; links_click_ids -> link.tracker.click; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mailing.trace", "table_name": ""}
+{"text": "Show me the fields of acrux.chat.select.conversation.wizard.", "response": "The acrux.chat.select.conversation.wizard model has 8 fields: conversation_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "acrux.chat.select.conversation.wizard", "table_name": ""}
+{"text": "Show me the fields of pos.gift.card.use.", "response": "The pos.gift.card.use model has 12 fields: card_id, customer_id, pos_order_id, order_date, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.gift.card.use", "table_name": ""}
+{"text": "What does the product.template.attribute.value model represent?", "response": "The product.template.attribute.value model represents Product Template Attribute Value in the ERP system. It contains 20 fields and is used to manage product template attribute value data. Key fields include: ptav_active, name, product_attribute_value_id, attribute_line_id, price_extra, currency_id, exclude_for, product_tmpl_id, attribute_id, ptav_product_variant_ids, html_color, is_custom, display_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.template.attribute.value", "table_name": ""}
+{"text": "How does sale.adv.wizard.product.line.specific relate to other models?", "response": "The sale.adv.wizard.product.line.specific model has 5 relational fields: sale_adv_wizard_id_specific -> sale.adv.wizard; product_id -> product.product; uom_po_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.adv.wizard.product.line.specific", "table_name": ""}
+{"text": "What foreign keys exist in stock.lot.serialize?", "response": "The stock.lot.serialize model has 4 relational fields: picking_id -> stock.picking; stock_move_line_ids -> stock.lot.serialize.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.lot.serialize", "table_name": ""}
+{"text": "What business logic is in sh.purchase.category.xls?", "response": "To use the sh.purchase.category.xls model, you need to provide values for required fields: none. Readonly fields: file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.purchase.category.xls", "table_name": ""}
+{"text": "What are common use cases for customer.category?", "response": "To use the customer.category model, you need to provide values for required fields: name. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "customer.category", "table_name": ""}
+{"text": "What fields does account.tax.report.line have?", "response": "The account.tax.report.line model has 18 fields: tag_ids, report_action_id, children_line_ids, parent_id, sequence, parent_path, report_id, code, formula, name, tag_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, many2one: 5, one2many: 1, integer: 2, char: 6, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.tax.report.line", "table_name": ""}
+{"text": "What are common use cases for ir.actions.server?", "response": "To use the ir.actions.server model, you need to provide values for required fields: name, type, model_id, activity_user_type, usage, state, binding_type. Readonly fields: model_name, crud_model_name, mass_edit_apply_domain_in_lines, xml_id, website_url, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.actions.server", "table_name": ""}
+{"text": "What are common use cases for approval.matrix.blanket.order?", "response": "To use the approval.matrix.blanket.order model, you need to provide values for required fields: name, company_id, branch_id. Readonly fields: company_id, is_good_services_order, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.blanket.order", "table_name": ""}
+{"text": "List all fields in the export.product.csv model.", "response": "The export.product.csv model has 40 fields: name, product_id_attachment_id, product_id_csv_created, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 8, many2one: 6, boolean: 6, one2many: 4, selection: 2, date: 2, many2many: 2, integer: 6, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "export.product.csv", "table_name": ""}
+{"text": "What models are connected to purchase.custom.checklist.template?", "response": "The purchase.custom.checklist.template model has 3 relational fields: checklist_template -> purchase.custom.checklist; create_uid -> res.users; write_uid -> res.users. Many2many fields: checklist_template.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.custom.checklist.template", "table_name": ""}
+{"text": "How do I use the iap.account model?", "response": "To use the iap.account 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "iap.account", "table_name": ""}
+{"text": "How is replace.product.wizard used in the system?", "response": "The replace.product.wizard model represents Replace Product in the ERP system. It contains 11 fields and is used to manage replace product data. Key fields include: product_id, replace_product_id, replace_qty, is_same_product, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "replace.product.wizard", "table_name": ""}
+{"text": "Describe the ir.actions.actions model in Odoo.", "response": "The ir.actions.actions model represents Actions in the ERP system. It contains 14 fields and is used to manage actions data. Key fields include: name, type, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.actions", "table_name": ""}
+{"text": "What methods are available in link.tracker?", "response": "The link.tracker model is defined in module: link_tracker. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "link.tracker", "table_name": ""}
+{"text": "How is internal.transfer.line implemented technically?", "response": "The internal.transfer.line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "internal.transfer.line", "table_name": ""}
+{"text": "What are the technical details of snailmail.confirm.invoice?", "response": "The snailmail.confirm.invoice model is defined in module: snailmail_account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "snailmail.confirm.invoice", "table_name": ""}
+{"text": "Which fields in stock.valuation.layer.revaluation are computed?", "response": "The stock.valuation.layer.revaluation model is defined in module: stock_account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.valuation.layer.revaluation", "table_name": ""}
+{"text": "What are the available fields for account.cashbox.wizard.line?", "response": "The account.cashbox.wizard.line model has 16 fields: account_cashbox_wizard_id, coin_value, number, subtotal, cashbox_id, currency_id, pos_config_id, pos_session_id, is_closing_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, float: 2, integer: 2, boolean: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.cashbox.wizard.line", "table_name": ""}
+{"text": "What methods are available in currency.log.api?", "response": "The currency.log.api model is defined in module: equip3_accounting_multicurrency. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "currency.log.api", "table_name": ""}
+{"text": "What are the available fields for delivery.price.rule?", "response": "The delivery.price.rule model has 16 fields: name, sequence, carrier_id, variable, operator, max_value, list_base_price, list_price, variable_factor, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 3, selection: 3, float: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "delivery.price.rule", "table_name": ""}
+{"text": "How is vendor.payment.request used in the system?", "response": "The vendor.payment.request model represents Vendor Payment Request in the ERP system. It contains 16 fields and is used to manage vendor payment request data. Key fields include: name, user_id, description, company_id, branch_id, component_line_id, state, amount_total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "vendor.payment.request", "table_name": ""}
+{"text": "What is the stock.move model?", "response": "The stock.move model represents Stock Move in the ERP system. It contains 237 fields and is used to manage stock move data. Key fields include: name, sequence, priority, create_date, date, date_deadline, company_id, description_picking, product_qty, product_uom_qty, product_uom, product_uom_category_id, product_tmpl_id, location_id, location_dest_id, partner_id, move_dest_ids, move_orig_ids, picking_partner_id, note, state, price_unit, backorder_id, origin, procure_method, scrapped, scrap_ids, group_id, rule_id, propagate_cancel, delay_alert_date, picking_type_id, inventory_id, move_line_ids, move_line_nosuggest_ids, origin_returned_move_id, returned_move_ids, availability, restrict_partner_id, route_ids, warehouse_id, has_tracking, show_operations, show_details_visible, show_reserved_availability, additional, is_locked, is_initial_demand_editable, is_quantity_done_editable, reference, has_move_lines, package_level_id, picking_type_entire_packs, display_assign_serial, next_serial_count, orderpoint_id, forecast_availability, forecast_expected_date, lot_ids, created_production_id, production_id, raw_material_production_id, unbuild_id, consume_unbuild_id, allowed_operation_ids, operation_id, workorder_id, bom_line_id, byproduct_id, unit_factor, is_done, order_finished_lot_ids, should_consume_qty, use_expiration_date, to_refund, account_move_ids, stock_valuation_layer_ids, is_reconstruct_svl, scrap_return_move_id, purchase_line_id, created_purchase_line_id, sh_quality_point, sh_quality_point_id, sh_last_qc_date, sh_last_qc_state, number_of_test, created_purchase_request_line_id, purchase_request_allocation_ids, purchase_request_ids, requisition_line_ids, sale_line_id, branch_id, weight, product_description, qty_pack, is_pack, repair_id, sh_stock_move_barcode_mobile, sh_stock_move_bm_is_cont_scan, length, width, height, product_id, is_adjustable_picking, package_measure_selection, picking_state, is_existing_package, move_package_id, filter_move_package_ids, mr_line_id, move_line_sequence, serial_no, export_file, export_name, next_serial, next_serial_not_autogenerate, next_lot_not_autogenerate, is_import, is_record_confirm, product_type, is_serial_number, next_lot, qty_per_lot, is_autogenerate, picking_code, is_product_service_operation, is_product_service_operation_delivery, is_product_service_operation_receiving, serial, initial_demand, move_progress, analytic_account_group_ids, remaining, fulfillment, current_qty, scheduled_date, responsible, late_time, late_time_hours, process_status, process_time, process_time_hours, package_type, qty_in_pack, packaging_ids, package_quant_ids, measure_ids, product_id_domain, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, created_assembly_id, assembly_finished_id, assembly_component_id, assembly_unit_factor, assembly_should_consume_qty, assembly_product_free_qty, description, created_kitchen_id, kitchen_finished_id, kitchen_component_id, kitchen_unit_factor, kitchen_should_consume_qty, kitchen_product_free_qty, asp_asm_stock_id, bom_product_uom_qty, sub_total, finish_good_rework_id, type_product_bom, finish_good_rework_finished_id, finish_good_rework_created_kitchen_id, finish_good_rework_by_product_id, assembly_record_type, assembly_confirm_date, assembly_product_id, assembly_bom_id, assembly_svl_value, assembly_difference, exp_date, qty_bundle, id_bundle, package_barcode, kitchen_confirm_date, kitchen_product_id, kitchen_bom_id, kitchen_svl_value, kitchen_difference, product_warehouse, product_location, expired_date, product_barcode, vendor_id, state_expired, state_check, picking_type_code, reserved_by_id, reserved_availability, is_reserved, picking_id, origin_src_location, origin_dest_location, picking_reference, is_transit, date_done, return_reason, action, is_transfer_in, is_transfer_out, quantity_done, volume, movement_type, cost, combo_item_id, pos_branch_id, pos_order_line_id, so_antar_badan, po_antar_badan, sale_order_id, purchase_order_id, date_done_real, taxes_id, price_subtotal, price_tax, price_total, price_untaxed_amount, discount_amount, price_discount, currency_id, returned_qty, remaining_checked_qty, id, display_name, create_uid, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.move", "table_name": ""}
+{"text": "What models are connected to sales.order.commission?", "response": "The sales.order.commission model has 6 relational fields: user_id -> res.users; job_id -> hr.job; order_id -> sale.order; invoice_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sales.order.commission", "table_name": ""}
+{"text": "How to query account.partial.reconcile data?", "response": "To use the account.partial.reconcile model, you need to provide values for required fields: debit_move_id, credit_move_id. Readonly fields: company_currency_id, debit_currency_id, credit_currency_id, max_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.partial.reconcile", "table_name": ""}
+{"text": "List all fields in the ks_dashboard_ninja.board model.", "response": "The ks_dashboard_ninja.board model has 30 fields: name, ks_dashboard_items_ids, ks_dashboard_menu_name, ks_dashboard_top_menu_id, ks_dashboard_client_action_id, ks_dashboard_menu_id, ks_dashboard_state, ks_dashboard_active, ks_dashboard_group_access, ks_dashboard_start_date, ks_dashboard_end_date, ks_date_filter_selection, ks_data_formatting, ks_gridstack_config, ks_dashboard_default_template, ks_set_interval, ks_dashboard_menu_sequence, ks_child_dashboard_ids, ks_dashboard_defined_filters_ids, ks_dashboard_custom_filters_ids, ks_croessel_speed, ks_dashboard_icon_budget, ks_dashboard_menu_icon_class, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 7, one2many: 4, many2one: 6, boolean: 1, many2many: 1, datetime: 5, selection: 4, integer: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.board", "table_name": ""}
+{"text": "Show me the relational structure of receipt.voucher.line.", "response": "The receipt.voucher.line model has 5 relational fields: receipt_voucher_id -> receipt.voucher; invoice_id -> account.move; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "receipt.voucher.line", "table_name": ""}
+{"text": "What fields does do.approval_matrix_detail have?", "response": "The do.approval_matrix_detail model has 11 fields: location_name, usage, company_id, do_approval_matrix_id2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "do.approval_matrix_detail", "table_name": ""}
+{"text": "Can you explain the purpose of account.general.ledger?", "response": "The account.general.ledger model represents General Ledger Report in the ERP system. It contains 22 fields and is used to manage general ledger report data. Key fields include: journal_ids, account_ids, account_tag_ids, analytic_ids, analytic_tag_ids, display_account, titles, target_move, all_account, filter_detail, expand, date_from, date_to, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.general.ledger", "table_name": ""}
+{"text": "What operations can I perform on free.product.lines?", "response": "To use the free.product.lines model, you need to provide values for required fields: product_id, description, quantity, uom_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "free.product.lines", "table_name": ""}
+{"text": "Describe the field structure of rma.reject.reason.", "response": "The rma.reject.reason model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "rma.reject.reason", "table_name": ""}
+{"text": "Describe the many2many relations for link.tracker.", "response": "The link.tracker model has 8 relational fields: link_code_ids -> link.tracker.code; link_click_ids -> link.tracker.click; mass_mailing_id -> mailing.mailing; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "link.tracker", "table_name": ""}
+{"text": "What fields does pos.product.bom have?", "response": "The pos.product.bom model has 16 fields: product_id, name, product_tmpl_id, product_qty, product_uom_id, product_bom_line_ids, state, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, char: 2, float: 1, one2many: 1, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.product.bom", "table_name": ""}
+{"text": "Tell me about the sh.stock.move.qc.measurement model.", "response": "The sh.stock.move.qc.measurement model represents Stock Move Measurement in the ERP system. It contains 12 fields and is used to manage stock move measurement data. Key fields include: product_id, quality_point_id, sh_measure, sh_message, picking_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.stock.move.qc.measurement", "table_name": ""}
+{"text": "What modules define report.equip3_kitchen_operations.report_cooking_list?", "response": "The report.equip3_kitchen_operations.report_cooking_list model is defined in module: equip3_kitchen_operations. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_kitchen_operations.report_cooking_list", "table_name": ""}
+{"text": "Describe the many2many relations for approval.matrix.purchase.request.line.", "response": "The approval.matrix.purchase.request.line model has 7 relational fields: user_ids -> res.users; approval_matrix_purchase_request -> approval.matrix.purchase.request; request_id -> purchase.request; approved_users -> res.users; last_approved -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.purchase.request.line", "table_name": ""}
+{"text": "What modules define ai.chat.session?", "response": "The ai.chat.session model is defined in module: ai_chat_agent. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ai.chat.session", "table_name": ""}
+{"text": "What fields does account.asset.category have?", "response": "The account.asset.category model has 41 fields: active, name, account_analytic_id, analytic_tag_ids, account_asset_id, account_depreciation_id, account_depreciation_expense_id, journal_id, company_id, method_number, method_period, method_progress_factor, method_time, method_end, prorata, open_asset, group_entries, type, branch_id, cut_off_asset_date, date_first_depreciation, account_sales_id, account_revaluation_surplus_id, account_revaluation_loss_id, method, is_monthly_depreciation, is_reset_january, account_sales_profit, account_sales_loss, dispose_account, sequence_id, set_sequence, sequence_number_next, is_fiscal_asset_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 7, char: 3, many2one: 16, many2many: 1, integer: 5, float: 1, selection: 4, date: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.asset.category", "table_name": ""}
+{"text": "What models are connected to mrp.production?", "response": "The mrp.production model has 43 relational fields: product_id -> product.product; allowed_product_ids -> product.product; product_tmpl_id -> product.template; product_uom_id -> uom.uom; lot_producing_id -> stock.production.lot; product_uom_category_id -> uom.category; picking_type_id -> stock.picking.type; location_src_id -> stock.location; location_dest_id -> stock.location; bom_id -> mrp.bom; move_raw_ids -> stock.move; move_finished_ids -> stock.move; move_byproduct_ids -> stock.move; finished_move_line_ids -> stock.move.line; workorder_ids -> mrp.workorder; move_dest_ids -> stock.move; user_id -> res.users; company_id -> res.company; procurement_group_id -> procurement.group; orderpoint_id -> stock.warehouse.orderpoint; scrap_ids -> stock.scrap; production_location_id -> stock.location; picking_ids -> stock.picking; sh_mrp_quality_check_ids -> sh.mrp.quality.check; sh_mrp_quality_alert_ids -> sh.mrp.quality.alert; sh_mrp_pass_fail_ids -> sh.mrp.pass.fail; sh_mrp_pics_ids -> sh.mrp.pics; sh_mrp_measurement_ids -> sh.mrp.measurement; sh_mrp_qc_measurement_ids -> sh.mrp.qc.measurement; attachment_ids -> ir.attachment; sh_mrp_quality_point_id -> sh.qc.point; partner_id -> res.partner; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: allowed_product_ids, picking_ids, attachment_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.production", "table_name": ""}
+{"text": "How to create records in report.sh_inventory_mrp_qc.quality_check_doc?", "response": "To use the report.sh_inventory_mrp_qc.quality_check_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_inventory_mrp_qc.quality_check_doc", "table_name": ""}
+{"text": "What fields does sh.quality.check have?", "response": "The sh.quality.check model has 43 fields: state, product_id, sh_picking, sh_date, sh_control_point, control_point_id, sh_norm, qc_type, company_id, attachment_ids, text_message, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 4, many2one: 9, date: 3, char: 5, float: 1, many2many: 3, text: 1, one2many: 4, boolean: 5, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.quality.check", "table_name": ""}
+{"text": "Show me the fields of setu.inventory.overstock.report.", "response": "The setu.inventory.overstock.report model has 16 fields: advance_stock_days, stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, binary: 1, date: 2, many2many: 4, many2one: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.overstock.report", "table_name": ""}
+{"text": "What methods are available in stock.quantity.history?", "response": "The stock.quantity.history model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.quantity.history", "table_name": ""}
+{"text": "Describe the field structure of group.card.", "response": "The group.card model has 36 fields: card_group_img, card_group_name, card_group_active, company_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 5, boolean: 6, many2one: 6, one2many: 4, selection: 2, date: 2, many2many: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "group.card", "table_name": ""}
+{"text": "What operations can I perform on account.bank.statement.line.wizard?", "response": "To use the account.bank.statement.line.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.bank.statement.line.wizard", "table_name": ""}
+{"text": "What are the relationships in payment.voucher.matrix.reject?", "response": "The payment.voucher.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "payment.voucher.matrix.reject", "table_name": ""}
+{"text": "What are the relationships in purchase.target.based.on?", "response": "The purchase.target.based.on model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.target.based.on", "table_name": ""}
+{"text": "What are the relationships in sh.stock.move.text?", "response": "The sh.stock.move.text model has 5 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; picking_id -> stock.picking; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.stock.move.text", "table_name": ""}
+{"text": "What is the product.image model?", "response": "The product.image model represents Product Image in the ERP system. It contains 19 fields and is used to manage product image data. Key fields include: name, sequence, image_1920, product_tmpl_id, product_variant_id, video_url, embed_code, can_image_1024_be_zoomed, image_1024, image_512, image_256, image_128, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.image", "table_name": ""}
+{"text": "What business logic is in account.aged.trial.balance?", "response": "To use the account.aged.trial.balance model, you need to provide values for required fields: period_length, journal_ids, result_selection, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.aged.trial.balance", "table_name": ""}
+{"text": "How to query pos.promotion.price data?", "response": "To use the pos.promotion.price model, you need to provide values for required fields: product_id, minimum_quantity, price_down, promotion_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion.price", "table_name": ""}
+{"text": "What are common use cases for account.tax.map.purchase.line?", "response": "To use the account.tax.map.purchase.line model, you need to provide values for required fields: map_id, child_company_id. Readonly fields: company_id, target_company, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.tax.map.purchase.line", "table_name": ""}
+{"text": "What are the available fields for account.fiscal.year?", "response": "The account.fiscal.year model has 11 fields: name, date_from, date_to, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, date: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.fiscal.year", "table_name": ""}
+{"text": "How does action.data relate to other models?", "response": "The action.data model has 3 relational fields: action_id -> ir.actions.actions; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "action.data", "table_name": ""}
+{"text": "What are the available fields for sh.qc.team.type?", "response": "The sh.qc.team.type model has 15 fields: name, team_id, check_count, alert_count, pending_qc_count, failed_qc_count, passed_qc_count, partially_passed_qc_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 7, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.qc.team.type", "table_name": ""}
+{"text": "What are the relationships in pos.cashier.change.wizard?", "response": "The pos.cashier.change.wizard model has 3 relational fields: pos_branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.cashier.change.wizard", "table_name": ""}
+{"text": "How does limit.approval.matrix.sale.reject relate to other models?", "response": "The limit.approval.matrix.sale.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "limit.approval.matrix.sale.reject", "table_name": ""}
+{"text": "Describe the implementation of sale.order.repair.", "response": "The sale.order.repair model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.order.repair", "table_name": ""}
+{"text": "What are common use cases for utm.medium?", "response": "To use the utm.medium 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "utm.medium", "table_name": ""}
+{"text": "How is stock.inventory.request.matrix.reject used in the system?", "response": "The stock.inventory.request.matrix.reject model represents Stock Inventory Matrix Reject in the ERP system. It contains 8 fields and is used to manage stock inventory matrix reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.inventory.request.matrix.reject", "table_name": ""}
+{"text": "How is ir.actions.act_window.view implemented technically?", "response": "The ir.actions.act_window.view model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.actions.act_window.view", "table_name": ""}
+{"text": "What business logic is in account.balance.report?", "response": "To use the account.balance.report model, you need to provide values for required fields: journal_ids, display_account, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.balance.report", "table_name": ""}
+{"text": "How does account.tax.digunggung relate to other models?", "response": "The account.tax.digunggung model has 4 relational fields: partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.tax.digunggung", "table_name": ""}
+{"text": "What are common use cases for account.group.template?", "response": "To use the account.group.template model, you need to provide values for required fields: chart_template_id, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.group.template", "table_name": ""}
+{"text": "Show me the fields of intrawarehouse.transfer.", "response": "The intrawarehouse.transfer model has 8 fields: interawarehouse_transfer_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "How do I use the purchase.tender.xls.report model?", "response": "To use the purchase.tender.xls.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.tender.xls.report", "table_name": ""}
+{"text": "List all fields in the _unknown model.", "response": "The _unknown model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "_unknown", "table_name": ""}
+{"text": "What does the change.lock.date model represent?", "response": "The change.lock.date model represents Change Lock Date in the ERP system. It contains 11 fields and is used to manage change lock date data. Key fields include: company_id, period_lock_date, fiscalyear_lock_date, tax_lock_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "change.lock.date", "table_name": ""}
+{"text": "Describe the field structure of report.eq_scrap_order_report.scrap_order_report.", "response": "The report.eq_scrap_order_report.scrap_order_report model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.eq_scrap_order_report.scrap_order_report", "table_name": ""}
+{"text": "Describe the field structure of list.pay.", "response": "The list.pay model has 16 fields: order_dic_id, cash, bank, total, invoice, customer, invoice_date, payments_date, salesperson, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, float: 3, char: 4, datetime: 5, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "list.pay", "table_name": ""}
+{"text": "Describe the sh.announcement model in Odoo.", "response": "The sh.announcement model represents sh.announcement in the ERP system. It contains 24 fields and is used to manage sh.announcement data. Key fields include: name, description, active, user_ids, font_color, background_color, date, is_animation, direction, simple_text, description_text, font_size, padding, font_family, google_font_family, is_popup_notification, notification_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.announcement", "table_name": ""}
+{"text": "What does the ir.cron model represent?", "response": "The ir.cron model represents Scheduled Actions in the ERP system. It contains 56 fields and is used to manage scheduled actions data. Key fields include: ir_actions_server_id, cron_name, user_id, active, interval_number, interval_type, numbercall, doall, nextcall, lastcall, priority, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, name, type, sequence, model_id, model_name, code, child_ids, crud_model_id, crud_model_name, link_field_id, fields_lines, groups_id, mass_edit_line_ids, mass_edit_apply_domain_in_lines, mass_edit_message, partner_ids, channel_ids, template_id, activity_type_id, activity_summary, activity_note, activity_date_deadline_range, activity_date_deadline_range_type, activity_user_type, activity_user_id, activity_user_field_name, usage, state, sms_template_id, sms_mass_keep_log, xml_id, website_path, website_url, website_published, help, binding_model_id, binding_type, binding_view_types.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.cron", "table_name": ""}
+{"text": "Show me the fields of sh.custom.tab.purchase.", "response": "The sh.custom.tab.purchase model has 15 fields: name, label, groups, sequence, view_id, tab_list, invisible_tab, sh_position, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2many: 1, integer: 2, many2one: 3, selection: 2, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.custom.tab.purchase", "table_name": ""}
+{"text": "How is access.rights.profile implemented technically?", "response": "The access.rights.profile model is defined in module: equip3_general_features. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "access.rights.profile", "table_name": ""}
+{"text": "Show me the fields of hr.departure.wizard.", "response": "The hr.departure.wizard model has 12 fields: departure_reason, departure_description, departure_date, employee_id, archive_private_address, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, text: 1, date: 1, many2one: 3, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "hr.departure.wizard", "table_name": ""}
+{"text": "What models are connected to sale.data.margin?", "response": "The sale.data.margin model has 6 relational fields: partner_id -> res.partner; company_id -> res.company; branch_id -> res.branch; order_line -> sale.data.margin.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.data.margin", "table_name": ""}
+{"text": "What fields does ks_dashboard_ninja.board_template have?", "response": "The ks_dashboard_ninja.board_template model has 13 fields: name, ks_gridstack_config, ks_item_count, ks_template_type, ks_dashboard_item_ids, ks_dashboard_board_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 2, selection: 1, one2many: 1, many2one: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.board_template", "table_name": ""}
+{"text": "What modules define sh.custom.tab.purchase?", "response": "The sh.custom.tab.purchase model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.custom.tab.purchase", "table_name": ""}
+{"text": "Describe the asset.depreciation.confirmation.wizard model in Odoo.", "response": "The asset.depreciation.confirmation.wizard model represents asset.depreciation.confirmation.wizard in the ERP system. It contains 8 fields and is used to manage asset.depreciation.confirmation.wizard data. Key fields include: date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "asset.depreciation.confirmation.wizard", "table_name": ""}
+{"text": "What is the website.published.mixin model?", "response": "The website.published.mixin model represents Website Published Mixin in the ERP system. It contains 7 fields and is used to manage website published mixin data. Key fields include: website_published, is_published, can_publish, website_url, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "website.published.mixin", "table_name": ""}
+{"text": "What models are connected to account.move.template?", "response": "The account.move.template model has 22 relational fields: journal_id -> account.journal; suitable_journal_ids -> account.journal; company_id -> res.company; company_currency_id -> res.currency; currency_id -> res.currency; line_ids -> account.move.template.line; partner_id -> res.partner; payment_id -> account.payment; statement_line_id -> account.bank.statement.line; reversed_entry_id -> account.move.template; reversal_move_id -> account.move.template; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: suitable_journal_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.move.template", "table_name": ""}
+{"text": "Describe the field structure of generate.opening.entries.", "response": "The generate.opening.entries model has 12 fields: name, old_fiscal_year_id, new_fiscal_year_id, journal_id, period_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 6, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "generate.opening.entries", "table_name": ""}
+{"text": "What business logic is in mrp.bom.operation?", "response": "To use the mrp.bom.operation model, you need to provide values for required fields: sequence, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mrp.bom.operation", "table_name": ""}
+{"text": "Tell me about the crm.phonecall model.", "response": "The crm.phonecall model represents Phonecall in the ERP system. It contains 46 fields and is used to manage phonecall data. Key fields include: date_action_last, date_action_next, create_date, team_id, user_id, partner_id, company_id, description, state, email_from, date_open, name, active, duration, tag_ids, partner_phone, partner_mobile, priority, date_closed, date, opportunity_id, direction, campaign_id, source_id, medium_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.phonecall", "table_name": ""}
+{"text": "What foreign keys exist in material.request.matrix.reject?", "response": "The material.request.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "material.request.matrix.reject", "table_name": ""}
+{"text": "How does account.journal.group relate to other models?", "response": "The account.journal.group model has 4 relational fields: company_id -> res.company; excluded_journal_ids -> account.journal; create_uid -> res.users; write_uid -> res.users. Many2many fields: excluded_journal_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.journal.group", "table_name": ""}
+{"text": "How is sh.sale.details.report.wizard implemented technically?", "response": "The sh.sale.details.report.wizard model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.sale.details.report.wizard", "table_name": ""}
+{"text": "Describe the field structure of purchase.line.wiz.", "response": "The purchase.line.wiz model has 9 fields: purchase_order_line_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.line.wiz", "table_name": ""}
+{"text": "What are the technical details of pos.loyalty.update.point?", "response": "The pos.loyalty.update.point model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.loyalty.update.point", "table_name": ""}
+{"text": "Tell me about the quotation.amount model.", "response": "The quotation.amount model represents quotation.amount in the ERP system. It contains 11 fields and is used to manage quotation.amount data. Key fields include: order_id, currency_id, amount, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "quotation.amount", "table_name": ""}
+{"text": "What modules define mail.activity.mixin?", "response": "The mail.activity.mixin model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.activity.mixin", "table_name": ""}
+{"text": "What methods are available in mailing.trace?", "response": "The mailing.trace model is defined in module: mass_mailing. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mailing.trace", "table_name": ""}
+{"text": "What fields does sh.sale.analysis.xls have?", "response": "The sh.sale.analysis.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.sale.analysis.xls", "table_name": ""}
+{"text": "What is the account.reconcile.model.line.template model?", "response": "The account.reconcile.model.line.template model represents Reconcile Model Line Template in the ERP system. It contains 15 fields and is used to manage reconcile model line template data. Key fields include: model_id, sequence, account_id, label, amount_type, amount_string, force_tax_included, tax_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.reconcile.model.line.template", "table_name": ""}
+{"text": "Show me the relational structure of wizard.product.bundle.bi.", "response": "The wizard.product.bundle.bi model has 4 relational fields: product_id -> product.product; bi_pack_ids -> bi.product.pack; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "wizard.product.bundle.bi", "table_name": ""}
+{"text": "What does the sale.order.report model represent?", "response": "The sale.order.report model represents Sale Order Report in the ERP system. It contains 11 fields and is used to manage sale order report data. Key fields include: start_date, end_date, company_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.order.report", "table_name": ""}
+{"text": "How do I use the stock.picking model?", "response": "To use the stock.picking model, you need to provide values for required fields: move_type, location_dest_id, picking_type_id, location_id, branch_id. Readonly fields: name, backorder_id, group_id, date_deadline, has_deadline_issue, delay_alert_date, json_popover, location_dest_id, has_scrap_move, picking_type_id, picking_type_code, picking_type_entire_packs, hide_picking_type, move_line_exist, has_packages, show_check_availability, show_mark_as_todo, show_validate, use_create_lots, product_id, show_operations, show_reserved, show_lots_text, has_tracking, products_availability, products_availability_state, sh_quality_check_ids, sh_quality_alert_ids, qc_count, qc_alert_count, need_qc, qc_fail, qc_pass, full_pass, is_mandatory, delivery_type, weight, carrier_tracking_url, weight_uom_name, package_ids, weight_bulk, shipping_weight, is_return_picking, return_label_ids, sh_stock_bm_is_cont_scan, website_id, is_transfer_in, is_transfer_out, location_id, date_done, company_id, is_show_location, branch_id, filter_branch_ids, filter_source_location_ids, filter_dest_location_ids, filter_operation_picking_type_ids, journal_cancel, merge_info, is_return_orders, return_date_limit, origin_src_location, origin_dest_location, check_second_picking_reserve, process_time, process_time_hours, show_entire_packs, is_mbs_on_transfer_operations, is_source_package, rn_approval_matrix, is_rn_request_approval_matrix, status_1, status_2, status_3, status_4, approved_matrix_ids, approval_matrix_line_id, is_approve_button, is_reset_to_draft, check_product, is_adjustable_picking, do_approval_matrix, is_do_request_approval_matrix, do_approved_matrix_ids, do_approval_matrix_line_id, is_approve_button_do, is_reset_to_draft_do, force_validate_button, current_user, partner_id_domain, owner_id_domain, journal_button, qty_can_minus_boolean, state, is_deployed, is_expired_tranfer, fulfillment, operation_warehouse_id, pos_branch_id, is_dropship, customer_partner_id, is_vendor_taxes, purchase_id, company_currency_id, amount_subtotal, amount_tax, amount_total, amount_discount, amount_untaxed, discount_promotions_amount, return_request_history_ids, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.picking", "table_name": ""}
+{"text": "What are the relationships in report_excel_import_wizard?", "response": "The report_excel_import_wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report_excel_import_wizard", "table_name": ""}
+{"text": "What are the technical details of sh.payment.report.wizard?", "response": "The sh.payment.report.wizard model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.payment.report.wizard", "table_name": ""}
+{"text": "What methods are available in ir.qweb?", "response": "The ir.qweb model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.qweb", "table_name": ""}
+{"text": "How to query ir.qweb.field.duration data?", "response": "To use the ir.qweb.field.duration model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.duration", "table_name": ""}
+{"text": "What are the available fields for sh.top.customers.xls?", "response": "The sh.top.customers.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.top.customers.xls", "table_name": ""}
+{"text": "What are the technical details of expiry.picking.confirmation?", "response": "The expiry.picking.confirmation model is defined in module: product_expiry. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "expiry.picking.confirmation", "table_name": ""}
+{"text": "How to create records in vendor.deposit?", "response": "To use the vendor.deposit model, you need to provide values for required fields: payment_date, deposit_reconcile_journal_id, deposit_account_id, currency_id. Readonly fields: name, remaining_amount, return_deposit, is_show_cancel, invoice_count, reconcile_count, filter_deposit_account_ids, approval_matrix_id, is_vendor_deposit_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, deposit_history, filter_branch_ids, move_id, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "vendor.deposit", "table_name": ""}
+{"text": "What is the account.tax.repartition.line model?", "response": "The account.tax.repartition.line model represents Tax Repartition Line in the ERP system. It contains 19 fields and is used to manage tax repartition line data. Key fields include: factor_percent, factor, repartition_type, account_id, tag_ids, invoice_tax_id, refund_tax_id, tax_id, tax_fiscal_country_id, company_id, sequence, use_in_tax_closing, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.tax.repartition.line", "table_name": ""}
+{"text": "Show me the fields of pos.payment.method.", "response": "The pos.payment.method model has 54 fields: name, receivable_account_id, is_cash_count, cash_journal_id, split_transactions, open_session_ids, config_ids, company_id, use_payment_terminal, hide_use_payment_terminal, active, apply_charges, fees_amount, fees_type, fees_product_id, optional, shortcut_key, jr_use_for, fullfill_amount, shortcut_keyboard, cheque_bank_information, discount, discount_type, discount_amount, discount_product_id, is_bank, generate_invoice, invoice_partner_id, able_use_card, is_mdr, is_mdr_discount, mdr_paid_by, mdr_intermediary_account_id, mdr_ids, is_receivables, account_journal_id, is_receivables_show, is_deposit_payment, is_edc_bca, is_edc_manual_input, edc_port, trans_type, trans_type_code, is_payment_edc, payment_edc_url, installment_tenor_ids, installment_plan, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 8, many2one: 10, boolean: 21, many2many: 3, selection: 5, float: 2, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.payment.method", "table_name": ""}
+{"text": "How to query stock.valuation.layer.revaluation data?", "response": "To use the stock.valuation.layer.revaluation model, you need to provide values for required fields: company_id, currency_id, product_id, added_value. Readonly fields: company_id, currency_id, property_valuation, product_uom_name, current_value_svl, current_quantity_svl, new_value, new_value_by_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.valuation.layer.revaluation", "table_name": ""}
+{"text": "How is website.track implemented technically?", "response": "The website.track model is defined in module: website. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.track", "table_name": ""}
+{"text": "Show me the relational structure of sh.qc.team.type.", "response": "The sh.qc.team.type model has 3 relational fields: team_id -> sh.qc.team; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.qc.team.type", "table_name": ""}
+{"text": "What is the base.partner.merge.automatic.wizard model?", "response": "The base.partner.merge.automatic.wizard model represents Merge Partner Wizard in the ERP system. It contains 21 fields and is used to manage merge partner wizard data. Key fields include: group_by_email, group_by_name, group_by_is_company, group_by_vat, group_by_parent_id, state, number_group, current_line_id, line_ids, partner_ids, dst_partner_id, exclude_contact, exclude_journal_item, maximum_group, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.partner.merge.automatic.wizard", "table_name": ""}
+{"text": "Describe the implementation of blanketwiz.blanketwiz.", "response": "The blanketwiz.blanketwiz model is defined in module: blanket_sale_order_app. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "blanketwiz.blanketwiz", "table_name": ""}
+{"text": "What are the available fields for account.cashbox.line?", "response": "The account.cashbox.line model has 15 fields: coin_value, number, subtotal, cashbox_id, currency_id, pos_config_id, pos_session_id, is_closing_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 2, integer: 2, many2one: 6, boolean: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.cashbox.line", "table_name": ""}
+{"text": "What are the relationships in sh.product.barcode.mobile.wizard?", "response": "The sh.product.barcode.mobile.wizard model has 4 relational fields: company_id -> res.company; product_line_id -> sh.product.barcode.mobile.wizard.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.product.barcode.mobile.wizard", "table_name": ""}
+{"text": "How to query sh.sale.category.wizard data?", "response": "To use the sh.sale.category.wizard model, you need to provide values for required fields: sh_end_date, sh_start_date. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.sale.category.wizard", "table_name": ""}
+{"text": "Tell me about the report.dynamic_accounts_report.balance_sheet model.", "response": "The report.dynamic_accounts_report.balance_sheet model represents BalanceSheet Report in the ERP system. It contains 3 fields and is used to manage balancesheet report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.dynamic_accounts_report.balance_sheet", "table_name": ""}
+{"text": "How does sale.order.pricelist.wizard.line relate to other models?", "response": "The sale.order.pricelist.wizard.line model has 6 relational fields: pricelist_id -> sale.order.pricelist.wizard; sh_pricelist_id -> product.pricelist; sh_unit_measure -> uom.uom; line_id -> sale.order.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.pricelist.wizard.line", "table_name": ""}
+{"text": "Show me the relational structure of pos.promotion.discount.category.", "response": "The pos.promotion.discount.category model has 5 relational fields: category_id -> pos.category; category_ids -> pos.category; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: category_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.promotion.discount.category", "table_name": ""}
+{"text": "Which fields in equip3.pos.membership.report are computed?", "response": "The equip3.pos.membership.report model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "equip3.pos.membership.report", "table_name": ""}
+{"text": "What models are connected to im_livechat.report.channel?", "response": "The im_livechat.report.channel model has 4 relational fields: channel_id -> mail.channel; livechat_channel_id -> im_livechat.channel; country_id -> res.country; partner_id -> res.partner. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "im_livechat.report.channel", "table_name": ""}
+{"text": "How is auditlog.log.line used in the system?", "response": "The auditlog.log.line model represents Auditlog - Log details (fields updated) in the ERP system. It contains 25 fields and is used to manage auditlog - log details (fields updated) data. Key fields include: field_id, log_id, old_value, new_value, old_value_text, new_value_text, field_name, field_description, name, model_id, model_name, model_model, res_id, user_id, method, http_session_id, http_request_id, log_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "auditlog.log.line", "table_name": ""}
+{"text": "Which fields in acrux.chat.select.conversation.wizard are computed?", "response": "The acrux.chat.select.conversation.wizard model is defined in module: acrux_chat_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "acrux.chat.select.conversation.wizard", "table_name": ""}
+{"text": "Describe the pmps.adv.wizard.product.line.specific model in Odoo.", "response": "The pmps.adv.wizard.product.line.specific model represents Purchase Multi Pro Selection Adv Wizard Pro Line Specific in the ERP system. It contains 13 fields and is used to manage purchase multi pro selection adv wizard pro line specific data. Key fields include: pmps_adv_wizard_id_specific, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pmps.adv.wizard.product.line.specific", "table_name": ""}
+{"text": "How to query weight.scale.barcode.format data?", "response": "To use the weight.scale.barcode.format model, you need to provide values for required fields: none. Readonly fields: total_digit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "weight.scale.barcode.format", "table_name": ""}
+{"text": "Show me the relational structure of hide.chatter.", "response": "The hide.chatter model has 4 relational fields: access_management_id -> access.management; model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hide.chatter", "table_name": ""}
+{"text": "What are the relationships in theme.ir.ui.view?", "response": "The theme.ir.ui.view model has 3 relational fields: copy_ids -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "theme.ir.ui.view", "table_name": ""}
+{"text": "What are the relationships in res.country.group?", "response": "The res.country.group model has 4 relational fields: country_ids -> res.country; pricelist_ids -> product.pricelist; create_uid -> res.users; write_uid -> res.users. Many2many fields: country_ids, pricelist_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.country.group", "table_name": ""}
+{"text": "Describe the many2many relations for portal.wizard.", "response": "The portal.wizard model has 3 relational fields: user_ids -> portal.wizard.user; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "portal.wizard", "table_name": ""}
+{"text": "What data can be stored in report.excel?", "response": "The report.excel model has 28 fields: name, active, out_file_name, data, doc_count, datas_fname, template_name_id, sheet_reference, description, description_report, root_model_id, ir_values_id, show_level, show_autofilter, report_excel_param_ids, report_id, report_excel_param_content, report_excel_section_ids, send_email, email_template_id, report_lang_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 6, boolean: 4, binary: 1, integer: 3, many2one: 7, text: 2, one2many: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.excel", "table_name": ""}
+{"text": "Describe the field structure of sale.data.margin.", "response": "The sale.data.margin model has 14 fields: partner_id, company_id, branch_id, title, order_line, date_order, margin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, one2many: 1, datetime: 4, float: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.data.margin", "table_name": ""}
+{"text": "What modules define blanket.quotation.line?", "response": "The blanket.quotation.line model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "blanket.quotation.line", "table_name": ""}
+{"text": "What modules define intrawarehouse.transfer?", "response": "The intrawarehouse.transfer model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "What is the queue.jobs.to.done model?", "response": "The queue.jobs.to.done model represents Set all selected jobs to done in the ERP system. It contains 8 fields and is used to manage set all selected jobs to done data. Key fields include: job_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "queue.jobs.to.done", "table_name": ""}
+{"text": "How to create records in ir.qweb.field.duration?", "response": "To use the ir.qweb.field.duration model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.duration", "table_name": ""}
+{"text": "Describe the many2many relations for stock.picking.type.", "response": "The stock.picking.type model has 13 relational fields: sequence_id -> ir.sequence; default_location_src_id -> stock.location; default_location_dest_id -> stock.location; return_picking_type_id -> stock.picking.type; warehouse_id -> stock.warehouse; company_id -> res.company; branch_id -> res.branch; filter_location_ids -> stock.location; stock_picking_dasboard_id -> stock.picking.type.dashboard; picking_ids -> stock.picking; pos_branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_location_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.picking.type", "table_name": ""}
+{"text": "Show me the fields of sale.excel.report.", "response": "The sale.excel.report model has 10 fields: name, excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, binary: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.excel.report", "table_name": ""}
+{"text": "Tell me about the forecast.quantity model.", "response": "The forecast.quantity model represents Forecast Quantity in the ERP system. It contains 11 fields and is used to manage forecast quantity data. Key fields include: schedule_date, reference, product_id, source_location, destination_location, forecast_qty, product_uom, state, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "forecast.quantity", "table_name": ""}
+{"text": "Describe the field structure of ir.logging.", "response": "The ir.logging model has 15 fields: create_uid, create_date, write_uid, write_date, name, type, dbname, level, message, path, func, line, id, display_name, __last_update. Field types distribution: integer: 3, datetime: 3, char: 7, selection: 1, text: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.logging", "table_name": ""}
+{"text": "Show me the relational structure of hr.job.", "response": "The hr.job model has 11 relational fields: employee_ids -> hr.employee; department_id -> hr.department; company_id -> res.company; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hr.job", "table_name": ""}
+{"text": "What fields does res.users.access.report.wizard have?", "response": "The res.users.access.report.wizard model has 14 fields: group_ids, show_login, sort_type, sort_type_mode, user_tag_ids, show_archived, show_group_category, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, boolean: 3, selection: 2, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.users.access.report.wizard", "table_name": ""}
+{"text": "What fields does approval.matrix.direct.purchase have?", "response": "The approval.matrix.direct.purchase model has 46 fields: name, company_id, branch_id, minimum_amt, maximum_amt, approval_matrix_direct_purchase_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. Field types distribution: char: 7, many2one: 10, float: 2, one2many: 5, boolean: 6, selection: 3, date: 2, many2many: 2, integer: 5, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.direct.purchase", "table_name": ""}
+{"text": "What foreign keys exist in pos.gift.card.type?", "response": "The pos.gift.card.type model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.gift.card.type", "table_name": ""}
+{"text": "How to query sh.qc.alert.stage data?", "response": "To use the sh.qc.alert.stage model, you need to provide values for required fields: none. Readonly fields: activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.qc.alert.stage", "table_name": ""}
+{"text": "What is the sale.order model?", "response": "The sale.order model represents Sales Order in the ERP system. It contains 289 fields and is used to manage sales order data. Key fields include: origin, client_order_ref, reference, is_expired, require_signature, require_payment, create_date, user_id, pricelist_id, currency_id, invoice_count, invoice_ids, invoice_status, amount_by_group, currency_rate, fiscal_position_id, team_id, signature, signed_by, signed_on, amount_undiscounted, type_name, transaction_ids, authorized_transaction_ids, show_update_pricelist, tag_ids, applied_coupon_ids, generated_coupon_ids, reward_amount, no_code_promo_program_ids, code_promo_program_id, promo_code, sale_order_option_ids, purchase_order_count, incoterm, picking_policy, picking_ids, delivery_count, procurement_group_id, effective_date, expected_date, json_popover, show_json_popover, website_order_line, cart_quantity, only_services, is_abandoned_cart, cart_recovery_email_sent, website_id, conversation_id, internal_id, inter_transfer_count, client_order_id, discount_amt, discount_amt_line, warranty_sale, recurring_rule_type, recurring_interval, delivery_message, delivery_rating_success, delivery_set, recompute_delivery_price, is_all_service, is_process_rma, merged, name, parent_saleorder_id, order_revised_count, so_number, margin, margin_percent, mrp_production_count, note, report_grids, grid_product_tmpl_id, grid_update, grid, tasks_ids, tasks_count, visible_project, project_ids, sh_sale_barcode_mobile, sh_sale_bm_is_cont_scan, partner_credit_conform, sh_purchase_count, sh_so_po_is_show_so_to_po_btn_flag, apply_manual_currency_exchange, manual_currency_exchange_rate, company_currency_id, active_manual_currency_rate, warning_stock, opportunity_id, report_template_id1, report_template_id, amount_to_text, timesheet_ids, timesheet_count, project_id, timesheet_encode_uom_id, timesheet_total_duration, rfm_segment_id, amount_delivery, order_credit_points, order_redeem_points, redeem_value, is_from_website, loyalty_point_credit, order_source, driver_id, order_driver_message_ids, payment_status_with_driver, latitude, longitude, distance_btn_2_loc, sale_order_comm_ids, commission_calc, commission_pay_on, stage_id, order_line_count, date_order, validity_date, payment_term_id, sale_order_template_id, sale_state, delivered_state, sale_state_1, state_2, revised_state, approval_matrix_state, approval_matrix_state_1, branch_id, account_tag, account_tag_ids, analytic_account_id, approving_matrix_sale_id, approved_matrix_ids, is_customer_approval_matrix, hide_proforma, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, is_quotation_cancel, company_id, deduction_ids, analytic_accounting, terms_conditions_id, group_multi_do, is_single_warehouse, is_single_delivery_date, commitment_date, revised_sale_order_ids, revised_sale_order_id, is_revision_so, is_print_report, qty_delivered, count_delivered, multilevel_disc, multi_discount, discount_method, discount_amount, date_confirm, is_sale_order, partner_name, is_hidden_button, lock_sale_order, readonly_disc, readonly_multi, brand, partner_invoice_id, partner_shipping_id, reject_reason, sale_fully_delivered, sale_partially_delivery, sale_fully_paid, sale_partially_paid, sale_hidden_compute_field, date_kanban, is_down_payment, down_payment_amount, total_amount_without_dp, carrier_id, amount_untaxed, amount_tax, amount_total, order_line, discount_type, city_id, state_id, show_mobile, is_external_link, tax_discount_policy, discount_amt_before, discount_amt_line_before, amount_subtotal, warehouse_id, warehouse_new_id, delivery_state, payment_status_driver, approving_matrix_limit_id, approved_matrix_limit_ids, is_over_limit_validation, is_limit_matrix_filled, is_direct_confirm, limit_approval_matrix_line_id, is_approve_button_limit, limit_matrix_state, limit_matrix_state_1, limit_matrix_state_2, sale_limit_state, sale_limit_state_1, sale_limit_state_2, sale_limit_state_3, sale_limit_state_4, sale_limit_state_5, approval_matrix_state_2, approval_matrix_state_3, approval_matrix_state_4, approval_matrix_state_5, approval_matrix_state_6, approval_matrix_state_7, approval_matrix_state_8, approval_matrix_state_9, creditlim, hide_button_revise, lock_order_line, have_available_customer_voucher, customer_voucher_used_ids, cashback_line_ids, show_cashback, cn_cashback_ids, cn_cashback_count, title, partner_id, book_order, ean13, pos_config_id, pos_location_id, delivery_date, delivered_date, delivery_address, delivery_phone, payment_partial_amount, payment_partial_method_id, insert, state, pos_branch_id, pos_order_id, is_self_pickup, is_dropship, purchase_request_ids, purchase_request_count, remark, 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, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.order", "table_name": ""}
+{"text": "How to query ir.rule data?", "response": "To use the ir.rule model, you need to provide values for required fields: model_id. Readonly fields: global, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.rule", "table_name": ""}
+{"text": "Describe the purchase.order.history model in Odoo.", "response": "The purchase.order.history model represents Purchase Order History in the ERP system. It contains 18 fields and is used to manage purchase order history data. Key fields include: purchase_reorder, name, order_id, po_id, product_id, price_unit, product_qty, product_uom, currency_id, price_subtotal, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order.history", "table_name": ""}
+{"text": "Show me the relational structure of bus.presence.", "response": "The bus.presence model has 1 relational fields: user_id -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "bus.presence", "table_name": ""}
+{"text": "What methods are available in list.order?", "response": "The list.order model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "list.order", "table_name": ""}
+{"text": "What is the ks.sales.forecast.report model?", "response": "The ks.sales.forecast.report model represents Sale Forecast Report in the ERP system. It contains 14 fields and is used to manage sale forecast report data. Key fields include: type, name, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks.sales.forecast.report", "table_name": ""}
+{"text": "What are the available fields for product.cancel?", "response": "The product.cancel model has 19 fields: order_ref, product_id, qty, uom_id, src_location_id, cashier_id, cancel_reason, pos_order_id, cancel_date, company_id, branch_id, last_supplier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 10, float: 1, text: 1, date: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.cancel", "table_name": ""}
+{"text": "What are common use cases for ir.module.module.dependency?", "response": "To use the ir.module.module.dependency model, you need to provide values for required fields: none. Readonly fields: depend_id, state, installed_version, latest_version, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.module.module.dependency", "table_name": ""}
+{"text": "How to create records in account.move.template.line?", "response": "To use the account.move.template.line model, you need to provide values for required fields: move_id, currency_id. Readonly fields: move_id, move_name, date, parent_state, journal_id, company_id, company_currency_id, tax_fiscal_country_id, account_internal_type, account_internal_group, account_root_id, balance, cumulated_balance, price_subtotal, price_total, reconciled, product_uom_category_id, reconcile_model_id, payment_id, statement_line_id, statement_id, tax_line_id, tax_group_id, tax_base_amount, tax_exigible, tax_repartition_line_id, tax_audit, amount_residual, amount_residual_currency, full_reconcile_id, matching_number, recompute_tax_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.move.template.line", "table_name": ""}
+{"text": "Show me the fields of account.tax.map.sales.line.", "response": "The account.tax.map.sales.line model has 17 fields: company_id, sales_tax_id, target_company, target_sales_tax, map_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, line_ids, child_company_id, ownership, sales_line_ids, purchase_line_ids. Field types distribution: many2one: 8, integer: 1, char: 1, datetime: 3, one2many: 3, float: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.tax.map.sales.line", "table_name": ""}
+{"text": "Can you explain the purpose of hr.employee.category?", "response": "The hr.employee.category model represents Employee Category in the ERP system. It contains 10 fields and is used to manage employee category data. Key fields include: name, color, employee_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "hr.employee.category", "table_name": ""}
+{"text": "Tell me about the pos.gift.card.recharge model.", "response": "The pos.gift.card.recharge model represents Used to Store Gift Card Recharge History. in the ERP system. It contains 12 fields and is used to manage used to store gift card recharge history. data. Key fields include: card_id, customer_id, recharge_date, user_id, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.gift.card.recharge", "table_name": ""}
+{"text": "Which fields in coupon.generate.wizard are computed?", "response": "The coupon.generate.wizard model is defined in module: coupon. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "coupon.generate.wizard", "table_name": ""}
+{"text": "How to query report_excel_import_wizard data?", "response": "To use the report_excel_import_wizard model, you need to provide values for required fields: data. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report_excel_import_wizard", "table_name": ""}
+{"text": "How do I use the purchase.change.request model?", "response": "To use the purchase.change.request model, you need to provide values for required fields: state. Readonly fields: name, company_id, state, state1, state2, approval_matrix, is_allowed_to_approval_matrix, approval_matrix_line_id, is_approve_button, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.change.request", "table_name": ""}
+{"text": "Describe the show.material.done.popup model in Odoo.", "response": "The show.material.done.popup model represents show.material.done.popup in the ERP system. It contains 7 fields and is used to manage show.material.done.popup data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "show.material.done.popup", "table_name": ""}
+{"text": "What are the available fields for res.mail.activity?", "response": "The res.mail.activity model has 15 fields: name, activity_type_id, summary, date_deadline, calendar_event_id, res_id, act_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 6, date: 1, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.mail.activity", "table_name": ""}
+{"text": "What foreign keys exist in purchase.product.template.line?", "response": "The purchase.product.template.line model has 6 relational fields: name -> product.product; product_uom -> uom.uom; purchase_template_id -> purchase.product.template; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.product.template.line", "table_name": ""}
+{"text": "Can you explain the purpose of target.activity.line.res?", "response": "The target.activity.line.res model represents target.activity.line.res in the ERP system. It contains 13 fields and is used to manage target.activity.line.res data. Key fields include: activity_id, user_id, activity_type, activity_done, target_activity, date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "target.activity.line.res", "table_name": ""}
+{"text": "Describe the pos.cashbox.history model in Odoo.", "response": "The pos.cashbox.history model represents Pos Cashbox History in the ERP system. It contains 14 fields and is used to manage pos cashbox history data. Key fields include: start_balance, closing_balance, opened_by_user_id, pos_session_id, pos_config_id, start_date, closing_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.cashbox.history", "table_name": ""}
+{"text": "How does sh.mrp.pics relate to other models?", "response": "The sh.mrp.pics model has 7 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; mrp_id -> mrp.production; workorder_id -> mrp.workorder; attachment_ids -> ir.attachment; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.mrp.pics", "table_name": ""}
+{"text": "What models are connected to website.sale.extra.field?", "response": "The website.sale.extra.field model has 4 relational fields: website_id -> website; field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.sale.extra.field", "table_name": ""}
+{"text": "Describe the implementation of kpi.measure.item.", "response": "The kpi.measure.item model is defined in module: kpi_scorecard. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kpi.measure.item", "table_name": ""}
+{"text": "What does the forecast.quantity model represent?", "response": "The forecast.quantity model represents Forecast Quantity in the ERP system. It contains 11 fields and is used to manage forecast quantity data. Key fields include: schedule_date, reference, product_id, source_location, destination_location, forecast_qty, product_uom, state, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "forecast.quantity", "table_name": ""}
+{"text": "How does kitchen.safety.stock.line relate to other models?", "response": "The kitchen.safety.stock.line model has 4 relational fields: stock_id -> kitchen.safety.stock; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kitchen.safety.stock.line", "table_name": ""}
+{"text": "How to query picking.order.line data?", "response": "To use the picking.order.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "picking.order.line", "table_name": ""}
+{"text": "What modules define base_import.import?", "response": "The base_import.import model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.import", "table_name": ""}
+{"text": "What are the technical details of res.config.settings?", "response": "The res.config.settings model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.config.settings", "table_name": ""}
+{"text": "Show me the fields of lost.product.", "response": "The lost.product model has 9 fields: name, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "lost.product", "table_name": ""}
+{"text": "What are common use cases for pos.payment.wizard?", "response": "To use the pos.payment.wizard model, you need to provide values for required fields: start_dt, end_dt. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.payment.wizard", "table_name": ""}
+{"text": "What data can be stored in product.warehouse.cost?", "response": "The product.warehouse.cost model has 10 fields: product_id, product_cost_line_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.warehouse.cost", "table_name": ""}
+{"text": "List all fields in the change.password.wizard model.", "response": "The change.password.wizard model has 8 fields: user_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "change.password.wizard", "table_name": ""}
+{"text": "Describe the report.sh_sale_reports.sh_sale_details_report_doc model in Odoo.", "response": "The report.sh_sale_reports.sh_sale_details_report_doc model represents sale details abstract model in the ERP system. It contains 3 fields and is used to manage sale details abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_sale_reports.sh_sale_details_report_doc", "table_name": ""}
+{"text": "What models are connected to setu.inventory.age.breakdown.report?", "response": "The setu.inventory.age.breakdown.report model has 5 relational fields: company_ids -> res.company; product_category_ids -> product.category; product_ids -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids, product_category_ids, product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.age.breakdown.report", "table_name": ""}
+{"text": "Can you explain the purpose of account.move.line?", "response": "The account.move.line model represents Journal Item in the ERP system. It contains 140 fields and is used to manage journal item data. Key fields include: asset_category_id, asset_start_date, asset_end_date, asset_mrr, purchase_line_id, purchase_order_id, period_id, fiscal_year, is_anglo_saxon_line, product_type, is_landed_costs_line, discount_method, discount_type, discount_amount, discount_amt, branch_id, repair_line_ids, repair_fee_ids, is_down_payment, move_id, move_name, date, ref, parent_state, journal_id, company_id, company_currency_id, tax_fiscal_country_id, account_id, account_internal_type, account_internal_group, account_root_id, sequence, name, quantity, price_unit, discount, debit, credit, balance, cumulated_balance, amount_currency, price_subtotal, price_total, reconciled, blocked, date_maturity, currency_id, partner_id, product_uom_id, product_id, product_uom_category_id, reconcile_model_id, payment_id, statement_line_id, statement_id, tax_ids, tax_line_id, tax_group_id, tax_base_amount, tax_exigible, tax_repartition_line_id, tax_tag_ids, tax_audit, amount_residual, amount_residual_currency, full_reconcile_id, matched_debit_ids, matched_credit_ids, matching_number, analytic_line_ids, analytic_account_id, analytic_tag_ids, recompute_tax_line, display_type, is_rounding_line, exclude_from_invoice_tab, is_fiscal_book_exclude, price_tax_discount, is_update_disc_line, price_tax, unit_price_fnct, disc_percentage_rel, date_id, is_discount_line, is_interest_line, is_analytic_tags, total_qty_price_unit, multi_discount, is_intercompany_transaction, customer_deposit_id, vendor_deposit_id, tax_ids_ppn, price_total_ppn, amount_ppn, taxes_ppn, sale_line_ids, is_down_payment_discount, res_dp_amount, is_purchase_order, is_sales_order, sequence2, pos_branch_id, approval_code, check_reconcile, check_reconcile_done, check_reconcile_flag, check_payment, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.move.line", "table_name": ""}
+{"text": "Show me the fields of pos.order.line.promotion.", "response": "The pos.order.line.promotion model has 15 fields: sequence, pos_order_line_id, promotion_id, promotion_disc, price, amount_percentage, amount, discount_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 4, float: 4, char: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.order.line.promotion", "table_name": ""}
+{"text": "How to create records in account.deposit.return?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.deposit.return", "table_name": ""}
+{"text": "What fields does vendor.payment.request.line have?", "response": "The vendor.payment.request.line model has 16 fields: payment_request_id, sequence, description, amount_total, currency_id, payable_amount, attachment_file, file_name, purchase_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, integer: 2, char: 3, monetary: 1, float: 1, binary: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "vendor.payment.request.line", "table_name": ""}
+{"text": "What are the relationships in mr.internal_transfer_line?", "response": "The mr.internal_transfer_line model has 12 relational fields: mr_id -> material.request; product_id -> product.product; uom_id -> uom.uom; source_location -> stock.location; source_warehouse_id -> stock.warehouse; mr_ir_wizard -> mr.internal_transfer; mr_line_id -> material.request.line; filter_warehouse_ids -> stock.warehouse; filter_location_ids -> stock.location; dest_warehouse_id -> stock.warehouse; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_warehouse_ids, filter_location_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mr.internal_transfer_line", "table_name": ""}
+{"text": "Tell me about the kpi.period model.", "response": "The kpi.period model represents KPI Period in the ERP system. It contains 20 fields and is used to manage kpi period data. Key fields include: name, date_start, date_end, line_ids, period_length, period_passed, parent_id, state, template_id, company_id, last_recalculation_date, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kpi.period", "table_name": ""}
+{"text": "What operations can I perform on report.excel.fields.sql?", "response": "To use the report.excel.fields.sql model, you need to provide values for required fields: cell, column_index. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.excel.fields.sql", "table_name": ""}
+{"text": "How is account.bank.statement.cashbox used in the system?", "response": "The account.bank.statement.cashbox model represents Account Bank Statement Cashbox Details in the ERP system. It contains 19 fields and is used to manage account bank statement cashbox details data. Key fields include: cashbox_lines_ids, start_bank_stmt_ids, end_bank_stmt_ids, total, currency_id, pos_config_ids, is_a_template, description, bnk_cash_control, is_closing_line, pos_session_id, bank_cashbox_lines_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.bank.statement.cashbox", "table_name": ""}
+{"text": "What are the technical details of ir.qweb.field.contact?", "response": "The ir.qweb.field.contact model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.qweb.field.contact", "table_name": ""}
+{"text": "How to create records in partial.quantity.done?", "response": "To use the partial.quantity.done 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "partial.quantity.done", "table_name": ""}
+{"text": "Describe the many2many relations for gamification.karma.rank.", "response": "The gamification.karma.rank model has 3 relational fields: user_ids -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "gamification.karma.rank", "table_name": ""}
+{"text": "What are the technical details of target.activity.line?", "response": "The target.activity.line model is defined in module: equip3_crm_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "target.activity.line", "table_name": ""}
+{"text": "What does the assign.pr.line.wizard model represent?", "response": "The assign.pr.line.wizard model represents Assign PR Line Wizard in the ERP system. It contains 13 fields and is used to manage assign pr line wizard data. Key fields include: wizard_id, pr_line_id, name, user_id, new_user_id, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assign.pr.line.wizard", "table_name": ""}
+{"text": "Tell me about the ir.model.relation model.", "response": "The ir.model.relation model represents Relation Model in the ERP system. It contains 10 fields and is used to manage relation model data. Key fields include: name, model, module, write_date, create_date, id, display_name, create_uid, write_uid, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.model.relation", "table_name": ""}
+{"text": "How do I use the receivable.flow.wizard model?", "response": "To use the receivable.flow.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "receivable.flow.wizard", "table_name": ""}
+{"text": "What modules define setu.inventory.fsn.analysis.bi.report?", "response": "The setu.inventory.fsn.analysis.bi.report model is defined in module: setu_advance_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "setu.inventory.fsn.analysis.bi.report", "table_name": ""}
+{"text": "How do I use the report.account.report_invoice_with_payments model?", "response": "To use the report.account.report_invoice_with_payments model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.account.report_invoice_with_payments", "table_name": ""}
+{"text": "Describe the implementation of mr.internal_transfer.", "response": "The mr.internal_transfer model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mr.internal_transfer", "table_name": ""}
+{"text": "How is ks_dashboard_ninja.item_action implemented technically?", "response": "The ks_dashboard_ninja.item_action model is defined in module: ks_dashboard_ninja. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks_dashboard_ninja.item_action", "table_name": ""}
+{"text": "How do I use the bve.view.line model?", "response": "To use the bve.view.line model, you need to provide values for required fields: table_alias. Readonly fields: name, model_name, field_name, view_field_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "bve.view.line", "table_name": ""}
+{"text": "How does nsfp.registration relate to other models?", "response": "The nsfp.registration model has 4 relational fields: fiscal_year -> sh.fiscal.year; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "nsfp.registration", "table_name": ""}
+{"text": "Show me the fields of base_import.tests.models.o2m.child.", "response": "The base_import.tests.models.o2m.child model has 9 fields: parent_id, value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.o2m.child", "table_name": ""}
+{"text": "What data can be stored in account.group?", "response": "The account.group model has 13 fields: parent_id, parent_path, code_prefix_start, code_prefix_end, company_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 5, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.group", "table_name": ""}
+{"text": "What data can be stored in account.common.account.report?", "response": "The account.common.account.report model has 14 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 types distribution: selection: 2, many2many: 1, date: 2, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.common.account.report", "table_name": ""}
+{"text": "What are the relationships in report.equip3_inventory_masterdata.report_product_forecast?", "response": "The report.equip3_inventory_masterdata.report_product_forecast model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_inventory_masterdata.report_product_forecast", "table_name": ""}
+{"text": "Describe the sale.order.partner.credit model in Odoo.", "response": "The sale.order.partner.credit model represents Sale Order Partner Credit in the ERP system. It contains 21 fields and is used to manage sale order partner credit data. Key fields include: name, order_partner, customer_credit_limit, set_customer_onhold, total_receivable, current_order, sale_orders_cnt_amt, cust_invoice_cnt_amt, sale_id, invoice_number, customer_max_invoice_overdue, is_set_customer_on_hold, avl_open_inv_limt, customer_on_hold_open_invoice, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.order.partner.credit", "table_name": ""}
+{"text": "What modules define limit.approval.matrix?", "response": "The limit.approval.matrix model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "limit.approval.matrix", "table_name": ""}
+{"text": "What fields does pos.combo.item have?", "response": "The pos.combo.item model has 15 fields: required, product_id, product_combo_id, quantity, price_extra, default, tracking, uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 3, many2one: 5, float: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.combo.item", "table_name": ""}
+{"text": "Show me the relational structure of repair.line.", "response": "The repair.line model has 14 relational fields: repair_id -> repair.order; company_id -> res.company; currency_id -> res.currency; product_id -> product.product; tax_id -> account.tax; product_uom -> uom.uom; product_uom_category_id -> uom.category; invoice_line_id -> account.move.line; location_id -> stock.location; location_dest_id -> stock.location; move_id -> stock.move; lot_id -> stock.production.lot; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "repair.line", "table_name": ""}
+{"text": "What are the available fields for mail.message?", "response": "The mail.message model has 49 fields: subject, date, body, description, attachment_ids, parent_id, child_ids, model, res_id, record_name, subtype_id, mail_activity_type_id, is_internal, email_from, author_id, author_avatar, partner_ids, notified_partner_ids, needaction, has_error, channel_ids, notification_ids, starred_partner_ids, starred, tracking_value_ids, no_auto_thread, message_id, reply_to, mail_server_id, moderation_status, moderator_id, need_moderation, email_layout_xmlid, add_sign, mail_ids, canned_response_ids, rating_ids, rating_value, has_sms_error, snailmail_error, letter_ids, message_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 9, datetime: 4, html: 1, many2many: 5, many2one: 8, one2many: 7, many2one_reference: 1, boolean: 9, binary: 1, selection: 2, float: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.message", "table_name": ""}
+{"text": "What are common use cases for website?", "response": "To use the website model, you need to provide values for required fields: name, company_id, default_lang_id, user_id. Readonly fields: has_social_default_image, menu_id, pricelist_id, pricelist_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "website", "table_name": ""}
+{"text": "How is approval.matrix.purchase.request implemented technically?", "response": "The approval.matrix.purchase.request model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "approval.matrix.purchase.request", "table_name": ""}
+{"text": "What foreign keys exist in receipt.voucher?", "response": "The receipt.voucher model has 22 relational fields: create_by -> res.users; payment_ids -> account.payment; partner_id -> res.partner; partner_ids -> res.partner; bank_id -> account.journal; customer_invoice_ids -> account.move; currency_id -> res.currency; company_id -> res.company; branch_id -> res.branch; receipt_voucher_line_ids -> receipt.voucher.line; customer_allowed_ids -> account.move; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, customer_invoice_ids, customer_allowed_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "receipt.voucher", "table_name": ""}
+{"text": "List all fields in the reject.picking.order model.", "response": "The reject.picking.order model has 12 fields: driver_id, picking_id, assign_date, reject_date, reject_reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, datetime: 5, text: 1, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "reject.picking.order", "table_name": ""}
+{"text": "What operations can I perform on budget.budget.budget.line?", "response": "To use the budget.budget.budget.line model, you need to provide values for required fields: budget_budget_id, date_from, date_to, planned_amount. Readonly fields: name, analytic_group_id, currency_id, practical_amount, theoritical_amount, percentage, company_id, is_above_budget, budget_budget_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "budget.budget.budget.line", "table_name": ""}
+{"text": "How to query all.loyalty.setting data?", "response": "To use the all.loyalty.setting model, you need to provide values for required fields: product_id, issue_date, expiry_date, loyalty_basis_on, company_id. Readonly fields: amount_footer, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "all.loyalty.setting", "table_name": ""}
+{"text": "What are the technical details of sh.top.vendor.excel.extended?", "response": "The sh.top.vendor.excel.extended model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.top.vendor.excel.extended", "table_name": ""}
+{"text": "What fields does product.brand have?", "response": "The product.brand model has 42 fields: brand_name, short_name, product_count, active, 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. Field types distribution: char: 8, integer: 6, boolean: 6, many2one: 8, one2many: 4, selection: 2, date: 2, many2many: 2, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.brand", "table_name": ""}
+{"text": "What are the available fields for mrp.bom.tools?", "response": "The mrp.bom.tools model has 17 fields: bom_id, company_id, workorder_id, product_id, quantity, uom_id, operation_id, allowed_operation_ids, operation_two_ids, operation_two_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, float: 1, many2many: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.bom.tools", "table_name": ""}
+{"text": "What fields does report.sh_purchase_reports.rpt_purchase_order_day_wise have?", "response": "The report.sh_purchase_reports.rpt_purchase_order_day_wise model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.rpt_purchase_order_day_wise", "table_name": ""}
+{"text": "What data can be stored in sh.qc.alert.tags?", "response": "The sh.qc.alert.tags model has 10 fields: name, color, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 3, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.qc.alert.tags", "table_name": ""}
+{"text": "How does stock.picking.batch.validate.line relate to other models?", "response": "The stock.picking.batch.validate.line model has 6 relational fields: line_id -> stock.picking.batch.validate; product_id -> product.product; transfer_id -> stock.picking; location_id -> stock.location; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.picking.batch.validate.line", "table_name": ""}
+{"text": "Which fields in do.matrix.reject are computed?", "response": "The do.matrix.reject model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "do.matrix.reject", "table_name": ""}
+{"text": "What methods are available in product.quantity.available.report?", "response": "The product.quantity.available.report model is defined in module: equip3_pos_general. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.quantity.available.report", "table_name": ""}
+{"text": "What fields does res.users.qiscuss have?", "response": "The res.users.qiscuss model has 10 fields: user_id, email, password, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.users.qiscuss", "table_name": ""}
+{"text": "How to query budget.budget data?", "response": "To use the budget.budget model, you need to provide values for required fields: name, date_from, date_to, state, company_id. Readonly fields: complete_name, state, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "budget.budget", "table_name": ""}
+{"text": "What are the available fields for auditlog.log?", "response": "The auditlog.log model has 18 fields: name, model_id, model_name, model_model, res_id, user_id, method, line_ids, http_session_id, http_request_id, log_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 6, integer: 2, one2many: 1, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "auditlog.log", "table_name": ""}
+{"text": "How does account.print.journal relate to other models?", "response": "The account.print.journal 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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.print.journal", "table_name": ""}
+{"text": "What are the technical details of forecast.quantity?", "response": "The forecast.quantity model is defined in module: equip3_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "forecast.quantity", "table_name": ""}
+{"text": "How to create records in finish.good.rework?", "response": "To use the finish.good.rework model, you need to provide values for required fields: product_tmpl_ids, product_ids, company_id, product_qty, rejected_qty, product_uom_id, state, location_src_id, location_dest_id, picking_type_id, date_planned_start, warehouse_id. Readonly fields: product_tmpl_ids, product_ids, name, company_id, is_branch_required, product_qty, rejected_qty, product_uom_id, product_uom_category_id, bom_id, branch_id, state, location_src_id, location_dest_id, picking_type_id, date_planned_start, date_planned_finished, date_deadline, procurement_group_id, production_location_id, warehouse_id, product_tracking, account_move_ids, purchase_request_ids, internal_transfer_count, product_use_expiration_date, show_submit_button, is_autogenerate, default_finished_lot_qty, default_rejected_lot_qty, show_byproduct_lot_tab, byproduct_manual_product_ids, default_byproduct_lot_qty, default_next_byproduct_product_id, any_byproduct_is_autogenerate, all_byproduct_is_autogenerate, total_bom_cost, total_bom_sub_total, total_bom_quantity, total_product_cost, total_product_sub_total, total_product_quantity, total_overall, total_overall_sub_total, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "finish.good.rework", "table_name": ""}
+{"text": "How is base.partner.merge.automatic.wizard used in the system?", "response": "The base.partner.merge.automatic.wizard model represents Merge Partner Wizard in the ERP system. It contains 21 fields and is used to manage merge partner wizard data. Key fields include: group_by_email, group_by_name, group_by_is_company, group_by_vat, group_by_parent_id, state, number_group, current_line_id, line_ids, partner_ids, dst_partner_id, exclude_contact, exclude_journal_item, maximum_group, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.partner.merge.automatic.wizard", "table_name": ""}
+{"text": "What does the payable.opening.balance model represent?", "response": "The payable.opening.balance model represents payable.opening.balance in the ERP system. It contains 14 fields and is used to manage payable.opening.balance data. Key fields include: partner_opening_bal_id, vendor_id, invoice, date, description, due_date, amount_due, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "payable.opening.balance", "table_name": ""}
+{"text": "How do I use the ks_dashboard_ninja.board_template model?", "response": "To use the ks_dashboard_ninja.board_template 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_dashboard_ninja.board_template", "table_name": ""}
+{"text": "Can you explain the purpose of report.accounting_pdf_reports.report_agedpartnerbalance?", "response": "The report.accounting_pdf_reports.report_agedpartnerbalance model represents Aged Partner Balance Report in the ERP system. It contains 3 fields and is used to manage aged partner balance report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.accounting_pdf_reports.report_agedpartnerbalance", "table_name": ""}
+{"text": "Which fields in force.done.memory are computed?", "response": "The force.done.memory model is defined in module: equip3_sale_other_operation_cont. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "force.done.memory", "table_name": ""}
+{"text": "Show me the fields of product.packaging.", "response": "The product.packaging model has 33 fields: name, sequence, qty, barcode, product_uom_id, company_id, height, width, packaging_length, max_weight, shipper_package_code, package_carrier_type, weight_uom_name, length_uom_name, product_id, maximum_height, maximum_length, maximum_width, maximum_volume, packages_barcode_prefix, digits, current_sequence, filter_value_ids, measure_ids, volume_calculation, volume_formula, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 9, integer: 6, float: 6, many2one: 4, selection: 1, many2many: 3, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.packaging", "table_name": ""}
+{"text": "Describe the many2many relations for quotation.amount.", "response": "The quotation.amount model has 4 relational fields: order_id -> sale.order; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "quotation.amount", "table_name": ""}
+{"text": "What is the stock.picking.batch.line model?", "response": "The stock.picking.batch.line model represents stock.picking.batch.line in the ERP system. It contains 18 fields and is used to manage stock.picking.batch.line data. Key fields include: sequence, transfer_id, product_id, name, location_id, demand_qty, reserved_qty, done_qty, uom_id, picking_batch_id, origin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.picking.batch.line", "table_name": ""}
+{"text": "Describe the many2many relations for asset.modify.", "response": "The asset.modify model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "asset.modify", "table_name": ""}
+{"text": "How to create records in rma.report?", "response": "To use the rma.report model, you need to provide values for required fields: none. Readonly fields: name, date, deadline_date, user_id, team_id, partner_id, company_id, state, product_id, product_tmpl_id, categ_id, replace_product_id, replace_qty, country_id, commercial_partner_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "rma.report", "table_name": ""}
+{"text": "What models are connected to asset.asset.revalue?", "response": "The asset.asset.revalue model has 8 relational fields: asset_id -> account.asset.asset; journal_id -> account.journal; user_id -> res.users; company_id -> res.company; company_currency_id -> res.currency; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "asset.asset.revalue", "table_name": ""}
+{"text": "What methods are available in gamification.badge.user?", "response": "The gamification.badge.user model is defined in module: gamification. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "gamification.badge.user", "table_name": ""}
+{"text": "What foreign keys exist in sale.payment.acquirer.onboarding.wizard?", "response": "The sale.payment.acquirer.onboarding.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "How do I use the mail.activity model?", "response": "To use the mail.activity model, you need to provide values for required fields: res_model_id, res_id, date_deadline, user_id. Readonly fields: res_model, res_name, activity_category, activity_decoration, icon, automated, state, previous_activity_type_id, has_recommended_activities, mail_template_ids, force_next, can_write, is_attachment_required, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.activity", "table_name": ""}
+{"text": "What methods are available in initial.balance.line?", "response": "The initial.balance.line model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "initial.balance.line", "table_name": ""}
+{"text": "Describe the field structure of sh.mrp.qc.alert.line.", "response": "The sh.mrp.qc.alert.line model has 10 fields: alert_id, product_id, partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.mrp.qc.alert.line", "table_name": ""}
+{"text": "What business logic is in hr.employee.public?", "response": "To use the hr.employee.public model, you need to provide values for required fields: none. Readonly fields: create_date, name, active, department_id, job_id, job_title, company_id, address_id, mobile_phone, work_phone, work_email, work_location, user_id, resource_id, resource_calendar_id, tz, color, child_ids, image_1920, image_1024, image_512, image_256, image_128, parent_id, coach_id, user_partner_id, subordinate_ids, hr_presence_state, last_activity, last_activity_time, hr_icon_display, goal_ids, badge_ids, has_badges, direct_badge_ids, child_all_count, id, display_name, create_uid, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "hr.employee.public", "table_name": ""}
+{"text": "Show me the fields of account.partner.ledger.", "response": "The account.partner.ledger model has 21 fields: journal_ids, account_ids, display_account, partner_ids, partner_category_ids, reconciled, account_type_ids, show_all_transaction, expand, 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 types distribution: many2many: 5, selection: 4, boolean: 1, date: 2, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.partner.ledger", "table_name": ""}
+{"text": "What business logic is in coupon.rule?", "response": "To use the coupon.rule model, you need to provide values for required fields: none. Readonly fields: applied_partner_ids, applied_product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "coupon.rule", "table_name": ""}
+{"text": "What are the relationships in base_import.mapping?", "response": "The base_import.mapping model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.mapping", "table_name": ""}
+{"text": "Describe the implementation of payment.voucher.matrix.reject.", "response": "The payment.voucher.matrix.reject model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "payment.voucher.matrix.reject", "table_name": ""}
+{"text": "Describe the many2many relations for material.request.", "response": "The material.request model has 21 relational fields: create_uid -> res.users; requested_by -> res.users; destination_location_id -> stock.location; destination_warehouse_id -> stock.warehouse; company_id -> res.company; branch_id -> res.branch; product_line -> material.request.line; mr_approval_matrix_id -> mr.approval.matrix; approved_matrix_ids -> mr.approval.matrix.line; approval_matrix_line_id -> mr.approval.matrix.line; analytic_account_group_ids -> account.analytic.tag; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; write_uid -> res.users. Many2many fields: analytic_account_group_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "material.request", "table_name": ""}
+{"text": "What foreign keys exist in purchase.order.partner.credit?", "response": "The purchase.order.partner.credit model has 4 relational fields: name -> purchase.order; order_partner -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.order.partner.credit", "table_name": ""}
+{"text": "Show me the relational structure of purchase.request.warning.", "response": "The purchase.request.warning model has 3 relational fields: warning_line_ids -> purchase.request.warning.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.request.warning", "table_name": ""}
+{"text": "Can you explain the purpose of asp.asm.stock?", "response": "The asp.asm.stock model represents Adjustment Stock in the ERP system. It contains 46 fields and is used to manage adjustment stock data. Key fields include: name, inv_ref, state, warehouse_id, company_id, user_id, analytic_tag_ids, line_ids, move_ids, branch_id, adjustmentt_type, remark, domain_warehouse_id, product_ids, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "asp.asm.stock", "table_name": ""}
+{"text": "Show me the relational structure of account.cash.rounding.", "response": "The account.cash.rounding model has 5 relational fields: profit_account_id -> account.account; loss_account_id -> account.account; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.cash.rounding", "table_name": ""}
+{"text": "List all fields in the mr_line.internal_transfer model.", "response": "The mr_line.internal_transfer model has 8 fields: ir_wizard_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mr_line.internal_transfer", "table_name": ""}
+{"text": "How do I use the pos.global.discount model?", "response": "To use the pos.global.discount model, you need to provide values for required fields: name, amount, product_id, reason, type. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.global.discount", "table_name": ""}
+{"text": "Show me the relational structure of mail.moderation.", "response": "The mail.moderation model has 3 relational fields: channel_id -> mail.channel; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.moderation", "table_name": ""}
+{"text": "What models are connected to link.tracker.click?", "response": "The link.tracker.click model has 7 relational fields: campaign_id -> utm.campaign; link_id -> link.tracker; country_id -> res.country; mailing_trace_id -> mailing.trace; mass_mailing_id -> mailing.mailing; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "link.tracker.click", "table_name": ""}
+{"text": "How to create records in base_import.tests.models.o2m?", "response": "To use the base_import.tests.models.o2m 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base_import.tests.models.o2m", "table_name": ""}
+{"text": "What are the relationships in ir.actions.client?", "response": "The ir.actions.client model has 3 relational fields: binding_model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.actions.client", "table_name": ""}
+{"text": "What foreign keys exist in website.mass_mailing.popup?", "response": "The website.mass_mailing.popup model has 4 relational fields: mailing_list_id -> mailing.list; website_id -> website; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.mass_mailing.popup", "table_name": ""}
+{"text": "Show me the relational structure of base.", "response": "The base model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base", "table_name": ""}
+{"text": "How to query ks_dashboard_ninja.board_template data?", "response": "To use the ks_dashboard_ninja.board_template 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_dashboard_ninja.board_template", "table_name": ""}
+{"text": "What business logic is in snailmail.letter.missing.required.fields?", "response": "To use the snailmail.letter.missing.required.fields 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "snailmail.letter.missing.required.fields", "table_name": ""}
+{"text": "Describe the pos.sale.analytic model in Odoo.", "response": "The pos.sale.analytic model represents Report sale analytic in the ERP system. It contains 15 fields and is used to manage report sale analytic data. Key fields include: name, user_id, date, product_id, product_categ_id, pos_categ_id, product_tmpl_id, company_id, origin, qty, sale_total, pos_branch_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.sale.analytic", "table_name": ""}
+{"text": "What business logic is in assign.pr.line.wizard?", "response": "To use the assign.pr.line.wizard model, you need to provide values for required fields: none. Readonly fields: name, user_id, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assign.pr.line.wizard", "table_name": ""}
+{"text": "How to create records in warranty.history?", "response": "To use the warranty.history 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "warranty.history", "table_name": ""}
+{"text": "Describe the field structure of sh.sale.analysis.xls.", "response": "The sh.sale.analysis.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.sale.analysis.xls", "table_name": ""}
+{"text": "How do I use the sh.send.notification model?", "response": "To use the sh.send.notification 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.send.notification", "table_name": ""}
+{"text": "What operations can I perform on sh.sale.category.wizard?", "response": "To use the sh.sale.category.wizard model, you need to provide values for required fields: sh_end_date, sh_start_date. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.sale.category.wizard", "table_name": ""}
+{"text": "What business logic is in theme.ir.attachment?", "response": "To use the theme.ir.attachment model, you need to provide values for required fields: name, key. Readonly fields: copy_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "theme.ir.attachment", "table_name": ""}
+{"text": "What are the available fields for auditlog.rule?", "response": "The auditlog.rule model has 20 fields: name, model_id, model_name, model_model, user_ids, log_read, log_write, log_unlink, log_create, log_type, state, action_id, capture_record, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 4, many2many: 1, boolean: 5, selection: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "auditlog.rule", "table_name": ""}
+{"text": "How does sh.purchase.details.report.wizard relate to other models?", "response": "The sh.purchase.details.report.wizard model has 4 relational fields: company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids, branch_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.details.report.wizard", "table_name": ""}
+{"text": "What does the wizard.scrap.order.report model represent?", "response": "The wizard.scrap.order.report model represents Wizard Scrap Order Report in the ERP system. It contains 13 fields and is used to manage wizard scrap order report data. Key fields include: company_id, start_date, end_date, state, name, data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "wizard.scrap.order.report", "table_name": ""}
+{"text": "What operations can I perform on res.currency.tax?", "response": "To use the res.currency.tax model, you need to provide values for required fields: name, currency_id. Readonly fields: rate, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.currency.tax", "table_name": ""}
+{"text": "How to create records in generate.closing.entries.confirmation.wizard?", "response": "To use the generate.closing.entries.confirmation.wizard model, you need to provide values for required fields: fiscal_year_id, closing_entry_date, journal_id, description, summary_account_id, retained_earnings_account_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "generate.closing.entries.confirmation.wizard", "table_name": ""}
+{"text": "What data can be stored in im_livechat.channel.rule?", "response": "The im_livechat.channel.rule model has 13 fields: regex_url, action, auto_popup_timer, channel_id, country_ids, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, selection: 1, integer: 3, many2one: 3, many2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "im_livechat.channel.rule", "table_name": ""}
+{"text": "How is invoice.templates implemented technically?", "response": "The invoice.templates model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.templates", "table_name": ""}
+{"text": "What are the technical details of product.template.attribute.line?", "response": "The product.template.attribute.line model is defined in module: product. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.template.attribute.line", "table_name": ""}
+{"text": "What fields does report.sh_sale_reports.sh_cus_sale_analysis_doc have?", "response": "The report.sh_sale_reports.sh_cus_sale_analysis_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_sale_reports.sh_cus_sale_analysis_doc", "table_name": ""}
+{"text": "Tell me about the base_import.tests.models.char.noreadonly model.", "response": "The base_import.tests.models.char.noreadonly model represents Tests : Base Import Model, Character No readonly in the ERP system. It contains 8 fields and is used to manage tests : base import model, character no readonly data. Key fields include: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.char.noreadonly", "table_name": ""}
+{"text": "What methods are available in stock.traceability.report?", "response": "The stock.traceability.report model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.traceability.report", "table_name": ""}
+{"text": "Tell me about the ms.query model.", "response": "The ms.query model represents Execute Query in the ERP system. It contains 25 fields and is used to manage execute query data. Key fields include: backup, name, result, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ms.query", "table_name": ""}
+{"text": "Show me the fields of report.sh_sale_reports.sh_cus_sale_analysis_doc.", "response": "The report.sh_sale_reports.sh_cus_sale_analysis_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_sale_reports.sh_cus_sale_analysis_doc", "table_name": ""}
+{"text": "Can you explain the purpose of order.driver.message?", "response": "The order.driver.message model represents order.driver.message in the ERP system. It contains 11 fields and is used to manage order.driver.message data. Key fields include: order_id, message, send_to_driver, partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "order.driver.message", "table_name": ""}
+{"text": "How do I use the sale.order.pricelist.wizard.line model?", "response": "To use the sale.order.pricelist.wizard.line model, you need to provide values for required fields: sh_pricelist_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.pricelist.wizard.line", "table_name": ""}
+{"text": "Show me the fields of sh.qc.alert.", "response": "The sh.qc.alert model has 11 fields: team_id, user_id, sh_priority, alert_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, selection: 1, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.qc.alert", "table_name": ""}
+{"text": "What does the res.config model represent?", "response": "The res.config model represents Config in the ERP system. It contains 7 fields and is used to manage config data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.config", "table_name": ""}
+{"text": "Which fields in list.top.product.compare are computed?", "response": "The list.top.product.compare model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "list.top.product.compare", "table_name": ""}
+{"text": "What are the technical details of mail.resend.cancel?", "response": "The mail.resend.cancel model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.resend.cancel", "table_name": ""}
+{"text": "What are the technical details of card.payment?", "response": "The card.payment model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "card.payment", "table_name": ""}
+{"text": "Describe the implementation of report.project.task.user.", "response": "The report.project.task.user model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.project.task.user", "table_name": ""}
+{"text": "Tell me about the vendor.pricelist.approval.matrix model.", "response": "The vendor.pricelist.approval.matrix model represents Vendor Pricelist Approval Matrix in the ERP system. It contains 14 fields and is used to manage vendor pricelist approval matrix data. Key fields include: name, company_id, branch_id, department_id, created_by, created_date, approval_matrix_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "vendor.pricelist.approval.matrix", "table_name": ""}
+{"text": "Show me the fields of approval.matrix.vendor.", "response": "The approval.matrix.vendor model has 11 fields: name, company_id, branch_id, approval_matrix_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.vendor", "table_name": ""}
+{"text": "Describe the many2many relations for pos.gift.card.recharge.", "response": "The pos.gift.card.recharge model has 5 relational fields: card_id -> pos.gift.card; customer_id -> res.partner; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.gift.card.recharge", "table_name": ""}
+{"text": "What is the link.tracker.code model?", "response": "The link.tracker.code model represents Link Tracker Code in the ERP system. It contains 9 fields and is used to manage link tracker code data. Key fields include: code, link_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "link.tracker.code", "table_name": ""}
+{"text": "How is account.pettycash.analysis used in the system?", "response": "The account.pettycash.analysis model represents Enterprise Petty Cash Analysis in the ERP system. It contains 22 fields and is used to manage enterprise petty cash analysis data. Key fields include: journal_ids, account_ids, display_account, branch_ids, top_expenses, date_from, date_to, titles, entities_comparison, period, years_prev, filter_period, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.pettycash.analysis", "table_name": ""}
+{"text": "Can you explain the purpose of blacklist.partner.wiz?", "response": "The blacklist.partner.wiz model represents Blacklist Partner Wizard in the ERP system. It contains 11 fields and is used to manage blacklist partner wizard data. Key fields include: partner_id, user_id, type, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "blacklist.partner.wiz", "table_name": ""}
+{"text": "What business logic is in fast.financial.report.query?", "response": "To use the fast.financial.report.query model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "fast.financial.report.query", "table_name": ""}
+{"text": "What are the technical details of ks_to.do.description?", "response": "The ks_to.do.description model is defined in module: ks_dashboard_ninja. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks_to.do.description", "table_name": ""}
+{"text": "Show me the relational structure of product.cross.", "response": "The product.cross model has 4 relational fields: product_tmpl_id -> product.template; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.cross", "table_name": ""}
+{"text": "What are common use cases for report.sh_purchase_reports.sh_payment_pr_report_doc?", "response": "To use the report.sh_purchase_reports.sh_payment_pr_report_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_payment_pr_report_doc", "table_name": ""}
+{"text": "What fields does vendor.pricelist.approval.matrix.line have?", "response": "The vendor.pricelist.approval.matrix.line model has 15 fields: sequence, approval_matrix, company_id, branch_id, user_ids, minimum_approver, sequence2, user_ids_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 4, many2one: 5, many2many: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "vendor.pricelist.approval.matrix.line", "table_name": ""}
+{"text": "How to query vendor.deposit.amount.wizard data?", "response": "To use the vendor.deposit.amount.wizard model, you need to provide values for required fields: none. Readonly fields: currency_id, final_amount, final_remaining_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "vendor.deposit.amount.wizard", "table_name": ""}
+{"text": "Describe the purchase.order.line.extract model in Odoo.", "response": "The purchase.order.line.extract model represents Purchase Order Line Extract in the ERP system. It contains 18 fields and is used to manage purchase order line extract data. Key fields include: sequence, tick, product_template_id, name, date_planned, product_qty, price_unit, destination_warehouse_id, extract_id, product_id, product_uom, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order.line.extract", "table_name": ""}
+{"text": "Show me the relational structure of stock.inventory.line.", "response": "The stock.inventory.line model has 21 relational fields: inventory_id -> stock.inventory; partner_id -> res.partner; product_id -> product.product; product_uom_id -> uom.uom; categ_id -> product.category; package_id -> stock.quant.package; prod_lot_id -> stock.production.lot; company_id -> res.company; location_id -> stock.location; adjustment_account_id -> account.account; filtered_adjustment_account_id -> account.account; analytic_tag_ids -> account.analytic.tag; uom_id -> uom.uom; category_uom_id -> uom.category; wizard_id -> stock.inventory.wizard; currency_id -> res.currency; user_id_1 -> res.users; user_id_2 -> res.users; current_user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: filtered_adjustment_account_id, analytic_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.inventory.line", "table_name": ""}
+{"text": "How is apply.voucher implemented technically?", "response": "The apply.voucher model is defined in module: equip3_sale_loyalty. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "apply.voucher", "table_name": ""}
+{"text": "What are common use cases for sh.stock.move.text?", "response": "To use the sh.stock.move.text model, you need to provide values for required fields: none. Readonly fields: product_id, sh_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.stock.move.text", "table_name": ""}
+{"text": "What fields does sh.top.purchasing.excel.extended have?", "response": "The sh.top.purchasing.excel.extended model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.top.purchasing.excel.extended", "table_name": ""}
+{"text": "What models are connected to resource.test?", "response": "The resource.test model has 5 relational fields: resource_id -> resource.resource; company_id -> res.company; resource_calendar_id -> resource.calendar; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "resource.test", "table_name": ""}
+{"text": "Describe the many2many relations for product.product.", "response": "The product.product model has 103 relational fields: product_tmpl_id -> product.template; product_template_attribute_value_ids -> product.template.attribute.value; barcode_line_ids -> product.template.barcode; stock_quant_ids -> stock.quant; stock_move_ids -> stock.move; orderpoint_ids -> stock.warehouse.orderpoint; putaway_rule_ids -> stock.putaway.rule; variant_bom_ids -> mrp.bom; bom_line_ids -> mrp.bom.line; stock_valuation_layer_ids -> stock.valuation.layer; product_cost_ids -> product.warehouse.cost; last_supplier_id -> res.partner; purchase_order_line_ids -> purchase.order.line; purchase_price_history_line_ids -> purchase.price.history; website_id -> website; product_variant_image_ids -> product.image; alternative_product_ids -> product.product; packaging_ids -> product.packaging; categ_id -> product.category; last_customer_id -> res.partner; product_lots_ids -> stock.production.lot; product_bom_id -> pos.product.bom; purchase_req_line_ids -> purchase.request.line; warehouse_price_ids -> product.warehouse.price; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users; currency_id -> res.currency; cost_currency_id -> res.currency; pricelist_id -> product.pricelist; uom_id -> uom.uom; uom_po_id -> uom.uom; seller_ids -> product.supplierinfo; variant_seller_ids -> product.supplierinfo; attribute_line_ids -> product.template.attribute.line; valid_product_template_attribute_line_ids -> product.template.attribute.line; product_variant_ids -> product.product; product_variant_id -> product.product; rating_ids -> rating.rating; taxes_id -> account.tax; property_account_income_id -> account.account; property_account_expense_id -> account.account; responsible_id -> res.users; property_stock_production -> stock.location; property_stock_inventory -> stock.location; location_id -> stock.location; warehouse_id -> stock.warehouse; route_from_categ_ids -> stock.location.route; bom_ids -> mrp.bom; deferred_revenue_category_id -> account.asset.category; email_template_id -> mail.template; property_account_creditor_price_difference -> account.account; pos_categ_id -> pos.category; route_ids -> stock.location.route; consignment_partner_id -> res.partner; optional_product_ids -> product.template; accessory_product_ids -> product.product; website_ribbon_id -> product.ribbon; public_categ_ids -> product.public.category; product_template_image_ids -> product.image; bi_pack_ids -> bi.product.pack; project_template_id -> project.project; multi_companies_all -> res.company; product_brand_id -> product.brand; project_id -> project.project; brand_attribute_id -> product.attribute; brand_ids -> product.brand; branch_id -> res.branch; secondary_uom_id -> uom.uom; multi_warehouses_all -> stock.warehouse; product_brand_ids -> product.brand; def_packaging_id -> product.packaging; group_stock_ids -> product.packaging; reordering_rules_ids -> stock.warehouse.orderpoint; variant_attribute_value_ids -> product.variant.attribute.value; product_ratio_line -> product.ratio.line; uom_categ_id -> uom.category; merchendise_id -> merchendise.code; asset_category_id -> account.asset.category; company_id -> res.company; sell_ids -> product.supplierinfo; template_purchase_price_history_line_ids -> purchase.price.history; combo_option_id -> combo.option; combo_option_items -> combo.option.item; pos_combo_item_ids -> pos.combo.item; pos_categ_ids -> pos.category; price_uom_ids -> product.uom.price; cross_ids -> product.cross; product_price_quantity_ids -> product.price.quantity; combo_limit_ids -> pos.combo.limit; uom_ids -> uom.uom; note_ids -> pos.note; tag_ids -> pos.tag; pos_branch_id -> res.branch; supplier_taxes_id -> account.tax. Many2many fields: product_template_attribute_value_ids, purchase_price_history_line_ids, alternative_product_ids, packaging_ids, message_partner_ids, message_channel_ids, valid_product_template_attribute_line_ids, taxes_id, route_from_categ_ids, route_ids, optional_product_ids, accessory_product_ids, public_categ_ids, multi_companies_all, brand_ids, multi_warehouses_all, product_brand_ids, group_stock_ids, template_purchase_price_history_line_ids, pos_categ_ids, uom_ids, note_ids, tag_ids, supplier_taxes_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.product", "table_name": ""}
+{"text": "What are the technical details of ir.qweb.field.date?", "response": "The ir.qweb.field.date model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.qweb.field.date", "table_name": ""}
+{"text": "What data can be stored in stock.scrap.approval.matrix.line?", "response": "The stock.scrap.approval.matrix.line model has 34 fields: sequence, user_ids, minimum_approver, sc_approval_matrix, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, scap_request_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 8, many2many: 4, many2one: 6, text: 1, datetime: 4, char: 2, boolean: 6, one2many: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.scrap.approval.matrix.line", "table_name": ""}
+{"text": "What fields does pos.loyalty.update.point have?", "response": "The pos.loyalty.update.point model has 19 fields: name, type_apply, state, member_id, pos_order_ids, is_orders, total_orders, current_point, reward_point, total_point, history_ids, is_editable_point, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, selection: 2, many2one: 3, many2many: 1, boolean: 2, float: 4, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.loyalty.update.point", "table_name": ""}
+{"text": "What operations can I perform on team.customer.segment?", "response": "To use the team.customer.segment model, you need to provide values for required fields: none. Readonly fields: total_orders, total_revenue, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "team.customer.segment", "table_name": ""}
+{"text": "Tell me about the kpi.measure.item model.", "response": "The kpi.measure.item model represents KPI Measurement (Variable) in the ERP system. It contains 20 fields and is used to manage kpi measurement (variable) data. Key fields include: name, measure_id, domain, model_id, model_name, measure_type, company_id, active, description, sequence, existing_kpi, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kpi.measure.item", "table_name": ""}
+{"text": "What is the report.report_finished_good_rework model?", "response": "The report.report_finished_good_rework model represents Finished Good Rework Report in the ERP system. It contains 3 fields and is used to manage finished good rework report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.report_finished_good_rework", "table_name": ""}
+{"text": "Show me the fields of module.advanced.upgrade.", "response": "The module.advanced.upgrade model has 17 fields: module_id, module_shortdesc, module_name, module_author, module_installed_version, module_latest_version, module_state, children_ids, parent_id, selected, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 6, selection: 1, one2many: 1, boolean: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "module.advanced.upgrade", "table_name": ""}
+{"text": "Which fields in account.user.reminder.lines are computed?", "response": "The account.user.reminder.lines model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.user.reminder.lines", "table_name": ""}
+{"text": "What are the relationships in blacklist.partner.wiz?", "response": "The blacklist.partner.wiz model has 4 relational fields: partner_id -> res.partner; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "blacklist.partner.wiz", "table_name": ""}
+{"text": "What are the technical details of base.document.layout?", "response": "The base.document.layout model is defined in module: web. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base.document.layout", "table_name": ""}
+{"text": "What fields does gamification.challenge have?", "response": "The gamification.challenge model has 47 fields: name, description, state, manager_id, user_ids, user_domain, period, start_date, end_date, invited_user_ids, line_ids, reward_id, reward_first_id, reward_second_id, reward_third_id, reward_failure, reward_realtime, visibility_mode, report_message_frequency, report_message_group_id, report_template_id, remind_update_delay, last_report_date, next_report_date, challenge_category, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, text: 1, selection: 5, many2one: 10, many2many: 4, date: 4, one2many: 4, boolean: 7, integer: 6, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "gamification.challenge", "table_name": ""}
+{"text": "What operations can I perform on base.update.translations?", "response": "To use the base.update.translations model, you need to provide values for required fields: lang. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.update.translations", "table_name": ""}
+{"text": "What are the available fields for account.common.journal.report?", "response": "The account.common.journal.report model has 14 fields: amount_currency, 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 types distribution: boolean: 1, many2many: 1, date: 2, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.common.journal.report", "table_name": ""}
+{"text": "List all fields in the account.journal model.", "response": "The account.journal model has 92 fields: kanban_dashboard, kanban_dashboard_graph, json_activity_data, show_on_dashboard, color, check_manual_sequencing, check_sequence_id, check_next_number, check_printing_payment_method_selected, edi_format_ids, compatible_edi_ids, sequence_id, sequence_number_next, refund_sequence_id, refund_sequence_number_next, pos_payment_method_ids, name, code, active, type_control_ids, account_control_ids, default_account_type, default_account_id, payment_debit_account_id, payment_credit_account_id, suspense_account_id, restrict_mode_hash_table, sequence, invoice_reference_type, invoice_reference_model, currency_id, company_id, country_code, refund_sequence, sequence_override_regex, inbound_payment_method_ids, outbound_payment_method_ids, at_least_one_inbound, at_least_one_outbound, profit_account_id, loss_account_id, company_partner_id, bank_account_id, bank_statements_source, bank_acc_number, bank_id, sale_activity_type_id, sale_activity_user_id, sale_activity_note, alias_id, alias_domain, alias_name, journal_group_ids, secure_sequence_id, use_reconcile, branch_id, type, is_fiscal_book_exclude, pos_method_type, decimal_rounding, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 5, boolean: 15, integer: 10, many2one: 25, char: 11, many2many: 9, one2many: 5, selection: 7, date: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.journal", "table_name": ""}
+{"text": "Show me the fields of allfresh.consignment.report.", "response": "The allfresh.consignment.report model has 15 fields: date_order, pos_ref, pos_branch_id, barcode, product_id, qty, price, margin, total_margin, consignment_move_id, currency_id, company_id, id, display_name, __last_update. Field types distribution: datetime: 2, char: 3, many2one: 5, float: 1, monetary: 3, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "allfresh.consignment.report", "table_name": ""}
+{"text": "What is the asp.asm.stock.line model?", "response": "The asp.asm.stock.line model represents Line item for adjustment in the ERP system. It contains 18 fields and is used to manage line item for adjustment data. Key fields include: name, product_id, location_id, filter_location_ids, product_qty, counted, difference_qty, asp_asm_stock_id, check_required_field, category_uom_id, uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "asp.asm.stock.line", "table_name": ""}
+{"text": "What fields does warehouse.capacity.excel.report have?", "response": "The warehouse.capacity.excel.report model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "warehouse.capacity.excel.report", "table_name": ""}
+{"text": "What are common use cases for ir.ui.menu.category?", "response": "To use the ir.ui.menu.category model, you need to provide values for required fields: sequence, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.ui.menu.category", "table_name": ""}
+{"text": "What fields does crm.team have?", "response": "The crm.team model has 73 fields: name, sequence, active, currency_id, color, favorite_user_ids, is_favorite, dashboard_button_name, dashboard_graph_data, use_leads, use_opportunities, alias_id, lead_unassigned_count, lead_all_assigned_month_count, opportunities_count, opportunities_amount, opportunities_overdue_count, opportunities_overdue_amount, use_quotations, invoiced, invoiced_target, quotations_count, quotations_amount, sales_to_invoice_count, website_ids, abandoned_carts_count, abandoned_carts_amount, use_warranty, rma_draft_count, rma_confirm_count, rma_process_count, rma_close_count, rma_reject_count, rma_ids, pos_config_ids, pos_sessions_open_count, pos_order_amount_total, user_id, company_id, member_ids, is_external_link, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, alias_name, alias_model_id, alias_user_id, alias_defaults, alias_force_thread_id, alias_domain, alias_parent_model_id, alias_parent_thread_id, alias_bounced_content, alias_contact. Field types distribution: char: 5, integer: 23, boolean: 12, many2one: 10, many2many: 3, text: 2, monetary: 2, float: 4, one2many: 7, datetime: 3, html: 1, selection: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.team", "table_name": ""}
+{"text": "Tell me about the limit.request.wizard model.", "response": "The limit.request.wizard model represents Limit Request Wizard in the ERP system. It contains 7 fields and is used to manage limit request wizard data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "limit.request.wizard", "table_name": ""}
+{"text": "Tell me about the setu.inventory.outofstock.report model.", "response": "The setu.inventory.outofstock.report model represents \n        Inventory OutOfStock Report\n        ===================================================================\n        Inventory OutOfStock Report is used to capture all products which are having demand but stock shortage as well.\n     in the ERP system. It contains 16 fields and is used to manage \n        inventory outofstock report\n        ===================================================================\n        inventory outofstock report is used to capture all products which are having demand but stock shortage as well.\n     data. Key fields include: advance_stock_days, stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "setu.inventory.outofstock.report", "table_name": ""}
+{"text": "How to query account.asset.asset data?", "response": "To use the account.asset.asset model, you need to provide values for required fields: name, value, currency_id, category_id, date, method_period, method_time, type, method, method_fiscal, method_period_fiscal, state, company_id, branch_id. Readonly fields: entry_count, name, code, value, currency_id, category_id, date, partner_id, method_number, method_period, method_end, method_progress_factor, value_residual, method_time, prorata, depreciation_line_ids, salvage_value, type, first_depreciation_manual_date, months_remaining, method, date_first_depreciation, fiscal_category_id, method_fiscal, months_remaining_fiscal, method_number_fiscal, method_period_fiscal, method_end_fiscal, depreciation_line_ids_fiscal, asset_value_residual, state1, state2, approval_matrix_id, approved_matrix_ids, is_approval_matrix, is_approve_button, approval_matrix_line_id, company_id, asset_post_entries_count, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.asset.asset", "table_name": ""}
+{"text": "What modules define stock.quant.package?", "response": "The stock.quant.package model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.quant.package", "table_name": ""}
+{"text": "What methods are available in utm.tag?", "response": "The utm.tag model is defined in module: utm. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "utm.tag", "table_name": ""}
+{"text": "How is stock.orderpoint.snooze implemented technically?", "response": "The stock.orderpoint.snooze model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.orderpoint.snooze", "table_name": ""}
+{"text": "Describe the implementation of account.fiscal.position.account.", "response": "The account.fiscal.position.account model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.fiscal.position.account", "table_name": ""}
+{"text": "What methods are available in report.sh_po_tender_management.report_analyze_quotations?", "response": "The report.sh_po_tender_management.report_analyze_quotations model is defined in module: sh_po_tender_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_po_tender_management.report_analyze_quotations", "table_name": ""}
+{"text": "What does the rating.rating model represent?", "response": "The rating.rating model represents Rating in the ERP system. It contains 30 fields and is used to manage rating data. Key fields include: create_date, res_name, res_model_id, res_model, res_id, resource_ref, parent_res_name, parent_res_model_id, parent_res_model, parent_res_id, parent_ref, rated_partner_id, partner_id, rating, rating_image, rating_text, feedback, message_id, is_internal, access_token, consumed, publisher_comment, publisher_id, publisher_datetime, id, display_name, create_uid, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "rating.rating", "table_name": ""}
+{"text": "Show me the fields of gamification.badge.user.", "response": "The gamification.badge.user model has 15 fields: user_id, sender_id, badge_id, challenge_id, comment, badge_name, level, employee_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, text: 1, char: 2, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "gamification.badge.user", "table_name": ""}
+{"text": "Describe the many2many relations for stock.picking.", "response": "The stock.picking model has 79 relational fields: backorder_id -> stock.picking; backorder_ids -> stock.picking; group_id -> procurement.group; location_dest_id -> stock.location; move_lines -> stock.move; move_ids_without_package -> stock.move; picking_type_id -> stock.picking.type; user_id -> res.users; move_line_ids -> stock.move.line; move_line_nosuggest_ids -> stock.move.line; owner_id -> res.partner; product_id -> product.product; package_level_ids -> stock.package_level; package_level_ids_details -> stock.package_level; batch_id -> stock.picking.batch; pos_session_id -> pos.session; sh_quality_check_ids -> sh.quality.check; sh_quality_alert_ids -> sh.quality.alert; attachment_ids -> ir.attachment; sale_id -> sale.order; carrier_id -> delivery.carrier; package_ids -> stock.quant.package; return_label_ids -> ir.attachment; rma_id -> dev.rma.rma; sale_ids -> sale.order; purchase_ids -> purchase.order; website_id -> website; report_template_id1 -> ir.actions.report; report_template_id -> ir.actions.report; stage_id -> order.stage; transfer_id -> internal.transfer; partner_id -> res.partner; location_id -> stock.location; company_id -> res.company; branch_id -> res.branch; filter_branch_ids -> res.branch; filter_source_location_ids -> stock.location; filter_dest_location_ids -> stock.location; filter_operation_picking_type_ids -> stock.picking.type; internal_transfer_line_id -> internal.transfer.line; analytic_account_group_ids -> account.analytic.tag; transfer_log_activity_ids -> transfer.log.activity; delivery_package_level_ids -> stock.package_level; mr_id -> material.request; rn_approval_matrix -> rn.approval.matrix; approved_matrix_ids -> rn.approval_matrix_line; approval_matrix_line_id -> rn.approval_matrix_line; do_approval_matrix -> do.approval.matrix; do_approved_matrix_ids -> do.approval_matrix_line; do_approval_matrix_line_id -> do.approval_matrix_line; picking_batch_id -> stock.picking.batch; warehouse_id -> stock.warehouse; batch_shipping_line -> batch.shipping.line; assembly_id -> assembly.production.record; kitchen_id -> kitchen.production.record; kitchen_warehouse_id -> stock.warehouse; kitchen_outlet_warehouse_id -> stock.warehouse; kitchen_analytic_group_ids -> account.analytic.tag; inv_line_ids -> account.move; operation_warehouse_id -> stock.warehouse; move_line_ids_without_package -> stock.move.line; pos_order_id -> pos.order; pos_branch_id -> res.branch; customer_partner_id -> res.partner; purchase_id -> purchase.order; company_currency_id -> res.currency; account_move_ids -> account.move; return_request_history_ids -> dev.rma.rma; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_quality_check_ids, sh_quality_alert_ids, attachment_ids, package_ids, sale_ids, purchase_ids, filter_branch_ids, filter_source_location_ids, filter_dest_location_ids, filter_operation_picking_type_ids, analytic_account_group_ids, kitchen_analytic_group_ids, inv_line_ids, account_move_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.picking", "table_name": ""}
+{"text": "Tell me about the pos.login.history model.", "response": "The pos.login.history model represents Pos Login History in the ERP system. It contains 13 fields and is used to manage pos login history data. Key fields include: user_id, pos_config_id, pos_branch_id, checkin_datetime, checkout_datetime, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.login.history", "table_name": ""}
+{"text": "What models are connected to snailmail.letter.missing.required.fields?", "response": "The snailmail.letter.missing.required.fields model has 6 relational fields: partner_id -> res.partner; letter_id -> snailmail.letter; state_id -> res.country.state; country_id -> res.country; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "snailmail.letter.missing.required.fields", "table_name": ""}
+{"text": "How is whatsapp.template.message.variable used in the system?", "response": "The whatsapp.template.message.variable model represents whatsapp Template in the ERP system. It contains 10 fields and is used to manage whatsapp template data. Key fields include: wa_id, name, description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "whatsapp.template.message.variable", "table_name": ""}
+{"text": "What data can be stored in create.purchase.request.direct?", "response": "The create.purchase.request.direct model has 12 fields: sync_data_planned, supplier_id, item_ids, journal_id, purchase_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 5, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "create.purchase.request.direct", "table_name": ""}
+{"text": "Which fields in kitchen.safety.stock are computed?", "response": "The kitchen.safety.stock model is defined in module: equip3_kitchen_operations. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kitchen.safety.stock", "table_name": ""}
+{"text": "What are the available fields for calendar.alarm_manager?", "response": "The calendar.alarm_manager model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "calendar.alarm_manager", "table_name": ""}
+{"text": "Describe the field structure of global.search.", "response": "The global.search model has 11 fields: model_id, field_ids, main_field_id, global_field_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, many2many: 1, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "global.search", "table_name": ""}
+{"text": "Tell me about the sh.tsp.top.selling.product model.", "response": "The sh.tsp.top.selling.product model represents Top selling product persistence model to  used in snippet or any other places in the ERP system. It contains 9 fields and is used to manage top selling product persistence model to  used in snippet or any other places data. Key fields include: product_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.tsp.top.selling.product", "table_name": ""}
+{"text": "List all fields in the rating.parent.mixin model.", "response": "The rating.parent.mixin model has 5 fields: rating_ids, rating_percentage_satisfaction, id, display_name, __last_update. Field types distribution: one2many: 1, integer: 2, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "rating.parent.mixin", "table_name": ""}
+{"text": "List all fields in the crm.phonecall2phonecall model.", "response": "The crm.phonecall2phonecall model has 17 fields: name, user_id, contact_name, phone, tag_ids, date, team_id, action, partner_id, note, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 5, many2many: 1, datetime: 4, selection: 1, text: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.phonecall2phonecall", "table_name": ""}
+{"text": "What are the technical details of coupon.rule?", "response": "The coupon.rule model is defined in module: coupon. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "coupon.rule", "table_name": ""}
+{"text": "Describe the many2many relations for report.dynamic_accounts_report.trial_balance.", "response": "The report.dynamic_accounts_report.trial_balance model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.trial_balance", "table_name": ""}
+{"text": "What does the initial.balance.line model represent?", "response": "The initial.balance.line model represents initial Balance Sheet in the ERP system. It contains 17 fields and is used to manage initial balance sheet data. Key fields include: name, report_name, account_id, company_id, currency_id, debit_amount, credit_amount, balance_amount, period_id, valid_value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "initial.balance.line", "table_name": ""}
+{"text": "What operations can I perform on hr.employee?", "response": "To use the hr.employee model, you need to provide values for required fields: company_id, resource_id. Readonly fields: user_partner_id, is_address_home_a_company, private_email, subordinate_ids, currency_id, image_1024, image_512, image_256, image_128, 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, hr_presence_state, last_activity, last_activity_time, hr_icon_display, goal_ids, badge_ids, has_badges, child_all_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "hr.employee", "table_name": ""}
+{"text": "What is the mrp.bom.tools model?", "response": "The mrp.bom.tools model represents MRP BoM Tools in the ERP system. It contains 17 fields and is used to manage mrp bom tools data. Key fields include: bom_id, company_id, workorder_id, product_id, quantity, uom_id, operation_id, allowed_operation_ids, operation_two_ids, operation_two_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.bom.tools", "table_name": ""}
+{"text": "How is res.config.settings implemented technically?", "response": "The res.config.settings model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.config.settings", "table_name": ""}
+{"text": "How is wizard.scrap.order.report implemented technically?", "response": "The wizard.scrap.order.report model is defined in module: eq_scrap_order_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "wizard.scrap.order.report", "table_name": ""}
+{"text": "How is report.account.report_journal used in the system?", "response": "The report.account.report_journal model represents Account Journal Report in the ERP system. It contains 3 fields and is used to manage account journal report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.account.report_journal", "table_name": ""}
+{"text": "How to create records in sale.order.alternative.product?", "response": "To use the sale.order.alternative.product 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.alternative.product", "table_name": ""}
+{"text": "What operations can I perform on blanket.quotation?", "response": "To use the blanket.quotation 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "blanket.quotation", "table_name": ""}
+{"text": "What is the account.group.template model?", "response": "The account.group.template model represents Template for Account Groups in the ERP system. It contains 12 fields and is used to manage template for account groups data. Key fields include: parent_id, code_prefix_start, code_prefix_end, chart_template_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.group.template", "table_name": ""}
+{"text": "What operations can I perform on tanda.terima.faktur?", "response": "To use the tanda.terima.faktur model, you need to provide values for required fields: move_type. Readonly fields: filter_account_move_ids, invoice_payments_widget, move_type, line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "tanda.terima.faktur", "table_name": ""}
+{"text": "Show me the relational structure of account.tax.repartition.line.template.", "response": "The account.tax.repartition.line.template model has 8 relational fields: account_id -> account.account.template; invoice_tax_id -> account.tax.template; refund_tax_id -> account.tax.template; tag_ids -> account.account.tag; plus_report_line_ids -> account.tax.report.line; minus_report_line_ids -> account.tax.report.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids, plus_report_line_ids, minus_report_line_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.tax.repartition.line.template", "table_name": ""}
+{"text": "Show me the relational structure of bus.bus.", "response": "The bus.bus model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "bus.bus", "table_name": ""}
+{"text": "Which fields in account.voucher.line are computed?", "response": "The account.voucher.line model is defined in module: aos_account_voucher. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.voucher.line", "table_name": ""}
+{"text": "What data can be stored in report.dynamic_barcode_labels.report_barcode_labels?", "response": "The report.dynamic_barcode_labels.report_barcode_labels model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.dynamic_barcode_labels.report_barcode_labels", "table_name": ""}
+{"text": "What are common use cases for gamification.challenge.line?", "response": "To use the gamification.challenge.line model, you need to provide values for required fields: challenge_id, definition_id, target_goal. Readonly fields: condition, definition_suffix, definition_monetary, definition_full_suffix, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "gamification.challenge.line", "table_name": ""}
+{"text": "What methods are available in account.partial.reconcile?", "response": "The account.partial.reconcile model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.partial.reconcile", "table_name": ""}
+{"text": "Describe the implementation of account.account.map.line.", "response": "The account.account.map.line model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.account.map.line", "table_name": ""}
+{"text": "What are common use cases for pos.promotion.special.category?", "response": "To use the pos.promotion.special.category model, you need to provide values for required fields: category_id, type, type_apply, promotion_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion.special.category", "table_name": ""}
+{"text": "How to query crm.merge.opportunity data?", "response": "To use the crm.merge.opportunity 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.merge.opportunity", "table_name": ""}
+{"text": "How do I use the report.equip3_kitchen_reports.report_kitchen_production model?", "response": "To use the report.equip3_kitchen_reports.report_kitchen_production model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_kitchen_reports.report_kitchen_production", "table_name": ""}
+{"text": "What is the mailing.trace model?", "response": "The mailing.trace model represents Mailing Statistics in the ERP system. It contains 28 fields and is used to manage mailing statistics data. Key fields include: trace_type, display_name, mail_mail_id, mail_mail_id_int, email, message_id, model, res_id, mass_mailing_id, campaign_id, ignored, scheduled, sent, exception, opened, replied, bounced, links_click_ids, clicked, state, failure_type, state_update, id, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mailing.trace", "table_name": ""}
+{"text": "What models are connected to pos.category?", "response": "The pos.category model has 7 relational fields: parent_id -> pos.category; child_id -> pos.category; pos_branch_ids -> res.branch; pos_config_ids -> pos.config; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_branch_ids, pos_config_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.category", "table_name": ""}
+{"text": "Tell me about the rn.approval_matrix_line model.", "response": "The rn.approval_matrix_line model represents Receiving Notes Approval line in the ERP system. It contains 20 fields and is used to manage receiving notes approval line data. Key fields include: sequence, sequence1, approver, minimal_approver, approval_status, feedback, time_stamp, last_approved, approved, rn_approval_matrix_id1, picking_id, approved_users, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "rn.approval_matrix_line", "table_name": ""}
+{"text": "Can you explain the purpose of report.sh_purchase_reports.sh_top_purchasing_product_doc?", "response": "The report.sh_purchase_reports.sh_top_purchasing_product_doc model represents top purchasing product report abstract model in the ERP system. It contains 3 fields and is used to manage top purchasing product report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_top_purchasing_product_doc", "table_name": ""}
+{"text": "What are the available fields for report.sh_inventory_mrp_qc.quality_alert_doc?", "response": "The report.sh_inventory_mrp_qc.quality_alert_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_inventory_mrp_qc.quality_alert_doc", "table_name": ""}
+{"text": "What methods are available in report.stock.report_product_product_replenishment?", "response": "The report.stock.report_product_product_replenishment model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.stock.report_product_product_replenishment", "table_name": ""}
+{"text": "What are the available fields for gamification.goal.definition?", "response": "The gamification.goal.definition model has 26 fields: name, description, monetary, suffix, full_suffix, computation_mode, display_mode, model_id, model_inherited_ids, field_id, field_date_id, domain, batch_mode, batch_distinctive_field, batch_user_expression, compute_code, condition, action_id, res_id_field, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 7, text: 2, boolean: 2, selection: 3, many2one: 7, many2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "gamification.goal.definition", "table_name": ""}
+{"text": "Describe the field structure of stock.location.route.", "response": "The stock.location.route model has 22 fields: name, active, sequence, rule_ids, product_selectable, product_categ_selectable, warehouse_selectable, supplied_wh_id, supplier_wh_id, company_id, product_ids, categ_ids, warehouse_domain_ids, warehouse_ids, sale_selectable, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 5, integer: 2, one2many: 2, many2one: 5, many2many: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.location.route", "table_name": ""}
+{"text": "Show me the fields of ir.qweb.field.html.", "response": "The ir.qweb.field.html model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.html", "table_name": ""}
+{"text": "Which fields in account.group are computed?", "response": "The account.group model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.group", "table_name": ""}
+{"text": "What operations can I perform on account.deposit.return?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.deposit.return", "table_name": ""}
+{"text": "Describe the implementation of stock.day.average.", "response": "The stock.day.average model is defined in module: equip3_inventory_control. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.day.average", "table_name": ""}
+{"text": "Can you explain the purpose of ir.logging?", "response": "The ir.logging model represents Logging in the ERP system. It contains 15 fields and is used to manage logging data. Key fields include: create_uid, create_date, write_uid, write_date, name, type, dbname, level, message, path, func, line, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.logging", "table_name": ""}
+{"text": "Show me the relational structure of theme.website.menu.", "response": "The theme.website.menu model has 5 relational fields: page_id -> theme.website.page; parent_id -> theme.website.menu; copy_ids -> website.menu; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "theme.website.menu", "table_name": ""}
+{"text": "Describe the field structure of ir.autovacuum.", "response": "The ir.autovacuum model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.autovacuum", "table_name": ""}
+{"text": "What are common use cases for barcode.rule?", "response": "To use the barcode.rule model, you need to provide values for required fields: name, encoding, pattern, alias, type. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "barcode.rule", "table_name": ""}
+{"text": "What are the available fields for base_import.tests.models.float?", "response": "The base_import.tests.models.float model has 10 fields: value, value2, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 1, monetary: 1, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.float", "table_name": ""}
+{"text": "What does the sh.fiscal.year model represent?", "response": "The sh.fiscal.year model represents Fiscal Year in the ERP system. It contains 18 fields and is used to manage fiscal year data. Key fields include: name, code, date_start, date_end, period_ids, state, company_id, branch_id, hide_button, move_id, summary_move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.fiscal.year", "table_name": ""}
+{"text": "Describe the implementation of sale.order.alternative.product.", "response": "The sale.order.alternative.product model is defined in module: equip3_sale_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.order.alternative.product", "table_name": ""}
+{"text": "What models are connected to ai.chat.session?", "response": "The ai.chat.session model has 7 relational fields: user_id -> res.users; config_id -> ai.agent.config; message_ids -> ai.chat.message; job_ids -> ai.chat.job; last_job_id -> ai.chat.job; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ai.chat.session", "table_name": ""}
+{"text": "What foreign keys exist in vendor.deposit.report?", "response": "The vendor.deposit.report model has 7 relational fields: partner_id -> res.partner; currency_id -> res.currency; deposit_move_id -> account.move; return_deposit -> account.move; deposit_reconcile_journal_id -> account.journal; journal_id -> account.journal; deposit_account_id -> account.account. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "vendor.deposit.report", "table_name": ""}
+{"text": "Tell me about the multiple.rfq model.", "response": "The multiple.rfq model represents Multiple Rfq in the ERP system. It contains 9 fields and is used to manage multiple rfq data. Key fields include: vendor_ids, product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "multiple.rfq", "table_name": ""}
+{"text": "What are the available fields for snailmail.letter.cancel?", "response": "The snailmail.letter.cancel model has 9 fields: model, help_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "snailmail.letter.cancel", "table_name": ""}
+{"text": "How does export.efaktur relate to other models?", "response": "The export.efaktur model has 4 relational fields: partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "export.efaktur", "table_name": ""}
+{"text": "What does the purchase.report.representative.xls model represent?", "response": "The purchase.report.representative.xls model represents Purchase Report Representative Xls in the ERP system. It contains 9 fields and is used to manage purchase report representative xls data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.report.representative.xls", "table_name": ""}
+{"text": "Which fields in account.keterangan.tambahan are computed?", "response": "The account.keterangan.tambahan model is defined in module: equip3_accounting_efaktur. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.keterangan.tambahan", "table_name": ""}
+{"text": "What models are connected to account.user.reminder?", "response": "The account.user.reminder model has 5 relational fields: company_id -> res.company; branch_id -> res.branch; account_line_ids -> account.user.reminder.lines; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.user.reminder", "table_name": ""}
+{"text": "List all fields in the generate.pos.voucher.use.history model.", "response": "The generate.pos.voucher.use.history model has 13 fields: pos_order_id, payment_id, voucher_id, value, used_date, cashier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, float: 1, datetime: 4, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "generate.pos.voucher.use.history", "table_name": ""}
+{"text": "What data can be stored in account.pettycash.fund.change?", "response": "The account.pettycash.fund.change model has 18 fields: fund, fund_name, custodian, fund_amount, new_amount, payable_account, receivable_account, effective_date, do_receivable, move, is_add_balance, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, char: 2, float: 2, date: 1, boolean: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.pettycash.fund.change", "table_name": ""}
+{"text": "Which fields in accounting.matrix.reject are computed?", "response": "The accounting.matrix.reject model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "accounting.matrix.reject", "table_name": ""}
+{"text": "What are the available fields for crm.lead.product?", "response": "The crm.lead.product model has 14 fields: product_id, description, qty, product_uom, price_unit, tax_id, lead_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, text: 1, float: 2, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.lead.product", "table_name": ""}
+{"text": "What methods are available in invoice.template.header?", "response": "The invoice.template.header model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.template.header", "table_name": ""}
+{"text": "Describe the many2many relations for procurement.group.", "response": "The procurement.group model has 6 relational fields: partner_id -> res.partner; stock_move_ids -> stock.move; mrp_production_ids -> mrp.production; sale_id -> sale.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "procurement.group", "table_name": ""}
+{"text": "Show me the relational structure of qiscus.wa.template.", "response": "The qiscus.wa.template model has 12 relational fields: content_ids -> qiscus.wa.template.content; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "qiscus.wa.template", "table_name": ""}
+{"text": "How to create records in account.account?", "response": "To use the account.account model, you need to provide values for required fields: name, code, user_type_id, company_id. Readonly fields: balance, credit, debit, initial_balance, used, internal_type, internal_group, company_id, group_id, root_id, opening_balance, is_off_balance, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.account", "table_name": ""}
+{"text": "How to query account.root data?", "response": "To use the account.root model, you need to provide values for required fields: none. Readonly fields: name, parent_id, company_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.root", "table_name": ""}
+{"text": "What are the technical details of res.users.qiscuss?", "response": "The res.users.qiscuss model is defined in module: equip3_crm_whatsapp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.qiscuss", "table_name": ""}
+{"text": "What modules define x.report.wizard?", "response": "The x.report.wizard model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "x.report.wizard", "table_name": ""}
+{"text": "Tell me about the account.tax.repartition.line model.", "response": "The account.tax.repartition.line model represents Tax Repartition Line in the ERP system. It contains 19 fields and is used to manage tax repartition line data. Key fields include: factor_percent, factor, repartition_type, account_id, tag_ids, invoice_tax_id, refund_tax_id, tax_id, tax_fiscal_country_id, company_id, sequence, use_in_tax_closing, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.tax.repartition.line", "table_name": ""}
+{"text": "What foreign keys exist in report.sh_sale_reports.sh_sale_details_report_doc?", "response": "The report.sh_sale_reports.sh_sale_details_report_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_sale_details_report_doc", "table_name": ""}
+{"text": "How to query dynamic.balance.sheet.report data?", "response": "To use the dynamic.balance.sheet.report model, you need to provide values for required fields: company_id, journal_ids, display_account, target_move. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "dynamic.balance.sheet.report", "table_name": ""}
+{"text": "Show me the relational structure of crm.meeting.overview.", "response": "The crm.meeting.overview model has 18 relational fields: calendar_id -> calendar.event; opportunity_id -> crm.lead; activity_type_id -> mail.activity.type; partner_ids -> res.partner; stage_id -> crm.stage; order_ids -> sale.order; final_quotation -> quotation.amount; activity_ids -> mail.activity; meeting_salesperson_ids -> res.users; activity_user_id -> res.users; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, meeting_salesperson_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.meeting.overview", "table_name": ""}
+{"text": "List all fields in the auth_totp.wizard model.", "response": "The auth_totp.wizard model has 12 fields: user_id, secret, url, qrcode, code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 4, binary: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "auth_totp.wizard", "table_name": ""}
+{"text": "What is the import.record.data model?", "response": "The import.record.data model represents import.record.data in the ERP system. It contains 46 fields and is used to manage import.record.data data. Key fields include: name, state, record_type, created_date, partner_id, warehouse_id, location_id, no_return, sheet_number, error_message, product_list, file, file_name, filter_location_ids, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "import.record.data", "table_name": ""}
+{"text": "What are common use cases for order.stage?", "response": "To use the order.stage 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "order.stage", "table_name": ""}
+{"text": "How do I use the approval.matrix.direct.purchase model?", "response": "To use the approval.matrix.direct.purchase model, you need to provide values for required fields: name, company_id, branch_id, minimum_amt, maximum_amt. Readonly fields: company_id, is_good_services_order, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.direct.purchase", "table_name": ""}
+{"text": "How does account.bank.statement.import.journal.creation relate to other models?", "response": "The account.bank.statement.import.journal.creation model has 40 relational fields: journal_id -> account.journal; create_uid -> res.users; write_uid -> res.users; check_sequence_id -> ir.sequence; edi_format_ids -> account.edi.format; compatible_edi_ids -> account.edi.format; sequence_id -> ir.sequence; refund_sequence_id -> ir.sequence; pos_payment_method_ids -> pos.payment.method; type_control_ids -> account.account.type; account_control_ids -> account.account; default_account_type -> account.account.type; default_account_id -> account.account; payment_debit_account_id -> account.account; payment_credit_account_id -> account.account; suspense_account_id -> account.account; currency_id -> res.currency; company_id -> res.company; inbound_payment_method_ids -> account.payment.method; outbound_payment_method_ids -> account.payment.method; profit_account_id -> account.account; loss_account_id -> account.account; company_partner_id -> res.partner; bank_account_id -> res.partner.bank; bank_id -> res.bank; sale_activity_type_id -> mail.activity.type; sale_activity_user_id -> res.users; alias_id -> mail.alias; journal_group_ids -> account.journal.group; secure_sequence_id -> ir.sequence; branch_id -> res.branch; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message. Many2many fields: edi_format_ids, compatible_edi_ids, type_control_ids, account_control_ids, inbound_payment_method_ids, outbound_payment_method_ids, journal_group_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.bank.statement.import.journal.creation", "table_name": ""}
+{"text": "What is the receivable.flow.wizard model?", "response": "The receivable.flow.wizard model represents receivable.flow.wizard in the ERP system. It contains 8 fields and is used to manage receivable.flow.wizard data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "receivable.flow.wizard", "table_name": ""}
+{"text": "What fields does cancel.closing.entries have?", "response": "The cancel.closing.entries model has 8 fields: fiscal_year_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "cancel.closing.entries", "table_name": ""}
+{"text": "Which fields in res.partner.title are computed?", "response": "The res.partner.title model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.partner.title", "table_name": ""}
+{"text": "What are the available fields for convert.revenue?", "response": "The convert.revenue model has 11 fields: date, revenue_account_id, deposit_type, expenses_account_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, many2one: 4, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "convert.revenue", "table_name": ""}
+{"text": "How is qiscus.wa.template.content used in the system?", "response": "The qiscus.wa.template.content model represents qiscus.wa.template.content in the ERP system. It contains 13 fields and is used to manage qiscus.wa.template.content data. Key fields include: template_id, name, language, content_id, content, category, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "qiscus.wa.template.content", "table_name": ""}
+{"text": "What does the sh.base.send.whatsapp.number.wizard model represent?", "response": "The sh.base.send.whatsapp.number.wizard model represents Send whatsapp message wizard in the ERP system. It contains 11 fields and is used to manage send whatsapp message wizard data. Key fields include: partner_ids, whatsapp_mobile, message, crm_lead_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.base.send.whatsapp.number.wizard", "table_name": ""}
+{"text": "How to create records in report_excel_export_gen?", "response": "To use the report_excel_export_gen 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report_excel_export_gen", "table_name": ""}
+{"text": "What methods are available in coupon.reward?", "response": "The coupon.reward model is defined in module: coupon. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "coupon.reward", "table_name": ""}
+{"text": "How to create records in sh.custom.field.model?", "response": "To use the sh.custom.field.model model, you need to provide values for required fields: name, model_id, field_type, model, field_description, state, ttype. Readonly fields: task_model_name, selected_tab, parent_model_name, relation_field_id, related_field_id, state, modules, relation_model_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.custom.field.model", "table_name": ""}
+{"text": "Tell me about the mass.editing.wizard model.", "response": "The mass.editing.wizard model represents Wizard for mass edition in the ERP system. It contains 13 fields and is used to manage wizard for mass edition data. Key fields include: selected_item_qty, remaining_item_qty, operation_description_info, operation_description_warning, operation_description_danger, message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mass.editing.wizard", "table_name": ""}
+{"text": "Show me the fields of account.fiscal.position.tax.template.", "response": "The account.fiscal.position.tax.template model has 10 fields: position_id, tax_src_id, tax_dest_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.fiscal.position.tax.template", "table_name": ""}
+{"text": "How to query project.task.create.timesheet data?", "response": "To use the project.task.create.timesheet model, you need to provide values for required fields: task_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.task.create.timesheet", "table_name": ""}
+{"text": "What are the relationships in project.task.type.delete.wizard?", "response": "The project.task.type.delete.wizard model has 4 relational fields: project_ids -> project.project; stage_ids -> project.task.type; create_uid -> res.users; write_uid -> res.users. Many2many fields: project_ids, stage_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "project.task.type.delete.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for res.country.state.", "response": "The res.country.state model has 4 relational fields: country_id -> res.country; city_ids -> res.country.city; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.country.state", "table_name": ""}
+{"text": "How do I use the purchase.request.allocation model?", "response": "To use the purchase.request.allocation model, you need to provide values for required fields: purchase_request_line_id, product_uom_id. Readonly fields: company_id, product_id, product_uom_id, open_product_qty, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.request.allocation", "table_name": ""}
+{"text": "What are the relationships in stock.warehouse.orderpoint?", "response": "The stock.warehouse.orderpoint model has 37 relational fields: product_tmpl_id -> product.template; product_id -> product.product; product_category_id -> product.category; product_uom -> uom.uom; group_id -> procurement.group; allowed_location_ids -> stock.location; rule_ids -> stock.rule; allowed_route_ids -> stock.location.route; route_id -> stock.location.route; bom_id -> mrp.bom; location_id -> stock.location; source_location_id -> stock.location; purchase_request_id -> purchase.request; purchase_order_id -> purchase.order; material_request_id -> material.request; internal_transfer_id -> internal.transfer; responsible_id -> res.users; branch_id -> res.branch; company_id -> res.company; warehouse_id -> stock.warehouse; filter_warehouse_id -> stock.location; notification_user_ids -> res.users; supplier_id -> res.partner; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: rule_ids, allowed_route_ids, responsible_id, filter_warehouse_id, notification_user_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.warehouse.orderpoint", "table_name": ""}
+{"text": "How to query pos.promotion.discount.apply data?", "response": "To use the pos.promotion.discount.apply model, you need to provide values for required fields: product_id, promotion_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion.discount.apply", "table_name": ""}
+{"text": "What operations can I perform on stock.picking?", "response": "To use the stock.picking model, you need to provide values for required fields: move_type, location_dest_id, picking_type_id, location_id, branch_id. Readonly fields: name, backorder_id, group_id, date_deadline, has_deadline_issue, delay_alert_date, json_popover, location_dest_id, has_scrap_move, picking_type_id, picking_type_code, picking_type_entire_packs, hide_picking_type, move_line_exist, has_packages, show_check_availability, show_mark_as_todo, show_validate, use_create_lots, product_id, show_operations, show_reserved, show_lots_text, has_tracking, products_availability, products_availability_state, sh_quality_check_ids, sh_quality_alert_ids, qc_count, qc_alert_count, need_qc, qc_fail, qc_pass, full_pass, is_mandatory, delivery_type, weight, carrier_tracking_url, weight_uom_name, package_ids, weight_bulk, shipping_weight, is_return_picking, return_label_ids, sh_stock_bm_is_cont_scan, website_id, is_transfer_in, is_transfer_out, location_id, date_done, company_id, is_show_location, branch_id, filter_branch_ids, filter_source_location_ids, filter_dest_location_ids, filter_operation_picking_type_ids, journal_cancel, merge_info, is_return_orders, return_date_limit, origin_src_location, origin_dest_location, check_second_picking_reserve, process_time, process_time_hours, show_entire_packs, is_mbs_on_transfer_operations, is_source_package, rn_approval_matrix, is_rn_request_approval_matrix, status_1, status_2, status_3, status_4, approved_matrix_ids, approval_matrix_line_id, is_approve_button, is_reset_to_draft, check_product, is_adjustable_picking, do_approval_matrix, is_do_request_approval_matrix, do_approved_matrix_ids, do_approval_matrix_line_id, is_approve_button_do, is_reset_to_draft_do, force_validate_button, current_user, partner_id_domain, owner_id_domain, journal_button, qty_can_minus_boolean, state, is_deployed, is_expired_tranfer, fulfillment, operation_warehouse_id, pos_branch_id, is_dropship, customer_partner_id, is_vendor_taxes, purchase_id, company_currency_id, amount_subtotal, amount_tax, amount_total, amount_discount, amount_untaxed, discount_promotions_amount, return_request_history_ids, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.picking", "table_name": ""}
+{"text": "What modules define report.project.task.user?", "response": "The report.project.task.user model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.project.task.user", "table_name": ""}
+{"text": "Describe the stock.rules.report model in Odoo.", "response": "The stock.rules.report model represents Stock Rules report in the ERP system. It contains 12 fields and is used to manage stock rules report data. Key fields include: product_id, product_tmpl_id, warehouse_ids, product_has_variants, so_route_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.rules.report", "table_name": ""}
+{"text": "What foreign keys exist in mrp.quality.check.report?", "response": "The mrp.quality.check.report model has 3 relational fields: product_ids -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.quality.check.report", "table_name": ""}
+{"text": "What foreign keys exist in update.customer.segment?", "response": "The update.customer.segment model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "update.customer.segment", "table_name": ""}
+{"text": "How is crm.salesperson.tracking.report used in the system?", "response": "The crm.salesperson.tracking.report model represents crm.salesperson.tracking.report in the ERP system. It contains 9 fields and is used to manage crm.salesperson.tracking.report data. Key fields include: sales_person, current_datetime, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.salesperson.tracking.report", "table_name": ""}
+{"text": "Show me the relational structure of setu.stock.movement.report.", "response": "The setu.stock.movement.report model has 7 relational fields: company_ids -> res.company; product_category_ids -> product.category; product_ids -> product.product; warehouse_ids -> stock.warehouse; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids, product_category_ids, product_ids, warehouse_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.stock.movement.report", "table_name": ""}
+{"text": "Describe the implementation of crm.lead2opportunity.partner.mass.", "response": "The crm.lead2opportunity.partner.mass model is defined in module: crm. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.lead2opportunity.partner.mass", "table_name": ""}
+{"text": "What business logic is in report.membership?", "response": "To use the report.membership model, you need to provide values for required fields: none. Readonly fields: start_date, date_to, num_waiting, num_invoiced, num_paid, tot_pending, tot_earned, partner_id, associate_member_id, membership_id, membership_state, user_id, company_id, quantity, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.membership", "table_name": ""}
+{"text": "What modules define hide.filters.groups?", "response": "The hide.filters.groups model is defined in module: simplify_access_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hide.filters.groups", "table_name": ""}
+{"text": "Which fields in sh.custom.model.tab are computed?", "response": "The sh.custom.model.tab model is defined in module: sh_global_custom_fields. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.custom.model.tab", "table_name": ""}
+{"text": "Tell me about the mr_line.pr.wizard_line model.", "response": "The mr_line.pr.wizard_line model represents mr_line.pr.wizard_line in the ERP system. It contains 17 fields and is used to manage mr_line.pr.wizard_line data. Key fields include: mr_id, mr_line_id, no, product_id, description, uom_id, qty_purchase, request_date, dest_warehouse_id, mr_pr_wizard, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mr_line.pr.wizard_line", "table_name": ""}
+{"text": "How is pos.promotion.gift.free implemented technically?", "response": "The pos.promotion.gift.free model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.promotion.gift.free", "table_name": ""}
+{"text": "What are the available fields for mrp.consumption.warning?", "response": "The mrp.consumption.warning model has 11 fields: mrp_production_ids, mrp_production_count, consumption, mrp_consumption_warning_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, integer: 2, selection: 1, one2many: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.consumption.warning", "table_name": ""}
+{"text": "Tell me about the approval.matrix.vendor.line model.", "response": "The approval.matrix.vendor.line model represents Approval Matrix Vendor Line in the ERP system. It contains 22 fields and is used to manage approval matrix vendor line data. Key fields include: sequence, approval_matrix, company_id, branch_id, user_ids, minimum_approver, approved_users, state_char, time_stamp, feedback, last_approved, approved, app_matrix_id, sequence2, approver_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.vendor.line", "table_name": ""}
+{"text": "What data can be stored in ir.exports.line?", "response": "The ir.exports.line model has 9 fields: name, export_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.exports.line", "table_name": ""}
+{"text": "How do I use the pos.promotion.multi.buy model?", "response": "To use the pos.promotion.multi.buy model, you need to provide values for required fields: product_ids, promotion_id, list_price, qty_apply. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion.multi.buy", "table_name": ""}
+{"text": "Describe the kitchen.cooking.list.line model in Odoo.", "response": "The kitchen.cooking.list.line model represents Kitchen Cooking lIst Line in the ERP system. It contains 13 fields and is used to manage kitchen cooking list line data. Key fields include: list_id, product_id, uom_id, inventory_quantity, outgoing_qty, to_produce_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kitchen.cooking.list.line", "table_name": ""}
+{"text": "How to query milestone.contract.template.checklist data?", "response": "To use the milestone.contract.template.checklist 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "milestone.contract.template.checklist", "table_name": ""}
+{"text": "How is ir.translation implemented technically?", "response": "The ir.translation model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.translation", "table_name": ""}
+{"text": "What modules define sale.order.pricelist.wizard.line?", "response": "The sale.order.pricelist.wizard.line model is defined in module: sh_sale_pricelist. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.order.pricelist.wizard.line", "table_name": ""}
+{"text": "How to query account.reconcile.model.line data?", "response": "To use the account.reconcile.model.line model, you need to provide values for required fields: sequence, account_id, amount_type, amount_string. Readonly fields: model_id, match_total_amount, match_total_amount_param, rule_type, company_id, show_force_tax_included, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.reconcile.model.line", "table_name": ""}
+{"text": "What data can be stored in report.mrp.report_bom_structure?", "response": "The report.mrp.report_bom_structure model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.mrp.report_bom_structure", "table_name": ""}
+{"text": "What operations can I perform on full.inv.adjustment.import?", "response": "To use the full.inv.adjustment.import model, you need to provide values for required fields: import_file. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "full.inv.adjustment.import", "table_name": ""}
+{"text": "What modules define budget.change.req.wizard?", "response": "The budget.change.req.wizard model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "budget.change.req.wizard", "table_name": ""}
+{"text": "How do I use the product.pricelist.history model?", "response": "To use the product.pricelist.history model, you need to provide values for required fields: none. Readonly fields: currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.pricelist.history", "table_name": ""}
+{"text": "What does the account.incoterms model represent?", "response": "The account.incoterms model represents Incoterms in the ERP system. It contains 10 fields and is used to manage incoterms data. Key fields include: name, code, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.incoterms", "table_name": ""}
+{"text": "What foreign keys exist in report.excel.fields?", "response": "The report.excel.fields model has 7 relational fields: report_excel_section_id -> report.excel.section; aggregate_ids -> report.excel.aggregate; aggregate_id -> report.excel.aggregate; having_param_ids -> report.excel.param; having_param_id -> report.excel.param; create_uid -> res.users; write_uid -> res.users. Many2many fields: aggregate_ids, having_param_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.excel.fields", "table_name": ""}
+{"text": "What are the available fields for res.currency.tax?", "response": "The res.currency.tax model has 13 fields: name, rate, conversion, mr_rate, currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, float: 3, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.currency.tax", "table_name": ""}
+{"text": "Show me the relational structure of rating.mixin.", "response": "The rating.mixin model has 1 relational fields: rating_ids -> rating.rating. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "rating.mixin", "table_name": ""}
+{"text": "What fields does utm.tag have?", "response": "The utm.tag model has 9 fields: name, color, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "utm.tag", "table_name": ""}
+{"text": "What foreign keys exist in repair.fee?", "response": "The repair.fee model has 10 relational fields: repair_id -> repair.order; company_id -> res.company; currency_id -> res.currency; product_id -> product.product; product_uom -> uom.uom; product_uom_category_id -> uom.category; tax_id -> account.tax; invoice_line_id -> account.move.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "repair.fee", "table_name": ""}
+{"text": "What business logic is in asset.asset.report?", "response": "To use the asset.asset.report model, you need to provide values for required fields: none. Readonly fields: name, date, depreciation_date, asset_id, asset_category_id, partner_id, state, installment_value, move_check, installment_nbr, depreciation_nbr, gross_value, posted_value, unposted_value, company_id, depreciation_value, salvage_value, value_residual, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "asset.asset.report", "table_name": ""}
+{"text": "What are the technical details of mail.wizard.invite?", "response": "The mail.wizard.invite model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.wizard.invite", "table_name": ""}
+{"text": "How is mr.internal_transfer_line implemented technically?", "response": "The mr.internal_transfer_line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mr.internal_transfer_line", "table_name": ""}
+{"text": "What foreign keys exist in account.account.template?", "response": "The account.account.template model has 8 relational fields: currency_id -> res.currency; user_type_id -> account.account.type; tax_ids -> account.tax.template; chart_template_id -> account.chart.template; tag_ids -> account.account.tag; parent_id -> account.account.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_ids, tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.account.template", "table_name": ""}
+{"text": "How do I use the analytic.sale.order.line model?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "analytic.sale.order.line", "table_name": ""}
+{"text": "How is ai.chat.session implemented technically?", "response": "The ai.chat.session model is defined in module: ai_chat_agent. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ai.chat.session", "table_name": ""}
+{"text": "How to create records in mail.resend.message?", "response": "To use the mail.resend.message model, you need to provide values for required fields: none. Readonly fields: mail_message_id, notification_ids, has_cancel, partner_readonly, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.resend.message", "table_name": ""}
+{"text": "What models are connected to remove.pos.order?", "response": "The remove.pos.order model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "remove.pos.order", "table_name": ""}
+{"text": "How to create records in ir.ui.view.custom?", "response": "To use the ir.ui.view.custom model, you need to provide values for required fields: ref_id, user_id, arch. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.ui.view.custom", "table_name": ""}
+{"text": "What modules define wizard.asset.create?", "response": "The wizard.asset.create model is defined in module: equip3_accounting_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "wizard.asset.create", "table_name": ""}
+{"text": "What are the relationships in remove.action?", "response": "The remove.action model has 8 relational fields: access_management_id -> access.management; model_id -> ir.model; view_data_ids -> view.data; server_action_ids -> action.data; report_action_ids -> action.data; view_ids -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: view_data_ids, server_action_ids, report_action_ids, view_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "remove.action", "table_name": ""}
+{"text": "Describe the account.tax.map.purchase.line model in Odoo.", "response": "The account.tax.map.purchase.line model represents Account Tax Map Purchase Line in the ERP system. It contains 17 fields and is used to manage account tax map purchase line data. Key fields include: company_id, purchase_tax_id, target_company, target_purchase_tax, map_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, line_ids, child_company_id, ownership, sales_line_ids, purchase_line_ids.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.tax.map.purchase.line", "table_name": ""}
+{"text": "How do I use the mail.template.preview model?", "response": "To use the mail.template.preview model, you need to provide values for required fields: mail_template_id. Readonly fields: model_id, no_record, error_msg, subject, email_from, email_to, email_cc, reply_to, scheduled_date, body_html, attachment_ids, partner_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.template.preview", "table_name": ""}
+{"text": "What are the relationships in sh.sale.invoice.summary.xls?", "response": "The sh.sale.invoice.summary.xls model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.sale.invoice.summary.xls", "table_name": ""}
+{"text": "What models are connected to mail.activity.type?", "response": "The mail.activity.type model has 9 relational fields: create_uid -> res.users; res_model_id -> ir.model; default_next_type_id -> mail.activity.type; next_type_ids -> mail.activity.type; previous_type_ids -> mail.activity.type; mail_template_ids -> mail.template; default_user_id -> res.users; initial_res_model_id -> ir.model; write_uid -> res.users. Many2many fields: next_type_ids, previous_type_ids, mail_template_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.activity.type", "table_name": ""}
+{"text": "What methods are available in expiry.picking.confirmation?", "response": "The expiry.picking.confirmation model is defined in module: product_expiry. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "expiry.picking.confirmation", "table_name": ""}
+{"text": "Describe the many2many relations for sh.purchase.update.mass.tag.wizard.", "response": "The sh.purchase.update.mass.tag.wizard model has 4 relational fields: purchase_order_ids -> purchase.order; wiz_tag_ids -> sh.purchase.tags; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_order_ids, wiz_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.update.mass.tag.wizard", "table_name": ""}
+{"text": "Show me the fields of material.request.line.", "response": "The material.request.line model has 47 fields: material_request_id, sequence, no, product, description, quantity, product_unit_measure, product_uom_category_id, destination_location_id, destination_warehouse_id, status, request_date, done_qty_dup, done_qty, requested_qty, remaining_qty, source_document, requested_by, company_id, branch_id, create_date, pr_requested_qty, pr_pending_qty_to_receive, pr_in_progress_qty, pr_done_qty, pr_cancelled_qty, itr_requested_qty, itr_in_progress_qty, itr_done_qty, itr_returned_qty, pr_lines_ids, ir_lines_ids, itr_war_lines_ids, analytic_account_group_ids, progress_quantity, pr_remaining_qty, itr_remaining_qty, itw_requested_qty, itw_in_progress_qty, itw_remaining_qty, itw_done_qty, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: many2one: 11, integer: 3, text: 1, float: 21, selection: 1, date: 1, char: 2, datetime: 3, one2many: 3, many2many: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "material.request.line", "table_name": ""}
+{"text": "Show me the fields of repair.order.make_invoice.", "response": "The repair.order.make_invoice model has 8 fields: group, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "repair.order.make_invoice", "table_name": ""}
+{"text": "Describe the many2many relations for opening.balance.line.", "response": "The opening.balance.line model has 7 relational fields: move_id -> opening.balance; company_id -> res.company; account_id -> account.account; partner_id -> res.partner; company_currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "opening.balance.line", "table_name": ""}
+{"text": "How does mail.activity.type relate to other models?", "response": "The mail.activity.type model has 9 relational fields: create_uid -> res.users; res_model_id -> ir.model; default_next_type_id -> mail.activity.type; next_type_ids -> mail.activity.type; previous_type_ids -> mail.activity.type; mail_template_ids -> mail.template; default_user_id -> res.users; initial_res_model_id -> ir.model; write_uid -> res.users. Many2many fields: next_type_ids, previous_type_ids, mail_template_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.activity.type", "table_name": ""}
+{"text": "What business logic is in combo.option?", "response": "To use the combo.option model, you need to provide values for required fields: combo_name. Readonly fields: image_1024, image_512, image_256, image_128, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "combo.option", "table_name": ""}
+{"text": "What are common use cases for global.search?", "response": "To use the global.search model, you need to provide values for required fields: model_id, main_field_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "global.search", "table_name": ""}
+{"text": "Show me the relational structure of ks_custom_report.ks_column.", "response": "The ks_custom_report.ks_column model has 4 relational fields: ks_cr_model_id -> ks_custom_report.ks_report; ks_cr_field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks_custom_report.ks_column", "table_name": ""}
+{"text": "Describe the implementation of account.multipayment.difference.", "response": "The account.multipayment.difference model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.multipayment.difference", "table_name": ""}
+{"text": "What operations can I perform on mail.compose.message?", "response": "To use the mail.compose.message model, you need to provide values for required fields: message_type. Readonly fields: active_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.compose.message", "table_name": ""}
+{"text": "How is account.automatic.entry.wizard implemented technically?", "response": "The account.automatic.entry.wizard model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.automatic.entry.wizard", "table_name": ""}
+{"text": "How to create records in report.pos.order?", "response": "To use the report.pos.order model, you need to provide values for required fields: none. Readonly fields: date, order_id, partner_id, product_id, product_tmpl_id, user_id, price_total, price_sub_total, total_discount, average_price, company_id, nbr_lines, product_qty, product_categ_id, invoiced, config_id, pos_categ_id, pricelist_id, session_id, employee_id, promotion_count, promotion_id, voucher_id, voucher_count, voucher_value, cashier_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.pos.order", "table_name": ""}
+{"text": "What modules define calendar.recurrence?", "response": "The calendar.recurrence model is defined in module: calendar. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "calendar.recurrence", "table_name": ""}
+{"text": "What fields does account.move.line have?", "response": "The account.move.line model has 140 fields: asset_category_id, asset_start_date, asset_end_date, asset_mrr, purchase_line_id, purchase_order_id, period_id, fiscal_year, is_anglo_saxon_line, product_type, is_landed_costs_line, discount_method, discount_type, discount_amount, discount_amt, branch_id, repair_line_ids, repair_fee_ids, is_down_payment, move_id, move_name, date, ref, parent_state, journal_id, company_id, company_currency_id, tax_fiscal_country_id, account_id, account_internal_type, account_internal_group, account_root_id, sequence, name, quantity, price_unit, discount, debit, credit, balance, cumulated_balance, amount_currency, price_subtotal, price_total, reconciled, blocked, date_maturity, currency_id, partner_id, product_uom_id, product_id, product_uom_category_id, reconcile_model_id, payment_id, statement_line_id, statement_id, tax_ids, tax_line_id, tax_group_id, tax_base_amount, tax_exigible, tax_repartition_line_id, tax_tag_ids, tax_audit, amount_residual, amount_residual_currency, full_reconcile_id, matched_debit_ids, matched_credit_ids, matching_number, analytic_line_ids, analytic_account_id, analytic_tag_ids, recompute_tax_line, display_type, is_rounding_line, exclude_from_invoice_tab, is_fiscal_book_exclude, price_tax_discount, is_update_disc_line, price_tax, unit_price_fnct, disc_percentage_rel, date_id, is_discount_line, is_interest_line, is_analytic_tags, total_qty_price_unit, multi_discount, is_intercompany_transaction, customer_deposit_id, vendor_deposit_id, tax_ids_ppn, price_total_ppn, amount_ppn, taxes_ppn, sale_line_ids, is_down_payment_discount, res_dp_amount, is_purchase_order, is_sales_order, sequence2, pos_branch_id, approval_code, check_reconcile, check_reconcile_done, check_reconcile_flag, check_payment, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 35, date: 7, float: 9, boolean: 26, selection: 9, one2many: 9, char: 11, integer: 7, monetary: 16, many2many: 7, html: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.move.line", "table_name": ""}
+{"text": "How to create records in barcode.nomenclature?", "response": "To use the barcode.nomenclature model, you need to provide values for required fields: name, upc_ean_conv. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "barcode.nomenclature", "table_name": ""}
+{"text": "What business logic is in delivery.price.rule?", "response": "To use the delivery.price.rule model, you need to provide values for required fields: sequence, carrier_id, variable, operator, max_value, list_base_price, list_price, variable_factor. Readonly fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "delivery.price.rule", "table_name": ""}
+{"text": "How do I use the asset.asset.revalue.wizard model?", "response": "To use the asset.asset.revalue.wizard model, you need to provide values for required fields: reason, remaining_value, amount, journal_id, method_number, method_period. Readonly fields: remaining_value, company_id, company_currency_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "asset.asset.revalue.wizard", "table_name": ""}
+{"text": "Show me the fields of orderwizline.orderwizline.", "response": "The orderwizline.orderwizline model has 17 fields: reverse_id, product_id, partner_id, remaining_quantity, new_quatation_quantity, unit_of_measure_id, unit_price, taxes_id, subtotal, blanket_order_line_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, float: 4, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "orderwizline.orderwizline", "table_name": ""}
+{"text": "Describe the many2many relations for product.expire.report.", "response": "The product.expire.report model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.expire.report", "table_name": ""}
+{"text": "How does approval.matrix.direct.purchase.line relate to other models?", "response": "The approval.matrix.direct.purchase.line model has 7 relational fields: user_ids -> res.users; approval_matrix_direct_purchase -> approval.matrix.direct.purchase; approved_users -> res.users; last_approved -> res.users; order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.direct.purchase.line", "table_name": ""}
+{"text": "What foreign keys exist in apply.voucher?", "response": "The apply.voucher model has 4 relational fields: customer_id -> res.partner; voucher_ids -> customer.voucher; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "apply.voucher", "table_name": ""}
+{"text": "What are common use cases for access.rights.profile?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "access.rights.profile", "table_name": ""}
+{"text": "Show me the relational structure of setu.inventory.fsn.xyz.analysis.bi.report.", "response": "The setu.inventory.fsn.xyz.analysis.bi.report model has 6 relational fields: product_id -> product.product; product_category_id -> product.category; company_id -> res.company; wizard_id -> setu.inventory.fsn.xyz.analysis.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.fsn.xyz.analysis.bi.report", "table_name": ""}
+{"text": "What methods are available in pos.generate.efaktur.digunggung?", "response": "The pos.generate.efaktur.digunggung model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.generate.efaktur.digunggung", "table_name": ""}
+{"text": "Show me the fields of mrp.production.backorder.", "response": "The mrp.production.backorder model has 10 fields: mrp_production_ids, mrp_production_backorder_line_ids, show_backorder_lines, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, one2many: 1, boolean: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.production.backorder", "table_name": ""}
+{"text": "What are the available fields for list.category?", "response": "The list.category model has 10 fields: order_id, categ, product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 2, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "list.category", "table_name": ""}
+{"text": "Tell me about the saleblanket.saleblanket model.", "response": "The saleblanket.saleblanket model represents Sale Blanket in the ERP system. It contains 85 fields and is used to manage sale blanket data. Key fields include: name, partner_id, pricelist_id, payment_term_id, current_user, sale_order_count, expiry_date, creation_date, user_id, order_line_count, state, currency_id, state1, state2, state3, bo_state, bo_state_1, company_id, current_company, branch_id, days_left, analytic_tag_ids, order_line_ids, qty, delivery_qty, remaining_qty, qty_invoiced, reason, delivery_status, approving_matrix_bo_sale_id, is_bo_approval_matrix, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, approved_matrix_ids, amount_untaxed, amount_tax, amount_total, analytic_accounting, invoice_address, delivery_address, is_product_filled, is_active_company, max_line_sequence, report_template_id1, report_template_id, amount_to_text, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "saleblanket.saleblanket", "table_name": ""}
+{"text": "Which fields in mrp.unbuild are computed?", "response": "The mrp.unbuild model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.unbuild", "table_name": ""}
+{"text": "What are the technical details of base_import.tests.models.float?", "response": "The base_import.tests.models.float model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.float", "table_name": ""}
+{"text": "What models are connected to sale.adv.wizard.product.line?", "response": "The sale.adv.wizard.product.line model has 5 relational fields: sale_adv_wizard_id -> sale.adv.wizard; product_id -> product.product; uom_po_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.adv.wizard.product.line", "table_name": ""}
+{"text": "Describe the field structure of store.model.nodes.", "response": "The store.model.nodes model has 13 fields: model_id, node_option, attribute_name, attribute_string, button_type, is_smart_button, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, selection: 2, char: 3, boolean: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "store.model.nodes", "table_name": ""}
+{"text": "What business logic is in loyalty.wizard.reedem?", "response": "To use the loyalty.wizard.reedem model, you need to provide values for required fields: none. Readonly fields: customer, loyalty_point, loyalty_balance, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "loyalty.wizard.reedem", "table_name": ""}
+{"text": "List all fields in the mailing.contact.subscription model.", "response": "The mailing.contact.subscription model has 13 fields: contact_id, list_id, opt_out, unsubscription_date, message_bounce, is_blacklisted, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, boolean: 2, datetime: 4, integer: 2, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mailing.contact.subscription", "table_name": ""}
+{"text": "Describe the field structure of ctm.dynamic.balance.sheet.report.", "response": "The ctm.dynamic.balance.sheet.report model has 29 fields: company_id, journal_ids, account_ids, account_tag_ids, analytic_ids, analytic_tag_ids, display_account, target_move, date_from, date_to, analytic_group_ids, comparison, previous, report_currency_id, book, consolidate, comp_detail, filter_budget, budget, debit_credit, entities_comparison, all_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, many2many: 6, selection: 9, date: 2, integer: 2, boolean: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ctm.dynamic.balance.sheet.report", "table_name": ""}
+{"text": "What models are connected to sh.mrp.correct.qc.measurement?", "response": "The sh.mrp.correct.qc.measurement model has 6 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; mrp_id -> mrp.production; workorder_id -> mrp.workorder; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.mrp.correct.qc.measurement", "table_name": ""}
+{"text": "Can you explain the purpose of mail.thread?", "response": "The mail.thread model represents Email Thread in the ERP system. It contains 18 fields and is used to manage email thread data. Key fields include: message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.thread", "table_name": ""}
+{"text": "How to query action.data data?", "response": "To use the action.data 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "action.data", "table_name": ""}
+{"text": "How to create records in ir.actions.todo?", "response": "To use the ir.actions.todo model, you need to provide values for required fields: action_id, state. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.actions.todo", "table_name": ""}
+{"text": "What are the technical details of report.equip3_accounting_reports.cash_flow_statement?", "response": "The report.equip3_accounting_reports.cash_flow_statement model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_accounting_reports.cash_flow_statement", "table_name": ""}
+{"text": "Show me the relational structure of expiring.product.calendar.", "response": "The expiring.product.calendar model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "expiring.product.calendar", "table_name": ""}
+{"text": "What modules define ir.translation?", "response": "The ir.translation model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.translation", "table_name": ""}
+{"text": "Show me the relational structure of account.account.", "response": "The account.account model has 23 relational fields: move_line_ids -> account.move.line; parent_id -> account.account; child_ids -> account.account; currency_id -> res.currency; user_type_id -> account.account.type; tax_ids -> account.tax; company_id -> res.company; tag_ids -> account.account.tag; group_id -> account.group; root_id -> account.root; allowed_journal_ids -> account.journal; branch_id -> res.branch; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_ids, tag_ids, allowed_journal_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.account", "table_name": ""}
+{"text": "What does the gamification.challenge.line model represent?", "response": "The gamification.challenge.line model represents Gamification generic goal for challenge in the ERP system. It contains 16 fields and is used to manage gamification generic goal for challenge data. Key fields include: challenge_id, definition_id, sequence, target_goal, name, condition, definition_suffix, definition_monetary, definition_full_suffix, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "gamification.challenge.line", "table_name": ""}
+{"text": "Show me the relational structure of validate.account.move.", "response": "The validate.account.move model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "validate.account.move", "table_name": ""}
+{"text": "What operations can I perform on project.task.type.delete.wizard?", "response": "To use the project.task.type.delete.wizard model, you need to provide values for required fields: none. Readonly fields: tasks_count, stages_active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.task.type.delete.wizard", "table_name": ""}
+{"text": "What modules define sh.purchase.product.indent.wizard?", "response": "The sh.purchase.product.indent.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.product.indent.wizard", "table_name": ""}
+{"text": "What are common use cases for account.fiscal.position.tax?", "response": "To use the account.fiscal.position.tax model, you need to provide values for required fields: position_id, tax_src_id. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.fiscal.position.tax", "table_name": ""}
+{"text": "Describe the blanket.quotation model in Odoo.", "response": "The blanket.quotation model represents blanket.quotation in the ERP system. It contains 8 fields and is used to manage blanket.quotation data. Key fields include: wiz_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "blanket.quotation", "table_name": ""}
+{"text": "Which fields in account.asset.category are computed?", "response": "The account.asset.category model is defined in module: om_account_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.asset.category", "table_name": ""}
+{"text": "What fields does mrp.immediate.production have?", "response": "The mrp.immediate.production model has 10 fields: mo_ids, show_productions, immediate_production_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, boolean: 1, one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.immediate.production", "table_name": ""}
+{"text": "What modules define ks.message.wizard?", "response": "The ks.message.wizard model is defined in module: ks_sales_forecast. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks.message.wizard", "table_name": ""}
+{"text": "How is material.request.line.show.stock implemented technically?", "response": "The material.request.line.show.stock model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "material.request.line.show.stock", "table_name": ""}
+{"text": "How is website.robots implemented technically?", "response": "The website.robots model is defined in module: website. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.robots", "table_name": ""}
+{"text": "What operations can I perform on setu.inventory.fsn.xyz.analysis.bi.report?", "response": "To use the setu.inventory.fsn.xyz.analysis.bi.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.fsn.xyz.analysis.bi.report", "table_name": ""}
+{"text": "Show me the relational structure of ir.exports.line.", "response": "The ir.exports.line model has 3 relational fields: export_id -> ir.exports; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.exports.line", "table_name": ""}
+{"text": "What modules define report_excel_export_wizard?", "response": "The report_excel_export_wizard model is defined in module: report_excel. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report_excel_export_wizard", "table_name": ""}
+{"text": "How to query stock.quant data?", "response": "To use the stock.quant model, you need to provide values for required fields: product_id, location_id, reserved_quantity. Readonly fields: product_uom_id, company_id, location_id, lot_id, package_id, owner_id, quantity, reserved_quantity, available_quantity, in_date, tracking, use_expiration_date, value, currency_id, layer_value, state_check, forecast_incoming, forecast_outgoing, forecast_qty, filter_available_product_ids, product_category, expire_days, expire_days_count, expire_date, weight, is_update_value, purchase_value_in_lot, warehouse_id, inv_report_qty_available, inv_report_incoming_qty, inv_report_outgoing_qty, inv_report_virtual_available, inv_report_free_qty, inv_report_qty_ref, inv_report_ref, inv_report_qty_sec, inv_report_sec, inv_report_sales, inv_report_stock_movement, inv_report_default_code, inv_report_hide_sales, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.quant", "table_name": ""}
+{"text": "What is the purchase.order.wizard model?", "response": "The purchase.order.wizard model represents Purchase Order Wizard in the ERP system. It contains 17 fields and is used to manage purchase order wizard data. Key fields include: order_line, partner_id, date_planned, order_selection, sh_group_by_partner, sh_cancel_old_rfqs, sh_create_po, partner_ids, so_id, is_dropship, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order.wizard", "table_name": ""}
+{"text": "Describe the field structure of ir.actions.report.", "response": "The ir.actions.report model has 30 fields: name, type, binding_type, model, model_id, report_type, report_name, report_file, groups_id, multi, paperformat_id, print_report_name, attachment_use, attachment, encrypt, encrypt_type, manual_password, password_fields, password_sub_field, xml_id, help, binding_model_id, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 11, selection: 3, many2one: 7, many2many: 1, boolean: 3, html: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.actions.report", "table_name": ""}
+{"text": "What data can be stored in report.equip3_inventory_masterdata.report_product_tmpl_forecast?", "response": "The report.equip3_inventory_masterdata.report_product_tmpl_forecast model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_inventory_masterdata.report_product_tmpl_forecast", "table_name": ""}
+{"text": "What is the material.request.matrix.reject model?", "response": "The material.request.matrix.reject model represents Material Request Matrix Reject in the ERP system. It contains 8 fields and is used to manage material request matrix reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "material.request.matrix.reject", "table_name": ""}
+{"text": "What fields does account.move.template have?", "response": "The account.move.template model has 68 fields: name, date, ref, narration, state, posted_before, move_type, type_name, to_check, journal_id, suitable_journal_ids, company_id, company_currency_id, currency_id, line_ids, partner_id, payment_id, statement_line_id, amount_untaxed, amount_tax, amount_total, amount_residual, amount_untaxed_signed, amount_tax_signed, amount_total_signed, amount_residual_signed, amount_by_group, payment_state, reversed_entry_id, reversal_move_id, invoice_filter_type_domain, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 11, date: 3, text: 2, selection: 5, boolean: 7, many2one: 13, many2many: 3, one2many: 6, monetary: 8, binary: 1, integer: 6, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.move.template", "table_name": ""}
+{"text": "Describe the implementation of ai.model.selection.wizard.", "response": "The ai.model.selection.wizard model is defined in module: ai_chat_agent. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ai.model.selection.wizard", "table_name": ""}
+{"text": "What are common use cases for approval.matrix.accounting?", "response": "To use the approval.matrix.accounting model, you need to provide values for required fields: name, company_id, approval_matrix_line_ids. Readonly fields: company_id, filter_branch_ids, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.accounting", "table_name": ""}
+{"text": "What modules define nsfp.registration?", "response": "The nsfp.registration model is defined in module: equip3_accounting_efaktur. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "nsfp.registration", "table_name": ""}
+{"text": "Describe the hr.department model in Odoo.", "response": "The hr.department model represents Department in the ERP system. It contains 33 fields and is used to manage department data. Key fields include: name, complete_name, active, company_id, parent_id, child_ids, manager_id, member_ids, jobs_ids, note, color, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "hr.department", "table_name": ""}
+{"text": "How does cancel.credit.limit relate to other models?", "response": "The cancel.credit.limit model has 3 relational fields: limit_id -> limit.request; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "cancel.credit.limit", "table_name": ""}
+{"text": "How is account.loan.post used in the system?", "response": "The account.loan.post model represents Loan post in the ERP system. It contains 10 fields and is used to manage loan post data. Key fields include: loan_id, journal_id, account_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.loan.post", "table_name": ""}
+{"text": "How to query base_import.tests.models.m2o.required data?", "response": "To use the base_import.tests.models.m2o.required model, you need to provide values for required fields: value. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base_import.tests.models.m2o.required", "table_name": ""}
+{"text": "Tell me about the sale.report model.", "response": "The sale.report model represents Sales Analysis Report in the ERP system. It contains 45 fields and is used to manage sales analysis report data. Key fields include: name, date, product_id, product_uom, product_uom_qty, qty_delivered, qty_to_invoice, qty_invoiced, partner_id, company_id, user_id, price_total, price_subtotal, untaxed_amount_to_invoice, untaxed_amount_invoiced, product_tmpl_id, categ_id, nbr, pricelist_id, analytic_account_id, team_id, country_id, industry_id, commercial_partner_id, weight, volume, discount, discount_amount, campaign_id, medium_id, source_id, order_id, warehouse_id, website_id, branch_id, state, margin, city_id, state_id, untaxed_amount, total_amount, grand_total_order, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.report", "table_name": ""}
+{"text": "List all fields in the credit.limit.approval model.", "response": "The credit.limit.approval model has 19 fields: sequence, sequence2, user_ids, minimum_approver, status, time, feedback, approved, approval, user_approved_ids, credit_id, last_approved, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 5, many2many: 2, text: 2, char: 2, boolean: 1, many2one: 4, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "credit.limit.approval", "table_name": ""}
+{"text": "Which fields in ks_dashboard_ninja.item are computed?", "response": "The ks_dashboard_ninja.item model is defined in module: ks_dashboard_ninja. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks_dashboard_ninja.item", "table_name": ""}
+{"text": "Describe the implementation of utm.medium.", "response": "The utm.medium model is defined in module: utm. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "utm.medium", "table_name": ""}
+{"text": "How is receivable.opening.balance used in the system?", "response": "The receivable.opening.balance model represents receivable.opening.balance in the ERP system. It contains 14 fields and is used to manage receivable.opening.balance data. Key fields include: partner_opening_bal_id, customer_id, purchase_order, date, description, due_date, amount_due, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "receivable.opening.balance", "table_name": ""}
+{"text": "How is res.partner.title used in the system?", "response": "The res.partner.title model represents Partner Title in the ERP system. It contains 9 fields and is used to manage partner title data. Key fields include: name, shortcut, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.partner.title", "table_name": ""}
+{"text": "How to query pos.voucher data?", "response": "To use the pos.voucher model, you need to provide values for required fields: start_date, end_date. Readonly fields: user_id, pos_order_id, pos_order_line_id, use_history_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.voucher", "table_name": ""}
+{"text": "How to query mail.render.mixin data?", "response": "To use the mail.render.mixin model, you need to provide values for required fields: none. Readonly fields: lang, model_object_field, sub_object, sub_model_object_field, null_value, copyvalue, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.render.mixin", "table_name": ""}
+{"text": "How to query global.search.fields data?", "response": "To use the global.search.fields model, you need to provide values for required fields: ttype. Readonly fields: name, related_model_id, ttype, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "global.search.fields", "table_name": ""}
+{"text": "Show me the fields of report.sh_purchase_reports.sh_top_purchasing_product_doc.", "response": "The report.sh_purchase_reports.sh_top_purchasing_product_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_top_purchasing_product_doc", "table_name": ""}
+{"text": "How to query product.margin data?", "response": "To use the product.margin model, you need to provide values for required fields: invoice_state. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.margin", "table_name": ""}
+{"text": "What does the assign.pr.wizard model represent?", "response": "The assign.pr.wizard model represents Assign PR Wizard in the ERP system. It contains 9 fields and is used to manage assign pr wizard data. Key fields include: pr_ids, line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assign.pr.wizard", "table_name": ""}
+{"text": "Describe the pos.gift.card.use model in Odoo.", "response": "The pos.gift.card.use model represents Used to Store Gift Card Uses History. in the ERP system. It contains 12 fields and is used to manage used to store gift card uses history. data. Key fields include: card_id, customer_id, pos_order_id, order_date, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.gift.card.use", "table_name": ""}
+{"text": "List all fields in the report_excel_export_wizard model.", "response": "The report_excel_export_wizard model has 8 fields: multiple_export, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report_excel_export_wizard", "table_name": ""}
+{"text": "What models are connected to internal.matrix.reject?", "response": "The internal.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "internal.matrix.reject", "table_name": ""}
+{"text": "How is mr.internal_transfer_line used in the system?", "response": "The mr.internal_transfer_line model represents mr.internal_transfer_line in the ERP system. It contains 22 fields and is used to manage mr.internal_transfer_line data. Key fields include: mr_id, no, product_id, description, uom_id, source_location, source_warehouse_id, current_qty, virtual_available, qty_transfer, mr_ir_wizard, mr_line_id, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mr.internal_transfer_line", "table_name": ""}
+{"text": "How to create records in ir.qweb.field.selection?", "response": "To use the ir.qweb.field.selection model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.selection", "table_name": ""}
+{"text": "What are the relationships in acrux.chat.pop.message?", "response": "The acrux.chat.pop.message model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "acrux.chat.pop.message", "table_name": ""}
+{"text": "What does the approval.matrix.sale.order.lines model represent?", "response": "The approval.matrix.sale.order.lines model represents Approval Matrix Sale Order Lines in the ERP system. It contains 23 fields and is used to manage approval matrix sale order lines data. Key fields include: approval_matrix, order_id, user_name_ids, sequence, sequence2, minimum_approver, state_char, time_stamp, feedback, last_approved, approved, approved_users, signature, approval_type, approver_state, bo_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.sale.order.lines", "table_name": ""}
+{"text": "What modules define ms.query?", "response": "The ms.query model is defined in module: ms_query. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ms.query", "table_name": ""}
+{"text": "What operations can I perform on report.dynamic_accounts_report.day_book?", "response": "To use the report.dynamic_accounts_report.day_book model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.day_book", "table_name": ""}
+{"text": "How does sale.order.pricelist.wizard relate to other models?", "response": "The sale.order.pricelist.wizard model has 4 relational fields: shs_pricelist_id -> product.pricelist; pricelist_line -> sale.order.pricelist.wizard.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.pricelist.wizard", "table_name": ""}
+{"text": "Which fields in base_import.tests.models.char.readonly are computed?", "response": "The base_import.tests.models.char.readonly model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.char.readonly", "table_name": ""}
+{"text": "Describe the field structure of report.point_of_sale.report_invoice.", "response": "The report.point_of_sale.report_invoice model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.point_of_sale.report_invoice", "table_name": ""}
+{"text": "What fields does base.partner.merge.line have?", "response": "The base.partner.merge.line model has 10 fields: wizard_id, min_id, aggr_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 2, char: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.partner.merge.line", "table_name": ""}
+{"text": "How does mrp.workcenter relate to other models?", "response": "The mrp.workcenter model has 26 relational fields: routing_line_ids -> mrp.routing.workcenter; order_ids -> mrp.workorder; time_ids -> mrp.workcenter.productivity; costs_hour_account_id -> account.analytic.account; location_id -> stock.location; location_finished_id -> stock.location; location_rejected_id -> stock.location; location_byproduct_id -> stock.location; oh_time -> overhead.time; ov_material -> overhead.material; branch_id -> res.branch; create_uid -> res.users; alternative_workcenter_ids -> mrp.workcenter; company_id -> res.company; resource_id -> resource.resource; resource_calendar_id -> resource.calendar; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; write_uid -> res.users. Many2many fields: alternative_workcenter_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.workcenter", "table_name": ""}
+{"text": "What models are connected to sale.product.configurator?", "response": "The sale.product.configurator model has 8 relational fields: product_template_id -> product.template; pricelist_id -> product.pricelist; product_template_attribute_value_ids -> product.template.attribute.value; product_custom_attribute_value_ids -> product.attribute.custom.value; product_no_variant_attribute_value_ids -> product.template.attribute.value; warehouse_id -> stock.warehouse; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_template_attribute_value_ids, product_custom_attribute_value_ids, product_no_variant_attribute_value_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.product.configurator", "table_name": ""}
+{"text": "Show me the fields of ir.actions.actions.", "response": "The ir.actions.actions model has 14 fields: name, type, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, html: 1, many2one: 3, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.actions.actions", "table_name": ""}
+{"text": "How do I use the partner.blacklist.history model?", "response": "To use the partner.blacklist.history 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "partner.blacklist.history", "table_name": ""}
+{"text": "What does the free.product.lines model represent?", "response": "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. 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "free.product.lines", "table_name": ""}
+{"text": "Describe the many2many relations for sh.top.customers.xls.", "response": "The sh.top.customers.xls model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.top.customers.xls", "table_name": ""}
+{"text": "How does stock.production.lot relate to other models?", "response": "The stock.production.lot model has 26 relational fields: product_id -> product.product; product_uom_id -> uom.uom; quant_ids -> stock.quant; purchase_order_ids -> purchase.order; sale_order_ids -> sale.order; company_id -> res.company; assembly_production_finished_id -> assembly.production.record; assembly_production_byproduct_id -> assembly.production.record; assembly_production_rejected_id -> assembly.production.record; kitchen_production_finished_id -> kitchen.production.record; kitchen_production_byproduct_id -> kitchen.production.record; kitchen_production_rejected_id -> kitchen.production.record; finish_good_rework_byproduct_id -> finish.good.rework; finish_good_rework_finished_id -> finish.good.rework; finish_good_rework_rejected_id -> finish.good.rework; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_order_ids, sale_order_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.production.lot", "table_name": ""}
+{"text": "How to query base.module.update data?", "response": "To use the base.module.update model, you need to provide values for required fields: none. Readonly fields: updated, added, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.module.update", "table_name": ""}
+{"text": "What are the available fields for pos.gift.card.recharge?", "response": "The pos.gift.card.recharge model has 12 fields: card_id, customer_id, recharge_date, user_id, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.gift.card.recharge", "table_name": ""}
+{"text": "Describe the field structure of utm.tag.", "response": "The utm.tag model has 9 fields: name, color, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "utm.tag", "table_name": ""}
+{"text": "How to create records in sh.stock.move.pass.fail?", "response": "To use the sh.stock.move.pass.fail model, you need to provide values for required fields: none. Readonly fields: product_id, sh_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.stock.move.pass.fail", "table_name": ""}
+{"text": "How to create records in report.sh_sale_reports.sh_top_selling_product_doc?", "response": "To use the report.sh_sale_reports.sh_top_selling_product_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_top_selling_product_doc", "table_name": ""}
+{"text": "Tell me about the sh.purchase.report.representative.wizard model.", "response": "The sh.purchase.report.representative.wizard model represents sh purchase report representative wizard model in the ERP system. It contains 13 fields and is used to manage sh purchase report representative wizard model data. Key fields include: date_start, date_end, user_ids, state, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.purchase.report.representative.wizard", "table_name": ""}
+{"text": "Can you explain the purpose of hr.employee.public?", "response": "The hr.employee.public model represents Public Employee in the ERP system. It contains 42 fields and is used to manage public employee data. Key fields include: create_date, name, active, department_id, job_id, job_title, company_id, address_id, mobile_phone, work_phone, work_email, work_location, user_id, resource_id, resource_calendar_id, tz, color, child_ids, image_1920, image_1024, image_512, image_256, image_128, parent_id, coach_id, user_partner_id, subordinate_ids, hr_presence_state, last_activity, last_activity_time, hr_icon_display, goal_ids, badge_ids, has_badges, direct_badge_ids, child_all_count, id, display_name, create_uid, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "hr.employee.public", "table_name": ""}
+{"text": "How do I use the customer.deposit model?", "response": "To use the customer.deposit model, you need to provide values for required fields: none. Readonly fields: name, return_deposit, filter_deposit_account_ids, deposit_move_id, is_show_cancel, invoice_count, reconcile_count, approval_matrix_id, is_customer_deposit_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, deposit_history, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "customer.deposit", "table_name": ""}
+{"text": "What are the relationships in repair.order?", "response": "The repair.order model has 29 relational fields: product_id -> product.product; product_uom -> uom.uom; product_uom_category_id -> uom.category; partner_id -> res.partner; address_id -> res.partner; default_address_id -> res.partner; location_id -> stock.location; lot_id -> stock.production.lot; operations -> repair.line; pricelist_id -> product.pricelist; currency_id -> res.currency; partner_invoice_id -> res.partner; invoice_id -> account.move; move_id -> stock.move; fees_lines -> repair.fee; user_id -> res.users; company_id -> res.company; tag_ids -> repair.tags; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "repair.order", "table_name": ""}
+{"text": "What fields does res.currency.tax have?", "response": "The res.currency.tax model has 13 fields: name, rate, conversion, mr_rate, currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, float: 3, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.currency.tax", "table_name": ""}
+{"text": "How to create records in pos.loyalty.history.update.point?", "response": "To use the pos.loyalty.history.update.point model, you need to provide values for required fields: type_apply. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.loyalty.history.update.point", "table_name": ""}
+{"text": "Describe the field structure of report.sh_sale_reports.sh_sale_invoice_summary_doc.", "response": "The report.sh_sale_reports.sh_sale_invoice_summary_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_sale_reports.sh_sale_invoice_summary_doc", "table_name": ""}
+{"text": "How does restaurant.printer relate to other models?", "response": "The restaurant.printer model has 3 relational fields: product_categories_ids -> pos.category; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_categories_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "restaurant.printer", "table_name": ""}
+{"text": "What modules define update.customer.segment?", "response": "The update.customer.segment model is defined in module: setu_rfm_analysis. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "update.customer.segment", "table_name": ""}
+{"text": "Can you explain the purpose of report.sh_purchase_reports.sh_representative_report_doc?", "response": "The report.sh_purchase_reports.sh_representative_report_doc model represents purchase person report abstract model in the ERP system. It contains 3 fields and is used to manage purchase person report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_representative_report_doc", "table_name": ""}
+{"text": "How to query sh.mrp.correct.qc.measurement data?", "response": "To use the sh.mrp.correct.qc.measurement model, you need to provide values for required fields: none. Readonly fields: sh_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.mrp.correct.qc.measurement", "table_name": ""}
+{"text": "How do I use the global.search model?", "response": "To use the global.search model, you need to provide values for required fields: model_id, main_field_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "global.search", "table_name": ""}
+{"text": "Show me the relational structure of setu.rfm.segment.", "response": "The setu.rfm.segment model has 7 relational fields: rfm_score_ids -> setu.rfm.score; partner_ids -> res.partner; order_ids -> sale.order; mailing_ids -> mailing.mailing; team_customer_segment_ids -> team.customer.segment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.rfm.segment", "table_name": ""}
+{"text": "Describe the pos.loyalty.category model in Odoo.", "response": "The pos.loyalty.category model represents Member loyalty type in the ERP system. It contains 20 fields and is used to manage member loyalty type data. Key fields include: name, code, active, from_point, to_point, coefficient, member_card, card_template_barcode, card_template_qrcode, card_template_barcode_name, card_template_qrcode_name, member_card_preview, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.loyalty.category", "table_name": ""}
+{"text": "What are the relationships in payment.link.wizard?", "response": "The payment.link.wizard model has 5 relational fields: currency_id -> res.currency; partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "payment.link.wizard", "table_name": ""}
+{"text": "How to create records in account.vendor.deposit.reconcile?", "response": "To use the account.vendor.deposit.reconcile 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.vendor.deposit.reconcile", "table_name": ""}
+{"text": "How to create records in export.efaktur?", "response": "To use the export.efaktur model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "export.efaktur", "table_name": ""}
+{"text": "What modules define coupon.reward?", "response": "The coupon.reward model is defined in module: coupon. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "coupon.reward", "table_name": ""}
+{"text": "What business logic is in stock.return.picking?", "response": "To use the stock.return.picking model, you need to provide values for required fields: none. Readonly fields: move_dest_exists, company_id, is_return_possible, picking_type_code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.return.picking", "table_name": ""}
+{"text": "Describe the many2many relations for sh.push.notification.", "response": "The sh.push.notification model has 3 relational fields: user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.push.notification", "table_name": ""}
+{"text": "What are the available fields for hr.employee?", "response": "The hr.employee model has 119 fields: name, user_id, user_partner_id, active, company_id, address_home_id, is_address_home_a_company, private_email, country_id, gender, marital, spouse_complete_name, spouse_birthdate, children, place_of_birth, country_of_birth, birthday, ssnid, sinid, identification_id, passport_id, bank_account_id, permit_no, visa_no, visa_expire, additional_note, certificate, study_field, study_school, emergency_contact, emergency_phone, km_home_work, image_1920, phone, child_ids, category_ids, notes, color, barcode, pin, departure_reason, departure_description, departure_date, message_main_attachment_id, subordinate_ids, timesheet_cost, currency_id, allow_discount, allow_qty, allow_price, allow_remove_line, allow_minus, allow_payment, allow_customer, allow_add_order, allow_remove_order, allow_add_product, allow_payment_zero, allow_offline_mode, pos_use_otp, pos_otp_phone, last_sent_otp, image_1024, image_512, image_256, image_128, 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, website_message_ids, message_has_sms_error, department_id, job_id, job_title, address_id, work_phone, mobile_phone, work_email, work_location, resource_id, resource_calendar_id, parent_id, coach_id, tz, hr_presence_state, last_activity, last_activity_time, hr_icon_display, goal_ids, badge_ids, has_badges, direct_badge_ids, child_all_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 29, many2one: 20, boolean: 21, selection: 9, date: 7, integer: 9, text: 3, binary: 5, one2many: 9, many2many: 3, monetary: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "hr.employee", "table_name": ""}
+{"text": "What operations can I perform on overhead.material?", "response": "To use the overhead.material model, you need to provide values for required fields: none. Readonly fields: product_price, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "overhead.material", "table_name": ""}
+{"text": "Describe the many2many relations for payment.icon.", "response": "The payment.icon model has 3 relational fields: acquirer_ids -> payment.acquirer; create_uid -> res.users; write_uid -> res.users. Many2many fields: acquirer_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "payment.icon", "table_name": ""}
+{"text": "What are the technical details of report.sh_sale_reports.sh_sale_product_indent_doc?", "response": "The report.sh_sale_reports.sh_sale_product_indent_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_sale_product_indent_doc", "table_name": ""}
+{"text": "Can you explain the purpose of report.equip3_crm_tracking.crm_sales_tracking_visit_report?", "response": "The report.equip3_crm_tracking.crm_sales_tracking_visit_report model represents Salesperson Tracking History Report in the ERP system. It contains 3 fields and is used to manage salesperson tracking history report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_crm_tracking.crm_sales_tracking_visit_report", "table_name": ""}
+{"text": "Tell me about the full.inv.adjustment.import model.", "response": "The full.inv.adjustment.import model represents Full Inv Adjustment Import in the ERP system. It contains 13 fields and is used to manage full inv adjustment import data. Key fields include: import_type, import_file, import_name, export_file, export_name, is_export, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "full.inv.adjustment.import", "table_name": ""}
+{"text": "What are the relationships in order.picking.lines?", "response": "The order.picking.lines model has 5 relational fields: order_id -> order.picking; product_id -> product.product; picking_id -> stock.picking; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "order.picking.lines", "table_name": ""}
+{"text": "Describe the many2many relations for sh.sale.analysis.wizard.", "response": "The sh.sale.analysis.wizard model has 7 relational fields: sh_product_ids -> product.product; company_ids -> res.company; sh_partner_ids -> res.partner; company_id -> res.company; sale_analysis_dic -> user.order.dic; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_product_ids, company_ids, sh_partner_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.sale.analysis.wizard", "table_name": ""}
+{"text": "What does the budget.carry.over.lines model represent?", "response": "The budget.carry.over.lines model represents Budget Carry Over Lines in the ERP system. It contains 27 fields and is used to manage budget carry over lines data. Key fields include: budget_carry_over_id, date_from, date_to, analytic_account_id, paid_date, parent_analytic_account_id, general_budget_id, reserve_amount, currency_id, account_tag_ids, filtered_budget_line, company_id, practical_amount, theoritical_amount, planned_amount, practical_budget_amount, percentage, is_above_budget, carry_over_amount, final_planned_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "budget.carry.over.lines", "table_name": ""}
+{"text": "Can you explain the purpose of website.visitor?", "response": "The website.visitor model represents Website Visitor in the ERP system. It contains 36 fields and is used to manage website visitor data. Key fields include: name, active, website_id, partner_id, partner_image, country_id, country_flag, lang_id, timezone, email, mobile, visit_count, website_track_ids, visitor_page_count, page_ids, page_count, last_visited_page_id, create_date, last_connection_datetime, time_since_last_action, is_connected, livechat_operator_id, livechat_operator_name, mail_channel_ids, session_count, lead_ids, lead_count, visitor_product_count, product_ids, product_count, id, display_name, create_uid, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "website.visitor", "table_name": ""}
+{"text": "What business logic is in account.tax.map.purchase.line?", "response": "To use the account.tax.map.purchase.line model, you need to provide values for required fields: map_id, child_company_id. Readonly fields: company_id, target_company, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.tax.map.purchase.line", "table_name": ""}
+{"text": "How is report.sh_sale_reports.sh_salesperson_report_doc implemented technically?", "response": "The report.sh_sale_reports.sh_salesperson_report_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_salesperson_report_doc", "table_name": ""}
+{"text": "How to query report.sh_inventory_mrp_qc.mrp_quality_alert_doc data?", "response": "To use the report.sh_inventory_mrp_qc.mrp_quality_alert_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_inventory_mrp_qc.mrp_quality_alert_doc", "table_name": ""}
+{"text": "How do I use the pos.generate.efaktur model?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.generate.efaktur", "table_name": ""}
+{"text": "How to create records in report.base.report_irmodulereference?", "response": "To use the report.base.report_irmodulereference model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.base.report_irmodulereference", "table_name": ""}
+{"text": "Describe the many2many relations for payment.link.wizard.", "response": "The payment.link.wizard model has 5 relational fields: currency_id -> res.currency; partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "payment.link.wizard", "table_name": ""}
+{"text": "What are the technical details of account.partner.ledger?", "response": "The account.partner.ledger model is defined in module: dynamic_accounts_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.partner.ledger", "table_name": ""}
+{"text": "List all fields in the ir.autovacuum model.", "response": "The ir.autovacuum model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.autovacuum", "table_name": ""}
+{"text": "Show me the relational structure of queue.job.dashboard.", "response": "The queue.job.dashboard model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "queue.job.dashboard", "table_name": ""}
+{"text": "Describe the setu.inventory.age.bi.report model in Odoo.", "response": "The setu.inventory.age.bi.report model represents setu.inventory.age.bi.report in the ERP system. It contains 19 fields and is used to manage setu.inventory.age.bi.report data. Key fields include: product_id, product_category_id, company_id, current_stock, current_stock_value, oldest_date, days_old, oldest_stock_qty, oldest_stock_value, stock_qty_ratio, stock_value_ratio, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "setu.inventory.age.bi.report", "table_name": ""}
+{"text": "How do I use the calendar.event model?", "response": "To use the calendar.event model, you need to provide values for required fields: name, start, stop, privacy, show_as. Readonly fields: attendee_status, display_time, res_model, partner_id, is_highlighted, team_id, state_1, state_2, opportunity_name, res_name, res_loc, meeting_salesperson_ids, is_hide_salesperson, dummy_boolean, reasons_reschedule, cancelled_reasons, meeting_overview, stage_id, meeting_count, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "calendar.event", "table_name": ""}
+{"text": "What are the available fields for utm.mixin?", "response": "The utm.mixin model has 6 fields: campaign_id, source_id, medium_id, id, display_name, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "utm.mixin", "table_name": ""}
+{"text": "How to create records in pos.loyalty.reward.product?", "response": "To use the pos.loyalty.reward.product model, you need to provide values for required fields: none. Readonly fields: default_code, list_price, uom_id, sh_qr_code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.loyalty.reward.product", "table_name": ""}
+{"text": "Describe the implementation of account.analytic.new.", "response": "The account.analytic.new model is defined in module: equip3_accounting_analytical. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.analytic.new", "table_name": ""}
+{"text": "List all fields in the ir.qweb model.", "response": "The ir.qweb model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb", "table_name": ""}
+{"text": "Can you explain the purpose of stock.scrap.approval.matrix.line?", "response": "The stock.scrap.approval.matrix.line model represents Stock Scrap Approval Matrix Line in the ERP system. It contains 34 fields and is used to manage stock scrap approval matrix line data. Key fields include: sequence, user_ids, minimum_approver, sc_approval_matrix, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, scap_request_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.scrap.approval.matrix.line", "table_name": ""}
+{"text": "Show me the fields of report.equip3_accounting_reports.customer_statement.", "response": "The report.equip3_accounting_reports.customer_statement model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.customer_statement", "table_name": ""}
+{"text": "What data can be stored in lost.product?", "response": "The lost.product model has 9 fields: name, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "lost.product", "table_name": ""}
+{"text": "Describe the field structure of return.inter.transfer.company.", "response": "The return.inter.transfer.company model has 24 fields: sale_id, sale_count, invoice_count, bill_count, invoice_id, purchase_id, purchase_count, internal_id, internal_count, name, state, from_warehouse, currency_id, to_warehouse, pricelist_id, product_lines, product_return_moves, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, integer: 6, many2many: 1, char: 2, selection: 1, one2many: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "return.inter.transfer.company", "table_name": ""}
+{"text": "How to query setu.inventory.xyz.analysis.report data?", "response": "To use the setu.inventory.xyz.analysis.report model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.xyz.analysis.report", "table_name": ""}
+{"text": "What foreign keys exist in report_excel_export_gen?", "response": "The report_excel_export_gen model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report_excel_export_gen", "table_name": ""}
+{"text": "Can you explain the purpose of report.sh_purchase_reports.sh_tv_top_vendors_doc?", "response": "The report.sh_purchase_reports.sh_tv_top_vendors_doc model represents top Vendors report abstract model in the ERP system. It contains 3 fields and is used to manage top vendors report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_tv_top_vendors_doc", "table_name": ""}
+{"text": "What are common use cases for sh.commision.detail?", "response": "To use the sh.commision.detail 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.commision.detail", "table_name": ""}
+{"text": "What is the sh.qc.point model?", "response": "The sh.qc.point model represents Quality Point in the ERP system. It contains 50 fields and is used to manage quality point data. Key fields include: product_id, type_id, logged_user, company_id, name, operation, team, sh_message, sh_instruction, type, sh_norm, sh_unit_to, sh_unit_from, sh_signature, is_mandatory, number_of_test, product_ids, operation_ids, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.qc.point", "table_name": ""}
+{"text": "What are the technical details of report.extra.content?", "response": "The report.extra.content model is defined in module: general_template. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.extra.content", "table_name": ""}
+{"text": "Describe the many2many relations for dev.purchase.team.", "response": "The dev.purchase.team model has 6 relational fields: user_id -> res.users; member_ids -> res.users; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "dev.purchase.team", "table_name": ""}
+{"text": "Show me the relational structure of vendor.deposit.amount.wizard.", "response": "The vendor.deposit.amount.wizard model has 3 relational fields: currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "vendor.deposit.amount.wizard", "table_name": ""}
+{"text": "What methods are available in account.loan.generate.wizard?", "response": "The account.loan.generate.wizard model is defined in module: account_loan. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.loan.generate.wizard", "table_name": ""}
+{"text": "What methods are available in ks_dashboard_ninja.ks_grid_per_company?", "response": "The ks_dashboard_ninja.ks_grid_per_company model is defined in module: ks_dashboard_ninja. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks_dashboard_ninja.ks_grid_per_company", "table_name": ""}
+{"text": "What is the sale.margin.report.wizard model?", "response": "The sale.margin.report.wizard model represents sale margin report wizard model in the ERP system. It contains 12 fields and is used to manage sale margin report wizard model data. Key fields include: partner_ids, start_date, end_date, company_ids, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.margin.report.wizard", "table_name": ""}
+{"text": "What modules define invoice.deposit.line.reconcile?", "response": "The invoice.deposit.line.reconcile model is defined in module: equip3_accounting_deposit. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.deposit.line.reconcile", "table_name": ""}
+{"text": "What operations can I perform on approval.matrix.direct.purchase?", "response": "To use the approval.matrix.direct.purchase model, you need to provide values for required fields: name, company_id, branch_id, minimum_amt, maximum_amt. Readonly fields: company_id, is_good_services_order, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.direct.purchase", "table_name": ""}
+{"text": "How does purchase.excel.extended relate to other models?", "response": "The purchase.excel.extended model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.excel.extended", "table_name": ""}
+{"text": "What modules define remove.action?", "response": "The remove.action model is defined in module: simplify_access_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "remove.action", "table_name": ""}
+{"text": "What foreign keys exist in partner.blacklist.history?", "response": "The partner.blacklist.history model has 4 relational fields: user_id -> res.users; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "partner.blacklist.history", "table_name": ""}
+{"text": "Describe the implementation of web_editor.converter.test.", "response": "The web_editor.converter.test model is defined in module: web_editor. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "web_editor.converter.test", "table_name": ""}
+{"text": "Which fields in vendor.deposit.report are computed?", "response": "The vendor.deposit.report model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "vendor.deposit.report", "table_name": ""}
+{"text": "What methods are available in invoice.payment.report.xls?", "response": "The invoice.payment.report.xls model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.payment.report.xls", "table_name": ""}
+{"text": "What business logic is in utm.tag?", "response": "To use the utm.tag 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "utm.tag", "table_name": ""}
+{"text": "Which fields in ir.actions.report are computed?", "response": "The ir.actions.report model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.actions.report", "table_name": ""}
+{"text": "What does the utm.medium model represent?", "response": "The utm.medium model represents UTM Medium in the ERP system. It contains 9 fields and is used to manage utm medium data. Key fields include: name, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "utm.medium", "table_name": ""}
+{"text": "Which fields in product.ratio.line are computed?", "response": "The product.ratio.line model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.ratio.line", "table_name": ""}
+{"text": "Tell me about the account.reconciliation.widget model.", "response": "The account.reconciliation.widget model represents Account Reconciliation widget in the ERP system. It contains 3 fields and is used to manage account reconciliation widget data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.reconciliation.widget", "table_name": ""}
+{"text": "How is account.analytic.group used in the system?", "response": "The account.analytic.group model represents Analytic Categories in the ERP system. It contains 42 fields and is used to manage analytic categories data. Key fields include: parent_path, children_ids, complete_name, name, description, parent_id, company_id, analytic_account_ids, analyticnew_ids, branch_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.analytic.group", "table_name": ""}
+{"text": "How do I use the cluster.warehouse.line model?", "response": "To use the cluster.warehouse.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cluster.warehouse.line", "table_name": ""}
+{"text": "Describe the pos.payment.method model in Odoo.", "response": "The pos.payment.method model represents Point of Sale Payment Methods in the ERP system. It contains 54 fields and is used to manage point of sale payment methods data. Key fields include: name, receivable_account_id, is_cash_count, cash_journal_id, split_transactions, open_session_ids, config_ids, company_id, use_payment_terminal, hide_use_payment_terminal, active, apply_charges, fees_amount, fees_type, fees_product_id, optional, shortcut_key, jr_use_for, fullfill_amount, shortcut_keyboard, cheque_bank_information, discount, discount_type, discount_amount, discount_product_id, is_bank, generate_invoice, invoice_partner_id, able_use_card, is_mdr, is_mdr_discount, mdr_paid_by, mdr_intermediary_account_id, mdr_ids, is_receivables, account_journal_id, is_receivables_show, is_deposit_payment, is_edc_bca, is_edc_manual_input, edc_port, trans_type, trans_type_code, is_payment_edc, payment_edc_url, installment_tenor_ids, installment_plan, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.payment.method", "table_name": ""}
+{"text": "Which fields in material.request.show.stock are computed?", "response": "The material.request.show.stock model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "material.request.show.stock", "table_name": ""}
+{"text": "Can you explain the purpose of approval.matrix.purchase.request.line?", "response": "The approval.matrix.purchase.request.line model represents Approval Matrix Purchase Request Line in the ERP system. It contains 20 fields and is used to manage approval matrix purchase request line data. Key fields include: sequence, user_ids, minimum_approver, approval_matrix_purchase_request, request_id, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, approver_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.purchase.request.line", "table_name": ""}
+{"text": "What is the ir.qweb.field.qweb model?", "response": "The ir.qweb.field.qweb model represents Qweb Field qweb in the ERP system. It contains 3 fields and is used to manage qweb field qweb data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb.field.qweb", "table_name": ""}
+{"text": "What operations can I perform on report.accounting_pdf_reports.report_trialbalance?", "response": "To use the report.accounting_pdf_reports.report_trialbalance model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.accounting_pdf_reports.report_trialbalance", "table_name": ""}
+{"text": "What models are connected to replace.product.wizard?", "response": "The replace.product.wizard model has 4 relational fields: product_id -> product.product; replace_product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "replace.product.wizard", "table_name": ""}
+{"text": "What modules define report.equip3_accounting_reports.journal_entry_report?", "response": "The report.equip3_accounting_reports.journal_entry_report model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_accounting_reports.journal_entry_report", "table_name": ""}
+{"text": "What business logic is in purchase.agreement.line?", "response": "To use the purchase.agreement.line model, you need to provide values for required fields: dest_warehouse_id, sh_product_id. Readonly fields: sh_ordered_qty, company_id, sequence2, analytic_accounting, product_uom_category_id, date_order, picking_type_id, set_single_delivery_date, set_single_delivery_destination, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.agreement.line", "table_name": ""}
+{"text": "How do I use the crm.lead.type model?", "response": "To use the crm.lead.type model, you need to provide values for required fields: description. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.lead.type", "table_name": ""}
+{"text": "What are the technical details of pos.payment?", "response": "The pos.payment model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.payment", "table_name": ""}
+{"text": "Describe the many2many relations for account.cashbox.wizard.", "response": "The account.cashbox.wizard model has 5 relational fields: pos_session_id -> pos.session; line_ids -> account.cashbox.wizard.line; line_bank_ids -> account.cashbox.wizard.bank.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.cashbox.wizard", "table_name": ""}
+{"text": "What operations can I perform on purchase.bill.union?", "response": "To use the purchase.bill.union model, you need to provide values for required fields: none. Readonly fields: name, reference, partner_id, date, amount, currency_id, company_id, vendor_bill_id, purchase_order_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.bill.union", "table_name": ""}
+{"text": "Show me the fields of report.equip3_kitchen_reports.report_kitchen_production.", "response": "The report.equip3_kitchen_reports.report_kitchen_production model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_kitchen_reports.report_kitchen_production", "table_name": ""}
+{"text": "What are common use cases for purchase.agreement.line?", "response": "To use the purchase.agreement.line model, you need to provide values for required fields: dest_warehouse_id, sh_product_id. Readonly fields: sh_ordered_qty, company_id, sequence2, analytic_accounting, product_uom_category_id, date_order, picking_type_id, set_single_delivery_date, set_single_delivery_destination, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.agreement.line", "table_name": ""}
+{"text": "How to query queue.jobs.kill data?", "response": "To use the queue.jobs.kill 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "queue.jobs.kill", "table_name": ""}
+{"text": "What are the relationships in payment.voucher.line?", "response": "The payment.voucher.line model has 5 relational fields: invoice_number_id -> account.move; currency_id -> res.currency; voucher_id -> payment.voucher; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "payment.voucher.line", "table_name": ""}
+{"text": "How does report.stock.quantity relate to other models?", "response": "The report.stock.quantity model has 5 relational fields: product_tmpl_id -> product.template; product_id -> product.product; move_ids -> stock.move; company_id -> res.company; warehouse_id -> stock.warehouse. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.stock.quantity", "table_name": ""}
+{"text": "What does the setu.inventory.turnover.analysis.bi.report model represent?", "response": "The setu.inventory.turnover.analysis.bi.report model represents setu.inventory.turnover.analysis.bi.report in the ERP system. It contains 17 fields and is used to manage setu.inventory.turnover.analysis.bi.report data. Key fields include: product_id, product_category_id, warehouse_id, company_id, opening_stock, closing_stock, average_stock, sales, turnover_ratio, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "setu.inventory.turnover.analysis.bi.report", "table_name": ""}
+{"text": "What are common use cases for export.partner.csv?", "response": "To use the export.partner.csv model, you need to provide values for required fields: none. Readonly fields: product_id_attachment_id, product_id_csv_created, 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, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "export.partner.csv", "table_name": ""}
+{"text": "Which fields in setu.inventory.turnover.analysis.bi.report are computed?", "response": "The setu.inventory.turnover.analysis.bi.report model is defined in module: setu_advance_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "setu.inventory.turnover.analysis.bi.report", "table_name": ""}
+{"text": "What are the relationships in ks.sales.forecast.report?", "response": "The ks.sales.forecast.report model has 3 relational fields: binding_model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks.sales.forecast.report", "table_name": ""}
+{"text": "How is report.equip3_pos_report.report_pos_payment used in the system?", "response": "The report.equip3_pos_report.report_pos_payment model represents POS Payment Report in the ERP system. It contains 3 fields and is used to manage pos payment report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_pos_report.report_pos_payment", "table_name": ""}
+{"text": "What are the relationships in mrp.bom.operation?", "response": "The mrp.bom.operation model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.bom.operation", "table_name": ""}
+{"text": "What modules define multiple.rfq?", "response": "The multiple.rfq model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "multiple.rfq", "table_name": ""}
+{"text": "Show me the fields of purchase.request.warning.", "response": "The purchase.request.warning model has 9 fields: name, warning_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: html: 1, one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.request.warning", "table_name": ""}
+{"text": "Tell me about the hr.plan.wizard model.", "response": "The hr.plan.wizard model represents Plan Wizard in the ERP system. It contains 9 fields and is used to manage plan wizard data. Key fields include: plan_id, employee_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "hr.plan.wizard", "table_name": ""}
+{"text": "What methods are available in ir.qweb.field.integer?", "response": "The ir.qweb.field.integer model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.qweb.field.integer", "table_name": ""}
+{"text": "Describe the many2many relations for base.module.update.", "response": "The base.module.update model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.module.update", "table_name": ""}
+{"text": "What foreign keys exist in approval.matrix.accounting?", "response": "The approval.matrix.accounting model has 18 relational fields: company_id -> res.company; branch_id -> res.branch; filter_branch_ids -> res.branch; approval_matrix_line_ids -> approval.matrix.accounting.lines; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_branch_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.accounting", "table_name": ""}
+{"text": "Describe the account.bank.statement.line model in Odoo.", "response": "The account.bank.statement.line model represents Bank Statement Line in the ERP system. It contains 362 fields and is used to manage bank statement line data. Key fields include: move_id, statement_id, sequence, account_number, partner_name, transaction_type, payment_ref, amount, amount_currency, foreign_currency_id, amount_residual, currency_id, partner_id, payment_ids, is_reconciled, state, country_code, move_name, unique_import_id, branch_id, transaction_date, pos_branch_id, voucher_id, pos_session_id, pos_cash_type, pos_statement_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, highest_name, ref, move_type, type_name, suitable_journal_ids, company_id, user_id, is_move_sent, payment_state, invoice_user_id, invoice_origin, invoice_source_email, preferred_payment_method_id, debit_origin_id, debit_note_ids, debit_note_count, edi_document_ids, edi_state, edi_error_count, edi_web_services_to_process, edi_show_cancel_button, edi_show_abandon_cancel_button, edi_error_message, edi_blocking_level, loan_line_id, loan_id, attn, signature, journal_bank_id, payment_proof, tax_payment_date, payment_fields_boolean, ppn, pph, tax_paid_status, file_name, payment_date, tax_payment_move_id, tax_pay_seprately_amount, is_edit_data, name, asset_depreciation_ids, transaction_ids, authorized_transaction_ids, purchase_vendor_bill_id, purchase_id, sh_invoice_recurring_order_id, period_id, fiscal_year, stock_move_id, stock_valuation_layer_ids, auto_reverse, auto_reverse_date, auto_reverse_journal_id, auto_reverse_date_mode, auto_reversal_entry_date, auto_reversed, is_prepayment, to_delete_from_svl, pos_order_ids, team_id, partner_shipping_id, is_consignment, consignment_start_date, consignment_end_date, consignment_pos_ids, l10n_id_tax_number, l10n_id_attachment_id, l10n_id_csv_created, l10n_id_need_kode_transaksi, landed_costs_ids, landed_costs_visible, website_id, is_line, discount_method, discount_amount, discount_type, discount_amt, amount_untaxed, discount_amt_line, discount_account_id, discount_amount_line, warranty_invoice, warranty_reg_id, related_project_id, show_intrest, interest, check_date, check_month, repair_ids, sh_invoice_barcode_mobile, sh_invoice_bm_is_cont_scan, target_commission_id, commission_count, apply_manual_currency_exchange, active_manual_currency_rate, down_payment_amount, total_down_payment_amount, is_down_payment, down_payment_purchase_id, report_template_id1, report_template_id, amount_to_text, timesheet_ids, timesheet_count, approval_matrix_id, is_invoice_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state1, state2, is_register_payment_done, analytic_group_ids, invoice_origin_id, invoice_origin_date, reason, ref_no, request_partner_id, is_fiscal_book_exclude, received_date, visible_received_date, to_approve_state_payment_count, show_name_warning, date, posted_before, to_check, journal_id, company_currency_id, line_ids, commercial_partner_id, partner_bank_id, payment_reference, payment_id, statement_line_id, amount_tax, amount_tax2, subtotal_amount, amount_total, amount_untaxed_signed, amount_tax_signed, amount_total_signed, amount_residual_signed, amount_by_group, tax_cash_basis_rec_id, tax_cash_basis_move_id, auto_post, reversed_entry_id, reversal_move_id, fiscal_position_id, invoice_date, invoice_date_due, invoice_payment_term_id, invoice_line_ids, invoice_incoterm_id, display_qr_code, qr_code_method, invoice_outstanding_credits_debits_widget, invoice_has_outstanding, invoice_payments_widget, invoice_vendor_bill_id, invoice_partner_display_name, invoice_cash_rounding_id, invoice_filter_type_domain, bank_partner_id, invoice_has_matching_suspense_amount, tax_lock_date_message, has_reconciled_entries, show_reset_to_draft_button, restrict_mode_hash_table, secure_sequence_number, inalterable_hash, string_to_hash, mr_show_analytic_account, journal_entries_template, analytic_tag_dynamic, credit_note_expiry_date, expiry_date, approvers_ids, approved_user_ids, internal_tf_id, reversal_avail, date_id, is_record_created, is_merge, is_merge_to, new_invoice_id, count_merged_invoice, is_button_update_invisible, narration, multi_discount, is_intercompany_transaction, account_asset_id, customer_deposit_ids, vendor_deposit_ids, status_code, nomor_seri, ebupot_id, code, check, check_invisible, total_tax_ppn, total_inv_ppn, subtotal_inv_ppn, tax_number_bupot, kode_dokumen, kode_seri, nomor_seri_bupot, check_invisible_ebupot, ebupot_template, l10n_id_replace_invoice_id, l10n_id_kode_transaksi, is_upload_djp, is_upload_djp_cn, pajak_express_id, approval_url, efaktur_url, nomor_dokumen_pendukung, hide_button_upload, hide_button_upload_cn, tipe_pembayaran, keterangan_tambahan, uang_muka, uang_muka_ppn, uang_muka_ppnbm, signature_country_id, signature_city_id, nomor_seri_domain, current_rate, is_company_curr, current_inverse_rate, inverse_rate_visible, tax_rate, taxes_base_price, sales_times_tax_rate, tax_applies_on, manual_currency_exchange_inverse_rate, manual_currency_exchange_rate, currency_revaluation_id, children_ids, currency_revaluation_ref_id, currency_revaluation_count, pettycash_id, is_petty_cash_voucher, sale_order_reference_id, filter_sale_order_reference_ids, exchange_id, exchange_stage, exchange_date, exchange_status, assembly_id, stock_scrap_id, kitchen_id, purchase_order_id, swo, swo_ids, amount_swo, is_services_orders, finish_good_rework_id, sale_order_ids, filter_sale_order_ids, purchase_order_ids, filter_purchase_order_ids, picking_ids, filter_picking_ids, sale_order_ids_boolean, purchase_order_ids_boolean, picking_ids_boolean, cashback_line_ids, show_cashback, is_cn_from_cashback, so_cashback_id, is_dp, payments_date, manual_change_status_code, return_picking_ids, picking_id, nomor_seri_faktur_pajak_new, rma_id, receiving_note_names, receiving_note_dates, account_invoice_ids, origin, pos_order_id, is_from_pos_receivable, is_from_pos_cash_management, is_from_pos_cash_difference, is_from_pos_umum, is_from_pos_member, is_from_pos_member_gabungan, is_from_pos_partner, is_pkp_record, deposit_account_journal_id, create_from_session_id, inventory_id, _barcode_scanned, 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, sequence_prefix, sequence_number.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.bank.statement.line", "table_name": ""}
+{"text": "What are the available fields for pos.coupon.use.history?", "response": "The pos.coupon.use.history model has 13 fields: coupon_id, pos_order_id, cashier_id, used_date, payment_id, value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, datetime: 4, float: 1, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.coupon.use.history", "table_name": ""}
+{"text": "Show me the relational structure of account.voucher.line.", "response": "The account.voucher.line model has 11 relational fields: voucher_id -> account.voucher; product_id -> product.product; uom_id -> uom.uom; account_id -> account.account; account_analytic_id -> account.analytic.account; analytic_tag_ids -> account.analytic.tag; company_id -> res.company; tax_ids -> account.tax; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, tax_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.voucher.line", "table_name": ""}
+{"text": "What modules define currency.invoice.revaluation?", "response": "The currency.invoice.revaluation model is defined in module: equip3_accounting_multicurrency. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "currency.invoice.revaluation", "table_name": ""}
+{"text": "What are common use cases for product.template.create.variant.line?", "response": "To use the product.template.create.variant.line model, you need to provide values for required fields: attribute_id. Readonly fields: filter_value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.template.create.variant.line", "table_name": ""}
+{"text": "How to query report.sh_sale_reports.sh_sale_by_category_doc data?", "response": "To use the report.sh_sale_reports.sh_sale_by_category_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_sale_by_category_doc", "table_name": ""}
+{"text": "What fields does stock.lot.serialize.line have?", "response": "The stock.lot.serialize.line model has 13 fields: stock_move_id, sequence, move_id, product_id, demand_qty, qty_per_lot, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, float: 1, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.lot.serialize.line", "table_name": ""}
+{"text": "How does account.cashbox.wizard.line relate to other models?", "response": "The account.cashbox.wizard.line model has 7 relational fields: account_cashbox_wizard_id -> account.cashbox.wizard; cashbox_id -> account.bank.statement.cashbox; currency_id -> res.currency; pos_config_id -> pos.config; pos_session_id -> pos.session; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.cashbox.wizard.line", "table_name": ""}
+{"text": "What operations can I perform on stock.rules.report?", "response": "To use the stock.rules.report model, you need to provide values for required fields: product_id, product_tmpl_id, warehouse_ids, product_has_variants. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.rules.report", "table_name": ""}
+{"text": "How to query base_import.mapping data?", "response": "To use the base_import.mapping 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base_import.mapping", "table_name": ""}
+{"text": "Which fields in report.accounting_pdf_reports.report_financial are computed?", "response": "The report.accounting_pdf_reports.report_financial model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.accounting_pdf_reports.report_financial", "table_name": ""}
+{"text": "Show me the fields of stock.scrap.approval.matrix.", "response": "The stock.scrap.approval.matrix model has 44 fields: name, company_id, warehouse_id, branch_id, approval_line_count, sc_approval_matrix_line_ids, 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. Field types distribution: char: 7, many2one: 11, integer: 6, one2many: 5, selection: 2, date: 2, boolean: 5, many2many: 2, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.scrap.approval.matrix", "table_name": ""}
+{"text": "How to query assign.pr.wizard data?", "response": "To use the assign.pr.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assign.pr.wizard", "table_name": ""}
+{"text": "How does ks.message.wizard relate to other models?", "response": "The ks.message.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks.message.wizard", "table_name": ""}
+{"text": "What operations can I perform on new.customer?", "response": "To use the new.customer 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "new.customer", "table_name": ""}
+{"text": "Which fields in res.users.access.report.wizard are computed?", "response": "The res.users.access.report.wizard model is defined in module: report_user_access_right. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.access.report.wizard", "table_name": ""}
+{"text": "What does the account.reconcile.model.template model represent?", "response": "The account.reconcile.model.template model represents Reconcile Model Template in the ERP system. It contains 36 fields and is used to manage reconcile model template data. Key fields include: chart_template_id, name, sequence, rule_type, auto_reconcile, to_check, matching_order, match_text_location_label, match_text_location_note, match_text_location_reference, match_journal_ids, match_nature, match_amount, match_amount_min, match_amount_max, match_label, match_label_param, match_note, match_note_param, match_transaction_type, match_transaction_type_param, match_same_currency, match_total_amount, match_total_amount_param, match_partner, match_partner_ids, match_partner_category_ids, line_ids, decimal_separator, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.reconcile.model.template", "table_name": ""}
+{"text": "Describe the many2many relations for sale.data.margin.line.", "response": "The sale.data.margin.line model has 4 relational fields: margin_id -> sale.data.margin; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.data.margin.line", "table_name": ""}
+{"text": "What data can be stored in stock.inventory.line?", "response": "The stock.inventory.line model has 49 fields: is_editable, inventory_id, partner_id, product_id, product_uom_id, product_qty, categ_id, package_id, prod_lot_id, company_id, state, theoretical_qty, inventory_date, outdated, product_tracking, unit_price, inv_cost, sh_inven_adjt_barcode_scanner_is_last_scanned, location_id, sequence, adjustment_account_id, filtered_adjustment_account_id, is_adj_val, analytic_tag_ids, uom_id, category_uom_id, wizard_id, to_call_difference_qty_compute, difference_qty, currency_id, new_unit_price, theoretical_unit_price, difference_unit_price, user_id_1, user_id_2, user_count_1, user_count_2, barcode, s_no, current_user_id, is_user_id_1, is_user_id_2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 8, many2one: 19, float: 6, selection: 2, datetime: 4, char: 3, many2many: 2, monetary: 3, integer: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.inventory.line", "table_name": ""}
+{"text": "Describe the mrp.bom.tools model in Odoo.", "response": "The mrp.bom.tools model represents MRP BoM Tools in the ERP system. It contains 17 fields and is used to manage mrp bom tools data. Key fields include: bom_id, company_id, workorder_id, product_id, quantity, uom_id, operation_id, allowed_operation_ids, operation_two_ids, operation_two_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.bom.tools", "table_name": ""}
+{"text": "What are the available fields for opening.balance?", "response": "The opening.balance model has 13 fields: account_date, company_id, journal_id, partner_id, date_id, line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, many2one: 5, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "opening.balance", "table_name": ""}
+{"text": "How to query assembly.safety.stock.line data?", "response": "To use the assembly.safety.stock.line model, you need to provide values for required fields: stock_id, product_id, product_qty. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assembly.safety.stock.line", "table_name": ""}
+{"text": "Describe the field structure of pos.config.", "response": "The pos.config model has 493 fields: name, is_installed_account_accountant, journal_id, invoice_journal_id, currency_id, iface_cashdrawer, iface_electronic_scale, iface_vkeyboard, iface_customer_facing_display, iface_print_via_proxy, iface_scan_via_proxy, iface_big_scrollbars, iface_print_auto, iface_print_skip_screen, iface_tax_included, iface_start_categ_id, selectable_categ_ids, iface_display_categ_images, restrict_price_control, cash_control, receipt_header, receipt_footer, proxy_ip, active, uuid, sequence_id, sequence_line_id, session_ids, current_session_id, current_session_state, last_session_closing_cash, last_session_closing_date, last_session_closing_cashbox, pos_session_username, pos_session_state, pos_session_duration, pricelist_id, available_pricelist_ids, allowed_pricelist_ids, company_id, barcode_nomenclature_id, iface_tipproduct, tip_product_id, fiscal_position_ids, default_fiscal_position_id, default_cashbox_id, use_pricelist, tax_regime, tax_regime_selection, start_category, module_account, module_pos_discount, module_pos_loyalty, module_pos_mercury, manage_orders, product_configurator, is_posbox, is_header_or_footer, module_pos_hr, amount_authorized_diff, payment_method_ids, company_has_template, current_user_id, other_devices, rounding_method, cash_rounding, only_round_cash_method, has_active_session, show_allow_invoicing_alert, manual_discount, iface_discount, discount_pc, discount_product_id, epson_printer_ip, employee_ids, iface_splitbill, iface_printbill, iface_orderline_notes, floor_ids, printer_ids, is_table_management, is_order_printer, set_tip_after_payment, module_pos_restaurant, crm_team_id, group_pos_manager_id, group_pos_user_id, pos_receipt_template_id, order_loading_options, number_of_days, weight_scale_barcode_format_id, bnk_cash_control, restaurant_order, restaurant_order_login, restaurant_order_password, pos_config_cashbox_lines_ids, pos_config_cashbox_clsosing_line_ids, cashbox_lines_ids, pos_cashbox_lines_ids, printer_id, load_coupon_program, coupon_program_apply_type, coupon_program_ids, coupon_giftcard_ids, coupon_giftcard_create, user_id, allow_change_pos_profile, allow_numpad, allow_discount, allow_qty, allow_price, allow_remove_line, allow_minus, allow_payment, allow_customer, allow_add_order, allow_remove_order, allow_add_product, allow_payment_zero, allow_closing_session, allow_closing_all_sessions_online, allow_duplicate_session, allow_otp, twilio_acc_sid, twilio_auth_token, pos_otp_reset_time, pos_otp_msg, tax_affect_compliment, sale_order, sale_order_auto_confirm, sale_order_auto_invoice, sale_order_auto_delivery, sale_order_required_signature, pos_orders_management, pos_order_tracking, pos_order_tracking_remove_when_closing_session, shipping_order, pos_orders_load_orders_another_pos, pos_orders_filter_by_branch, pos_order_period_return_days, pos_allowed_return_category_ids, required_reason_return, display_return_days_receipt, display_onhand, allow_order_out_of_stock, allow_pos_categories_out_of_stock, hide_product_when_outof_stock, print_voucher, voucher_sequence_id, expired_days_voucher, sync_multi_session, sync_play_sound, sync_multi_session_with, sync_multi_session_manual_stop, sync_multi_session_alert_remove_order, sync_multi_session_offline, sync_to_pos_config_ids, sync_tracking_activities_user, display_person_add_line, internal_transfer, internal_transfer_picking_type_id, discount, discount_ids, delay, discount_limit, discount_limit_type, discount_limit_amount, return_products, return_method_id, return_covert_to_coupon, return_coupon_program_id, return_duplicate, return_viva_scan_barcode, validate_payment, validate_remove_order, validate_new_order, validate_change_minus, validate_quantity_change, validate_quantity_change_type, validate_price_change, validate_price_change_type, validate_discount_change, validate_discount_change_type, validate_remove_line, validate_return, validate_coupon, product_operation, note_order, signature_order, booking_orders, load_booked_orders_type, booking_orders_load_orders_another_pos, booking_orders_alert, booking_allow_confirm_sale, booking_orders_display_shipping_receipt, display_tax_orderline, display_tax_receipt, display_image_orderline, display_amount_discount, display_barcode, quickly_look_up_product, management_invoice, load_invoices_type, invoice_offline, wallet, payment_journal_ids, send_invoice_email, customer_default_id, auto_invoice, auto_invoice_with_customer_default, invoice_without_download, fiscal_position_auto_detect, display_sale_price_within_tax, display_cost_price, display_product_ref, display_product_detail, allow_remove_product, allow_edit_product, display_product_name_without_product_code, product_virtual_keyboard, hide_product_image, multi_location, update_stock_onhand, multi_stock_operation_type, multi_stock_operation_type_ids, product_view, update_tax, update_tax_ids, check_duplicate_email, check_duplicate_phone, check_required_phone, check_required_email, check_required_vat, add_sale_person, default_seller_id, seller_ids, force_seller, backup_orders, backup_orders_automatic, save_orders_removed, management_session, default_set_cash_open, default_set_cash_amount, default_set_cash_notes, cash_inout_reason_ids, barcode_receipt, qrcode_receipt, qrcode_ids, receipt_template, hide_mobile, hide_phone, hide_email, update_client, add_client, archive_client, remove_client, report_signature, report_product_summary, report_product_summary_auto_check_product, report_product_summary_auto_check_category, report_product_summary_auto_check_location, report_product_summary_auto_check_payment, report_order_summary, report_order_summary_auto_check_order, report_order_summary_auto_check_category, report_order_summary_auto_check_payment, report_order_summary_default_state, report_payment_summary, report_sale_summary, report_sale_summary_show_profit, default_product_sort_by, hide_order_screen, add_customer_before_products_already_in_shopping_cart, allow_cashier_select_pricelist, sale_with_package, allow_set_price_smaller_min_price, create_lots, fullfill_lots_type, fullfill_lots, stock_location_ids, validate_by_manager, discount_unlock_by_manager, assigned_user_ids, manager_ids, stock_location_id, stock_location_dest_id, discount_value, discount_value_limit, discount_global_id, posbox_save_orders, posbox_save_orders_server_ip, posbox_save_orders_server_port, analytic_account_id, limit_categories, iface_available_categ_ids, barcode_scan_timeout, rounding_automatic, rounding_type, service_charge_ids, service_charge_type, service_shipping_automatic, google_map_api_key, payment_reference, display_margin, start_session_oneclick, translate_products_name, set_product_name_from_field, replace_partners_name, set_partner_name_from_field, create_quotation, assign_orders_to_config_ids, product_generic_option, mrp, last_save_cache, category_ancestors, point_of_sale_update_stock_quantities, multi_session, display_filter_product_categories, product_category_ids, sessions_opened, search_query_only_start_when_enter, create_category_direct, create_product_direct, customer_facing_screen, customer_facing_screen_width, customer_facing_screen_height, rounding, rounding_factor, decimal_places, font_family, price_tag_color, header_background_color, cart_box_style, buttons_box_style, background, product_screen_background, cart_background, payment_screen_background, numpad_background, product_categories_height, product_width, product_height, product_margin, product_image_width, product_image_height, product_name_font_size, display_mobile_mode, display_mobile_screen_size, display_product_image, cart_width, whatsapp_api, whatsapp_token, whatsapp_send_type, whatsapp_message_receipt, checkin_screen, hidden_product_ids, warning_closing_session, warning_odoo_offline, pos_title, sync_partners_realtime, cache, local_network_printer, local_network_printer_ip_address, local_network_printer_port, product_recommendation, product_recommendation_number, show_session_information, tip_percent, tip_percent_max, categ_dislay_type, custom_sale, custom_sale_product_id, multi_currency, multi_currency_ids, allowed_employee_ids, fire_appetizer, fire_main_course, fire_dessert, enable_fire_appetizer, enable_fire_main_course, enable_fire_dessert, enable_seat_time, seat_time, show_product_template, available_product_domain, promotion_manual_select, promotion_auto_add, promotion_ids, is_manual_sync_for_sync_between_session, is_manual_sync_masterdata, is_manual_sync_member, is_auto_sync_product_stock, is_auto_sync_product_price, is_auto_sync_product, is_auto_sync_pricelist, is_auto_sync_promotion, is_auto_sync_coupon, is_monitor_auto_sync, is_force_sync_promotion, is_force_sync_pricelist, filter_load_pos_order, zone_id, product_voucher_service_id, product_coupon_service_id, display_table, display_all_product, product_categ_ids, product_categ_display_names, set_lines_to_done, order_receipt_tickets, qr_orders, login_title, login_required, login_create_partner, qrcode_order_screen, qrcode_order_auto_alert, customer_facing_display_html, user_ids, sync_manual_button, period_minutes_warning, enable_void_time, void_time, void_order_pin_ids, void_order_pins, void_order_line_pin_ids, void_order_line_pins, advertisement_image_ids, marquee_type, marquee_text, marque_color, marque_bg_color, marque_font_size, mute_video_sound, ac_width, ac_height, ac_qrcod, ac_qr_link, warehouse_id, is_order_rounding, order_rounding_type, picking_type_id, pos_branch_id, pos_branch_name, branch_telephone, branch_address, branch_street, branch_street_2, enable_gift_card, gift_card_account_id, gift_card_product_id, gift_payment_method_id, manual_card_number, msg_before_card_pay, is_difference_value_opening_control_validation, is_cash_management_with_validation, cashbox_payment_method_id, pos_cashbox_product_services, cashbox_line_amount, screen_type, is_allow_product_exchange, product_exchange_pin_ids, product_exchange_line_pins, is_save_order_history_local, save_order_history_local_days, is_save_order_to_pos_cache_service, link_pos_cache_service, select_shortcut, enable_shortcuts, display_point_receipt, pos_loyalty_id, pos_loyalty_ids, loyalty_combine_promotion, loyalty_redeem_in_pos_screen, is_allow_redeem_in_pos_screen, is_allow_create_member_in_pos_screen, customer_deposit_account_id, customer_deposit_reconcile_journal_id, order_summery, product_summery, product_categ_summery, loc_summery, payment_summery, pos_code, is_hide_pos_order_button, analytic_group_ids, is_pos_load_data_from_pos_cache_sdk, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 48, boolean: 267, many2one: 51, selection: 29, many2many: 39, text: 12, one2many: 7, float: 16, date: 1, integer: 19, html: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.config", "table_name": ""}
+{"text": "How to query return.inter.transfer.company data?", "response": "To use the return.inter.transfer.company model, you need to provide values for required fields: from_warehouse, to_warehouse. Readonly fields: sale_count, invoice_count, bill_count, purchase_count, internal_count, name, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "return.inter.transfer.company", "table_name": ""}
+{"text": "Can you explain the purpose of ks_dashboard_ninja.item_action?", "response": "The ks_dashboard_ninja.item_action model represents Dashboard Ninja Items Action Lines in the ERP system. It contains 17 fields and is used to manage dashboard ninja items action lines data. Key fields include: ks_item_action_field, ks_item_action_field_type, ks_item_action_date_groupby, ks_chart_type, ks_dashboard_item_id, ks_model_id, sequence, ks_record_limit, ks_sort_by_field, ks_sort_by_order, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.item_action", "table_name": ""}
+{"text": "List all fields in the ir.http model.", "response": "The ir.http model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.http", "table_name": ""}
+{"text": "What are the available fields for setu.inventory.fsn.xyz.analysis.bi.report?", "response": "The setu.inventory.fsn.xyz.analysis.bi.report model has 19 fields: product_id, product_category_id, company_id, average_stock, sales, turnover_ratio, current_stock, stock_value, fsn_classification, xyz_classification, combine_classification, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, float: 5, char: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.fsn.xyz.analysis.bi.report", "table_name": ""}
+{"text": "Describe the many2many relations for debt.collection.report.", "response": "The debt.collection.report model has 7 relational fields: partner_ids -> res.partner; user_ids -> res.users; journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, user_ids, journal_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "debt.collection.report", "table_name": ""}
+{"text": "What are the technical details of res.partner.type?", "response": "The res.partner.type model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.partner.type", "table_name": ""}
+{"text": "How do I use the product.pricelist.item model?", "response": "To use the product.pricelist.item model, you need to provide values for required fields: base, pricelist_id, compute_price, applied_on. Readonly fields: company_id, currency_id, active, price, uom_ids, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.pricelist.item", "table_name": ""}
+{"text": "What data can be stored in sh.sale.product.indent.xls?", "response": "The sh.sale.product.indent.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.sale.product.indent.xls", "table_name": ""}
+{"text": "Describe the many2many relations for base_import.tests.models.o2m.", "response": "The base_import.tests.models.o2m model has 3 relational fields: value -> base_import.tests.models.o2m.child; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.o2m", "table_name": ""}
+{"text": "What methods are available in recurring.move.line?", "response": "The recurring.move.line model is defined in module: sh_invoice_recurring. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "recurring.move.line", "table_name": ""}
+{"text": "How to query report.equip3_accounting_reports.equity_move data?", "response": "To use the report.equip3_accounting_reports.equity_move model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.equity_move", "table_name": ""}
+{"text": "What models are connected to account.deposit.return?", "response": "The account.deposit.return model has 6 relational fields: journal_id -> account.journal; diff_amount_account_id -> account.account; customer_deposit_id -> customer.deposit; vendor_deposit_id -> vendor.deposit; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.deposit.return", "table_name": ""}
+{"text": "What are the available fields for whatsapp.template.message.variable?", "response": "The whatsapp.template.message.variable model has 10 fields: wa_id, name, description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "whatsapp.template.message.variable", "table_name": ""}
+{"text": "What models are connected to pos.payment.installment.tenor?", "response": "The pos.payment.installment.tenor model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.payment.installment.tenor", "table_name": ""}
+{"text": "What models are connected to res.branch?", "response": "The res.branch model has 18 relational fields: analytic_tag_ids -> account.analytic.tag; company_id -> res.company; state_id -> res.country.state; country_id -> res.country; user_id -> res.users; user_ids -> res.users; config_ids -> pos.config; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, user_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.branch", "table_name": ""}
+{"text": "What fields does project.delete.wizard have?", "response": "The project.delete.wizard model has 10 fields: project_ids, task_count, projects_archived, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, integer: 2, boolean: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.delete.wizard", "table_name": ""}
+{"text": "What foreign keys exist in hour.group?", "response": "The hour.group model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hour.group", "table_name": ""}
+{"text": "What are the available fields for uom.uom?", "response": "The uom.uom model has 19 fields: name, category_id, factor, factor_inv, rounding, active, uom_type, timesheet_widget, is_pos_groupable, is_custom_uom, product_ratio_line, is_external_link, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 3, float: 3, boolean: 4, selection: 1, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "uom.uom", "table_name": ""}
+{"text": "Describe the implementation of account.payment.register.", "response": "The account.payment.register model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.payment.register", "table_name": ""}
+{"text": "How do I use the pos.sale.summary.wizard model?", "response": "To use the pos.sale.summary.wizard model, you need to provide values for required fields: start_dt, end_dt. Readonly fields: report_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.sale.summary.wizard", "table_name": ""}
+{"text": "What are the available fields for bus.bus?", "response": "The bus.bus model has 9 fields: channel, message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "bus.bus", "table_name": ""}
+{"text": "How to query mrp.immediate.production.line data?", "response": "To use the mrp.immediate.production.line model, you need to provide values for required fields: immediate_production_id, production_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mrp.immediate.production.line", "table_name": ""}
+{"text": "Show me the relational structure of ir.qweb.field.many2one.", "response": "The ir.qweb.field.many2one model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb.field.many2one", "table_name": ""}
+{"text": "What business logic is in intrawarehouse.transfer.line?", "response": "To use the intrawarehouse.transfer.line model, you need to provide values for required fields: none. Readonly fields: filter_location_ids, warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "intrawarehouse.transfer.line", "table_name": ""}
+{"text": "Describe the implementation of list.customer.compare.", "response": "The list.customer.compare model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "list.customer.compare", "table_name": ""}
+{"text": "List all fields in the project.task.recurrence model.", "response": "The project.task.recurrence model has 28 fields: task_ids, next_recurrence_date, recurrence_left, repeat_interval, repeat_unit, repeat_type, repeat_until, repeat_number, repeat_on_month, repeat_on_year, mon, tue, wed, thu, fri, sat, sun, repeat_day, repeat_week, repeat_weekday, repeat_month, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, date: 2, integer: 4, selection: 8, boolean: 7, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.task.recurrence", "table_name": ""}
+{"text": "What are the relationships in sh.correct.qc.measurement?", "response": "The sh.correct.qc.measurement model has 5 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; picking_id -> stock.picking; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.correct.qc.measurement", "table_name": ""}
+{"text": "Which fields in account.debt.collection are computed?", "response": "The account.debt.collection model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.debt.collection", "table_name": ""}
+{"text": "How to create records in mail.bot?", "response": "To use the mail.bot model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.bot", "table_name": ""}
+{"text": "What models are connected to stock.picking.batch.validate.line?", "response": "The stock.picking.batch.validate.line model has 6 relational fields: line_id -> stock.picking.batch.validate; product_id -> product.product; transfer_id -> stock.picking; location_id -> stock.location; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.picking.batch.validate.line", "table_name": ""}
+{"text": "What methods are available in res.partner.rfm.segment.history?", "response": "The res.partner.rfm.segment.history model is defined in module: setu_rfm_analysis. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.partner.rfm.segment.history", "table_name": ""}
+{"text": "List all fields in the warranty.claim.category model.", "response": "The warranty.claim.category model has 9 fields: name, team_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "warranty.claim.category", "table_name": ""}
+{"text": "How is account.multipayment used in the system?", "response": "The account.multipayment model represents Multipayment in the ERP system. It contains 90 fields and is used to manage multipayment data. Key fields include: name, partner_id, amount, journal_id, currency_id, date, ref, memo, line_credit_ids, line_debit_ids, diff_amount, partner_type, total_amount_credit, total_amount_debit, payment_id_count, company_id, branch_id, create_uid, create_date, different_move_id, request_partner_id, payment_method, multipul_payment_approval_matrix_id, is_multi_payment_approval_matrix, is_approve_button, approved_matrix_ids, approval_matrix_line_id, action_validate_boolean, action_draft_boolean, action_cancel_boolean, request_for_approval_boolean, action_approved_rp_boolean, rp_reject_boolean, state_boolean, state1_boolean, state2_boolean, difference_ids, payment_difference_amount, writeoff_account_id, writeoff_label, payment_type, clearing_account_id, move_id, due_date, receive_date, clearing_date, is_vendor, state, state1, state2, payment_ids, invoice_cutoff_date, is_cutoff_date, is_check_all, 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, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.multipayment", "table_name": ""}
+{"text": "How do I use the sh.purchase.analysis.xls model?", "response": "To use the sh.purchase.analysis.xls model, you need to provide values for required fields: none. Readonly fields: file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.purchase.analysis.xls", "table_name": ""}
+{"text": "What are the available fields for list.order?", "response": "The list.order model has 28 fields: order_dic_id, order_number, order_date, total, due_amount, cust_dic_id, invoice_number, invoice_date, invoice_currency_id, salesperson, sale_currency_id, sale_amount, paid_amount, balance_amount, product, customer, qty, cost, sale_price, profit, margin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 6, datetime: 5, float: 10, integer: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "list.order", "table_name": ""}
+{"text": "How does ir.http relate to other models?", "response": "The ir.http model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.http", "table_name": ""}
+{"text": "How does report.sh_sale_reports.sh_salesperson_report_doc relate to other models?", "response": "The report.sh_sale_reports.sh_salesperson_report_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_salesperson_report_doc", "table_name": ""}
+{"text": "How to query gamification.badge data?", "response": "To use the gamification.badge model, you need to provide values for required fields: name, rule_auth. Readonly fields: granted_count, granted_users_count, unique_owner_ids, stat_this_month, stat_my, stat_my_this_month, stat_my_monthly_sending, remaining_sending, granted_employees_count, can_publish, website_url, image_1024, image_512, image_256, image_128, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "gamification.badge", "table_name": ""}
+{"text": "Describe the pos.account.cashbox.line model in Odoo.", "response": "The pos.account.cashbox.line model represents CashBox Line in the ERP system. It contains 11 fields and is used to manage cashbox line data. Key fields include: coin_value, number, subtotal, pos_config_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.account.cashbox.line", "table_name": ""}
+{"text": "What models are connected to gamification.goal?", "response": "The gamification.goal model has 6 relational fields: definition_id -> gamification.goal.definition; user_id -> res.users; line_id -> gamification.challenge.line; challenge_id -> gamification.challenge; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "gamification.goal", "table_name": ""}
+{"text": "What does the report.equip3_accounting_reports.balance_sheet model represent?", "response": "The report.equip3_accounting_reports.balance_sheet model represents report.equip3_accounting_reports.balance_sheet in the ERP system. It contains 3 fields and is used to manage report.equip3_accounting_reports.balance_sheet data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.balance_sheet", "table_name": ""}
+{"text": "What business logic is in base.module.update?", "response": "To use the base.module.update model, you need to provide values for required fields: none. Readonly fields: updated, added, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.module.update", "table_name": ""}
+{"text": "What business logic is in account.group.template?", "response": "To use the account.group.template model, you need to provide values for required fields: chart_template_id, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.group.template", "table_name": ""}
+{"text": "Tell me about the vendor.delay.report model.", "response": "The vendor.delay.report model represents Vendor Delay Report in the ERP system. It contains 10 fields and is used to manage vendor delay report data. Key fields include: partner_id, product_id, category_id, date, qty_total, qty_on_time, on_time_rate, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "vendor.delay.report", "table_name": ""}
+{"text": "Which fields in report.accounting_pdf_reports.report_tax are computed?", "response": "The report.accounting_pdf_reports.report_tax model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.accounting_pdf_reports.report_tax", "table_name": ""}
+{"text": "What are common use cases for product.public.category?", "response": "To use the product.public.category model, you need to provide values for required fields: name. Readonly fields: parents_and_self, amount_footer, image_1024, image_512, image_256, image_128, is_seo_optimized, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.public.category", "table_name": ""}
+{"text": "What business logic is in ir.sequence.date_range?", "response": "To use the ir.sequence.date_range model, you need to provide values for required fields: date_from, date_to, sequence_id, number_next. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.sequence.date_range", "table_name": ""}
+{"text": "How to create records in invoice.templates?", "response": "To use the invoice.templates 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "invoice.templates", "table_name": ""}
+{"text": "Show me the relational structure of setu.inventory.turnover.analysis.report.", "response": "The setu.inventory.turnover.analysis.report model has 7 relational fields: product_category_ids -> product.category; product_ids -> product.product; warehouse_ids -> stock.warehouse; company_id -> res.company; company_ids -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_category_ids, product_ids, warehouse_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.turnover.analysis.report", "table_name": ""}
+{"text": "How does sh.qc.alert.tags relate to other models?", "response": "The sh.qc.alert.tags model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.qc.alert.tags", "table_name": ""}
+{"text": "List all fields in the sale.advance.payment.inv model.", "response": "The sale.advance.payment.inv model has 20 fields: advance_payment_method, deduct_down_payments, has_down_payments, product_id, count, amount, currency_id, fixed_amount, deposit_account_id, deposit_taxes_id, date_start_invoice_timesheet, date_end_invoice_timesheet, invoicing_timesheet_enabled, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, boolean: 3, many2one: 5, integer: 2, float: 1, monetary: 1, many2many: 1, date: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.advance.payment.inv", "table_name": ""}
+{"text": "What are the available fields for account.account.tag?", "response": "The account.account.tag model has 14 fields: applicability, color, active, tax_report_line_ids, tax_negate, country_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, integer: 2, boolean: 2, many2many: 1, many2one: 3, char: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.account.tag", "table_name": ""}
+{"text": "What data can be stored in calendar.alarm?", "response": "The calendar.alarm model has 12 fields: name, duration, interval, duration_minutes, alarm_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 3, selection: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "calendar.alarm", "table_name": ""}
+{"text": "How is pos.product.bom.line implemented technically?", "response": "The pos.product.bom.line model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.product.bom.line", "table_name": ""}
+{"text": "What business logic is in restore.lead.type?", "response": "To use the restore.lead.type 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "restore.lead.type", "table_name": ""}
+{"text": "What methods are available in analytic.priority?", "response": "The analytic.priority model is defined in module: equip3_accounting_analytical. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "analytic.priority", "table_name": ""}
+{"text": "What foreign keys exist in product.warehouse.cost.line?", "response": "The product.warehouse.cost.line model has 6 relational fields: prod_wh_cost_id -> product.warehouse.cost; warehouse_id -> stock.warehouse; company_id -> res.company; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.warehouse.cost.line", "table_name": ""}
+{"text": "What fields does res.currency.rate have?", "response": "The res.currency.rate model has 13 fields: name, currency_id, company_id, rate, conversion, mr_rate, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, many2one: 4, float: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.currency.rate", "table_name": ""}
+{"text": "Describe the field structure of res.users.apikeys.show.", "response": "The res.users.apikeys.show model has 4 fields: key, id, display_name, __last_update. Field types distribution: char: 2, integer: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.users.apikeys.show", "table_name": ""}
+{"text": "Describe the many2many relations for mr.approval.matrix.line.", "response": "The mr.approval.matrix.line model has 13 relational fields: user_ids -> res.users; mr_approval_matrix -> mr.approval.matrix; approved_users -> res.users; last_approved -> res.users; mr_matrix_id -> material.request; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mr.approval.matrix.line", "table_name": ""}
+{"text": "What data can be stored in pos.promotion.gift.free?", "response": "The pos.promotion.gift.free model has 13 fields: active, product_id, quantity_free, promotion_id, type_apply, product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 4, float: 1, selection: 1, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.promotion.gift.free", "table_name": ""}
+{"text": "How to create records in crm.merge.opportunity?", "response": "To use the crm.merge.opportunity 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.merge.opportunity", "table_name": ""}
+{"text": "What are the technical details of ir.rule?", "response": "The ir.rule model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.rule", "table_name": ""}
+{"text": "How does account.account.map relate to other models?", "response": "The account.account.map model has 7 relational fields: company_id -> res.company; line_ids -> account.account.map.line; child_company_id -> res.company; sales_line_ids -> account.tax.map.sales.line; purchase_line_ids -> account.tax.map.purchase.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.account.map", "table_name": ""}
+{"text": "What does the service.work.order.checklist model represent?", "response": "The service.work.order.checklist model represents Service Work Order Checklist in the ERP system. It contains 12 fields and is used to manage service work order checklist data. Key fields include: swo_id, name, desc, state, state2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "service.work.order.checklist", "table_name": ""}
+{"text": "What models are connected to report.excel.param?", "response": "The report.excel.param model has 5 relational fields: report_excel_id -> report.excel; param_ir_model_id -> ir.model; wizard_param_ir_model_field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.excel.param", "table_name": ""}
+{"text": "List all fields in the module.advanced.upgrade model.", "response": "The module.advanced.upgrade model has 17 fields: module_id, module_shortdesc, module_name, module_author, module_installed_version, module_latest_version, module_state, children_ids, parent_id, selected, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 6, selection: 1, one2many: 1, boolean: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "module.advanced.upgrade", "table_name": ""}
+{"text": "What models are connected to report.equip3_kitchen_reports.report_kitchen_production?", "response": "The report.equip3_kitchen_reports.report_kitchen_production model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_kitchen_reports.report_kitchen_production", "table_name": ""}
+{"text": "What methods are available in budget.carry.over?", "response": "The budget.carry.over model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "budget.carry.over", "table_name": ""}
+{"text": "What are the relationships in report.point_of_sale.report_saledetails?", "response": "The report.point_of_sale.report_saledetails model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.point_of_sale.report_saledetails", "table_name": ""}
+{"text": "How does reset.view.arch.wizard relate to other models?", "response": "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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "reset.view.arch.wizard", "table_name": ""}
+{"text": "What are the relationships in kpi.item?", "response": "The kpi.item model has 18 relational fields: category_id -> kpi.category; line_ids -> kpi.scorecard.line; currency_id -> res.currency; parent_id -> kpi.item; all_parent_ids -> kpi.item; child_ids -> kpi.item; measures_ids -> kpi.measure.item; constant_ids -> kpi.constant; kpi_ids -> kpi.item; company_id -> res.company; user_ids -> res.users; user_group_ids -> res.groups; access_user_ids -> res.users; edit_user_ids -> res.users; edit_user_group_ids -> res.groups; edit_access_user_ids -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: all_parent_ids, measures_ids, constant_ids, kpi_ids, user_ids, user_group_ids, access_user_ids, edit_user_ids, edit_user_group_ids, edit_access_user_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kpi.item", "table_name": ""}
+{"text": "How to query sh.account.period data?", "response": "To use the sh.account.period model, you need to provide values for required fields: name, date_start, date_end, company_id. Readonly fields: name, code, date_start, date_end, fiscal_year_id, special, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.account.period", "table_name": ""}
+{"text": "What are the relationships in pos.keyboard.shortcuts?", "response": "The pos.keyboard.shortcuts model has 3 relational fields: payment_methods -> pos.payment.method.key; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.keyboard.shortcuts", "table_name": ""}
+{"text": "What are common use cases for export.efaktur?", "response": "To use the export.efaktur model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "export.efaktur", "table_name": ""}
+{"text": "How to query ir.qweb.field.selection data?", "response": "To use the ir.qweb.field.selection model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.selection", "table_name": ""}
+{"text": "What does the sh.mpo.merge.purchase.order.wizard model represent?", "response": "The sh.mpo.merge.purchase.order.wizard model represents Merge Purchase Order Wizard in the ERP system. It contains 12 fields and is used to manage merge purchase order wizard data. Key fields include: partner_id, purchase_order_id, purchase_order_ids, merge_type, merge_option, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.mpo.merge.purchase.order.wizard", "table_name": ""}
+{"text": "What business logic is in sh.qc.alert?", "response": "To use the sh.qc.alert model, you need to provide values for required fields: team_id, user_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.qc.alert", "table_name": ""}
+{"text": "Can you explain the purpose of purchase.agreement.type?", "response": "The purchase.agreement.type model represents Purchase Agreement Type in the ERP system. It contains 8 fields and is used to manage purchase agreement type data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.agreement.type", "table_name": ""}
+{"text": "Show me the fields of account.bank.statement.line.wizard.", "response": "The account.bank.statement.line.wizard model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.bank.statement.line.wizard", "table_name": ""}
+{"text": "What business logic is in recurring.move.line?", "response": "To use the recurring.move.line model, you need to provide values for required fields: recurring_id, account_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "recurring.move.line", "table_name": ""}
+{"text": "What are the technical details of account.analytic.new?", "response": "The account.analytic.new model is defined in module: equip3_accounting_analytical. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.analytic.new", "table_name": ""}
+{"text": "Show me the relational structure of pos.promotion.", "response": "The pos.promotion model has 34 relational fields: product_id -> product.product; discount_order_ids -> pos.promotion.discount.order; discount_category_ids -> pos.promotion.discount.category; discount_quantity_ids -> pos.promotion.discount.quantity; gift_condition_ids -> pos.promotion.gift.condition; gift_free_ids -> pos.promotion.gift.free; discount_condition_ids -> pos.promotion.discount.condition; discount_apply_ids -> pos.promotion.discount.apply; multilevel_condition_ids -> pos.promotion.multilevel.condition; multilevel_gift_ids -> pos.promotion.multilevel.gift; price_ids -> pos.promotion.price; special_category_ids -> pos.promotion.special.category; multi_buy_ids -> pos.promotion.multi.buy; promotion_specific_product_ids -> pos.promotion.specific.product; tebus_murah_product_ids -> pos.promotion.tebus.murah; product_ids -> product.product; special_customer_ids -> res.partner; promotion_group_ids -> res.partner.group; pos_branch_ids -> res.branch; payment_method_ids -> pos.payment.method; pos_apply -> pos.config; card_payment_id -> card.payment; card_payment_ids -> card.payment; branch_id -> res.branch; promotion_based_on_brand_ids -> pos.promotion.selected.brand; tebus_murah_selected_brand_ids -> pos.promotion.tebus.murah.selected.brand; tebus_murah_brand_ids -> product.brand; promotion_product_discount_id -> product.product; company_id -> res.company; currency_id -> res.currency; pos_loyalty_category_ids -> pos.loyalty.category; pos_branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, special_customer_ids, promotion_group_ids, pos_branch_ids, payment_method_ids, pos_apply, card_payment_ids, tebus_murah_brand_ids, pos_loyalty_category_ids, pos_branch_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.promotion", "table_name": ""}
+{"text": "What fields does pos.combo.limit have?", "response": "The pos.combo.limit model has 11 fields: product_tmpl_id, pos_categ_id, quantity_limited, default_product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 2, many2many: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.combo.limit", "table_name": ""}
+{"text": "What foreign keys exist in quality.alert.report?", "response": "The quality.alert.report model has 5 relational fields: product_ids -> product.product; user_ids -> res.users; stage_id -> sh.qc.alert.stage; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, user_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "quality.alert.report", "table_name": ""}
+{"text": "How does account.account relate to other models?", "response": "The account.account model has 23 relational fields: move_line_ids -> account.move.line; parent_id -> account.account; child_ids -> account.account; currency_id -> res.currency; user_type_id -> account.account.type; tax_ids -> account.tax; company_id -> res.company; tag_ids -> account.account.tag; group_id -> account.group; root_id -> account.root; allowed_journal_ids -> account.journal; branch_id -> res.branch; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_ids, tag_ids, allowed_journal_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.account", "table_name": ""}
+{"text": "Describe the many2many relations for crossovered.budget.wizard.", "response": "The crossovered.budget.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crossovered.budget.wizard", "table_name": ""}
+{"text": "What are common use cases for overhead.time?", "response": "To use the overhead.time 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "overhead.time", "table_name": ""}
+{"text": "Describe the implementation of stock.package.destination.", "response": "The stock.package.destination model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.package.destination", "table_name": ""}
+{"text": "What foreign keys exist in report.equip3_accounting_reports.pettycash_analysis?", "response": "The report.equip3_accounting_reports.pettycash_analysis model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.pettycash_analysis", "table_name": ""}
+{"text": "How to query stock.move.line data?", "response": "To use the stock.move.line model, you need to provide values for required fields: company_id, product_uom_id, product_uom_qty, date, location_id, location_dest_id. Readonly fields: company_id, product_uom_category_id, lots_visible, picking_code, picking_type_use_create_lots, picking_type_use_existing_lots, state, is_locked, tracking, origin, picking_type_entire_packs, is_double_product_usage, sale_price, product_type, quant_package_ids, source_picking_id, is_batch_shipping_packing, is_batch_shipping_delivery, description, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.move.line", "table_name": ""}
+{"text": "What modules define repair.fee?", "response": "The repair.fee model is defined in module: repair. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "repair.fee", "table_name": ""}
+{"text": "What foreign keys exist in nsfp.registration?", "response": "The nsfp.registration model has 4 relational fields: fiscal_year -> sh.fiscal.year; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "nsfp.registration", "table_name": ""}
+{"text": "How is stock.warehouse implemented technically?", "response": "The stock.warehouse model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.warehouse", "table_name": ""}
+{"text": "Which fields in account.deposit.reconcile are computed?", "response": "The account.deposit.reconcile model is defined in module: equip3_accounting_deposit. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.deposit.reconcile", "table_name": ""}
+{"text": "Describe the many2many relations for hr.employee.", "response": "The hr.employee model has 32 relational fields: user_id -> res.users; user_partner_id -> res.partner; company_id -> res.company; address_home_id -> res.partner; country_id -> res.country; country_of_birth -> res.country; bank_account_id -> res.partner.bank; child_ids -> hr.employee; category_ids -> hr.employee.category; message_main_attachment_id -> ir.attachment; subordinate_ids -> hr.employee; currency_id -> res.currency; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; website_message_ids -> mail.message; department_id -> hr.department; job_id -> hr.job; address_id -> res.partner; resource_id -> resource.resource; resource_calendar_id -> resource.calendar; parent_id -> hr.employee; coach_id -> hr.employee; goal_ids -> gamification.goal; badge_ids -> gamification.badge.user; direct_badge_ids -> gamification.badge.user; create_uid -> res.users; write_uid -> res.users. Many2many fields: category_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hr.employee", "table_name": ""}
+{"text": "What are the available fields for pos.loyalty.reward.product?", "response": "The pos.loyalty.reward.product model has 14 fields: gift_reward_id, product_id, redeem_point, default_code, list_price, uom_id, sh_qr_code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, integer: 2, char: 3, float: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.loyalty.reward.product", "table_name": ""}
+{"text": "How to create records in crm.team?", "response": "To use the crm.team model, you need to provide values for required fields: name, alias_id, alias_model_id, alias_defaults, alias_contact. Readonly fields: currency_id, dashboard_button_name, dashboard_graph_data, lead_unassigned_count, lead_all_assigned_month_count, opportunities_count, opportunities_amount, opportunities_overdue_count, opportunities_overdue_amount, invoiced, quotations_count, quotations_amount, sales_to_invoice_count, abandoned_carts_count, abandoned_carts_amount, rma_draft_count, rma_confirm_count, rma_process_count, rma_close_count, rma_reject_count, pos_sessions_open_count, pos_order_amount_total, company_id, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, alias_domain. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.team", "table_name": ""}
+{"text": "How is product.product implemented technically?", "response": "The product.product model is defined in module: product. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.product", "table_name": ""}
+{"text": "What models are connected to mail.thread.cc?", "response": "The mail.thread.cc model has 6 relational fields: message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.thread.cc", "table_name": ""}
+{"text": "What is the report_excel_gen model?", "response": "The report_excel_gen model represents   in the ERP system. It contains 7 fields and is used to manage   data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report_excel_gen", "table_name": ""}
+{"text": "Describe the many2many relations for receipt.payment.line.credit.", "response": "The receipt.payment.line.credit model has 7 relational fields: line_id -> receipt.payment; currency_id -> res.currency; invoice_id -> account.move; account_id -> account.account; payment_id -> account.payment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "receipt.payment.line.credit", "table_name": ""}
+{"text": "Describe the field structure of limit.approval.matrix.sale.reject.", "response": "The limit.approval.matrix.sale.reject model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "limit.approval.matrix.sale.reject", "table_name": ""}
+{"text": "What are the relationships in mass.editing.wizard?", "response": "The mass.editing.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mass.editing.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for auth_totp.wizard.", "response": "The auth_totp.wizard model has 3 relational fields: user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "auth_totp.wizard", "table_name": ""}
+{"text": "How do I use the report.dev_rma.report_rma_template model?", "response": "To use the report.dev_rma.report_rma_template model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.dev_rma.report_rma_template", "table_name": ""}
+{"text": "What are the technical details of sale.order.deduction?", "response": "The sale.order.deduction model is defined in module: equip3_sale_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.order.deduction", "table_name": ""}
+{"text": "What models are connected to sh.purchase.product.profit.xls?", "response": "The sh.purchase.product.profit.xls model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.product.profit.xls", "table_name": ""}
+{"text": "What fields does cashback.line have?", "response": "The cashback.line model has 16 fields: sequence, product_id, name, product_uom_qty, price_unit, total, customer_voucher_id, order_id, invoice_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 6, char: 2, float: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "cashback.line", "table_name": ""}
+{"text": "What are common use cases for crm.quotation.partner?", "response": "To use the crm.quotation.partner model, you need to provide values for required fields: action, lead_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.quotation.partner", "table_name": ""}
+{"text": "What data can be stored in account.analytic.default?", "response": "The account.analytic.default model has 43 fields: sequence, analytic_id, analytic_tag_ids, product_id, user_id, company_id, date_start, partner_id, account_id, date_stop, branch_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 6, many2one: 12, many2many: 3, date: 4, one2many: 4, selection: 2, char: 4, boolean: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.analytic.default", "table_name": ""}
+{"text": "List all fields in the sequence.mixin model.", "response": "The sequence.mixin model has 5 fields: sequence_prefix, sequence_number, id, display_name, __last_update. Field types distribution: char: 2, integer: 2, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sequence.mixin", "table_name": ""}
+{"text": "What fields does tax.adjustments.wizard have?", "response": "The tax.adjustments.wizard model has 17 fields: reason, journal_id, date, debit_account_id, credit_account_id, amount, adjustment_type, tax_report_line_id, company_currency_id, report_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 8, date: 1, monetary: 1, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "tax.adjustments.wizard", "table_name": ""}
+{"text": "Which fields in generate.closing.entries are computed?", "response": "The generate.closing.entries model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "generate.closing.entries", "table_name": ""}
+{"text": "How is product.brand implemented technically?", "response": "The product.brand model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.brand", "table_name": ""}
+{"text": "Describe the implementation of cust.credit.limit.xls.", "response": "The cust.credit.limit.xls model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "cust.credit.limit.xls", "table_name": ""}
+{"text": "Show me the fields of milestone.contract.template.", "response": "The milestone.contract.template model has 11 fields: name, checklist_template_id, line_ids, checklist_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, one2many: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "milestone.contract.template", "table_name": ""}
+{"text": "How to query tax.sale.details.report data?", "response": "To use the tax.sale.details.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "tax.sale.details.report", "table_name": ""}
+{"text": "How to query pos.order.log data?", "response": "To use the pos.order.log model, you need to provide values for required fields: name, action, create_date. Readonly fields: name, order_json, action, create_date, write_date, config_id, session_id, branch_id, company_id, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, write_uid, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.order.log", "table_name": ""}
+{"text": "Show me the relational structure of mrp.bom.operation.", "response": "The mrp.bom.operation model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.bom.operation", "table_name": ""}
+{"text": "Describe the field structure of internal.transfer.", "response": "The internal.transfer model has 84 fields: name, description, source_document, state, state1, state2, state3, product_line_ids, operation_type_in_id, operation_type_out_id, is_transit, operation_count, expiry_date, is_source_loc, is_destination_loc, internal_transfer_line_total, operations, 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, source_warehouse_id, destination_warehouse_id, company_id, filter_source_warehouse_id, filter_destination_warehouse_id, requested_by, get_warehouse, is_mbs_on_transfer_operations, branch_id, domain_warehouse_source_id, domain_warehouse_destination_id, sh_it_barcode_mobile, sh_it_bm_is_cont_scan, mr_id, average_id, is_outlet_order, analytic_account_group_ids, is_expired_tranfer, arrival_date, source_location_id, destination_location_id, scheduled_date, create_date, 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, write_uid, write_date, __last_update. Field types distribution: char: 12, text: 3, selection: 6, one2many: 6, many2one: 20, boolean: 16, integer: 7, datetime: 6, many2many: 6, date: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "internal.transfer", "table_name": ""}
+{"text": "Show me the relational structure of all.loyalty.history.", "response": "The all.loyalty.history model has 7 relational fields: order_id -> sale.order; pos_order_id -> pos.order; partner_id -> res.partner; currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "all.loyalty.history", "table_name": ""}
+{"text": "Show me the relational structure of ir.config_parameter.", "response": "The ir.config_parameter model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.config_parameter", "table_name": ""}
+{"text": "Can you explain the purpose of account.internal.transfer?", "response": "The account.internal.transfer model represents Account Internal Transfer in the ERP system. It contains 68 fields and is used to manage account internal transfer data. Key fields include: request_partner_id, bank_from_journal_id, bank_to_journal_id, transfer_in_transit, account_in_transit, transfer_desc, transfer_amount, currency_id, transfer_date, create_date, create_uid, company_id, branch_id, state, filter_branch_ids, administration, administration_account, administration_fee, has_reconciled_entries, approval_matrix_id, is_internal_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state1, state2, analytic_group_ids, apply_manual_currency_exchange, manual_currency_exchange_rate, manual_currency_exchange_inverse_rate, type_curr, name, 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, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.internal.transfer", "table_name": ""}
+{"text": "How does base.module.update relate to other models?", "response": "The base.module.update model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.module.update", "table_name": ""}
+{"text": "What models are connected to stock.return.picking?", "response": "The stock.return.picking model has 10 relational fields: picking_id -> stock.picking; product_return_moves -> stock.return.picking.line; original_location_id -> stock.location; parent_location_id -> stock.location; company_id -> res.company; location_id -> stock.location; return_reason -> return.reason; return_line_ids -> stock.return.move.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.return.picking", "table_name": ""}
+{"text": "Tell me about the all.loyalty.history model.", "response": "The all.loyalty.history model represents all loyalty history in the ERP system. It contains 19 fields and is used to manage all loyalty history data. Key fields include: order_id, pos_order_id, partner_id, date, generated_from, transaction_type, points, amount, currency_id, company_id, check_state, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "all.loyalty.history", "table_name": ""}
+{"text": "What are the available fields for o2m.global.search.fields?", "response": "The o2m.global.search.fields model has 14 fields: sequence, name, field_id, global_o2m_search_id, model_id, related_model_id, ttype, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, char: 3, many2one: 5, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "o2m.global.search.fields", "table_name": ""}
+{"text": "What are common use cases for stock.location.tag?", "response": "To use the stock.location.tag 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.location.tag", "table_name": ""}
+{"text": "What foreign keys exist in o2m.global.search.fields?", "response": "The o2m.global.search.fields model has 5 relational fields: field_id -> ir.model.fields; global_o2m_search_id -> global.search.fields; model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "o2m.global.search.fields", "table_name": ""}
+{"text": "How is calendar.event.type implemented technically?", "response": "The calendar.event.type model is defined in module: calendar. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "calendar.event.type", "table_name": ""}
+{"text": "List all fields in the cust.credit.limit.data.line model.", "response": "The cust.credit.limit.data.line model has 13 fields: cust_credit_id, partner_id, cust_credit_limit, customer_credit_limit, balance_due, aval_credit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "cust.credit.limit.data.line", "table_name": ""}
+{"text": "How is wizard.ir.model.menu.create used in the system?", "response": "The wizard.ir.model.menu.create model represents Create Menu Wizard in the ERP system. It contains 9 fields and is used to manage create menu wizard data. Key fields include: menu_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "wizard.ir.model.menu.create", "table_name": ""}
+{"text": "What fields does multiple.rfq have?", "response": "The multiple.rfq model has 9 fields: vendor_ids, product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "multiple.rfq", "table_name": ""}
+{"text": "How to create records in material.request?", "response": "To use the material.request model, you need to provide values for required fields: name, requested_by, schedule_date, analytic_account_group_ids. Readonly fields: create_date, create_uid, company_id, branch_id, status_1, status_2, status_3, check_product, mr_approval_matrix_id, is_material_request_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, is_reset_to_draft, pr_count, ir_count, itr_war_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, id, display_name, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "material.request", "table_name": ""}
+{"text": "Describe the account.cashbox.wizard.validate model in Odoo.", "response": "The account.cashbox.wizard.validate model represents account.cashbox.wizard.validate in the ERP system. It contains 9 fields and is used to manage account.cashbox.wizard.validate data. Key fields include: pin, account_cashbox_wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.cashbox.wizard.validate", "table_name": ""}
+{"text": "Describe the many2many relations for pos.voucher.", "response": "The pos.voucher model has 15 relational fields: customer_id -> res.partner; user_id -> res.users; pos_order_id -> pos.order; pos_order_line_id -> pos.order.line; use_history_ids -> pos.voucher.use.history; generated_source_id -> generate.pos.voucher; limit_restrict_product_ids -> product.product; pos_category_ids -> pos.category; company_id -> res.company; receipt_template_id -> pos.receipt.template; source_document_id -> generate.pos.voucher; brand_ids -> product.brand; member_type_ids -> pos.loyalty.category; create_uid -> res.users; write_uid -> res.users. Many2many fields: limit_restrict_product_ids, pos_category_ids, brand_ids, member_type_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.voucher", "table_name": ""}
+{"text": "What does the barcode.product.lines model represent?", "response": "The barcode.product.lines model represents barcode.product.lines in the ERP system. It contains 13 fields and is used to manage barcode.product.lines data. Key fields include: product_id, lot_id, wizard_id, qty, is_multi_barcode, barcode, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "barcode.product.lines", "table_name": ""}
+{"text": "What methods are available in ks_custom_report.ks_report?", "response": "The ks_custom_report.ks_report model is defined in module: ks_custom_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks_custom_report.ks_report", "table_name": ""}
+{"text": "How do I use the warranty.claim.stage model?", "response": "To use the warranty.claim.stage 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "warranty.claim.stage", "table_name": ""}
+{"text": "What business logic is in queue.job.function?", "response": "To use the queue.job.function model, you need to provide values for required fields: channel_id. Readonly fields: channel, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "queue.job.function", "table_name": ""}
+{"text": "What data can be stored in rn.approval_matrix_detail?", "response": "The rn.approval_matrix_detail model has 11 fields: location_name, usage, company_id, rn_approval_matrix_id2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "rn.approval_matrix_detail", "table_name": ""}
+{"text": "Show me the fields of pos.voucher.", "response": "The pos.voucher model has 39 fields: active, customer_id, code, start_date, end_date, state, value, apply_type, method, use_date, user_id, source, pos_order_id, pos_order_line_id, use_history_ids, number, maximum_discount_amount, minimum_purchase_amount, is_generate_voucher, generated_source_id, limit_restrict_product_ids, pos_category_ids, company_id, receipt_template_id, source_document_id, is_customize_sequence, sequence_generate_method, manual_input_sequence, running_number_prefix, running_number_digit, brand_ids, member_type_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 3, many2one: 10, char: 6, datetime: 6, selection: 4, float: 3, one2many: 1, many2many: 4, integer: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.voucher", "table_name": ""}
+{"text": "What is the report.sh_purchase_reports.sh_po_product_profit_doc model?", "response": "The report.sh_purchase_reports.sh_po_product_profit_doc model represents Purchase Product Profit report abstract model in the ERP system. It contains 3 fields and is used to manage purchase product profit report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_po_product_profit_doc", "table_name": ""}
+{"text": "Show me the fields of sale.margin.report.wizard.", "response": "The sale.margin.report.wizard model has 12 fields: partner_ids, start_date, end_date, company_ids, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, datetime: 5, many2one: 3, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.margin.report.wizard", "table_name": ""}
+{"text": "What foreign keys exist in report.stock.report_product_product_replenishment?", "response": "The report.stock.report_product_product_replenishment model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.stock.report_product_product_replenishment", "table_name": ""}
+{"text": "What are the available fields for vendor.deposit?", "response": "The vendor.deposit model has 77 fields: name, is_deposit, amount, remaining_amount, communication, return_deposit, payment_date, deposit_reconcile_journal_id, journal_id, deposit_account_id, company_id, currency_id, state, is_show_cancel, invoice_count, reconcile_count, reconcile_deposit_ids, invoice_deposit_ids, filter_deposit_account_ids, approval_matrix_id, is_vendor_deposit_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state1, state2, request_partner_id, deposit_history, add_amount_approver, approve_add_amount, deposit_count, description, partner_id, employee_id, branch_id, filter_branch_ids, move_id, is_cash_advance, return_cash_advance_ids, 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. Field types distribution: char: 9, boolean: 11, monetary: 3, many2one: 21, date: 3, selection: 5, integer: 8, many2many: 8, one2many: 5, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "vendor.deposit", "table_name": ""}
+{"text": "Which fields in ir.qweb.field.contact are computed?", "response": "The ir.qweb.field.contact model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.qweb.field.contact", "table_name": ""}
+{"text": "List all fields in the product.ribbon model.", "response": "The product.ribbon model has 11 fields: html, bg_color, text_color, html_class, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.ribbon", "table_name": ""}
+{"text": "What business logic is in pos.details.wizard?", "response": "To use the pos.details.wizard model, you need to provide values for required fields: start_date, end_date. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.details.wizard", "table_name": ""}
+{"text": "What are the technical details of sale.order.option?", "response": "The sale.order.option model is defined in module: sale_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.order.option", "table_name": ""}
+{"text": "What are the relationships in mail.compose.message?", "response": "The mail.compose.message model has 13 relational fields: parent_id -> mail.message; template_id -> mail.template; attachment_ids -> ir.attachment; author_id -> res.partner; subtype_id -> mail.message.subtype; mail_activity_type_id -> mail.activity.type; partner_ids -> res.partner; mail_server_id -> ir.mail_server; mass_mailing_id -> mailing.mailing; campaign_id -> utm.campaign; mailing_list_ids -> mailing.list; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids, partner_ids, mailing_list_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.compose.message", "table_name": ""}
+{"text": "Show me the fields of pmps.adv.wizard.", "response": "The pmps.adv.wizard model has 10 fields: product_ids, product_attr_ids, specific_product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 2, many2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pmps.adv.wizard", "table_name": ""}
+{"text": "Can you explain the purpose of base.language.import?", "response": "The base.language.import model represents Language Import in the ERP system. It contains 12 fields and is used to manage language import data. Key fields include: name, code, data, filename, overwrite, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.language.import", "table_name": ""}
+{"text": "What is the report.equip3_pos_report.report_pos_payment model?", "response": "The report.equip3_pos_report.report_pos_payment model represents POS Payment Report in the ERP system. It contains 3 fields and is used to manage pos payment report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_pos_report.report_pos_payment", "table_name": ""}
+{"text": "What are common use cases for account.petty.cash.report?", "response": "To use the account.petty.cash.report model, you need to provide values for required fields: none. Readonly fields: name, custodian_id, main_cash_account_id, amount, balance, virtual_balance, company_id, branch_id, effective_date, create_uid, create_date, expense_amount, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.petty.cash.report", "table_name": ""}
+{"text": "Show me the fields of mail.resend.cancel.", "response": "The mail.resend.cancel model has 9 fields: model, help_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.resend.cancel", "table_name": ""}
+{"text": "What business logic is in pos.tracking.client?", "response": "To use the pos.tracking.client model, you need to provide values for required fields: none. Readonly fields: user_id, number, action, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.tracking.client", "table_name": ""}
+{"text": "What models are connected to report.mrp.report_bom_structure?", "response": "The report.mrp.report_bom_structure model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.mrp.report_bom_structure", "table_name": ""}
+{"text": "What models are connected to team.customer.segment?", "response": "The team.customer.segment model has 4 relational fields: team_id -> crm.team; rfm_segment_id -> setu.rfm.segment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "team.customer.segment", "table_name": ""}
+{"text": "Describe the field structure of customer.order.dic.", "response": "The customer.order.dic model has 10 fields: report_id, list_order, saleperson, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, one2many: 1, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "customer.order.dic", "table_name": ""}
+{"text": "Describe the field structure of ir.demo_failure.", "response": "The ir.demo_failure model has 10 fields: module_id, error, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.demo_failure", "table_name": ""}
+{"text": "Describe the field structure of queue.jobs.to.done.", "response": "The queue.jobs.to.done model has 8 fields: job_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "queue.jobs.to.done", "table_name": ""}
+{"text": "What models are connected to mail.bot?", "response": "The mail.bot model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.bot", "table_name": ""}
+{"text": "What are the available fields for intrawarehouse.transfer?", "response": "The intrawarehouse.transfer model has 8 fields: interawarehouse_transfer_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "What modules define stock.production.lot?", "response": "The stock.production.lot model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.production.lot", "table_name": ""}
+{"text": "Tell me about the account.invoice.exchange.approval.wizard model.", "response": "The account.invoice.exchange.approval.wizard model represents account.invoice.exchange.approval.wizard in the ERP system. It contains 8 fields and is used to manage account.invoice.exchange.approval.wizard data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.invoice.exchange.approval.wizard", "table_name": ""}
+{"text": "How to query sh.tv.top.vendor.wizard data?", "response": "To use the sh.tv.top.vendor.wizard model, you need to provide values for required fields: date_from, date_to, no_of_top_item, currency_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.tv.top.vendor.wizard", "table_name": ""}
+{"text": "What fields does base_import.tests.models.char.readonly have?", "response": "The base_import.tests.models.char.readonly model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.char.readonly", "table_name": ""}
+{"text": "What operations can I perform on base_import.tests.models.m2o.related?", "response": "To use the base_import.tests.models.m2o.related 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base_import.tests.models.m2o.related", "table_name": ""}
+{"text": "What operations can I perform on repair.order.make_invoice?", "response": "To use the repair.order.make_invoice 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "repair.order.make_invoice", "table_name": ""}
+{"text": "How does pos.coupon.apply.code relate to other models?", "response": "The pos.coupon.apply.code model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.coupon.apply.code", "table_name": ""}
+{"text": "How do I use the setu.rfm.score model?", "response": "To use the setu.rfm.score model, you need to provide values for required fields: none. Readonly fields: total_customers, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.rfm.score", "table_name": ""}
+{"text": "List all fields in the pos.product.attribute model.", "response": "The pos.product.attribute model has 9 fields: sequence, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.product.attribute", "table_name": ""}
+{"text": "What operations can I perform on cust.credit.limit.report.wizard?", "response": "To use the cust.credit.limit.report.wizard model, you need to provide values for required fields: branch_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cust.credit.limit.report.wizard", "table_name": ""}
+{"text": "Show me the relational structure of account.setup.bank.manual.config.", "response": "The account.setup.bank.manual.config model has 10 relational fields: res_partner_bank_id -> res.partner.bank; linked_journal_id -> account.journal; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users; partner_id -> res.partner; bank_id -> res.bank; currency_id -> res.currency; company_id -> res.company; journal_id -> account.journal. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.setup.bank.manual.config", "table_name": ""}
+{"text": "How to query mr_line.internal_transfer_line data?", "response": "To use the mr_line.internal_transfer_line model, you need to provide values for required fields: qty_transfer. Readonly fields: no, virtual_available, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mr_line.internal_transfer_line", "table_name": ""}
+{"text": "List all fields in the project.sale.line.employee.map model.", "response": "The project.sale.line.employee.map model has 14 fields: project_id, employee_id, sale_line_id, company_id, timesheet_product_id, price_unit, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.sale.line.employee.map", "table_name": ""}
+{"text": "What methods are available in project.task.type.delete.wizard?", "response": "The project.task.type.delete.wizard model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "project.task.type.delete.wizard", "table_name": ""}
+{"text": "Can you explain the purpose of hour.group?", "response": "The hour.group model represents Hour Group in the ERP system. It contains 12 fields and is used to manage hour group data. Key fields include: name, start_hour, end_hour, active, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "hour.group", "table_name": ""}
+{"text": "What are the relationships in sale.data.margin.line?", "response": "The sale.data.margin.line model has 4 relational fields: margin_id -> sale.data.margin; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.data.margin.line", "table_name": ""}
+{"text": "Can you explain the purpose of initial.balance.line?", "response": "The initial.balance.line model represents initial Balance Sheet in the ERP system. It contains 17 fields and is used to manage initial balance sheet data. Key fields include: name, report_name, account_id, company_id, currency_id, debit_amount, credit_amount, balance_amount, period_id, valid_value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "initial.balance.line", "table_name": ""}
+{"text": "Describe the implementation of stock.backorder.confirmation.line.", "response": "The stock.backorder.confirmation.line model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.backorder.confirmation.line", "table_name": ""}
+{"text": "What business logic is in project.tags?", "response": "To use the project.tags 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.tags", "table_name": ""}
+{"text": "List all fields in the pos.tag model.", "response": "The pos.tag model has 12 fields: name, color, is_return_reason, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, boolean: 1, many2one: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.tag", "table_name": ""}
+{"text": "What are the available fields for restaurant.table?", "response": "The restaurant.table model has 17 fields: name, floor_id, shape, position_h, position_v, width, height, seats, color, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 3, selection: 1, float: 4, integer: 2, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "restaurant.table", "table_name": ""}
+{"text": "What data can be stored in crm.phonecall?", "response": "The crm.phonecall model has 46 fields: date_action_last, date_action_next, create_date, team_id, user_id, partner_id, company_id, description, state, email_from, date_open, name, active, duration, tag_ids, partner_phone, partner_mobile, priority, date_closed, date, opportunity_id, direction, campaign_id, source_id, medium_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: datetime: 8, many2one: 11, text: 1, selection: 3, char: 5, boolean: 6, float: 1, many2many: 3, one2many: 3, integer: 5.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.phonecall", "table_name": ""}
+{"text": "Can you explain the purpose of product.public.category?", "response": "The product.public.category model represents Website Product Category in the ERP system. It contains 29 fields and is used to manage website product category data. Key fields include: name, parent_id, parent_path, child_id, parents_and_self, sequence, website_description, product_tmpl_ids, Minimum_amount, amount_footer, image_1920, image_1024, image_512, image_256, image_128, is_seo_optimized, website_meta_title, website_meta_description, website_meta_keywords, website_meta_og_img, seo_name, website_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.public.category", "table_name": ""}
+{"text": "Show me the fields of sale.order.repair.line.", "response": "The sale.order.repair.line model has 11 fields: repair_id, product_id, quantity, location_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.order.repair.line", "table_name": ""}
+{"text": "Which fields in wizard.scrap.order.report are computed?", "response": "The wizard.scrap.order.report model is defined in module: eq_scrap_order_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "wizard.scrap.order.report", "table_name": ""}
+{"text": "What operations can I perform on mail.alias?", "response": "To use the mail.alias model, you need to provide values for required fields: alias_model_id, alias_defaults, alias_contact. Readonly fields: alias_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.alias", "table_name": ""}
+{"text": "What business logic is in customer.voucher?", "response": "To use the customer.voucher model, you need to provide values for required fields: none. Readonly fields: name, state, start_date, end_date, reward_type, discount_line_product_id, expired_date, expiration_period, customer_voucher_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "customer.voucher", "table_name": ""}
+{"text": "Can you explain the purpose of ir.qweb?", "response": "The ir.qweb model represents Qweb in the ERP system. It contains 3 fields and is used to manage qweb data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb", "table_name": ""}
+{"text": "How is print.purchase.tender.report used in the system?", "response": "The print.purchase.tender.report model represents Purchase Tender Pdf/XLS Report in the ERP system. It contains 9 fields and is used to manage purchase tender pdf/xls report data. Key fields include: selection, purchase_agreement_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "print.purchase.tender.report", "table_name": ""}
+{"text": "What are the relationships in account.move.template.line?", "response": "The account.move.template.line model has 26 relational fields: move_id -> account.move.template; journal_id -> account.journal; company_id -> res.company; company_currency_id -> res.currency; tax_fiscal_country_id -> res.country; account_id -> account.account; account_root_id -> account.root; currency_id -> res.currency; partner_id -> res.partner; product_uom_id -> uom.uom; product_id -> product.product; product_uom_category_id -> uom.category; reconcile_model_id -> account.reconcile.model; payment_id -> account.payment; statement_line_id -> account.bank.statement.line; statement_id -> account.bank.statement; tax_ids -> account.tax; tax_line_id -> account.tax; tax_group_id -> account.tax.group; tax_repartition_line_id -> account.tax.repartition.line; tax_tag_ids -> account.account.tag; full_reconcile_id -> account.full.reconcile; analytic_account_id -> account.analytic.account; analytic_tag_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_ids, tax_tag_ids, analytic_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.move.template.line", "table_name": ""}
+{"text": "Show me the relational structure of website.sale.extra.field.", "response": "The website.sale.extra.field model has 4 relational fields: website_id -> website; field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.sale.extra.field", "table_name": ""}
+{"text": "Tell me about the overhead.time model.", "response": "The overhead.time model represents Overhead Time Management in the ERP system. It contains 10 fields and is used to manage overhead time management data. Key fields include: product, cost_hr, mrp_workcenter_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "overhead.time", "table_name": ""}
+{"text": "What is the mailing.mailing model?", "response": "The mailing.mailing model represents Mass Mailing in the ERP system. It contains 90 fields and is used to manage mass mailing data. Key fields include: active, subject, preview, email_from, sent_date, schedule_date, body_arch, body_html, attachment_ids, keep_archives, campaign_id, source_id, medium_id, state, color, user_id, mailing_type, reply_to_mode, reply_to, mailing_model_real, mailing_model_id, mailing_model_name, mailing_domain, mail_server_id, contact_list_ids, contact_ab_pc, unique_ab_testing, kpi_mail_required, mailing_trace_ids, total, scheduled, expected, ignored, sent, delivered, opened, clicked, replied, bounced, failed, received_ratio, opened_ratio, replied_ratio, bounced_ratio, clicks_ratio, next_departure, use_leads, crm_lead_count, sale_quotation_count, sale_invoiced_amount, rfm_segment_id, lang, model_object_field, sub_object, sub_model_object_field, null_value, copyvalue, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, name.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mailing.mailing", "table_name": ""}
+{"text": "What does the ir.actions.act_window_close model represent?", "response": "The ir.actions.act_window_close model represents Action Window Close in the ERP system. It contains 14 fields and is used to manage action window close data. Key fields include: type, name, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.act_window_close", "table_name": ""}
+{"text": "How is setu.rfm.segment used in the system?", "response": "The setu.rfm.segment model represents \n        The  idea is to segment customers based on when their last purchase was, \n        how often they’ve purchased in the past, and how much they’ve spent overall. \n        All three of these measures have proven to be effective predictors of a customer's willingness to engage in marketing messages and offers.\n     in the ERP system. It contains 31 fields and is used to manage \n        the  idea is to segment customers based on when their last purchase was, \n        how often they’ve purchased in the past, and how much they’ve spent overall. \n        all three of these measures have proven to be effective predictors of a customer's willingness to engage in marketing messages and offers.\n     data. Key fields include: name, segment_description, actionable_tips, rfm_score_ids, rfm_score_syntax, rfm_score_condition, segment_rank, partner_ids, order_ids, mailing_ids, total_mailing, total_customers, total_orders, total_revenue, team_customer_segment_ids, open_lead_count, open_rfq_count, total_customers_ratio, total_orders_ratio, total_revenue_ratio, from_date, to_date, calculated_on, desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "setu.rfm.segment", "table_name": ""}
+{"text": "List all fields in the intrawarehouse.transfer model.", "response": "The intrawarehouse.transfer model has 8 fields: interawarehouse_transfer_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "List all fields in the calendar.alarm_manager model.", "response": "The calendar.alarm_manager model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "calendar.alarm_manager", "table_name": ""}
+{"text": "What are the technical details of hr.employee.base?", "response": "The hr.employee.base model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hr.employee.base", "table_name": ""}
+{"text": "How do I use the sh.purchase.bill.summary.wizard model?", "response": "To use the sh.purchase.bill.summary.wizard model, you need to provide values for required fields: sh_start_date, sh_end_date, sh_partner_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.purchase.bill.summary.wizard", "table_name": ""}
+{"text": "Describe the field structure of pos.promotion.discount.order.", "response": "The pos.promotion.discount.order model has 15 fields: active, minimum_amount, discount, discount2, multi_discount, max_discount_amount, discount_fixed_amount, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, float: 5, char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.promotion.discount.order", "table_name": ""}
+{"text": "What are common use cases for cancel.credit.limit?", "response": "To use the cancel.credit.limit model, you need to provide values for required fields: limit_id, reason. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cancel.credit.limit", "table_name": ""}
+{"text": "How is lost.product implemented technically?", "response": "The lost.product model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "lost.product", "table_name": ""}
+{"text": "What are the technical details of account.report.partner.ledger?", "response": "The account.report.partner.ledger model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.report.partner.ledger", "table_name": ""}
+{"text": "What operations can I perform on generate.closing.entries?", "response": "To use the generate.closing.entries model, you need to provide values for required fields: fiscal_year_id, closing_entry_date, journal_id, description, summary_account_id, retained_earnings_account_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "generate.closing.entries", "table_name": ""}
+{"text": "What modules define pos.promotion.discount.order?", "response": "The pos.promotion.discount.order model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.promotion.discount.order", "table_name": ""}
+{"text": "Tell me about the account.reconcile.model.line model.", "response": "The account.reconcile.model.line model represents Rules for the reconciliation model in the ERP system. It contains 24 fields and is used to manage rules for the reconciliation model data. Key fields include: model_id, match_total_amount, match_total_amount_param, rule_type, company_id, sequence, account_id, journal_id, label, amount_type, show_force_tax_included, force_tax_included, amount, amount_string, tax_ids, analytic_account_id, analytic_tag_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.reconcile.model.line", "table_name": ""}
+{"text": "Describe the field structure of all.redeem.rule.", "response": "The all.redeem.rule model has 12 fields: name, min_amt, max_amt, reward_amt, loyality_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 4, many2one: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "all.redeem.rule", "table_name": ""}
+{"text": "What models are connected to analytic.sale.order.line?", "response": "The analytic.sale.order.line model has 9 relational fields: product_id -> product.product; product_uom -> uom.uom; analytic_tag_ids -> account.analytic.tag; tax_ids -> account.tax; subscription_product_line_id -> account.analytic.account; not_subscription_product_line_id -> account.analytic.account; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, tax_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "analytic.sale.order.line", "table_name": ""}
+{"text": "How is cust.credit.limit.data used in the system?", "response": "The cust.credit.limit.data model represents cust.credit.limit.data in the ERP system. It contains 11 fields and is used to manage cust.credit.limit.data data. Key fields include: company_id, branch_id, partner_id, cust_credit_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "cust.credit.limit.data", "table_name": ""}
+{"text": "What does the account.analytic.tag model represent?", "response": "The account.analytic.tag model represents Analytic Tags in the ERP system. It contains 39 fields and is used to manage analytic tags data. Key fields include: color, active, active_analytic_distribution, analytic_distribution_ids, name, company_id, branch_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.analytic.tag", "table_name": ""}
+{"text": "What does the sale.order model represent?", "response": "The sale.order model represents Sales Order in the ERP system. It contains 289 fields and is used to manage sales order data. Key fields include: origin, client_order_ref, reference, is_expired, require_signature, require_payment, create_date, user_id, pricelist_id, currency_id, invoice_count, invoice_ids, invoice_status, amount_by_group, currency_rate, fiscal_position_id, team_id, signature, signed_by, signed_on, amount_undiscounted, type_name, transaction_ids, authorized_transaction_ids, show_update_pricelist, tag_ids, applied_coupon_ids, generated_coupon_ids, reward_amount, no_code_promo_program_ids, code_promo_program_id, promo_code, sale_order_option_ids, purchase_order_count, incoterm, picking_policy, picking_ids, delivery_count, procurement_group_id, effective_date, expected_date, json_popover, show_json_popover, website_order_line, cart_quantity, only_services, is_abandoned_cart, cart_recovery_email_sent, website_id, conversation_id, internal_id, inter_transfer_count, client_order_id, discount_amt, discount_amt_line, warranty_sale, recurring_rule_type, recurring_interval, delivery_message, delivery_rating_success, delivery_set, recompute_delivery_price, is_all_service, is_process_rma, merged, name, parent_saleorder_id, order_revised_count, so_number, margin, margin_percent, mrp_production_count, note, report_grids, grid_product_tmpl_id, grid_update, grid, tasks_ids, tasks_count, visible_project, project_ids, sh_sale_barcode_mobile, sh_sale_bm_is_cont_scan, partner_credit_conform, sh_purchase_count, sh_so_po_is_show_so_to_po_btn_flag, apply_manual_currency_exchange, manual_currency_exchange_rate, company_currency_id, active_manual_currency_rate, warning_stock, opportunity_id, report_template_id1, report_template_id, amount_to_text, timesheet_ids, timesheet_count, project_id, timesheet_encode_uom_id, timesheet_total_duration, rfm_segment_id, amount_delivery, order_credit_points, order_redeem_points, redeem_value, is_from_website, loyalty_point_credit, order_source, driver_id, order_driver_message_ids, payment_status_with_driver, latitude, longitude, distance_btn_2_loc, sale_order_comm_ids, commission_calc, commission_pay_on, stage_id, order_line_count, date_order, validity_date, payment_term_id, sale_order_template_id, sale_state, delivered_state, sale_state_1, state_2, revised_state, approval_matrix_state, approval_matrix_state_1, branch_id, account_tag, account_tag_ids, analytic_account_id, approving_matrix_sale_id, approved_matrix_ids, is_customer_approval_matrix, hide_proforma, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, is_quotation_cancel, company_id, deduction_ids, analytic_accounting, terms_conditions_id, group_multi_do, is_single_warehouse, is_single_delivery_date, commitment_date, revised_sale_order_ids, revised_sale_order_id, is_revision_so, is_print_report, qty_delivered, count_delivered, multilevel_disc, multi_discount, discount_method, discount_amount, date_confirm, is_sale_order, partner_name, is_hidden_button, lock_sale_order, readonly_disc, readonly_multi, brand, partner_invoice_id, partner_shipping_id, reject_reason, sale_fully_delivered, sale_partially_delivery, sale_fully_paid, sale_partially_paid, sale_hidden_compute_field, date_kanban, is_down_payment, down_payment_amount, total_amount_without_dp, carrier_id, amount_untaxed, amount_tax, amount_total, order_line, discount_type, city_id, state_id, show_mobile, is_external_link, tax_discount_policy, discount_amt_before, discount_amt_line_before, amount_subtotal, warehouse_id, warehouse_new_id, delivery_state, payment_status_driver, approving_matrix_limit_id, approved_matrix_limit_ids, is_over_limit_validation, is_limit_matrix_filled, is_direct_confirm, limit_approval_matrix_line_id, is_approve_button_limit, limit_matrix_state, limit_matrix_state_1, limit_matrix_state_2, sale_limit_state, sale_limit_state_1, sale_limit_state_2, sale_limit_state_3, sale_limit_state_4, sale_limit_state_5, approval_matrix_state_2, approval_matrix_state_3, approval_matrix_state_4, approval_matrix_state_5, approval_matrix_state_6, approval_matrix_state_7, approval_matrix_state_8, approval_matrix_state_9, creditlim, hide_button_revise, lock_order_line, have_available_customer_voucher, customer_voucher_used_ids, cashback_line_ids, show_cashback, cn_cashback_ids, cn_cashback_count, title, partner_id, book_order, ean13, pos_config_id, pos_location_id, delivery_date, delivered_date, delivery_address, delivery_phone, payment_partial_amount, payment_partial_method_id, insert, state, pos_branch_id, pos_order_id, is_self_pickup, is_dropship, purchase_request_ids, purchase_request_count, remark, 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, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.order", "table_name": ""}
+{"text": "What modules define account.root?", "response": "The account.root model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.root", "table_name": ""}
+{"text": "List all fields in the cancel.credit.limit model.", "response": "The cancel.credit.limit model has 9 fields: limit_id, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, text: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "cancel.credit.limit", "table_name": ""}
+{"text": "Describe the implementation of sh.purchase.tags.", "response": "The sh.purchase.tags model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.tags", "table_name": ""}
+{"text": "Describe the field structure of milestone.contract.template.line.", "response": "The milestone.contract.template.line model has 11 fields: template_id, checklist_template_id, name, contract_term, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 2, float: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "milestone.contract.template.line", "table_name": ""}
+{"text": "What are the available fields for website.rewrite?", "response": "The website.rewrite model has 15 fields: name, website_id, active, url_from, route_id, url_to, redirect_type, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 4, boolean: 1, selection: 1, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "website.rewrite", "table_name": ""}
+{"text": "What models are connected to website.visitor?", "response": "The website.visitor model has 13 relational fields: website_id -> website; partner_id -> res.partner; country_id -> res.country; lang_id -> res.lang; website_track_ids -> website.track; page_ids -> website.page; last_visited_page_id -> website.page; livechat_operator_id -> res.partner; mail_channel_ids -> mail.channel; lead_ids -> crm.lead; product_ids -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: page_ids, lead_ids, product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.visitor", "table_name": ""}
+{"text": "How to query account.pettycash data?", "response": "To use the account.pettycash model, you need to provide values for required fields: cash_journal, name, custodian, journal, amount. Readonly fields: number, name, custodian, main_cash_account_id, journal, balance, virtual_balance, company_id, create_uid, create_date, move_id, is_custodian_user, custodian_partner, is_replenished, 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, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.pettycash", "table_name": ""}
+{"text": "How does milestone.contract.template.checklist relate to other models?", "response": "The milestone.contract.template.checklist model has 3 relational fields: template_id -> milestone.contract.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "milestone.contract.template.checklist", "table_name": ""}
+{"text": "How to query publisher_warranty.contract data?", "response": "To use the publisher_warranty.contract model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "publisher_warranty.contract", "table_name": ""}
+{"text": "How do I use the ks_custom_report.ks_report model?", "response": "To use the ks_custom_report.ks_report model, you need to provide values for required fields: name, ks_cr_menu_name, ks_cr_top_menu_id, ks_cr_menu_priority. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_custom_report.ks_report", "table_name": ""}
+{"text": "What are common use cases for ir.model.relation?", "response": "To use the ir.model.relation model, you need to provide values for required fields: name, model, module. Readonly fields: id, display_name, create_uid, write_uid, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.model.relation", "table_name": ""}
+{"text": "Which fields in credit.limit.approval are computed?", "response": "The credit.limit.approval model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "credit.limit.approval", "table_name": ""}
+{"text": "What are the available fields for sh.mrp.text?", "response": "The sh.mrp.text model has 13 fields: product_id, sh_message, mrp_quality_point_id, mrp_id, workorder_id, text_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, text: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.mrp.text", "table_name": ""}
+{"text": "What models are connected to debt.collection.report?", "response": "The debt.collection.report model has 7 relational fields: partner_ids -> res.partner; user_ids -> res.users; journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, user_ids, journal_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "debt.collection.report", "table_name": ""}
+{"text": "What is the ir.actions.server model?", "response": "The ir.actions.server model represents Server Action in the ERP system. It contains 45 fields and is used to manage server action data. Key fields include: name, type, sequence, model_id, model_name, code, child_ids, crud_model_id, crud_model_name, link_field_id, fields_lines, groups_id, mass_edit_line_ids, mass_edit_apply_domain_in_lines, mass_edit_message, partner_ids, channel_ids, template_id, activity_type_id, activity_summary, activity_note, activity_date_deadline_range, activity_date_deadline_range_type, activity_user_type, activity_user_id, activity_user_field_name, usage, state, sms_template_id, sms_mass_keep_log, xml_id, website_path, website_url, website_published, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.server", "table_name": ""}
+{"text": "Describe the account.move.template model in Odoo.", "response": "The account.move.template model represents Journal Entry Template in the ERP system. It contains 68 fields and is used to manage journal entry template data. Key fields include: name, date, ref, narration, state, posted_before, move_type, type_name, to_check, journal_id, suitable_journal_ids, company_id, company_currency_id, currency_id, line_ids, partner_id, payment_id, statement_line_id, amount_untaxed, amount_tax, amount_total, amount_residual, amount_untaxed_signed, amount_tax_signed, amount_total_signed, amount_residual_signed, amount_by_group, payment_state, reversed_entry_id, reversal_move_id, invoice_filter_type_domain, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.move.template", "table_name": ""}
+{"text": "How is website.multi.mixin implemented technically?", "response": "The website.multi.mixin model is defined in module: website. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.multi.mixin", "table_name": ""}
+{"text": "What is the warranty.history model?", "response": "The warranty.history model represents Warranty History in the ERP system. It contains 14 fields and is used to manage warranty history data. Key fields include: date_renewal, warranty_renewal_date, warranty_renew_end_date, renewal_cost, paid, free, warranty_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "warranty.history", "table_name": ""}
+{"text": "Tell me about the sms.resend.recipient model.", "response": "The sms.resend.recipient model represents Resend Notification in the ERP system. It contains 14 fields and is used to manage resend notification data. Key fields include: sms_resend_id, notification_id, resend, failure_type, partner_id, partner_name, sms_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sms.resend.recipient", "table_name": ""}
+{"text": "How do I use the account.voucher.line model?", "response": "To use the account.voucher.line model, you need to provide values for required fields: name, voucher_id, uom_id, account_id, price_unit, quantity. Readonly fields: price_subtotal, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.voucher.line", "table_name": ""}
+{"text": "What business logic is in ram.tags?", "response": "To use the ram.tags 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ram.tags", "table_name": ""}
+{"text": "What is the advertisement.images model?", "response": "The advertisement.images model represents advertisement.images in the ERP system. It contains 21 fields and is used to manage advertisement.images data. Key fields include: name, sequence, description, ad_image, image_type, file_type, video_type, ad_video, video_url, ace_video_url, is_youtube_url, url, ad_video_fname, image_duration, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "advertisement.images", "table_name": ""}
+{"text": "What is the sale.order.template.line model?", "response": "The sale.order.template.line model represents Quotation Template Line in the ERP system. It contains 16 fields and is used to manage quotation template line data. Key fields include: sequence, sale_order_template_id, company_id, name, product_id, product_uom_qty, product_uom_id, product_uom_category_id, display_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.order.template.line", "table_name": ""}
+{"text": "What models are connected to purchase.change.request.line?", "response": "The purchase.change.request.line model has 4 relational fields: purchase_chn_req_id -> purchase.change.request; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.change.request.line", "table_name": ""}
+{"text": "Which fields in sale.order.cancel are computed?", "response": "The sale.order.cancel model is defined in module: sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.order.cancel", "table_name": ""}
+{"text": "What data can be stored in sh.sale.category.xls?", "response": "The sh.sale.category.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.sale.category.xls", "table_name": ""}
+{"text": "Which fields in pos.call.log are computed?", "response": "The pos.call.log model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.call.log", "table_name": ""}
+{"text": "What methods are available in account.pettycash.analysis?", "response": "The account.pettycash.analysis model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.pettycash.analysis", "table_name": ""}
+{"text": "Describe the report.sh_purchase_reports.sh_po_product_indent_doc model in Odoo.", "response": "The report.sh_purchase_reports.sh_po_product_indent_doc model represents Purchase product indent report abstract model in the ERP system. It contains 3 fields and is used to manage purchase product indent report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_po_product_indent_doc", "table_name": ""}
+{"text": "Describe the field structure of salesperson.tracking.history.", "response": "The salesperson.tracking.history model has 11 fields: name, marker, history_data, tracking_history_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, binary: 1, html: 1, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "salesperson.tracking.history", "table_name": ""}
+{"text": "What is the pos.promotion.price model?", "response": "The pos.promotion.price model represents Promotion sale off in the ERP system. It contains 12 fields and is used to manage promotion sale off data. Key fields include: active, product_id, minimum_quantity, price_down, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.promotion.price", "table_name": ""}
+{"text": "What are common use cases for sms.resend?", "response": "To use the sms.resend model, you need to provide values for required fields: mail_message_id. Readonly fields: mail_message_id, has_cancel, has_insufficient_credit, has_unregistered_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sms.resend", "table_name": ""}
+{"text": "What modules define pos.loyalty.reward.product?", "response": "The pos.loyalty.reward.product model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.loyalty.reward.product", "table_name": ""}
+{"text": "How does report.dynamic_accounts_report.general_ledger relate to other models?", "response": "The report.dynamic_accounts_report.general_ledger model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.general_ledger", "table_name": ""}
+{"text": "What are the available fields for asp.asm.stock.line?", "response": "The asp.asm.stock.line model has 18 fields: name, product_id, location_id, filter_location_ids, product_qty, counted, difference_qty, asp_asm_stock_id, check_required_field, category_uom_id, uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 7, many2many: 1, float: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "asp.asm.stock.line", "table_name": ""}
+{"text": "What are the relationships in sh.purchase.bill.summary.xls?", "response": "The sh.purchase.bill.summary.xls model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.bill.summary.xls", "table_name": ""}
+{"text": "Which fields in report.sh_sale_reports.sh_sales_product_profit_doc are computed?", "response": "The report.sh_sale_reports.sh_sales_product_profit_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_sales_product_profit_doc", "table_name": ""}
+{"text": "Describe the stock.inventory.wizard model in Odoo.", "response": "The stock.inventory.wizard model represents stock.inventory.wizard in the ERP system. It contains 8 fields and is used to manage stock.inventory.wizard data. Key fields include: wizard_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.inventory.wizard", "table_name": ""}
+{"text": "What data can be stored in sale.order.cancel?", "response": "The sale.order.cancel model has 10 fields: order_id, display_invoice_alert, display_delivery_alert, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, boolean: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.order.cancel", "table_name": ""}
+{"text": "Describe the implementation of report.sh_sale_reports.sh_sale_by_category_doc.", "response": "The report.sh_sale_reports.sh_sale_by_category_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_sale_by_category_doc", "table_name": ""}
+{"text": "What data can be stored in base_import.tests.models.char.stillreadonly?", "response": "The base_import.tests.models.char.stillreadonly model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.char.stillreadonly", "table_name": ""}
+{"text": "What does the product.supplierinfo.approval model represent?", "response": "The product.supplierinfo.approval model represents product.supplierinfo.approval in the ERP system. It contains 20 fields and is used to manage product.supplierinfo.approval data. Key fields include: sequence, sequence2, user_ids, minimum_approver, status, time, feedback, approved, approval, last_approved, time_stamp, user_approved_ids, supplier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.supplierinfo.approval", "table_name": ""}
+{"text": "What are common use cases for product.ratio.line?", "response": "To use the product.ratio.line model, you need to provide values for required fields: uom_id, product_tmpl_id, ratio. Readonly fields: description, uom_ref_id, product_variant_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.ratio.line", "table_name": ""}
+{"text": "What models are connected to snailmail.confirm.invoice?", "response": "The snailmail.confirm.invoice model has 3 relational fields: invoice_send_id -> account.invoice.send; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "snailmail.confirm.invoice", "table_name": ""}
+{"text": "How to create records in export.partner.csv?", "response": "To use the export.partner.csv model, you need to provide values for required fields: none. Readonly fields: product_id_attachment_id, product_id_csv_created, 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, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "export.partner.csv", "table_name": ""}
+{"text": "What data can be stored in ir.module.module?", "response": "The ir.module.module model has 41 fields: name, category_id, shortdesc, summary, description, description_html, author, maintainer, contributors, website, installed_version, latest_version, published_version, url, sequence, dependencies_id, exclusion_ids, auto_install, state, demo, license, menus_by_module, reports_by_module, views_by_module, application, icon, icon_image, to_buy, has_iap, version_status, imported, local_updatable, image_ids, is_installed_on_current_website, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 12, many2one: 3, text: 5, html: 1, integer: 2, one2many: 3, boolean: 8, selection: 3, binary: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.module.module", "table_name": ""}
+{"text": "What foreign keys exist in vendor.deposit.line.reconcile?", "response": "The vendor.deposit.line.reconcile model has 5 relational fields: deposit_reconcile_id -> account.vendor.deposit.reconcile; invoice_id -> account.move; filter_move_ids -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_move_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "vendor.deposit.line.reconcile", "table_name": ""}
+{"text": "Describe the field structure of sh.purchase.category.xls.", "response": "The sh.purchase.category.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.purchase.category.xls", "table_name": ""}
+{"text": "Show me the fields of fast.financial.report.query.", "response": "The fast.financial.report.query model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "fast.financial.report.query", "table_name": ""}
+{"text": "Can you explain the purpose of report_excel_import_wizard?", "response": "The report_excel_import_wizard model represents report_excel_import Wizard in the ERP system. It contains 8 fields and is used to manage report_excel_import wizard data. Key fields include: data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report_excel_import_wizard", "table_name": ""}
+{"text": "What are the available fields for report.equip3_accounting_operation.report_statement_temp?", "response": "The report.equip3_accounting_operation.report_statement_temp model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_accounting_operation.report_statement_temp", "table_name": ""}
+{"text": "Describe the field structure of purchase.request.warning.line.", "response": "The purchase.request.warning.line model has 11 fields: warning_id, product_id, purchase_req_budget, realized_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.request.warning.line", "table_name": ""}
+{"text": "How to query budget.change.req data?", "response": "To use the budget.change.req model, you need to provide values for required fields: requested_id, budget_std_id, date, state, company_id. Readonly fields: name, state, approval_matrix, is_allowed_to_approval_matrix, approval_matrix_line_id, is_approve_button, company_id, currency_id, state1, state2, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "budget.change.req", "table_name": ""}
+{"text": "Describe the field structure of ir.sequence.", "response": "The ir.sequence model has 20 fields: name, code, implementation, active, prefix, suffix, number_next, number_next_actual, number_increment, padding, company_id, use_date_range, date_range_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, selection: 1, boolean: 2, integer: 5, many2one: 3, one2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.sequence", "table_name": ""}
+{"text": "Describe the many2many relations for l10n_id_efaktur.efaktur.range.", "response": "The l10n_id_efaktur.efaktur.range model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "l10n_id_efaktur.efaktur.range", "table_name": ""}
+{"text": "What fields does invoice.payment.report.xls have?", "response": "The invoice.payment.report.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "invoice.payment.report.xls", "table_name": ""}
+{"text": "What are the available fields for account.bank.statement.line?", "response": "The account.bank.statement.line model has 362 fields: move_id, statement_id, sequence, account_number, partner_name, transaction_type, payment_ref, amount, amount_currency, foreign_currency_id, amount_residual, currency_id, partner_id, payment_ids, is_reconciled, state, country_code, move_name, unique_import_id, branch_id, transaction_date, pos_branch_id, voucher_id, pos_session_id, pos_cash_type, pos_statement_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, highest_name, ref, move_type, type_name, suitable_journal_ids, company_id, user_id, is_move_sent, payment_state, invoice_user_id, invoice_origin, invoice_source_email, preferred_payment_method_id, debit_origin_id, debit_note_ids, debit_note_count, edi_document_ids, edi_state, edi_error_count, edi_web_services_to_process, edi_show_cancel_button, edi_show_abandon_cancel_button, edi_error_message, edi_blocking_level, loan_line_id, loan_id, attn, signature, journal_bank_id, payment_proof, tax_payment_date, payment_fields_boolean, ppn, pph, tax_paid_status, file_name, payment_date, tax_payment_move_id, tax_pay_seprately_amount, is_edit_data, name, asset_depreciation_ids, transaction_ids, authorized_transaction_ids, purchase_vendor_bill_id, purchase_id, sh_invoice_recurring_order_id, period_id, fiscal_year, stock_move_id, stock_valuation_layer_ids, auto_reverse, auto_reverse_date, auto_reverse_journal_id, auto_reverse_date_mode, auto_reversal_entry_date, auto_reversed, is_prepayment, to_delete_from_svl, pos_order_ids, team_id, partner_shipping_id, is_consignment, consignment_start_date, consignment_end_date, consignment_pos_ids, l10n_id_tax_number, l10n_id_attachment_id, l10n_id_csv_created, l10n_id_need_kode_transaksi, landed_costs_ids, landed_costs_visible, website_id, is_line, discount_method, discount_amount, discount_type, discount_amt, amount_untaxed, discount_amt_line, discount_account_id, discount_amount_line, warranty_invoice, warranty_reg_id, related_project_id, show_intrest, interest, check_date, check_month, repair_ids, sh_invoice_barcode_mobile, sh_invoice_bm_is_cont_scan, target_commission_id, commission_count, apply_manual_currency_exchange, active_manual_currency_rate, down_payment_amount, total_down_payment_amount, is_down_payment, down_payment_purchase_id, report_template_id1, report_template_id, amount_to_text, timesheet_ids, timesheet_count, approval_matrix_id, is_invoice_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state1, state2, is_register_payment_done, analytic_group_ids, invoice_origin_id, invoice_origin_date, reason, ref_no, request_partner_id, is_fiscal_book_exclude, received_date, visible_received_date, to_approve_state_payment_count, show_name_warning, date, posted_before, to_check, journal_id, company_currency_id, line_ids, commercial_partner_id, partner_bank_id, payment_reference, payment_id, statement_line_id, amount_tax, amount_tax2, subtotal_amount, amount_total, amount_untaxed_signed, amount_tax_signed, amount_total_signed, amount_residual_signed, amount_by_group, tax_cash_basis_rec_id, tax_cash_basis_move_id, auto_post, reversed_entry_id, reversal_move_id, fiscal_position_id, invoice_date, invoice_date_due, invoice_payment_term_id, invoice_line_ids, invoice_incoterm_id, display_qr_code, qr_code_method, invoice_outstanding_credits_debits_widget, invoice_has_outstanding, invoice_payments_widget, invoice_vendor_bill_id, invoice_partner_display_name, invoice_cash_rounding_id, invoice_filter_type_domain, bank_partner_id, invoice_has_matching_suspense_amount, tax_lock_date_message, has_reconciled_entries, show_reset_to_draft_button, restrict_mode_hash_table, secure_sequence_number, inalterable_hash, string_to_hash, mr_show_analytic_account, journal_entries_template, analytic_tag_dynamic, credit_note_expiry_date, expiry_date, approvers_ids, approved_user_ids, internal_tf_id, reversal_avail, date_id, is_record_created, is_merge, is_merge_to, new_invoice_id, count_merged_invoice, is_button_update_invisible, narration, multi_discount, is_intercompany_transaction, account_asset_id, customer_deposit_ids, vendor_deposit_ids, status_code, nomor_seri, ebupot_id, code, check, check_invisible, total_tax_ppn, total_inv_ppn, subtotal_inv_ppn, tax_number_bupot, kode_dokumen, kode_seri, nomor_seri_bupot, check_invisible_ebupot, ebupot_template, l10n_id_replace_invoice_id, l10n_id_kode_transaksi, is_upload_djp, is_upload_djp_cn, pajak_express_id, approval_url, efaktur_url, nomor_dokumen_pendukung, hide_button_upload, hide_button_upload_cn, tipe_pembayaran, keterangan_tambahan, uang_muka, uang_muka_ppn, uang_muka_ppnbm, signature_country_id, signature_city_id, nomor_seri_domain, current_rate, is_company_curr, current_inverse_rate, inverse_rate_visible, tax_rate, taxes_base_price, sales_times_tax_rate, tax_applies_on, manual_currency_exchange_inverse_rate, manual_currency_exchange_rate, currency_revaluation_id, children_ids, currency_revaluation_ref_id, currency_revaluation_count, pettycash_id, is_petty_cash_voucher, sale_order_reference_id, filter_sale_order_reference_ids, exchange_id, exchange_stage, exchange_date, exchange_status, assembly_id, stock_scrap_id, kitchen_id, purchase_order_id, swo, swo_ids, amount_swo, is_services_orders, finish_good_rework_id, sale_order_ids, filter_sale_order_ids, purchase_order_ids, filter_purchase_order_ids, picking_ids, filter_picking_ids, sale_order_ids_boolean, purchase_order_ids_boolean, picking_ids_boolean, cashback_line_ids, show_cashback, is_cn_from_cashback, so_cashback_id, is_dp, payments_date, manual_change_status_code, return_picking_ids, picking_id, nomor_seri_faktur_pajak_new, rma_id, receiving_note_names, receiving_note_dates, account_invoice_ids, origin, pos_order_id, is_from_pos_receivable, is_from_pos_cash_management, is_from_pos_cash_difference, is_from_pos_umum, is_from_pos_member, is_from_pos_member_gabungan, is_from_pos_partner, is_pkp_record, deposit_account_journal_id, create_from_session_id, inventory_id, _barcode_scanned, 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, sequence_prefix, sequence_number. Field types distribution: many2one: 92, integer: 16, char: 50, monetary: 13, float: 21, many2many: 21, boolean: 74, selection: 21, date: 18, datetime: 4, one2many: 20, text: 5, html: 4, binary: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.bank.statement.line", "table_name": ""}
+{"text": "Show me the relational structure of approval.matrix.vendor.line.", "response": "The approval.matrix.vendor.line model has 9 relational fields: approval_matrix -> approval.matrix.vendor; company_id -> res.company; branch_id -> res.branch; user_ids -> res.users; approved_users -> res.users; last_approved -> res.users; app_matrix_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.vendor.line", "table_name": ""}
+{"text": "What is the milestone.contract.template.purchase model?", "response": "The milestone.contract.template.purchase model represents Milestone Contract Purchase in the ERP system. It contains 12 fields and is used to manage milestone contract purchase data. Key fields include: purchase_order_id, name, checklist_template_id, contract_term, progress_paid, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "milestone.contract.template.purchase", "table_name": ""}
+{"text": "Describe the field structure of stock.scrap.approval.matrix.", "response": "The stock.scrap.approval.matrix model has 44 fields: name, company_id, warehouse_id, branch_id, approval_line_count, sc_approval_matrix_line_ids, 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. Field types distribution: char: 7, many2one: 11, integer: 6, one2many: 5, selection: 2, date: 2, boolean: 5, many2many: 2, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.scrap.approval.matrix", "table_name": ""}
+{"text": "What is the crm.salesperson.tracking.history model?", "response": "The crm.salesperson.tracking.history model represents crm.salesperson.tracking.history in the ERP system. It contains 11 fields and is used to manage crm.salesperson.tracking.history data. Key fields include: sales_person_name, history_date, track_lan_lng, track_hist, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.salesperson.tracking.history", "table_name": ""}
+{"text": "How is queue.job.function used in the system?", "response": "The queue.job.function model represents Job Functions in the ERP system. It contains 12 fields and is used to manage job functions data. Key fields include: name, model_id, method, channel_id, channel, retry_pattern, edit_retry_pattern, related_action, edit_related_action, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "queue.job.function", "table_name": ""}
+{"text": "How to create records in ir.qweb.field.image_url?", "response": "To use the ir.qweb.field.image_url model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.image_url", "table_name": ""}
+{"text": "How is product.template.attribute.exclusion used in the system?", "response": "The product.template.attribute.exclusion model represents Product Template Attribute Exclusion in the ERP system. It contains 10 fields and is used to manage product template attribute exclusion data. Key fields include: product_template_attribute_value_id, product_tmpl_id, value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.template.attribute.exclusion", "table_name": ""}
+{"text": "How to create records in assembly.safety.stock?", "response": "To use the assembly.safety.stock model, you need to provide values for required fields: name, company_id, warehouse_id. Readonly fields: is_branch_required, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assembly.safety.stock", "table_name": ""}
+{"text": "How is ai.memory.export.import.wizard used in the system?", "response": "The ai.memory.export.import.wizard model represents AI Memory Export/Import Wizard in the ERP system. It contains 11 fields and is used to manage ai memory export/import wizard data. Key fields include: operation, import_file, import_filename, import_mode, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ai.memory.export.import.wizard", "table_name": ""}
+{"text": "Show me the relational structure of pos.generate.efaktur.digunggung.", "response": "The pos.generate.efaktur.digunggung model has 5 relational fields: gen_efaktur_id -> pos.generate.efaktur; partner_id -> res.partner; account_move_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.generate.efaktur.digunggung", "table_name": ""}
+{"text": "How to create records in picking.return.line?", "response": "To use the picking.return.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "picking.return.line", "table_name": ""}
+{"text": "Show me the fields of account.pettycash.fund.change.", "response": "The account.pettycash.fund.change model has 18 fields: fund, fund_name, custodian, fund_amount, new_amount, payable_account, receivable_account, effective_date, do_receivable, move, is_add_balance, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, char: 2, float: 2, date: 1, boolean: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.pettycash.fund.change", "table_name": ""}
+{"text": "What are the relationships in product.uom.price?", "response": "The product.uom.price model has 4 relational fields: uom_id -> uom.uom; product_tmpl_id -> product.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.uom.price", "table_name": ""}
+{"text": "What fields does ir.config_parameter have?", "response": "The ir.config_parameter model has 9 fields: key, value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, text: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.config_parameter", "table_name": ""}
+{"text": "What does the sh.purchase.product.profit.wizard model represent?", "response": "The sh.purchase.product.profit.wizard model represents Purchase Product Profit Wizard in the ERP system. It contains 14 fields and is used to manage purchase product profit wizard data. Key fields include: sh_start_date, sh_end_date, sh_partner_ids, report_by, sh_product_ids, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.purchase.product.profit.wizard", "table_name": ""}
+{"text": "What are the relationships in report.stock.report_stock_rule?", "response": "The report.stock.report_stock_rule model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.stock.report_stock_rule", "table_name": ""}
+{"text": "How is resource.calendar.attendance implemented technically?", "response": "The resource.calendar.attendance model is defined in module: resource. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "resource.calendar.attendance", "table_name": ""}
+{"text": "How is approval.matrix.vendor implemented technically?", "response": "The approval.matrix.vendor model is defined in module: equip3_purchase_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "approval.matrix.vendor", "table_name": ""}
+{"text": "How to create records in report.dynamic_accounts_report.day_book?", "response": "To use the report.dynamic_accounts_report.day_book model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.day_book", "table_name": ""}
+{"text": "What are common use cases for product.brand?", "response": "To use the product.brand model, you need to provide values for required fields: brand_name. Readonly fields: product_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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.brand", "table_name": ""}
+{"text": "What is the mr.approval.matrix model?", "response": "The mr.approval.matrix model represents Material Approval Matrix in the ERP system. It contains 45 fields and is used to manage material approval matrix data. Key fields include: name, company_id, branch_id, warehouse_id, approval_line_count, mr_approval_matrix_line_ids, location_child_ids, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mr.approval.matrix", "table_name": ""}
+{"text": "Show me the fields of utm.stage.", "response": "The utm.stage model has 9 fields: name, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "utm.stage", "table_name": ""}
+{"text": "What fields does ir.model.fields have?", "response": "The ir.model.fields model has 44 fields: name, complete_name, model, relation, relation_field, relation_field_id, model_id, field_description, help, selection, selection_ids, copied, related, related_field_id, required, readonly, index, translate, size, state, on_delete, domain, groups, group_expand, selectable, modules, relation_table, column1, column2, compute, depends, store, ttype, serialization_field_id, tracking, relation_model_name, website_form_blacklisted, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 16, many2one: 6, text: 2, one2many: 1, boolean: 9, integer: 3, selection: 3, many2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.model.fields", "table_name": ""}
+{"text": "What are the technical details of vendor.deposit.line.reconcile?", "response": "The vendor.deposit.line.reconcile model is defined in module: equip3_accounting_deposit. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "vendor.deposit.line.reconcile", "table_name": ""}
+{"text": "What data can be stored in coupon.reward?", "response": "The coupon.reward model has 19 fields: reward_description, reward_product_id, reward_product_quantity, discount_type, discount_percentage, discount_apply_on, discount_specific_product_ids, discount_max_amount, discount_fixed_amount, reward_product_uom_id, discount_line_product_id, reward_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 5, integer: 2, selection: 3, float: 3, many2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "coupon.reward", "table_name": ""}
+{"text": "What are common use cases for asset.cip.line?", "response": "To use the asset.cip.line model, you need to provide values for required fields: label. Readonly fields: move_posted_check, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "asset.cip.line", "table_name": ""}
+{"text": "Can you explain the purpose of res.config?", "response": "The res.config model represents Config in the ERP system. It contains 7 fields and is used to manage config data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.config", "table_name": ""}
+{"text": "What data can be stored in base_import.tests.models.m2o.required?", "response": "The base_import.tests.models.m2o.required model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.m2o.required", "table_name": ""}
+{"text": "How do I use the expiring.product.calendar model?", "response": "To use the expiring.product.calendar 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "expiring.product.calendar", "table_name": ""}
+{"text": "List all fields in the milestone.contract.template.purchase model.", "response": "The milestone.contract.template.purchase model has 12 fields: purchase_order_id, name, checklist_template_id, contract_term, progress_paid, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 2, float: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "milestone.contract.template.purchase", "table_name": ""}
+{"text": "What modules define ir.fields.converter?", "response": "The ir.fields.converter model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.fields.converter", "table_name": ""}
+{"text": "How to query account.fiscal.position data?", "response": "To use the account.fiscal.position model, you need to provide values for required fields: company_id, name. Readonly fields: company_id, states_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.fiscal.position", "table_name": ""}
+{"text": "What are common use cases for orderline.orderline?", "response": "To use the orderline.orderline model, you need to provide values for required fields: product_id, sequence. Readonly fields: price_subtotal, ordered_qty, delivered_qty, qty_invoiced, undelivered_qty, sequence2, company_id, price_tax, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "orderline.orderline", "table_name": ""}
+{"text": "What are common use cases for account.loan?", "response": "To use the account.loan model, you need to provide values for required fields: name, partner_id, company_id, state, periods, method_period, rate, rate_type, loan_type, loan_amount, residual_amount, journal_id, short_term_loan_account_id, interest_expenses_account_id. Readonly fields: name, partner_id, company_id, line_ids, periods, method_period, start_date, rate_period, rate_type, loan_type, fixed_amount, fixed_loan_amount, fixed_periods, loan_amount, residual_amount, round_on_end, payment_on_first_period, currency_id, journal_type, journal_id, is_leasing, leased_asset_account_id, pending_principal_amount, payment_amount, interests_amount, short_term_loan_account_id, long_term_loan_account_id, interest_expenses_account_id, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.loan", "table_name": ""}
+{"text": "Show me the relational structure of tax.sale.details.report.", "response": "The tax.sale.details.report model has 3 relational fields: details_id -> sh.sale.details.report.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "tax.sale.details.report", "table_name": ""}
+{"text": "What modules define overhead.material?", "response": "The overhead.material model is defined in module: equip3_manuf_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "overhead.material", "table_name": ""}
+{"text": "What models are connected to customer.order.dic?", "response": "The customer.order.dic model has 4 relational fields: report_id -> sh.sale.invoice.summary.wizard; list_order -> list.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "customer.order.dic", "table_name": ""}
+{"text": "What foreign keys exist in sh.top.selling.products?", "response": "The sh.top.selling.products model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.top.selling.products", "table_name": ""}
+{"text": "How do I use the assign.pr.line.wizard model?", "response": "To use the assign.pr.line.wizard model, you need to provide values for required fields: none. Readonly fields: name, user_id, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assign.pr.line.wizard", "table_name": ""}
+{"text": "What methods are available in report.accounting_pdf_reports.report_agedpartnerbalance?", "response": "The report.accounting_pdf_reports.report_agedpartnerbalance model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.accounting_pdf_reports.report_agedpartnerbalance", "table_name": ""}
+{"text": "Show me the fields of rn.approval_matrix_detail.", "response": "The rn.approval_matrix_detail model has 11 fields: location_name, usage, company_id, rn_approval_matrix_id2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "rn.approval_matrix_detail", "table_name": ""}
+{"text": "What fields does pos.details.wizard have?", "response": "The pos.details.wizard model has 10 fields: start_date, end_date, pos_config_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2many: 1, integer: 1, char: 1, many2one: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.details.wizard", "table_name": ""}
+{"text": "What are the relationships in account.fiscal.position.account?", "response": "The account.fiscal.position.account model has 6 relational fields: position_id -> account.fiscal.position; company_id -> res.company; account_src_id -> account.account; account_dest_id -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.fiscal.position.account", "table_name": ""}
+{"text": "Which fields in sh.send.notification are computed?", "response": "The sh.send.notification model is defined in module: sh_backmate_theme_adv. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.send.notification", "table_name": ""}
+{"text": "What models are connected to account.day.book?", "response": "The account.day.book model has 5 relational fields: company_id -> res.company; journal_ids -> account.journal; account_ids -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: journal_ids, account_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.day.book", "table_name": ""}
+{"text": "How is acrux.chat.conversation implemented technically?", "response": "The acrux.chat.conversation model is defined in module: acrux_chat. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "acrux.chat.conversation", "table_name": ""}
+{"text": "What models are connected to picking.order?", "response": "The picking.order model has 27 relational fields: delivery_boy -> res.partner; sale_order -> sale.order; invoice -> account.move; picking -> stock.picking; partner_id -> res.partner; pos_order_id -> pos.order; pos_partner_id -> res.partner; state_id -> res.country.state; country_id -> res.country; bank_statement_ids -> pos.payment; lines -> picking.order.line; session_id -> pos.session; cashier -> res.users; warehouse_id -> stock.warehouse; transaction_id -> payment.transaction; stage_id -> order.stage; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "picking.order", "table_name": ""}
+{"text": "What data can be stored in pos.promotion.discount.apply?", "response": "The pos.promotion.discount.apply model has 13 fields: active, product_id, type, discount, discount_fixed_amount, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 4, selection: 1, float: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.promotion.discount.apply", "table_name": ""}
+{"text": "Show me the fields of stock.backorder.confirmation.line.", "response": "The stock.backorder.confirmation.line model has 10 fields: backorder_confirmation_id, picking_id, to_backorder, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.backorder.confirmation.line", "table_name": ""}
+{"text": "Can you explain the purpose of target.activity.line?", "response": "The target.activity.line model represents target.activity.line in the ERP system. It contains 13 fields and is used to manage target.activity.line data. Key fields include: user_id, activity_id, activity_type, activity_target, achieved_target, remaining_target, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "target.activity.line", "table_name": ""}
+{"text": "What is the base.geocoder model?", "response": "The base.geocoder model represents Geo Coder in the ERP system. It contains 3 fields and is used to manage geo coder data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.geocoder", "table_name": ""}
+{"text": "List all fields in the stock.valuation.adjustment.lines model.", "response": "The stock.valuation.adjustment.lines model has 19 fields: name, cost_id, cost_line_id, move_id, product_id, quantity, weight, volume, former_cost, additional_landed_cost, final_cost, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 7, float: 3, monetary: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.valuation.adjustment.lines", "table_name": ""}
+{"text": "What are the relationships in purchase.quotation.excel.extended?", "response": "The purchase.quotation.excel.extended model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.quotation.excel.extended", "table_name": ""}
+{"text": "What is the approval.matrix.vendor.reject model?", "response": "The approval.matrix.vendor.reject model represents approval.matrix.vendor.reject in the ERP system. It contains 8 fields and is used to manage approval.matrix.vendor.reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.vendor.reject", "table_name": ""}
+{"text": "How does res.currency.tax relate to other models?", "response": "The res.currency.tax model has 4 relational fields: currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.currency.tax", "table_name": ""}
+{"text": "What operations can I perform on sh.mrp.qc.alert?", "response": "To use the sh.mrp.qc.alert model, you need to provide values for required fields: team_id, user_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.mrp.qc.alert", "table_name": ""}
+{"text": "What are common use cases for queue.job.demo?", "response": "To use the queue.job.demo 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "queue.job.demo", "table_name": ""}
+{"text": "Can you explain the purpose of warranty.claim?", "response": "The warranty.claim model represents Claim in the ERP system. It contains 35 fields and is used to manage claim data. Key fields include: id, name, active, action_next, date_action_next, description, resolution, create_date, write_date, date_deadline, date_closed, date, categ_id, priority, type_action, user_id, user_fault, team_id, company_id, partner_id, email_cc, email_from, partner_phone, stage_id, cause, product_ids, product_id, serial_nos, serial_no, warranty, stage_match, display_name, create_uid, write_uid, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "warranty.claim", "table_name": ""}
+{"text": "How is stock.inventory.wizard implemented technically?", "response": "The stock.inventory.wizard model is defined in module: allfresh_mod_stock_count. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.inventory.wizard", "table_name": ""}
+{"text": "What is the generate.closing.entries model?", "response": "The generate.closing.entries model represents Generate Opening Entries in the ERP system. It contains 13 fields and is used to manage generate opening entries data. Key fields include: fiscal_year_id, closing_entry_date, journal_id, description, summary_account_id, retained_earnings_account_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "generate.closing.entries", "table_name": ""}
+{"text": "What modules define invoice.template.header?", "response": "The invoice.template.header model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.template.header", "table_name": ""}
+{"text": "List all fields in the pos.gift.card.exchange.history model.", "response": "The pos.gift.card.exchange.history model has 10 fields: customer_id, old_card_no, new_card_no, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.gift.card.exchange.history", "table_name": ""}
+{"text": "Tell me about the crm.team model.", "response": "The crm.team model represents Sales Team in the ERP system. It contains 73 fields and is used to manage sales team data. Key fields include: name, sequence, active, currency_id, color, favorite_user_ids, is_favorite, dashboard_button_name, dashboard_graph_data, use_leads, use_opportunities, alias_id, lead_unassigned_count, lead_all_assigned_month_count, opportunities_count, opportunities_amount, opportunities_overdue_count, opportunities_overdue_amount, use_quotations, invoiced, invoiced_target, quotations_count, quotations_amount, sales_to_invoice_count, website_ids, abandoned_carts_count, abandoned_carts_amount, use_warranty, rma_draft_count, rma_confirm_count, rma_process_count, rma_close_count, rma_reject_count, rma_ids, pos_config_ids, pos_sessions_open_count, pos_order_amount_total, user_id, company_id, member_ids, is_external_link, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, alias_name, alias_model_id, alias_user_id, alias_defaults, alias_force_thread_id, alias_domain, alias_parent_model_id, alias_parent_thread_id, alias_bounced_content, alias_contact.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.team", "table_name": ""}
+{"text": "What is the pos.generate.efaktur.other model?", "response": "The pos.generate.efaktur.other model represents Pos Generate Efaktur Other in the ERP system. It contains 11 fields and is used to manage pos generate efaktur other data. Key fields include: gen_efaktur_id, partner_id, account_move_id, l10n_id_tax_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.generate.efaktur.other", "table_name": ""}
+{"text": "What does the export.partner.csv model represent?", "response": "The export.partner.csv model represents Export Partner in the ERP system. It contains 40 fields and is used to manage export partner data. Key fields include: name, product_id_attachment_id, product_id_csv_created, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "export.partner.csv", "table_name": ""}
+{"text": "What foreign keys exist in portal.wizard.user?", "response": "The portal.wizard.user model has 5 relational fields: wizard_id -> portal.wizard; partner_id -> res.partner; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "portal.wizard.user", "table_name": ""}
+{"text": "How to create records in base.module.upgrade?", "response": "To use the base.module.upgrade model, you need to provide values for required fields: none. Readonly fields: module_info, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.module.upgrade", "table_name": ""}
+{"text": "What operations can I perform on pos.promotion.specific.product?", "response": "To use the pos.promotion.specific.product model, you need to provide values for required fields: type_apply, promotion_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion.specific.product", "table_name": ""}
+{"text": "What are common use cases for vendor.deposit?", "response": "To use the vendor.deposit model, you need to provide values for required fields: payment_date, deposit_reconcile_journal_id, deposit_account_id, currency_id. Readonly fields: name, remaining_amount, return_deposit, is_show_cancel, invoice_count, reconcile_count, filter_deposit_account_ids, approval_matrix_id, is_vendor_deposit_approval_matrix, approval_matrix_line_id, is_approve_button, state1, state2, deposit_history, filter_branch_ids, move_id, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "vendor.deposit", "table_name": ""}
+{"text": "What business logic is in pos.gift.card.exchange.history?", "response": "To use the pos.gift.card.exchange.history model, you need to provide values for required fields: none. Readonly fields: old_card_no, new_card_no, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.gift.card.exchange.history", "table_name": ""}
+{"text": "What are the relationships in sh.mrp.quality.check?", "response": "The sh.mrp.quality.check model has 17 relational fields: product_id -> product.product; sh_workorder_id -> mrp.workorder; sh_mrp -> mrp.production; control_point_id -> sh.qc.point; company_id -> res.company; attachment_ids -> ir.attachment; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.mrp.quality.check", "table_name": ""}
+{"text": "What models are connected to sh.target.commision.new?", "response": "The sh.target.commision.new model has 4 relational fields: commission_id -> sh.target.commision; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.target.commision.new", "table_name": ""}
+{"text": "How to create records in import.pricelist.wizard?", "response": "To use the import.pricelist.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "import.pricelist.wizard", "table_name": ""}
+{"text": "Show me the fields of itr.approval.matrix.line.", "response": "The itr.approval.matrix.line model has 34 fields: sequence, user_ids, minimum_approver, itr_approval_matrix, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, transfer_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 8, many2many: 4, many2one: 6, text: 1, datetime: 4, char: 2, boolean: 6, one2many: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "itr.approval.matrix.line", "table_name": ""}
+{"text": "What are the relationships in whatsapp.template.message.variable?", "response": "The whatsapp.template.message.variable model has 3 relational fields: wa_id -> whatsapp.template.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "whatsapp.template.message.variable", "table_name": ""}
+{"text": "What operations can I perform on ks.custom.query.report.column?", "response": "To use the ks.custom.query.report.column 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks.custom.query.report.column", "table_name": ""}
+{"text": "Show me the relational structure of pos.report.payment.", "response": "The pos.report.payment model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.report.payment", "table_name": ""}
+{"text": "What are the available fields for uom.conversion.history?", "response": "The uom.conversion.history model has 17 fields: product_id, location_id, prod_lot_id, package_id, partner_id, product_qty, uom_id, counted_qty, uom_conversion, si_uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 10, float: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "uom.conversion.history", "table_name": ""}
+{"text": "What models are connected to product.margin?", "response": "The product.margin model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.margin", "table_name": ""}
+{"text": "What is the bve.view.line model?", "response": "The bve.view.line model represents BI View Editor Lines in the ERP system. It contains 27 fields and is used to manage bi view editor lines data. Key fields include: name, sequence, bve_view_id, model_id, model_name, table_alias, join_model_id, field_id, field_name, ttype, description, relation, join_node, left_join, row, column, measure, in_list, list_attr, view_field_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "bve.view.line", "table_name": ""}
+{"text": "Can you explain the purpose of coupon.program?", "response": "The coupon.program model represents Coupon Program in the ERP system. It contains 68 fields and is used to manage coupon program data. Key fields include: name, active, rule_id, reward_id, sequence, maximum_use_number, program_type, promo_code, promo_applicability, coupon_ids, coupon_count, company_id, currency_id, validity_duration, order_count, is_sale_promotion, customers_selection, products_selection, customer_category_ids, product_category_ids, selected_customers_ids, selected_products_ids, single_promotion, promotion_type, pos_order_count, is_gift_card, maximum_cards_create, description, gift_product_id, is_vendor_promotion, rule_purchase_product_domain, rule_vendors_domain, vendors_selection, purchase_order_count, promo_code_usage, purchase_products_selection, purchase_product_category_ids, purchase_selected_customers_ids, purchase_selected_products_ids, website_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, rule_date_from, rule_date_to, rule_partners_domain, rule_products_domain, rule_min_quantity, rule_minimum_amount, rule_minimum_amount_tax_inclusion, applied_partner_ids, applied_product_ids, reward_description, reward_product_id, reward_product_quantity, discount_type, discount_percentage, discount_apply_on, discount_specific_product_ids, discount_max_amount, discount_fixed_amount, reward_product_uom_id, discount_line_product_id, reward_type.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "coupon.program", "table_name": ""}
+{"text": "How to query res.partner.type data?", "response": "To use the res.partner.type 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.partner.type", "table_name": ""}
+{"text": "What fields does l10n_id_efaktur.efaktur.range have?", "response": "The l10n_id_efaktur.efaktur.range model has 11 fields: company_id, max, min, available, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "l10n_id_efaktur.efaktur.range", "table_name": ""}
+{"text": "What methods are available in ks.sales.forecast?", "response": "The ks.sales.forecast model is defined in module: ks_sales_forecast. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks.sales.forecast", "table_name": ""}
+{"text": "What does the measure.for.packaging model represent?", "response": "The measure.for.packaging model represents measure.for.packaging in the ERP system. It contains 8 fields and is used to manage measure.for.packaging data. Key fields include: measure, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "measure.for.packaging", "table_name": ""}
+{"text": "Show me the relational structure of setu.inventory.age.breakdown.report.", "response": "The setu.inventory.age.breakdown.report model has 5 relational fields: company_ids -> res.company; product_category_ids -> product.category; product_ids -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids, product_category_ids, product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.age.breakdown.report", "table_name": ""}
+{"text": "How to create records in sh.sale.invoice.summary.wizard?", "response": "To use the sh.sale.invoice.summary.wizard model, you need to provide values for required fields: sh_start_date, sh_end_date, sh_partner_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.sale.invoice.summary.wizard", "table_name": ""}
+{"text": "Describe the utm.campaign model in Odoo.", "response": "The utm.campaign model represents UTM Campaign in the ERP system. It contains 26 fields and is used to manage utm campaign data. Key fields include: name, user_id, stage_id, tag_ids, is_website, color, click_count, use_leads, crm_lead_count, mailing_mail_ids, mailing_mail_count, received_ratio, opened_ratio, replied_ratio, bounced_ratio, quotation_count, invoiced_amount, company_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "utm.campaign", "table_name": ""}
+{"text": "What does the kpi.scorecard.line model represent?", "response": "The kpi.scorecard.line model represents KPI Target in the ERP system. It contains 24 fields and is used to manage kpi target data. Key fields include: kpi_id, category_id, description, period_id, target_value, formatted_target_value, actual_value, computation_error, formatted_actual_value, result, sequence, all_parents, edit_rights, company_id, period_length, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kpi.scorecard.line", "table_name": ""}
+{"text": "What modules define sms.resend?", "response": "The sms.resend model is defined in module: sms. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sms.resend", "table_name": ""}
+{"text": "Describe the field structure of mrp.quality.alert.report.", "response": "The mrp.quality.alert.report model has 13 fields: date_from, date_to, product_ids, user_ids, stage_id, operation_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, many2many: 2, many2one: 3, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.quality.alert.report", "table_name": ""}
+{"text": "What modules define pos.sale.summary.wizard?", "response": "The pos.sale.summary.wizard model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.sale.summary.wizard", "table_name": ""}
+{"text": "What methods are available in assets.approval.reject?", "response": "The assets.approval.reject model is defined in module: equip3_accounting_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "assets.approval.reject", "table_name": ""}
+{"text": "What fields does allfresh.consignment.report have?", "response": "The allfresh.consignment.report model has 15 fields: date_order, pos_ref, pos_branch_id, barcode, product_id, qty, price, margin, total_margin, consignment_move_id, currency_id, company_id, id, display_name, __last_update. Field types distribution: datetime: 2, char: 3, many2one: 5, float: 1, monetary: 3, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "allfresh.consignment.report", "table_name": ""}
+{"text": "What are the relationships in report_excel_wizard?", "response": "The report_excel_wizard model has 3 relational fields: report_conf -> report.excel; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report_excel_wizard", "table_name": ""}
+{"text": "What operations can I perform on res.partner.title?", "response": "To use the res.partner.title 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.partner.title", "table_name": ""}
+{"text": "What are the relationships in account.equity.move?", "response": "The account.equity.move 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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.equity.move", "table_name": ""}
+{"text": "What are the technical details of fetchmail.server?", "response": "The fetchmail.server model is defined in module: fetchmail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "fetchmail.server", "table_name": ""}
+{"text": "How do I use the target.activity.line model?", "response": "To use the target.activity.line model, you need to provide values for required fields: none. Readonly fields: user_id, achieved_target, remaining_target, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "target.activity.line", "table_name": ""}
+{"text": "What models are connected to ks_ninja_dashboard.item_action?", "response": "The ks_ninja_dashboard.item_action model has 5 relational fields: ks_dashboard_item_ids -> ks_dashboard_ninja.item; ks_dashboard_ninja_id -> ks_dashboard_ninja.board; ks_dashboard_ninja_ids -> ks_dashboard_ninja.board; create_uid -> res.users; write_uid -> res.users. Many2many fields: ks_dashboard_item_ids, ks_dashboard_ninja_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks_ninja_dashboard.item_action", "table_name": ""}
+{"text": "Can you explain the purpose of report.equip3_accounting_reports.tax_report?", "response": "The report.equip3_accounting_reports.tax_report model represents report.equip3_accounting_reports.tax_report in the ERP system. It contains 3 fields and is used to manage report.equip3_accounting_reports.tax_report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.tax_report", "table_name": ""}
+{"text": "What operations can I perform on blanket.quotation.line?", "response": "To use the blanket.quotation.line model, you need to provide values for required fields: bq_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "blanket.quotation.line", "table_name": ""}
+{"text": "What models are connected to product.warehouse.cost.line?", "response": "The product.warehouse.cost.line model has 6 relational fields: prod_wh_cost_id -> product.warehouse.cost; warehouse_id -> stock.warehouse; company_id -> res.company; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.warehouse.cost.line", "table_name": ""}
+{"text": "Show me the relational structure of mail.message.", "response": "The mail.message model has 20 relational fields: attachment_ids -> ir.attachment; parent_id -> mail.message; child_ids -> mail.message; subtype_id -> mail.message.subtype; mail_activity_type_id -> mail.activity.type; author_id -> res.partner; partner_ids -> res.partner; notified_partner_ids -> res.partner; channel_ids -> mail.channel; notification_ids -> mail.notification; starred_partner_ids -> res.partner; tracking_value_ids -> mail.tracking.value; mail_server_id -> ir.mail_server; moderator_id -> res.users; mail_ids -> mail.mail; canned_response_ids -> mail.shortcode; rating_ids -> rating.rating; letter_ids -> snailmail.letter; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids, partner_ids, notified_partner_ids, channel_ids, starred_partner_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.message", "table_name": ""}
+{"text": "What modules define account.loan?", "response": "The account.loan model is defined in module: account_loan. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.loan", "table_name": ""}
+{"text": "Describe the implementation of pos.category.", "response": "The pos.category model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.category", "table_name": ""}
+{"text": "How to query sale.order.alternative.product data?", "response": "To use the sale.order.alternative.product 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.alternative.product", "table_name": ""}
+{"text": "What business logic is in purchase.agreement.comparison?", "response": "To use the purchase.agreement.comparison model, you need to provide values for required fields: none. Readonly fields: on_time_rate, fulfillment, final_point, final_star, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.agreement.comparison", "table_name": ""}
+{"text": "What business logic is in base.language.export?", "response": "To use the base.language.export model, you need to provide values for required fields: lang, format. Readonly fields: name, data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.language.export", "table_name": ""}
+{"text": "What methods are available in product.pricelist.history?", "response": "The product.pricelist.history model is defined in module: equip3_sale_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.pricelist.history", "table_name": ""}
+{"text": "Which fields in payment.icon are computed?", "response": "The payment.icon model is defined in module: payment. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "payment.icon", "table_name": ""}
+{"text": "What models are connected to sh.send.notification?", "response": "The sh.send.notification model has 4 relational fields: specific_ids -> sh.push.notification; log_historys -> sh.notification.logger; create_uid -> res.users; write_uid -> res.users. Many2many fields: specific_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.send.notification", "table_name": ""}
+{"text": "What are common use cases for account.tax.template?", "response": "To use the account.tax.template model, you need to provide values for required fields: chart_template_id, type_tax_use, amount_type, sequence, amount, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.tax.template", "table_name": ""}
+{"text": "Show me the fields of base.geo_provider.", "response": "The base.geo_provider model has 9 fields: tech_name, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.geo_provider", "table_name": ""}
+{"text": "How do I use the action.data model?", "response": "To use the action.data 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "action.data", "table_name": ""}
+{"text": "Show me the fields of stock.backorder.confirmation.", "response": "The stock.backorder.confirmation model has 10 fields: pick_ids, show_transfers, backorder_confirmation_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, boolean: 1, one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.backorder.confirmation", "table_name": ""}
+{"text": "What foreign keys exist in mailing.list?", "response": "The mailing.list model has 5 relational fields: contact_ids -> mailing.contact; subscription_ids -> mailing.contact.subscription; website_popup_ids -> website.mass_mailing.popup; create_uid -> res.users; write_uid -> res.users. Many2many fields: contact_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mailing.list", "table_name": ""}
+{"text": "Describe the implementation of limit.approval.matrix.lines.", "response": "The limit.approval.matrix.lines model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "limit.approval.matrix.lines", "table_name": ""}
+{"text": "What are common use cases for blanket.quotation.line?", "response": "To use the blanket.quotation.line model, you need to provide values for required fields: bq_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "blanket.quotation.line", "table_name": ""}
+{"text": "What business logic is in ks_ninja_dashboard.item_action?", "response": "To use the ks_ninja_dashboard.item_action 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_ninja_dashboard.item_action", "table_name": ""}
+{"text": "What methods are available in product.margin?", "response": "The product.margin model is defined in module: product_margin. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.margin", "table_name": ""}
+{"text": "What are common use cases for sale.coupon.apply.code?", "response": "To use the sale.coupon.apply.code model, you need to provide values for required fields: coupon_code. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.coupon.apply.code", "table_name": ""}
+{"text": "Tell me about the report.sh_purchase_reports.sh_po_by_category_doc model.", "response": "The report.sh_purchase_reports.sh_po_by_category_doc model represents Purchase by category report abstract model in the ERP system. It contains 3 fields and is used to manage purchase by category report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_po_by_category_doc", "table_name": ""}
+{"text": "What business logic is in crossovered.budget.lines?", "response": "To use the crossovered.budget.lines model, you need to provide values for required fields: crossovered_budget_id, date_from, date_to, planned_amount. Readonly fields: name, analytic_group_id, currency_id, company_id, is_above_budget, crossovered_budget_state, reserve_amount, account_tag_ids, filtered_budget_line, practical_budget_amount, remaining_amount, theoritical_amount_2, percentage_2, theoritical_amount, practical_amount, percentage, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crossovered.budget.lines", "table_name": ""}
+{"text": "What are common use cases for report.equip3_accounting_operation.report_statement_temp?", "response": "To use the report.equip3_accounting_operation.report_statement_temp model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_operation.report_statement_temp", "table_name": ""}
+{"text": "What does the mail.activity.type model represent?", "response": "The mail.activity.type model represents Activity Type in the ERP system. It contains 29 fields and is used to manage activity type data. Key fields include: name, summary, sequence, active, create_uid, delay_count, delay_unit, delay_label, delay_from, icon, decoration_type, res_model_id, default_next_type_id, force_next, next_type_ids, previous_type_ids, mail_template_ids, default_user_id, default_description, initial_res_model_id, res_model_change, category, attachment_required, id, display_name, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.activity.type", "table_name": ""}
+{"text": "Describe the field structure of mrp.bom.operation.", "response": "The mrp.bom.operation model has 9 fields: sequence, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, char: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.bom.operation", "table_name": ""}
+{"text": "How to query pos.qrcode data?", "response": "To use the pos.qrcode model, you need to provide values for required fields: name, field_id, config_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.qrcode", "table_name": ""}
+{"text": "What modules define sale.order.merge.wizard?", "response": "The sale.order.merge.wizard model is defined in module: odoo_sale_order_merge. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.order.merge.wizard", "table_name": ""}
+{"text": "How is invoice.printout.editor.lines implemented technically?", "response": "The invoice.printout.editor.lines model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.printout.editor.lines", "table_name": ""}
+{"text": "What does the base.partner.merge.automatic.wizard model represent?", "response": "The base.partner.merge.automatic.wizard model represents Merge Partner Wizard in the ERP system. It contains 21 fields and is used to manage merge partner wizard data. Key fields include: group_by_email, group_by_name, group_by_is_company, group_by_vat, group_by_parent_id, state, number_group, current_line_id, line_ids, partner_ids, dst_partner_id, exclude_contact, exclude_journal_item, maximum_group, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.partner.merge.automatic.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for report.equip3_accounting_reports.balance_sheet.", "response": "The report.equip3_accounting_reports.balance_sheet model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.balance_sheet", "table_name": ""}
+{"text": "Can you explain the purpose of pmps.adv.wizard?", "response": "The pmps.adv.wizard model represents Purchase Multi Product Selection Advanced Wizard in the ERP system. It contains 10 fields and is used to manage purchase multi product selection advanced wizard data. Key fields include: product_ids, product_attr_ids, specific_product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pmps.adv.wizard", "table_name": ""}
+{"text": "What models are connected to sh.edit.title?", "response": "The sh.edit.title model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.edit.title", "table_name": ""}
+{"text": "How do I use the im_livechat.channel model?", "response": "To use the im_livechat.channel model, you need to provide values for required fields: name. Readonly fields: web_page, are_you_inside, script_external, nbr_channel, can_publish, website_url, rating_percentage_satisfaction, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "im_livechat.channel", "table_name": ""}
+{"text": "What fields does measure.for.packaging have?", "response": "The measure.for.packaging model has 8 fields: measure, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "measure.for.packaging", "table_name": ""}
+{"text": "What are common use cases for dev.rma.line?", "response": "To use the dev.rma.line model, you need to provide values for required fields: product_id, delivered_qty. Readonly fields: is_po, account_move_id, tax_number, tax_number_new, grand_total, partner_id, branch_id, tax_amount, grand_total_untaxed, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "dev.rma.line", "table_name": ""}
+{"text": "Which fields in wizard.report.menu.create are computed?", "response": "The wizard.report.menu.create model is defined in module: report_excel. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "wizard.report.menu.create", "table_name": ""}
+{"text": "How to query account.tax.digunggung data?", "response": "To use the account.tax.digunggung model, you need to provide values for required fields: tax_report, start_date_digunggung, end_date_digunggung, partner_id. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.tax.digunggung", "table_name": ""}
+{"text": "What is the report.extra.content model?", "response": "The report.extra.content model represents ReportExtraContent in the ERP system. It contains 11 fields and is used to manage reportextracontent data. Key fields include: file_name, append_extra_content, model_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.extra.content", "table_name": ""}
+{"text": "List all fields in the payment.token model.", "response": "The payment.token model has 16 fields: name, short_name, partner_id, acquirer_id, company_id, acquirer_ref, active, payment_ids, verified, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 5, boolean: 2, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "payment.token", "table_name": ""}
+{"text": "What fields does invoice.template.footer have?", "response": "The invoice.template.footer model has 10 fields: template_id, field_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "invoice.template.footer", "table_name": ""}
+{"text": "How to query project.task.type data?", "response": "To use the project.task.type model, you need to provide values for required fields: name, legend_blocked, legend_done, legend_normal. Readonly fields: disabled_rating_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.task.type", "table_name": ""}
+{"text": "How does account.common.partner.report relate to other models?", "response": "The account.common.partner.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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.common.partner.report", "table_name": ""}
+{"text": "Describe the field structure of kpi.category.", "response": "The kpi.category model has 22 fields: name, active, parent_id, child_ids, company_id, description, sequence, user_ids, user_group_ids, access_user_ids, edit_user_ids, edit_user_group_ids, edit_access_user_ids, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 2, many2one: 4, one2many: 1, text: 1, integer: 2, many2many: 6, html: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "kpi.category", "table_name": ""}
+{"text": "What are common use cases for customer.order.dic?", "response": "To use the customer.order.dic 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "customer.order.dic", "table_name": ""}
+{"text": "Describe the many2many relations for membership.membership_line.", "response": "The membership.membership_line model has 7 relational fields: partner -> res.partner; membership_id -> product.product; account_invoice_line -> account.move.line; account_invoice_id -> account.move; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "membership.membership_line", "table_name": ""}
+{"text": "How to query report.accounting_pdf_reports.report_general_ledger data?", "response": "To use the report.accounting_pdf_reports.report_general_ledger model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.accounting_pdf_reports.report_general_ledger", "table_name": ""}
+{"text": "Tell me about the account.efaktur model.", "response": "The account.efaktur model represents account.efaktur in the ERP system. It contains 19 fields and is used to manage account.efaktur data. Key fields include: year, record_id, invoice_id, partner_id, invoice_date, company_id, is_pjap, is_used_pjap, branch_id, is_cancel, is_used, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.efaktur", "table_name": ""}
+{"text": "What fields does account.cashbox.wizard.line have?", "response": "The account.cashbox.wizard.line model has 16 fields: account_cashbox_wizard_id, coin_value, number, subtotal, cashbox_id, currency_id, pos_config_id, pos_session_id, is_closing_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, float: 2, integer: 2, boolean: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.cashbox.wizard.line", "table_name": ""}
+{"text": "How to create records in snailmail.confirm.invoice?", "response": "To use the snailmail.confirm.invoice 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "snailmail.confirm.invoice", "table_name": ""}
+{"text": "How to create records in account.pettycash?", "response": "To use the account.pettycash model, you need to provide values for required fields: cash_journal, name, custodian, journal, amount. Readonly fields: number, name, custodian, main_cash_account_id, journal, balance, virtual_balance, company_id, create_uid, create_date, move_id, is_custodian_user, custodian_partner, is_replenished, 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, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.pettycash", "table_name": ""}
+{"text": "What data can be stored in generate.closing.entries?", "response": "The generate.closing.entries model has 13 fields: fiscal_year_id, closing_entry_date, journal_id, description, summary_account_id, retained_earnings_account_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, date: 1, text: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "generate.closing.entries", "table_name": ""}
+{"text": "What are the technical details of ai.generate.training.data?", "response": "The ai.generate.training.data model is defined in module: ai_chat_agent. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ai.generate.training.data", "table_name": ""}
+{"text": "What methods are available in stock.valuation.adjustment.lines?", "response": "The stock.valuation.adjustment.lines model is defined in module: stock_landed_costs. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.valuation.adjustment.lines", "table_name": ""}
+{"text": "What fields does picking.order.line have?", "response": "The picking.order.line model has 11 fields: picking_order_id, product_id, price_unit, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "picking.order.line", "table_name": ""}
+{"text": "How to create records in stock.inventory.approval.matrix.line?", "response": "To use the stock.inventory.approval.matrix.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: sequence2, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.inventory.approval.matrix.line", "table_name": ""}
+{"text": "What business logic is in dev.credit.note.wizard?", "response": "To use the dev.credit.note.wizard model, you need to provide values for required fields: none. Readonly fields: picking_type_code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "dev.credit.note.wizard", "table_name": ""}
+{"text": "What models are connected to usage.type?", "response": "The usage.type model has 22 relational fields: company_id -> res.company; branch_id -> res.branch; account_id -> account.account; filter_account_ids -> account.account; income_account_id -> account.account; product_category_id -> product.category; inv_val_account_id -> account.account; filter_income_account_ids -> account.account; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_account_ids, filter_income_account_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "usage.type", "table_name": ""}
+{"text": "What modules define sh.model.fields.global.selection?", "response": "The sh.model.fields.global.selection model is defined in module: sh_global_custom_fields. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.model.fields.global.selection", "table_name": ""}
+{"text": "List all fields in the base_import.tests.models.preview model.", "response": "The base_import.tests.models.preview model has 10 fields: name, somevalue, othervalue, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 3, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.preview", "table_name": ""}
+{"text": "Describe the many2many relations for partial.quantity.done.", "response": "The partial.quantity.done model has 4 relational fields: product_id -> product.product; move_id -> stock.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "partial.quantity.done", "table_name": ""}
+{"text": "How to create records in stock.backorder.confirmation.line?", "response": "To use the stock.backorder.confirmation.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.backorder.confirmation.line", "table_name": ""}
+{"text": "What modules define customer.category?", "response": "The customer.category model is defined in module: equip3_sale_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "customer.category", "table_name": ""}
+{"text": "Describe the field structure of account.bank.statement.integrate.", "response": "The account.bank.statement.integrate model has 15 fields: name, journal_id, date_from, date_to, status, created_by, created_date, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 4, date: 3, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.bank.statement.integrate", "table_name": ""}
+{"text": "What operations can I perform on pos.query.log?", "response": "To use the pos.query.log model, you need to provide values for required fields: none. Readonly fields: name, results, write_date, id, display_name, create_uid, create_date, write_uid, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.query.log", "table_name": ""}
+{"text": "Which fields in account.common.journal.report are computed?", "response": "The account.common.journal.report model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.common.journal.report", "table_name": ""}
+{"text": "Describe the res.partner.industry model in Odoo.", "response": "The res.partner.industry model represents Industry in the ERP system. It contains 10 fields and is used to manage industry data. Key fields include: name, full_name, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.partner.industry", "table_name": ""}
+{"text": "How to create records in sms.resend?", "response": "To use the sms.resend model, you need to provide values for required fields: mail_message_id. Readonly fields: mail_message_id, has_cancel, has_insufficient_credit, has_unregistered_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sms.resend", "table_name": ""}
+{"text": "Describe the implementation of coupon.rule.", "response": "The coupon.rule model is defined in module: coupon. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "coupon.rule", "table_name": ""}
+{"text": "What models are connected to replenish.wizard?", "response": "The replenish.wizard model has 4 relational fields: fund_id -> account.pettycash; replenish_account_id -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "replenish.wizard", "table_name": ""}
+{"text": "What business logic is in acrux.chat.message.wizard?", "response": "To use the acrux.chat.message.wizard model, you need to provide values for required fields: text, partner_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "acrux.chat.message.wizard", "table_name": ""}
+{"text": "What models are connected to account.asset.category.fiscal?", "response": "The account.asset.category.fiscal model has 3 relational fields: asset_category_id -> account.asset.category; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.asset.category.fiscal", "table_name": ""}
+{"text": "How do I use the product.product model?", "response": "To use the product.product model, you need to provide values for required fields: product_tmpl_id, name, uom_id, uom_po_id, product_variant_ids, tracking, purchase_line_warn, sale_line_warn, type. Readonly fields: price_extra, code, partner_ref, combination_indices, is_product_variant, pricelist_item_count, image_variant_1024, image_variant_512, image_variant_256, image_variant_128, can_image_variant_1024_be_zoomed, image_1024, image_512, image_256, image_128, can_image_1024_be_zoomed, sh_qr_code_img, qty_available, virtual_available, free_qty, incoming_qty, outgoing_qty, nbr_reordering_rules, reordering_min_qty, reordering_max_qty, image_chat, bom_count, used_in_bom_count, mrp_product_qty, date_from, date_to, invoice_state, sale_avg_price, purchase_avg_price, sale_num_invoiced, purchase_num_invoiced, sales_gap, purchase_gap, turnover, total_cost, sale_expected, normal_cost, total_margin, expected_margin, total_margin_rate, expected_margin_rate, purchased_product_qty, value_svl, quantity_svl, valuation, cost_method, product_cost_ids, sales_count, purchase_price_history_line_ids, website_url, near_expire, expired, id, warranty_sale_config, cart_qty, is_generate_product, category_prefix_preference, is_secret_product, variant_short_name, is_variants, purchase_price, purchase_price_totals, assembly_inventory_quantity, assembly_safety_stock_qty, assembly_to_produce_qty, assembly_outgoing_qty, product_display_name, kitchen_inventory_quantity, kitchen_safety_stock_qty, kitchen_to_produce_qty, kitchen_outgoing_qty, is_pos_bom, purchase_req_line_ids, is_gift_product, warehouse_price_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, display_name, create_uid, create_date, write_uid, write_date, __last_update, currency_id, cost_currency_id, volume_uom_name, weight_uom_name, uom_name, valid_product_template_attribute_line_ids, product_variant_id, product_variant_count, has_configurable_attributes, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, has_available_route_ids, is_seo_optimized, can_publish, categ_costing_method, visible_expense_policy, visible_qty_configurator, brand_attribute_id, company_id_domain, group_stock_ids, reordering_rules_ids, hide, brand_setting, uom_categ_id, is_approve, template_purchase_price_history_line_ids, is_vendor_pricelist, is_from_assembly, url_pic, is_from_kitchen, combo_option_items, uom_ids, is_cost_per_warehouse. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.product", "table_name": ""}
+{"text": "How is report_excel_gen implemented technically?", "response": "The report_excel_gen model is defined in module: report_excel. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report_excel_gen", "table_name": ""}
+{"text": "How is ir.actions.server implemented technically?", "response": "The ir.actions.server model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.actions.server", "table_name": ""}
+{"text": "Which fields in report.equip3_accounting_reports.cash_flow_statement are computed?", "response": "The report.equip3_accounting_reports.cash_flow_statement model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_accounting_reports.cash_flow_statement", "table_name": ""}
+{"text": "How is base_import.tests.models.m2o used in the system?", "response": "The base_import.tests.models.m2o model represents Tests : Base Import Model, Many to One in the ERP system. It contains 8 fields and is used to manage tests : base import model, many to one data. Key fields include: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.m2o", "table_name": ""}
+{"text": "How is stock.move.line used in the system?", "response": "The stock.move.line model represents Product Moves (Stock Move Line) in the ERP system. It contains 64 fields and is used to manage product moves (stock move line) data. Key fields include: picking_id, move_id, company_id, product_id, product_uom_id, product_uom_category_id, product_qty, product_uom_qty, qty_done, package_id, package_level_id, lot_id, lot_name, date, owner_id, location_id, location_dest_id, lots_visible, picking_code, picking_type_use_create_lots, picking_type_use_existing_lots, state, is_initial_demand_editable, is_locked, consume_line_ids, produce_line_ids, reference, tracking, origin, picking_type_entire_packs, description_picking, workorder_id, production_id, expiration_date, scrap_return_move_id, is_double_product_usage, sale_price, sequence, move_line_sequence, product_type, quant_package_ids, result_package_id, is_quant_update, force_to_reserve_qty, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, assembly_id, scrap_sale_price, is_low_stock, description, kitchen_id, finish_good_rework_id, exp_date, remark, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.move.line", "table_name": ""}
+{"text": "What business logic is in internal.transfer?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "internal.transfer", "table_name": ""}
+{"text": "How to create records in hr.plan.activity.type?", "response": "To use the hr.plan.activity.type model, you need to provide values for required fields: responsible. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "hr.plan.activity.type", "table_name": ""}
+{"text": "What are common use cases for invoice.template.table?", "response": "To use the invoice.template.table model, you need to provide values for required fields: template_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "invoice.template.table", "table_name": ""}
+{"text": "What does the res.partner.rfm.segment.history model represent?", "response": "The res.partner.rfm.segment.history model represents \n    Customer RFM segment history table will automatically add records in the table when the customer RFM score will be changed to another one and if the segment value has been changed\n     in the ERP system. It contains 16 fields and is used to manage \n    customer rfm segment history table will automatically add records in the table when the customer rfm score will be changed to another one and if the segment value has been changed\n     data. Key fields include: partner_id, history_date, old_rfm_segment_id, new_rfm_segment_id, old_rfm_score_id, new_rfm_score_id, old_segment_rank, new_segment_rank, engagement_direction, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.partner.rfm.segment.history", "table_name": ""}
+{"text": "Describe the many2many relations for stock.warn.insufficient.qty.repair.", "response": "The stock.warn.insufficient.qty.repair model has 6 relational fields: repair_id -> repair.order; product_id -> product.product; location_id -> stock.location; quant_ids -> stock.quant; create_uid -> res.users; write_uid -> res.users. Many2many fields: quant_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.warn.insufficient.qty.repair", "table_name": ""}
+{"text": "How to query pos.order.line.promotion data?", "response": "To use the pos.order.line.promotion 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.order.line.promotion", "table_name": ""}
+{"text": "List all fields in the store.filters.groups model.", "response": "The store.filters.groups model has 11 fields: model_id, node_option, attribute_name, attribute_string, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, selection: 1, char: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "store.filters.groups", "table_name": ""}
+{"text": "Describe the report.equip3_accounting_reports.cash_flow_statement model in Odoo.", "response": "The report.equip3_accounting_reports.cash_flow_statement model represents report.equip3_accounting_reports.cash_flow_statement in the ERP system. It contains 3 fields and is used to manage report.equip3_accounting_reports.cash_flow_statement data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.cash_flow_statement", "table_name": ""}
+{"text": "What foreign keys exist in purchase.team.analysis?", "response": "The purchase.team.analysis model has 5 relational fields: user_id -> res.users; purchase_ids -> purchase.order; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.team.analysis", "table_name": ""}
+{"text": "Describe the field structure of res.company.", "response": "The res.company model has 428 fields: name, sequence, child_ids, report_header, report_footer, logo, logo_web, user_ids, street2, zip, city, state_id, bank_ids, country_id, website, paperformat_id, external_report_layout_id, base_onboarding_company_state, favicon, font, primary_color, secondary_color, nomenclature_id, resource_calendar_ids, resource_calendar_id, catchall_email, catchall_formatted, email_formatted, hr_presence_control_email_amount, hr_presence_control_ip_list, kpi_history_tolerance, show_kpi_help, 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, company_name_logo, enable_menu_search, enable_web_push_notification, api_key, vapid, config_details, sh_multi_barcode_unique, message_has_sms_error, snailmail_color, snailmail_cover, snailmail_duplex, sh_product_stock, sh_product_attribute, sh_product_image, sh_product_category, sh_product_code, sh_product_barcode, sh_product_sale_price, sh_product_sale_description, sh_touch_kyboard, sh_welcome_message, sh_message, sh_company_logo, sh_display, sh_display_view, sh_display_landscape, sh_display_portrait, sh_delay_screen, fiscalyear_last_day, fiscalyear_last_month, period_lock_date, fiscalyear_lock_date, tax_lock_date, transfer_account_id, expects_chart_of_accounts, chart_template_id, bank_account_code_prefix, cash_account_code_prefix, default_cash_difference_income_account_id, default_cash_difference_expense_account_id, account_journal_suspense_account_id, transfer_account_code_prefix, account_sale_tax_id, account_purchase_tax_id, tax_calculation_rounding_method, currency_exchange_journal_id, income_currency_exchange_account_id, expense_currency_exchange_account_id, anglo_saxon_accounting, property_stock_account_input_categ_id, property_stock_account_output_categ_id, property_stock_valuation_account_id, bank_journal_ids, tax_exigibility, account_tax_fiscal_country_id, incoterm_id, qr_code, invoice_is_email, invoice_is_print, account_opening_move_id, account_opening_journal_id, account_opening_date, account_setup_bank_data_state, account_setup_fy_data_state, account_setup_coa_state, account_onboarding_invoice_layout_state, account_onboarding_create_invoice_state, account_onboarding_sale_tax_state, account_invoice_onboarding_state, account_dashboard_onboarding_state, invoice_terms, account_setup_bill_state, account_default_pos_receivable_account_id, expense_accrual_account_id, revenue_accrual_account_id, automatic_entry_default_journal_id, country_code, tax_cash_basis_journal_id, account_cash_basis_base_account_id, internal_transit_location_id, stock_move_email_validation, stock_mail_confirmation_template_id, website_theme_onboarding_done, account_check_printing_layout, account_check_printing_date_label, account_check_printing_multi_stub, account_check_printing_margin_top, account_check_printing_margin_left, account_check_printing_margin_right, account_bank_reconciliation_start, vat_check_vies, picking_operation_type, sh_it_barcode_mobile_type, sh_it_bm_is_cont_scan, sh_it_bm_is_notify_on_success, sh_it_bm_is_notify_on_fail, sh_it_bm_is_sound_on_success, sh_it_bm_is_sound_on_fail, sh_it_bm_is_add_product, project_time_mode_id, timesheet_encode_uom_id, manufacturing_lead, payment_acquirer_onboarding_state, payment_onboarding_payment_method, po_lead, po_lock, po_double_validation, po_double_validation_amount, sh_invoice_online_signature, sh_enable_approval, sh_restrict_for_close_period, invoice_is_snailmail, stock_move_sms_validation, stock_sms_confirmation_template_id, has_received_warning_stock_sms, account_edi_proxy_client_ids, inv_cost, point_of_sale_update_stock_quantities, days_to_purchase, portal_confirmation_sign, portal_confirmation_pay, quotation_validity_days, sale_quotation_onboarding_state, sale_onboarding_order_confirmation_state, sale_onboarding_sample_quotation_state, sale_onboarding_payment_method, po_operation_type, cancel_receipt, cancel_bill, purchase_show_signature, chk_sign_confirm, purchase_enable_other_sign_option, sh_expiry_notification, sh_is_notify_vendor, sh_on_date_notify, enter_before_first_notify, enter_before_second_notify, enter_before_third_notify, enter_after_first_notify, enter_after_second_notify, enter_after_third_notify, attachment_email, sh_pmps_pro_field_ids, sh_pmps_pro_attr_ids, sh_purchase_configuration_limit, item_limit_purchase, record_based_on_purchase, purchase_order_information_in_message, purchase_product_detail_in_message, purchase_signature, purchase_display_in_message, po_send_pdf_in_message, sh_auto_add_followers, sh_portal_user_create, sh_tender_document_manage, sh_purchase_revision, sale_order_template_id, security_lead, sh_manage_tender_doc_portal, lc_journal_id, website_sale_onboarding_payment_acquirer_state, intercompany_warehouse_id, validate_picking, create_invoice, validate_invoice, allow_auto_intercompany, use_sale_order_note, sale_order_note, keep_name_so, sh_sale_bm_is_cont_scan, sh_sale_bm_is_notify_on_success, sh_sale_bm_is_notify_on_fail, sh_sale_bm_is_sound_on_success, sh_sale_bm_is_sound_on_fail, sh_purchase_barcode_mobile_type, sh_purchase_bm_is_cont_scan, sh_purchase_bm_is_notify_on_success, sh_purchase_bm_is_notify_on_fail, sh_purchase_bm_is_sound_on_success, sh_purchase_bm_is_sound_on_fail, sh_invoice_barcode_mobile_type, sh_invoice_bm_is_cont_scan, sh_invoice_bm_is_notify_on_success, sh_invoice_bm_is_notify_on_fail, sh_invoice_bm_is_sound_on_success, sh_invoice_bm_is_sound_on_fail, sh_bom_barcode_mobile_type, sh_bom_bm_is_cont_scan, sh_bom_bm_is_notify_on_success, sh_bom_bm_is_notify_on_fail, sh_bom_bm_is_sound_on_success, sh_bom_bm_is_sound_on_fail, sh_stock_barcode_mobile_type, sh_stock_bm_is_cont_scan, sh_stock_bm_is_notify_on_success, sh_stock_bm_is_notify_on_fail, sh_stock_bm_is_sound_on_success, sh_stock_bm_is_sound_on_fail, sh_stock_bm_is_add_product, sh_inventory_adjt_barcode_mobile_type, sh_inventory_adjt_bm_is_cont_scan, sh_inventory_adjt_bm_is_notify_on_success, sh_inventory_adjt_bm_is_notify_on_fail, sh_inventory_adjt_bm_is_sound_on_success, sh_inventory_adjt_bm_is_sound_on_fail, sh_product_barcode_mobile_type, sh_product_bm_is_cont_scan, sh_product_bm_is_notify_on_success, sh_product_bm_is_notify_on_fail, sh_product_bm_is_sound_on_success, sh_product_bm_is_sound_on_fail, sh_product_bm_is_default_code, sh_product_bm_is_lst_price, sh_product_bm_is_qty_available, sh_product_bm_is_virtual_available, sh_global_document_search_is_enable, sh_global_document_search_is_sale, sh_global_document_search_is_purchase, sh_global_document_search_is_picking, sh_global_document_search_is_invoice, sh_global_document_search_is_product, sh_global_document_search_is_lot, sh_global_document_search_is_location, sh_global_document_search_action_target_type, sale_credit_limit_email_alerts, sale_email_specific_user_id, quot_to_po, so_to_po, down_payment_product_id, implementor_setting, general, purchase, sales, inventory, manufacturing, central_kitchen, human_resource, pos, simple_manufacturing, assembly, cutting, mining, agriculture, show_branch, branch_ids, theme_color, theme_text_color, text_color, company_color, customer_color, company_address_color, customer_address_color, odd_party_color, even_party_color, report_template_id1, report_template_id, report_sale_template_id1, report_sale_template_id, report_po_template_id1, report_po_template_id, report_rfq_template_id, report_delivery_template_id1, report_delivery_template_id, report_picking_template_id, invoice_logo, is_description, watermark_logo, is_company_bold, is_customer_bold, standard_template, add_product_image, add_amount_in_words, is_show_watermark, watermark, watermark_text, watermark_text_color, watermark_text_font_size, report_footer_selection, font_id, font_size, is_show_signature, signature, logo_footer, is_show_bank_details, report_bank_id, is_show_notes, is_show_payment_notes, is_show_payment_description, is_show_barcode, is_inverse_rate, is_taxes_rate, unrealized_exchange_journal_id, income_unrealized_exchange_account_id, expense_unrealized_exchange_account_id, tax_discount_policy, sale_account_id, purchase_account_id, interest_income, interest_expense, deposit_account_id, post_discount_account, partner_id, street, phone, email, vat, company_registry, currency_id, parent_id, social_twitter, social_facebook, social_github, social_linkedin, social_youtube, social_instagram, city_id, manufacturing_plan_conf, manufacturing_order_conf, mrp_plan_partial_availability, production_record_conf, mrp_production_partial_availability, mrp_submit_purchase_request, mrp_submit_material_request, mrp_force_done, mo_force_done, mo_auto_reserve_availability_materials, mp_auto_reserve_availability_materials, send_wa_approval_notification_mrp, send_wa_approval_notification_mp, send_wa_approval_notification_mpr, manufacturing_mps, manufacturing_period, manufacturing_period_to_display, sh_sale_barcode_mobile_type, accounting, bom_tools, company_delivery_rate, company_delivery_product, mr_show_analytic_account, brand_setting, short_name, is_message_rn, send_notification_users_ids, pjap_x_token, npwp, is_centralized_efaktur, sh_sale_pro_field_ids, sh_sale_pro_attr_ids, product_pricelist_default, owner, report_pr_template_id, contact_address, is_order_rounding, order_rounding_type, rounding_multiplier, apply_rounding_type, rounding_method_id, pos_def_receipt_template_id, is_pos_receivable, pos_product_discount1_id, is_post_closing_cashbox_value_in_session, is_pos_use_deposit, membership_pluspoint_rounding, membership_pluspoint_rounding_type, membership_pluspoint_rounding_multiplier, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 50, integer: 22, one2many: 10, text: 5, binary: 8, many2many: 8, many2one: 74, selection: 53, boolean: 179, date: 7, float: 8, monetary: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.company", "table_name": ""}
+{"text": "What does the purchase.agreement model represent?", "response": "The purchase.agreement model represents Purchase Agreement in the ERP system. It contains 100 fields and is used to manage purchase agreement data. Key fields include: name, rfq_count, order_count, sh_vender_id, user_id, sh_agreement_deadline, sh_source, sh_purchase_agreement_line_ids, compute_custom_boolean, sh_manage_tender_document, document_count, is_goods_orders, is_services_orders, purchase_request_id, sh_purchase_user_id, sh_agreement_type, partner_ids, days_left, analytic_accounting, account_tag_ids, branch_id, destination_warehouse_id, set_single_delivery_destination, set_single_delivery_date, comparison_ids, tender_scope, tender_name, company_id, currency_id, amount_total, is_price_ratting_rfq_tender, show_analytic_tags, sh_order_date, sh_delivery_date, state, state1, state4, state2, pt_state, state3, state5, approval_matrix, amount, approval_matrix_line_ids, user_approval_ids, current_user, partner_id, approver, line_approve, is_approve_button, approval_matrix_line_id, sh_bid_agreement_deadline, sh_bid_selection_agreement_deadline, is_purchase_tender_approval_matrix, term_condition, term_condition_box, sh_notes, sh_partner_id, vendor_names, purchase_order_ids, is_assets_orders, legal_documents_ids, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.agreement", "table_name": ""}
+{"text": "List all fields in the salesperson.tracking.history model.", "response": "The salesperson.tracking.history model has 11 fields: name, marker, history_data, tracking_history_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, binary: 1, html: 1, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "salesperson.tracking.history", "table_name": ""}
+{"text": "What does the report.membership model represent?", "response": "The report.membership model represents Membership Analysis in the ERP system. It contains 17 fields and is used to manage membership analysis data. Key fields include: start_date, date_to, num_waiting, num_invoiced, num_paid, tot_pending, tot_earned, partner_id, associate_member_id, membership_id, membership_state, user_id, company_id, quantity, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.membership", "table_name": ""}
+{"text": "Show me the fields of ir.server.object.lines.", "response": "The ir.server.object.lines model has 12 fields: server_id, col1, value, evaluation_type, resource_ref, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, text: 1, selection: 1, reference: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.server.object.lines", "table_name": ""}
+{"text": "What fields does pos.loyalty have?", "response": "The pos.loyalty model has 24 fields: name, rule_ids, reward_ids, product_redeem_ids, reward_redeem_ids, count_product_redeem, state, type, product_loyalty_id, rounding, rounding_down, config_ids, pos_config_ids, period_expired, start_date, end_date, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, one2many: 5, integer: 3, selection: 2, many2one: 4, float: 1, boolean: 1, many2many: 1, datetime: 5.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.loyalty", "table_name": ""}
+{"text": "Describe the purchase.request.warning.line model in Odoo.", "response": "The purchase.request.warning.line model represents Purchase Request Line Warning in the ERP system. It contains 11 fields and is used to manage purchase request line warning data. Key fields include: warning_id, product_id, purchase_req_budget, realized_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.request.warning.line", "table_name": ""}
+{"text": "List all fields in the kpi.period.value model.", "response": "The kpi.period.value model has 10 fields: period_id, constant_id, target_value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "kpi.period.value", "table_name": ""}
+{"text": "Show me the fields of payment.voucher.", "response": "The payment.voucher model has 63 fields: create_by, name, partner_id, partner_ids, date, bank_id, cheque_number, cheque_date, vendor_bill_ids, remarks, company_id, request_partner_id, currency_id, line_ids, branch_id, state, amount, amount_text, payment_ids, payment_count, approval_matrix_id, is_payment_voucher_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state1, state2, amount_to_text, invoice_cutoff_date, vendor_allowed_ids, is_cutoff_date, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 14, char: 8, many2many: 5, date: 5, text: 1, one2many: 7, selection: 5, monetary: 1, integer: 6, boolean: 8, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "payment.voucher", "table_name": ""}
+{"text": "What are the relationships in report.reordering?", "response": "The report.reordering model has 4 relational fields: warehouse_id -> stock.warehouse; location_ids -> stock.location; create_uid -> res.users; write_uid -> res.users. Many2many fields: location_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.reordering", "table_name": ""}
+{"text": "How is customer.target used in the system?", "response": "The customer.target model represents Customer Target in the ERP system. It contains 32 fields and is used to manage customer target data. Key fields include: name, res_name, company_id, applied_to, customer_categ_id, partner_ids, target_amount, currency_id, start_date, end_date, reward_type, disc_type, disc_amount, disc_percentage, product_id, quantity, discount_line_product_id, customer_voucher_ids, customer_voucher_count, apply_cashback, percentage, fixed_amount, voucher_type, voucher_expiration, free_product_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "customer.target", "table_name": ""}
+{"text": "Can you explain the purpose of pos.top.selling.wizard?", "response": "The pos.top.selling.wizard model represents POS Top Selling Wizard in the ERP system. It contains 14 fields and is used to manage pos top selling wizard data. Key fields include: start_dt, end_dt, report_type, no_product, top_selling, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.top.selling.wizard", "table_name": ""}
+{"text": "Which fields in multiple.rfq are computed?", "response": "The multiple.rfq model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "multiple.rfq", "table_name": ""}
+{"text": "How is sms.api used in the system?", "response": "The sms.api model represents SMS API in the ERP system. It contains 3 fields and is used to manage sms api data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sms.api", "table_name": ""}
+{"text": "What models are connected to mail.message.subtype?", "response": "The mail.message.subtype model has 3 relational fields: parent_id -> mail.message.subtype; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.message.subtype", "table_name": ""}
+{"text": "What modules define sh_barcode_scanner_adv.search.document?", "response": "The sh_barcode_scanner_adv.search.document model is defined in module: sh_all_in_one_mbs. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh_barcode_scanner_adv.search.document", "table_name": ""}
+{"text": "What fields does account.vendor.deposit.reconcile have?", "response": "The account.vendor.deposit.reconcile model has 9 fields: date, allocation_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.vendor.deposit.reconcile", "table_name": ""}
+{"text": "What business logic is in sh.custom.tab.purchase?", "response": "To use the sh.custom.tab.purchase model, you need to provide values for required fields: none. Readonly fields: invisible_tab, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.custom.tab.purchase", "table_name": ""}
+{"text": "How is payment.voucher.matrix.reject used in the system?", "response": "The payment.voucher.matrix.reject model represents Payment Voucher Matrix Reject in the ERP system. It contains 8 fields and is used to manage payment voucher matrix reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "payment.voucher.matrix.reject", "table_name": ""}
+{"text": "What are the relationships in web.environment.ribbon.backend?", "response": "The web.environment.ribbon.backend model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "web.environment.ribbon.backend", "table_name": ""}
+{"text": "What are common use cases for auditlog.autovacuum?", "response": "To use the auditlog.autovacuum 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "auditlog.autovacuum", "table_name": ""}
+{"text": "How does mrp.production relate to other models?", "response": "The mrp.production model has 43 relational fields: product_id -> product.product; allowed_product_ids -> product.product; product_tmpl_id -> product.template; product_uom_id -> uom.uom; lot_producing_id -> stock.production.lot; product_uom_category_id -> uom.category; picking_type_id -> stock.picking.type; location_src_id -> stock.location; location_dest_id -> stock.location; bom_id -> mrp.bom; move_raw_ids -> stock.move; move_finished_ids -> stock.move; move_byproduct_ids -> stock.move; finished_move_line_ids -> stock.move.line; workorder_ids -> mrp.workorder; move_dest_ids -> stock.move; user_id -> res.users; company_id -> res.company; procurement_group_id -> procurement.group; orderpoint_id -> stock.warehouse.orderpoint; scrap_ids -> stock.scrap; production_location_id -> stock.location; picking_ids -> stock.picking; sh_mrp_quality_check_ids -> sh.mrp.quality.check; sh_mrp_quality_alert_ids -> sh.mrp.quality.alert; sh_mrp_pass_fail_ids -> sh.mrp.pass.fail; sh_mrp_pics_ids -> sh.mrp.pics; sh_mrp_measurement_ids -> sh.mrp.measurement; sh_mrp_qc_measurement_ids -> sh.mrp.qc.measurement; attachment_ids -> ir.attachment; sh_mrp_quality_point_id -> sh.qc.point; partner_id -> res.partner; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: allowed_product_ids, picking_ids, attachment_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.production", "table_name": ""}
+{"text": "How do I use the sale.order.template.line model?", "response": "To use the sale.order.template.line model, you need to provide values for required fields: sale_order_template_id, name, product_uom_qty. Readonly fields: company_id, product_uom_category_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.template.line", "table_name": ""}
+{"text": "How to create records in sale.data.margin.line?", "response": "To use the sale.data.margin.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.data.margin.line", "table_name": ""}
+{"text": "Which fields in pos.loyalty.reward are computed?", "response": "The pos.loyalty.reward model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.loyalty.reward", "table_name": ""}
+{"text": "What are the available fields for res.config.settings?", "response": "The res.config.settings model has 849 fields: user_default_rights, external_email_server_default, module_base_import, module_google_calendar, module_microsoft_calendar, module_google_drive, module_google_spreadsheet, module_auth_oauth, module_auth_ldap, module_base_gengo, module_account_inter_company_rules, module_pad, module_voip, module_web_unsplash, module_partner_autocomplete, module_base_geolocalize, module_google_recaptcha, report_footer, group_multi_currency, paperformat_id, external_report_layout_id, show_effect, company_count, active_user_count, language_count, company_name, company_informations, app_default_superbar_lazy_search, geoloc_provider_id, geoloc_provider_techname, geoloc_provider_googlemap_key, recaptcha_public_key, recaptcha_private_key, recaptcha_min_score, fail_counter, alias_domain, unsplash_access_key, app_system_name, app_show_lang, app_show_debug, app_show_documentation, app_show_documentation_dev, app_show_support, app_show_account, app_show_enterprise, app_show_share, app_show_poweredby, group_show_author_in_apps, module_odoo_referral, app_documentation_url, app_documentation_dev_url, app_support_url, app_account_title, app_account_url, app_enterprise_url, app_ribbon_name, auth_signup_reset_password, auth_signup_template_user_id, resource_calendar_id, module_hr_presence, module_hr_skills, hr_presence_control_login, hr_presence_control_email, hr_presence_control_ip, module_hr_attendance, hr_presence_control_email_amount, hr_presence_control_ip_list, hr_employee_self_edit, kpi_company_id, kpi_history_tolerance, show_kpi_help, group_discount_per_so_line, group_uom, group_product_variant, module_sale_product_configurator, module_sale_product_matrix, group_stock_packaging, group_product_pricelist, group_sale_pricelist, product_pricelist_setting, product_weight_in_lbs, product_volume_volume_in_cubic_feet, enable_menu_search, enable_web_push_notification, api_key, vapid, config_details, sh_multi_barcode_unique, is_sh_product_qrcode_generator_when_create, snailmail_color, snailmail_cover, snailmail_duplex, digest_emails, digest_id, company_id, sh_product_stock, sh_product_attribute, sh_product_image, sh_product_category, sh_product_code, sh_product_barcode, sh_product_sale_price, sh_product_sale_description, sh_touch_kyboard, sh_welcome_message, sh_message, sh_company_logo, sh_display, sh_display_view, sh_display_landscape, sh_display_portrait, sh_delay_screen, has_accounting_entries, currency_id, has_chart_of_accounts, chart_template_id, purchase_tax_id, tax_calculation_rounding_method, module_account_accountant, group_analytic_accounting, group_warning_account, group_cash_rounding, group_show_line_subtotals_tax_excluded, group_show_line_subtotals_tax_included, group_show_sale_receipts, group_show_purchase_receipts, show_line_subtotals_tax_selection, module_account_budget, module_account_payment, module_account_reports, module_account_check_printing, module_account_batch_payment, module_account_sepa, module_account_sepa_direct_debit, module_account_plaid, module_account_yodlee, module_account_bank_statement_import_qif, module_account_bank_statement_import_ofx, module_account_bank_statement_import_csv, module_account_bank_statement_import_camt, module_currency_rate_live, module_account_intrastat, module_product_margin, module_l10n_eu_service, module_account_taxcloud, module_account_invoice_extract, module_snailmail_account, tax_exigibility, tax_cash_basis_journal_id, account_cash_basis_base_account_id, qr_code, invoice_is_print, invoice_is_email, incoterm_id, invoice_terms, use_invoice_terms, country_code, crm_alias_prefix, generate_lead_from_alias, group_use_lead, group_use_recurring_revenues, module_crm_iap_lead, module_crm_iap_lead_website, module_crm_iap_lead_enrich, module_mail_client_extension, lead_enrich_auto, lead_mining_in_pipeline, predictive_lead_scoring_start_date, predictive_lead_scoring_start_date_str, predictive_lead_scoring_fields, predictive_lead_scoring_fields_str, group_mass_mailing_campaign, mass_mailing_outgoing_mail_server, mass_mailing_mail_server_id, show_blacklist_buttons, module_project_forecast, module_hr_timesheet, group_subtask_project, group_project_rating, group_project_recurring_tasks, module_product_expiry, group_stock_production_lot, group_lot_on_delivery_slip, group_stock_tracking_lot, group_stock_tracking_owner, group_stock_adv_location, group_warning_stock, group_stock_sign_delivery, module_stock_picking_batch, module_stock_barcode, stock_move_email_validation, stock_mail_confirmation_template_id, module_stock_sms, group_stock_multi_locations, website_id, website_name, website_domain, website_country_group_ids, website_company_id, website_logo, language_ids, website_language_count, website_default_lang_id, website_default_lang_code, specific_user_account, website_cookies_bar, google_analytics_key, google_management_client_id, google_management_client_secret, google_search_console, cdn_activated, cdn_url, cdn_filters, social_twitter, social_facebook, social_github, social_linkedin, social_youtube, social_instagram, has_social_network, favicon, social_default_image, google_maps_api_key, group_multi_website, has_google_analytics, has_google_analytics_dashboard, has_google_maps, has_google_search_console, has_default_share_image, account_check_printing_layout, account_check_printing_date_label, account_check_printing_multi_stub, account_check_printing_margin_top, account_check_printing_margin_left, account_check_printing_margin_right, vat_check_vies, group_show_form_view, picking_operation_type, sh_it_barcode_mobile_type, sh_it_bm_is_cont_scan, sh_it_bm_is_notify_on_success, sh_it_bm_is_notify_on_fail, sh_it_bm_is_sound_on_success, sh_it_bm_is_sound_on_fail, sh_it_bm_is_add_product, module_project_timesheet_synchro, module_project_timesheet_holidays, project_time_mode_id, timesheet_encode_uom_id, timesheet_min_duration, timesheet_rounding, is_encode_uom_days, manufacturing_lead, use_manufacturing_lead, group_mrp_byproducts, module_mrp_mps, module_mrp_plm, module_mrp_workorder, module_quality_control, module_mrp_subcontracting, group_mrp_routings, group_locked_by_default, group_expiry_date_on_delivery_slip, lock_confirmed_po, po_lock, po_order_approval, po_double_validation, po_double_validation_amount, company_currency_id, default_purchase_method, group_warning_purchase, module_account_3way_match, module_purchase_requisition, module_purchase_product_matrix, po_lead, use_po_lead, group_send_reminder, module_sg_bank_reconcile, module_sg_dbs_giro, sh_invoice_online_signature, sh_enable_approval, sh_restrict_for_close_period, invoice_is_snailmail, module_stock_landed_costs, stock_qty_forecast_method, stock_qty_forecast_interval, stock_qty_predicted_periods, stock_move_sms_validation, stock_sms_confirmation_template_id, channel_id, group_enable_discuss, group_disable_poll, app_stop_subscribe, inv_cost, is_cost_price_per_warehouse, fiscalyear_last_day, fiscalyear_last_month, period_lock_date, fiscalyear_lock_date, group_fiscal_year, sale_tax_id, module_pos_mercury, module_pos_adyen, module_pos_six, update_stock_quantities, module_stock_dropshipping, days_to_purchase, is_installed_sale, group_auto_done_setting, module_sale_margin, quotation_validity_days, use_quotation_validity_days, group_warning_sale, portal_confirmation_sign, portal_confirmation_pay, group_sale_delivery_address, group_proforma_sales, default_invoice_policy, deposit_default_product_id, auth_signup_uninvited, module_delivery, module_delivery_dhl, module_delivery_fedex, module_delivery_ups, module_delivery_usps, module_delivery_bpost, module_delivery_easypost, module_product_email_template, module_sale_coupon, module_sale_amazon, automatic_invoice, template_id, confirmation_template_id, sh_group_enable_report_section, group_enable_merge_purchase_order, po_operation_type, cancel_receipt, cancel_bill, group_enable_purchase_checklist, group_enable_purchase_custom_product_template, purchase_show_signature, chk_sign_confirm, purchase_enable_other_sign_option, sh_expiry_notification, sh_is_notify_vendor, sh_on_date_notify, enter_before_first_notify, enter_before_second_notify, enter_before_third_notify, enter_after_first_notify, enter_after_second_notify, enter_after_third_notify, attachment_email, group_enable_purchase_multi_product_adv, sh_purchase_configuration_limit, group_enable_purchase_order_history, item_limit_purchase, record_based_on_purchase, group_enable_purchase_price_history, purchase_order_information_in_message, purchase_product_detail_in_message, purchase_signature, purchase_display_in_message, po_send_pdf_in_message, sh_auto_add_followers, sh_portal_user_create, sh_tender_document_manage, sh_purchase_revision, is_enable_vendor_notification, user_ids, is_enable_auto_portal_user, is_enable_company_portal_user, is_enable_company_contact_portal_user, crm_default_team_id, crm_default_user_id, l10n_id_tax_address, l10n_id_tax_name, reminder_frequency, group_sale_order_template, company_so_template_id, module_sale_quotation_builder, security_lead, group_display_incoterm, group_lot_on_invoice, use_security_lead, default_picking_policy, sh_manage_tender_doc_portal, lc_journal_id, salesperson_id, salesteam_id, module_website_sale_delivery, sale_delivery_settings, group_delivery_invoice_address, module_website_sale_digital, module_website_sale_wishlist, module_website_sale_comparison, module_website_sale_stock, module_account, cart_recovery_mail_template, cart_abandoned_delay, mailsend_check, email_notification_days, res_user_ids, validate_picking, create_invoice, validate_invoice, allow_auto_intercompany, ks_forecast_method, use_sale_order_note, sale_order_note, keep_name_so, sh_sale_barcode_mobile_type, sh_sale_bm_is_cont_scan, sh_sale_bm_is_notify_on_success, sh_sale_bm_is_notify_on_fail, sh_sale_bm_is_sound_on_success, sh_sale_bm_is_sound_on_fail, sh_purchase_barcode_mobile_type, sh_purchase_bm_is_cont_scan, sh_purchase_bm_is_notify_on_success, sh_purchase_bm_is_notify_on_fail, sh_purchase_bm_is_sound_on_success, sh_purchase_bm_is_sound_on_fail, sh_invoice_barcode_mobile_type, sh_invoice_bm_is_cont_scan, sh_invoice_bm_is_notify_on_success, sh_invoice_bm_is_notify_on_fail, sh_invoice_bm_is_sound_on_success, sh_invoice_bm_is_sound_on_fail, sh_bom_barcode_mobile_type, sh_bom_bm_is_cont_scan, sh_bom_bm_is_notify_on_success, sh_bom_bm_is_notify_on_fail, sh_bom_bm_is_sound_on_success, sh_bom_bm_is_sound_on_fail, sh_stock_barcode_mobile_type, sh_stock_bm_is_cont_scan, sh_stock_bm_is_notify_on_success, sh_stock_bm_is_notify_on_fail, sh_stock_bm_is_sound_on_success, sh_stock_bm_is_sound_on_fail, sh_stock_bm_is_add_product, sh_inventory_adjt_barcode_mobile_type, sh_inventory_adjt_bm_is_cont_scan, sh_inventory_adjt_bm_is_notify_on_success, sh_inventory_adjt_bm_is_notify_on_fail, sh_inventory_adjt_bm_is_sound_on_success, sh_inventory_adjt_bm_is_sound_on_fail, sh_product_barcode_mobile_type, sh_product_bm_is_cont_scan, sh_product_bm_is_notify_on_success, sh_product_bm_is_notify_on_fail, sh_product_bm_is_sound_on_success, sh_product_bm_is_sound_on_fail, sh_product_bm_is_default_code, sh_product_bm_is_lst_price, sh_product_bm_is_qty_available, sh_product_bm_is_virtual_available, sh_global_document_search_is_enable, sh_global_document_search_is_sale, sh_global_document_search_is_purchase, sh_global_document_search_is_picking, sh_global_document_search_is_invoice, sh_global_document_search_is_product, sh_global_document_search_is_lot, sh_global_document_search_is_location, sh_global_document_search_action_target_type, sale_credit_limit_email_alerts, sale_email_specific_user_id, quot_to_po, so_to_po, inventory_availability, available_threshold, website_warehouse_id, down_payment_product_id, implementor_setting, general, purchase, sales, inventory, manufacturing, central_kitchen, human_resource, pos, simple_manufacturing, assembly, cutting, mining, agriculture, show_branch, past_x_days_sales, currency_exchange_journal_id, income_currency_exchange_account_id, expense_currency_exchange_account_id, unrealized_exchange_journal_id, income_unrealized_exchange_account_id, expense_unrealized_exchange_account_id, is_inverse_rate, is_taxes_rate, tax_discount_policy, sale_account_id, purchase_account_id, interest_income, interest_expense, deposit_reconcile_journal_id, journal_id, deposit_account_id, petty_cash_expense_account_id, overdue_template, tax_rounding_type, accounting, is_credit_note_approval_matrix, is_refund_approval_matrix, is_customer_deposit_approval_matrix, is_vendor_deposit_approval_matrix, is_receipt_giro_approval_matrix, is_payment_giro_approval_matrix, is_purchase_currency_approval_matrix, is_budget_approval_matrix, is_budget_change_req_approval_matrix, is_purchase_budget_approval_matrix, is_purchase_budget_change_req_approval_matrix, is_internal_transaction, is_analytic_groups_balance_sheet, is_assets_approving_matrix, is_cash_advance_approving_matrix, is_invoice_approval_matrix, is_bill_approval_matrix, is_other_income_approval_matrix, is_other_expense_approval_matrix, is_customer_multi_receipt_approval_matrix, is_vendor_multipayment_approval_matrix, is_receipt_approval_matrix, is_payment_approval_matrix, is_payment_voucher_approval_matrix, group_is_credit_note_approval_matrix, group_is_refund_approval_matrix, group_is_customer_deposit_approval_matrix, group_is_vendor_deposit_approval_matrix, group_is_receipt_giro_approval_matrix, group_is_payment_giro_approval_matrix, group_is_internal_transfer_approval_matrix, group_is_purchase_currency_approval_matrix, group_is_budget_approval_matrix, group_is_budget_change_req_approval_matrix, group_is_purchase_budget_approval_matrix, group_is_purchase_budget_change_req_approval_matrix, group_account_asset_category_fiscal, group_assets_approving_matrix, group_cash_advance_approval_matrix, group_is_invoice_approval_matrix, group_is_bill_approval_matrix, group_is_other_income_approval_matrix, group_is_other_expense_approval_matrix, group_is_customer_multi_receipt_approval_matrix, group_is_vendor_multipayment_approval_matrix, group_is_receipt_approval_matrix, group_is_payment_approval_matrix, group_is_payment_voucher_approval_matrix, module_om_account_budget, Use_received_date, customer_availability, automated_invoice_followup, followup_sending_date, reminder_interval_before, reminder_interval_before_unit, reminder_notification_before, reminder_interval_after, reminder_interval_after_unit, reminder_notification_after, invoice_bill_reminder, reminder_interval_before_invoice, reminder_interval_after_invoice, reminder_interval_before_unit_invoice, eminder_interval_after_unit_invoice, reminder_notification_before_invoice, reminder_notification_after_invoice, days_bill_before, days_bill_after, days_invoice_before, days_invoice_after, sending_date_bill_before, sending_date_bill_after, sending_date_invoice_before, sending_date_invoice_after, date_last_reminder_due_date, date_last_reminder_after_due_date, date_last_reminder_bill_due_date, date_last_reminder_bill_after_due_date, date_last_reminder_bill_before_due_date, is_invoice_cutoff_date, invoice_cutoff_date, post_discount_account, prefix_limit, is_material_request_approval_matrix, is_internal_transfer_approval_matrix, is_stock_count_approval, is_product_usage_approval, is_return_orders, return_type, is_inventory_adjustment_with_value, putaway_max_capacity, set_warehouse_sublevel, warehouse_sublevel_zone, warehouse_sublevel_shelf, warehouse_sublevel_rack, warehouse_sublevel_bin, group_is_three_dimension_warehouse, is_mbs_on_transfer_operations, is_mbs_on_product_usage, is_mbs_on_stock_count_and_inventory_adjustment, outgoing_routing_strategy, sort_quants_by, routing_order, is_receiving_notes_approval_matrix, is_adj_picking, is_delivery_order_approval_matrix, brand_setting, is_manufacturing_plan, allow_submit_purchase_request, allow_submit_material_request, mo_force_done, manufacturing_plan_conf, manufacturing_order_conf, mrp_plan_partial_availability, mp_auto_reserve_availability_materials, mo_auto_reserve_availability_materials, production_record_conf, mrp_production_partial_availability, mrp_submit_purchase_request, mrp_submit_material_request, mrp_force_done, manufacturing_mps, manufacturing_period, manufacturing_period_to_display, autogenerated_based_methods, send_wa_approval_notification_mrp, send_wa_approval_notification_mp, send_wa_approval_notification_mpr, is_vendor_approval_matrix, is_purchase_order_approval_matrix, is_purchase_request_approval_matrix, is_vendor_pricelist_approval_matrix, is_purchase_tender_approval_matrix, purchase_approval_matrix, is_blanket_order_approval_matrix, is_good_services_order, is_purchase_tender, is_blanket_order, is_direct_purchase_approval_matrix, is_pr_department, is_price_ratting_rfq_tender, retail, module_equip3_purchase_rental, is_product_brand_filter, is_product_vendor_pricelist_filter, is_service_work_order, is_purchase_request_assign_user, group_create_purchase_request_direct, is_customer_approval_matrix, is_customer_limit_matrix, is_over_limit_validation, is_bo_approval_matrix, show_sale_barcode_mobile_type, sh_sale_barcode_mobile_type_new, group_om_account_budget, credit_note_expiry_date, bom_tools, sale_order_multiple_pricelist, automatic_confirm_saleorder, automatic_invoice_create, is_delivery_acknowledgement, is_broadcast_order, module_pragmatic_portal_user, module_pragmatic_delivery_acknowledgement, module_pragmatic_website_cash_on_delivery, commission_pay_on, commission_calc, commission_pay_by, is_message_rn, send_notification_users_ids, bank_integrate_url, bank_integrate_username, bank_integrate_password, validate_api, accounting_budget_use_theoretical_achievement, is_pajak_express_integration, pajak_express_url, pajak_express_transaction_url, pajak_express_username, pajak_express_password, validate_api_first, validate_api_express, validate_api_express_fail, group_is_pajak_express_integration, is_call_bi_api, is_call_kemenkeu_api, token_kemenkeu_api, internal_type, ex_period, material_request, is_product_service_operation, is_product_service_operation_delivery, mr_expiry_days, itr_expiry_days, is_return_limit_policy, return_policy_days, is_display_warehouse_address, module_procurement_jit, is_warehouse_shipments, qty_can_minus, is_vendor_approval_email, is_vendor_approval_whatsapp, is_vendor_pricelist_approval_email, is_vendor_pricelist_approval_whatsapp, sale_matrix_config, is_total_amount, total_sequence, total_sequence_select, is_margin_amount, margin_sequence, margin_sequence_select, is_discount_amount, discount_sequence, discount_sequence_select, expired_date, multilevel_disc_sale, is_wa_so_approval, is_email_so_approval, show_select_product_button, lock_sale_order, product_pricelist_default, auto_mail, group_multi_do, whatsapp_instance_id, whatsapp_token, qr_code_image, whatsapp_authenticate, product_expiry, expiry_days_select, group_analytic_tags, pu_barcode_mobile_type, pu_bm_is_cont_scan, pu_bm_is_notify_on_success, pu_bm_is_notify_on_fail, pu_bm_is_sound_on_success, pu_bm_is_sound_on_fail, pu_bm_is_add_product, pr_expiry_notification, pr_on_date_notify, pr_enter_before_first_notify, pr_enter_after_first_notify, pr_expiry_date, pr_expiry_date_goods, pr_expiry_date_services, rfq_exp_date, po_exp_date, rfq_exp_date_goods, rfq_exp_date_services, po_exp_date_goods, po_exp_date_services, max_percentage, pr_qty_limit, multilevel_disc, is_email_notification_req, is_whatsapp_notification_req, vendor_purchase_limit, is_email_notification, is_whatsapp_notification, pr_order_average_price, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, customer_credit_limit, customer_max_invoice_overdue_days, customer_open_invoice_limit, is_over_credit_limit, over_credit_limit_sequence, over_credit_limit_sequence_select, is_invoice_overdue, invoice_overdue_sequence, invoice_overdue_sequence_select, open_invoice_limit, open_invoice_limit_sequence, open_invoice_limit_sequence_select, is_wa_overlimit_approval, is_email_overlimit_approval, is_email_notification_customer_credit, is_whatsapp_notification_customer_credit, group_use_multi_salesperson_on_leads, is_auto_follow_up, interval_number, interval_type, number_of_repetition, expired_lot_serial_no, is_auto_validate, scrap_income_id, scrap_expense_id, pt_expiry_notification, pt_on_date_notify, pt_enter_before_first_notify, pt_enter_after_first_notify, pt_expiry_date, bo_expiry_notification, bo_enter_before_first_notify, bo_enter_after_first_notify, pt_goods_order_expiry_date, pt_service_order_expiry_date, bo_goods_order_expiry_date, bo_service_order_expiry_date, is_email_notification_tender, is_whatsapp_notification_tender, is_email_notification_bo, is_whatsapp_notification_bo, notifications_expiry_voucher, notifications_time, bo_expiry_date, bo_before_exp_notify, bo_days_before_exp_notify, bo_on_date_notify, bo_approval_email_notify, bo_approval_wa_notify, is_order_rounding, order_rounding_type, rounding_multiplier, pos_product_discount1_id, apply_rounding_type, rounding_method_id, pos_def_receipt_template_id, is_pos_receivable, direct_control, qty_limit, budget_limit, is_email_notification_direct_purchase, is_whatsapp_notification_direct_purchase, is_post_closing_cashbox_value_in_session, allow_create_member_in_pos_screen, pkp_customer, membership_pluspoint_rounding, membership_pluspoint_rounding_type, membership_pluspoint_rounding_multiplier, is_pos_use_deposit, is_return_request_approval_matrix, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 535, text: 7, many2one: 61, integer: 71, char: 52, float: 16, selection: 85, date: 8, many2many: 6, binary: 4, monetary: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.config.settings", "table_name": ""}
+{"text": "What does the res.branch model represent?", "response": "The res.branch model represents Branch of shops, like a multi company in the ERP system. It contains 50 fields and is used to manage branch of shops, like a multi company data. Key fields include: analytic_tag_ids, name, company_id, telephone, address, street, street_2, city, state_id, country_id, zip_code, active_company_sequence, npwp, user_id, user_ids, is_external_link, config_ids, branch_code, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.branch", "table_name": ""}
+{"text": "What does the stock.picking.batch.line model represent?", "response": "The stock.picking.batch.line model represents stock.picking.batch.line in the ERP system. It contains 18 fields and is used to manage stock.picking.batch.line data. Key fields include: sequence, transfer_id, product_id, name, location_id, demand_qty, reserved_qty, done_qty, uom_id, picking_batch_id, origin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.picking.batch.line", "table_name": ""}
+{"text": "Show me the relational structure of gamification.karma.tracking.", "response": "The gamification.karma.tracking model has 3 relational fields: user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "gamification.karma.tracking", "table_name": ""}
+{"text": "List all fields in the allfresh.consignment.report model.", "response": "The allfresh.consignment.report model has 15 fields: date_order, pos_ref, pos_branch_id, barcode, product_id, qty, price, margin, total_margin, consignment_move_id, currency_id, company_id, id, display_name, __last_update. Field types distribution: datetime: 2, char: 3, many2one: 5, float: 1, monetary: 3, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "allfresh.consignment.report", "table_name": ""}
+{"text": "Describe the implementation of account.print.journal.", "response": "The account.print.journal model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.print.journal", "table_name": ""}
+{"text": "What are the technical details of stock.package_level?", "response": "The stock.package_level model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.package_level", "table_name": ""}
+{"text": "What foreign keys exist in stock.move?", "response": "The stock.move model has 92 relational fields: company_id -> res.company; product_uom -> uom.uom; product_uom_category_id -> uom.category; product_tmpl_id -> product.template; location_id -> stock.location; location_dest_id -> stock.location; partner_id -> res.partner; move_dest_ids -> stock.move; move_orig_ids -> stock.move; picking_partner_id -> res.partner; backorder_id -> stock.picking; scrap_ids -> stock.scrap; group_id -> procurement.group; rule_id -> stock.rule; picking_type_id -> stock.picking.type; inventory_id -> stock.inventory; move_line_ids -> stock.move.line; move_line_nosuggest_ids -> stock.move.line; origin_returned_move_id -> stock.move; returned_move_ids -> stock.move; restrict_partner_id -> res.partner; route_ids -> stock.location.route; warehouse_id -> stock.warehouse; package_level_id -> stock.package_level; orderpoint_id -> stock.warehouse.orderpoint; lot_ids -> stock.production.lot; created_production_id -> mrp.production; production_id -> mrp.production; raw_material_production_id -> mrp.production; unbuild_id -> mrp.unbuild; consume_unbuild_id -> mrp.unbuild; allowed_operation_ids -> mrp.routing.workcenter; operation_id -> mrp.routing.workcenter; workorder_id -> mrp.workorder; bom_line_id -> mrp.bom.line; byproduct_id -> mrp.bom.byproduct; order_finished_lot_ids -> stock.production.lot; account_move_ids -> account.move; stock_valuation_layer_ids -> stock.valuation.layer; scrap_return_move_id -> stock.move.line; purchase_line_id -> purchase.order.line; created_purchase_line_id -> purchase.order.line; sh_quality_point_id -> sh.qc.point; created_purchase_request_line_id -> purchase.request.line; purchase_request_allocation_ids -> purchase.request.allocation; purchase_request_ids -> purchase.request; requisition_line_ids -> purchase.requisition.line; sale_line_id -> sale.order.line; branch_id -> res.branch; repair_id -> repair.order; product_id -> product.product; move_package_id -> stock.quant.package; filter_move_package_ids -> stock.quant.package; mr_line_id -> material.request.line; analytic_account_group_ids -> account.analytic.tag; responsible -> res.users; package_type -> product.packaging; packaging_ids -> product.packaging; package_quant_ids -> stock.quant; measure_ids -> measure.for.packaging; source_picking_id -> stock.picking; source_move_id -> stock.move; created_assembly_id -> assembly.production.record; assembly_finished_id -> assembly.production.record; assembly_component_id -> assembly.production.record; created_kitchen_id -> kitchen.production.record; kitchen_finished_id -> kitchen.production.record; kitchen_component_id -> kitchen.production.record; asp_asm_stock_id -> asp.asm.stock; finish_good_rework_id -> finish.good.rework; finish_good_rework_finished_id -> finish.good.rework; finish_good_rework_created_kitchen_id -> finish.good.rework; finish_good_rework_by_product_id -> finish.good.rework; assembly_product_id -> product.product; assembly_bom_id -> mrp.bom; kitchen_product_id -> product.product; kitchen_bom_id -> mrp.bom; product_warehouse -> stock.location; product_location -> stock.warehouse; vendor_id -> res.partner; reserved_by_id -> res.users; picking_id -> stock.picking; return_reason -> return.reason; combo_item_id -> pos.combo.item; pos_branch_id -> res.branch; pos_order_line_id -> pos.order.line; sale_order_id -> sale.order; purchase_order_id -> purchase.order; taxes_id -> account.tax; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: move_dest_ids, move_orig_ids, route_ids, lot_ids, allowed_operation_ids, order_finished_lot_ids, filter_move_package_ids, analytic_account_group_ids, packaging_ids, package_quant_ids, measure_ids, taxes_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.move", "table_name": ""}
+{"text": "Describe the field structure of auditlog.http.request.", "response": "The auditlog.http.request model has 13 fields: display_name, name, root_url, user_id, http_session_id, user_context, log_ids, id, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 4, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "auditlog.http.request", "table_name": ""}
+{"text": "List all fields in the sh.sale.category.xls model.", "response": "The sh.sale.category.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.sale.category.xls", "table_name": ""}
+{"text": "What models are connected to acrux.chat.connector?", "response": "The acrux.chat.connector model has 6 relational fields: company_id -> res.company; team_id -> crm.team; sale_report_id -> ir.actions.report; qc_template_ids -> qiscus.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "acrux.chat.connector", "table_name": ""}
+{"text": "Tell me about the mail.tracking.value model.", "response": "The mail.tracking.value model represents Mail Tracking Value in the ERP system. It contains 25 fields and is used to manage mail tracking value data. Key fields include: field, field_desc, field_type, field_groups, old_value_integer, old_value_float, old_value_monetary, old_value_char, old_value_text, old_value_datetime, new_value_integer, new_value_float, new_value_monetary, new_value_char, new_value_text, new_value_datetime, mail_message_id, tracking_sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.tracking.value", "table_name": ""}
+{"text": "What is the kpi.item model?", "response": "The kpi.item model represents KPI in the ERP system. It contains 36 fields and is used to manage kpi data. Key fields include: name, category_id, formula, formula_warning, line_ids, result_type, result_appearance, result_suffix, result_preffix, currency_id, result_rounding, parent_id, all_parent_ids, child_ids, measures_ids, constant_ids, kpi_ids, company_id, active, description, sequence, user_ids, user_group_ids, access_user_ids, edit_user_ids, edit_user_group_ids, edit_access_user_ids, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kpi.item", "table_name": ""}
+{"text": "What fields does import.record.data have?", "response": "The import.record.data model has 46 fields: name, state, record_type, created_date, partner_id, warehouse_id, location_id, no_return, sheet_number, error_message, product_list, file, file_name, filter_location_ids, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 7, selection: 4, date: 3, many2one: 8, integer: 6, text: 1, html: 1, binary: 1, many2many: 3, one2many: 4, boolean: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "import.record.data", "table_name": ""}
+{"text": "Describe the implementation of purchase.agreement.legal.document.", "response": "The purchase.agreement.legal.document model is defined in module: equip3_purchase_masterdata_indonesia. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.agreement.legal.document", "table_name": ""}
+{"text": "What are common use cases for ir.qweb.field.many2many?", "response": "To use the ir.qweb.field.many2many model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.many2many", "table_name": ""}
+{"text": "What are the technical details of import.record.data?", "response": "The import.record.data model is defined in module: import_data_modifier. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "import.record.data", "table_name": ""}
+{"text": "What foreign keys exist in sh.top.customers.xls?", "response": "The sh.top.customers.xls model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.top.customers.xls", "table_name": ""}
+{"text": "What are the relationships in crm.phonecall2phonecall?", "response": "The crm.phonecall2phonecall model has 6 relational fields: user_id -> res.users; tag_ids -> crm.tag; team_id -> crm.team; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.phonecall2phonecall", "table_name": ""}
+{"text": "How is mr_line.internal_transfer used in the system?", "response": "The mr_line.internal_transfer model represents mr_line.internal_transfer in the ERP system. It contains 8 fields and is used to manage mr_line.internal_transfer data. Key fields include: ir_wizard_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mr_line.internal_transfer", "table_name": ""}
+{"text": "Tell me about the account.multipayment model.", "response": "The account.multipayment model represents Multipayment in the ERP system. It contains 90 fields and is used to manage multipayment data. Key fields include: name, partner_id, amount, journal_id, currency_id, date, ref, memo, line_credit_ids, line_debit_ids, diff_amount, partner_type, total_amount_credit, total_amount_debit, payment_id_count, company_id, branch_id, create_uid, create_date, different_move_id, request_partner_id, payment_method, multipul_payment_approval_matrix_id, is_multi_payment_approval_matrix, is_approve_button, approved_matrix_ids, approval_matrix_line_id, action_validate_boolean, action_draft_boolean, action_cancel_boolean, request_for_approval_boolean, action_approved_rp_boolean, rp_reject_boolean, state_boolean, state1_boolean, state2_boolean, difference_ids, payment_difference_amount, writeoff_account_id, writeoff_label, payment_type, clearing_account_id, move_id, due_date, receive_date, clearing_date, is_vendor, state, state1, state2, payment_ids, invoice_cutoff_date, is_cutoff_date, is_check_all, 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, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.multipayment", "table_name": ""}
+{"text": "What are the relationships in report.account.report_journal?", "response": "The report.account.report_journal model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.account.report_journal", "table_name": ""}
+{"text": "Describe the pos.loyalty model in Odoo.", "response": "The pos.loyalty model represents Loyalties Program, on this object we define loyalty program, included rules of plus points and rules of redeem points in the ERP system. It contains 24 fields and is used to manage loyalties program, on this object we define loyalty program, included rules of plus points and rules of redeem points data. Key fields include: name, rule_ids, reward_ids, product_redeem_ids, reward_redeem_ids, count_product_redeem, state, type, product_loyalty_id, rounding, rounding_down, config_ids, pos_config_ids, period_expired, start_date, end_date, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.loyalty", "table_name": ""}
+{"text": "What are the available fields for purchase.order.line.wizard?", "response": "The purchase.order.line.wizard model has 14 fields: name, wizard_id, product_id, product_qty, price_unit, product_uom, price_subtotal, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2one: 5, float: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.order.line.wizard", "table_name": ""}
+{"text": "How to create records in account.fiscal.position.tax?", "response": "To use the account.fiscal.position.tax model, you need to provide values for required fields: position_id, tax_src_id. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.fiscal.position.tax", "table_name": ""}
+{"text": "What operations can I perform on ks_dashboard_item.multiplier?", "response": "To use the ks_dashboard_item.multiplier model, you need to provide values for required fields: none. Readonly fields: ks_model_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_dashboard_item.multiplier", "table_name": ""}
+{"text": "What modules define crm.lead2opportunity.partner.mass?", "response": "The crm.lead2opportunity.partner.mass model is defined in module: crm. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.lead2opportunity.partner.mass", "table_name": ""}
+{"text": "What methods are available in customer.order.dic?", "response": "The customer.order.dic model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "customer.order.dic", "table_name": ""}
+{"text": "What business logic is in report.sh_purchase_reports.sh_tv_top_vendors_doc?", "response": "To use the report.sh_purchase_reports.sh_tv_top_vendors_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_tv_top_vendors_doc", "table_name": ""}
+{"text": "What methods are available in report.sh_sale_reports.sh_top_selling_product_doc?", "response": "The report.sh_sale_reports.sh_top_selling_product_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_top_selling_product_doc", "table_name": ""}
+{"text": "Describe the setu.rfm.segment model in Odoo.", "response": "The setu.rfm.segment model represents \n        The  idea is to segment customers based on when their last purchase was, \n        how often they’ve purchased in the past, and how much they’ve spent overall. \n        All three of these measures have proven to be effective predictors of a customer's willingness to engage in marketing messages and offers.\n     in the ERP system. It contains 31 fields and is used to manage \n        the  idea is to segment customers based on when their last purchase was, \n        how often they’ve purchased in the past, and how much they’ve spent overall. \n        all three of these measures have proven to be effective predictors of a customer's willingness to engage in marketing messages and offers.\n     data. Key fields include: name, segment_description, actionable_tips, rfm_score_ids, rfm_score_syntax, rfm_score_condition, segment_rank, partner_ids, order_ids, mailing_ids, total_mailing, total_customers, total_orders, total_revenue, team_customer_segment_ids, open_lead_count, open_rfq_count, total_customers_ratio, total_orders_ratio, total_revenue_ratio, from_date, to_date, calculated_on, desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "setu.rfm.segment", "table_name": ""}
+{"text": "What are the relationships in ks.custom.query.report.column?", "response": "The ks.custom.query.report.column model has 3 relational fields: ks_cr_model_id -> ks_custom_report.ks_report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks.custom.query.report.column", "table_name": ""}
+{"text": "Which fields in report.dynamic_accounts_report.balance_sheet are computed?", "response": "The report.dynamic_accounts_report.balance_sheet model is defined in module: dynamic_accounts_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.dynamic_accounts_report.balance_sheet", "table_name": ""}
+{"text": "Describe the field structure of account.payment.term.line.", "response": "The account.payment.term.line model has 14 fields: value, value_amount, days, day_of_the_month, option, payment_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 2, float: 1, integer: 4, many2one: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.payment.term.line", "table_name": ""}
+{"text": "Describe the many2many relations for report.coupon.report_coupon.", "response": "The report.coupon.report_coupon model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.coupon.report_coupon", "table_name": ""}
+{"text": "Describe the implementation of crm.salesperson.tracking.report.", "response": "The crm.salesperson.tracking.report model is defined in module: equip3_crm_tracking. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.salesperson.tracking.report", "table_name": ""}
+{"text": "What are common use cases for sh.sale.analysis.wizard?", "response": "To use the sh.sale.analysis.wizard model, you need to provide values for required fields: sh_end_date, sh_partner_ids, sh_start_date. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.sale.analysis.wizard", "table_name": ""}
+{"text": "How is order.picking implemented technically?", "response": "The order.picking model is defined in module: equip3_accounting_salepurchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "order.picking", "table_name": ""}
+{"text": "How do I use the res.users.apikeys model?", "response": "To use the res.users.apikeys model, you need to provide values for required fields: name, user_id. Readonly fields: name, user_id, scope, create_date, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.users.apikeys", "table_name": ""}
+{"text": "What operations can I perform on format.address.mixin?", "response": "To use the format.address.mixin model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "format.address.mixin", "table_name": ""}
+{"text": "What data can be stored in mrp.immediate.production.line?", "response": "The mrp.immediate.production.line model has 10 fields: immediate_production_id, production_id, to_immediate, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.immediate.production.line", "table_name": ""}
+{"text": "How do I use the pos.login.history model?", "response": "To use the pos.login.history 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.login.history", "table_name": ""}
+{"text": "Which fields in purchase.order.report are computed?", "response": "The purchase.order.report model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.order.report", "table_name": ""}
+{"text": "How is res.users.log used in the system?", "response": "The res.users.log model represents Users Log in the ERP system. It contains 7 fields and is used to manage users log data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.users.log", "table_name": ""}
+{"text": "List all fields in the sh.qc.alert.tags model.", "response": "The sh.qc.alert.tags model has 10 fields: name, color, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 3, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.qc.alert.tags", "table_name": ""}
+{"text": "What models are connected to stock.valuation.adjustment.lines?", "response": "The stock.valuation.adjustment.lines model has 7 relational fields: cost_id -> stock.landed.cost; cost_line_id -> stock.landed.cost.lines; move_id -> stock.move; product_id -> product.product; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.valuation.adjustment.lines", "table_name": ""}
+{"text": "Show me the fields of product.warranty.", "response": "The product.warranty model has 30 fields: partner_id, phone, email, comment, accept1, product_id, serial_no, warranty_end_date, merchant, renew_no, warranty_create_date, product_serial_id, warranty_history_ids, warranty_type, warranty_team, tags_w, model_no, warranty_cost, warranty_claim_ids, warranty_sales_person, state, so_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, char: 6, text: 1, boolean: 1, date: 2, integer: 2, one2many: 2, selection: 2, many2many: 1, float: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.warranty", "table_name": ""}
+{"text": "What are the technical details of crm.activity.report?", "response": "The crm.activity.report model is defined in module: crm. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.activity.report", "table_name": ""}
+{"text": "What modules define auditlog.rule?", "response": "The auditlog.rule model is defined in module: auditlog. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "auditlog.rule", "table_name": ""}
+{"text": "What foreign keys exist in print.prenumbered.checks?", "response": "The print.prenumbered.checks model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "print.prenumbered.checks", "table_name": ""}
+{"text": "What are the technical details of barcode.nomenclature?", "response": "The barcode.nomenclature model is defined in module: barcodes. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "barcode.nomenclature", "table_name": ""}
+{"text": "What models are connected to delivery.price.rule?", "response": "The delivery.price.rule model has 3 relational fields: carrier_id -> delivery.carrier; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "delivery.price.rule", "table_name": ""}
+{"text": "What models are connected to account.cashbox.line?", "response": "The account.cashbox.line model has 6 relational fields: cashbox_id -> account.bank.statement.cashbox; currency_id -> res.currency; pos_config_id -> pos.config; pos_session_id -> pos.session; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.cashbox.line", "table_name": ""}
+{"text": "What is the assets.approval.reject model?", "response": "The assets.approval.reject model represents assets.approval.reject in the ERP system. It contains 8 fields and is used to manage assets.approval.reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assets.approval.reject", "table_name": ""}
+{"text": "How to create records in voucher.matrix.reject?", "response": "To use the voucher.matrix.reject model, you need to provide values for required fields: none. Readonly fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "voucher.matrix.reject", "table_name": ""}
+{"text": "How is invoice.template.footer used in the system?", "response": "The invoice.template.footer model represents Invoice Template Footer in the ERP system. It contains 10 fields and is used to manage invoice template footer data. Key fields include: template_id, field_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "invoice.template.footer", "table_name": ""}
+{"text": "How to create records in report_excel_gen?", "response": "To use the report_excel_gen 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report_excel_gen", "table_name": ""}
+{"text": "What are the technical details of account.analytic.tag?", "response": "The account.analytic.tag model is defined in module: analytic. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.analytic.tag", "table_name": ""}
+{"text": "What are the relationships in sh.stock.move.pass.fail?", "response": "The sh.stock.move.pass.fail model has 5 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; picking_id -> stock.picking; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.stock.move.pass.fail", "table_name": ""}
+{"text": "What is the sh.tc.top.customer.wizard model?", "response": "The sh.tc.top.customer.wizard model represents Top Customers in the ERP system. It contains 23 fields and is used to manage top customers data. Key fields include: type, date_to, date_compare_from, date_compare_to, no_of_top_item, amount_total, team_id, currency_id, company_ids, company_id, top_customer_ids, top_customer_compare_ids, lost_cust_ids, new_cust_ids, sale_currency_id, date_from, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.tc.top.customer.wizard", "table_name": ""}
+{"text": "What is the open.stock.series model?", "response": "The open.stock.series model represents Calculate trend and forecast in the ERP system. It contains 25 fields and is used to manage calculate trend and forecast data. Key fields include: stats_type, stats_for, product_id, template_id, location_id, include_children, date_start, date_end, predicted_periods, interval, forecast_method, seasons, p_coefficient, d_coefficient, q_coefficient, seasonal_p_coefficient, seasonal_d_coefficient, seasonal_q_coefficient, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "open.stock.series", "table_name": ""}
+{"text": "How is pos.payment.installment.tenor used in the system?", "response": "The pos.payment.installment.tenor model represents Pos Payment Installment Tenor in the ERP system. It contains 9 fields and is used to manage pos payment installment tenor data. Key fields include: name, value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.payment.installment.tenor", "table_name": ""}
+{"text": "Describe the implementation of crm.lead.scoring.frequency.", "response": "The crm.lead.scoring.frequency model is defined in module: crm. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.lead.scoring.frequency", "table_name": ""}
+{"text": "Describe the pos.service.charge model in Odoo.", "response": "The pos.service.charge model represents Management Service Charge in the ERP system. It contains 15 fields and is used to manage management service charge data. Key fields include: name, product_id, type, amount, distance_from, distance_to, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.service.charge", "table_name": ""}
+{"text": "What modules define hide.view.nodes?", "response": "The hide.view.nodes model is defined in module: simplify_access_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hide.view.nodes", "table_name": ""}
+{"text": "How is pos.login.history used in the system?", "response": "The pos.login.history model represents Pos Login History in the ERP system. It contains 13 fields and is used to manage pos login history data. Key fields include: user_id, pos_config_id, pos_branch_id, checkin_datetime, checkout_datetime, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.login.history", "table_name": ""}
+{"text": "Describe the field structure of sh.top.purchasing.excel.extended.", "response": "The sh.top.purchasing.excel.extended model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.top.purchasing.excel.extended", "table_name": ""}
+{"text": "What are the available fields for untaken.stock.line?", "response": "The untaken.stock.line model has 11 fields: product_id, quantity, product_unit_measure, untaken_stock_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "untaken.stock.line", "table_name": ""}
+{"text": "What fields does sh.notification.logger have?", "response": "The sh.notification.logger model has 12 fields: name, error, datetime, base_config_id, status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, datetime: 4, many2one: 3, selection: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.notification.logger", "table_name": ""}
+{"text": "How to create records in snailmail.letter.format.error?", "response": "To use the snailmail.letter.format.error 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "snailmail.letter.format.error", "table_name": ""}
+{"text": "What are the relationships in confirm.stock.sms?", "response": "The confirm.stock.sms model has 3 relational fields: pick_ids -> stock.picking; create_uid -> res.users; write_uid -> res.users. Many2many fields: pick_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "confirm.stock.sms", "table_name": ""}
+{"text": "What operations can I perform on credit.limit.product.brand?", "response": "To use the credit.limit.product.brand model, you need to provide values for required fields: none. Readonly fields: customer_avail_credit_limit, sequence2, brand_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "credit.limit.product.brand", "table_name": ""}
+{"text": "What are common use cases for milestone.contract.template?", "response": "To use the milestone.contract.template model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "milestone.contract.template", "table_name": ""}
+{"text": "What methods are available in stock.warehouse.driver?", "response": "The stock.warehouse.driver model is defined in module: pragmatic_delivery_control_app. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.warehouse.driver", "table_name": ""}
+{"text": "What methods are available in pos.coupon?", "response": "The pos.coupon model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.coupon", "table_name": ""}
+{"text": "What data can be stored in warehouse.capacity.report?", "response": "The warehouse.capacity.report model has 12 fields: company_id, warehouse_ids, location_ids, filter_location_ids, hide_location, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 3, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "warehouse.capacity.report", "table_name": ""}
+{"text": "What are the technical details of queue.jobs.kill?", "response": "The queue.jobs.kill model is defined in module: queue_job. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "queue.jobs.kill", "table_name": ""}
+{"text": "What are the technical details of report.sh_sale_reports.sh_sales_product_profit_doc?", "response": "The report.sh_sale_reports.sh_sales_product_profit_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_sales_product_profit_doc", "table_name": ""}
+{"text": "How to query res.partner data?", "response": "To use the res.partner model, you need to provide values for required fields: property_account_payable_id, property_account_receivable_id. Readonly fields: display_name, parent_name, active_lang_count, tz_offset, same_vat_partner_id, email_formatted, partner_share, contact_address, commercial_partner_id, commercial_company_name, self, country_enforce_cities, im_status, signup_valid, signup_url, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, email_normalized, is_blacklisted, 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, phone_sanitized, phone_sanitized_blacklisted, phone_blacklisted, mobile_blacklisted, message_has_sms_error, credit, debit, total_invoiced, currency_id, journal_item_count, has_unreconciled_entries, last_time_entries_checked, invoice_ids, contract_ids, bank_account_count, opportunity_count, meeting_count, task_count, is_seo_optimized, can_publish, website_url, phonecall_count, membership_state, membership_start, membership_stop, membership_cancel, payment_token_count, purchase_order_count, supplier_invoice_count, pos_order_count, on_time_rate, sale_order_count, visible_eval, country_code, last_website_so_id, report_template_id1, report_sale_template_id1, report_po_template_id1, report_delivery_template_id1, loyalty_points, visible_vat_bp, visible_nin, visible_doc_number, visible_other_tax, visible_desc_other_tax, visible_date, visible_country, visible_all, customer_sequence, debtor_id, customer_creation_date, bank_info, vendor_sequence, state1, state2, state3, is_approving_matrix_vendor, approving_matrix_vendor_id, approved_matrix_ids, is_approve_button, approval_matrix_line_id, is_similiar, similiar_partner_count, vendor_creation_date, vendor_available_purchase_limit, customer_credit_limit, is_over_credit_limit, is_invoice_overdue, open_invoice_limit, avl_open_inv_limt, filter_brand_ids, lead_sequence, pos_order_ids, pos_total_amount, pos_partner_type_id, customer_target_id, customer_voucher_count, target_amount_customer_target, pos_loyalty_point, order_count, pos_loyalty_point_available, image_1024, image_512, image_256, image_128, id, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.partner", "table_name": ""}
+{"text": "What are the available fields for account.financial.year.op?", "response": "The account.financial.year.op model has 12 fields: company_id, opening_move_posted, opening_date, fiscalyear_last_day, fiscalyear_last_month, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, boolean: 1, date: 1, integer: 2, selection: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.financial.year.op", "table_name": ""}
+{"text": "What are the technical details of board.board?", "response": "The board.board model is defined in module: board. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "board.board", "table_name": ""}
+{"text": "List all fields in the hr.employee.public model.", "response": "The hr.employee.public model has 42 fields: create_date, name, active, department_id, job_id, job_title, company_id, address_id, mobile_phone, work_phone, work_email, work_location, user_id, resource_id, resource_calendar_id, tz, color, child_ids, image_1920, image_1024, image_512, image_256, image_128, parent_id, coach_id, user_partner_id, subordinate_ids, hr_presence_state, last_activity, last_activity_time, hr_icon_display, goal_ids, badge_ids, has_badges, direct_badge_ids, child_all_count, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: datetime: 3, char: 8, boolean: 2, many2one: 12, selection: 3, integer: 3, one2many: 5, binary: 5, date: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "hr.employee.public", "table_name": ""}
+{"text": "What are the technical details of pos.combo.limit?", "response": "The pos.combo.limit model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.combo.limit", "table_name": ""}
+{"text": "What are common use cases for mail.thread.blacklist?", "response": "To use the mail.thread.blacklist model, you need to provide values for required fields: none. Readonly fields: email_normalized, is_blacklisted, message_bounce, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.thread.blacklist", "table_name": ""}
+{"text": "How is bank.account.account implemented technically?", "response": "The bank.account.account model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "bank.account.account", "table_name": ""}
+{"text": "How is purchase.request.line.make.purchase.order implemented technically?", "response": "The purchase.request.line.make.purchase.order model is defined in module: purchase_request. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.request.line.make.purchase.order", "table_name": ""}
+{"text": "Describe the implementation of purchase.down.payment.", "response": "The purchase.down.payment model is defined in module: dev_purchase_down_payment. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.down.payment", "table_name": ""}
+{"text": "What methods are available in account.multipayment?", "response": "The account.multipayment model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.multipayment", "table_name": ""}
+{"text": "Show me the fields of sh.correct.qc.measurement.", "response": "The sh.correct.qc.measurement model has 13 fields: product_id, sh_measure, sh_message, sh_text, sh_quality_point_id, picking_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 1, text: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.correct.qc.measurement", "table_name": ""}
+{"text": "What fields does journal.entry.report have?", "response": "The journal.entry.report model has 15 fields: company_id, journal_ids, account_ids, display_account, target_move, date_from, date_to, move_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 3, selection: 2, date: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "journal.entry.report", "table_name": ""}
+{"text": "What operations can I perform on tax.sale.details.report?", "response": "To use the tax.sale.details.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "tax.sale.details.report", "table_name": ""}
+{"text": "What data can be stored in sh.sale.product.profit.xls?", "response": "The sh.sale.product.profit.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.sale.product.profit.xls", "table_name": ""}
+{"text": "Show me the relational structure of recurring.move.line.", "response": "The recurring.move.line model has 6 relational fields: partner_id -> res.partner; recurring_id -> invoice.recurring; account_id -> account.account; analytic_group_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_group_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "recurring.move.line", "table_name": ""}
+{"text": "How to query purchase.bill.union data?", "response": "To use the purchase.bill.union model, you need to provide values for required fields: none. Readonly fields: name, reference, partner_id, date, amount, currency_id, company_id, vendor_bill_id, purchase_order_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.bill.union", "table_name": ""}
+{"text": "What does the pos.payment.installment.tenor model represent?", "response": "The pos.payment.installment.tenor model represents Pos Payment Installment Tenor in the ERP system. It contains 9 fields and is used to manage pos payment installment tenor data. Key fields include: name, value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.payment.installment.tenor", "table_name": ""}
+{"text": "Which fields in close.fiscal.year are computed?", "response": "The close.fiscal.year model is defined in module: sh_sync_fiscal_year. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "close.fiscal.year", "table_name": ""}
+{"text": "What methods are available in account.payment.register?", "response": "The account.payment.register model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.payment.register", "table_name": ""}
+{"text": "What foreign keys exist in full.inv.adjustment.import?", "response": "The full.inv.adjustment.import model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "full.inv.adjustment.import", "table_name": ""}
+{"text": "Describe the many2many relations for ir.exports.line.", "response": "The ir.exports.line model has 3 relational fields: export_id -> ir.exports; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.exports.line", "table_name": ""}
+{"text": "How does pos.config relate to other models?", "response": "The pos.config model has 97 relational fields: journal_id -> account.journal; invoice_journal_id -> account.journal; currency_id -> res.currency; iface_start_categ_id -> pos.category; selectable_categ_ids -> pos.category; sequence_id -> ir.sequence; sequence_line_id -> ir.sequence; session_ids -> pos.session; current_session_id -> pos.session; last_session_closing_cashbox -> account.bank.statement.cashbox; pricelist_id -> product.pricelist; available_pricelist_ids -> product.pricelist; allowed_pricelist_ids -> product.pricelist; company_id -> res.company; barcode_nomenclature_id -> barcode.nomenclature; tip_product_id -> product.product; fiscal_position_ids -> account.fiscal.position; default_fiscal_position_id -> account.fiscal.position; default_cashbox_id -> account.bank.statement.cashbox; payment_method_ids -> pos.payment.method; current_user_id -> res.users; rounding_method -> account.cash.rounding; discount_product_id -> product.product; employee_ids -> hr.employee; floor_ids -> restaurant.floor; printer_ids -> restaurant.printer; crm_team_id -> crm.team; group_pos_manager_id -> res.groups; group_pos_user_id -> res.groups; pos_receipt_template_id -> pos.receipt.template; weight_scale_barcode_format_id -> weight.scale.barcode.format; pos_config_cashbox_lines_ids -> account.cashbox.line; pos_config_cashbox_clsosing_line_ids -> account.cashbox.line; cashbox_lines_ids -> account.cashbox.line; pos_cashbox_lines_ids -> pos.account.cashbox.line; printer_id -> pos.epson; coupon_program_ids -> coupon.program; coupon_giftcard_ids -> coupon.program; user_id -> res.users; pos_allowed_return_category_ids -> pos.category; allow_pos_categories_out_of_stock -> pos.category; voucher_sequence_id -> ir.sequence; sync_to_pos_config_ids -> pos.config; internal_transfer_picking_type_id -> stock.picking.type; discount_ids -> pos.global.discount; return_method_id -> pos.payment.method; return_coupon_program_id -> coupon.program; payment_journal_ids -> account.journal; customer_default_id -> res.partner; multi_stock_operation_type_ids -> stock.picking.type; update_tax_ids -> account.tax; default_seller_id -> res.users; seller_ids -> res.users; qrcode_ids -> pos.qrcode; stock_location_ids -> stock.location; assigned_user_ids -> res.users; manager_ids -> res.users; stock_location_id -> stock.location; stock_location_dest_id -> stock.location; discount_global_id -> product.product; analytic_account_id -> account.analytic.account; iface_available_categ_ids -> pos.category; service_charge_ids -> pos.service.charge; assign_orders_to_config_ids -> pos.config; product_category_ids -> product.category; hidden_product_ids -> product.product; custom_sale_product_id -> product.product; multi_currency_ids -> res.currency; allowed_employee_ids -> hr.employee; fire_appetizer -> pos.category; fire_main_course -> pos.category; fire_dessert -> pos.category; promotion_ids -> pos.promotion; zone_id -> pos.zone; product_voucher_service_id -> product.product; product_coupon_service_id -> product.product; product_categ_ids -> pos.category; user_ids -> res.users; void_order_pin_ids -> res.users; void_order_line_pin_ids -> res.users; advertisement_image_ids -> advertisement.images; warehouse_id -> stock.warehouse; picking_type_id -> stock.picking.type; pos_branch_id -> res.branch; gift_card_account_id -> account.account; gift_card_product_id -> product.product; gift_payment_method_id -> pos.payment.method; cashbox_payment_method_id -> pos.payment.method; product_exchange_pin_ids -> res.users; select_shortcut -> pos.keyboard.shortcuts; pos_loyalty_id -> pos.loyalty; pos_loyalty_ids -> pos.loyalty; customer_deposit_account_id -> account.account; customer_deposit_reconcile_journal_id -> account.journal; analytic_group_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: selectable_categ_ids, available_pricelist_ids, allowed_pricelist_ids, fiscal_position_ids, payment_method_ids, employee_ids, printer_ids, coupon_program_ids, coupon_giftcard_ids, pos_allowed_return_category_ids, allow_pos_categories_out_of_stock, sync_to_pos_config_ids, discount_ids, payment_journal_ids, multi_stock_operation_type_ids, update_tax_ids, seller_ids, stock_location_ids, assigned_user_ids, manager_ids, iface_available_categ_ids, service_charge_ids, assign_orders_to_config_ids, product_category_ids, hidden_product_ids, multi_currency_ids, allowed_employee_ids, fire_appetizer, fire_main_course, fire_dessert, promotion_ids, product_categ_ids, user_ids, void_order_pin_ids, void_order_line_pin_ids, advertisement_image_ids, product_exchange_pin_ids, pos_loyalty_ids, analytic_group_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.config", "table_name": ""}
+{"text": "Describe the field structure of basemodel.extend.", "response": "The basemodel.extend model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "basemodel.extend", "table_name": ""}
+{"text": "What are the technical details of ir.translation?", "response": "The ir.translation model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.translation", "table_name": ""}
+{"text": "How does advertisement.images relate to other models?", "response": "The advertisement.images model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "advertisement.images", "table_name": ""}
+{"text": "What does the website.mass_mailing.popup model represent?", "response": "The website.mass_mailing.popup model represents Mailing list popup in the ERP system. It contains 10 fields and is used to manage mailing list popup data. Key fields include: mailing_list_id, website_id, popup_content, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "website.mass_mailing.popup", "table_name": ""}
+{"text": "What are the relationships in auditlog.log?", "response": "The auditlog.log model has 7 relational fields: model_id -> ir.model; user_id -> res.users; line_ids -> auditlog.log.line; http_session_id -> auditlog.http.session; http_request_id -> auditlog.http.request; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "auditlog.log", "table_name": ""}
+{"text": "What foreign keys exist in mrp.workcenter.productivity.loss.type?", "response": "The mrp.workcenter.productivity.loss.type model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.workcenter.productivity.loss.type", "table_name": ""}
+{"text": "What is the link.tracker model?", "response": "The link.tracker model represents Link Tracker in the ERP system. It contains 22 fields and is used to manage link tracker data. Key fields include: url, absolute_url, short_url, redirected_url, short_url_host, title, label, link_code_ids, code, link_click_ids, count, mass_mailing_id, campaign_id, source_id, medium_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "link.tracker", "table_name": ""}
+{"text": "Describe the implementation of account_edi_proxy_client.user.", "response": "The account_edi_proxy_client.user model is defined in module: account_edi_proxy_client. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account_edi_proxy_client.user", "table_name": ""}
+{"text": "What methods are available in purchase.custom.checklist.template?", "response": "The purchase.custom.checklist.template model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.custom.checklist.template", "table_name": ""}
+{"text": "What does the auditlog.log.line model represent?", "response": "The auditlog.log.line model represents Auditlog - Log details (fields updated) in the ERP system. It contains 25 fields and is used to manage auditlog - log details (fields updated) data. Key fields include: field_id, log_id, old_value, new_value, old_value_text, new_value_text, field_name, field_description, name, model_id, model_name, model_model, res_id, user_id, method, http_session_id, http_request_id, log_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "auditlog.log.line", "table_name": ""}
+{"text": "How is pos.receipt.template used in the system?", "response": "The pos.receipt.template model represents POS Receipt Template in the ERP system. It contains 28 fields and is used to manage pos receipt template data. Key fields include: name, is_default, size, custom_size, is_need_header, receipt_header_text, is_need_footer, receipt_footer_text, is_receipt_disc_in_orderline, is_receipt_tax_include_orderline, is_receipt_serial_lot_info, is_receipt_savings_summary, savings_summary_text, is_receipt_product_code, preview_receipt, company_id, voucher_receipt_display, generate_voucher_id, is_voucher_receipt, is_show_discount_detail, is_receipt_member_info, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.receipt.template", "table_name": ""}
+{"text": "What data can be stored in account.fiscal.position.tax.template?", "response": "The account.fiscal.position.tax.template model has 10 fields: position_id, tax_src_id, tax_dest_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.fiscal.position.tax.template", "table_name": ""}
+{"text": "What methods are available in assembly.safety.stock.line?", "response": "The assembly.safety.stock.line model is defined in module: equip3_assembly_operations. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "assembly.safety.stock.line", "table_name": ""}
+{"text": "What does the pos.sync.session.log model represent?", "response": "The pos.sync.session.log model represents Transactions Logs of POS Users in the ERP system. It contains 17 fields and is used to manage transactions logs of pos users data. Key fields include: order_uid, create_date, send_from_session_id, send_to_session_id, user_id, user_receive_id, action, logs, state, branch_id, company_id, id, display_name, create_uid, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.sync.session.log", "table_name": ""}
+{"text": "How does sh.top.vendor.excel.extended relate to other models?", "response": "The sh.top.vendor.excel.extended model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.top.vendor.excel.extended", "table_name": ""}
+{"text": "How to create records in accounting.flow.wizard?", "response": "To use the accounting.flow.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "accounting.flow.wizard", "table_name": ""}
+{"text": "How do I use the auditlog.log model?", "response": "To use the auditlog.log model, you need to provide values for required fields: none. Readonly fields: model_name, model_model, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "auditlog.log", "table_name": ""}
+{"text": "What does the account.account model represent?", "response": "The account.account model represents Account in the ERP system. It contains 62 fields and is used to manage account data. Key fields include: move_line_ids, balance, credit, debit, parent_id, child_ids, parent_path, initial_balance, discount_account, name, currency_id, code, deprecated, used, user_type_id, internal_type, internal_group, reconcile, tax_ids, note, company_id, tag_ids, group_id, root_id, allowed_journal_ids, opening_debit, opening_credit, opening_balance, is_off_balance, branch_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.account", "table_name": ""}
+{"text": "List all fields in the budget.carry.over model.", "response": "The budget.carry.over model has 34 fields: name, complete_name, crossover_budget_id, state, parent_id, is_parent_budget, account_tag_ids, budget_carry_over_line_ids, company_id, date_from, date_to, branch_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 7, selection: 1, boolean: 6, many2many: 3, one2many: 4, date: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "budget.carry.over", "table_name": ""}
+{"text": "Tell me about the credit.note.product.lines model.", "response": "The credit.note.product.lines model represents Credit Note Product Lines in the ERP system. It contains 13 fields and is used to manage credit note product lines data. Key fields include: product_id, quantity, price, sale_line_id, credit_note_id, purchase_line_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "credit.note.product.lines", "table_name": ""}
+{"text": "How does sms.composer relate to other models?", "response": "The sms.composer model has 3 relational fields: template_id -> sms.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sms.composer", "table_name": ""}
+{"text": "How does product.price.quantity relate to other models?", "response": "The product.price.quantity model has 3 relational fields: product_tmpl_id -> product.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.price.quantity", "table_name": ""}
+{"text": "What are common use cases for base.document.layout?", "response": "To use the base.document.layout model, you need to provide values for required fields: company_id. Readonly fields: preview_logo, logo_primary_color, logo_secondary_color, preview, partner_id, phone, email, website, vat, name, country_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.document.layout", "table_name": ""}
+{"text": "What methods are available in ir.default?", "response": "The ir.default model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.default", "table_name": ""}
+{"text": "Describe the field structure of sh.purchase.product.indent.xls.", "response": "The sh.purchase.product.indent.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.purchase.product.indent.xls", "table_name": ""}
+{"text": "Describe the implementation of hr.employee.public.", "response": "The hr.employee.public model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hr.employee.public", "table_name": ""}
+{"text": "What foreign keys exist in approval.matrix.vendor?", "response": "The approval.matrix.vendor model has 5 relational fields: company_id -> res.company; branch_id -> res.branch; approval_matrix_line_ids -> approval.matrix.vendor.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.vendor", "table_name": ""}
+{"text": "What are the relationships in sh_barcode_scanner_adv.search.document?", "response": "The sh_barcode_scanner_adv.search.document model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh_barcode_scanner_adv.search.document", "table_name": ""}
+{"text": "What fields does acrux.chat.connector have?", "response": "The acrux.chat.connector model has 38 fields: name, sequence, message, company_id, team_id, verify, source, channel, endpoint, apikey, sandbox, uuid, time_to_respond, time_to_reasign, border_color, ca_app_name, ca_status, ca_status_txt, ca_qr_code, sale_report_id, connector_type, qc_app_name, qc_status, qc_status_txt, qc_qr_code, qc_channel, qc_channel_id, qc_sdk_token, qc_template_ids, qc_webhook_url, connection_status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 15, integer: 4, text: 1, many2one: 5, boolean: 4, binary: 2, selection: 3, one2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "acrux.chat.connector", "table_name": ""}
+{"text": "What is the product.template.attribute.exclusion model?", "response": "The product.template.attribute.exclusion model represents Product Template Attribute Exclusion in the ERP system. It contains 10 fields and is used to manage product template attribute exclusion data. Key fields include: product_template_attribute_value_id, product_tmpl_id, value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.template.attribute.exclusion", "table_name": ""}
+{"text": "Describe the implementation of res.company.", "response": "The res.company model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.company", "table_name": ""}
+{"text": "What are the relationships in pos.promotion.discount.quantity?", "response": "The pos.promotion.discount.quantity model has 5 relational fields: product_id -> product.product; product_ids -> product.product; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.promotion.discount.quantity", "table_name": ""}
+{"text": "How do I use the sh.product.qrcode.generator.wizard model?", "response": "To use the sh.product.qrcode.generator.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.product.qrcode.generator.wizard", "table_name": ""}
+{"text": "What are the technical details of kitchen.production.record?", "response": "The kitchen.production.record model is defined in module: equip3_kitchen_operations. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kitchen.production.record", "table_name": ""}
+{"text": "What fields does project.task.recurrence have?", "response": "The project.task.recurrence model has 28 fields: task_ids, next_recurrence_date, recurrence_left, repeat_interval, repeat_unit, repeat_type, repeat_until, repeat_number, repeat_on_month, repeat_on_year, mon, tue, wed, thu, fri, sat, sun, repeat_day, repeat_week, repeat_weekday, repeat_month, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, date: 2, integer: 4, selection: 8, boolean: 7, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.task.recurrence", "table_name": ""}
+{"text": "How do I use the report.dynamic_accounts_report.partner_ledger model?", "response": "To use the report.dynamic_accounts_report.partner_ledger model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.partner_ledger", "table_name": ""}
+{"text": "Can you explain the purpose of pos.session?", "response": "The pos.session model represents Point of Sale Session in the ERP system. It contains 101 fields and is used to manage point of sale session data. Key fields include: company_id, config_id, name, user_id, currency_id, start_at, stop_at, sequence_number, cash_control, cash_journal_id, cash_register_id, cash_register_balance_start, cash_register_balance_end, cash_register_difference, cash_real_difference, cash_real_transaction, cash_real_expected, order_ids, order_count, statement_ids, failed_pickings, picking_count, picking_ids, rescue, move_id, payment_method_ids, total_payments_amount, is_in_company_currency, update_stock_at_closing, move_id_old, orderline_checked, crm_team_id, required_reinstall_cache, backup_session, pos_branch_id, employee_id, lock_state, order_log_ids, opened_at, opened_uid, last_login_time, login_number, state, cash_opening_balance, cash_closing_balance, is_closing_wizard, pos_config_cashbox_lines_ids, pos_config_cashbox_clsosing_line_ids, cash_register_balance_end_real, cashier_id, total_invoice_count, total_faktur_count, log_cashier_ids, is_multi_session, order_with_receivable_invoice_ids, pos_config_uuid, pos_session_cashbox_wizard_ids, cash_management_ids, cash_history_ids, gain_loss_move_id, is_pos_config_save_order_history_local, scheduler_invoice_finish_date, void_ids, bank_register_total_entry_encoding, cash_register_total_entry_encoding, bank_closing_balance, pos_session_bank_cashbox_wizard_ids, to_recompute, is_invoice_recreate, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.session", "table_name": ""}
+{"text": "How does account.pettycash relate to other models?", "response": "The account.pettycash model has 24 relational fields: cash_journal -> account.journal; custodian -> res.users; main_cash_account_id -> account.account; journal -> account.journal; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; move_id -> account.move; voucher_id -> account.pettycash.voucher.wizard; paid_voucher_ids -> account.pettycash.voucher.wizard; custodian_partner -> res.partner; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.pettycash", "table_name": ""}
+{"text": "What fields does stock.scrap have?", "response": "The stock.scrap model has 53 fields: name, company_id, origin, product_id, product_uom_category_id, tracking, lot_id, package_id, owner_id, move_id, picking_id, scrap_location_id, state, production_id, workorder_id, product_uom_id, scrap_id, filter_location_ids, filter_product_ids, location_id, sale_price, product_usage_state, analytic_tag_ids, filter_lot_ids, filter_package_ids, filter_owner_ids, scrap_qty, product_state, usage_type, warehouse_id, date_done, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 19, selection: 4, many2many: 8, float: 2, datetime: 4, boolean: 5, one2many: 3, integer: 5.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.scrap", "table_name": ""}
+{"text": "Show me the relational structure of project.delete.wizard.", "response": "The project.delete.wizard model has 3 relational fields: project_ids -> project.project; create_uid -> res.users; write_uid -> res.users. Many2many fields: project_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "project.delete.wizard", "table_name": ""}
+{"text": "Describe the crm.lost.reason model in Odoo.", "response": "The crm.lost.reason model represents Opp. Lost Reason in the ERP system. It contains 10 fields and is used to manage opp. lost reason data. Key fields include: name, active, leads_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.lost.reason", "table_name": ""}
+{"text": "What methods are available in purchase.order.report?", "response": "The purchase.order.report model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.order.report", "table_name": ""}
+{"text": "Tell me about the account.print.journal model.", "response": "The account.print.journal model represents Account Print Journal in the ERP system. It contains 15 fields and is used to manage account print journal data. Key fields include: sort_selection, journal_ids, amount_currency, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.print.journal", "table_name": ""}
+{"text": "What foreign keys exist in crm.phonecall.report?", "response": "The crm.phonecall.report model has 4 relational fields: user_id -> res.users; team_id -> crm.team; partner_id -> res.partner; company_id -> res.company. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.phonecall.report", "table_name": ""}
+{"text": "How do I use the coupon.rule model?", "response": "To use the coupon.rule model, you need to provide values for required fields: none. Readonly fields: applied_partner_ids, applied_product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "coupon.rule", "table_name": ""}
+{"text": "What are the technical details of report.sh_sale_reports.sh_top_selling_product_doc?", "response": "The report.sh_sale_reports.sh_top_selling_product_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_top_selling_product_doc", "table_name": ""}
+{"text": "Describe the utm.source model in Odoo.", "response": "The utm.source model represents UTM Source in the ERP system. It contains 8 fields and is used to manage utm source data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "utm.source", "table_name": ""}
+{"text": "Show me the relational structure of account.common.journal.report.", "response": "The account.common.journal.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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.common.journal.report", "table_name": ""}
+{"text": "Describe the implementation of account.general.ledger.", "response": "The account.general.ledger model is defined in module: dynamic_accounts_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.general.ledger", "table_name": ""}
+{"text": "What is the ir.exports model?", "response": "The ir.exports model represents Exports in the ERP system. It contains 10 fields and is used to manage exports data. Key fields include: name, resource, export_fields, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.exports", "table_name": ""}
+{"text": "Tell me about the report.sh_purchase_reports.sh_po_product_profit_doc model.", "response": "The report.sh_purchase_reports.sh_po_product_profit_doc model represents Purchase Product Profit report abstract model in the ERP system. It contains 3 fields and is used to manage purchase product profit report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_po_product_profit_doc", "table_name": ""}
+{"text": "Which fields in sh.mpo.merge.purchase.order.wizard are computed?", "response": "The sh.mpo.merge.purchase.order.wizard model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.mpo.merge.purchase.order.wizard", "table_name": ""}
+{"text": "How do I use the approval.request.reject model?", "response": "To use the approval.request.reject model, you need to provide values for required fields: reason. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.request.reject", "table_name": ""}
+{"text": "What methods are available in pos.promotion.gift.condition?", "response": "The pos.promotion.gift.condition model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.promotion.gift.condition", "table_name": ""}
+{"text": "What are the relationships in pos.order.line?", "response": "The pos.order.line model has 30 relational fields: company_id -> res.company; product_id -> product.product; order_id -> pos.order; tax_ids -> account.tax; tax_ids_after_fiscal_position -> account.tax; pack_lot_ids -> pos.pack.operation.lot; currency_id -> res.currency; promotion_id -> pos.promotion; coupon_program_id -> coupon.program; coupon_id -> coupon.coupon; coupon_ids -> coupon.coupon; zone_id -> pos.zone; promotion_stack_ids -> pos.order.line.promotion; pos_coupon_id -> pos.coupon; picking_type_id -> stock.picking.type; partner_id -> res.partner; user_id -> res.users; tag_ids -> pos.tag; config_id -> pos.config; pos_branch_id -> res.branch; manager_user_id -> res.users; analytic_account_id -> account.analytic.account; returned_order_line_id -> pos.order.line; uom_id -> uom.uom; product_uom_id -> uom.uom; original_line_id -> pos.order.line; last_supplier_id -> res.partner; reward_id -> pos.loyalty.reward; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_ids, tax_ids_after_fiscal_position, coupon_ids, tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.order.line", "table_name": ""}
+{"text": "How to query ir.actions.report data?", "response": "To use the ir.actions.report model, you need to provide values for required fields: name, type, binding_type, model, report_type, report_name. Readonly fields: model_id, xml_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.actions.report", "table_name": ""}
+{"text": "Describe the implementation of pos.make.payment.", "response": "The pos.make.payment model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.make.payment", "table_name": ""}
+{"text": "Show me the relational structure of portal.share.", "response": "The portal.share model has 3 relational fields: partner_ids -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "portal.share", "table_name": ""}
+{"text": "Describe the field structure of sh.sale.invoice.summary.wizard.", "response": "The sh.sale.invoice.summary.wizard model has 15 fields: sh_start_date, sh_end_date, sh_partner_ids, sh_status, company_ids, company_id, customer_order_dic, currency_precision, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2many: 2, selection: 1, many2one: 3, one2many: 1, integer: 2, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.sale.invoice.summary.wizard", "table_name": ""}
+{"text": "How is kitchen.safety.stock implemented technically?", "response": "The kitchen.safety.stock model is defined in module: equip3_kitchen_operations. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kitchen.safety.stock", "table_name": ""}
+{"text": "Show me the relational structure of account.report.general.ledger.", "response": "The account.report.general.ledger 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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.report.general.ledger", "table_name": ""}
+{"text": "How to query report_excel_wizard data?", "response": "To use the report_excel_wizard model, you need to provide values for required fields: report_conf. Readonly fields: report_conf, report_name, report_description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report_excel_wizard", "table_name": ""}
+{"text": "What business logic is in report.product.report_pricelist?", "response": "To use the report.product.report_pricelist model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.product.report_pricelist", "table_name": ""}
+{"text": "Describe the field structure of receipt.payment.line.debit.", "response": "The receipt.payment.line.debit model has 20 fields: line_id, currency_id, invoice_id, account_id, invoice_date, invoice_date_due, original_amount, base_amount, original_unreconcile, base_unreconcile, is_full_reconcile, amount, payment_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, date: 2, monetary: 5, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "receipt.payment.line.debit", "table_name": ""}
+{"text": "Tell me about the dev.purchase.team model.", "response": "The dev.purchase.team model represents Purchase Team in the ERP system. It contains 13 fields and is used to manage purchase team data. Key fields include: name, user_id, member_ids, active, company_id, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "dev.purchase.team", "table_name": ""}
+{"text": "How to create records in asset.depreciation.confirmation.wizard?", "response": "To use the asset.depreciation.confirmation.wizard model, you need to provide values for required fields: date. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "asset.depreciation.confirmation.wizard", "table_name": ""}
+{"text": "What methods are available in crm.sales.tracking.history?", "response": "The crm.sales.tracking.history model is defined in module: equip3_crm_tracking. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.sales.tracking.history", "table_name": ""}
+{"text": "How does crm.meeting.overview relate to other models?", "response": "The crm.meeting.overview model has 18 relational fields: calendar_id -> calendar.event; opportunity_id -> crm.lead; activity_type_id -> mail.activity.type; partner_ids -> res.partner; stage_id -> crm.stage; order_ids -> sale.order; final_quotation -> quotation.amount; activity_ids -> mail.activity; meeting_salesperson_ids -> res.users; activity_user_id -> res.users; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, meeting_salesperson_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.meeting.overview", "table_name": ""}
+{"text": "Can you explain the purpose of product.quantity.available.report?", "response": "The product.quantity.available.report model represents Product Quantity Available Report Each Location in the ERP system. It contains 10 fields and is used to manage product quantity available report each location data. Key fields include: product_barcode, product_default_code, location_id, product_id, qty_available, in_date, sale_qty, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.quantity.available.report", "table_name": ""}
+{"text": "Describe the many2many relations for create.purchase.request.direct.", "response": "The create.purchase.request.direct model has 6 relational fields: supplier_id -> res.partner; item_ids -> create.purchase.request.direct.lines; journal_id -> account.journal; purchase_order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "create.purchase.request.direct", "table_name": ""}
+{"text": "What models are connected to account.partner.ageing?", "response": "The account.partner.ageing model has 7 relational fields: partner_ids -> res.partner; partner_category_ids -> res.partner.category; journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, partner_category_ids, journal_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.partner.ageing", "table_name": ""}
+{"text": "What fields does account.petty.cash.report have?", "response": "The account.petty.cash.report model has 16 fields: name, custodian_id, main_cash_account_id, journal_id, amount, balance, virtual_balance, company_id, branch_id, effective_date, create_uid, create_date, expense_amount, id, display_name, __last_update. Field types distribution: char: 2, many2one: 6, float: 4, date: 1, datetime: 2, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.petty.cash.report", "table_name": ""}
+{"text": "How does sale.order.partner.credit relate to other models?", "response": "The sale.order.partner.credit model has 4 relational fields: name -> sale.order; order_partner -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.partner.credit", "table_name": ""}
+{"text": "What methods are available in budget.carry.over.lines?", "response": "The budget.carry.over.lines model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "budget.carry.over.lines", "table_name": ""}
+{"text": "Describe the implementation of mail.thread.", "response": "The mail.thread model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.thread", "table_name": ""}
+{"text": "What operations can I perform on setu.rfm.score?", "response": "To use the setu.rfm.score model, you need to provide values for required fields: none. Readonly fields: total_customers, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.rfm.score", "table_name": ""}
+{"text": "Describe the field structure of pos.login.history.", "response": "The pos.login.history model has 13 fields: user_id, pos_config_id, pos_branch_id, checkin_datetime, checkout_datetime, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, datetime: 5, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.login.history", "table_name": ""}
+{"text": "Describe the many2many relations for ir.qweb.field.float_time.", "response": "The ir.qweb.field.float_time model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb.field.float_time", "table_name": ""}
+{"text": "How does bi.product.pack relate to other models?", "response": "The bi.product.pack model has 5 relational fields: product_id -> product.product; bi_product_template -> product.template; uom_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "bi.product.pack", "table_name": ""}
+{"text": "What models are connected to ir.qweb?", "response": "The ir.qweb model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb", "table_name": ""}
+{"text": "What does the pos.order.line.promotion model represent?", "response": "The pos.order.line.promotion model represents POS Order Line Promotion for Promotion Stack in the ERP system. It contains 15 fields and is used to manage pos order line promotion for promotion stack data. Key fields include: sequence, pos_order_line_id, promotion_id, promotion_disc, price, amount_percentage, amount, discount_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.order.line.promotion", "table_name": ""}
+{"text": "Describe the pos.gift.card.recharge model in Odoo.", "response": "The pos.gift.card.recharge model represents Used to Store Gift Card Recharge History. in the ERP system. It contains 12 fields and is used to manage used to store gift card recharge history. data. Key fields include: card_id, customer_id, recharge_date, user_id, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.gift.card.recharge", "table_name": ""}
+{"text": "Show me the relational structure of split.pr.wizard.", "response": "The split.pr.wizard model has 4 relational fields: pr_line_id -> purchase.request.line; line_ids -> split.pr.line.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "split.pr.wizard", "table_name": ""}
+{"text": "What methods are available in bo.request.matrix.reject?", "response": "The bo.request.matrix.reject model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "bo.request.matrix.reject", "table_name": ""}
+{"text": "How to query ir.sequence data?", "response": "To use the ir.sequence model, you need to provide values for required fields: name, implementation, number_next, number_increment, padding. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.sequence", "table_name": ""}
+{"text": "Can you explain the purpose of purchase.request.allocation?", "response": "The purchase.request.allocation model represents Purchase Request Allocation in the ERP system. It contains 17 fields and is used to manage purchase request allocation data. Key fields include: purchase_request_line_id, company_id, stock_move_id, purchase_line_id, product_id, product_uom_id, requested_product_uom_qty, allocated_product_qty, open_product_qty, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.request.allocation", "table_name": ""}
+{"text": "What fields does coupon.rule have?", "response": "The coupon.rule model has 16 fields: rule_date_from, rule_date_to, rule_partners_domain, rule_products_domain, rule_min_quantity, rule_minimum_amount, rule_minimum_amount_tax_inclusion, applied_partner_ids, applied_product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, char: 3, integer: 2, float: 1, selection: 1, many2many: 2, many2one: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "coupon.rule", "table_name": ""}
+{"text": "What is the ks_dashboard_ninja.import model?", "response": "The ks_dashboard_ninja.import model represents Import Dashboard in the ERP system. It contains 8 fields and is used to manage import dashboard data. Key fields include: ks_import_dashboard, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.import", "table_name": ""}
+{"text": "Can you explain the purpose of ks_to.do.description?", "response": "The ks_to.do.description model represents to do description in the ERP system. It contains 10 fields and is used to manage to do description data. Key fields include: ks_to_do_header_id, ks_description, ks_active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks_to.do.description", "table_name": ""}
+{"text": "What modules define purchase.agreement.line?", "response": "The purchase.agreement.line model is defined in module: sh_po_tender_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.agreement.line", "table_name": ""}
+{"text": "Describe the implementation of sh.edit.title.", "response": "The sh.edit.title model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.edit.title", "table_name": ""}
+{"text": "List all fields in the snailmail.letter.missing.required.fields model.", "response": "The snailmail.letter.missing.required.fields model has 15 fields: partner_id, letter_id, street, street2, zip, city, state_id, country_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, char: 5, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "snailmail.letter.missing.required.fields", "table_name": ""}
+{"text": "How to create records in journal.entries.report?", "response": "To use the journal.entries.report model, you need to provide values for required fields: none. Readonly fields: num, label, account_id, partner_id, analytic_account_id, amount_currency, currency_id, debit, credit, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "journal.entries.report", "table_name": ""}
+{"text": "List all fields in the auditlog.rule model.", "response": "The auditlog.rule model has 20 fields: name, model_id, model_name, model_model, user_ids, log_read, log_write, log_unlink, log_create, log_type, state, action_id, capture_record, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 4, many2many: 1, boolean: 5, selection: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "auditlog.rule", "table_name": ""}
+{"text": "Describe the many2many relations for create.purchase.request.direct.lines.", "response": "The create.purchase.request.direct.lines model has 8 relational fields: wiz_id -> create.purchase.request.direct; line_id -> purchase.request.line; request_id -> purchase.request; product_id -> product.product; product_uom_id -> uom.uom; destination_location_id -> stock.location; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "create.purchase.request.direct.lines", "table_name": ""}
+{"text": "What are the technical details of sh.purchase.bill.summary.xls?", "response": "The sh.purchase.bill.summary.xls model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.bill.summary.xls", "table_name": ""}
+{"text": "What data can be stored in account.setup.bank.manual.config?", "response": "The account.setup.bank.manual.config model has 30 fields: res_partner_bank_id, new_journal_name, linked_journal_id, bank_bic, num_journals_without_account, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, active, acc_type, acc_number, sanitized_acc_number, acc_holder_name, partner_id, bank_id, bank_name, sequence, currency_id, company_id, journal_id, aba_routing, acc_holder_email, acc_holder_type, acc_holder_resident, acc_holder_address. Field types distribution: many2one: 9, char: 10, integer: 3, datetime: 3, boolean: 1, selection: 3, one2many: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.setup.bank.manual.config", "table_name": ""}
+{"text": "What operations can I perform on mrp.bom?", "response": "To use the mrp.bom model, you need to provide values for required fields: ready_to_produce, consumption, type, product_qty, product_uom_id, product_tmpl_id. Readonly fields: product_uom_category_id, sh_bom_bm_is_cont_scan, company_id, forecast_cost, bom_tools, next_new_sequence, operation_two_ids, is_branch_required, use_operations, product_name_display, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mrp.bom", "table_name": ""}
+{"text": "What is the pos.generate.efaktur.digunggung model?", "response": "The pos.generate.efaktur.digunggung model represents Pos Generate Efaktur Digunggung in the ERP system. It contains 14 fields and is used to manage pos generate efaktur digunggung data. Key fields include: gen_efaktur_id, partner_id, account_move_id, account_move_data, no_of_invoice, amount_total, l10n_id_tax_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.generate.efaktur.digunggung", "table_name": ""}
+{"text": "What models are connected to sh.custom.tab.purchase?", "response": "The sh.custom.tab.purchase model has 4 relational fields: groups -> res.groups; view_id -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: groups.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.custom.tab.purchase", "table_name": ""}
+{"text": "How is whatsapp.scan.qr implemented technically?", "response": "The whatsapp.scan.qr model is defined in module: pragmatic_odoo_delivery_boy. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "whatsapp.scan.qr", "table_name": ""}
+{"text": "Describe the implementation of purchase.tender.xls.report.", "response": "The purchase.tender.xls.report model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.tender.xls.report", "table_name": ""}
+{"text": "What is the update.historical.data model?", "response": "The update.historical.data model represents Update Historical Data in the ERP system. It contains 57 fields and is used to manage update historical data data. Key fields include: name, action, error_message, start_date, end_date, batch, limit, run_hour_from, run_hour_to, picking_return_id, list_data_double, list_data_double_count, picking_return_count, product_ids, list_data_issue, list_data_issue_quant, quant_ids_data, list_data_issue_count, warehouse_ids, list_data_quant_count, list_data_je_created_ids, list_data_je_count, list_data_product_count, list_data_issue_svl_double_create, list_data_issue_svl_double_create_count, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "update.historical.data", "table_name": ""}
+{"text": "Show me the fields of itr.matrix.reject.", "response": "The itr.matrix.reject model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "itr.matrix.reject", "table_name": ""}
+{"text": "Show me the fields of account.partial.reconcile.", "response": "The account.partial.reconcile model has 18 fields: debit_move_id, credit_move_id, full_reconcile_id, company_currency_id, debit_currency_id, credit_currency_id, amount, debit_amount_currency, credit_amount_currency, company_id, max_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, monetary: 3, date: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.partial.reconcile", "table_name": ""}
+{"text": "Tell me about the theme.ir.attachment model.", "response": "The theme.ir.attachment model represents Theme Attachments in the ERP system. It contains 11 fields and is used to manage theme attachments data. Key fields include: name, key, url, copy_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "theme.ir.attachment", "table_name": ""}
+{"text": "Can you explain the purpose of faktur.message?", "response": "The faktur.message model represents faktur.message in the ERP system. It contains 8 fields and is used to manage faktur.message data. Key fields include: sum_faktur, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "faktur.message", "table_name": ""}
+{"text": "Describe the field structure of ir.qweb.field.date.", "response": "The ir.qweb.field.date model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.date", "table_name": ""}
+{"text": "Can you explain the purpose of account.cash.flow?", "response": "The account.cash.flow model represents Cash Flow Report in the ERP system. It contains 16 fields and is used to manage cash flow report data. Key fields include: date_from, date_to, today, levels, account_ids, journal_ids, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.cash.flow", "table_name": ""}
+{"text": "What models are connected to account.resequence.wizard?", "response": "The account.resequence.wizard model has 3 relational fields: move_ids -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: move_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.resequence.wizard", "table_name": ""}
+{"text": "What foreign keys exist in ir.mail_server?", "response": "The ir.mail_server model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.mail_server", "table_name": ""}
+{"text": "What models are connected to change.production.qty?", "response": "The change.production.qty model has 3 relational fields: mo_id -> mrp.production; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "change.production.qty", "table_name": ""}
+{"text": "Show me the fields of sh.tsp.top.selling.product.wizard.", "response": "The sh.tsp.top.selling.product.wizard model has 21 fields: type, date_to, date_compare_from, date_compare_to, no_of_top_item, product_uom_qty, team_id, company_ids, company_id, top_product_ids, top_product_compare_ids, lost_product_ids, new_product_ids, date_from, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, datetime: 7, integer: 2, float: 1, many2one: 4, many2many: 1, one2many: 4, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.tsp.top.selling.product.wizard", "table_name": ""}
+{"text": "How does material.request.show.stock relate to other models?", "response": "The material.request.show.stock model has 3 relational fields: stock_quant_line_ids -> material.request.line.show.stock; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "material.request.show.stock", "table_name": ""}
+{"text": "Can you explain the purpose of sh.commision.detail?", "response": "The sh.commision.detail model represents sh.commision.detail in the ERP system. It contains 11 fields and is used to manage sh.commision.detail data. Key fields include: sales_amount, collection_amount, commision, target_commision_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.commision.detail", "table_name": ""}
+{"text": "Can you explain the purpose of pos.gift.card.recharge?", "response": "The pos.gift.card.recharge model represents Used to Store Gift Card Recharge History. in the ERP system. It contains 12 fields and is used to manage used to store gift card recharge history. data. Key fields include: card_id, customer_id, recharge_date, user_id, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.gift.card.recharge", "table_name": ""}
+{"text": "What are the relationships in receipt.payment.line.debit?", "response": "The receipt.payment.line.debit model has 7 relational fields: line_id -> receipt.payment; currency_id -> res.currency; invoice_id -> account.move; account_id -> account.account; payment_id -> account.payment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "receipt.payment.line.debit", "table_name": ""}
+{"text": "How does account.voucher.line relate to other models?", "response": "The account.voucher.line model has 11 relational fields: voucher_id -> account.voucher; product_id -> product.product; uom_id -> uom.uom; account_id -> account.account; account_analytic_id -> account.analytic.account; analytic_tag_ids -> account.analytic.tag; company_id -> res.company; tax_ids -> account.tax; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, tax_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.voucher.line", "table_name": ""}
+{"text": "What does the generate.pos.voucher.use.history model represent?", "response": "The generate.pos.voucher.use.history model represents Histories Generate use voucher of customer in the ERP system. It contains 13 fields and is used to manage histories generate use voucher of customer data. Key fields include: pos_order_id, payment_id, voucher_id, value, used_date, cashier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "generate.pos.voucher.use.history", "table_name": ""}
+{"text": "What data can be stored in mr_line.internal_transfer_line?", "response": "The mr_line.internal_transfer_line model has 22 fields: mr_id, mr_line_id, no, product_id, description, uom_id, source_location, source_warehouse_id, current_qty, virtual_available, qty_transfer, mr_ir_wizard, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 10, integer: 2, char: 2, float: 3, many2many: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mr_line.internal_transfer_line", "table_name": ""}
+{"text": "Describe the ks_dashboard_ninja.item_action model in Odoo.", "response": "The ks_dashboard_ninja.item_action model represents Dashboard Ninja Items Action Lines in the ERP system. It contains 17 fields and is used to manage dashboard ninja items action lines data. Key fields include: ks_item_action_field, ks_item_action_field_type, ks_item_action_date_groupby, ks_chart_type, ks_dashboard_item_id, ks_model_id, sequence, ks_record_limit, ks_sort_by_field, ks_sort_by_order, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.item_action", "table_name": ""}
+{"text": "What fields does vendor.evaluation.rating have?", "response": "The vendor.evaluation.rating model has 9 fields: partner_id, fulfillment_avg, on_time_rate_avg, final_point_avg, vendor_evaluation_count, branch_id, id, display_name, __last_update. Field types distribution: many2one: 2, float: 3, integer: 2, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "vendor.evaluation.rating", "table_name": ""}
+{"text": "What are the available fields for product.brand?", "response": "The product.brand model has 42 fields: brand_name, short_name, product_count, active, 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. Field types distribution: char: 8, integer: 6, boolean: 6, many2one: 8, one2many: 4, selection: 2, date: 2, many2many: 2, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.brand", "table_name": ""}
+{"text": "What operations can I perform on quality.check.report?", "response": "To use the quality.check.report model, you need to provide values for required fields: date_from, date_to. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "quality.check.report", "table_name": ""}
+{"text": "Can you explain the purpose of export.product.csv?", "response": "The export.product.csv model represents export.product.csv in the ERP system. It contains 40 fields and is used to manage export.product.csv data. Key fields include: name, product_id_attachment_id, product_id_csv_created, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "export.product.csv", "table_name": ""}
+{"text": "What are the available fields for report.product.report_pricelist?", "response": "The report.product.report_pricelist model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.product.report_pricelist", "table_name": ""}
+{"text": "How is sh.wqm.quick.menu implemented technically?", "response": "The sh.wqm.quick.menu model is defined in module: sh_backmate_theme_adv. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.wqm.quick.menu", "table_name": ""}
+{"text": "How do I use the website.published.multi.mixin model?", "response": "To use the website.published.multi.mixin model, you need to provide values for required fields: none. Readonly fields: website_published, website_id, is_published, can_publish, website_url, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "website.published.multi.mixin", "table_name": ""}
+{"text": "What foreign keys exist in report.dynamic_barcode_labels.report_barcode_labels?", "response": "The report.dynamic_barcode_labels.report_barcode_labels model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.dynamic_barcode_labels.report_barcode_labels", "table_name": ""}
+{"text": "What data can be stored in card.payment?", "response": "The card.payment model has 41 fields: card_img, card_name, card_active, card_group, BIN, company_id, have_char, card_type, card_status, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 7, boolean: 7, many2one: 7, selection: 3, one2many: 4, date: 2, many2many: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "card.payment", "table_name": ""}
+{"text": "How to query stock.return.picking.inter.company data?", "response": "To use the stock.return.picking.inter.company model, you need to provide values for required fields: none. Readonly fields: uom_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.return.picking.inter.company", "table_name": ""}
+{"text": "Show me the fields of report.dynamic_accounts_report.general_ledger.", "response": "The report.dynamic_accounts_report.general_ledger model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.dynamic_accounts_report.general_ledger", "table_name": ""}
+{"text": "What are common use cases for auditlog.log.line?", "response": "To use the auditlog.log.line model, you need to provide values for required fields: none. Readonly fields: field_name, field_description, name, model_id, model_name, model_model, res_id, user_id, method, http_session_id, http_request_id, log_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "auditlog.log.line", "table_name": ""}
+{"text": "What are common use cases for term.condition?", "response": "To use the term.condition 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "term.condition", "table_name": ""}
+{"text": "What are the relationships in mrp.quality.alert.report?", "response": "The mrp.quality.alert.report model has 5 relational fields: product_ids -> product.product; user_ids -> res.users; stage_id -> sh.qc.alert.stage; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, user_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.quality.alert.report", "table_name": ""}
+{"text": "How to create records in acrux.chat.default.answer?", "response": "To use the acrux.chat.default.answer model, you need to provide values for required fields: name, default_answer_type, ttype. Readonly fields: res_model, res_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "acrux.chat.default.answer", "table_name": ""}
+{"text": "What is the customer.voucher model?", "response": "The customer.voucher model represents Customer Voucher in the ERP system. It contains 22 fields and is used to manage customer voucher data. Key fields include: name, customer_id, customer_target_id, state, start_date, end_date, reward_type, discount_line_product_id, sale_order_line_ids, cashback_line_ids, creation_date, expired_date, expiration_period, customer_voucher_type, is_apply_voucher, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "customer.voucher", "table_name": ""}
+{"text": "Describe the invoice.template.header model in Odoo.", "response": "The invoice.template.header model represents Invoice Template Header in the ERP system. It contains 10 fields and is used to manage invoice template header data. Key fields include: template_id, field_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "invoice.template.header", "table_name": ""}
+{"text": "How to query account.cash.rounding data?", "response": "To use the account.cash.rounding model, you need to provide values for required fields: name, rounding, strategy, rounding_method. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.cash.rounding", "table_name": ""}
+{"text": "What are the available fields for rfm.yearly.analysis.by.segment?", "response": "The rfm.yearly.analysis.by.segment model has 7 fields: calculation_year, segment_id, total_customers, ratio, id, display_name, __last_update. Field types distribution: text: 1, many2one: 1, integer: 2, float: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "rfm.yearly.analysis.by.segment", "table_name": ""}
+{"text": "What does the res.lang model represent?", "response": "The res.lang model represents Languages in the ERP system. It contains 21 fields and is used to manage languages data. Key fields include: name, code, iso_code, url_code, active, direction, date_format, time_format, week_start, grouping, decimal_point, thousands_sep, flag_image, flag_image_url, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.lang", "table_name": ""}
+{"text": "What methods are available in approval.matrix.sale.order?", "response": "The approval.matrix.sale.order model is defined in module: equip3_sale_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "approval.matrix.sale.order", "table_name": ""}
+{"text": "What are the relationships in account.bank.statement.import?", "response": "The account.bank.statement.import model has 3 relational fields: attachment_ids -> ir.attachment; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.bank.statement.import", "table_name": ""}
+{"text": "How does report.account.report_invoice relate to other models?", "response": "The report.account.report_invoice model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.account.report_invoice", "table_name": ""}
+{"text": "What does the purchase.quotation.report model represent?", "response": "The purchase.quotation.report model represents Puechase Quotation Report in the ERP system. It contains 8 fields and is used to manage puechase quotation report data. Key fields include: purchase_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.quotation.report", "table_name": ""}
+{"text": "What operations can I perform on base.partner.merge.line?", "response": "To use the base.partner.merge.line model, you need to provide values for required fields: aggr_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.partner.merge.line", "table_name": ""}
+{"text": "What are the technical details of pos.cashier.change.wizard?", "response": "The pos.cashier.change.wizard model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.cashier.change.wizard", "table_name": ""}
+{"text": "What models are connected to report.reordering?", "response": "The report.reordering model has 4 relational fields: warehouse_id -> stock.warehouse; location_ids -> stock.location; create_uid -> res.users; write_uid -> res.users. Many2many fields: location_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.reordering", "table_name": ""}
+{"text": "How do I use the untaken.stock.line model?", "response": "To use the untaken.stock.line model, you need to provide values for required fields: none. Readonly fields: quantity, product_unit_measure, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "untaken.stock.line", "table_name": ""}
+{"text": "Which fields in mail.notification are computed?", "response": "The mail.notification model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.notification", "table_name": ""}
+{"text": "Describe the account.analytic.account model in Odoo.", "response": "The account.analytic.account model represents Analytic Account in the ERP system. It contains 57 fields and is used to manage analytic account data. Key fields include: code, active, line_ids, partner_id, balance, debit, credit, currency_id, project_ids, project_count, name, crossovered_budget_line, subscription_product_line_ids, not_subscription_product_line_ids, terms_and_conditions, start_date, end_date, recurring_interval, recurring_next_date, journal_id, invoice_count, number_of_days, contract_lock, recurring_rule_type, stage, sub_amount_untaxed, sub_amount_tax, sub_amount_total, sale_amount_untaxed, sale_amount_tax, sale_amount_total, order_invoice_currency_id, group_id, company_id, branch_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.analytic.account", "table_name": ""}
+{"text": "Which fields in sale.data.margin are computed?", "response": "The sale.data.margin model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.data.margin", "table_name": ""}
+{"text": "What are the relationships in account.reconcile.model.partner.mapping?", "response": "The account.reconcile.model.partner.mapping model has 4 relational fields: model_id -> account.reconcile.model; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.reconcile.model.partner.mapping", "table_name": ""}
+{"text": "Describe the many2many relations for account.asset.asset.", "response": "The account.asset.asset model has 27 relational fields: currency_id -> res.currency; category_id -> account.asset.category; partner_id -> res.partner; depreciation_line_ids -> account.asset.depreciation.line; invoice_id -> account.move; account_analytic_id -> account.analytic.account; analytic_tag_ids -> account.analytic.tag; user_id -> res.users; fiscal_category_id -> account.asset.category.fiscal; depreciation_line_ids_fiscal -> account.asset.fiscal.line; asset_history_lines_ids -> asset.asset.revalue; account_cip_id -> asset.cip; approval_matrix_id -> assets.approval.matrix; approved_matrix_ids -> assets.approval.matrix.line; approval_matrix_line_id -> assets.approval.matrix.line; request_partner_id -> res.partner; company_id -> res.company; branch_id -> res.branch; product_id -> product.product; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.asset.asset", "table_name": ""}
+{"text": "What fields does batch.shipping.line have?", "response": "The batch.shipping.line model has 12 fields: serial_number, picking_id, warehouse_id, batch_shipping_id, used_picking_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 5, many2many: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "batch.shipping.line", "table_name": ""}
+{"text": "Tell me about the report.point_of_sale.report_invoice model.", "response": "The report.point_of_sale.report_invoice model represents Point of Sale Invoice Report in the ERP system. It contains 3 fields and is used to manage point of sale invoice report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.point_of_sale.report_invoice", "table_name": ""}
+{"text": "Show me the fields of pos.gift.card.recharge.", "response": "The pos.gift.card.recharge model has 12 fields: card_id, customer_id, recharge_date, user_id, amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.gift.card.recharge", "table_name": ""}
+{"text": "How to create records in restaurant.floor?", "response": "To use the restaurant.floor 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "restaurant.floor", "table_name": ""}
+{"text": "What are the available fields for account.day.book?", "response": "The account.day.book model has 13 fields: company_id, journal_ids, account_ids, date_from, date_to, target_move, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 2, date: 2, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.day.book", "table_name": ""}
+{"text": "What operations can I perform on account.invoice.exchange?", "response": "To use the account.invoice.exchange model, you need to provide values for required fields: exchange_type, stage, move_type. Readonly fields: filter_move_ids, stage, invoice_payments_widget, move_type, line_ids, grand_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.invoice.exchange", "table_name": ""}
+{"text": "Describe the implementation of res.config.installer.", "response": "The res.config.installer model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.config.installer", "table_name": ""}
+{"text": "Describe the many2many relations for mail.resend.partner.", "response": "The mail.resend.partner model has 4 relational fields: partner_id -> res.partner; resend_wizard_id -> mail.resend.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.resend.partner", "table_name": ""}
+{"text": "List all fields in the utm.stage model.", "response": "The utm.stage model has 9 fields: name, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "utm.stage", "table_name": ""}
+{"text": "What data can be stored in sale.commission.excel.report?", "response": "The sale.commission.excel.report model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.commission.excel.report", "table_name": ""}
+{"text": "What data can be stored in crm.lost.reason?", "response": "The crm.lost.reason model has 10 fields: name, active, leads_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 1, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.lost.reason", "table_name": ""}
+{"text": "Which fields in pos.coupon.generate.wizard are computed?", "response": "The pos.coupon.generate.wizard model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.coupon.generate.wizard", "table_name": ""}
+{"text": "How to create records in stock.traceability.report?", "response": "To use the stock.traceability.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.traceability.report", "table_name": ""}
+{"text": "Can you explain the purpose of warranty.tag?", "response": "The warranty.tag model represents Warranty Tag in the ERP system. It contains 9 fields and is used to manage warranty tag data. Key fields include: tag_name, tag_desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "warranty.tag", "table_name": ""}
+{"text": "What models are connected to payment.link.wizard?", "response": "The payment.link.wizard model has 5 relational fields: currency_id -> res.currency; partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "payment.link.wizard", "table_name": ""}
+{"text": "Describe the field structure of report.sh_purchase_reports.sh_tv_top_vendors_doc.", "response": "The report.sh_purchase_reports.sh_tv_top_vendors_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_tv_top_vendors_doc", "table_name": ""}
+{"text": "Tell me about the purchase.product.template.line model.", "response": "The purchase.product.template.line model represents Purchase Product Template Line in the ERP system. It contains 14 fields and is used to manage purchase product template line data. Key fields include: name, description, ordered_qty, unit_price, product_uom, purchase_template_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.product.template.line", "table_name": ""}
+{"text": "List all fields in the queue.job.dashboard model.", "response": "The queue.job.dashboard model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "queue.job.dashboard", "table_name": ""}
+{"text": "Show me the fields of account.ebupot.", "response": "The account.ebupot model has 18 fields: year, name, is_used, invoice_ids, tax_report_id, date_from, date_to, partner_id, company_id, ebupot_template, tahun_pajak, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 3, boolean: 1, one2many: 1, selection: 1, date: 2, binary: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.ebupot", "table_name": ""}
+{"text": "How to query access.management data?", "response": "To use the access.management model, you need to provide values for required fields: company_ids. Readonly fields: self_module_menu_ids, self_model_ids, total_rules, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "access.management", "table_name": ""}
+{"text": "What is the sms.cancel model?", "response": "The sms.cancel model represents Dismiss notification for resend by model in the ERP system. It contains 9 fields and is used to manage dismiss notification for resend by model data. Key fields include: model, help_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sms.cancel", "table_name": ""}
+{"text": "What are the technical details of vendor.evaluation.template.eval?", "response": "The vendor.evaluation.template.eval model is defined in module: equip3_purchase_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "vendor.evaluation.template.eval", "table_name": ""}
+{"text": "What business logic is in account.fiscal.position?", "response": "To use the account.fiscal.position model, you need to provide values for required fields: company_id, name. Readonly fields: company_id, states_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.fiscal.position", "table_name": ""}
+{"text": "Which fields in report.equip3_pos_report.report_open_session are computed?", "response": "The report.equip3_pos_report.report_open_session model is defined in module: equip3_pos_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_pos_report.report_open_session", "table_name": ""}
+{"text": "Show me the relational structure of target.activity.line.res.", "response": "The target.activity.line.res model has 5 relational fields: activity_id -> target.activity; user_id -> res.users; activity_type -> mail.activity.type; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "target.activity.line.res", "table_name": ""}
+{"text": "Describe the field structure of crm.lead2opportunity.partner.", "response": "The crm.lead2opportunity.partner model has 15 fields: name, action, lead_id, duplicated_lead_ids, partner_id, user_id, team_id, force_assignment, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 2, many2one: 6, many2many: 1, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.lead2opportunity.partner", "table_name": ""}
+{"text": "How to create records in sh.mrp.allow.qc.measurement?", "response": "To use the sh.mrp.allow.qc.measurement model, you need to provide values for required fields: none. Readonly fields: product_id, sh_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.mrp.allow.qc.measurement", "table_name": ""}
+{"text": "Describe the many2many relations for payment.voucher.line.", "response": "The payment.voucher.line model has 5 relational fields: invoice_number_id -> account.move; currency_id -> res.currency; voucher_id -> payment.voucher; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "payment.voucher.line", "table_name": ""}
+{"text": "What fields does assets.approval.reject have?", "response": "The assets.approval.reject model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "assets.approval.reject", "table_name": ""}
+{"text": "What are the technical details of setu.inventory.fsn.xyz.analysis.bi.report?", "response": "The setu.inventory.fsn.xyz.analysis.bi.report model is defined in module: setu_advance_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "setu.inventory.fsn.xyz.analysis.bi.report", "table_name": ""}
+{"text": "Can you explain the purpose of mail.blacklist?", "response": "The mail.blacklist model represents Mail Blacklist in the ERP system. It contains 24 fields and is used to manage mail blacklist data. Key fields include: email, active, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.blacklist", "table_name": ""}
+{"text": "What models are connected to project.create.sale.order.line?", "response": "The project.create.sale.order.line model has 7 relational fields: wizard_id -> project.create.sale.order; product_id -> product.product; currency_id -> res.currency; employee_id -> hr.employee; sale_line_id -> sale.order.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "project.create.sale.order.line", "table_name": ""}
+{"text": "What models are connected to setu.inventory.turnover.analysis.report?", "response": "The setu.inventory.turnover.analysis.report model has 7 relational fields: product_category_ids -> product.category; product_ids -> product.product; warehouse_ids -> stock.warehouse; company_id -> res.company; company_ids -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_category_ids, product_ids, warehouse_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.turnover.analysis.report", "table_name": ""}
+{"text": "What modules define stock.picking.batch.line?", "response": "The stock.picking.batch.line model is defined in module: equip3_inventory_operations_countd. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.picking.batch.line", "table_name": ""}
+{"text": "Describe the many2many relations for website.robots.", "response": "The website.robots model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.robots", "table_name": ""}
+{"text": "List all fields in the account.pettycash.fund.reconcile model.", "response": "The account.pettycash.fund.reconcile model has 14 fields: fund, date, payable_account, reconciled_amount, move, vouchers, is_pettycash_voucher_approved, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, float: 1, many2many: 1, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.pettycash.fund.reconcile", "table_name": ""}
+{"text": "How is calendar.event.reschedule.wizard used in the system?", "response": "The calendar.event.reschedule.wizard model represents Get Meeting Reschedule Reason in the ERP system. It contains 10 fields and is used to manage get meeting reschedule reason data. Key fields include: reschedule_date, reschedule_reason, have_reschedule_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "calendar.event.reschedule.wizard", "table_name": ""}
+{"text": "Describe the pos.receipt.template model in Odoo.", "response": "The pos.receipt.template model represents POS Receipt Template in the ERP system. It contains 28 fields and is used to manage pos receipt template data. Key fields include: name, is_default, size, custom_size, is_need_header, receipt_header_text, is_need_footer, receipt_footer_text, is_receipt_disc_in_orderline, is_receipt_tax_include_orderline, is_receipt_serial_lot_info, is_receipt_savings_summary, savings_summary_text, is_receipt_product_code, preview_receipt, company_id, voucher_receipt_display, generate_voucher_id, is_voucher_receipt, is_show_discount_detail, is_receipt_member_info, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.receipt.template", "table_name": ""}
+{"text": "How to create records in rn.approval.matrix?", "response": "To use the rn.approval.matrix model, you need to provide values for required fields: name, warehouse_id. Readonly fields: create_date, create_uid, level, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "rn.approval.matrix", "table_name": ""}
+{"text": "How is account.partner.ledger used in the system?", "response": "The account.partner.ledger model represents Partner Ledger Report in the ERP system. It contains 21 fields and is used to manage partner ledger report data. Key fields include: journal_ids, account_ids, display_account, partner_ids, partner_category_ids, reconciled, account_type_ids, show_all_transaction, expand, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.partner.ledger", "table_name": ""}
+{"text": "What business logic is in asset.asset.sale?", "response": "To use the asset.asset.sale model, you need to provide values for required fields: partner_id, amount, is_invoice, currency_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "asset.asset.sale", "table_name": ""}
+{"text": "Can you explain the purpose of account.trial.balance?", "response": "The account.trial.balance model represents Trial Balance Report in the ERP system. It contains 16 fields and is used to manage trial balance report data. Key fields include: journal_ids, display_account, consolidate, all_account, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.trial.balance", "table_name": ""}
+{"text": "What models are connected to purchase.request.warning.line?", "response": "The purchase.request.warning.line model has 4 relational fields: warning_id -> purchase.request.warning; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.request.warning.line", "table_name": ""}
+{"text": "Show me the relational structure of pos.order.line.promotion.", "response": "The pos.order.line.promotion model has 4 relational fields: pos_order_line_id -> pos.order.line; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.order.line.promotion", "table_name": ""}
+{"text": "Describe the product.removal model in Odoo.", "response": "The product.removal model represents Removal Strategy in the ERP system. It contains 9 fields and is used to manage removal strategy data. Key fields include: name, method, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.removal", "table_name": ""}
+{"text": "How to query report.equip3_accounting_operation.report_statement_temp data?", "response": "To use the report.equip3_accounting_operation.report_statement_temp model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_operation.report_statement_temp", "table_name": ""}
+{"text": "What operations can I perform on snailmail.letter.missing.required.fields?", "response": "To use the snailmail.letter.missing.required.fields 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "snailmail.letter.missing.required.fields", "table_name": ""}
+{"text": "Can you explain the purpose of budget.budget.budget.line?", "response": "The budget.budget.budget.line model represents Budget Line in the ERP system. It contains 23 fields and is used to manage budget line data. Key fields include: name, budget_budget_id, analytic_account_id, analytic_group_id, general_budget_id, date_from, date_to, paid_date, currency_id, planned_amount, practical_amount, theoritical_amount, percentage, company_id, is_above_budget, budget_budget_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "budget.budget.budget.line", "table_name": ""}
+{"text": "How to query project.sale.line.employee.map data?", "response": "To use the project.sale.line.employee.map model, you need to provide values for required fields: project_id, employee_id. Readonly fields: company_id, price_unit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.sale.line.employee.map", "table_name": ""}
+{"text": "How does mail.wizard.invite relate to other models?", "response": "The mail.wizard.invite model has 4 relational fields: partner_ids -> res.partner; channel_ids -> mail.channel; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.wizard.invite", "table_name": ""}
+{"text": "What are the technical details of product.attribute.value?", "response": "The product.attribute.value model is defined in module: product. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.attribute.value", "table_name": ""}
+{"text": "What data can be stored in pos.loyalty.history.update.point?", "response": "The pos.loyalty.history.update.point model has 12 fields: type_apply, total_orders, total_point, pos_order_ids, parent_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, float: 2, many2many: 1, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.loyalty.history.update.point", "table_name": ""}
+{"text": "What models are connected to account.pettycash?", "response": "The account.pettycash model has 24 relational fields: cash_journal -> account.journal; custodian -> res.users; main_cash_account_id -> account.account; journal -> account.journal; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; move_id -> account.move; voucher_id -> account.pettycash.voucher.wizard; paid_voucher_ids -> account.pettycash.voucher.wizard; custodian_partner -> res.partner; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.pettycash", "table_name": ""}
+{"text": "How to query mass.editing.line data?", "response": "To use the mass.editing.line model, you need to provide values for required fields: server_action_id, field_id. Readonly fields: model_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mass.editing.line", "table_name": ""}
+{"text": "How do I use the pos.backup.orders model?", "response": "To use the pos.backup.orders model, you need to provide values for required fields: config_id. Readonly fields: config_id, unpaid_orders, total_orders, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.backup.orders", "table_name": ""}
+{"text": "What is the im_livechat.channel model?", "response": "The im_livechat.channel model represents Livechat Channel in the ERP system. It contains 30 fields and is used to manage livechat channel data. Key fields include: name, button_text, default_message, input_placeholder, header_background_color, title_color, button_background_color, button_text_color, web_page, are_you_inside, script_external, nbr_channel, image_128, user_ids, channel_ids, rule_ids, website_published, is_published, can_publish, website_url, website_description, rating_ids, rating_percentage_satisfaction, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "im_livechat.channel", "table_name": ""}
+{"text": "What are the technical details of receipt.payment.line.debit?", "response": "The receipt.payment.line.debit model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "receipt.payment.line.debit", "table_name": ""}
+{"text": "How does pos.cashbox.history relate to other models?", "response": "The pos.cashbox.history model has 5 relational fields: opened_by_user_id -> res.users; pos_session_id -> pos.session; pos_config_id -> pos.config; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.cashbox.history", "table_name": ""}
+{"text": "What is the stock.return.picking.inter.company model?", "response": "The stock.return.picking.inter.company model represents stock.return.picking.inter.company in the ERP system. It contains 12 fields and is used to manage stock.return.picking.inter.company data. Key fields include: product_id, quantity, uom_id, wizard_id, move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.return.picking.inter.company", "table_name": ""}
+{"text": "What fields does report.equip3_crm_tracking.crm_sales_tracking_visit_report have?", "response": "The report.equip3_crm_tracking.crm_sales_tracking_visit_report model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_crm_tracking.crm_sales_tracking_visit_report", "table_name": ""}
+{"text": "What modules define uom.uom?", "response": "The uom.uom model is defined in module: uom. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "uom.uom", "table_name": ""}
+{"text": "How do I use the saleblanket.saleblanket model?", "response": "To use the saleblanket.saleblanket model, you need to provide values for required fields: name, expiry_date, branch_id. Readonly fields: name, sale_order_count, creation_date, user_id, order_line_count, state, currency_id, state1, state2, state3, bo_state, bo_state_1, company_id, approving_matrix_bo_sale_id, is_bo_approval_matrix, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, approved_matrix_ids, amount_untaxed, amount_tax, amount_total, analytic_accounting, is_product_filled, max_line_sequence, report_template_id1, amount_to_text, activity_state, activity_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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "saleblanket.saleblanket", "table_name": ""}
+{"text": "Describe the ir.logging model in Odoo.", "response": "The ir.logging model represents Logging in the ERP system. It contains 15 fields and is used to manage logging data. Key fields include: create_uid, create_date, write_uid, write_date, name, type, dbname, level, message, path, func, line, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.logging", "table_name": ""}
+{"text": "What are common use cases for base_import.tests.models.float?", "response": "To use the base_import.tests.models.float 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base_import.tests.models.float", "table_name": ""}
+{"text": "What operations can I perform on report.equip3_inventory_reports.expiring_product_calendar?", "response": "To use the report.equip3_inventory_reports.expiring_product_calendar model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_inventory_reports.expiring_product_calendar", "table_name": ""}
+{"text": "What does the export.product.csv model represent?", "response": "The export.product.csv model represents export.product.csv in the ERP system. It contains 40 fields and is used to manage export.product.csv data. Key fields include: name, product_id_attachment_id, product_id_csv_created, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "export.product.csv", "table_name": ""}
+{"text": "What are the available fields for sale.payment.acquirer.onboarding.wizard?", "response": "The sale.payment.acquirer.onboarding.wizard model has 19 fields: payment_method, paypal_user_type, paypal_email_account, paypal_seller_account, paypal_pdt_token, stripe_secret_key, stripe_publishable_key, manual_name, journal_name, acc_number, manual_post_msg, _data_fetched, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 2, char: 9, html: 1, boolean: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "What fields does report.equip3_accounting_reports.equity_move have?", "response": "The report.equip3_accounting_reports.equity_move model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.equity_move", "table_name": ""}
+{"text": "How is base_import.import used in the system?", "response": "The base_import.import model represents Base Import in the ERP system. It contains 11 fields and is used to manage base import data. Key fields include: res_model, file, file_name, file_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.import", "table_name": ""}
+{"text": "What is the sale.report model?", "response": "The sale.report model represents Sales Analysis Report in the ERP system. It contains 45 fields and is used to manage sales analysis report data. Key fields include: name, date, product_id, product_uom, product_uom_qty, qty_delivered, qty_to_invoice, qty_invoiced, partner_id, company_id, user_id, price_total, price_subtotal, untaxed_amount_to_invoice, untaxed_amount_invoiced, product_tmpl_id, categ_id, nbr, pricelist_id, analytic_account_id, team_id, country_id, industry_id, commercial_partner_id, weight, volume, discount, discount_amount, campaign_id, medium_id, source_id, order_id, warehouse_id, website_id, branch_id, state, margin, city_id, state_id, untaxed_amount, total_amount, grand_total_order, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.report", "table_name": ""}
+{"text": "Can you explain the purpose of sh.sale.category.wizard?", "response": "The sh.sale.category.wizard model represents Sale By Category Wizard in the ERP system. It contains 14 fields and is used to manage sale by category wizard data. Key fields include: sh_end_date, sh_category_ids, company_ids, company_id, category_order_dic, currency_precision, sh_start_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.sale.category.wizard", "table_name": ""}
+{"text": "What are common use cases for digest.digest?", "response": "To use the digest.digest model, you need to provide values for required fields: name, periodicity. Readonly fields: available_fields, is_subscribed, state, kpi_res_users_connected_value, kpi_mail_message_total_value, kpi_account_total_revenue_value, kpi_crm_lead_created_value, kpi_crm_opportunities_won_value, kpi_livechat_rating_value, kpi_livechat_conversations_value, kpi_livechat_response_value, kpi_project_task_opened_value, kpi_pos_total_value, kpi_all_sale_total_value, kpi_website_sale_total_value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "digest.digest", "table_name": ""}
+{"text": "Show me the fields of account.pettycash.", "response": "The account.pettycash model has 65 fields: replenish_interval, times, replenish_date, replenish_date_2, replenish_week, replenish_intervals, auto_replenish, cash_journal, number, name, custodian, main_cash_account_id, journal, amount, balance, virtual_balance, company_id, branch_id, effective_date, create_uid, create_date, state, move_id, voucher_id, paid_voucher_ids, is_custodian_user, custodian_partner, is_replenished, next_execute_date, 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, write_uid, write_date, __last_update. Field types distribution: selection: 8, integer: 6, boolean: 8, many2one: 15, char: 8, float: 3, date: 4, datetime: 3, one2many: 7, many2many: 2, text: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.pettycash", "table_name": ""}
+{"text": "List all fields in the sh.purchase.tags model.", "response": "The sh.purchase.tags model has 9 fields: name, color, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.purchase.tags", "table_name": ""}
+{"text": "Describe the field structure of report.report_finished_good_rework.", "response": "The report.report_finished_good_rework model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.report_finished_good_rework", "table_name": ""}
+{"text": "Show me the fields of accounting.flow.wizard.", "response": "The accounting.flow.wizard model has 8 fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "accounting.flow.wizard", "table_name": ""}
+{"text": "How to create records in stock.move?", "response": "To use the stock.move model, you need to provide values for required fields: name, date, company_id, product_uom_qty, product_uom, location_id, location_dest_id, procure_method, product_id. Readonly fields: priority, create_date, date_deadline, product_uom_category_id, state, scrapped, delay_alert_date, availability, has_tracking, show_details_visible, show_reserved_availability, is_locked, is_initial_demand_editable, is_quantity_done_editable, reference, has_move_lines, picking_type_entire_packs, display_assign_serial, forecast_availability, forecast_expected_date, allowed_operation_ids, unit_factor, is_done, order_finished_lot_ids, should_consume_qty, use_expiration_date, is_reconstruct_svl, purchase_line_id, created_purchase_line_id, sh_last_qc_date, sh_last_qc_state, number_of_test, created_purchase_request_line_id, purchase_request_ids, weight, product_description, sh_stock_move_bm_is_cont_scan, length, width, height, is_adjustable_picking, picking_state, filter_move_package_ids, serial_no, next_serial, product_type, is_serial_number, next_lot, is_autogenerate, picking_code, is_product_service_operation, is_product_service_operation_delivery, is_product_service_operation_receiving, serial, remaining, fulfillment, current_qty, responsible, late_time, late_time_hours, process_status, process_time, process_time_hours, packaging_ids, measure_ids, product_id_domain, assembly_unit_factor, assembly_should_consume_qty, assembly_product_free_qty, description, kitchen_unit_factor, kitchen_should_consume_qty, kitchen_product_free_qty, sub_total, type_product_bom, assembly_record_type, assembly_confirm_date, assembly_product_id, assembly_bom_id, assembly_svl_value, assembly_difference, kitchen_confirm_date, kitchen_product_id, kitchen_bom_id, kitchen_svl_value, kitchen_difference, product_warehouse, product_location, product_barcode, vendor_id, state_check, picking_type_code, reserved_availability, picking_reference, date_done, volume, movement_type, cost, pos_branch_id, so_antar_badan, po_antar_badan, sale_order_id, purchase_order_id, date_done_real, price_subtotal, price_tax, price_total, price_untaxed_amount, id, display_name, create_uid, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.move", "table_name": ""}
+{"text": "Which fields in base_import.tests.models.float are computed?", "response": "The base_import.tests.models.float model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.float", "table_name": ""}
+{"text": "What is the ks_custom_report.ks_column model?", "response": "The ks_custom_report.ks_column model represents Report Field in the ERP system. It contains 25 fields and is used to manage report field data. Key fields include: name, ks_cr_model_id, ks_model_field_chan, ks_model_name, ks_cr_field_id, ks_incl_search_filter, ks_incl_group_filter, sequence, ks_operator, ks_value, ks_visible_operator_fields, ks_visible_date_fields, ks_alter_values, ks_year, ks_month, ks_week, ks_day, ks_hour, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks_custom_report.ks_column", "table_name": ""}
+{"text": "What are the available fields for account.asset.category.fiscal?", "response": "The account.asset.category.fiscal model has 25 fields: asset_category_id, is_fiscal_asset_type, method_time, method_number, method_period, method_end, method, asset_type, asset_type_1, sub_asset_type, non_building_type, method_number_fiscal, prorata, cut_off_asset_date, is_monthly_depreciation, is_reset_january, double_declining_method_number, double_declining_method_period, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, boolean: 4, selection: 6, integer: 7, date: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.asset.category.fiscal", "table_name": ""}
+{"text": "What models are connected to stock.scrap.approval.matrix?", "response": "The stock.scrap.approval.matrix model has 18 relational fields: company_id -> res.company; warehouse_id -> stock.warehouse; branch_id -> res.branch; sc_approval_matrix_line_ids -> stock.scrap.approval.matrix.line; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.scrap.approval.matrix", "table_name": ""}
+{"text": "What modules define report.sh_purchase_reports.sh_po_by_category_doc?", "response": "The report.sh_purchase_reports.sh_po_by_category_doc model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_purchase_reports.sh_po_by_category_doc", "table_name": ""}
+{"text": "Can you explain the purpose of account.multipayment?", "response": "The account.multipayment model represents Multipayment in the ERP system. It contains 90 fields and is used to manage multipayment data. Key fields include: name, partner_id, amount, journal_id, currency_id, date, ref, memo, line_credit_ids, line_debit_ids, diff_amount, partner_type, total_amount_credit, total_amount_debit, payment_id_count, company_id, branch_id, create_uid, create_date, different_move_id, request_partner_id, payment_method, multipul_payment_approval_matrix_id, is_multi_payment_approval_matrix, is_approve_button, approved_matrix_ids, approval_matrix_line_id, action_validate_boolean, action_draft_boolean, action_cancel_boolean, request_for_approval_boolean, action_approved_rp_boolean, rp_reject_boolean, state_boolean, state1_boolean, state2_boolean, difference_ids, payment_difference_amount, writeoff_account_id, writeoff_label, payment_type, clearing_account_id, move_id, due_date, receive_date, clearing_date, is_vendor, state, state1, state2, payment_ids, invoice_cutoff_date, is_cutoff_date, is_check_all, 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, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.multipayment", "table_name": ""}
+{"text": "Tell me about the crm.lead.product model.", "response": "The crm.lead.product model represents crm.lead.product in the ERP system. It contains 14 fields and is used to manage crm.lead.product data. Key fields include: product_id, description, qty, product_uom, price_unit, tax_id, lead_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.lead.product", "table_name": ""}
+{"text": "How is base.language.import implemented technically?", "response": "The base.language.import model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base.language.import", "table_name": ""}
+{"text": "What foreign keys exist in account.tour.upload.bill?", "response": "The account.tour.upload.bill model has 14 relational fields: composer_id -> mail.compose.message; create_uid -> res.users; write_uid -> res.users; parent_id -> mail.message; template_id -> mail.template; attachment_ids -> ir.attachment; author_id -> res.partner; subtype_id -> mail.message.subtype; mail_activity_type_id -> mail.activity.type; partner_ids -> res.partner; mail_server_id -> ir.mail_server; mass_mailing_id -> mailing.mailing; campaign_id -> utm.campaign; mailing_list_ids -> mailing.list. Many2many fields: attachment_ids, partner_ids, mailing_list_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.tour.upload.bill", "table_name": ""}
+{"text": "What are common use cases for list.product?", "response": "To use the list.product 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "list.product", "table_name": ""}
+{"text": "Which fields in inter.transfer.company are computed?", "response": "The inter.transfer.company model is defined in module: bi_inter_company_transfer. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "inter.transfer.company", "table_name": ""}
+{"text": "How do I use the material.request.show.stock model?", "response": "To use the material.request.show.stock 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "material.request.show.stock", "table_name": ""}
+{"text": "What fields does pos.session have?", "response": "The pos.session model has 101 fields: company_id, config_id, name, user_id, currency_id, start_at, stop_at, sequence_number, cash_control, cash_journal_id, cash_register_id, cash_register_balance_start, cash_register_balance_end, cash_register_difference, cash_real_difference, cash_real_transaction, cash_real_expected, order_ids, order_count, statement_ids, failed_pickings, picking_count, picking_ids, rescue, move_id, payment_method_ids, total_payments_amount, is_in_company_currency, update_stock_at_closing, move_id_old, orderline_checked, crm_team_id, required_reinstall_cache, backup_session, pos_branch_id, employee_id, lock_state, order_log_ids, opened_at, opened_uid, last_login_time, login_number, state, cash_opening_balance, cash_closing_balance, is_closing_wizard, pos_config_cashbox_lines_ids, pos_config_cashbox_clsosing_line_ids, cash_register_balance_end_real, cashier_id, total_invoice_count, total_faktur_count, log_cashier_ids, is_multi_session, order_with_receivable_invoice_ids, pos_config_uuid, pos_session_cashbox_wizard_ids, cash_management_ids, cash_history_ids, gain_loss_move_id, is_pos_config_save_order_history_local, scheduler_invoice_finish_date, void_ids, bank_register_total_entry_encoding, cash_register_total_entry_encoding, bank_closing_balance, pos_session_bank_cashbox_wizard_ids, to_recompute, is_invoice_recreate, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 19, char: 6, datetime: 8, integer: 11, boolean: 18, monetary: 12, one2many: 17, many2many: 3, float: 1, selection: 4, date: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.session", "table_name": ""}
+{"text": "Show me the fields of theme.utils.", "response": "The theme.utils model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "theme.utils", "table_name": ""}
+{"text": "Which fields in sale.terms.and.conditions are computed?", "response": "The sale.terms.and.conditions model is defined in module: equip3_sale_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.terms.and.conditions", "table_name": ""}
+{"text": "What does the account.invoice.exchange.approval.wizard model represent?", "response": "The account.invoice.exchange.approval.wizard model represents account.invoice.exchange.approval.wizard in the ERP system. It contains 8 fields and is used to manage account.invoice.exchange.approval.wizard data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.invoice.exchange.approval.wizard", "table_name": ""}
+{"text": "How is pos.qrcode used in the system?", "response": "The pos.qrcode model represents QrCode fields display for scan qrcode of Receipt in the ERP system. It contains 10 fields and is used to manage qrcode fields display for scan qrcode of receipt data. Key fields include: name, field_id, config_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.qrcode", "table_name": ""}
+{"text": "Describe the implementation of website.page.", "response": "The website.page model is defined in module: website. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.page", "table_name": ""}
+{"text": "What are the technical details of inter.transfer.company?", "response": "The inter.transfer.company model is defined in module: bi_inter_company_transfer. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "inter.transfer.company", "table_name": ""}
+{"text": "What modules define res.currency?", "response": "The res.currency model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.currency", "table_name": ""}
+{"text": "What business logic is in report.fonts?", "response": "To use the report.fonts model, you need to provide values for required fields: family, name, path, mode. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.fonts", "table_name": ""}
+{"text": "What are the technical details of res.users.access.report.record?", "response": "The res.users.access.report.record model is defined in module: report_user_access_right. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.access.report.record", "table_name": ""}
+{"text": "Tell me about the report.sh_inventory_mrp_qc.quality_check_doc model.", "response": "The report.sh_inventory_mrp_qc.quality_check_doc model represents quality check report abstract model in the ERP system. It contains 3 fields and is used to manage quality check report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_inventory_mrp_qc.quality_check_doc", "table_name": ""}
+{"text": "How is acrux.chat.default.answer used in the system?", "response": "The acrux.chat.default.answer model represents Chat Default Answer in the ERP system. It contains 17 fields and is used to manage chat default answer data. Key fields include: name, sequence, file_attach, file_attach_name, template_id, default_answer_type, text, ttype, res_model, res_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "acrux.chat.default.answer", "table_name": ""}
+{"text": "What foreign keys exist in base.import.module?", "response": "The base.import.module model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.import.module", "table_name": ""}
+{"text": "What are the relationships in pos.voucher.report?", "response": "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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.voucher.report", "table_name": ""}
+{"text": "What are the relationships in account.reconcile.model.line.template?", "response": "The account.reconcile.model.line.template model has 5 relational fields: model_id -> account.reconcile.model.template; account_id -> account.account.template; tax_ids -> account.tax.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.reconcile.model.line.template", "table_name": ""}
+{"text": "Tell me about the mrp.workcenter model.", "response": "The mrp.workcenter model represents Work Center in the ERP system. It contains 72 fields and is used to manage work center data. Key fields include: active, note, sequence, color, routing_line_ids, order_ids, workorder_count, workorder_ready_count, workorder_progress_count, workorder_pending_count, workorder_late_count, time_ids, working_state, blocked_time, productive_time, oee, performance, workcenter_load, costs_hour_account_id, name, location_id, location_finished_id, location_rejected_id, location_byproduct_id, oh_time, ov_material, costs_hour, branch_id, create_uid, alternative_workcenter_ids, code, company_id, time_efficiency, capacity, oee_target, time_start, time_stop, is_branch_required, resource_id, resource_calendar_id, tz, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.workcenter", "table_name": ""}
+{"text": "What data can be stored in res.users.identitycheck?", "response": "The res.users.identitycheck model has 8 fields: password, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.users.identitycheck", "table_name": ""}
+{"text": "What operations can I perform on account.analytic.tag?", "response": "To use the account.analytic.tag model, you need to provide values for required fields: name. Readonly fields: activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.analytic.tag", "table_name": ""}
+{"text": "Which fields in overhead.time are computed?", "response": "The overhead.time model is defined in module: equip3_manuf_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "overhead.time", "table_name": ""}
+{"text": "What foreign keys exist in ir.qweb.field.contact?", "response": "The ir.qweb.field.contact model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb.field.contact", "table_name": ""}
+{"text": "What operations can I perform on stock.backorder.confirmation.line?", "response": "To use the stock.backorder.confirmation.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.backorder.confirmation.line", "table_name": ""}
+{"text": "Describe the many2many relations for crm.lead.lost.", "response": "The crm.lead.lost model has 3 relational fields: lost_reason_id -> crm.lost.reason; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.lead.lost", "table_name": ""}
+{"text": "Describe the order.picking model in Odoo.", "response": "The order.picking model represents Order Picking in the ERP system. It contains 9 fields and is used to manage order picking data. Key fields include: move_id, order_picking_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "order.picking", "table_name": ""}
+{"text": "What modules define ir.qweb.field.datetime?", "response": "The ir.qweb.field.datetime model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.qweb.field.datetime", "table_name": ""}
+{"text": "Describe the implementation of login.as.", "response": "The login.as model is defined in module: oi_login_as. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "login.as", "table_name": ""}
+{"text": "Tell me about the sh.sale.category.xls model.", "response": "The sh.sale.category.xls model represents Sale by Category Xls Report in the ERP system. It contains 9 fields and is used to manage sale by category xls report data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.sale.category.xls", "table_name": ""}
+{"text": "What does the sh.back.theme.config.settings model represent?", "response": "The sh.back.theme.config.settings model represents Back Theme Config Settings in the ERP system. It contains 89 fields and is used to manage back theme config settings data. Key fields include: name, theme_color, theme_style, pre_theme_style, primary_color, primary_hover, primary_active, gradient_color, secondary_color, secondary_hover, secondary_active, header_background_color, header_font_color, header_hover_color, header_active_color, h1_color, h2_color, h3_color, h4_color, h5_color, h6_color, p_color, h1_size, h2_size, h3_size, h4_size, h5_size, h6_size, p_size, body_font_color, body_background_type, body_background_color, body_background_image, body_font_family, body_google_font_family, is_used_google_font, button_style, is_button_with_icon_text, is_button_with_box_shadow, separator_style, separator_color, sidebar_background_style, sidebar_background_image, sidebar_background_color, sidebar_font_color, sidebar_font_hover_color, sidebar_font_hover_background_color, sidebar_is_show_nav_bar, sidebar_collapse_style, loading_style, progress_style, progress_height, progress_color, loading_gif, loading_gif_file_name, list_view_border, list_view_is_hover_row, list_view_hover_bg_color, list_view_even_row_color, list_view_odd_row_color, login_page_style, login_page_background_type, login_page_background_color, login_page_background_image, login_page_box_color, login_page_banner_image, login_page_icon_img, login_page_icon_img_long, is_sticky_form, is_sticky_chatter, is_sticky_list, is_sticky_list_inside_form, icon_style, modal_popup_style, tab_style, tab_style_mobile, horizontal_tab_style, vertical_tab_style, form_element_style, search_style, breadcrumb_style, chatter_position, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.back.theme.config.settings", "table_name": ""}
+{"text": "Tell me about the base_import.tests.models.char model.", "response": "The base_import.tests.models.char model represents Tests : Base Import Model, Character in the ERP system. It contains 8 fields and is used to manage tests : base import model, character data. Key fields include: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.char", "table_name": ""}
+{"text": "What fields does report_excel_export_gen have?", "response": "The report_excel_export_gen model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report_excel_export_gen", "table_name": ""}
+{"text": "Describe the sh.product.qrcode.generator.wizard model in Odoo.", "response": "The sh.product.qrcode.generator.wizard model represents Product QR Code Generator Wizard in the ERP system. It contains 10 fields and is used to manage product qr code generator wizard data. Key fields include: product_tmpl_ids, product_var_ids, is_overwrite_existing, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.product.qrcode.generator.wizard", "table_name": ""}
+{"text": "What operations can I perform on crm.lost.reason?", "response": "To use the crm.lost.reason model, you need to provide values for required fields: name. Readonly fields: leads_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.lost.reason", "table_name": ""}
+{"text": "What is the report_excel_export_wizard model?", "response": "The report_excel_export_wizard model represents report_excel_export Wizard in the ERP system. It contains 8 fields and is used to manage report_excel_export wizard data. Key fields include: multiple_export, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report_excel_export_wizard", "table_name": ""}
+{"text": "What is the purchase.request.line.make.purchase.order model?", "response": "The purchase.request.line.make.purchase.order model represents Purchase Request Line Make Purchase Order in the ERP system. It contains 15 fields and is used to manage purchase request line make purchase order data. Key fields include: item_ids, sync_data_planned, supplier_ids, supplier_id, create_rfq, partner_id, pr_id, purchase_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.request.line.make.purchase.order", "table_name": ""}
+{"text": "Show me the fields of sh.model.fields.purchase.order.selection.", "response": "The sh.model.fields.purchase.order.selection model has 11 fields: sh_field_po_id, value, name, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.model.fields.purchase.order.selection", "table_name": ""}
+{"text": "What are the available fields for purchase.order.partner.credit?", "response": "The purchase.order.partner.credit model has 15 fields: name, order_partner, vendor_credit_limit, is_set_vendor_onhold, total_payable, current_order, purchase_orders_cnt_amt, cust_invoice_cnt_amt, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 3, boolean: 1, char: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.order.partner.credit", "table_name": ""}
+{"text": "What methods are available in ks_dashboard_ninja.board_template?", "response": "The ks_dashboard_ninja.board_template model is defined in module: ks_dashboard_ninja. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks_dashboard_ninja.board_template", "table_name": ""}
+{"text": "What fields does return.inter.transfer.company have?", "response": "The return.inter.transfer.company model has 24 fields: sale_id, sale_count, invoice_count, bill_count, invoice_id, purchase_id, purchase_count, internal_id, internal_count, name, state, from_warehouse, currency_id, to_warehouse, pricelist_id, product_lines, product_return_moves, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, integer: 6, many2many: 1, char: 2, selection: 1, one2many: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "return.inter.transfer.company", "table_name": ""}
+{"text": "How do I use the report.sh_sale_reports.sh_sale_product_indent_doc model?", "response": "To use the report.sh_sale_reports.sh_sale_product_indent_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_sale_product_indent_doc", "table_name": ""}
+{"text": "How does equip3.pos.membership.report relate to other models?", "response": "The equip3.pos.membership.report model has 1 relational fields: company_id -> res.company. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "equip3.pos.membership.report", "table_name": ""}
+{"text": "Which fields in account.partial.reconcile are computed?", "response": "The account.partial.reconcile model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.partial.reconcile", "table_name": ""}
+{"text": "How to create records in vendor.evaluation.template?", "response": "To use the vendor.evaluation.template model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "vendor.evaluation.template", "table_name": ""}
+{"text": "What modules define account.equity.move?", "response": "The account.equity.move model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.equity.move", "table_name": ""}
+{"text": "What methods are available in stock.return.move.line?", "response": "The stock.return.move.line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.return.move.line", "table_name": ""}
+{"text": "How is rating.rating implemented technically?", "response": "The rating.rating model is defined in module: rating. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "rating.rating", "table_name": ""}
+{"text": "What foreign keys exist in ir.http?", "response": "The ir.http model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.http", "table_name": ""}
+{"text": "What data can be stored in ir.module.category?", "response": "The ir.module.category model has 17 fields: name, parent_id, child_ids, module_nr, module_ids, description, sequence, visible, exclusive, xml_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 3, one2many: 2, integer: 3, text: 1, boolean: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.module.category", "table_name": ""}
+{"text": "Describe the many2many relations for budget.purchase.lines.", "response": "The budget.purchase.lines model has 12 relational fields: purchase_budget_id -> budget.purchase; analytic_account_id -> account.analytic.account; analytic_group_id -> account.analytic.group; product_budget -> account.budget.post; currency_id -> res.currency; company_id -> res.company; parent_analytic_account_id -> account.analytic.account; account_tag_ids -> account.analytic.tag; product_id -> product.product; purchase_order_line_budget_id -> purchase.order.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: account_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "budget.purchase.lines", "table_name": ""}
+{"text": "What are the technical details of ram.tags?", "response": "The ram.tags model is defined in module: dev_rma. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ram.tags", "table_name": ""}
+{"text": "What data can be stored in do.approval_matrix_detail?", "response": "The do.approval_matrix_detail model has 11 fields: location_name, usage, company_id, do_approval_matrix_id2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "do.approval_matrix_detail", "table_name": ""}
+{"text": "What foreign keys exist in acrux.chat.conversation?", "response": "The acrux.chat.conversation model has 12 relational fields: connector_id -> acrux.chat.connector; res_partner_id -> res.partner; chat_message_ids -> acrux.chat.message; sellman_id -> res.users; company_id -> res.company; team_id -> crm.team; crm_lead_id -> crm.lead; sale_order_id -> sale.order; partner_sellman_id -> res.users; team_ids -> crm.team; create_uid -> res.users; write_uid -> res.users. Many2many fields: team_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "acrux.chat.conversation", "table_name": ""}
+{"text": "How do I use the faktur.message model?", "response": "To use the faktur.message 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "faktur.message", "table_name": ""}
+{"text": "Show me the fields of account.balance.report.", "response": "The account.balance.report model has 14 fields: journal_ids, display_account, 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 types distribution: many2many: 1, selection: 2, date: 2, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.balance.report", "table_name": ""}
+{"text": "What foreign keys exist in account.resequence.wizard?", "response": "The account.resequence.wizard model has 3 relational fields: move_ids -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: move_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.resequence.wizard", "table_name": ""}
+{"text": "What is the sh.qc.team model?", "response": "The sh.qc.team model represents Quality Team in the ERP system. It contains 50 fields and is used to manage quality team data. Key fields include: sh_logged_user, name, email, user_ids, sh_employee, company_id, name_id, alias_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, alias_name, alias_model_id, alias_user_id, alias_defaults, alias_force_thread_id, alias_domain, alias_parent_model_id, alias_parent_thread_id, alias_bounced_content, alias_contact.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.qc.team", "table_name": ""}
+{"text": "What is the report.sh_sale_reports.sh_sale_by_category_doc model?", "response": "The report.sh_sale_reports.sh_sale_by_category_doc model represents Sale by category report abstract model in the ERP system. It contains 3 fields and is used to manage sale by category report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_sale_reports.sh_sale_by_category_doc", "table_name": ""}
+{"text": "What fields does setu.inventory.turnover.analysis.bi.report have?", "response": "The setu.inventory.turnover.analysis.bi.report model has 17 fields: product_id, product_category_id, warehouse_id, company_id, opening_stock, closing_stock, average_stock, sales, turnover_ratio, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, float: 5, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.turnover.analysis.bi.report", "table_name": ""}
+{"text": "Describe the bank.account.account model in Odoo.", "response": "The bank.account.account model represents Bank Account Account in the ERP system. It contains 12 fields and is used to manage bank account account data. Key fields include: acc_number, bank_id, bank_bic, company_id, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "bank.account.account", "table_name": ""}
+{"text": "What fields does report.base.report_irmodulereference have?", "response": "The report.base.report_irmodulereference model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.base.report_irmodulereference", "table_name": ""}
+{"text": "What does the mail.alias.mixin model represent?", "response": "The mail.alias.mixin model represents Email Aliases Mixin in the ERP system. It contains 18 fields and is used to manage email aliases mixin data. Key fields include: alias_id, id, display_name, __last_update, alias_name, alias_model_id, alias_user_id, alias_defaults, alias_force_thread_id, alias_domain, alias_parent_model_id, alias_parent_thread_id, alias_bounced_content, alias_contact, create_uid, create_date, write_uid, write_date.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.alias.mixin", "table_name": ""}
+{"text": "Can you explain the purpose of pos.cash.in.out?", "response": "The pos.cash.in.out model represents Pos Cash In Out in the ERP system. It contains 13 fields and is used to manage pos cash in out data. Key fields include: action, product_id, amount, reason, pos_session_id, account_move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.cash.in.out", "table_name": ""}
+{"text": "What fields does qiscus.wa.template.content have?", "response": "The qiscus.wa.template.content model has 13 fields: template_id, name, language, content_id, content, category, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 2, text: 1, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "qiscus.wa.template.content", "table_name": ""}
+{"text": "What are the relationships in vendor.evaluation.rating?", "response": "The vendor.evaluation.rating model has 2 relational fields: partner_id -> res.partner; branch_id -> res.branch. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "vendor.evaluation.rating", "table_name": ""}
+{"text": "What data can be stored in account.tax.map.purchase.line?", "response": "The account.tax.map.purchase.line model has 17 fields: company_id, purchase_tax_id, target_company, target_purchase_tax, map_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, line_ids, child_company_id, ownership, sales_line_ids, purchase_line_ids. Field types distribution: many2one: 8, integer: 1, char: 1, datetime: 3, one2many: 3, float: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.tax.map.purchase.line", "table_name": ""}
+{"text": "Describe the field structure of pos.loyalty.update.point.", "response": "The pos.loyalty.update.point model has 19 fields: name, type_apply, state, member_id, pos_order_ids, is_orders, total_orders, current_point, reward_point, total_point, history_ids, is_editable_point, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, selection: 2, many2one: 3, many2many: 1, boolean: 2, float: 4, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.loyalty.update.point", "table_name": ""}
+{"text": "What data can be stored in stock.location?", "response": "The stock.location model has 66 fields: name, complete_name, active, usage, location_id, child_ids, comment, parent_path, company_id, scrap_location, return_location, removal_strategy_id, putaway_rule_ids, quant_ids, day_limit, freeze_status, barcode, posx, posy, posz, sizex, sizey, sizez, warehouse_id, valuation_in_account_id, valuation_out_account_id, occupied_order, capacity_unit, occupied_unit_theoretical, capacity_weight, capacity_volume, is_expired_stock_location, occupied_unit, to_trigger_occupied_unit, responsible_users, additional_transfer_note, on_max_capacity, putaway_destination, is_putaway_max_capacity, description, removal_priority, capacity_type, occupied_weight, occupied_volume, occupied_length, occupied_width, occupied_height, capacity_length, capacity_width, capacity_height, occupied_percent, branch_id, location_complete_name, warehouse_delivery_steps, location_display_name, tag_ids, quantity_validate, pos_branch_id, location_address_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 8, boolean: 9, selection: 4, many2one: 13, one2many: 3, text: 1, integer: 10, reference: 1, float: 13, many2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.location", "table_name": ""}
+{"text": "How is pos.global.discount used in the system?", "response": "The pos.global.discount model represents Management Global Discount in the ERP system. It contains 14 fields and is used to manage management global discount data. Key fields include: name, amount, product_id, reason, type, branch_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.global.discount", "table_name": ""}
+{"text": "What is the sale.adv.wizard.product.line model?", "response": "The sale.adv.wizard.product.line model represents Sale Multi Product Selection Advanced Wizard Product Line in the ERP system. It contains 13 fields and is used to manage sale multi product selection advanced wizard product line data. Key fields include: sale_adv_wizard_id, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.adv.wizard.product.line", "table_name": ""}
+{"text": "What are the relationships in pos.cash.in.out?", "response": "The pos.cash.in.out model has 5 relational fields: product_id -> product.product; pos_session_id -> pos.session; account_move_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.cash.in.out", "table_name": ""}
+{"text": "How do I use the sale.coupon.apply.code model?", "response": "To use the sale.coupon.apply.code model, you need to provide values for required fields: coupon_code. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.coupon.apply.code", "table_name": ""}
+{"text": "What foreign keys exist in ir.demo?", "response": "The ir.demo model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.demo", "table_name": ""}
+{"text": "How does purchase.request.line.make.purchase.order relate to other models?", "response": "The purchase.request.line.make.purchase.order model has 8 relational fields: item_ids -> purchase.request.line.make.purchase.order.item; supplier_ids -> res.partner; supplier_id -> res.partner; partner_id -> res.partner; pr_id -> purchase.request; purchase_order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: supplier_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.request.line.make.purchase.order", "table_name": ""}
+{"text": "List all fields in the sh.qc.team.type model.", "response": "The sh.qc.team.type model has 15 fields: name, team_id, check_count, alert_count, pending_qc_count, failed_qc_count, passed_qc_count, partially_passed_qc_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 7, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.qc.team.type", "table_name": ""}
+{"text": "What operations can I perform on purchase.order.report?", "response": "To use the purchase.order.report model, you need to provide values for required fields: start_date, end_date. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.order.report", "table_name": ""}
+{"text": "Which fields in ks.message.wizard are computed?", "response": "The ks.message.wizard model is defined in module: ks_sales_forecast. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks.message.wizard", "table_name": ""}
+{"text": "What business logic is in x.report.wizard?", "response": "To use the x.report.wizard model, you need to provide values for required fields: pos_session_ids. Readonly fields: report_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "x.report.wizard", "table_name": ""}
+{"text": "What are the available fields for account.loan.line?", "response": "The account.loan.line model has 27 fields: name, loan_id, is_leasing, loan_type, loan_state, sequence, date, long_term_loan_account_id, currency_id, rate, pending_principal_amount, long_term_pending_principal_amount, payment_amount, interests_amount, principal_amount, long_term_principal_amount, final_pending_principal_amount, move_ids, has_moves, has_invoices, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 5, boolean: 3, selection: 2, integer: 2, date: 1, float: 1, monetary: 7, one2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.loan.line", "table_name": ""}
+{"text": "What foreign keys exist in base.language.import?", "response": "The base.language.import model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.language.import", "table_name": ""}
+{"text": "Describe the implementation of update.historical.data.", "response": "The update.historical.data model is defined in module: equip3_update_historical. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "update.historical.data", "table_name": ""}
+{"text": "Describe the field structure of product.warranty.", "response": "The product.warranty model has 30 fields: partner_id, phone, email, comment, accept1, product_id, serial_no, warranty_end_date, merchant, renew_no, warranty_create_date, product_serial_id, warranty_history_ids, warranty_type, warranty_team, tags_w, model_no, warranty_cost, warranty_claim_ids, warranty_sales_person, state, so_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, char: 6, text: 1, boolean: 1, date: 2, integer: 2, one2many: 2, selection: 2, many2many: 1, float: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.warranty", "table_name": ""}
+{"text": "What are the relationships in mailing.contact.subscription?", "response": "The mailing.contact.subscription model has 4 relational fields: contact_id -> mailing.contact; list_id -> mailing.list; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mailing.contact.subscription", "table_name": ""}
+{"text": "List all fields in the pos.order.line.promotion model.", "response": "The pos.order.line.promotion model has 15 fields: sequence, pos_order_line_id, promotion_id, promotion_disc, price, amount_percentage, amount, discount_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 4, float: 4, char: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.order.line.promotion", "table_name": ""}
+{"text": "How does report.point_of_sale.report_saledetails relate to other models?", "response": "The report.point_of_sale.report_saledetails model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.point_of_sale.report_saledetails", "table_name": ""}
+{"text": "What are the relationships in report.paperformat?", "response": "The report.paperformat model has 3 relational fields: report_ids -> ir.actions.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.paperformat", "table_name": ""}
+{"text": "Describe the field structure of base.language.import.", "response": "The base.language.import model has 12 fields: name, code, data, filename, overwrite, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, binary: 1, boolean: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.language.import", "table_name": ""}
+{"text": "How is sh.stock.move.qc.measurement used in the system?", "response": "The sh.stock.move.qc.measurement model represents Stock Move Measurement in the ERP system. It contains 12 fields and is used to manage stock move measurement data. Key fields include: product_id, quality_point_id, sh_measure, sh_message, picking_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.stock.move.qc.measurement", "table_name": ""}
+{"text": "What modules define advertisement.images?", "response": "The advertisement.images model is defined in module: equip3_pos_general. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "advertisement.images", "table_name": ""}
+{"text": "What data can be stored in list.top.product.compare?", "response": "The list.top.product.compare model has 10 fields: name, qty, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, float: 1, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "list.top.product.compare", "table_name": ""}
+{"text": "How do I use the sh.purchase.product.indent.wizard model?", "response": "To use the sh.purchase.product.indent.wizard model, you need to provide values for required fields: sh_start_date, sh_end_date, sh_partner_ids, sh_category_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.purchase.product.indent.wizard", "table_name": ""}
+{"text": "What does the pos.voucher model represent?", "response": "The pos.voucher model represents Management POS voucher in the ERP system. It contains 39 fields and is used to manage management pos voucher data. Key fields include: active, customer_id, code, start_date, end_date, state, value, apply_type, method, use_date, user_id, source, pos_order_id, pos_order_line_id, use_history_ids, number, maximum_discount_amount, minimum_purchase_amount, is_generate_voucher, generated_source_id, limit_restrict_product_ids, pos_category_ids, company_id, receipt_template_id, source_document_id, is_customize_sequence, sequence_generate_method, manual_input_sequence, running_number_prefix, running_number_digit, brand_ids, member_type_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.voucher", "table_name": ""}
+{"text": "List all fields in the mail.channel model.", "response": "The mail.channel model has 71 fields: name, active, is_chat, description, uuid, email_send, channel_last_seen_partner_ids, channel_partner_ids, channel_message_ids, is_member, public, group_public_id, group_ids, image_128, is_subscribed, moderation, moderator_ids, is_moderator, moderation_ids, moderation_count, moderation_notify, moderation_notify_msg, moderation_guidelines, moderation_guidelines_msg, subscription_department_ids, rating_ids, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, anonymous_name, channel_type, livechat_active, livechat_channel_id, livechat_operator_id, country_id, livechat_visitor_id, alias_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, alias_name, alias_model_id, alias_user_id, alias_defaults, alias_force_thread_id, alias_domain, alias_parent_model_id, alias_parent_thread_id, alias_bounced_content, alias_contact. Field types distribution: char: 6, boolean: 15, text: 5, one2many: 6, many2many: 7, selection: 3, many2one: 12, binary: 2, integer: 9, float: 2, datetime: 3, html: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.channel", "table_name": ""}
+{"text": "What are the technical details of cashback.line?", "response": "The cashback.line model is defined in module: equip3_sale_loyalty. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "cashback.line", "table_name": ""}
+{"text": "How is pos.payment.method.key used in the system?", "response": "The pos.payment.method.key model represents Pos Payment Method Key in the ERP system. It contains 10 fields and is used to manage pos payment method key data. Key fields include: shortcut_payment_method_ids, payment_method_id, key_journals, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.payment.method.key", "table_name": ""}
+{"text": "What business logic is in account.chart.template?", "response": "To use the account.chart.template model, you need to provide values for required fields: code_digits, currency_id, bank_account_code_prefix, cash_account_code_prefix, transfer_account_code_prefix, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.chart.template", "table_name": ""}
+{"text": "What modules define sh.purchase.report.representative.wizard?", "response": "The sh.purchase.report.representative.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.report.representative.wizard", "table_name": ""}
+{"text": "How do I use the customer.order.dic model?", "response": "To use the customer.order.dic 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "customer.order.dic", "table_name": ""}
+{"text": "What models are connected to report.layout?", "response": "The report.layout model has 3 relational fields: view_id -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.layout", "table_name": ""}
+{"text": "Show me the fields of product.ribbon.", "response": "The product.ribbon model has 11 fields: html, bg_color, text_color, html_class, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.ribbon", "table_name": ""}
+{"text": "What operations can I perform on mailing.list?", "response": "To use the mailing.list model, you need to provide values for required fields: name. Readonly fields: contact_nbr, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mailing.list", "table_name": ""}
+{"text": "Describe the implementation of apply.voucher.", "response": "The apply.voucher model is defined in module: equip3_sale_loyalty. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "apply.voucher", "table_name": ""}
+{"text": "Show me the relational structure of basemodel.extend.", "response": "The basemodel.extend model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "basemodel.extend", "table_name": ""}
+{"text": "What foreign keys exist in approval.matrix.purchase.order.line?", "response": "The approval.matrix.purchase.order.line model has 7 relational fields: user_ids -> res.users; approval_matrix_purchase_order -> approval.matrix.purchase.order; approved_users -> res.users; last_approved -> res.users; order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.purchase.order.line", "table_name": ""}
+{"text": "What modules define crm.phonecall?", "response": "The crm.phonecall model is defined in module: crm_phonecall. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.phonecall", "table_name": ""}
+{"text": "Describe the many2many relations for receipt.voucher.", "response": "The receipt.voucher model has 22 relational fields: create_by -> res.users; payment_ids -> account.payment; partner_id -> res.partner; partner_ids -> res.partner; bank_id -> account.journal; customer_invoice_ids -> account.move; currency_id -> res.currency; company_id -> res.company; branch_id -> res.branch; receipt_voucher_line_ids -> receipt.voucher.line; customer_allowed_ids -> account.move; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, customer_invoice_ids, customer_allowed_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "receipt.voucher", "table_name": ""}
+{"text": "Can you explain the purpose of report.eq_scrap_order_report.scrap_order_report?", "response": "The report.eq_scrap_order_report.scrap_order_report model represents report.eq_scrap_order_report.scrap_order_report in the ERP system. It contains 3 fields and is used to manage report.eq_scrap_order_report.scrap_order_report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.eq_scrap_order_report.scrap_order_report", "table_name": ""}
+{"text": "How to query report.sh_sale_reports.sh_salesperson_report_doc data?", "response": "To use the report.sh_sale_reports.sh_salesperson_report_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_salesperson_report_doc", "table_name": ""}
+{"text": "Describe the many2many relations for ir.actions.client.", "response": "The ir.actions.client model has 3 relational fields: binding_model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.actions.client", "table_name": ""}
+{"text": "What are the technical details of ir.demo_failure?", "response": "The ir.demo_failure model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.demo_failure", "table_name": ""}
+{"text": "What is the base_import.tests.models.char.states model?", "response": "The base_import.tests.models.char.states model represents Tests : Base Import Model, Character states in the ERP system. It contains 8 fields and is used to manage tests : base import model, character states data. Key fields include: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.char.states", "table_name": ""}
+{"text": "What fields does ir.qweb.field.image have?", "response": "The ir.qweb.field.image model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.image", "table_name": ""}
+{"text": "How is stock.lot.serialize used in the system?", "response": "The stock.lot.serialize model represents Stock Lot Serialize in the ERP system. It contains 9 fields and is used to manage stock lot serialize data. Key fields include: picking_id, stock_move_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.lot.serialize", "table_name": ""}
+{"text": "What are the available fields for sh.notification.logger?", "response": "The sh.notification.logger model has 12 fields: name, error, datetime, base_config_id, status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, datetime: 4, many2one: 3, selection: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.notification.logger", "table_name": ""}
+{"text": "Show me the relational structure of sh.purchase.analysis.wizard.", "response": "The sh.purchase.analysis.wizard model has 6 relational fields: sh_partner_ids -> res.partner; sh_product_ids -> product.product; company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_partner_ids, sh_product_ids, company_ids, branch_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.analysis.wizard", "table_name": ""}
+{"text": "What are the relationships in ks_to.do.description?", "response": "The ks_to.do.description model has 3 relational fields: ks_to_do_header_id -> ks_to.do.headers; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks_to.do.description", "table_name": ""}
+{"text": "What is the asset.asset.report model?", "response": "The asset.asset.report model represents Assets Analysis in the ERP system. It contains 21 fields and is used to manage assets analysis data. Key fields include: name, date, depreciation_date, asset_id, asset_category_id, partner_id, state, installment_value, move_check, installment_nbr, depreciation_nbr, gross_value, posted_value, unposted_value, company_id, depreciation_value, salvage_value, value_residual, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "asset.asset.report", "table_name": ""}
+{"text": "What is the sh.top.customers.xls model?", "response": "The sh.top.customers.xls model represents Top Customer XLS in the ERP system. It contains 9 fields and is used to manage top customer xls data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.top.customers.xls", "table_name": ""}
+{"text": "Show me the fields of blacklist.partner.wiz.", "response": "The blacklist.partner.wiz model has 11 fields: partner_id, user_id, type, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, selection: 1, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "blacklist.partner.wiz", "table_name": ""}
+{"text": "What modules define report.dynamic_accounts_report.general_ledger?", "response": "The report.dynamic_accounts_report.general_ledger model is defined in module: dynamic_accounts_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.dynamic_accounts_report.general_ledger", "table_name": ""}
+{"text": "Describe the order.picking.lines model in Odoo.", "response": "The order.picking.lines model represents Order Picking Lines in the ERP system. It contains 15 fields and is used to manage order picking lines data. Key fields include: order_id, product_id, quantity, unit_price, subtotal, picking_id, state, move_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "order.picking.lines", "table_name": ""}
+{"text": "What data can be stored in image.mixin?", "response": "The image.mixin model has 8 fields: image_1920, image_1024, image_512, image_256, image_128, id, display_name, __last_update. Field types distribution: binary: 5, integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "image.mixin", "table_name": ""}
+{"text": "Describe the implementation of stock.immediate.transfer.", "response": "The stock.immediate.transfer model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.immediate.transfer", "table_name": ""}
+{"text": "How is pos.remote.session implemented technically?", "response": "The pos.remote.session model is defined in module: equip3_pos_general. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.remote.session", "table_name": ""}
+{"text": "Describe the implementation of invoice.template.header.", "response": "The invoice.template.header model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.template.header", "table_name": ""}
+{"text": "Describe the implementation of payable.flow.wizard.", "response": "The payable.flow.wizard model is defined in module: equip3_accounting_flow. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "payable.flow.wizard", "table_name": ""}
+{"text": "What are the relationships in website.cover_properties.mixin?", "response": "The website.cover_properties.mixin model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.cover_properties.mixin", "table_name": ""}
+{"text": "Show me the fields of ks_dashboard_ninja.item.", "response": "The ks_dashboard_ninja.item model has 122 fields: name, ks_dashboard_board_template_id, ks_domain, ks_model_id_2, ks_model_name_2, ks_domain_temp, ks_background_color, ks_icon, ks_default_icon, ks_default_icon_color, ks_icon_select, ks_font_color, ks_dashboard_item_theme, ks_layout, ks_preview, ks_model_name, ks_record_count_type_2, ks_record_field_2, ks_record_count_2, ks_record_count_type, ks_record_count, ks_record_field, ks_record_data_limit_visibility, ks_isDateFilterApplied, ks_date_filter_selection, ks_date_filter_field, ks_item_start_date, ks_item_end_date, ks_date_filter_field_2, ks_item_start_date_2, ks_item_end_date_2, ks_domain_2, ks_domain_2_temp, ks_date_filter_selection_2, ks_previous_period, ks_dashboard_ninja_board_id, ks_dashboard_item_type, ks_chart_groupby_type, ks_chart_sub_groupby_type, ks_chart_relation_groupby, ks_chart_relation_sub_groupby, ks_chart_date_groupby, ks_chart_date_sub_groupby, ks_graph_preview, ks_chart_data, ks_chart_data_count_type, ks_chart_measure_field, ks_chart_cumulative_field, ks_chart_cumulative, ks_chart_measure_field_2, ks_bar_chart_stacked, ks_semi_circle_chart, ks_sort_by_field, ks_sort_by_order, ks_record_data_limit, ks_list_view_preview, ks_kpi_preview, ks_kpi_type, ks_target_view, ks_data_comparison, ks_kpi_data, ks_chart_item_color, ks_list_view_type, ks_list_view_fields, ks_export_all_records, ks_list_view_group_fields, ks_list_view_data, ks_company_id, ks_goal_enable, ks_goal_bar_line, ks_standard_goal_value, ks_goal_lines, ks_list_target_deviation_field, ks_many2many_field_ordering, ks_show_data_value, ks_action_lines, ks_actions, ks_compare_period, ks_year_period, ks_compare_period_2, ks_year_period_2, ks_multiplier_active, ks_multiplier, ks_update_items_data, ks_unit, ks_unit_selection, ks_chart_unit, ks_show_records, ks_fill_temporal, ks_domain_extension, ks_domain_extension_2, ks_hide_legend, ks_data_format, ks_button_color, ks_auto_update_type, ks_show_live_pop_up, ks_is_client_action, ks_client_action, ks_pagination_limit, ks_multiplier_lines, ks_precision_digits, ks_to_do_preview, ks_dn_header_lines, ks_to_do_data, ks_header_bg_color, ks_custom_query, ks_data_calculation_type, ks_query_result, ks_xlabels, ks_ylabels, ks_model_id, ks_list_view_layout, ks_is_date_ranges, ks_query_start_date, ks_query_end_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 35, many2one: 18, binary: 1, selection: 19, integer: 9, float: 4, boolean: 18, datetime: 9, many2many: 4, one2many: 4, text: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.item", "table_name": ""}
+{"text": "Show me the fields of report.fonts.", "response": "The report.fonts model has 11 fields: family, name, path, mode, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.fonts", "table_name": ""}
+{"text": "What are common use cases for pos.coupon.use.history?", "response": "To use the pos.coupon.use.history model, you need to provide values for required fields: coupon_id, used_date. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.coupon.use.history", "table_name": ""}
+{"text": "Show me the fields of report.accounting_pdf_reports.report_partnerledger.", "response": "The report.accounting_pdf_reports.report_partnerledger model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.accounting_pdf_reports.report_partnerledger", "table_name": ""}
+{"text": "What is the sh.mrp.allow.qc.measurement model?", "response": "The sh.mrp.allow.qc.measurement model represents Not Allow For Quality Check in the ERP system. It contains 11 fields and is used to manage not allow for quality check data. Key fields include: product_id, sh_message, sh_quality_point_id, mrp_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.mrp.allow.qc.measurement", "table_name": ""}
+{"text": "What data can be stored in report.sh_purchase_reports.sh_po_by_category_doc?", "response": "The report.sh_purchase_reports.sh_po_by_category_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_po_by_category_doc", "table_name": ""}
+{"text": "What methods are available in website.sale.extra.field?", "response": "The website.sale.extra.field model is defined in module: website_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.sale.extra.field", "table_name": ""}
+{"text": "What foreign keys exist in gamification.badge?", "response": "The gamification.badge model has 14 relational fields: rule_auth_user_ids -> res.users; rule_auth_badge_ids -> gamification.badge; challenge_ids -> gamification.challenge; goal_definition_ids -> gamification.goal.definition; owner_ids -> gamification.badge.user; unique_owner_ids -> res.users; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: rule_auth_user_ids, rule_auth_badge_ids, goal_definition_ids, unique_owner_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "gamification.badge", "table_name": ""}
+{"text": "How to create records in tax.sale.details.report?", "response": "To use the tax.sale.details.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "tax.sale.details.report", "table_name": ""}
+{"text": "Describe the field structure of pos.promotion.discount.category.", "response": "The pos.promotion.discount.category model has 17 fields: active, category_id, category_ids, discount, min_qty, discount2, multi_discount, promotion_id, discount_fixed_amount, max_discount_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 4, many2many: 1, float: 5, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.promotion.discount.category", "table_name": ""}
+{"text": "Which fields in purchase.custom.checklist.line are computed?", "response": "The purchase.custom.checklist.line model is defined in module: sh_all_in_one_purchase_tools. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.custom.checklist.line", "table_name": ""}
+{"text": "Which fields in stock.inventory.wizard.line are computed?", "response": "The stock.inventory.wizard.line model is defined in module: allfresh_mod_stock_count. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.inventory.wizard.line", "table_name": ""}
+{"text": "What are the relationships in qiscus.wa.template.content?", "response": "The qiscus.wa.template.content model has 3 relational fields: template_id -> qiscus.wa.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "qiscus.wa.template.content", "table_name": ""}
+{"text": "What fields does sale.order.option have?", "response": "The sale.order.option model has 18 fields: is_present, order_id, line_id, name, product_id, price_unit, discount, uom_id, product_uom_category_id, quantity, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 7, text: 1, float: 3, integer: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.order.option", "table_name": ""}
+{"text": "What business logic is in ir.exports?", "response": "To use the ir.exports 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.exports", "table_name": ""}
+{"text": "How do I use the ir.qweb.field.barcode model?", "response": "To use the ir.qweb.field.barcode model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.barcode", "table_name": ""}
+{"text": "What foreign keys exist in report.equip3_purchase_other_operation.report_analyze_quot?", "response": "The report.equip3_purchase_other_operation.report_analyze_quot model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_purchase_other_operation.report_analyze_quot", "table_name": ""}
+{"text": "What modules define voucher.matrix.reject?", "response": "The voucher.matrix.reject model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "voucher.matrix.reject", "table_name": ""}
+{"text": "What modules define fast.financial.report.query?", "response": "The fast.financial.report.query model is defined in module: fast_financial_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "fast.financial.report.query", "table_name": ""}
+{"text": "What is the snailmail.confirm.invoice model?", "response": "The snailmail.confirm.invoice model represents Snailmail Confirm Invoice in the ERP system. It contains 9 fields and is used to manage snailmail confirm invoice data. Key fields include: invoice_send_id, model_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "snailmail.confirm.invoice", "table_name": ""}
+{"text": "What are the relationships in account.edi.document?", "response": "The account.edi.document model has 5 relational fields: move_id -> account.move; edi_format_id -> account.edi.format; attachment_id -> ir.attachment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.edi.document", "table_name": ""}
+{"text": "What models are connected to purchase.request.line?", "response": "The purchase.request.line model has 35 relational fields: request_id -> purchase.request; company_id -> res.company; analytic_account_id -> account.analytic.account; requested_by -> res.users; assigned_to -> res.users; supplier_id -> res.partner; purchase_lines -> purchase.order.line; move_dest_ids -> stock.move; orderpoint_id -> stock.warehouse.orderpoint; purchase_request_allocation_ids -> purchase.request.allocation; currency_id -> res.currency; mr_line_id -> material.request.line; branch_id -> res.branch; assigned_to_partner_id -> res.partner; dest_loc_id -> stock.warehouse; picking_type_dest -> stock.picking.type; product_uom_id -> uom.uom; product_uom_category_id -> uom.category; analytic_account_group_ids -> account.analytic.tag; agreement_id -> purchase.agreement; tender_line_ids -> purchase.agreement.line; purchase_order_line_ids -> purchase.order.line; product_id -> product.product; merchendise_id -> merchendise.code; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_lines, analytic_account_group_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.request.line", "table_name": ""}
+{"text": "Describe the implementation of stock.picking.batch.validate.line.", "response": "The stock.picking.batch.validate.line model is defined in module: equip3_inventory_operations_countd. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.picking.batch.validate.line", "table_name": ""}
+{"text": "List all fields in the sh.announcement model.", "response": "The sh.announcement model has 24 fields: name, description, active, user_ids, font_color, background_color, date, is_animation, direction, simple_text, description_text, font_size, padding, font_family, google_font_family, is_popup_notification, notification_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, html: 1, boolean: 4, many2many: 1, date: 1, selection: 3, text: 1, integer: 2, float: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.announcement", "table_name": ""}
+{"text": "Show me the fields of acrux.chat.base.message.", "response": "The acrux.chat.base.message model has 7 fields: text, ttype, res_model, res_id, id, display_name, __last_update. Field types distribution: text: 1, selection: 1, char: 2, integer: 2, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "acrux.chat.base.message", "table_name": ""}
+{"text": "What models are connected to vendor.evaluation.rating?", "response": "The vendor.evaluation.rating model has 2 relational fields: partner_id -> res.partner; branch_id -> res.branch. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "vendor.evaluation.rating", "table_name": ""}
+{"text": "What are the available fields for sh.back.theme.config.settings?", "response": "The sh.back.theme.config.settings model has 89 fields: name, theme_color, theme_style, pre_theme_style, primary_color, primary_hover, primary_active, gradient_color, secondary_color, secondary_hover, secondary_active, header_background_color, header_font_color, header_hover_color, header_active_color, h1_color, h2_color, h3_color, h4_color, h5_color, h6_color, p_color, h1_size, h2_size, h3_size, h4_size, h5_size, h6_size, p_size, body_font_color, body_background_type, body_background_color, body_background_image, body_font_family, body_google_font_family, is_used_google_font, button_style, is_button_with_icon_text, is_button_with_box_shadow, separator_style, separator_color, sidebar_background_style, sidebar_background_image, sidebar_background_color, sidebar_font_color, sidebar_font_hover_color, sidebar_font_hover_background_color, sidebar_is_show_nav_bar, sidebar_collapse_style, loading_style, progress_style, progress_height, progress_color, loading_gif, loading_gif_file_name, list_view_border, list_view_is_hover_row, list_view_hover_bg_color, list_view_even_row_color, list_view_odd_row_color, login_page_style, login_page_background_type, login_page_background_color, login_page_background_image, login_page_box_color, login_page_banner_image, login_page_icon_img, login_page_icon_img_long, is_sticky_form, is_sticky_chatter, is_sticky_list, is_sticky_list_inside_form, icon_style, modal_popup_style, tab_style, tab_style_mobile, horizontal_tab_style, vertical_tab_style, form_element_style, search_style, breadcrumb_style, chatter_position, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 39, selection: 24, integer: 8, binary: 4, boolean: 9, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.back.theme.config.settings", "table_name": ""}
+{"text": "What are the available fields for credit.limit.approval?", "response": "The credit.limit.approval model has 19 fields: sequence, sequence2, user_ids, minimum_approver, status, time, feedback, approved, approval, user_approved_ids, credit_id, last_approved, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 5, many2many: 2, text: 2, char: 2, boolean: 1, many2one: 4, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "credit.limit.approval", "table_name": ""}
+{"text": "What modules define ir.qweb.field.many2one?", "response": "The ir.qweb.field.many2one model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.qweb.field.many2one", "table_name": ""}
+{"text": "What operations can I perform on account.common.partner.report?", "response": "To use the account.common.partner.report model, you need to provide values for required fields: result_selection, journal_ids, target_move, company_id. Readonly fields: result_selection, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.common.partner.report", "table_name": ""}
+{"text": "What are the relationships in replenishment.history.wizard?", "response": "The replenishment.history.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "replenishment.history.wizard", "table_name": ""}
+{"text": "What are the technical details of account.bank.statement.import.journal.creation?", "response": "The account.bank.statement.import.journal.creation model is defined in module: om_account_bank_statement_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.bank.statement.import.journal.creation", "table_name": ""}
+{"text": "How to create records in sh.qc.alert?", "response": "To use the sh.qc.alert model, you need to provide values for required fields: team_id, user_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.qc.alert", "table_name": ""}
+{"text": "What models are connected to sh.qc.measurement.line?", "response": "The sh.qc.measurement.line model has 5 relational fields: measurement_id -> sh.qc.measurement; product_id -> product.product; quality_point_id -> sh.qc.point; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.qc.measurement.line", "table_name": ""}
+{"text": "What data can be stored in ir.filters?", "response": "The ir.filters model has 16 fields: name, user_id, domain, context, sort, model_id, is_default, action_id, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, text: 3, selection: 1, boolean: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.filters", "table_name": ""}
+{"text": "What are the available fields for pos.coupon.generate.wizard?", "response": "The pos.coupon.generate.wizard model has 9 fields: no_of_coupon, coupon_program_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.coupon.generate.wizard", "table_name": ""}
+{"text": "What are the technical details of term.condition?", "response": "The term.condition model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "term.condition", "table_name": ""}
+{"text": "Describe the many2many relations for transfer.log.activity.", "response": "The transfer.log.activity model has 4 relational fields: reference -> stock.picking; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "transfer.log.activity", "table_name": ""}
+{"text": "What data can be stored in sh.purchase.bill.summary.xls?", "response": "The sh.purchase.bill.summary.xls model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.purchase.bill.summary.xls", "table_name": ""}
+{"text": "How do I use the base.partner.merge.line model?", "response": "To use the base.partner.merge.line model, you need to provide values for required fields: aggr_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.partner.merge.line", "table_name": ""}
+{"text": "Describe the many2many relations for crm.send.message.mass.", "response": "The crm.send.message.mass model has 5 relational fields: message_chat_ids -> acrux.chat.message.wizard; conversation_id -> acrux.chat.conversation; connector_id -> acrux.chat.connector; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.send.message.mass", "table_name": ""}
+{"text": "Show me the fields of receivable.opening.balance.", "response": "The receivable.opening.balance model has 14 fields: partner_opening_bal_id, customer_id, purchase_order, date, description, due_date, amount_due, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 3, date: 2, float: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "receivable.opening.balance", "table_name": ""}
+{"text": "What are the available fields for assembly.safety.stock?", "response": "The assembly.safety.stock model has 13 fields: name, company_id, is_branch_required, branch_id, warehouse_id, stock_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 5, boolean: 1, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "assembly.safety.stock", "table_name": ""}
+{"text": "Show me the fields of update.qty.", "response": "The update.qty model has 8 fields: sh_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "update.qty", "table_name": ""}
+{"text": "How does gamification.karma.tracking relate to other models?", "response": "The gamification.karma.tracking model has 3 relational fields: user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "gamification.karma.tracking", "table_name": ""}
+{"text": "Which fields in create.recurring.invoice are computed?", "response": "The create.recurring.invoice model is defined in module: contract_recurring_invoice_analytic. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "create.recurring.invoice", "table_name": ""}
+{"text": "How to query qiscus.wa.template.content data?", "response": "To use the qiscus.wa.template.content model, you need to provide values for required fields: none. Readonly fields: name, category, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "qiscus.wa.template.content", "table_name": ""}
+{"text": "What is the sh.mrp.pics model?", "response": "The sh.mrp.pics model represents MRP Quality Measurement Pictures in the ERP system. It contains 13 fields and is used to manage mrp quality measurement pictures data. Key fields include: product_id, sh_message, sh_quality_point_id, mrp_id, workorder_id, attachment_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.mrp.pics", "table_name": ""}
+{"text": "What operations can I perform on sh.purchase.analysis.wizard?", "response": "To use the sh.purchase.analysis.wizard model, you need to provide values for required fields: sh_start_date, sh_end_date, sh_partner_ids. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.purchase.analysis.wizard", "table_name": ""}
+{"text": "What modules define choose.delivery.carrier?", "response": "The choose.delivery.carrier model is defined in module: delivery. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "choose.delivery.carrier", "table_name": ""}
+{"text": "What data can be stored in account.payment.register?", "response": "The account.payment.register model has 73 fields: payment_date, amount, communication, group_payment, currency_id, journal_id, company_currency_id, line_ids, payment_type, partner_type, source_amount, source_amount_currency, source_currency_id, can_edit_wizard, can_group_payments, company_id, partner_id, payment_method_id, available_payment_method_ids, hide_payment_method, payment_difference, payment_difference_handling, writeoff_account_id, writeoff_label, show_partner_bank_account, require_partner_bank_account, country_code, is_prepayment, prepayment_journal_id, start_date, end_date, recurring_interval, recurring_interval_unit, stop_recurring_interval, stop_recurring_interval_unit, revenue_account, move_type, is_show_prepayment, payment_token_id, suitable_payment_token_partner_ids, payment_method_code, apply_manual_currency_exchange, manual_currency_exchange_rate, active_manual_currency_rate, receipt_approval_matrix_id, is_receipt_approval_matrix, difference_ids, payment_difference_amount, partner_bank_id, administration, analytic_group_ids, administration_account, administration_fee, current_rate_id, current_inverse_rate_id, is_same_main_currency, inverse_rate, estimasi_transfer, is_vendor_deposit, validated_move_ids, available_partner_bank_ids, pos_validate_file, pos_validate_filename, validate_data, validated_line_ids, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 4, monetary: 6, char: 7, boolean: 14, many2one: 17, many2many: 7, selection: 5, integer: 3, float: 4, one2many: 1, binary: 1, html: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.payment.register", "table_name": ""}
+{"text": "How do I use the pos.epson model?", "response": "To use the pos.epson model, you need to provide values for required fields: name, ip. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.epson", "table_name": ""}
+{"text": "What are the relationships in picking.order?", "response": "The picking.order model has 27 relational fields: delivery_boy -> res.partner; sale_order -> sale.order; invoice -> account.move; picking -> stock.picking; partner_id -> res.partner; pos_order_id -> pos.order; pos_partner_id -> res.partner; state_id -> res.country.state; country_id -> res.country; bank_statement_ids -> pos.payment; lines -> picking.order.line; session_id -> pos.session; cashier -> res.users; warehouse_id -> stock.warehouse; transaction_id -> payment.transaction; stage_id -> order.stage; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "picking.order", "table_name": ""}
+{"text": "Show me the fields of pos.report.journal.", "response": "The pos.report.journal model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.report.journal", "table_name": ""}
+{"text": "What fields does budget.budget have?", "response": "The budget.budget model has 31 fields: name, complete_name, parent_id, user_id, date_from, date_to, state, budget_budget_line, company_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 6, date: 2, selection: 1, one2many: 4, boolean: 5, many2many: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "budget.budget", "table_name": ""}
+{"text": "How is cust.credit.limit.data implemented technically?", "response": "The cust.credit.limit.data model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "cust.credit.limit.data", "table_name": ""}
+{"text": "Show me the relational structure of sms.cancel.", "response": "The sms.cancel model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sms.cancel", "table_name": ""}
+{"text": "What models are connected to hr.plan.activity.type?", "response": "The hr.plan.activity.type model has 4 relational fields: activity_type_id -> mail.activity.type; responsible_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hr.plan.activity.type", "table_name": ""}
+{"text": "How do I use the sale.order.repair model?", "response": "To use the sale.order.repair model, you need to provide values for required fields: none. Readonly fields: repair_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.repair", "table_name": ""}
+{"text": "What foreign keys exist in stock.quantity.history?", "response": "The stock.quantity.history model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.quantity.history", "table_name": ""}
+{"text": "What are the relationships in report.equip3_inventory_masterdata.report_product_tmpl_forecast?", "response": "The report.equip3_inventory_masterdata.report_product_tmpl_forecast model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_inventory_masterdata.report_product_tmpl_forecast", "table_name": ""}
+{"text": "Can you explain the purpose of base_import.tests.models.complex?", "response": "The base_import.tests.models.complex model represents Tests: Base Import Model Complex in the ERP system. It contains 13 fields and is used to manage tests: base import model complex data. Key fields include: f, m, c, currency_id, d, dt, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.complex", "table_name": ""}
+{"text": "Describe the implementation of payment.token.", "response": "The payment.token model is defined in module: payment. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "payment.token", "table_name": ""}
+{"text": "Show me the relational structure of stock.putaway.rule.", "response": "The stock.putaway.rule model has 8 relational fields: product_id -> product.product; location_in_id -> stock.location; location_out_id -> stock.location; company_id -> res.company; product_ids -> product.product; category_id -> product.category; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, category_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.putaway.rule", "table_name": ""}
+{"text": "What data can be stored in ai.model.selection.wizard?", "response": "The ai.model.selection.wizard model has 12 fields: config_id, provider, available_models_text, selected_model, error_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, selection: 1, text: 2, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ai.model.selection.wizard", "table_name": ""}
+{"text": "What are the available fields for product.sale.details.report?", "response": "The product.sale.details.report model has 15 fields: product_id, product_name, code, quantity, price_unit, discount, uom, details_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 4, float: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.sale.details.report", "table_name": ""}
+{"text": "What foreign keys exist in product.removal?", "response": "The product.removal model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.removal", "table_name": ""}
+{"text": "How is bi.product.pack implemented technically?", "response": "The bi.product.pack model is defined in module: dynamic_product_bundle. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "bi.product.pack", "table_name": ""}
+{"text": "Show me the relational structure of base_import.tests.models.char.", "response": "The base_import.tests.models.char model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.char", "table_name": ""}
+{"text": "How to query stock.scrap.request.matrix.reject data?", "response": "To use the stock.scrap.request.matrix.reject 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.scrap.request.matrix.reject", "table_name": ""}
+{"text": "Show me the fields of limit.request.", "response": "The limit.request model has 66 fields: name, partner_id, limit_type, limit_type_old, limit_type_new, credit_amount, last_credit_limit, open_inv_no, last_open_inv_no, new_max_invoice, last_max_invoice, description, state, state1, state2, branch_id, limit_approval_matrix, approval_ids, approval_matrix_line_id, user_approval_ids, current_user, approval, approval2, new_amount, last_amount, is_approve_button, user_id, is_credit_limit_brand, product_brand_ids, brand_ids, company_id, 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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 15, selection: 8, float: 8, text: 1, one2many: 6, many2many: 4, boolean: 9, date: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "limit.request", "table_name": ""}
+{"text": "How does report.equip3_pos_report.report_closed_session relate to other models?", "response": "The report.equip3_pos_report.report_closed_session model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_pos_report.report_closed_session", "table_name": ""}
+{"text": "How is do.matrix.reject implemented technically?", "response": "The do.matrix.reject model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "do.matrix.reject", "table_name": ""}
+{"text": "What business logic is in sh.stock.move.global.check?", "response": "To use the sh.stock.move.global.check model, you need to provide values for required fields: none. Readonly fields: product_id, sh_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.stock.move.global.check", "table_name": ""}
+{"text": "List all fields in the report.excel.section model.", "response": "The report.excel.section model has 31 fields: sequence, name, report_excel_id, parent_id, children_ids, report_id, report_excel_param_content, type_data, level, report_excel_fields_ids, root_model_related_field_id, root_model_id, root_model_name, check_root_model, section, section_level, section_start, section_end, sql_bool, sql_statement, report_excel_fields_sql_ids, domain, archive_bool, description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 5, char: 6, many2one: 6, one2many: 3, selection: 2, boolean: 4, text: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.excel.section", "table_name": ""}
+{"text": "Describe the implementation of sh.purchase.analysis.wizard.", "response": "The sh.purchase.analysis.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.analysis.wizard", "table_name": ""}
+{"text": "Describe the sh.purchase.update.mass.tag.wizard model in Odoo.", "response": "The sh.purchase.update.mass.tag.wizard model represents Mass Tag Update Wizard in the ERP system. It contains 10 fields and is used to manage mass tag update wizard data. Key fields include: purchase_order_ids, wiz_tag_ids, update_method, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.purchase.update.mass.tag.wizard", "table_name": ""}
+{"text": "List all fields in the pos.voucher.report model.", "response": "The pos.voucher.report model has 14 fields: name, used_date, number, code, pos_order_id, config_id, session_id, apply_type, amount, pos_branch_id, company_id, id, display_name, __last_update. Field types distribution: char: 4, datetime: 2, many2one: 5, selection: 1, float: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.voucher.report", "table_name": ""}
+{"text": "Describe the implementation of warehouse.capacity.report.", "response": "The warehouse.capacity.report model is defined in module: equip3_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "warehouse.capacity.report", "table_name": ""}
+{"text": "What data can be stored in pos.generate.efaktur.digunggung?", "response": "The pos.generate.efaktur.digunggung model has 14 fields: gen_efaktur_id, partner_id, account_move_id, account_move_data, no_of_invoice, amount_total, l10n_id_tax_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, text: 1, integer: 2, float: 1, char: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.generate.efaktur.digunggung", "table_name": ""}
+{"text": "Describe the many2many relations for stock.scheduler.compute.", "response": "The stock.scheduler.compute model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.scheduler.compute", "table_name": ""}
+{"text": "What are the available fields for blanket.approval.matrix?", "response": "The blanket.approval.matrix model has 45 fields: name, company_id, branch_id, config, minimum_amt, maximum_amt, approver_matrix_line_ids, 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. Field types distribution: char: 7, many2one: 10, selection: 3, float: 2, one2many: 5, date: 2, boolean: 5, many2many: 2, integer: 5, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "blanket.approval.matrix", "table_name": ""}
+{"text": "Describe the void.order.line model in Odoo.", "response": "The void.order.line model represents void.order.line in the ERP system. It contains 12 fields and is used to manage void.order.line data. Key fields include: name, session_id, order_id, void_uid, cashier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "void.order.line", "table_name": ""}
+{"text": "What models are connected to wizard.quotation.agreement?", "response": "The wizard.quotation.agreement model has 5 relational fields: agreement_id -> purchase.agreement; partner_ids -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "wizard.quotation.agreement", "table_name": ""}
+{"text": "What are the relationships in pos.promotion?", "response": "The pos.promotion model has 34 relational fields: product_id -> product.product; discount_order_ids -> pos.promotion.discount.order; discount_category_ids -> pos.promotion.discount.category; discount_quantity_ids -> pos.promotion.discount.quantity; gift_condition_ids -> pos.promotion.gift.condition; gift_free_ids -> pos.promotion.gift.free; discount_condition_ids -> pos.promotion.discount.condition; discount_apply_ids -> pos.promotion.discount.apply; multilevel_condition_ids -> pos.promotion.multilevel.condition; multilevel_gift_ids -> pos.promotion.multilevel.gift; price_ids -> pos.promotion.price; special_category_ids -> pos.promotion.special.category; multi_buy_ids -> pos.promotion.multi.buy; promotion_specific_product_ids -> pos.promotion.specific.product; tebus_murah_product_ids -> pos.promotion.tebus.murah; product_ids -> product.product; special_customer_ids -> res.partner; promotion_group_ids -> res.partner.group; pos_branch_ids -> res.branch; payment_method_ids -> pos.payment.method; pos_apply -> pos.config; card_payment_id -> card.payment; card_payment_ids -> card.payment; branch_id -> res.branch; promotion_based_on_brand_ids -> pos.promotion.selected.brand; tebus_murah_selected_brand_ids -> pos.promotion.tebus.murah.selected.brand; tebus_murah_brand_ids -> product.brand; promotion_product_discount_id -> product.product; company_id -> res.company; currency_id -> res.currency; pos_loyalty_category_ids -> pos.loyalty.category; pos_branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, special_customer_ids, promotion_group_ids, pos_branch_ids, payment_method_ids, pos_apply, card_payment_ids, tebus_murah_brand_ids, pos_loyalty_category_ids, pos_branch_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.promotion", "table_name": ""}
+{"text": "Which fields in account.open.chart are computed?", "response": "The account.open.chart model is defined in module: account_parent. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.open.chart", "table_name": ""}
+{"text": "What fields does approval.matrix.purchase.request have?", "response": "The approval.matrix.purchase.request model has 48 fields: name, company_id, branch_id, department_id, minimum_amt, maximum_amt, is_purchase_request_department, approval_matrix_purchase_request_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. Field types distribution: char: 7, many2one: 11, float: 2, boolean: 7, one2many: 5, selection: 3, date: 2, many2many: 2, integer: 5, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.purchase.request", "table_name": ""}
+{"text": "What are the available fields for ai.chat.session?", "response": "The ai.chat.session model has 34 fields: name, user_id, config_id, state, session_summary, session_summary_message_count, session_summary_last_updated, auto_compress_enabled, compression_threshold, trim_ratio, message_count, last_activity, total_tokens_used, last_tokens_used, message_ids, job_ids, last_job_id, has_running_job, is_ai_renamed, is_quick_chat, quick_chat_model, quick_chat_res_id, cached_user_message_hash, cached_relevant_memories, cached_system_prompt, thinking_chain, last_frequent_actions_query, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 5, selection: 1, text: 5, integer: 7, datetime: 5, boolean: 4, float: 1, one2many: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ai.chat.session", "table_name": ""}
+{"text": "What modules define pos.pack.operation.lot?", "response": "The pos.pack.operation.lot model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.pack.operation.lot", "table_name": ""}
+{"text": "Describe the kpi.measure.item model in Odoo.", "response": "The kpi.measure.item model represents KPI Measurement (Variable) in the ERP system. It contains 20 fields and is used to manage kpi measurement (variable) data. Key fields include: name, measure_id, domain, model_id, model_name, measure_type, company_id, active, description, sequence, existing_kpi, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kpi.measure.item", "table_name": ""}
+{"text": "What methods are available in sh.qc.alert.tags?", "response": "The sh.qc.alert.tags model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.qc.alert.tags", "table_name": ""}
+{"text": "Show me the relational structure of account.day.book.", "response": "The account.day.book model has 5 relational fields: company_id -> res.company; journal_ids -> account.journal; account_ids -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: journal_ids, account_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.day.book", "table_name": ""}
+{"text": "List all fields in the sale.order.option model.", "response": "The sale.order.option model has 18 fields: is_present, order_id, line_id, name, product_id, price_unit, discount, uom_id, product_uom_category_id, quantity, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 7, text: 1, float: 3, integer: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.order.option", "table_name": ""}
+{"text": "What models are connected to opening.balance?", "response": "The opening.balance model has 6 relational fields: company_id -> res.company; journal_id -> account.journal; partner_id -> res.partner; line_ids -> opening.balance.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "opening.balance", "table_name": ""}
+{"text": "Tell me about the pos.details.wizard model.", "response": "The pos.details.wizard model represents Point of Sale Details Report in the ERP system. It contains 10 fields and is used to manage point of sale details report data. Key fields include: start_date, end_date, pos_config_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.details.wizard", "table_name": ""}
+{"text": "Show me the fields of product.pricelist.history.", "response": "The product.pricelist.history model has 25 fields: pricelist_id, logdate, user_id, name, method, description, old_value_text, new_value_text, category_id, product_tmpl_id, product_id, uom_id, model, pl_id, pricelist_item_id, company_id, currency_id, is_seen, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 11, datetime: 4, char: 7, integer: 2, boolean: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.pricelist.history", "table_name": ""}
+{"text": "Describe the implementation of res.currency.", "response": "The res.currency model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.currency", "table_name": ""}
+{"text": "What models are connected to mail.followers?", "response": "The mail.followers model has 3 relational fields: partner_id -> res.partner; channel_id -> mail.channel; subtype_ids -> mail.message.subtype. Many2many fields: subtype_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.followers", "table_name": ""}
+{"text": "Tell me about the blanket.quotation.line model.", "response": "The blanket.quotation.line model represents blanket.quotation.line in the ERP system. It contains 19 fields and is used to manage blanket.quotation.line data. Key fields include: bq_id, product_id, vendor_id, remaining_quantity, new_quatation_quantity, blanket_order_line_id, unit_of_measure_id, unit_price, subtotal, is_goods_orders, is_services_orders, is_assets_orders, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "blanket.quotation.line", "table_name": ""}
+{"text": "Describe the implementation of pos.session.", "response": "The pos.session model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.session", "table_name": ""}
+{"text": "What are the available fields for report.dynamic_accounts_report.balance_sheet?", "response": "The report.dynamic_accounts_report.balance_sheet model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.dynamic_accounts_report.balance_sheet", "table_name": ""}
+{"text": "What data can be stored in account.tax.map.sales.line?", "response": "The account.tax.map.sales.line model has 17 fields: company_id, sales_tax_id, target_company, target_sales_tax, map_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, line_ids, child_company_id, ownership, sales_line_ids, purchase_line_ids. Field types distribution: many2one: 8, integer: 1, char: 1, datetime: 3, one2many: 3, float: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.tax.map.sales.line", "table_name": ""}
+{"text": "Can you explain the purpose of global.search?", "response": "The global.search model represents Global Search in the ERP system. It contains 11 fields and is used to manage global search data. Key fields include: model_id, field_ids, main_field_id, global_field_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "global.search", "table_name": ""}
+{"text": "What business logic is in sh.target.commision?", "response": "To use the sh.target.commision model, you need to provide values for required fields: company_id, user_id, commision_calculator, from_date, to_date, target_on, main_traget, target_based_on, target_based_on1, target_based_on2. Readonly fields: achieved_sales_target, achieved_collection_target, remaining_sales_target, remaining_collection_target, sales_target_achieved, bill_count, bill_ids, name, collection_target_achieved, deduction, current_achievement, current_commission, curr_achieve, target_left, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.target.commision", "table_name": ""}
+{"text": "What does the coupon.reward model represent?", "response": "The coupon.reward model represents Coupon Reward in the ERP system. It contains 19 fields and is used to manage coupon reward data. Key fields include: reward_description, reward_product_id, reward_product_quantity, discount_type, discount_percentage, discount_apply_on, discount_specific_product_ids, discount_max_amount, discount_fixed_amount, reward_product_uom_id, discount_line_product_id, reward_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "coupon.reward", "table_name": ""}
+{"text": "What business logic is in account.group?", "response": "To use the account.group model, you need to provide values for required fields: company_id, name. Readonly fields: parent_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.group", "table_name": ""}
+{"text": "What are the relationships in product.pricelist.history?", "response": "The product.pricelist.history model has 11 relational fields: pricelist_id -> product.pricelist; user_id -> res.users; category_id -> product.category; product_tmpl_id -> product.template; product_id -> product.product; uom_id -> uom.uom; pricelist_item_id -> product.pricelist.item; company_id -> res.company; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.pricelist.history", "table_name": ""}
+{"text": "What data can be stored in basemodel.extend?", "response": "The basemodel.extend model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "basemodel.extend", "table_name": ""}
+{"text": "What modules define global.search.fields?", "response": "The global.search.fields model is defined in module: sh_backmate_theme_adv. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "global.search.fields", "table_name": ""}
+{"text": "Tell me about the report.mrp.report_bom_structure model.", "response": "The report.mrp.report_bom_structure model represents BOM Structure Report in the ERP system. It contains 3 fields and is used to manage bom structure report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.mrp.report_bom_structure", "table_name": ""}
+{"text": "What does the account.trial.balance model represent?", "response": "The account.trial.balance model represents Trial Balance Report in the ERP system. It contains 16 fields and is used to manage trial balance report data. Key fields include: journal_ids, display_account, consolidate, all_account, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.trial.balance", "table_name": ""}
+{"text": "How is stock.quantity.history used in the system?", "response": "The stock.quantity.history model represents Stock Quantity History in the ERP system. It contains 8 fields and is used to manage stock quantity history data. Key fields include: inventory_datetime, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.quantity.history", "table_name": ""}
+{"text": "Describe the res.currency.tax model in Odoo.", "response": "The res.currency.tax model represents Currency Tax Rate in the ERP system. It contains 13 fields and is used to manage currency tax rate data. Key fields include: name, rate, conversion, mr_rate, currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.currency.tax", "table_name": ""}
+{"text": "Which fields in barcode.rule are computed?", "response": "The barcode.rule model is defined in module: barcodes. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "barcode.rule", "table_name": ""}
+{"text": "What are the relationships in ir.module.module.exclusion?", "response": "The ir.module.module.exclusion model has 4 relational fields: module_id -> ir.module.module; exclusion_id -> ir.module.module; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.module.module.exclusion", "table_name": ""}
+{"text": "What foreign keys exist in purchase.agreement.line?", "response": "The purchase.agreement.line model has 12 relational fields: agreement_id -> purchase.agreement; company_id -> res.company; sh_product_uom_id -> uom.uom; product_uom_category_id -> uom.category; analytic_tag_ids -> account.analytic.tag; dest_warehouse_id -> stock.warehouse; picking_type_id -> stock.picking.type; request_line_id -> purchase.request.line; branch_id -> res.branch; sh_product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.agreement.line", "table_name": ""}
+{"text": "Which fields in queue.jobs.to.done are computed?", "response": "The queue.jobs.to.done model is defined in module: queue_job. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "queue.jobs.to.done", "table_name": ""}
+{"text": "How does ir.qweb.field.float relate to other models?", "response": "The ir.qweb.field.float model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.qweb.field.float", "table_name": ""}
+{"text": "What models are connected to mrp.immediate.production.line?", "response": "The mrp.immediate.production.line model has 4 relational fields: immediate_production_id -> mrp.immediate.production; production_id -> mrp.production; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.immediate.production.line", "table_name": ""}
+{"text": "What models are connected to stock.life?", "response": "The stock.life model has 6 relational fields: product_ids -> product.product; category_ids -> product.category; is_customer -> res.partner; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, category_ids, branch_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.life", "table_name": ""}
+{"text": "What models are connected to hour.group?", "response": "The hour.group model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hour.group", "table_name": ""}
+{"text": "How is sh.tsp.top.purchasing.product used in the system?", "response": "The sh.tsp.top.purchasing.product model represents Top purchasing product persistence model to  used in snippet or any other places in the ERP system. It contains 9 fields and is used to manage top purchasing product persistence model to  used in snippet or any other places data. Key fields include: product_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.tsp.top.purchasing.product", "table_name": ""}
+{"text": "What operations can I perform on sh.sale.product.indent.wizard?", "response": "To use the sh.sale.product.indent.wizard model, you need to provide values for required fields: sh_end_date, sh_partner_ids, sh_category_ids, sh_start_date. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.sale.product.indent.wizard", "table_name": ""}
+{"text": "Show me the relational structure of receipt.payment.line.credit.", "response": "The receipt.payment.line.credit model has 7 relational fields: line_id -> receipt.payment; currency_id -> res.currency; invoice_id -> account.move; account_id -> account.account; payment_id -> account.payment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "receipt.payment.line.credit", "table_name": ""}
+{"text": "What are common use cases for mail.channel?", "response": "To use the mail.channel model, you need to provide values for required fields: name, public, alias_id, alias_model_id, alias_defaults, alias_contact. Readonly fields: is_chat, is_member, is_subscribed, is_moderator, moderation_count, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, alias_domain. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.channel", "table_name": ""}
+{"text": "Show me the relational structure of stock.quant.", "response": "The stock.quant model has 18 relational fields: product_id -> product.product; product_tmpl_id -> product.template; product_uom_id -> uom.uom; company_id -> res.company; location_id -> stock.location; lot_id -> stock.production.lot; package_id -> stock.quant.package; owner_id -> res.partner; currency_id -> res.currency; move_id -> stock.move; analytic_account_group_ids -> account.analytic.tag; filter_available_product_ids -> product.product; product_category -> product.category; warehouse_id -> stock.warehouse; inv_report_ref -> uom.category; inv_report_sec -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_account_group_ids, filter_available_product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.quant", "table_name": ""}
+{"text": "What methods are available in pos.promotion.specific.product?", "response": "The pos.promotion.specific.product model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.promotion.specific.product", "table_name": ""}
+{"text": "How does account.fiscal.position.tax relate to other models?", "response": "The account.fiscal.position.tax model has 6 relational fields: position_id -> account.fiscal.position; company_id -> res.company; tax_src_id -> account.tax; tax_dest_id -> account.tax; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.fiscal.position.tax", "table_name": ""}
+{"text": "What are the technical details of report.dynamic_accounts_report.day_book?", "response": "The report.dynamic_accounts_report.day_book model is defined in module: dynamic_accounts_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.dynamic_accounts_report.day_book", "table_name": ""}
+{"text": "How to create records in mail.thread?", "response": "To use the mail.thread model, you need to provide values for required fields: none. Readonly fields: message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.thread", "table_name": ""}
+{"text": "Show me the relational structure of choose.delivery.carrier.", "response": "The choose.delivery.carrier model has 8 relational fields: order_id -> sale.order; partner_id -> res.partner; carrier_id -> delivery.carrier; currency_id -> res.currency; company_id -> res.company; available_carrier_ids -> delivery.carrier; create_uid -> res.users; write_uid -> res.users. Many2many fields: available_carrier_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "choose.delivery.carrier", "table_name": ""}
+{"text": "Show me the fields of all.loyalty.history.", "response": "The all.loyalty.history model has 19 fields: order_id, pos_order_id, partner_id, date, generated_from, transaction_type, points, amount, currency_id, company_id, check_state, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, datetime: 4, selection: 3, integer: 2, char: 2, boolean: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "all.loyalty.history", "table_name": ""}
+{"text": "How does hr.employee.category relate to other models?", "response": "The hr.employee.category model has 3 relational fields: employee_ids -> hr.employee; create_uid -> res.users; write_uid -> res.users. Many2many fields: employee_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hr.employee.category", "table_name": ""}
+{"text": "How is sms.resend.recipient implemented technically?", "response": "The sms.resend.recipient model is defined in module: sms. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sms.resend.recipient", "table_name": ""}
+{"text": "What models are connected to multi.receipt.matrix.reject?", "response": "The multi.receipt.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "multi.receipt.matrix.reject", "table_name": ""}
+{"text": "How to query wizard.ir.model.menu.create data?", "response": "To use the wizard.ir.model.menu.create model, you need to provide values for required fields: menu_id, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "wizard.ir.model.menu.create", "table_name": ""}
+{"text": "How do I use the pos.sale.report model?", "response": "To use the pos.sale.report model, you need to provide values for required fields: none. Readonly fields: report_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.sale.report", "table_name": ""}
+{"text": "What operations can I perform on wizard.quotation.agreement?", "response": "To use the wizard.quotation.agreement 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "wizard.quotation.agreement", "table_name": ""}
+{"text": "Show me the relational structure of website.sale.payment.acquirer.onboarding.wizard.", "response": "The website.sale.payment.acquirer.onboarding.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.sale.payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "What data can be stored in account.invoice.exchange.approval.wizard?", "response": "The account.invoice.exchange.approval.wizard model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.invoice.exchange.approval.wizard", "table_name": ""}
+{"text": "Describe the portal.share model in Odoo.", "response": "The portal.share model represents Portal Sharing in the ERP system. It contains 13 fields and is used to manage portal sharing data. Key fields include: res_model, res_id, partner_ids, note, share_link, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "portal.share", "table_name": ""}
+{"text": "Describe the many2many relations for purchase.agreement.approval.matrix.", "response": "The purchase.agreement.approval.matrix model has 17 relational fields: company_id -> res.company; branch_id -> res.branch; approval_matrix_purchase_agreement_line_ids -> approval.matrix.purchase.agreement.line; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.agreement.approval.matrix", "table_name": ""}
+{"text": "Which fields in limit.approval.matrix.sale.reject are computed?", "response": "The limit.approval.matrix.sale.reject model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "limit.approval.matrix.sale.reject", "table_name": ""}
+{"text": "What operations can I perform on purchase.down.payment?", "response": "To use the purchase.down.payment model, you need to provide values for required fields: none. Readonly fields: is_service_work_order, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.down.payment", "table_name": ""}
+{"text": "How is split.pr.wizard implemented technically?", "response": "The split.pr.wizard model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "split.pr.wizard", "table_name": ""}
+{"text": "Tell me about the customer.deposit.report model.", "response": "The customer.deposit.report model represents Customer Deposit Report in the ERP system. It contains 16 fields and is used to manage customer deposit report data. Key fields include: name, partner_id, amount, currency_id, remaining_amount, communication, move_id, return_deposit, payment_date, deposit_reconcile_journal_id, journal_id, deposit_account_id, used_amount, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "customer.deposit.report", "table_name": ""}
+{"text": "How does sh.sale.category.xls relate to other models?", "response": "The sh.sale.category.xls model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.sale.category.xls", "table_name": ""}
+{"text": "What methods are available in ir.logging?", "response": "The ir.logging model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.logging", "table_name": ""}
+{"text": "What are the technical details of sale.adv.settings?", "response": "The sale.adv.settings model is defined in module: equip3_sale_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.adv.settings", "table_name": ""}
+{"text": "What are the available fields for report_excel_wizard?", "response": "The report_excel_wizard model has 11 fields: report_conf, report_name, report_description, data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 2, text: 1, serialized: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report_excel_wizard", "table_name": ""}
+{"text": "What does the cash.box.out model represent?", "response": "The cash.box.out model represents Cash Box Out in the ERP system. It contains 9 fields and is used to manage cash box out data. Key fields include: amount, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "cash.box.out", "table_name": ""}
+{"text": "What business logic is in pos.product.bom?", "response": "To use the pos.product.bom model, you need to provide values for required fields: product_id, product_qty, product_uom_id. Readonly fields: name, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.product.bom", "table_name": ""}
+{"text": "What business logic is in approval.matrix.sale.order?", "response": "To use the approval.matrix.sale.order model, you need to provide values for required fields: name, company_id, branch_id, config, minimum_amt, maximum_amt. Readonly fields: company_id, description, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.sale.order", "table_name": ""}
+{"text": "What business logic is in sh.sale.report.salesperson.wizard?", "response": "To use the sh.sale.report.salesperson.wizard model, you need to provide values for required fields: date_start, date_end. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.sale.report.salesperson.wizard", "table_name": ""}
+{"text": "What are the technical details of pos.cash.in.out?", "response": "The pos.cash.in.out model is defined in module: equip3_pos_cashbox. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.cash.in.out", "table_name": ""}
+{"text": "How to query mrp.production data?", "response": "To use the mrp.production model, you need to provide values for required fields: product_id, product_qty, product_uom_id, picking_type_id, location_src_id, location_dest_id, date_planned_start, company_id, consumption. Readonly fields: name, product_id, product_tracking, allowed_product_ids, product_tmpl_id, product_qty, product_uom_id, product_uom_category_id, product_uom_qty, use_create_components_lots, location_src_id, location_dest_id, date_deadline, date_start, date_finished, bom_id, state, reservation_state, workorder_done_count, unreserve_visible, reserve_visible, qty_produced, delay_alert_date, json_popover, scrap_count, is_planned, show_final_lots, production_location_id, picking_ids, delivery_count, confirm_cancel, consumption, mrp_production_child_count, mrp_production_source_count, mrp_production_backorder_count, show_lock, components_availability, components_availability_state, show_lot_ids, show_valuation, sh_mrp_quality_check_ids_nbr, pending_qc, qc_fail, qc_pass, is_mandatory, qc_count, qc_alert_count, purchase_order_count, sale_order_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mrp.production", "table_name": ""}
+{"text": "Show me the relational structure of account.reconcile.model.line.template.", "response": "The account.reconcile.model.line.template model has 5 relational fields: model_id -> account.reconcile.model.template; account_id -> account.account.template; tax_ids -> account.tax.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: tax_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.reconcile.model.line.template", "table_name": ""}
+{"text": "Describe the report.sh_purchase_reports.sh_vend_po_analysis_doc model in Odoo.", "response": "The report.sh_purchase_reports.sh_vend_po_analysis_doc model represents Vendor Purchase Analysis report abstract model in the ERP system. It contains 3 fields and is used to manage vendor purchase analysis report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_vend_po_analysis_doc", "table_name": ""}
+{"text": "What modules define credit.limit.approval?", "response": "The credit.limit.approval model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "credit.limit.approval", "table_name": ""}
+{"text": "What data can be stored in account.day.book?", "response": "The account.day.book model has 13 fields: company_id, journal_ids, account_ids, date_from, date_to, target_move, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 2, date: 2, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.day.book", "table_name": ""}
+{"text": "List all fields in the project.task.type.delete.wizard model.", "response": "The project.task.type.delete.wizard model has 11 fields: project_ids, stage_ids, tasks_count, stages_active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, integer: 2, boolean: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.task.type.delete.wizard", "table_name": ""}
+{"text": "What data can be stored in utm.campaign?", "response": "The utm.campaign model has 26 fields: name, user_id, stage_id, tag_ids, is_website, color, click_count, use_leads, crm_lead_count, mailing_mail_ids, mailing_mail_count, received_ratio, opened_ratio, replied_ratio, bounced_ratio, quotation_count, invoiced_amount, company_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 6, many2many: 1, boolean: 2, integer: 11, one2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "utm.campaign", "table_name": ""}
+{"text": "How does sh.base.send.whatsapp.number.wizard relate to other models?", "response": "The sh.base.send.whatsapp.number.wizard model has 4 relational fields: partner_ids -> res.partner; crm_lead_id -> crm.lead; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.base.send.whatsapp.number.wizard", "table_name": ""}
+{"text": "List all fields in the report.sh_sale_reports.sh_payment_report_doc model.", "response": "The report.sh_sale_reports.sh_payment_report_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_sale_reports.sh_payment_report_doc", "table_name": ""}
+{"text": "How do I use the res.partner.rfm.segment.history model?", "response": "To use the res.partner.rfm.segment.history 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.partner.rfm.segment.history", "table_name": ""}
+{"text": "Show me the fields of pos.sync.session.log.", "response": "The pos.sync.session.log model has 17 fields: order_uid, create_date, send_from_session_id, send_to_session_id, user_id, user_receive_id, action, logs, state, branch_id, company_id, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: char: 2, datetime: 3, many2one: 8, selection: 2, text: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.sync.session.log", "table_name": ""}
+{"text": "Describe the field structure of setu.inventory.outofstock.report.", "response": "The setu.inventory.outofstock.report model has 16 fields: advance_stock_days, stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, binary: 1, date: 2, many2many: 4, many2one: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.outofstock.report", "table_name": ""}
+{"text": "Can you explain the purpose of hide.filters.groups?", "response": "The hide.filters.groups model represents Hide Filters Groups in the ERP system. It contains 14 fields and is used to manage hide filters groups data. Key fields include: model_id, model_name, filters_store_model_nodes_ids, groups_store_model_nodes_ids, access_management_id, restrict_custom_filter, restrict_custom_group, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "hide.filters.groups", "table_name": ""}
+{"text": "What modules define expiring.product.calendar?", "response": "The expiring.product.calendar model is defined in module: equip3_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "expiring.product.calendar", "table_name": ""}
+{"text": "What operations can I perform on currency.log.api?", "response": "To use the currency.log.api 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "currency.log.api", "table_name": ""}
+{"text": "What are common use cases for project.tags?", "response": "To use the project.tags 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.tags", "table_name": ""}
+{"text": "What are the technical details of budget.purchase.lines?", "response": "The budget.purchase.lines model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "budget.purchase.lines", "table_name": ""}
+{"text": "Describe the ir.actions.act_url model in Odoo.", "response": "The ir.actions.act_url model represents Action URL in the ERP system. It contains 16 fields and is used to manage action url data. Key fields include: name, type, url, target, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.act_url", "table_name": ""}
+{"text": "What modules define report.accounting_pdf_reports.report_partnerledger?", "response": "The report.accounting_pdf_reports.report_partnerledger model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.accounting_pdf_reports.report_partnerledger", "table_name": ""}
+{"text": "What foreign keys exist in sale.order.template.line?", "response": "The sale.order.template.line model has 7 relational fields: sale_order_template_id -> sale.order.template; company_id -> res.company; product_id -> product.product; product_uom_id -> uom.uom; product_uom_category_id -> uom.category; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.template.line", "table_name": ""}
+{"text": "What foreign keys exist in setu.inventory.turnover.analysis.report?", "response": "The setu.inventory.turnover.analysis.report model has 7 relational fields: product_category_ids -> product.category; product_ids -> product.product; warehouse_ids -> stock.warehouse; company_id -> res.company; company_ids -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_category_ids, product_ids, warehouse_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.turnover.analysis.report", "table_name": ""}
+{"text": "List all fields in the product.packaging model.", "response": "The product.packaging model has 33 fields: name, sequence, qty, barcode, product_uom_id, company_id, height, width, packaging_length, max_weight, shipper_package_code, package_carrier_type, weight_uom_name, length_uom_name, product_id, maximum_height, maximum_length, maximum_width, maximum_volume, packages_barcode_prefix, digits, current_sequence, filter_value_ids, measure_ids, volume_calculation, volume_formula, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 9, integer: 6, float: 6, many2one: 4, selection: 1, many2many: 3, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.packaging", "table_name": ""}
+{"text": "What data can be stored in base_import.tests.models.m2o.related?", "response": "The base_import.tests.models.m2o.related model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.m2o.related", "table_name": ""}
+{"text": "How is phone.blacklist implemented technically?", "response": "The phone.blacklist model is defined in module: phone_validation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "phone.blacklist", "table_name": ""}
+{"text": "What operations can I perform on account.efaktur.generate?", "response": "To use the account.efaktur.generate model, you need to provide values for required fields: company_id. Readonly fields: is_pajak_express_integration, company_id, is_centralized_efaktur, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.efaktur.generate", "table_name": ""}
+{"text": "What models are connected to sh.sale.product.indent.wizard?", "response": "The sh.sale.product.indent.wizard model has 7 relational fields: sh_partner_ids -> res.partner; sh_category_ids -> product.category; company_ids -> res.company; company_id -> res.company; product_indent_dic -> user.order.dic; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_partner_ids, sh_category_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.sale.product.indent.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for reject.picking.order.", "response": "The reject.picking.order model has 4 relational fields: driver_id -> res.partner; picking_id -> picking.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "reject.picking.order", "table_name": ""}
+{"text": "What is the list.top.product.compare model?", "response": "The list.top.product.compare model represents list.top.product.compare in the ERP system. It contains 10 fields and is used to manage list.top.product.compare data. Key fields include: name, qty, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "list.top.product.compare", "table_name": ""}
+{"text": "Show me the relational structure of sale.excel.report.", "response": "The sale.excel.report model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.excel.report", "table_name": ""}
+{"text": "What are common use cases for rn.approval.matrix?", "response": "To use the rn.approval.matrix model, you need to provide values for required fields: name, warehouse_id. Readonly fields: create_date, create_uid, level, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "rn.approval.matrix", "table_name": ""}
+{"text": "What fields does followup.invoice.tmp have?", "response": "The followup.invoice.tmp model has 45 fields: name, date, partner_id, company_id, currency_id, overdue_template, move_id, total_overdue, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 8, date: 3, many2one: 8, text: 2, many2many: 3, monetary: 1, one2many: 4, selection: 2, boolean: 5, integer: 6, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "followup.invoice.tmp", "table_name": ""}
+{"text": "Show me the relational structure of account.group.", "response": "The account.group model has 4 relational fields: parent_id -> account.group; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.group", "table_name": ""}
+{"text": "Tell me about the pos.session model.", "response": "The pos.session model represents Point of Sale Session in the ERP system. It contains 101 fields and is used to manage point of sale session data. Key fields include: company_id, config_id, name, user_id, currency_id, start_at, stop_at, sequence_number, cash_control, cash_journal_id, cash_register_id, cash_register_balance_start, cash_register_balance_end, cash_register_difference, cash_real_difference, cash_real_transaction, cash_real_expected, order_ids, order_count, statement_ids, failed_pickings, picking_count, picking_ids, rescue, move_id, payment_method_ids, total_payments_amount, is_in_company_currency, update_stock_at_closing, move_id_old, orderline_checked, crm_team_id, required_reinstall_cache, backup_session, pos_branch_id, employee_id, lock_state, order_log_ids, opened_at, opened_uid, last_login_time, login_number, state, cash_opening_balance, cash_closing_balance, is_closing_wizard, pos_config_cashbox_lines_ids, pos_config_cashbox_clsosing_line_ids, cash_register_balance_end_real, cashier_id, total_invoice_count, total_faktur_count, log_cashier_ids, is_multi_session, order_with_receivable_invoice_ids, pos_config_uuid, pos_session_cashbox_wizard_ids, cash_management_ids, cash_history_ids, gain_loss_move_id, is_pos_config_save_order_history_local, scheduler_invoice_finish_date, void_ids, bank_register_total_entry_encoding, cash_register_total_entry_encoding, bank_closing_balance, pos_session_bank_cashbox_wizard_ids, to_recompute, is_invoice_recreate, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.session", "table_name": ""}
+{"text": "How does portal.share relate to other models?", "response": "The portal.share model has 3 relational fields: partner_ids -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "portal.share", "table_name": ""}
+{"text": "What foreign keys exist in website.sale.extra.field?", "response": "The website.sale.extra.field model has 4 relational fields: website_id -> website; field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "website.sale.extra.field", "table_name": ""}
+{"text": "What is the approval.matrix.vendor model?", "response": "The approval.matrix.vendor model represents Approval Matrix Vendor in the ERP system. It contains 11 fields and is used to manage approval matrix vendor data. Key fields include: name, company_id, branch_id, approval_matrix_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.vendor", "table_name": ""}
+{"text": "What is the account.invoice.exchange model?", "response": "The account.invoice.exchange model represents account.invoice.exchange in the ERP system. It contains 23 fields and is used to manage account.invoice.exchange data. Key fields include: branch_id, name, partner_id, date, filter_move_ids, remarks, company_id, exchange_type, stage, reason, type_account, move_ids, invoice_payments_widget, move_type, line_ids, grand_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.invoice.exchange", "table_name": ""}
+{"text": "What are the available fields for account.root?", "response": "The account.root model has 6 fields: name, parent_id, company_id, id, display_name, __last_update. Field types distribution: char: 2, many2one: 2, integer: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.root", "table_name": ""}
+{"text": "Describe the field structure of gamification.karma.rank.", "response": "The gamification.karma.rank model has 18 fields: name, description, description_motivational, karma_min, user_ids, rank_users_count, image_1920, image_1024, image_512, image_256, image_128, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, html: 2, integer: 3, one2many: 1, binary: 5, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "gamification.karma.rank", "table_name": ""}
+{"text": "How to query customer.deposit.report data?", "response": "To use the customer.deposit.report model, you need to provide values for required fields: partner_id, amount, currency_id, move_id, payment_date, deposit_reconcile_journal_id, deposit_account_id. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "customer.deposit.report", "table_name": ""}
+{"text": "How does tax.sale.details.report relate to other models?", "response": "The tax.sale.details.report model has 3 relational fields: details_id -> sh.sale.details.report.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "tax.sale.details.report", "table_name": ""}
+{"text": "What fields does material.request.show.stock have?", "response": "The material.request.show.stock model has 8 fields: stock_quant_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "material.request.show.stock", "table_name": ""}
+{"text": "What operations can I perform on currency.invoice.revaluation?", "response": "To use the currency.invoice.revaluation model, you need to provide values for required fields: revaluation_period_start, revaluation_period_end, revaluation_date, journal_id, income_unrealized_account, expense_unrealized_account. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "currency.invoice.revaluation", "table_name": ""}
+{"text": "How does sale.order.alternative.product relate to other models?", "response": "The sale.order.alternative.product model has 6 relational fields: alter_product_ids -> product.product; product_id -> product.product; sale_line_id -> sale.order.line; selected_product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: alter_product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.alternative.product", "table_name": ""}
+{"text": "What data can be stored in account.analytic.new?", "response": "The account.analytic.new model has 34 fields: name, group_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, one2many: 4, selection: 2, char: 4, date: 2, boolean: 5, many2many: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.analytic.new", "table_name": ""}
+{"text": "Describe the _unknown model in Odoo.", "response": "The _unknown model represents Unknown in the ERP system. It contains 3 fields and is used to manage unknown data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "_unknown", "table_name": ""}
+{"text": "What foreign keys exist in term.condition?", "response": "The term.condition model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "term.condition", "table_name": ""}
+{"text": "How does account.user.reminder.lines relate to other models?", "response": "The account.user.reminder.lines model has 4 relational fields: account_line_id -> account.user.reminder; user_ids -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.user.reminder.lines", "table_name": ""}
+{"text": "Describe the implementation of res.mail.activity.", "response": "The res.mail.activity model is defined in module: equip3_crm_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.mail.activity", "table_name": ""}
+{"text": "Show me the fields of ir.qweb.field.datetime.", "response": "The ir.qweb.field.datetime model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.datetime", "table_name": ""}
+{"text": "How to query account.cash.flow.statement data?", "response": "To use the account.cash.flow.statement model, you need to provide values for required fields: levels, comp_detail, type_report, journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.cash.flow.statement", "table_name": ""}
+{"text": "What is the base_import.tests.models.char.noreadonly model?", "response": "The base_import.tests.models.char.noreadonly model represents Tests : Base Import Model, Character No readonly in the ERP system. It contains 8 fields and is used to manage tests : base import model, character no readonly data. Key fields include: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.char.noreadonly", "table_name": ""}
+{"text": "List all fields in the crm.lead model.", "response": "The crm.lead model has 155 fields: user_id, user_email, user_login, active, type, priority, team_id, stage_id, kanban_state, activity_date_deadline_my, color, prorated_revenue, recurring_revenue, recurring_plan, recurring_revenue_monthly, recurring_revenue_monthly_prorated, company_currency, date_closed, date_action_last, date_open, date_last_stage_update, date_conversion, partner_id, partner_is_blacklisted, contact_name, partner_name, title, email_from, phone, phone_mobile_search, phone_state, email_state, street2, zip, city, state_id, country_id, automated_probability, is_automated_probability, meeting_count, lost_reason, ribbon_message, phonecall_ids, phonecall_count, reveal_id, conversation_id, visitor_ids, visitor_page_count, visitor_sessions_count, sale_amount_total, sale_order_count, meeting_ids, one_metting, is_due_date, multiple_metting, type_id, decision_maker, has_budget, activity_data, scale, einstein_score, einstein_score_text, probability_new, automated_probability_new, salesperson_lines, dummy_boolean, user_ids, one_metting_int, multiple_metting_int, number_of_repetition, lead_product_ids, res_activity_ids, activity_count, last_follow_up, order_ids, due_date_activity, next_week_has_activity, next_week_no_activity, this_week_has_activity, this_week_no_activity, last_week_has_activity, last_week_no_activity, only_one_meeting, quotation_count, city_id, is_similar, similar_leads_count, original_team_id, name, website, street, probability, function, mobile, lang_id, company_id, campaign_id, source_id, medium_id, date_deadline, tag_ids, day_open, day_close, referred, description, branch_id, tag, expected_revenue, default_expected_revenue, is_automated_expected_revenue, quotation, final_quotation, remark, cannot_be_quoted, potential, 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, email_normalized, is_blacklisted, message_bounce, email_cc, 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, phone_sanitized, phone_sanitized_blacklisted, phone_blacklisted, mobile_blacklisted, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 26, char: 26, boolean: 30, selection: 9, date: 5, integer: 19, monetary: 7, datetime: 8, float: 7, one2many: 11, many2many: 5, html: 1, text: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.lead", "table_name": ""}
+{"text": "How do I use the purchase.agreement.legal.document model?", "response": "To use the purchase.agreement.legal.document 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.agreement.legal.document", "table_name": ""}
+{"text": "What models are connected to purchase.product.template.line?", "response": "The purchase.product.template.line model has 6 relational fields: name -> product.product; product_uom -> uom.uom; purchase_template_id -> purchase.product.template; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.product.template.line", "table_name": ""}
+{"text": "What foreign keys exist in warranty.history?", "response": "The warranty.history model has 3 relational fields: warranty_id -> product.warranty; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "warranty.history", "table_name": ""}
+{"text": "What business logic is in pos.generate.efaktur.other?", "response": "To use the pos.generate.efaktur.other model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.generate.efaktur.other", "table_name": ""}
+{"text": "How is bus.presence used in the system?", "response": "The bus.presence model represents User Presence in the ERP system. It contains 7 fields and is used to manage user presence data. Key fields include: user_id, last_poll, last_presence, status, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "bus.presence", "table_name": ""}
+{"text": "Can you explain the purpose of bus.presence?", "response": "The bus.presence model represents User Presence in the ERP system. It contains 7 fields and is used to manage user presence data. Key fields include: user_id, last_poll, last_presence, status, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "bus.presence", "table_name": ""}
+{"text": "What business logic is in gamification.badge.user?", "response": "To use the gamification.badge.user model, you need to provide values for required fields: user_id, badge_id. Readonly fields: level, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "gamification.badge.user", "table_name": ""}
+{"text": "What foreign keys exist in base_import.tests.models.m2o?", "response": "The base_import.tests.models.m2o model has 3 relational fields: value -> base_import.tests.models.m2o.related; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.m2o", "table_name": ""}
+{"text": "Can you explain the purpose of customer.order.dic?", "response": "The customer.order.dic model represents customer.order.dic in the ERP system. It contains 10 fields and is used to manage customer.order.dic data. Key fields include: report_id, list_order, saleperson, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "customer.order.dic", "table_name": ""}
+{"text": "What are the technical details of rfm.yearly.analysis.by.segment?", "response": "The rfm.yearly.analysis.by.segment model is defined in module: setu_rfm_analysis. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "rfm.yearly.analysis.by.segment", "table_name": ""}
+{"text": "Show me the relational structure of report_excel_export_wizard.", "response": "The report_excel_export_wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report_excel_export_wizard", "table_name": ""}
+{"text": "How is pos.promotion.multilevel.gift implemented technically?", "response": "The pos.promotion.multilevel.gift model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.promotion.multilevel.gift", "table_name": ""}
+{"text": "How do I use the report.sh_purchase_reports.sh_pr_details_report_doc model?", "response": "To use the report.sh_purchase_reports.sh_pr_details_report_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_pr_details_report_doc", "table_name": ""}
+{"text": "How do I use the im_livechat.channel.rule model?", "response": "To use the im_livechat.channel.rule model, you need to provide values for required fields: action. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "im_livechat.channel.rule", "table_name": ""}
+{"text": "Describe the material.request model in Odoo.", "response": "The material.request model represents Material Request in the ERP system. It contains 62 fields and is used to manage material request data. Key fields include: name, create_date, create_uid, requested_by, destination_location_id, destination_warehouse_id, company_id, branch_id, schedule_date, expiry_date, description, source_document, status, status_1, status_2, status_3, product_line, purchase_request, internal_transfer, check_product, mr_approval_matrix_id, is_material_request_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, is_reset_to_draft, analytic_account_group_ids, cancel_reason, internal_note, pr_count, ir_count, itr_war_count, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "material.request", "table_name": ""}
+{"text": "What methods are available in hr.plan.wizard?", "response": "The hr.plan.wizard model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hr.plan.wizard", "table_name": ""}
+{"text": "What modules define product.quantity.available.report?", "response": "The product.quantity.available.report model is defined in module: equip3_pos_general. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.quantity.available.report", "table_name": ""}
+{"text": "What business logic is in faktur.message?", "response": "To use the faktur.message 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "faktur.message", "table_name": ""}
+{"text": "What models are connected to split.pr.wizard?", "response": "The split.pr.wizard model has 4 relational fields: pr_line_id -> purchase.request.line; line_ids -> split.pr.line.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "split.pr.wizard", "table_name": ""}
+{"text": "What foreign keys exist in receipt.payment.matrix.reject?", "response": "The receipt.payment.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "receipt.payment.matrix.reject", "table_name": ""}
+{"text": "Tell me about the res.users.identitycheck model.", "response": "The res.users.identitycheck model represents Password Check Wizard in the ERP system. It contains 8 fields and is used to manage password check wizard data. Key fields include: password, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.users.identitycheck", "table_name": ""}
+{"text": "Describe the store.filters.groups model in Odoo.", "response": "The store.filters.groups model represents Store Filters Groups in the ERP system. It contains 11 fields and is used to manage store filters groups data. Key fields include: model_id, node_option, attribute_name, attribute_string, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "store.filters.groups", "table_name": ""}
+{"text": "Describe the many2many relations for sale.adv.wizard.", "response": "The sale.adv.wizard model has 5 relational fields: product_ids -> sale.adv.wizard.product.line; product_attr_ids -> product.attribute.value; specific_product_ids -> sale.adv.wizard.product.line.specific; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_attr_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.adv.wizard", "table_name": ""}
+{"text": "How is sh.target.commision.new used in the system?", "response": "The sh.target.commision.new model represents sh.target.commision.new in the ERP system. It contains 18 fields and is used to manage sh.target.commision.new data. Key fields include: commission_id, name, user_id, main_target, current_achievement, current_achievement_formula, curr_achieve, target_based_on, target_on, to_date, type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.target.commision.new", "table_name": ""}
+{"text": "Show me the fields of report.dev_rma.report_rma_template.", "response": "The report.dev_rma.report_rma_template model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.dev_rma.report_rma_template", "table_name": ""}
+{"text": "How is stock.move implemented technically?", "response": "The stock.move model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.move", "table_name": ""}
+{"text": "Can you explain the purpose of board.board?", "response": "The board.board model represents Board in the ERP system. It contains 3 fields and is used to manage board data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "board.board", "table_name": ""}
+{"text": "Show me the fields of sh.edit.title.", "response": "The sh.edit.title model has 8 fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.edit.title", "table_name": ""}
+{"text": "How to query format.address.mixin data?", "response": "To use the format.address.mixin model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "format.address.mixin", "table_name": ""}
+{"text": "Describe the field structure of pos.generate.efaktur.digunggung.", "response": "The pos.generate.efaktur.digunggung model has 14 fields: gen_efaktur_id, partner_id, account_move_id, account_move_data, no_of_invoice, amount_total, l10n_id_tax_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, text: 1, integer: 2, float: 1, char: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.generate.efaktur.digunggung", "table_name": ""}
+{"text": "What fields does purchase.request.line.make.purchase.order have?", "response": "The purchase.request.line.make.purchase.order model has 15 fields: item_ids, sync_data_planned, supplier_ids, supplier_id, create_rfq, partner_id, pr_id, purchase_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, boolean: 1, many2many: 1, many2one: 6, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.request.line.make.purchase.order", "table_name": ""}
+{"text": "How do I use the rating.mixin model?", "response": "To use the rating.mixin model, you need to provide values for required fields: none. Readonly fields: rating_ids, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "rating.mixin", "table_name": ""}
+{"text": "What methods are available in wizard.scrap.order.report?", "response": "The wizard.scrap.order.report model is defined in module: eq_scrap_order_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "wizard.scrap.order.report", "table_name": ""}
+{"text": "What data can be stored in purchase.change.request?", "response": "The purchase.change.request model has 25 fields: name, requested_id, budget_std_id, date, company_id, branch_id, pur_change_req_ids, state, state1, state2, budget_line, approval_matrix, is_allowed_to_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, currency_id, request_partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 10, date: 1, one2many: 3, selection: 3, boolean: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.change.request", "table_name": ""}
+{"text": "How is mail.tracking.value implemented technically?", "response": "The mail.tracking.value model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.tracking.value", "table_name": ""}
+{"text": "Which fields in milestone.contract.template are computed?", "response": "The milestone.contract.template model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "milestone.contract.template", "table_name": ""}
+{"text": "Show me the fields of sh_barcode_scanner_adv.search.document.", "response": "The sh_barcode_scanner_adv.search.document model has 8 fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh_barcode_scanner_adv.search.document", "table_name": ""}
+{"text": "What are the available fields for account.tax.map.purchase.line?", "response": "The account.tax.map.purchase.line model has 17 fields: company_id, purchase_tax_id, target_company, target_purchase_tax, map_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, line_ids, child_company_id, ownership, sales_line_ids, purchase_line_ids. Field types distribution: many2one: 8, integer: 1, char: 1, datetime: 3, one2many: 3, float: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.tax.map.purchase.line", "table_name": ""}
+{"text": "Describe the many2many relations for report.sh_purchase_reports.sh_pr_details_report_doc.", "response": "The report.sh_purchase_reports.sh_pr_details_report_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_pr_details_report_doc", "table_name": ""}
+{"text": "Can you explain the purpose of crm.lead.scoring.frequency?", "response": "The crm.lead.scoring.frequency model represents Lead Scoring Frequency in the ERP system. It contains 12 fields and is used to manage lead scoring frequency data. Key fields include: variable, value, won_count, lost_count, team_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.lead.scoring.frequency", "table_name": ""}
+{"text": "Describe the field structure of orderline.orderline.", "response": "The orderline.orderline model has 25 fields: reverse_id, product_id, name, quantity, remaining_quantity, product_uom, price_unit, tax_id, price_subtotal, ordered_qty, delivered_qty, qty_invoiced, undelivered_qty, sequence, sequence2, company_id, analytic_tag_ids, price_tax, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, text: 1, float: 9, many2many: 2, integer: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "orderline.orderline", "table_name": ""}
+{"text": "What are the relationships in product.image?", "response": "The product.image model has 4 relational fields: product_tmpl_id -> product.template; product_variant_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.image", "table_name": ""}
+{"text": "What business logic is in sh.top.purchasing.excel.extended?", "response": "To use the sh.top.purchasing.excel.extended 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.top.purchasing.excel.extended", "table_name": ""}
+{"text": "Show me the relational structure of account.pettycash.fund.change.", "response": "The account.pettycash.fund.change model has 7 relational fields: fund -> account.pettycash; custodian -> res.users; payable_account -> account.account; receivable_account -> account.account; move -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.pettycash.fund.change", "table_name": ""}
+{"text": "How to query queue.requeue.job data?", "response": "To use the queue.requeue.job 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "queue.requeue.job", "table_name": ""}
+{"text": "How is report.sh_purchase_reports.sh_vend_po_analysis_doc used in the system?", "response": "The report.sh_purchase_reports.sh_vend_po_analysis_doc model represents Vendor Purchase Analysis report abstract model in the ERP system. It contains 3 fields and is used to manage vendor purchase analysis report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_vend_po_analysis_doc", "table_name": ""}
+{"text": "Can you explain the purpose of invoice.confirmation.availability?", "response": "The invoice.confirmation.availability model represents Confirmation Wizard in the ERP system. It contains 10 fields and is used to manage confirmation wizard data. Key fields include: message, invoice_id, whatsapp, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "invoice.confirmation.availability", "table_name": ""}
+{"text": "What operations can I perform on service.work.order?", "response": "To use the service.work.order model, you need to provide values for required fields: none. Readonly fields: name, partner_id, account_analytic_tag_ids, date_planned, company_id, branch_id, checklist_ids, milestone_name, contract_term, move_id, account_move_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "service.work.order", "table_name": ""}
+{"text": "What data can be stored in budget.carry.over?", "response": "The budget.carry.over model has 34 fields: name, complete_name, crossover_budget_id, state, parent_id, is_parent_budget, account_tag_ids, budget_carry_over_line_ids, company_id, date_from, date_to, branch_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 7, selection: 1, boolean: 6, many2many: 3, one2many: 4, date: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "budget.carry.over", "table_name": ""}
+{"text": "List all fields in the approval.matrix.accounting.lines model.", "response": "The approval.matrix.accounting.lines model has 31 fields: sequence, user_ids, minimum_approver, approval_matrix_id, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, approver_state, move_id, receipt_id, multi_receipt_id, voucher_id, payment_voc_id, acc_internal_transfer_id, account_budget_request_id, account_budget_id, budget_purchase_id, account_budget_req_id, customer_deposit_id, acc_vendor_deposit_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 4, many2many: 2, many2one: 16, text: 1, datetime: 4, char: 2, boolean: 1, selection: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.accounting.lines", "table_name": ""}
+{"text": "How do I use the sms.template.preview model?", "response": "To use the sms.template.preview model, you need to provide values for required fields: sms_template_id. Readonly fields: model_id, body, no_record, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sms.template.preview", "table_name": ""}
+{"text": "What data can be stored in account.tour.upload.bill?", "response": "The account.tour.upload.bill model has 41 fields: composer_id, selection, sample_bill_preview, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, subject, body, parent_id, template_id, attachment_ids, layout, add_sign, email_from, author_id, composition_mode, model, res_id, record_name, use_active_domain, active_domain, message_type, subtype_id, mail_activity_type_id, reply_to, no_auto_thread, is_log, partner_ids, notify, auto_delete, auto_delete_message, mail_server_id, mass_mailing_id, campaign_id, mass_mailing_name, mailing_list_ids, is_wp. Field types distribution: many2one: 11, selection: 3, binary: 1, integer: 2, char: 8, datetime: 3, html: 1, many2many: 3, boolean: 8, text: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.tour.upload.bill", "table_name": ""}
+{"text": "What models are connected to stock.lot.serialize?", "response": "The stock.lot.serialize model has 4 relational fields: picking_id -> stock.picking; stock_move_line_ids -> stock.lot.serialize.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.lot.serialize", "table_name": ""}
+{"text": "What is the res.city model?", "response": "The res.city model represents City in the ERP system. It contains 11 fields and is used to manage city data. Key fields include: name, zipcode, country_id, state_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.city", "table_name": ""}
+{"text": "What foreign keys exist in sh.qc.point?", "response": "The sh.qc.point model has 18 relational fields: product_id -> product.product; logged_user -> res.users; company_id -> res.company; operation -> stock.picking.type; team -> sh.qc.team; product_ids -> product.product; operation_ids -> stock.picking.type; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, operation_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.qc.point", "table_name": ""}
+{"text": "What are the relationships in project.task.recurrence?", "response": "The project.task.recurrence model has 3 relational fields: task_ids -> project.task; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "project.task.recurrence", "table_name": ""}
+{"text": "What is the sale.adv.wizard model?", "response": "The sale.adv.wizard model represents Sale Multi Product Selection Advanced Wizard in the ERP system. It contains 11 fields and is used to manage sale multi product selection advanced wizard data. Key fields include: product_ids, product_attr_ids, specific_product_ids, order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.adv.wizard", "table_name": ""}
+{"text": "Tell me about the pos.remote.session model.", "response": "The pos.remote.session model represents Help manage remote sessions in the ERP system. It contains 10 fields and is used to manage help manage remote sessions data. Key fields include: message, config_ids, action, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.remote.session", "table_name": ""}
+{"text": "What fields does report.stock.demand have?", "response": "The report.stock.demand model has 10 fields: date_datetime, quantity, forecast, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, float: 1, boolean: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.stock.demand", "table_name": ""}
+{"text": "Show me the fields of account.invoice.exchange.", "response": "The account.invoice.exchange model has 23 fields: branch_id, name, partner_id, date, filter_move_ids, remarks, company_id, exchange_type, stage, reason, type_account, move_ids, invoice_payments_widget, move_type, line_ids, grand_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, date: 1, many2many: 2, text: 3, selection: 4, one2many: 1, float: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.invoice.exchange", "table_name": ""}
+{"text": "Describe the implementation of return.approval.matrix.", "response": "The return.approval.matrix model is defined in module: allfresh_mod_inventory. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "return.approval.matrix", "table_name": ""}
+{"text": "How does rn.approval_matrix_line relate to other models?", "response": "The rn.approval_matrix_line model has 7 relational fields: approver -> res.users; last_approved -> res.users; rn_approval_matrix_id1 -> rn.approval.matrix; picking_id -> stock.picking; approved_users -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: approver, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "rn.approval_matrix_line", "table_name": ""}
+{"text": "What foreign keys exist in cashback.line?", "response": "The cashback.line model has 6 relational fields: product_id -> product.product; customer_voucher_id -> customer.voucher; order_id -> sale.order; invoice_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "cashback.line", "table_name": ""}
+{"text": "What are the available fields for account.edi.format?", "response": "The account.edi.format model has 9 fields: name, code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.edi.format", "table_name": ""}
+{"text": "Describe the many2many relations for purchase.tender.create.wizard.", "response": "The purchase.tender.create.wizard model has 5 relational fields: vendor_ids -> res.partner; product_line_ids -> purchase.tender.create.lines.wizard; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: vendor_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.tender.create.wizard", "table_name": ""}
+{"text": "What models are connected to account.fiscal.position.template?", "response": "The account.fiscal.position.template model has 8 relational fields: chart_template_id -> account.chart.template; account_ids -> account.fiscal.position.account.template; tax_ids -> account.fiscal.position.tax.template; country_id -> res.country; country_group_id -> res.country.group; state_ids -> res.country.state; create_uid -> res.users; write_uid -> res.users. Many2many fields: state_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.fiscal.position.template", "table_name": ""}
+{"text": "Show me the fields of report.equip3_kitchen_operations.report_cooking_list.", "response": "The report.equip3_kitchen_operations.report_cooking_list model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_kitchen_operations.report_cooking_list", "table_name": ""}
+{"text": "Show me the fields of crm.lead2opportunity.partner.mass.", "response": "The crm.lead2opportunity.partner.mass model has 18 fields: lead_id, lead_tomerge_ids, user_ids, deduplicate, action, force_assignment, name, duplicated_lead_ids, partner_id, user_id, team_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, many2many: 3, boolean: 2, selection: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.lead2opportunity.partner.mass", "table_name": ""}
+{"text": "How to create records in ir.qweb.field.float?", "response": "To use the ir.qweb.field.float model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.float", "table_name": ""}
+{"text": "How does payment.acquirer.onboarding.wizard relate to other models?", "response": "The payment.acquirer.onboarding.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "How is wizard.report.menu.create implemented technically?", "response": "The wizard.report.menu.create model is defined in module: report_excel. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "wizard.report.menu.create", "table_name": ""}
+{"text": "What methods are available in pos.product.attribute?", "response": "The pos.product.attribute model is defined in module: equip3_pos_general. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.product.attribute", "table_name": ""}
+{"text": "What operations can I perform on product.quantity.available.report?", "response": "To use the product.quantity.available.report model, you need to provide values for required fields: none. Readonly fields: product_barcode, product_default_code, location_id, product_id, qty_available, in_date, sale_qty, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.quantity.available.report", "table_name": ""}
+{"text": "Tell me about the report.sh_purchase_reports.sh_payment_pr_report_doc model.", "response": "The report.sh_purchase_reports.sh_payment_pr_report_doc model represents Bill payment report abstract model in the ERP system. It contains 3 fields and is used to manage bill payment report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_payment_pr_report_doc", "table_name": ""}
+{"text": "What methods are available in ir.sequence?", "response": "The ir.sequence model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.sequence", "table_name": ""}
+{"text": "Describe the implementation of mail.resend.message.", "response": "The mail.resend.message model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.resend.message", "table_name": ""}
+{"text": "What is the bus.presence model?", "response": "The bus.presence model represents User Presence in the ERP system. It contains 7 fields and is used to manage user presence data. Key fields include: user_id, last_poll, last_presence, status, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "bus.presence", "table_name": ""}
+{"text": "What methods are available in account.tax.digunggung?", "response": "The account.tax.digunggung model is defined in module: equip3_accounting_efaktur. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.tax.digunggung", "table_name": ""}
+{"text": "How does base_import.tests.models.char.readonly relate to other models?", "response": "The base_import.tests.models.char.readonly model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.char.readonly", "table_name": ""}
+{"text": "How does project.sale.line.employee.map relate to other models?", "response": "The project.sale.line.employee.map model has 8 relational fields: project_id -> project.project; employee_id -> hr.employee; sale_line_id -> sale.order.line; company_id -> res.company; timesheet_product_id -> product.product; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "project.sale.line.employee.map", "table_name": ""}
+{"text": "What does the customer.order.dic model represent?", "response": "The customer.order.dic model represents customer.order.dic in the ERP system. It contains 10 fields and is used to manage customer.order.dic data. Key fields include: report_id, list_order, saleperson, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "customer.order.dic", "table_name": ""}
+{"text": "Show me the relational structure of account.debit.note.", "response": "The account.debit.note model has 4 relational fields: move_ids -> account.move; journal_id -> account.journal; create_uid -> res.users; write_uid -> res.users. Many2many fields: move_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.debit.note", "table_name": ""}
+{"text": "What operations can I perform on change.password.wizard?", "response": "To use the change.password.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "change.password.wizard", "table_name": ""}
+{"text": "Describe the field structure of report.accounting_pdf_reports.report_financial.", "response": "The report.accounting_pdf_reports.report_financial model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.accounting_pdf_reports.report_financial", "table_name": ""}
+{"text": "Can you explain the purpose of acrux.chat.connector?", "response": "The acrux.chat.connector model represents Connector Definition in the ERP system. It contains 38 fields and is used to manage connector definition data. Key fields include: name, sequence, message, company_id, team_id, verify, source, channel, endpoint, apikey, sandbox, uuid, time_to_respond, time_to_reasign, border_color, ca_app_name, ca_status, ca_status_txt, ca_qr_code, sale_report_id, connector_type, qc_app_name, qc_status, qc_status_txt, qc_qr_code, qc_channel, qc_channel_id, qc_sdk_token, qc_template_ids, qc_webhook_url, connection_status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "acrux.chat.connector", "table_name": ""}
+{"text": "Which fields in queue.requeue.job are computed?", "response": "The queue.requeue.job model is defined in module: queue_job. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "queue.requeue.job", "table_name": ""}
+{"text": "How do I use the ir.cron model?", "response": "To use the ir.cron model, you need to provide values for required fields: ir_actions_server_id, user_id, nextcall, name, type, model_id, activity_user_type, usage, state, binding_type. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update, model_name, crud_model_name, mass_edit_apply_domain_in_lines, xml_id, website_url. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.cron", "table_name": ""}
+{"text": "What are common use cases for report.stock.report_product_product_replenishment?", "response": "To use the report.stock.report_product_product_replenishment model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.stock.report_product_product_replenishment", "table_name": ""}
+{"text": "What are common use cases for pos.make.payment?", "response": "To use the pos.make.payment model, you need to provide values for required fields: config_id, amount, payment_method_id, payment_date. Readonly fields: payment_difference, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.make.payment", "table_name": ""}
+{"text": "Describe the field structure of res.users.", "response": "The res.users model has 719 fields: partner_id, login, password, new_password, signature, active, active_partner, action_id, groups_id, log_ids, login_date, share, companies_count, tz_offset, company_id, company_ids, accesses_count, rules_count, groups_count, api_key_ids, user_tag_id, totp_enabled, im_status, resource_ids, resource_calendar_id, digital_signature, notification_type, is_moderator, moderation_counter, moderation_channel_ids, access_management_ids, notify_success_channel_name, notify_danger_channel_name, notify_warning_channel_name, notify_info_channel_name, notify_default_channel_name, state, karma, karma_tracking_ids, gold_badge, silver_badge, bronze_badge, rank_id, next_rank_id, employee_ids, employee_id, job_title, work_phone, mobile_phone, employee_phone, work_email, category_ids, department_id, address_id, work_location, employee_parent_id, coach_id, address_home_id, is_address_home_a_company, private_email, km_home_work, employee_bank_account_id, employee_country_id, identification_id, passport_id, gender, birthday, place_of_birth, country_of_birth, marital, spouse_complete_name, spouse_birthdate, children, emergency_contact, emergency_phone, visa_no, permit_no, visa_expire, additional_note, barcode, pin, certificate, study_field, study_school, employee_count, hr_presence_state, last_activity, last_activity_time, can_edit, odoobot_failed, sale_team_id, goal_ids, badge_ids, sh_wqm_web_quick_menu_line, sh_enable_one_click, sh_direct_redirect, target_sales_won, target_sales_done, livechat_username, website_id, acrux_chat_active, equip_theme_color, odoobot_state, purchase_team_id, sign, is_tendor_vendor, property_warehouse_id, target_sales_invoiced, restrict_locations, stock_location_ids, default_picking_type_ids, qc_email, qc_password, qc_token, qc_avatar_url, show_branch, branch_id, branch_ids, analytic_tag_ids, allow_analytic_group, access_rights_profile_id, user_delegation_id, warehouse_ids, warehouse_id, default_warehouse_id, allowed_warehouse_ids, is_external_link, device_token, pos_config_id, pos_config_ids, pos_delete_order, pos_branch_id, pos_portal_user, allow_access_backend, cashier_code, allow_discount, allow_qty, allow_price, allow_remove_line, allow_minus, allow_payment, allow_customer, allow_add_order, allow_remove_order, allow_add_product, allow_payment_zero, allow_offline_mode, pos_security_pin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, name, title, parent_id, parent_name, child_ids, ref, lang, active_lang_count, tz, vat, same_vat_partner_id, bank_ids, website, comment, category_id, credit_limit, employee, function, street, street2, zip, city, state_id, country_id, partner_latitude, partner_longitude, email_formatted, mobile, is_company, industry_id, company_type, color, user_ids, partner_share, contact_address, commercial_partner_id, commercial_company_name, company_name, self, country_enforce_cities, date_localization, email, phone, channel_ids, user_id, signup_token, signup_type, signup_expiration, signup_valid, signup_url, calendar_last_notif_ack, 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, email_normalized, is_blacklisted, message_bounce, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, phone_sanitized, phone_sanitized_blacklisted, phone_blacklisted, mobile_blacklisted, website_message_ids, message_has_sms_error, credit, debit, debit_limit, total_invoiced, currency_id, journal_item_count, property_account_position_id, property_payment_term_id, property_supplier_payment_term_id, ref_company_ids, has_unreconciled_entries, last_time_entries_checked, invoice_ids, contract_ids, bank_account_count, trust, invoice_warn, invoice_warn_msg, supplier_rank, customer_rank, team_id, opportunity_ids, meeting_ids, opportunity_count, meeting_count, task_ids, task_count, property_stock_customer, property_stock_supplier, picking_warn, picking_warn_msg, is_seo_optimized, website_meta_title, website_meta_description, website_meta_keywords, website_meta_og_img, seo_name, is_published, can_publish, website_url, website_published, visitor_ids, property_payment_method_id, phonecall_ids, phonecall_count, associate_member, member_lines, free_member, membership_amount, membership_state, membership_start, membership_stop, membership_cancel, payment_token_ids, payment_token_count, property_purchase_currency_id, purchase_order_count, supplier_invoice_count, purchase_warn, purchase_warn_msg, receipt_reminder_email, reminder_date_before_receipt, website_description, website_short_description, pos_order_count, purchase_line_ids, on_time_rate, sale_order_count, sale_order_ids, sale_warn, sale_warn_msg, vendor_products, vendor_product_categ_ids, visible_eval, percent_consignment, country_code, l10n_id_pkp, l10n_id_nik, l10n_id_tax_address, l10n_id_tax_name, l10n_id_kode_transaksi, last_website_so_id, contact_ids, related_company_id, property_delivery_carrier_id, report_template_id1, report_template_id, report_sale_template_id1, report_sale_template_id, report_po_template_id1, report_po_template_id, report_rfq_template_id, report_delivery_template_id1, report_delivery_template_id, report_picking_template_id, rfm_segment_id, rfm_score_id, partner_segment_history_ids, loyalty_points, loyalty_amount, loyalty_history_ids, interest_vendor_account_payable, interest_customer_account_receivable, sign_ebupot_id, identity_id, vat_bp, nin, user_sign, tax_facility, doc_number, other_tax, desc_other_tax, tin, date, country, no_paspor, no_kitas, visible_vat_bp, visible_nin, visible_doc_number, visible_other_tax, visible_desc_other_tax, visible_date, visible_country, visible_all, customer_sequence, debtor_id, is_limit_salesperson, customer_category, property_product_pricelist, res_city_id, city_id, customer_creation_date, preferred_location, customer_availability, bank_info, faktur_pajak_gabungan, blok, kelurahan, kecamatan, rukun_tetangga, rukun_warga, street_number, street_number2, overpayment_processed_by, vendor_sequence, is_vendor, state1, state2, state3, is_approving_matrix_vendor, approved_user_ids, approving_matrix_vendor_id, approved_matrix_ids, is_approve_button, approval_matrix_line_id, request_partner_id, capital_revenue, company_size, company_size2, is_similiar, similiar_partner_count, place, birthdate, blacklist_history_ids, vendor_creation_date, drive_rate, is_driver, is_app_login, device_imei_no, status, driver_message, is_leads, is_set_vendor_purchase_limit, vendor_purchase_limit, vendor_available_purchase_limit, is_set_vendor_onhold, report_pr_template_id, type, is_customer_invoice_overdue, customer_max_invoice_overdue, is_set_customer_on_hold, customer_credit, customer_credit_limit, set_customer_onhold, cust_credit_limit, is_over_credit_limit, is_invoice_overdue, open_invoice_limit, is_open_invoice_limit, no_open_inv_limit, avl_open_inv_limt, customer_on_hold_open_invoice, set_customer_credit_limit_per_brand, product_brand_ids, filter_brand_ids, lead_sequence, discount_id, birthday_date, group_ids, pos_order_ids, pos_total_amount, pos_partner_type_id, special_name, is_pos_partner, customer_target_id, customer_voucher_ids, customer_voucher_count, target_amount_customer_target, index, is_customer, is_pos_member, pos_loyalty_point_import, pos_loyalty_point, pos_loyalty_type, pos_loyalty_point_ids, order_count, pos_loyalty_point_available, id_number, civil, employee_number, file_name, file_siup, npwp, salinan_anggaran_dasar, surat_persetujuan_dirjen_ahu, akta_perubahan_pengurus_terakhir, sppkp, surat_keterangan_tidak_kena_pajak, surat_pernyataan_dan_kuasa, gender_type, is_birthday_gift, npwp_binary, ktp_binary, property_account_payable_id, property_account_receivable_id, persentase_antar_badan, image_1920, image_1024, image_512, image_256, image_128, sel_groups_2_3, sel_groups_75_76, sel_groups_256_257_258, sel_groups_14, in_group_267, in_group_266, sel_groups_62_63_64_81, in_group_274, in_group_271, in_group_269, in_group_272, in_group_273, in_group_268, in_group_270, sel_groups_145_146, sel_groups_131_132, in_group_90, in_group_98, in_group_100, in_group_92, in_group_96, in_group_89, in_group_95, in_group_99, in_group_93, in_group_91, in_group_101, in_group_97, in_group_94, sel_groups_226, sel_groups_140_141, in_group_82, in_group_83, in_group_84, in_group_85, sel_groups_37_38, sel_groups_51_53_52_133, sel_groups_138_139, sel_groups_1_9_10, in_group_237, in_group_238, in_group_236, sel_groups_173_174, sel_groups_104_105, sel_groups_182_183, sel_groups_147_148_149, sel_groups_155_217_218_156, sel_groups_207, sel_groups_203_212_204, sel_groups_290, sel_groups_176_177, sel_groups_134_135, sel_groups_184_185, sel_groups_27_28, sel_groups_17, sel_groups_58_213_59, sel_groups_214_215_216, in_group_54, in_group_60, in_group_11, in_group_7, in_group_88, in_group_233, in_group_55, in_group_79, in_group_46, in_group_47, in_group_129, in_group_108, in_group_124, in_group_125, in_group_136, in_group_152, in_group_130, in_group_116, in_group_118, in_group_111, in_group_222, in_group_78, in_group_34, in_group_70, in_group_77, in_group_198, in_group_228, in_group_128, in_group_153, in_group_122, in_group_107, in_group_223, in_group_102, in_group_151, in_group_163, in_group_208, in_group_161, in_group_26, in_group_229, in_group_110, in_group_109, in_group_154, in_group_114, in_group_121, in_group_115, in_group_68, in_group_162, in_group_239, in_group_126, in_group_127, in_group_123, in_group_57, in_group_220, in_group_113, in_group_120, in_group_117, in_group_50, in_group_15, in_group_240, in_group_16, in_group_74, in_group_227, in_group_241, in_group_87, in_group_86, in_group_48, in_group_49, in_group_143, in_group_144, in_group_142, in_group_119, in_group_112, in_group_221, sel_groups_25, sel_groups_199, in_group_167, in_group_44, in_group_170, in_group_172, in_group_168, in_group_171, in_group_40, in_group_71, in_group_43, in_group_39, in_group_35, in_group_29, in_group_36, in_group_41, in_group_32, in_group_33, in_group_42, in_group_169, in_group_157, in_group_45, in_group_61, in_group_67, in_group_66, in_group_31, in_group_205, in_group_30, in_group_69, in_group_232, in_group_65, in_group_235, in_group_72, in_group_56, in_group_73, in_group_225, in_group_193, in_group_209, in_group_201, in_group_211, in_group_210, in_group_189, in_group_191, in_group_192, in_group_194, in_group_196, in_group_197, in_group_190, in_group_195, in_group_200, sel_groups_291_292, in_group_8, in_group_4, in_group_5, in_group_6, in_group_283, in_group_261, in_group_259, in_group_288, in_group_21, in_group_20, in_group_22, in_group_282, in_group_279, in_group_289, in_group_280, in_group_276, in_group_103, in_group_164, in_group_178, in_group_231, in_group_175, in_group_277, in_group_206, in_group_23, in_group_18, in_group_24, in_group_13, in_group_165, in_group_150, in_group_137, in_group_180, in_group_224, in_group_234, in_group_286, in_group_230, in_group_106, in_group_285, in_group_284, in_group_186, in_group_187, in_group_275, in_group_158, in_group_281, in_group_287, in_group_166, in_group_188, in_group_80, in_group_19, in_group_245, in_group_202, in_group_181, in_group_263, in_group_278, in_group_12, in_group_179, in_group_264, in_group_219, in_group_260. Field types distribution: many2one: 84, char: 99, html: 2, boolean: 295, many2many: 21, one2many: 35, datetime: 7, integer: 44, binary: 15, selection: 63, date: 15, text: 13, float: 21, monetary: 5.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.users", "table_name": ""}
+{"text": "What foreign keys exist in sale.coupon.apply.code?", "response": "The sale.coupon.apply.code model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.coupon.apply.code", "table_name": ""}
+{"text": "What modules define pos.loyalty.update.point?", "response": "The pos.loyalty.update.point model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.loyalty.update.point", "table_name": ""}
+{"text": "Tell me about the report.equip3_kitchen_reports.report_kitchen_production model.", "response": "The report.equip3_kitchen_reports.report_kitchen_production model represents Kitchen Structure Report in the ERP system. It contains 3 fields and is used to manage kitchen structure report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_kitchen_reports.report_kitchen_production", "table_name": ""}
+{"text": "How to create records in ir.qweb.field.many2one?", "response": "To use the ir.qweb.field.many2one model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.many2one", "table_name": ""}
+{"text": "What are common use cases for pos.loyalty.category?", "response": "To use the pos.loyalty.category model, you need to provide values for required fields: name, from_point, to_point, coefficient. Readonly fields: member_card_preview, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.loyalty.category", "table_name": ""}
+{"text": "Describe the res.users.apikeys model in Odoo.", "response": "The res.users.apikeys model represents res.users.apikeys in the ERP system. It contains 7 fields and is used to manage res.users.apikeys data. Key fields include: name, user_id, scope, create_date, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.users.apikeys", "table_name": ""}
+{"text": "What are the technical details of sh.announcement?", "response": "The sh.announcement model is defined in module: sh_backmate_theme_adv. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.announcement", "table_name": ""}
+{"text": "What foreign keys exist in account.efaktur?", "response": "The account.efaktur model has 7 relational fields: year -> sh.fiscal.year; invoice_id -> account.move; partner_id -> res.partner; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.efaktur", "table_name": ""}
+{"text": "Describe the implementation of payment.link.wizard.", "response": "The payment.link.wizard model is defined in module: payment. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "payment.link.wizard", "table_name": ""}
+{"text": "How to create records in sms.resend.recipient?", "response": "To use the sms.resend.recipient model, you need to provide values for required fields: sms_resend_id, notification_id. Readonly fields: failure_type, partner_id, partner_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sms.resend.recipient", "table_name": ""}
+{"text": "List all fields in the saleblanket.saleblanket model.", "response": "The saleblanket.saleblanket model has 85 fields: name, partner_id, pricelist_id, payment_term_id, current_user, sale_order_count, expiry_date, creation_date, user_id, order_line_count, state, currency_id, state1, state2, state3, bo_state, bo_state_1, company_id, current_company, branch_id, days_left, analytic_tag_ids, order_line_ids, qty, delivery_qty, remaining_qty, qty_invoiced, reason, delivery_status, approving_matrix_bo_sale_id, is_bo_approval_matrix, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, approved_matrix_ids, amount_untaxed, amount_tax, amount_total, analytic_accounting, invoice_address, delivery_address, is_product_filled, is_active_company, max_line_sequence, report_template_id1, report_template_id, amount_to_text, 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. Field types distribution: char: 8, many2one: 23, integer: 9, datetime: 5, selection: 8, many2many: 3, one2many: 6, float: 4, text: 2, boolean: 12, monetary: 3, date: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "saleblanket.saleblanket", "table_name": ""}
+{"text": "How to query report.sh_sale_reports.sh_top_selling_product_doc data?", "response": "To use the report.sh_sale_reports.sh_top_selling_product_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_top_selling_product_doc", "table_name": ""}
+{"text": "What models are connected to kpi.scorecard.line?", "response": "The kpi.scorecard.line model has 6 relational fields: kpi_id -> kpi.item; category_id -> kpi.category; period_id -> kpi.period; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kpi.scorecard.line", "table_name": ""}
+{"text": "What methods are available in customer.deposit.wizard?", "response": "The customer.deposit.wizard model is defined in module: equip3_accounting_deposit. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "customer.deposit.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for mr_line.pr.wizard.", "response": "The mr_line.pr.wizard model has 3 relational fields: pr_wizard_line -> mr_line.pr.wizard_line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mr_line.pr.wizard", "table_name": ""}
+{"text": "What are common use cases for report.equip3_accounting_reports.balance_sheet?", "response": "To use the report.equip3_accounting_reports.balance_sheet model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.balance_sheet", "table_name": ""}
+{"text": "List all fields in the report.equip3_pos_report.report_pos_payment model.", "response": "The report.equip3_pos_report.report_pos_payment model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_pos_report.report_pos_payment", "table_name": ""}
+{"text": "List all fields in the sale.order.pricelist.wizard model.", "response": "The sale.order.pricelist.wizard model has 9 fields: shs_pricelist_id, pricelist_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.order.pricelist.wizard", "table_name": ""}
+{"text": "What modules define pos.payment.method.key?", "response": "The pos.payment.method.key model is defined in module: equip3_pos_keyboard_shortcut. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.payment.method.key", "table_name": ""}
+{"text": "Describe the apply.voucher model in Odoo.", "response": "The apply.voucher model represents apply.voucher in the ERP system. It contains 9 fields and is used to manage apply.voucher data. Key fields include: customer_id, voucher_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "apply.voucher", "table_name": ""}
+{"text": "What modules define account.multipayment.credit?", "response": "The account.multipayment.credit model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.multipayment.credit", "table_name": ""}
+{"text": "How is snailmail.letter used in the system?", "response": "The snailmail.letter model represents Snailmail Letter in the ERP system. It contains 31 fields and is used to manage snailmail letter data. Key fields include: user_id, model, res_id, partner_id, company_id, report_template, attachment_id, attachment_datas, attachment_fname, color, cover, duplex, state, error_code, info_msg, display_name, reference, message_id, notification_ids, street, street2, zip, city, state_id, country_id, id, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "snailmail.letter", "table_name": ""}
+{"text": "Describe the many2many relations for intrawarehouse.transfer.", "response": "The intrawarehouse.transfer model has 3 relational fields: interawarehouse_transfer_ids -> intrawarehouse.transfer.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "Describe the many2many relations for stock.life.", "response": "The stock.life model has 6 relational fields: product_ids -> product.product; category_ids -> product.category; is_customer -> res.partner; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, category_ids, branch_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.life", "table_name": ""}
+{"text": "Show me the fields of pos.tracking.client.", "response": "The pos.tracking.client model has 11 fields: name, user_id, number, action, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 2, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.tracking.client", "table_name": ""}
+{"text": "Which fields in account.invoice.send are computed?", "response": "The account.invoice.send model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.invoice.send", "table_name": ""}
+{"text": "Describe the field structure of repair.tags.", "response": "The repair.tags model has 9 fields: name, color, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "repair.tags", "table_name": ""}
+{"text": "What are the technical details of project.task?", "response": "The project.task model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "project.task", "table_name": ""}
+{"text": "What data can be stored in overhead.time?", "response": "The overhead.time model has 10 fields: product, cost_hr, mrp_workcenter_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "overhead.time", "table_name": ""}
+{"text": "What is the mail.moderation model?", "response": "The mail.moderation model represents Channel black/white list in the ERP system. It contains 10 fields and is used to manage channel black/white list data. Key fields include: email, status, channel_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.moderation", "table_name": ""}
+{"text": "Tell me about the combo.option.item model.", "response": "The combo.option.item model represents combo.option.item in the ERP system. It contains 11 fields and is used to manage combo.option.item data. Key fields include: combo_option_id, product_id, product_variant_id, extra_price, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "combo.option.item", "table_name": ""}
+{"text": "What are the relationships in service.level.agreement?", "response": "The service.level.agreement model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "service.level.agreement", "table_name": ""}
+{"text": "Tell me about the invoice.printout.editor model.", "response": "The invoice.printout.editor model represents invoice.printout.editor in the ERP system. It contains 19 fields and is used to manage invoice.printout.editor data. Key fields include: name, invoice_ids, invoice_header_ids, invoice_header_filter_ids, invoice_table_ids, invoice_table_filter_ids, invoice_footer_ids, invoice_footer_filter_ids, template_id, orientation, paper_size_format, preview, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "invoice.printout.editor", "table_name": ""}
+{"text": "Describe the field structure of receipt.voucher.", "response": "The receipt.voucher model has 53 fields: create_by, create_date, payment_count, payment_ids, name, partner_id, partner_ids, voucher_date, bank_id, cheque_number, cheque_date, customer_invoice_ids, currency_id, remarks, company_id, branch_id, state, amount, receipt_voucher_line_ids, invoice_cutoff_date, customer_allowed_ids, is_cutoff_date, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, write_uid, write_date, __last_update. Field types distribution: many2one: 11, datetime: 3, integer: 6, one2many: 6, char: 6, many2many: 5, date: 5, text: 1, selection: 3, monetary: 1, boolean: 6.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "receipt.voucher", "table_name": ""}
+{"text": "What does the list.customer model represent?", "response": "The list.customer model represents list.customer in the ERP system. It contains 10 fields and is used to manage list.customer data. Key fields include: name, sale_amount, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "list.customer", "table_name": ""}
+{"text": "What modules define mail.shortcode?", "response": "The mail.shortcode model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.shortcode", "table_name": ""}
+{"text": "Show me the relational structure of pos.loyalty.category.", "response": "The pos.loyalty.category model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.loyalty.category", "table_name": ""}
+{"text": "What modules define hr.employee.public?", "response": "The hr.employee.public model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hr.employee.public", "table_name": ""}
+{"text": "What data can be stored in reset.view.arch.wizard?", "response": "The reset.view.arch.wizard model has 14 fields: view_id, view_name, has_diff, arch_diff, reset_mode, compare_view_id, arch_to_compare, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 2, boolean: 1, html: 1, selection: 1, text: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "reset.view.arch.wizard", "table_name": ""}
+{"text": "Show me the relational structure of asp.asm.stock.", "response": "The asp.asm.stock model has 19 relational fields: warehouse_id -> stock.warehouse; company_id -> res.company; user_id -> res.users; analytic_tag_ids -> account.analytic.tag; line_ids -> asp.asm.stock.line; move_ids -> stock.move; branch_id -> res.branch; product_ids -> product.product; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, product_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "asp.asm.stock", "table_name": ""}
+{"text": "What business logic is in vendor.payment.request?", "response": "To use the vendor.payment.request model, you need to provide values for required fields: branch_id. Readonly fields: name, amount_total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "vendor.payment.request", "table_name": ""}
+{"text": "How does report.sh_sale_reports.sh_tc_top_customers_doc relate to other models?", "response": "The report.sh_sale_reports.sh_tc_top_customers_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_tc_top_customers_doc", "table_name": ""}
+{"text": "What data can be stored in mailing.list.merge?", "response": "The mailing.list.merge model has 12 fields: src_list_ids, dest_list_id, merge_options, new_list_name, archive_src_lists, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, many2one: 3, selection: 1, char: 2, boolean: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mailing.list.merge", "table_name": ""}
+{"text": "Tell me about the journal.entries.report model.", "response": "The journal.entries.report model represents Journal Entries Report in the ERP system. It contains 12 fields and is used to manage journal entries report data. Key fields include: num, label, account_id, partner_id, analytic_account_id, amount_currency, currency_id, debit, credit, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "journal.entries.report", "table_name": ""}
+{"text": "Show me the relational structure of pos.gift.card.type.", "response": "The pos.gift.card.type model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.gift.card.type", "table_name": ""}
+{"text": "How to create records in gamification.goal?", "response": "To use the gamification.goal model, you need to provide values for required fields: definition_id, user_id, target_goal, current, state. Readonly fields: challenge_id, completeness, definition_description, definition_condition, definition_suffix, definition_display, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "gamification.goal", "table_name": ""}
+{"text": "What are the relationships in product.expire.report?", "response": "The product.expire.report model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.expire.report", "table_name": ""}
+{"text": "How do I use the sale.terms.and.conditions model?", "response": "To use the sale.terms.and.conditions model, you need to provide values for required fields: name, description. Readonly fields: activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.terms.and.conditions", "table_name": ""}
+{"text": "What are the technical details of account.open.chart?", "response": "The account.open.chart model is defined in module: account_parent. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.open.chart", "table_name": ""}
+{"text": "Show me the relational structure of sh.custom.model.purchase.order.", "response": "The sh.custom.model.purchase.order model has 14 relational fields: sh_position_field -> ir.model.fields; model_id -> ir.model; ref_model_id -> ir.model; ir_model_fields_obj -> ir.model.fields; ir_ui_view_obj -> ir.ui.view; inherit_view_obj -> ir.ui.view; groups -> res.groups; sh_selection_ids -> sh.model.fields.purchase.order.selection; relation_field_id -> ir.model.fields; selection_ids -> ir.model.fields.selection; related_field_id -> ir.model.fields; serialization_field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: groups.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.custom.model.purchase.order", "table_name": ""}
+{"text": "Show me the fields of restaurant.floor.", "response": "The restaurant.floor model has 14 fields: name, pos_config_id, background_image, background_color, table_ids, sequence, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 3, binary: 1, one2many: 1, integer: 2, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "restaurant.floor", "table_name": ""}
+{"text": "Describe the implementation of mr.approval.matrix.line.", "response": "The mr.approval.matrix.line model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mr.approval.matrix.line", "table_name": ""}
+{"text": "How to query module.advanced.upgrade data?", "response": "To use the module.advanced.upgrade model, you need to provide values for required fields: module_id. Readonly fields: module_shortdesc, module_name, module_author, module_installed_version, module_latest_version, module_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "module.advanced.upgrade", "table_name": ""}
+{"text": "Describe the phone.validation.mixin model in Odoo.", "response": "The phone.validation.mixin model represents Phone Validation Mixin in the ERP system. It contains 3 fields and is used to manage phone validation mixin data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "phone.validation.mixin", "table_name": ""}
+{"text": "What business logic is in budget.purchase.lines?", "response": "To use the budget.purchase.lines model, you need to provide values for required fields: purchase_budget_id, date_from, date_to, planned_amount. Readonly fields: name, analytic_group_id, currency_id, practical_amount, remaining_amount, theoritical_amount, percentage, company_id, is_above_budget, purchase_budget_state, account_tag_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "budget.purchase.lines", "table_name": ""}
+{"text": "What data can be stored in acrux.chat.pop.message?", "response": "The acrux.chat.pop.message model has 9 fields: name, info, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, html: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "acrux.chat.pop.message", "table_name": ""}
+{"text": "Show me the relational structure of report.equip3_pos_report.report_top_selling.", "response": "The report.equip3_pos_report.report_top_selling model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_pos_report.report_top_selling", "table_name": ""}
+{"text": "What are the technical details of intrawarehouse.transfer?", "response": "The intrawarehouse.transfer model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "What models are connected to stock.inventory.wizard?", "response": "The stock.inventory.wizard model has 3 relational fields: wizard_line_ids -> stock.inventory.wizard.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.inventory.wizard", "table_name": ""}
+{"text": "What data can be stored in approval.matrix.accounting?", "response": "The approval.matrix.accounting model has 47 fields: approval_matrix_type, change_amount, name, min_amount, max_amount, company_id, branch_id, filter_branch_ids, approval_matrix_line_ids, 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. Field types distribution: selection: 3, float: 3, char: 7, many2one: 10, many2many: 3, one2many: 5, date: 2, boolean: 5, integer: 5, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.accounting", "table_name": ""}
+{"text": "Can you explain the purpose of rn.approval_matrix_line?", "response": "The rn.approval_matrix_line model represents Receiving Notes Approval line in the ERP system. It contains 20 fields and is used to manage receiving notes approval line data. Key fields include: sequence, sequence1, approver, minimal_approver, approval_status, feedback, time_stamp, last_approved, approved, rn_approval_matrix_id1, picking_id, approved_users, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "rn.approval_matrix_line", "table_name": ""}
+{"text": "What are common use cases for account.financial.report?", "response": "To use the account.financial.report model, you need to provide values for required fields: name, sign. Readonly fields: level, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.financial.report", "table_name": ""}
+{"text": "List all fields in the receipt.voucher.line model.", "response": "The receipt.voucher.line model has 17 fields: receipt_voucher_id, invoice_id, invoice_date, untaxed_amount, tax_amount, total_invoice_amount, currency_id, amount_due, amount, total_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, date: 1, monetary: 6, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "receipt.voucher.line", "table_name": ""}
+{"text": "What methods are available in mrp.consumption.warning.line?", "response": "The mrp.consumption.warning.line model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.consumption.warning.line", "table_name": ""}
+{"text": "What are the relationships in account.account.map.line?", "response": "The account.account.map.line model has 11 relational fields: company_id -> res.company; account_id -> account.account; target_company -> res.company; target_account -> account.account; map_id -> account.account.map; create_uid -> res.users; write_uid -> res.users; line_ids -> account.account.map.line; child_company_id -> res.company; sales_line_ids -> account.tax.map.sales.line; purchase_line_ids -> account.tax.map.purchase.line. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.account.map.line", "table_name": ""}
+{"text": "What are the relationships in sale.order.repair?", "response": "The sale.order.repair model has 4 relational fields: repair_line_ids -> sale.order.repair.line; return_sale_order_id -> dev.rma.rma; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.repair", "table_name": ""}
+{"text": "Which fields in kitchen.production.record are computed?", "response": "The kitchen.production.record model is defined in module: equip3_kitchen_operations. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kitchen.production.record", "table_name": ""}
+{"text": "What methods are available in website.sale.payment.acquirer.onboarding.wizard?", "response": "The website.sale.payment.acquirer.onboarding.wizard model is defined in module: website_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.sale.payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "List all fields in the warehouse.capacity.report model.", "response": "The warehouse.capacity.report model has 12 fields: company_id, warehouse_ids, location_ids, filter_location_ids, hide_location, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 3, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "warehouse.capacity.report", "table_name": ""}
+{"text": "What are common use cases for pos.report.payment?", "response": "To use the pos.report.payment 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.report.payment", "table_name": ""}
+{"text": "How to query picking.return.line data?", "response": "To use the picking.return.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "picking.return.line", "table_name": ""}
+{"text": "What are the relationships in account.tax.report?", "response": "The account.tax.report model has 7 relational fields: country_id -> res.country; line_ids -> account.tax.report.line; root_line_ids -> account.tax.report.line; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.tax.report", "table_name": ""}
+{"text": "What does the ir.qweb.field.many2one model represent?", "response": "The ir.qweb.field.many2one model represents Qweb Field Many to One in the ERP system. It contains 3 fields and is used to manage qweb field many to one data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb.field.many2one", "table_name": ""}
+{"text": "What foreign keys exist in gamification.goal.definition?", "response": "The gamification.goal.definition model has 8 relational fields: model_id -> ir.model; model_inherited_ids -> ir.model; field_id -> ir.model.fields; field_date_id -> ir.model.fields; batch_distinctive_field -> ir.model.fields; action_id -> ir.actions.act_window; create_uid -> res.users; write_uid -> res.users. Many2many fields: model_inherited_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "gamification.goal.definition", "table_name": ""}
+{"text": "What methods are available in wizard.asset.create?", "response": "The wizard.asset.create model is defined in module: equip3_accounting_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "wizard.asset.create", "table_name": ""}
+{"text": "How is mail.notification used in the system?", "response": "The mail.notification model represents Message Notifications in the ERP system. It contains 15 fields and is used to manage message notifications data. Key fields include: mail_message_id, mail_id, res_partner_id, notification_status, is_read, read_date, failure_reason, sms_id, sms_number, notification_type, letter_id, failure_type, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.notification", "table_name": ""}
+{"text": "How to query account.setup.bank.manual.config data?", "response": "To use the account.setup.bank.manual.config model, you need to provide values for required fields: res_partner_bank_id, new_journal_name, acc_number, partner_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update, acc_type, sanitized_acc_number, company_id, journal_id. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.setup.bank.manual.config", "table_name": ""}
+{"text": "Which fields in internal.matrix.reject are computed?", "response": "The internal.matrix.reject model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "internal.matrix.reject", "table_name": ""}
+{"text": "Tell me about the account.fiscal.year model.", "response": "The account.fiscal.year model represents Fiscal Year in the ERP system. It contains 11 fields and is used to manage fiscal year data. Key fields include: name, date_from, date_to, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.fiscal.year", "table_name": ""}
+{"text": "What are the technical details of base_import.tests.models.char.required?", "response": "The base_import.tests.models.char.required model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.char.required", "table_name": ""}
+{"text": "How does asp.asm.stock relate to other models?", "response": "The asp.asm.stock model has 19 relational fields: warehouse_id -> stock.warehouse; company_id -> res.company; user_id -> res.users; analytic_tag_ids -> account.analytic.tag; line_ids -> asp.asm.stock.line; move_ids -> stock.move; branch_id -> res.branch; product_ids -> product.product; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_tag_ids, product_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "asp.asm.stock", "table_name": ""}
+{"text": "What does the orderline.orderline model represent?", "response": "The orderline.orderline model represents Sale Blanket Order line in the ERP system. It contains 25 fields and is used to manage sale blanket order line data. Key fields include: reverse_id, product_id, name, quantity, remaining_quantity, product_uom, price_unit, tax_id, price_subtotal, ordered_qty, delivered_qty, qty_invoiced, undelivered_qty, sequence, sequence2, company_id, analytic_tag_ids, price_tax, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "orderline.orderline", "table_name": ""}
+{"text": "Describe the implementation of account.cashbox.wizard.line.", "response": "The account.cashbox.wizard.line model is defined in module: equip3_pos_cashbox. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.cashbox.wizard.line", "table_name": ""}
+{"text": "Can you explain the purpose of export.efaktur?", "response": "The export.efaktur model represents export.efaktur in the ERP system. It contains 12 fields and is used to manage export.efaktur data. Key fields include: partner_id, tax_report_id, date_from, date_to, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "export.efaktur", "table_name": ""}
+{"text": "Describe the field structure of send.message.mass.", "response": "The send.message.mass model has 10 fields: message_chat_ids, conversation_id, connector_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "send.message.mass", "table_name": ""}
+{"text": "Describe the mr.internal_transfer_line model in Odoo.", "response": "The mr.internal_transfer_line model represents mr.internal_transfer_line in the ERP system. It contains 22 fields and is used to manage mr.internal_transfer_line data. Key fields include: mr_id, no, product_id, description, uom_id, source_location, source_warehouse_id, current_qty, virtual_available, qty_transfer, mr_ir_wizard, mr_line_id, filter_warehouse_ids, filter_location_ids, dest_warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mr.internal_transfer_line", "table_name": ""}
+{"text": "Tell me about the res.currency model.", "response": "The res.currency model represents Currency in the ERP system. It contains 51 fields and is used to manage currency data. Key fields include: 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, display_rounding_warning, name, symbol, rate, conversion, rate_ids, rounding, decimal_places, active, position, date, currency_unit_label, currency_subunit_label, tax_rate_ids, tax_rate, tax_conversion, is_taxes_rate, company_id, converted_currency, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.currency", "table_name": ""}
+{"text": "What data can be stored in rma.reject.reason?", "response": "The rma.reject.reason model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "rma.reject.reason", "table_name": ""}
+{"text": "What data can be stored in website.route?", "response": "The website.route model has 8 fields: path, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "website.route", "table_name": ""}
+{"text": "What models are connected to base.partner.merge.automatic.wizard?", "response": "The base.partner.merge.automatic.wizard model has 6 relational fields: current_line_id -> base.partner.merge.line; line_ids -> base.partner.merge.line; partner_ids -> res.partner; dst_partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.partner.merge.automatic.wizard", "table_name": ""}
+{"text": "How to query equip3.reporting.asset.wizard data?", "response": "To use the equip3.reporting.asset.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "equip3.reporting.asset.wizard", "table_name": ""}
+{"text": "How is pos.tracking.client implemented technically?", "response": "The pos.tracking.client model is defined in module: equip3_pos_general. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.tracking.client", "table_name": ""}
+{"text": "How is sh.qc.alert.tags used in the system?", "response": "The sh.qc.alert.tags model represents Quality Alert Tags in the ERP system. It contains 10 fields and is used to manage quality alert tags data. Key fields include: name, color, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.qc.alert.tags", "table_name": ""}
+{"text": "How is report.stock.quantity implemented technically?", "response": "The report.stock.quantity model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.stock.quantity", "table_name": ""}
+{"text": "What is the approval.matrix.purchase.order.line model?", "response": "The approval.matrix.purchase.order.line model represents Approval Matrix Purchase Order Line in the ERP system. It contains 20 fields and is used to manage approval matrix purchase order line data. Key fields include: sequence, user_ids, minimum_approver, approval_matrix_purchase_order, sequence2, approved_users, state_char, time_stamp, feedback, last_approved, approved, order_id, approver_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.purchase.order.line", "table_name": ""}
+{"text": "Describe the implementation of asset.asset.revalue.", "response": "The asset.asset.revalue model is defined in module: equip3_accounting_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "asset.asset.revalue", "table_name": ""}
+{"text": "What are the technical details of res.partner.bank?", "response": "The res.partner.bank model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.partner.bank", "table_name": ""}
+{"text": "What business logic is in purchase.order.split?", "response": "To use the purchase.order.split 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.order.split", "table_name": ""}
+{"text": "What data can be stored in pos.promotion.tebus.murah?", "response": "The pos.promotion.tebus.murah model has 13 fields: active, promotion_id, product_id, price, quantity, product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 4, float: 1, integer: 2, many2many: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.promotion.tebus.murah", "table_name": ""}
+{"text": "What models are connected to pos.voucher?", "response": "The pos.voucher model has 15 relational fields: customer_id -> res.partner; user_id -> res.users; pos_order_id -> pos.order; pos_order_line_id -> pos.order.line; use_history_ids -> pos.voucher.use.history; generated_source_id -> generate.pos.voucher; limit_restrict_product_ids -> product.product; pos_category_ids -> pos.category; company_id -> res.company; receipt_template_id -> pos.receipt.template; source_document_id -> generate.pos.voucher; brand_ids -> product.brand; member_type_ids -> pos.loyalty.category; create_uid -> res.users; write_uid -> res.users. Many2many fields: limit_restrict_product_ids, pos_category_ids, brand_ids, member_type_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.voucher", "table_name": ""}
+{"text": "How to query allfresh.consignment.report data?", "response": "To use the allfresh.consignment.report model, you need to provide values for required fields: none. Readonly fields: date_order, barcode, product_id, qty, price, margin, total_margin, consignment_move_id, currency_id, company_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "allfresh.consignment.report", "table_name": ""}
+{"text": "What foreign keys exist in z.report.wizard?", "response": "The z.report.wizard model has 5 relational fields: pos_session_ids -> pos.session; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_session_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "z.report.wizard", "table_name": ""}
+{"text": "Show me the relational structure of credit.limit.product.brand.", "response": "The credit.limit.product.brand model has 7 relational fields: partner_id -> res.partner; brand_id -> product.brand; limit_request_id -> limit.request; brand_ids -> product.brand; signature_country_id -> res.country; create_uid -> res.users; write_uid -> res.users. Many2many fields: brand_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "credit.limit.product.brand", "table_name": ""}
+{"text": "Can you explain the purpose of base?", "response": "The base model represents Base in the ERP system. It contains 3 fields and is used to manage base data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base", "table_name": ""}
+{"text": "How does purchase.price.history relate to other models?", "response": "The purchase.price.history model has 7 relational fields: name -> purchase.order.line; partner_id -> res.partner; variant_id -> product.product; purchase_order_id -> purchase.order; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.price.history", "table_name": ""}
+{"text": "What fields does internal.transfer.line have?", "response": "The internal.transfer.line model has 34 fields: qty_cancel, product_line, product_id, qty, uom, source_location_id, destination_location_id, transfer_qty, return_qty, total_trf, scheduled_date, filter_source_loc, filter_dest_loc, current_qty, filter_available_product_ids, analytic_account_group_ids, status, description, mr_line_id, source_document, requested_by, company_id, picking_id, itr_in_progress_qty, itr_remaining_qty, sequence, current_dest_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 9, many2one: 10, datetime: 4, many2many: 4, selection: 1, text: 1, char: 3, one2many: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "internal.transfer.line", "table_name": ""}
+{"text": "How is purchase.flow.wizard used in the system?", "response": "The purchase.flow.wizard model represents purchase.flow.wizard in the ERP system. It contains 8 fields and is used to manage purchase.flow.wizard data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.flow.wizard", "table_name": ""}
+{"text": "How do I use the global.search.fields model?", "response": "To use the global.search.fields model, you need to provide values for required fields: ttype. Readonly fields: name, related_model_id, ttype, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "global.search.fields", "table_name": ""}
+{"text": "What foreign keys exist in sms.template?", "response": "The sms.template model has 7 relational fields: model_id -> ir.model; sidebar_action_id -> ir.actions.act_window; model_object_field -> ir.model.fields; sub_object -> ir.model; sub_model_object_field -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sms.template", "table_name": ""}
+{"text": "What fields does sale.order.cancel have?", "response": "The sale.order.cancel model has 10 fields: order_id, display_invoice_alert, display_delivery_alert, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, boolean: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sale.order.cancel", "table_name": ""}
+{"text": "What are the technical details of ir.ui.menu?", "response": "The ir.ui.menu model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.ui.menu", "table_name": ""}
+{"text": "List all fields in the project.create.sale.order model.", "response": "The project.create.sale.order model has 16 fields: project_id, company_id, partner_id, commercial_partner_id, pricing_type, link_selection, sale_order_id, line_ids, info_invoice, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, selection: 2, one2many: 1, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.create.sale.order", "table_name": ""}
+{"text": "What are the relationships in sale.order.line?", "response": "The sale.order.line model has 57 relational fields: order_id -> sale.order; invoice_lines -> account.move.line; product_uom_category_id -> uom.category; product_custom_attribute_value_ids -> product.attribute.custom.value; product_no_variant_attribute_value_ids -> product.template.attribute.value; salesman_id -> res.users; currency_id -> res.currency; order_partner_id -> res.partner; analytic_tag_ids -> account.analytic.tag; sale_order_option_ids -> sale.order.option; product_template_attribute_value_ids -> product.template.attribute.value; purchase_line_ids -> purchase.order.line; product_packaging -> product.packaging; route_id -> stock.location.route; move_ids -> stock.move; warehouse_id -> stock.warehouse; linked_line_id -> sale.order.line; option_line_ids -> sale.order.line; project_id -> project.project; task_id -> project.task; location_id -> stock.location; analytic_line_ids -> account.analytic.line; customer_id -> res.partner; user_id -> res.users; product_id -> product.product; company_id -> res.company; account_tag_ids -> account.analytic.tag; analytic_account_id -> account.analytic.account; location_dest_id -> stock.location; line_warehouse_id -> stock.warehouse; line_warehouse_id_new -> stock.warehouse; branch_id -> res.branch; delivery_address_id -> res.partner; filter_delivery_address_id -> res.partner; product_template_id -> product.template; product_uom -> uom.uom; tax_id -> account.tax; res_product_uom -> uom.uom; brand_ids -> product.brand; customer_voucher_id -> customer.voucher; parent_id -> sale.order.line; lot_id -> stock.production.lot; pos_branch_id -> res.branch; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: invoice_lines, product_no_variant_attribute_value_ids, analytic_tag_ids, product_template_attribute_value_ids, account_tag_ids, filter_delivery_address_id, tax_id, brand_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.line", "table_name": ""}
+{"text": "What are common use cases for sh.mrp.allow.qc.measurement?", "response": "To use the sh.mrp.allow.qc.measurement model, you need to provide values for required fields: none. Readonly fields: product_id, sh_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.mrp.allow.qc.measurement", "table_name": ""}
+{"text": "Describe the implementation of purchase.line.wiz.", "response": "The purchase.line.wiz model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.line.wiz", "table_name": ""}
+{"text": "Show me the fields of kitchen.safety.stock.", "response": "The kitchen.safety.stock model has 13 fields: name, company_id, is_branch_required, branch_id, warehouse_id, stock_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 5, boolean: 1, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "kitchen.safety.stock", "table_name": ""}
+{"text": "What is the approval.matrix.purchase.request model?", "response": "The approval.matrix.purchase.request model represents Approval Matrix Purchase Reqest in the ERP system. It contains 48 fields and is used to manage approval matrix purchase reqest data. Key fields include: name, company_id, branch_id, department_id, minimum_amt, maximum_amt, is_purchase_request_department, approval_matrix_purchase_request_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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.purchase.request", "table_name": ""}
+{"text": "How to create records in website.rewrite?", "response": "To use the website.rewrite 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "website.rewrite", "table_name": ""}
+{"text": "What data can be stored in dev.credit.note.wizard?", "response": "The dev.credit.note.wizard model has 14 fields: rma_id, product_line_ids, picking_type_code, sale_id, purchase_id, purchase_ids, sale_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, one2many: 1, selection: 1, many2many: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "dev.credit.note.wizard", "table_name": ""}
+{"text": "How does measure.for.packaging relate to other models?", "response": "The measure.for.packaging model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "measure.for.packaging", "table_name": ""}
+{"text": "What does the stock.lot.serialize model represent?", "response": "The stock.lot.serialize model represents Stock Lot Serialize in the ERP system. It contains 9 fields and is used to manage stock lot serialize data. Key fields include: picking_id, stock_move_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.lot.serialize", "table_name": ""}
+{"text": "What are the technical details of report.sh_purchase_reports.sh_payment_pr_report_doc?", "response": "The report.sh_purchase_reports.sh_payment_pr_report_doc model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_purchase_reports.sh_payment_pr_report_doc", "table_name": ""}
+{"text": "Show me the fields of crm.salesperson.tracking.report.", "response": "The crm.salesperson.tracking.report model has 9 fields: sales_person, current_datetime, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, date: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.salesperson.tracking.report", "table_name": ""}
+{"text": "What operations can I perform on print.prenumbered.checks?", "response": "To use the print.prenumbered.checks model, you need to provide values for required fields: next_check_number. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "print.prenumbered.checks", "table_name": ""}
+{"text": "List all fields in the sh.tsp.top.selling.product.wizard model.", "response": "The sh.tsp.top.selling.product.wizard model has 21 fields: type, date_to, date_compare_from, date_compare_to, no_of_top_item, product_uom_qty, team_id, company_ids, company_id, top_product_ids, top_product_compare_ids, lost_product_ids, new_product_ids, date_from, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, datetime: 7, integer: 2, float: 1, many2one: 4, many2many: 1, one2many: 4, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.tsp.top.selling.product.wizard", "table_name": ""}
+{"text": "What fields does nsfp.registration.wizard have?", "response": "The nsfp.registration.wizard model has 10 fields: fiscal_year, start, end, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "nsfp.registration.wizard", "table_name": ""}
+{"text": "What operations can I perform on mailing.contact?", "response": "To use the mailing.contact model, you need to provide values for required fields: none. Readonly fields: opt_out, email_normalized, is_blacklisted, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mailing.contact", "table_name": ""}
+{"text": "Which fields in crm.salesperson.tracking are computed?", "response": "The crm.salesperson.tracking model is defined in module: equip3_crm_tracking. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.salesperson.tracking", "table_name": ""}
+{"text": "What operations can I perform on account.fiscal.position.tax?", "response": "To use the account.fiscal.position.tax model, you need to provide values for required fields: position_id, tax_src_id. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.fiscal.position.tax", "table_name": ""}
+{"text": "How does base_import.tests.models.char.stillreadonly relate to other models?", "response": "The base_import.tests.models.char.stillreadonly model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.char.stillreadonly", "table_name": ""}
+{"text": "What methods are available in mailing.list?", "response": "The mailing.list model is defined in module: mass_mailing. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mailing.list", "table_name": ""}
+{"text": "What are the relationships in material.request.line.show.stock?", "response": "The material.request.line.show.stock model has 6 relational fields: stock_quant_id -> material.request.show.stock; product_id -> product.product; location_id -> stock.location; warehouse_id -> stock.warehouse; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "material.request.line.show.stock", "table_name": ""}
+{"text": "What data can be stored in pmps.adv.wizard.product.line.specific?", "response": "The pmps.adv.wizard.product.line.specific model has 13 fields: pmps_adv_wizard_id_specific, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, float: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pmps.adv.wizard.product.line.specific", "table_name": ""}
+{"text": "What models are connected to membership.invoice?", "response": "The membership.invoice model has 3 relational fields: product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "membership.invoice", "table_name": ""}
+{"text": "What data can be stored in account.payment?", "response": "The account.payment model has 398 fields: partner_type, check_amount_in_words, check_manual_sequencing, check_number, name, payment_transaction_id, payment_token_id, related_partner_ids, is_prepayment, prepayment_journal_id, start_date, end_date, recurring_interval, recurring_interval_unit, stop_recurring_interval, stop_recurring_interval_unit, revenue_account, apply_manual_currency_exchange, manual_currency_exchange_rate, active_manual_currency_rate, user_id, move_id, is_reconciled, is_matched, partner_bank_id, is_internal_transfer, qr_code, payment_method_id, available_payment_method_ids, hide_payment_method, amount, payment_type, payment_reference, currency_id, partner_id, destination_account_id, reconciled_invoice_ids, reconciled_invoices_count, reconciled_bill_ids, reconciled_bills_count, reconciled_statement_ids, reconciled_statements_count, payment_method_code, show_partner_bank_account, require_partner_bank_account, country_code, voucher_id, receipt_voucher_id, branch_id, payment_receipt_approval_matrix_id, is_receipt_approval_matrix, is_approve_button, approved_matrix_ids, approval_matrix_line_id, approval_invoice_id, administration, analytic_group_ids, administration_account, administration_fee, payment_transaction_credit, payment_transaction_credit_count, payment_transaction_debit, payment_transaction_debit_count, reconcile_invisible, online_payment_status, estimasi_transfer, af_move_id, origin, pos_branch_id, pos_session_id, available_partner_bank_ids, is_pos_void_fixed, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, highest_name, ref, move_type, type_name, suitable_journal_ids, company_id, is_move_sent, payment_state, invoice_user_id, invoice_origin, invoice_source_email, preferred_payment_method_id, debit_origin_id, debit_note_ids, debit_note_count, edi_document_ids, edi_state, edi_error_count, edi_web_services_to_process, edi_show_cancel_button, edi_show_abandon_cancel_button, edi_error_message, edi_blocking_level, loan_line_id, loan_id, attn, signature, journal_bank_id, payment_proof, tax_payment_date, payment_fields_boolean, ppn, pph, tax_paid_status, file_name, payment_date, tax_payment_move_id, tax_pay_seprately_amount, is_edit_data, asset_depreciation_ids, transaction_ids, authorized_transaction_ids, purchase_vendor_bill_id, purchase_id, sh_invoice_recurring_order_id, period_id, fiscal_year, stock_move_id, stock_valuation_layer_ids, auto_reverse, auto_reverse_date, auto_reverse_journal_id, auto_reverse_date_mode, auto_reversal_entry_date, auto_reversed, to_delete_from_svl, pos_order_ids, team_id, partner_shipping_id, is_consignment, consignment_start_date, consignment_end_date, consignment_pos_ids, l10n_id_tax_number, l10n_id_attachment_id, l10n_id_csv_created, l10n_id_need_kode_transaksi, landed_costs_ids, landed_costs_visible, website_id, is_line, discount_method, discount_amount, discount_type, discount_amt, amount_untaxed, discount_amt_line, discount_account_id, discount_amount_line, warranty_invoice, warranty_reg_id, related_project_id, show_intrest, interest, check_date, check_month, repair_ids, sh_invoice_barcode_mobile, sh_invoice_bm_is_cont_scan, target_commission_id, commission_count, down_payment_amount, total_down_payment_amount, is_down_payment, down_payment_purchase_id, report_template_id1, report_template_id, amount_to_text, timesheet_ids, timesheet_count, approval_matrix_id, is_invoice_approval_matrix, state1, state2, is_register_payment_done, invoice_origin_id, invoice_origin_date, reason, ref_no, request_partner_id, is_fiscal_book_exclude, received_date, visible_received_date, to_approve_state_payment_count, show_name_warning, date, posted_before, to_check, journal_id, company_currency_id, line_ids, commercial_partner_id, payment_id, statement_line_id, amount_tax, amount_tax2, subtotal_amount, amount_total, amount_untaxed_signed, amount_tax_signed, amount_total_signed, amount_residual_signed, amount_by_group, tax_cash_basis_rec_id, tax_cash_basis_move_id, auto_post, reversed_entry_id, reversal_move_id, fiscal_position_id, invoice_date, invoice_date_due, invoice_payment_term_id, invoice_line_ids, invoice_incoterm_id, display_qr_code, qr_code_method, invoice_outstanding_credits_debits_widget, invoice_has_outstanding, invoice_payments_widget, invoice_vendor_bill_id, invoice_partner_display_name, invoice_cash_rounding_id, invoice_filter_type_domain, bank_partner_id, invoice_has_matching_suspense_amount, tax_lock_date_message, has_reconciled_entries, show_reset_to_draft_button, restrict_mode_hash_table, secure_sequence_number, inalterable_hash, string_to_hash, mr_show_analytic_account, journal_entries_template, analytic_tag_dynamic, credit_note_expiry_date, expiry_date, approvers_ids, approved_user_ids, internal_tf_id, reversal_avail, date_id, is_record_created, is_merge, is_merge_to, new_invoice_id, count_merged_invoice, is_button_update_invisible, narration, multi_discount, is_intercompany_transaction, account_asset_id, state, customer_deposit_ids, vendor_deposit_ids, status_code, nomor_seri, ebupot_id, code, check, check_invisible, total_tax_ppn, total_inv_ppn, subtotal_inv_ppn, tax_number_bupot, kode_dokumen, kode_seri, nomor_seri_bupot, check_invisible_ebupot, ebupot_template, l10n_id_replace_invoice_id, l10n_id_kode_transaksi, is_upload_djp, is_upload_djp_cn, pajak_express_id, approval_url, efaktur_url, nomor_dokumen_pendukung, hide_button_upload, hide_button_upload_cn, tipe_pembayaran, keterangan_tambahan, uang_muka, uang_muka_ppn, uang_muka_ppnbm, signature_country_id, signature_city_id, nomor_seri_domain, current_rate, is_company_curr, current_inverse_rate, inverse_rate_visible, amount_residual, tax_rate, taxes_base_price, sales_times_tax_rate, tax_applies_on, manual_currency_exchange_inverse_rate, currency_revaluation_id, children_ids, currency_revaluation_ref_id, currency_revaluation_count, pettycash_id, is_petty_cash_voucher, sale_order_reference_id, filter_sale_order_reference_ids, exchange_id, exchange_stage, exchange_date, exchange_status, assembly_id, stock_scrap_id, kitchen_id, purchase_order_id, swo, swo_ids, amount_swo, is_services_orders, finish_good_rework_id, sale_order_ids, filter_sale_order_ids, purchase_order_ids, filter_purchase_order_ids, picking_ids, filter_picking_ids, sale_order_ids_boolean, purchase_order_ids_boolean, picking_ids_boolean, cashback_line_ids, show_cashback, is_cn_from_cashback, so_cashback_id, is_dp, payments_date, manual_change_status_code, return_picking_ids, picking_id, nomor_seri_faktur_pajak_new, rma_id, receiving_note_names, receiving_note_dates, account_invoice_ids, sequence, pos_order_id, is_from_pos_receivable, is_from_pos_cash_management, is_from_pos_cash_difference, is_from_pos_umum, is_from_pos_member, is_from_pos_member_gabungan, is_from_pos_partner, is_pkp_record, deposit_account_journal_id, create_from_session_id, inventory_id, _barcode_scanned, campaign_id, source_id, medium_id, access_url, access_token, access_warning, sequence_prefix, sequence_number. Field types distribution: selection: 24, char: 49, boolean: 84, many2one: 100, many2many: 26, date: 20, integer: 23, float: 20, monetary: 14, one2many: 22, datetime: 4, text: 5, html: 4, binary: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.payment", "table_name": ""}
+{"text": "What foreign keys exist in pos.order.line.promotion?", "response": "The pos.order.line.promotion model has 4 relational fields: pos_order_line_id -> pos.order.line; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.order.line.promotion", "table_name": ""}
+{"text": "What are common use cases for approval.matrix.purchase.request.line?", "response": "To use the approval.matrix.purchase.request.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: sequence2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.purchase.request.line", "table_name": ""}
+{"text": "What is the delivery.carrier model?", "response": "The delivery.carrier model represents Shipping Methods in the ERP system. It contains 35 fields and is used to manage shipping methods data. Key fields include: name, active, sequence, integration_level, prod_environment, debug_logging, company_id, product_id, invoice_policy, country_ids, state_ids, zip_from, zip_to, margin, free_over, amount, can_generate_return, return_label_on_delivery, get_return_label_from_portal, fixed_price, price_rule_ids, website_description, delivery_type, website_published, website_id, is_published, can_publish, website_url, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "delivery.carrier", "table_name": ""}
+{"text": "What is the sms.template.preview model?", "response": "The sms.template.preview model represents SMS Template Preview in the ERP system. It contains 13 fields and is used to manage sms template preview data. Key fields include: sms_template_id, lang, model_id, body, resource_ref, no_record, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sms.template.preview", "table_name": ""}
+{"text": "What are the available fields for account.tax.repartition.line.template?", "response": "The account.tax.repartition.line.template model has 16 fields: factor_percent, repartition_type, account_id, invoice_tax_id, refund_tax_id, tag_ids, use_in_tax_closing, plus_report_line_ids, minus_report_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 1, selection: 1, many2one: 5, many2many: 3, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.tax.repartition.line.template", "table_name": ""}
+{"text": "What are the available fields for ks_custom_report.ks_column?", "response": "The ks_custom_report.ks_column model has 25 fields: name, ks_cr_model_id, ks_model_field_chan, ks_model_name, ks_cr_field_id, ks_incl_search_filter, ks_incl_group_filter, sequence, ks_operator, ks_value, ks_visible_operator_fields, ks_visible_date_fields, ks_alter_values, ks_year, ks_month, ks_week, ks_day, ks_hour, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 4, boolean: 5, integer: 7, selection: 1, float: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks_custom_report.ks_column", "table_name": ""}
+{"text": "How does resource.test relate to other models?", "response": "The resource.test model has 5 relational fields: resource_id -> resource.resource; company_id -> res.company; resource_calendar_id -> resource.calendar; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "resource.test", "table_name": ""}
+{"text": "What are the relationships in stock.return.picking.inter.company?", "response": "The stock.return.picking.inter.company model has 6 relational fields: product_id -> product.product; uom_id -> product.uom; wizard_id -> return.inter.transfer.company; move_id -> stock.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.return.picking.inter.company", "table_name": ""}
+{"text": "What modules define pos.combo.limit?", "response": "The pos.combo.limit model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.combo.limit", "table_name": ""}
+{"text": "Describe the field structure of sh.model.fields.purchase.order.selection.", "response": "The sh.model.fields.purchase.order.selection model has 11 fields: sh_field_po_id, value, name, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.model.fields.purchase.order.selection", "table_name": ""}
+{"text": "What are the technical details of website.rewrite?", "response": "The website.rewrite model is defined in module: website. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.rewrite", "table_name": ""}
+{"text": "What modules define mrp.bom.line?", "response": "The mrp.bom.line model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.bom.line", "table_name": ""}
+{"text": "How to query pos.gift.card.recharge data?", "response": "To use the pos.gift.card.recharge model, you need to provide values for required fields: none. Readonly fields: card_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.gift.card.recharge", "table_name": ""}
+{"text": "Show me the relational structure of account.payment.method.", "response": "The account.payment.method model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.payment.method", "table_name": ""}
+{"text": "Which fields in gamification.goal.wizard are computed?", "response": "The gamification.goal.wizard model is defined in module: gamification. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "gamification.goal.wizard", "table_name": ""}
+{"text": "What are the available fields for approval.matrix.sale.order.lines?", "response": "The approval.matrix.sale.order.lines model has 23 fields: approval_matrix, order_id, user_name_ids, sequence, sequence2, minimum_approver, state_char, time_stamp, feedback, last_approved, approved, approved_users, signature, approval_type, approver_state, bo_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, many2many: 2, integer: 4, text: 1, datetime: 4, char: 2, boolean: 1, binary: 1, selection: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.sale.order.lines", "table_name": ""}
+{"text": "What fields does queue.job.channel have?", "response": "The queue.job.channel model has 12 fields: name, complete_name, parent_id, job_function_ids, removal_interval, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 3, one2many: 1, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "queue.job.channel", "table_name": ""}
+{"text": "What modules define whatsapp.template?", "response": "The whatsapp.template model is defined in module: equip3_crm_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "whatsapp.template", "table_name": ""}
+{"text": "Tell me about the account.analytic.distribution model.", "response": "The account.analytic.distribution model represents Analytic Account Distribution in the ERP system. It contains 12 fields and is used to manage analytic account distribution data. Key fields include: account_id, percentage, name, tag_id, analytic_group_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.analytic.distribution", "table_name": ""}
+{"text": "What business logic is in mail.notification?", "response": "To use the mail.notification model, you need to provide values for required fields: mail_message_id, notification_type. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.notification", "table_name": ""}
+{"text": "What methods are available in account.aged.trial.balance?", "response": "The account.aged.trial.balance model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.aged.trial.balance", "table_name": ""}
+{"text": "How is sh.sale.product.indent.xls used in the system?", "response": "The sh.sale.product.indent.xls model represents Sale Product Indent Xls Report in the ERP system. It contains 9 fields and is used to manage sale product indent xls report data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.sale.product.indent.xls", "table_name": ""}
+{"text": "What are common use cases for sale.order.report?", "response": "To use the sale.order.report model, you need to provide values for required fields: start_date, end_date, company_id. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.order.report", "table_name": ""}
+{"text": "Tell me about the ks.sales.forecast model.", "response": "The ks.sales.forecast model represents This model is to predict sales on the bases of historical data with trending and seasonal factor in the ERP system. It contains 69 fields and is used to manage this model is to predict sales on the bases of historical data with trending and seasonal factor data. Key fields include: ks_name, ks_is_file, ks_file_type, ks_import_file, ks_file_name, ks_is_method_change, ks_forecast_method, ks_default_forecast_method, ks_predicted_forecast_method, ks_model, ks_start_date, ks_end_date, ks_forecast_base, ks_product_ids, ks_p, ks_d, ks_q, ks_P, ks_D, ks_Q, ks_m, ks_trend, ks_forecast_unit, ks_forecast_period, ks_is_predicted, ks_is_predicted_method, ks_chart_data, ks_report_data, ks_graph_view, ks_outcome, ks_danger_outcome, ks_resp, ks_resd, ks_resq, ks_sp, ks_sd, ks_sq, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks.sales.forecast", "table_name": ""}
+{"text": "Show me the relational structure of account.tax.template.", "response": "The account.tax.template model has 8 relational fields: chart_template_id -> account.chart.template; children_tax_ids -> account.tax.template; invoice_repartition_line_ids -> account.tax.repartition.line.template; refund_repartition_line_ids -> account.tax.repartition.line.template; tax_group_id -> account.tax.group; cash_basis_transition_account_id -> account.account.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: children_tax_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.tax.template", "table_name": ""}
+{"text": "What methods are available in account.bank.statement.line?", "response": "The account.bank.statement.line model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.bank.statement.line", "table_name": ""}
+{"text": "Can you explain the purpose of blanket.quotation?", "response": "The blanket.quotation model represents blanket.quotation in the ERP system. It contains 8 fields and is used to manage blanket.quotation data. Key fields include: wiz_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "blanket.quotation", "table_name": ""}
+{"text": "Show me the fields of account.cashbox.wizard.bank.line.", "response": "The account.cashbox.wizard.bank.line model has 15 fields: account_cashbox_wizard_bank_id, payment_method_id, bank_value, cashbox_id, currency_id, pos_config_id, pos_session_id, is_closing_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, float: 1, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.cashbox.wizard.bank.line", "table_name": ""}
+{"text": "Which fields in apply.voucher are computed?", "response": "The apply.voucher model is defined in module: equip3_sale_loyalty. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "apply.voucher", "table_name": ""}
+{"text": "What is the mrp.bom.operation model?", "response": "The mrp.bom.operation model represents MRP BoM Operation in the ERP system. It contains 9 fields and is used to manage mrp bom operation data. Key fields include: sequence, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.bom.operation", "table_name": ""}
+{"text": "What fields does pos.coupon.apply.code have?", "response": "The pos.coupon.apply.code model has 8 fields: coupon_code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.coupon.apply.code", "table_name": ""}
+{"text": "Show me the relational structure of account.tax.report.line.", "response": "The account.tax.report.line model has 7 relational fields: tag_ids -> account.account.tag; report_action_id -> ir.actions.act_window; children_line_ids -> account.tax.report.line; parent_id -> account.tax.report.line; report_id -> account.tax.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.tax.report.line", "table_name": ""}
+{"text": "How to create records in purchase.tender.xls.report?", "response": "To use the purchase.tender.xls.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.tender.xls.report", "table_name": ""}
+{"text": "How does report.sh_inventory_mrp_qc.mrp_quality_check_doc relate to other models?", "response": "The report.sh_inventory_mrp_qc.mrp_quality_check_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_inventory_mrp_qc.mrp_quality_check_doc", "table_name": ""}
+{"text": "What models are connected to currency.invoice.revaluation?", "response": "The currency.invoice.revaluation model has 5 relational fields: journal_id -> account.journal; income_unrealized_account -> account.account; expense_unrealized_account -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "currency.invoice.revaluation", "table_name": ""}
+{"text": "Describe the implementation of sh.mrp.allow.qc.measurement.", "response": "The sh.mrp.allow.qc.measurement model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.mrp.allow.qc.measurement", "table_name": ""}
+{"text": "Describe the stock.rule model in Odoo.", "response": "The stock.rule model represents Stock Rule in the ERP system. It contains 29 fields and is used to manage stock rule data. Key fields include: name, active, group_propagation_option, group_id, sequence, company_id, location_id, location_src_id, route_id, route_company_id, procure_method, route_sequence, picking_type_id, picking_type_code_domain, delay, partner_address_id, propagate_cancel, warehouse_id, propagate_warehouse_id, auto, rule_message, action, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.rule", "table_name": ""}
+{"text": "Can you explain the purpose of sh.tsp.top.purchasing.product?", "response": "The sh.tsp.top.purchasing.product model represents Top purchasing product persistence model to  used in snippet or any other places in the ERP system. It contains 9 fields and is used to manage top purchasing product persistence model to  used in snippet or any other places data. Key fields include: product_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.tsp.top.purchasing.product", "table_name": ""}
+{"text": "Describe the auditlog.autovacuum model in Odoo.", "response": "The auditlog.autovacuum model represents Auditlog - Delete old logs in the ERP system. It contains 7 fields and is used to manage auditlog - delete old logs data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "auditlog.autovacuum", "table_name": ""}
+{"text": "Describe the many2many relations for stock.move.", "response": "The stock.move model has 92 relational fields: company_id -> res.company; product_uom -> uom.uom; product_uom_category_id -> uom.category; product_tmpl_id -> product.template; location_id -> stock.location; location_dest_id -> stock.location; partner_id -> res.partner; move_dest_ids -> stock.move; move_orig_ids -> stock.move; picking_partner_id -> res.partner; backorder_id -> stock.picking; scrap_ids -> stock.scrap; group_id -> procurement.group; rule_id -> stock.rule; picking_type_id -> stock.picking.type; inventory_id -> stock.inventory; move_line_ids -> stock.move.line; move_line_nosuggest_ids -> stock.move.line; origin_returned_move_id -> stock.move; returned_move_ids -> stock.move; restrict_partner_id -> res.partner; route_ids -> stock.location.route; warehouse_id -> stock.warehouse; package_level_id -> stock.package_level; orderpoint_id -> stock.warehouse.orderpoint; lot_ids -> stock.production.lot; created_production_id -> mrp.production; production_id -> mrp.production; raw_material_production_id -> mrp.production; unbuild_id -> mrp.unbuild; consume_unbuild_id -> mrp.unbuild; allowed_operation_ids -> mrp.routing.workcenter; operation_id -> mrp.routing.workcenter; workorder_id -> mrp.workorder; bom_line_id -> mrp.bom.line; byproduct_id -> mrp.bom.byproduct; order_finished_lot_ids -> stock.production.lot; account_move_ids -> account.move; stock_valuation_layer_ids -> stock.valuation.layer; scrap_return_move_id -> stock.move.line; purchase_line_id -> purchase.order.line; created_purchase_line_id -> purchase.order.line; sh_quality_point_id -> sh.qc.point; created_purchase_request_line_id -> purchase.request.line; purchase_request_allocation_ids -> purchase.request.allocation; purchase_request_ids -> purchase.request; requisition_line_ids -> purchase.requisition.line; sale_line_id -> sale.order.line; branch_id -> res.branch; repair_id -> repair.order; product_id -> product.product; move_package_id -> stock.quant.package; filter_move_package_ids -> stock.quant.package; mr_line_id -> material.request.line; analytic_account_group_ids -> account.analytic.tag; responsible -> res.users; package_type -> product.packaging; packaging_ids -> product.packaging; package_quant_ids -> stock.quant; measure_ids -> measure.for.packaging; source_picking_id -> stock.picking; source_move_id -> stock.move; created_assembly_id -> assembly.production.record; assembly_finished_id -> assembly.production.record; assembly_component_id -> assembly.production.record; created_kitchen_id -> kitchen.production.record; kitchen_finished_id -> kitchen.production.record; kitchen_component_id -> kitchen.production.record; asp_asm_stock_id -> asp.asm.stock; finish_good_rework_id -> finish.good.rework; finish_good_rework_finished_id -> finish.good.rework; finish_good_rework_created_kitchen_id -> finish.good.rework; finish_good_rework_by_product_id -> finish.good.rework; assembly_product_id -> product.product; assembly_bom_id -> mrp.bom; kitchen_product_id -> product.product; kitchen_bom_id -> mrp.bom; product_warehouse -> stock.location; product_location -> stock.warehouse; vendor_id -> res.partner; reserved_by_id -> res.users; picking_id -> stock.picking; return_reason -> return.reason; combo_item_id -> pos.combo.item; pos_branch_id -> res.branch; pos_order_line_id -> pos.order.line; sale_order_id -> sale.order; purchase_order_id -> purchase.order; taxes_id -> account.tax; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: move_dest_ids, move_orig_ids, route_ids, lot_ids, allowed_operation_ids, order_finished_lot_ids, filter_move_package_ids, analytic_account_group_ids, packaging_ids, package_quant_ids, measure_ids, taxes_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.move", "table_name": ""}
+{"text": "How do I use the account.cash.flow model?", "response": "To use the account.cash.flow model, you need to provide values for required fields: levels, journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.cash.flow", "table_name": ""}
+{"text": "How is project.create.sale.order.line used in the system?", "response": "The project.create.sale.order.line model represents Create SO Line from project in the ERP system. It contains 13 fields and is used to manage create so line from project data. Key fields include: wizard_id, product_id, price_unit, currency_id, employee_id, sale_line_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "project.create.sale.order.line", "table_name": ""}
+{"text": "What methods are available in sh.quality.alert?", "response": "The sh.quality.alert model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.quality.alert", "table_name": ""}
+{"text": "Tell me about the product.template.barcode model.", "response": "The product.template.barcode model represents Product Barcode in the ERP system. It contains 13 fields and is used to manage product barcode data. 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.template.barcode", "table_name": ""}
+{"text": "What models are connected to setu.inventory.xyz.analysis.bi.report?", "response": "The setu.inventory.xyz.analysis.bi.report model has 6 relational fields: product_id -> product.product; product_category_id -> product.category; company_id -> res.company; wizard_id -> setu.inventory.xyz.analysis.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.xyz.analysis.bi.report", "table_name": ""}
+{"text": "Which fields in product.product are computed?", "response": "The product.product model is defined in module: product. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.product", "table_name": ""}
+{"text": "How to query sh.tsp.top.selling.product data?", "response": "To use the sh.tsp.top.selling.product 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.tsp.top.selling.product", "table_name": ""}
+{"text": "How to create records in setu.inventory.turnover.analysis.bi.report?", "response": "To use the setu.inventory.turnover.analysis.bi.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.turnover.analysis.bi.report", "table_name": ""}
+{"text": "What data can be stored in project.profitability.report?", "response": "The project.profitability.report model has 23 fields: analytic_account_id, project_id, currency_id, company_id, user_id, partner_id, line_date, timesheet_unit_amount, timesheet_cost, expense_cost, order_confirmation_date, sale_line_id, sale_order_id, product_id, amount_untaxed_to_invoice, amount_untaxed_invoiced, expense_amount_untaxed_to_invoice, expense_amount_untaxed_invoiced, other_revenues, margin, id, display_name, __last_update. Field types distribution: many2one: 9, date: 1, float: 9, datetime: 2, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.profitability.report", "table_name": ""}
+{"text": "Describe the mailing.mailing.test model in Odoo.", "response": "The mailing.mailing.test model represents Sample Mail Wizard in the ERP system. It contains 9 fields and is used to manage sample mail wizard data. Key fields include: email_to, mass_mailing_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mailing.mailing.test", "table_name": ""}
+{"text": "What are common use cases for kitchen.cooking.list?", "response": "To use the kitchen.cooking.list 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "kitchen.cooking.list", "table_name": ""}
+{"text": "What operations can I perform on customer.deposit.report?", "response": "To use the customer.deposit.report model, you need to provide values for required fields: partner_id, amount, currency_id, move_id, payment_date, deposit_reconcile_journal_id, deposit_account_id. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "customer.deposit.report", "table_name": ""}
+{"text": "What methods are available in hr.employee?", "response": "The hr.employee model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hr.employee", "table_name": ""}
+{"text": "What data can be stored in setu.inventory.fsn.xyz.analysis.bi.report?", "response": "The setu.inventory.fsn.xyz.analysis.bi.report model has 19 fields: product_id, product_category_id, company_id, average_stock, sales, turnover_ratio, current_stock, stock_value, fsn_classification, xyz_classification, combine_classification, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, float: 5, char: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.fsn.xyz.analysis.bi.report", "table_name": ""}
+{"text": "What does the sh.tv.top.vendor.wizard model represent?", "response": "The sh.tv.top.vendor.wizard model represents Top Vendors in the ERP system. It contains 17 fields and is used to manage top vendors data. Key fields include: type, date_from, date_to, date_compare_from, date_compare_to, no_of_top_item, amount_total, currency_id, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.tv.top.vendor.wizard", "table_name": ""}
+{"text": "Which fields in receivable.opening.balance are computed?", "response": "The receivable.opening.balance model is defined in module: equip3_accounting_opening_balance. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "receivable.opening.balance", "table_name": ""}
+{"text": "How is account.unreconcile used in the system?", "response": "The account.unreconcile model represents Account Unreconcile in the ERP system. It contains 7 fields and is used to manage account unreconcile data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.unreconcile", "table_name": ""}
+{"text": "What are the available fields for approval.matrix.sale.order?", "response": "The approval.matrix.sale.order model has 46 fields: name, company_id, branch_id, config, minimum_amt, maximum_amt, approver_matrix_line_ids, description, 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. Field types distribution: char: 7, many2one: 10, selection: 3, float: 2, one2many: 5, text: 2, date: 2, boolean: 5, many2many: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.sale.order", "table_name": ""}
+{"text": "What foreign keys exist in report.excel.param?", "response": "The report.excel.param model has 5 relational fields: report_excel_id -> report.excel; param_ir_model_id -> ir.model; wizard_param_ir_model_field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.excel.param", "table_name": ""}
+{"text": "What are the available fields for sh.stock.move.global.check?", "response": "The sh.stock.move.global.check model has 16 fields: product_id, sh_message, sh_quality_point_id, picking_id, sh_measure, text_message, attachment_ids, type, move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, text: 2, float: 1, many2many: 1, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.stock.move.global.check", "table_name": ""}
+{"text": "What foreign keys exist in account.balance.report?", "response": "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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.balance.report", "table_name": ""}
+{"text": "What operations can I perform on report.equip3_accounting_reports.debt_collection?", "response": "To use the report.equip3_accounting_reports.debt_collection model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.debt_collection", "table_name": ""}
+{"text": "How does report.account.report_invoice_with_payments relate to other models?", "response": "The report.account.report_invoice_with_payments model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.account.report_invoice_with_payments", "table_name": ""}
+{"text": "How do I use the account.bank.statement.line.wizard model?", "response": "To use the account.bank.statement.line.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.bank.statement.line.wizard", "table_name": ""}
+{"text": "What operations can I perform on ir.qweb.field.date?", "response": "To use the ir.qweb.field.date model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb.field.date", "table_name": ""}
+{"text": "How to create records in account.bank.statement.cashbox?", "response": "To use the account.bank.statement.cashbox model, you need to provide values for required fields: none. Readonly fields: total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.bank.statement.cashbox", "table_name": ""}
+{"text": "What are the available fields for sh.top.purchasing.excel.extended?", "response": "The sh.top.purchasing.excel.extended model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.top.purchasing.excel.extended", "table_name": ""}
+{"text": "Tell me about the import.record.data model.", "response": "The import.record.data model represents import.record.data in the ERP system. It contains 46 fields and is used to manage import.record.data data. Key fields include: name, state, record_type, created_date, partner_id, warehouse_id, location_id, no_return, sheet_number, error_message, product_list, file, file_name, filter_location_ids, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "import.record.data", "table_name": ""}
+{"text": "Describe the ks_dashboard_ninja.board_defined_filters model in Odoo.", "response": "The ks_dashboard_ninja.board_defined_filters model represents Dashboard Ninja Defined Filters in the ERP system. It contains 16 fields and is used to manage dashboard ninja defined filters data. Key fields include: name, ks_dashboard_board_id, ks_model_id, ks_domain, ks_domain_temp, ks_model_name, display_type, sequence, ks_is_active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.board_defined_filters", "table_name": ""}
+{"text": "What modules define stock.package.destination?", "response": "The stock.package.destination model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.package.destination", "table_name": ""}
+{"text": "How to create records in product.ribbon?", "response": "To use the product.ribbon model, you need to provide values for required fields: html, html_class. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.ribbon", "table_name": ""}
+{"text": "Which fields in phone.validation.mixin are computed?", "response": "The phone.validation.mixin model is defined in module: phone_validation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "phone.validation.mixin", "table_name": ""}
+{"text": "Describe the many2many relations for all.redeem.rule.", "response": "The all.redeem.rule model has 3 relational fields: loyality_id -> all.loyalty.setting; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "all.redeem.rule", "table_name": ""}
+{"text": "What are the technical details of account.asset.depreciation.line?", "response": "The account.asset.depreciation.line model is defined in module: om_account_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.asset.depreciation.line", "table_name": ""}
+{"text": "Tell me about the sh.custom.tab.purchase model.", "response": "The sh.custom.tab.purchase model represents Custom Tab purchase in the ERP system. It contains 15 fields and is used to manage custom tab purchase data. Key fields include: name, label, groups, sequence, view_id, tab_list, invisible_tab, sh_position, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.custom.tab.purchase", "table_name": ""}
+{"text": "What are the available fields for mr.internal_transfer?", "response": "The mr.internal_transfer model has 9 fields: source_warehouse_id, ir_wizard_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mr.internal_transfer", "table_name": ""}
+{"text": "What operations can I perform on res.currency.rate?", "response": "To use the res.currency.rate model, you need to provide values for required fields: name, currency_id. Readonly fields: currency_id, rate, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.currency.rate", "table_name": ""}
+{"text": "What foreign keys exist in rfm.yearly.analysis.by.segment?", "response": "The rfm.yearly.analysis.by.segment model has 1 relational fields: segment_id -> setu.rfm.segment. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "rfm.yearly.analysis.by.segment", "table_name": ""}
+{"text": "Show me the fields of decimal.precision.", "response": "The decimal.precision model has 9 fields: name, digits, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "decimal.precision", "table_name": ""}
+{"text": "What foreign keys exist in account.partner.ageing?", "response": "The account.partner.ageing model has 7 relational fields: partner_ids -> res.partner; partner_category_ids -> res.partner.category; journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, partner_category_ids, journal_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.partner.ageing", "table_name": ""}
+{"text": "What are the available fields for ir.ui.menu.category?", "response": "The ir.ui.menu.category model has 10 fields: sequence, name, color, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, char: 3, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.ui.menu.category", "table_name": ""}
+{"text": "How to query invoice.recurring.line data?", "response": "To use the invoice.recurring.line model, you need to provide values for required fields: invoice_recurring_id, account_id, name, price_unit, quantity, analytic_group_ids. Readonly fields: product_uom_category_id, journal_id, subtotal, price_tax, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "invoice.recurring.line", "table_name": ""}
+{"text": "List all fields in the pos.coupon.apply.code model.", "response": "The pos.coupon.apply.code model has 8 fields: coupon_code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.coupon.apply.code", "table_name": ""}
+{"text": "List all fields in the split.pr.line.wizard model.", "response": "The split.pr.line.wizard model has 14 fields: wizard_id, pr_line_id, name, user_id, new_user_id, product_id, product_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, char: 2, float: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "split.pr.line.wizard", "table_name": ""}
+{"text": "What are the relationships in report.account.report_hash_integrity?", "response": "The report.account.report_hash_integrity model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.account.report_hash_integrity", "table_name": ""}
+{"text": "What fields does credit.note.product.lines have?", "response": "The credit.note.product.lines model has 13 fields: product_id, quantity, price, sale_line_id, credit_note_id, purchase_line_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, float: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "credit.note.product.lines", "table_name": ""}
+{"text": "What are the relationships in all.loyalty.setting?", "response": "The all.loyalty.setting model has 5 relational fields: product_id -> product.product; redeem_ids -> all.redeem.rule; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "all.loyalty.setting", "table_name": ""}
+{"text": "What modules define apply.voucher?", "response": "The apply.voucher model is defined in module: equip3_sale_loyalty. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "apply.voucher", "table_name": ""}
+{"text": "How do I use the account.account.template model?", "response": "To use the account.account.template model, you need to provide values for required fields: code, user_type_id, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.account.template", "table_name": ""}
+{"text": "Describe the journal.entries.report model in Odoo.", "response": "The journal.entries.report model represents Journal Entries Report in the ERP system. It contains 12 fields and is used to manage journal entries report data. Key fields include: num, label, account_id, partner_id, analytic_account_id, amount_currency, currency_id, debit, credit, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "journal.entries.report", "table_name": ""}
+{"text": "Describe the account.debt.collection.line model in Odoo.", "response": "The account.debt.collection.line model represents Debt Collection Line in the ERP system. It contains 28 fields and is used to manage debt collection line data. Key fields include: debt_collection_id, invoice_id, invoice_date, currency_id, amount_invoice, amount_residual, state, journal_id, date, amount, is_full_collect, payment_id, is_pic_line, user_id, partner_id, deadline_date, invoice_due_date, total_due_date, debt_coll_pic, invoice_week_number, invoice_week_start, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.debt.collection.line", "table_name": ""}
+{"text": "Show me the fields of base_import.tests.models.char.readonly.", "response": "The base_import.tests.models.char.readonly model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.char.readonly", "table_name": ""}
+{"text": "What data can be stored in restaurant.printer?", "response": "The restaurant.printer model has 12 fields: name, proxy_ip, product_categories_ids, printer_type, epson_printer_ip, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2many: 1, selection: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "restaurant.printer", "table_name": ""}
+{"text": "What are the technical details of purchase.order?", "response": "The purchase.order model is defined in module: purchase. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.order", "table_name": ""}
+{"text": "Show me the relational structure of sale.payment.acquirer.onboarding.wizard.", "response": "The sale.payment.acquirer.onboarding.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.payment.acquirer.onboarding.wizard", "table_name": ""}
+{"text": "How to query account.analytic.line data?", "response": "To use the account.analytic.line model, you need to provide values for required fields: name, account_id, company_id, date, amount. Readonly fields: product_uom_category_id, currency_id, general_account_id, department_id, encoding_uom_id, timesheet_invoice_type, timesheet_invoice_id, company_id, group_id, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.analytic.line", "table_name": ""}
+{"text": "List all fields in the sh.sale.invoice.summary.wizard model.", "response": "The sh.sale.invoice.summary.wizard model has 15 fields: sh_start_date, sh_end_date, sh_partner_ids, sh_status, company_ids, company_id, customer_order_dic, currency_precision, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2many: 2, selection: 1, many2one: 3, one2many: 1, integer: 2, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.sale.invoice.summary.wizard", "table_name": ""}
+{"text": "Describe the field structure of ir.exports.line.", "response": "The ir.exports.line model has 9 fields: name, export_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.exports.line", "table_name": ""}
+{"text": "How do I use the snailmail.confirm.invoice model?", "response": "To use the snailmail.confirm.invoice 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "snailmail.confirm.invoice", "table_name": ""}
+{"text": "How is phone.blacklist.remove used in the system?", "response": "The phone.blacklist.remove model represents Remove phone from blacklist in the ERP system. It contains 9 fields and is used to manage remove phone from blacklist data. Key fields include: phone, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "phone.blacklist.remove", "table_name": ""}
+{"text": "What are the available fields for pos.generate.efaktur.other?", "response": "The pos.generate.efaktur.other model has 11 fields: gen_efaktur_id, partner_id, account_move_id, l10n_id_tax_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.generate.efaktur.other", "table_name": ""}
+{"text": "Describe the implementation of base_import.tests.models.m2o.related.", "response": "The base_import.tests.models.m2o.related model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.m2o.related", "table_name": ""}
+{"text": "How is generate.closing.entries.confirmation.wizard implemented technically?", "response": "The generate.closing.entries.confirmation.wizard model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "generate.closing.entries.confirmation.wizard", "table_name": ""}
+{"text": "What methods are available in report.dynamic_accounts_report.balance_sheet?", "response": "The report.dynamic_accounts_report.balance_sheet model is defined in module: dynamic_accounts_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.dynamic_accounts_report.balance_sheet", "table_name": ""}
+{"text": "What operations can I perform on cust.credit.limit.data?", "response": "To use the cust.credit.limit.data 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cust.credit.limit.data", "table_name": ""}
+{"text": "How does sale.excel.report relate to other models?", "response": "The sale.excel.report model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.excel.report", "table_name": ""}
+{"text": "What business logic is in report.equip3_accounting_reports.financial_ratio_report?", "response": "To use the report.equip3_accounting_reports.financial_ratio_report model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.financial_ratio_report", "table_name": ""}
+{"text": "Describe the implementation of mrp.immediate.production.", "response": "The mrp.immediate.production model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.immediate.production", "table_name": ""}
+{"text": "What are common use cases for theme.website.menu?", "response": "To use the theme.website.menu model, you need to provide values for required fields: name. Readonly fields: copy_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "theme.website.menu", "table_name": ""}
+{"text": "How is utm.campaign used in the system?", "response": "The utm.campaign model represents UTM Campaign in the ERP system. It contains 26 fields and is used to manage utm campaign data. Key fields include: name, user_id, stage_id, tag_ids, is_website, color, click_count, use_leads, crm_lead_count, mailing_mail_ids, mailing_mail_count, received_ratio, opened_ratio, replied_ratio, bounced_ratio, quotation_count, invoiced_amount, company_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "utm.campaign", "table_name": ""}
+{"text": "How to create records in coupon.coupon?", "response": "To use the coupon.coupon model, you need to provide values for required fields: code, state. Readonly fields: code, expiration_date, order_id, sales_order_id, pos_order_id, is_gift_card, redeem_history_ids, pos_create_date, pos_create_uid, pos_config_id, redeem_amount, balance_amount, pos_orderline_id, purchase_id, purchases_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "coupon.coupon", "table_name": ""}
+{"text": "What business logic is in sh.purchase.product.indent.xls?", "response": "To use the sh.purchase.product.indent.xls model, you need to provide values for required fields: none. Readonly fields: file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.purchase.product.indent.xls", "table_name": ""}
+{"text": "How is invoice.printout.editor used in the system?", "response": "The invoice.printout.editor model represents invoice.printout.editor in the ERP system. It contains 19 fields and is used to manage invoice.printout.editor data. Key fields include: name, invoice_ids, invoice_header_ids, invoice_header_filter_ids, invoice_table_ids, invoice_table_filter_ids, invoice_footer_ids, invoice_footer_filter_ids, template_id, orientation, paper_size_format, preview, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "invoice.printout.editor", "table_name": ""}
+{"text": "How is account.tax.map.sales.line implemented technically?", "response": "The account.tax.map.sales.line model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.tax.map.sales.line", "table_name": ""}
+{"text": "Which fields in salesperson.tracking.history are computed?", "response": "The salesperson.tracking.history model is defined in module: equip3_crm_tracking. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "salesperson.tracking.history", "table_name": ""}
+{"text": "What fields does order.stage have?", "response": "The order.stage model has 15 fields: name, description, sequence, warehouse_ids, action_type, is_hidden, planned_date, actual_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, text: 1, integer: 2, many2many: 1, selection: 1, boolean: 1, datetime: 5, many2one: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "order.stage", "table_name": ""}
+{"text": "What modules define mailing.mailing.test?", "response": "The mailing.mailing.test model is defined in module: mass_mailing. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mailing.mailing.test", "table_name": ""}
+{"text": "How to query pos.payment.edc data?", "response": "To use the pos.payment.edc model, you need to provide values for required fields: none. Readonly fields: pos_branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.payment.edc", "table_name": ""}
+{"text": "How is account.move.line implemented technically?", "response": "The account.move.line model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.move.line", "table_name": ""}
+{"text": "What business logic is in stock.warn.insufficient.qty.scrap?", "response": "To use the stock.warn.insufficient.qty.scrap model, you need to provide values for required fields: product_id, location_id, quantity, product_uom_name. Readonly fields: quant_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.warn.insufficient.qty.scrap", "table_name": ""}
+{"text": "What are the technical details of report.stock.demand?", "response": "The report.stock.demand model is defined in module: stock_qty_forecast. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.stock.demand", "table_name": ""}
+{"text": "Describe the many2many relations for stock.assign.serial.", "response": "The stock.assign.serial model has 4 relational fields: product_id -> product.product; move_id -> stock.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.assign.serial", "table_name": ""}
+{"text": "What operations can I perform on sh.send.notification?", "response": "To use the sh.send.notification 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.send.notification", "table_name": ""}
+{"text": "Show me the relational structure of quality.check.report.", "response": "The quality.check.report model has 3 relational fields: product_ids -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "quality.check.report", "table_name": ""}
+{"text": "How is purchase.order.wizard used in the system?", "response": "The purchase.order.wizard model represents Purchase Order Wizard in the ERP system. It contains 17 fields and is used to manage purchase order wizard data. Key fields include: order_line, partner_id, date_planned, order_selection, sh_group_by_partner, sh_cancel_old_rfqs, sh_create_po, partner_ids, so_id, is_dropship, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order.wizard", "table_name": ""}
+{"text": "What methods are available in sh.sale.invoice.summary.wizard?", "response": "The sh.sale.invoice.summary.wizard model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.sale.invoice.summary.wizard", "table_name": ""}
+{"text": "What foreign keys exist in overhead.material?", "response": "The overhead.material model has 5 relational fields: product -> product.product; consumed_uom -> uom.uom; mrp_wc_id -> mrp.workcenter; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "overhead.material", "table_name": ""}
+{"text": "What are the relationships in acrux.chat.conversation?", "response": "The acrux.chat.conversation model has 12 relational fields: connector_id -> acrux.chat.connector; res_partner_id -> res.partner; chat_message_ids -> acrux.chat.message; sellman_id -> res.users; company_id -> res.company; team_id -> crm.team; crm_lead_id -> crm.lead; sale_order_id -> sale.order; partner_sellman_id -> res.users; team_ids -> crm.team; create_uid -> res.users; write_uid -> res.users. Many2many fields: team_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "acrux.chat.conversation", "table_name": ""}
+{"text": "What does the account.fiscal.position model represent?", "response": "The account.fiscal.position model represents Fiscal Position in the ERP system. It contains 23 fields and is used to manage fiscal position data. Key fields include: sequence, active, company_id, account_ids, tax_ids, auto_apply, vat_required, country_id, country_group_id, state_ids, zip_from, zip_to, states_count, name, note, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.fiscal.position", "table_name": ""}
+{"text": "What methods are available in repair.line?", "response": "The repair.line model is defined in module: repair. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "repair.line", "table_name": ""}
+{"text": "What business logic is in mail.shortcode?", "response": "To use the mail.shortcode model, you need to provide values for required fields: source, substitution. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.shortcode", "table_name": ""}
+{"text": "What methods are available in ir.mail_server?", "response": "The ir.mail_server model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.mail_server", "table_name": ""}
+{"text": "How do I use the kitchen.cooking.list model?", "response": "To use the kitchen.cooking.list 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "kitchen.cooking.list", "table_name": ""}
+{"text": "Tell me about the stock.inventory.line model.", "response": "The stock.inventory.line model represents Inventory Line in the ERP system. It contains 49 fields and is used to manage inventory line data. Key fields include: is_editable, inventory_id, partner_id, product_id, product_uom_id, product_qty, categ_id, package_id, prod_lot_id, company_id, state, theoretical_qty, inventory_date, outdated, product_tracking, unit_price, inv_cost, sh_inven_adjt_barcode_scanner_is_last_scanned, location_id, sequence, adjustment_account_id, filtered_adjustment_account_id, is_adj_val, analytic_tag_ids, uom_id, category_uom_id, wizard_id, to_call_difference_qty_compute, difference_qty, currency_id, new_unit_price, theoretical_unit_price, difference_unit_price, user_id_1, user_id_2, user_count_1, user_count_2, barcode, s_no, current_user_id, is_user_id_1, is_user_id_2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.inventory.line", "table_name": ""}
+{"text": "Describe the invoice.deposit.line.reconcile model in Odoo.", "response": "The invoice.deposit.line.reconcile model represents invoice.deposit.line.reconcile in the ERP system. It contains 12 fields and is used to manage invoice.deposit.line.reconcile data. Key fields include: deposit_reconcile_id, invoice_id, filter_move_ids, allocation_amount, invoice_due_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "invoice.deposit.line.reconcile", "table_name": ""}
+{"text": "What are the technical details of ir.server.object.lines?", "response": "The ir.server.object.lines model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.server.object.lines", "table_name": ""}
+{"text": "How to query do.approval.matrix data?", "response": "To use the do.approval.matrix model, you need to provide values for required fields: name, warehouse_id. Readonly fields: create_date, create_uid, level, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "do.approval.matrix", "table_name": ""}
+{"text": "What operations can I perform on export.partner.csv?", "response": "To use the export.partner.csv model, you need to provide values for required fields: none. Readonly fields: product_id_attachment_id, product_id_csv_created, 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, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "export.partner.csv", "table_name": ""}
+{"text": "How is cust.credit.limit.report.wizard used in the system?", "response": "The cust.credit.limit.report.wizard model represents Customer Credit Limit Wizard in the ERP system. It contains 10 fields and is used to manage customer credit limit wizard data. Key fields include: partner_ids, company_ids, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "cust.credit.limit.report.wizard", "table_name": ""}
+{"text": "How to create records in ks_dashboard_ninja.item?", "response": "To use the ks_dashboard_ninja.item model, you need to provide values for required fields: ks_layout, ks_date_filter_selection, ks_date_filter_selection_2, ks_dashboard_item_type, ks_list_view_type. Readonly fields: ks_model_name_2, ks_model_name, ks_record_count_2, ks_record_count, ks_chart_groupby_type, ks_chart_sub_groupby_type, ks_chart_data, ks_kpi_data, ks_list_view_data, ks_to_do_data, ks_query_result, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_dashboard_ninja.item", "table_name": ""}
+{"text": "How do I use the access.management model?", "response": "To use the access.management model, you need to provide values for required fields: company_ids. Readonly fields: self_module_menu_ids, self_model_ids, total_rules, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "access.management", "table_name": ""}
+{"text": "Show me the relational structure of store.model.nodes.", "response": "The store.model.nodes model has 3 relational fields: model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "store.model.nodes", "table_name": ""}
+{"text": "Describe the field structure of debt.collection.report.", "response": "The debt.collection.report model has 16 fields: partner_ids, user_ids, journal_ids, state, 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 types distribution: many2many: 3, selection: 2, date: 2, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "debt.collection.report", "table_name": ""}
+{"text": "What are the relationships in hide.view.nodes?", "response": "The hide.view.nodes model has 7 relational fields: model_id -> ir.model; btn_store_model_nodes_ids -> store.model.nodes; page_store_model_nodes_ids -> store.model.nodes; link_store_model_nodes_ids -> store.model.nodes; access_management_id -> access.management; create_uid -> res.users; write_uid -> res.users. Many2many fields: btn_store_model_nodes_ids, page_store_model_nodes_ids, link_store_model_nodes_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hide.view.nodes", "table_name": ""}
+{"text": "Show me the fields of setu.inventory.fsn.analysis.report.", "response": "The setu.inventory.fsn.analysis.report model has 16 fields: stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, stock_movement_type, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, date: 2, many2many: 4, selection: 1, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.fsn.analysis.report", "table_name": ""}
+{"text": "How is ks.parameter.tuning.wizard implemented technically?", "response": "The ks.parameter.tuning.wizard model is defined in module: ks_sales_forecast. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks.parameter.tuning.wizard", "table_name": ""}
+{"text": "Show me the fields of hide.chatter.", "response": "The hide.chatter model has 13 fields: access_management_id, model_id, hide_chatter, hide_send_mail, hide_log_notes, hide_schedule_activity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, boolean: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "hide.chatter", "table_name": ""}
+{"text": "Tell me about the kitchen.cooking.list model.", "response": "The kitchen.cooking.list model represents Kitchen Cooking List in the ERP system. It contains 12 fields and is used to manage kitchen cooking list data. Key fields include: from_date, to_date, company_id, warehouse_id, product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "kitchen.cooking.list", "table_name": ""}
+{"text": "What business logic is in account.pettycash.fund.change?", "response": "To use the account.pettycash.fund.change model, you need to provide values for required fields: fund, effective_date. Readonly fields: fund_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.pettycash.fund.change", "table_name": ""}
+{"text": "What models are connected to mrp.production.backorder?", "response": "The mrp.production.backorder model has 4 relational fields: mrp_production_ids -> mrp.production; mrp_production_backorder_line_ids -> mrp.production.backorder.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: mrp_production_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.production.backorder", "table_name": ""}
+{"text": "Describe the field structure of auditlog.http.session.", "response": "The auditlog.http.session model has 10 fields: display_name, name, user_id, http_request_ids, id, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "auditlog.http.session", "table_name": ""}
+{"text": "What are the relationships in report.sh_purchase_reports.sh_po_bill_summary_doc?", "response": "The report.sh_purchase_reports.sh_po_bill_summary_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_po_bill_summary_doc", "table_name": ""}
+{"text": "What methods are available in account.financial.year.op?", "response": "The account.financial.year.op model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.financial.year.op", "table_name": ""}
+{"text": "Describe the many2many relations for pos.payment.report.", "response": "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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.payment.report", "table_name": ""}
+{"text": "What data can be stored in analytic.sale.order.line?", "response": "The analytic.sale.order.line model has 21 fields: name, product_id, product_uom_qty, product_uom, price_unit, analytic_tag_ids, tax_ids, discount, subscription_product_line_id, not_subscription_product_line_id, price_subtotal, price_tax, price_total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2one: 7, float: 6, many2many: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "analytic.sale.order.line", "table_name": ""}
+{"text": "How to create records in bus.presence?", "response": "To use the bus.presence model, you need to provide values for required fields: user_id. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "bus.presence", "table_name": ""}
+{"text": "How is restore.lead.type used in the system?", "response": "The restore.lead.type model represents Restore in the ERP system. It contains 8 fields and is used to manage restore data. Key fields include: lead_type_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "restore.lead.type", "table_name": ""}
+{"text": "How do I use the account.group.template model?", "response": "To use the account.group.template model, you need to provide values for required fields: chart_template_id, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.group.template", "table_name": ""}
+{"text": "Describe the implementation of report.equip3_accounting_reports.customer_statement.", "response": "The report.equip3_accounting_reports.customer_statement model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.equip3_accounting_reports.customer_statement", "table_name": ""}
+{"text": "What methods are available in setu.inventory.age.bi.report?", "response": "The setu.inventory.age.bi.report model is defined in module: setu_advance_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "setu.inventory.age.bi.report", "table_name": ""}
+{"text": "What does the receipt.payment.line.credit model represent?", "response": "The receipt.payment.line.credit model represents   in the ERP system. It contains 20 fields and is used to manage   data. Key fields include: line_id, currency_id, invoice_id, account_id, invoice_date, invoice_date_due, original_amount, base_amount, original_unreconcile, base_unreconcile, is_full_reconcile, amount, payment_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "receipt.payment.line.credit", "table_name": ""}
+{"text": "What data can be stored in stock.picking.type?", "response": "The stock.picking.type model has 43 fields: name, color, sequence, sequence_id, sequence_code, default_location_src_id, default_location_dest_id, return_picking_type_id, show_entire_packs, warehouse_id, active, use_create_lots, use_existing_lots, show_operations, show_reserved, count_picking_draft, count_picking_ready, count_picking, count_picking_waiting, count_picking_late, count_picking_backorders, rate_picking_late, rate_picking_backorders, barcode, company_id, code, count_mo_todo, count_mo_waiting, count_mo_late, use_create_components_lots, branch_id, is_transit, filter_location_ids, stock_picking_dasboard_id, picking_ids, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, integer: 14, many2one: 11, boolean: 8, selection: 1, many2many: 1, one2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.picking.type", "table_name": ""}
+{"text": "What methods are available in res.users.qiscuss?", "response": "The res.users.qiscuss model is defined in module: equip3_crm_whatsapp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.qiscuss", "table_name": ""}
+{"text": "What business logic is in mail.followers?", "response": "To use the mail.followers model, you need to provide values for required fields: res_model. Readonly fields: name, email, is_active, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.followers", "table_name": ""}
+{"text": "Describe the account.tax.template model in Odoo.", "response": "The account.tax.template model represents Templates for Taxes in the ERP system. It contains 25 fields and is used to manage templates for taxes data. Key fields include: chart_template_id, type_tax_use, tax_scope, amount_type, active, children_tax_ids, sequence, amount, price_include, include_base_amount, analytic, invoice_repartition_line_ids, refund_repartition_line_ids, tax_group_id, tax_exigibility, cash_basis_transition_account_id, name, description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.tax.template", "table_name": ""}
+{"text": "Describe the sh.top.selling.products model in Odoo.", "response": "The sh.top.selling.products model represents Top Selling XLS in the ERP system. It contains 9 fields and is used to manage top selling xls data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.top.selling.products", "table_name": ""}
+{"text": "List all fields in the stock.lot.serialize.line model.", "response": "The stock.lot.serialize.line model has 13 fields: stock_move_id, sequence, move_id, product_id, demand_qty, qty_per_lot, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, char: 2, float: 1, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.lot.serialize.line", "table_name": ""}
+{"text": "Can you explain the purpose of product.supplierinfo.approval?", "response": "The product.supplierinfo.approval model represents product.supplierinfo.approval in the ERP system. It contains 20 fields and is used to manage product.supplierinfo.approval data. Key fields include: sequence, sequence2, user_ids, minimum_approver, status, time, feedback, approved, approval, last_approved, time_stamp, user_approved_ids, supplier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.supplierinfo.approval", "table_name": ""}
+{"text": "What business logic is in purchase.order.partner.credit?", "response": "To use the purchase.order.partner.credit model, you need to provide values for required fields: none. Readonly fields: name, order_partner, vendor_credit_limit, total_payable, current_order, purchase_orders_cnt_amt, cust_invoice_cnt_amt, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.order.partner.credit", "table_name": ""}
+{"text": "What are the available fields for weight.scale.barcode.format?", "response": "The weight.scale.barcode.format model has 10 fields: name, line_ids, total_digit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, one2many: 1, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "weight.scale.barcode.format", "table_name": ""}
+{"text": "What business logic is in ir.config_parameter?", "response": "To use the ir.config_parameter model, you need to provide values for required fields: key, value. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.config_parameter", "table_name": ""}
+{"text": "What data can be stored in apps.installation.activity.log?", "response": "The apps.installation.activity.log model has 14 fields: activity_date, module_name, technical_name, latest_version, user_id, activity, description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 4, char: 4, many2one: 3, selection: 1, text: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "apps.installation.activity.log", "table_name": ""}
+{"text": "How is product.pricelist.change implemented technically?", "response": "The product.pricelist.change model is defined in module: allfresh_mod_pricelist. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.pricelist.change", "table_name": ""}
+{"text": "How is sh.commision.detail used in the system?", "response": "The sh.commision.detail model represents sh.commision.detail in the ERP system. It contains 11 fields and is used to manage sh.commision.detail data. Key fields include: sales_amount, collection_amount, commision, target_commision_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.commision.detail", "table_name": ""}
+{"text": "What does the assets.approval.matrix.line model represent?", "response": "The assets.approval.matrix.line model represents Assets Approval Matrix Line in the ERP system. It contains 19 fields and is used to manage assets approval matrix line data. Key fields include: sequence, user_ids, minimum_approver, assets_approval_matrix_id, sequence2, approved_users, state_char, time_stamp, feedback, last_approved, approved, assets_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assets.approval.matrix.line", "table_name": ""}
+{"text": "Can you explain the purpose of ks_dashboard_ninja.item?", "response": "The ks_dashboard_ninja.item model represents Dashboard Ninja items in the ERP system. It contains 122 fields and is used to manage dashboard ninja items data. Key fields include: name, ks_dashboard_board_template_id, ks_domain, ks_model_id_2, ks_model_name_2, ks_domain_temp, ks_background_color, ks_icon, ks_default_icon, ks_default_icon_color, ks_icon_select, ks_font_color, ks_dashboard_item_theme, ks_layout, ks_preview, ks_model_name, ks_record_count_type_2, ks_record_field_2, ks_record_count_2, ks_record_count_type, ks_record_count, ks_record_field, ks_record_data_limit_visibility, ks_isDateFilterApplied, ks_date_filter_selection, ks_date_filter_field, ks_item_start_date, ks_item_end_date, ks_date_filter_field_2, ks_item_start_date_2, ks_item_end_date_2, ks_domain_2, ks_domain_2_temp, ks_date_filter_selection_2, ks_previous_period, ks_dashboard_ninja_board_id, ks_dashboard_item_type, ks_chart_groupby_type, ks_chart_sub_groupby_type, ks_chart_relation_groupby, ks_chart_relation_sub_groupby, ks_chart_date_groupby, ks_chart_date_sub_groupby, ks_graph_preview, ks_chart_data, ks_chart_data_count_type, ks_chart_measure_field, ks_chart_cumulative_field, ks_chart_cumulative, ks_chart_measure_field_2, ks_bar_chart_stacked, ks_semi_circle_chart, ks_sort_by_field, ks_sort_by_order, ks_record_data_limit, ks_list_view_preview, ks_kpi_preview, ks_kpi_type, ks_target_view, ks_data_comparison, ks_kpi_data, ks_chart_item_color, ks_list_view_type, ks_list_view_fields, ks_export_all_records, ks_list_view_group_fields, ks_list_view_data, ks_company_id, ks_goal_enable, ks_goal_bar_line, ks_standard_goal_value, ks_goal_lines, ks_list_target_deviation_field, ks_many2many_field_ordering, ks_show_data_value, ks_action_lines, ks_actions, ks_compare_period, ks_year_period, ks_compare_period_2, ks_year_period_2, ks_multiplier_active, ks_multiplier, ks_update_items_data, ks_unit, ks_unit_selection, ks_chart_unit, ks_show_records, ks_fill_temporal, ks_domain_extension, ks_domain_extension_2, ks_hide_legend, ks_data_format, ks_button_color, ks_auto_update_type, ks_show_live_pop_up, ks_is_client_action, ks_client_action, ks_pagination_limit, ks_multiplier_lines, ks_precision_digits, ks_to_do_preview, ks_dn_header_lines, ks_to_do_data, ks_header_bg_color, ks_custom_query, ks_data_calculation_type, ks_query_result, ks_xlabels, ks_ylabels, ks_model_id, ks_list_view_layout, ks_is_date_ranges, ks_query_start_date, ks_query_end_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks_dashboard_ninja.item", "table_name": ""}
+{"text": "What foreign keys exist in base_import.tests.models.char?", "response": "The base_import.tests.models.char model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.char", "table_name": ""}
+{"text": "Describe the implementation of crm.phonecall.", "response": "The crm.phonecall model is defined in module: crm_phonecall. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.phonecall", "table_name": ""}
+{"text": "How does account.invoice.to.draft relate to other models?", "response": "The account.invoice.to.draft model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.invoice.to.draft", "table_name": ""}
+{"text": "What fields does qiscus.template.content have?", "response": "The qiscus.template.content model has 12 fields: template_id, name, language, content_id, content, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 2, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "qiscus.template.content", "table_name": ""}
+{"text": "What are the technical details of base.automation?", "response": "The base.automation model is defined in module: base_automation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base.automation", "table_name": ""}
+{"text": "What fields does account.deposit.return have?", "response": "The account.deposit.return model has 16 fields: return_date, return_amount, journal_id, payment_difference, payment_difference_handling, diff_amount_account_id, remaining_amount, customer_deposit_id, vendor_deposit_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, float: 3, many2one: 6, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.deposit.return", "table_name": ""}
+{"text": "Tell me about the purchase.request.report model.", "response": "The purchase.request.report model represents purchase.request.report in the ERP system. It contains 21 fields and is used to manage purchase.request.report data. Key fields include: name, product_qty, create_date, category_id, requested_by, assigned_to, expiry_date, origin, group_id, state, purchase_req_state, picking_type_id, company_id, branch_id, product_uom_id, date_required, estimated_cost, department_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.request.report", "table_name": ""}
+{"text": "Show me the fields of payment.voucher.matrix.reject.", "response": "The payment.voucher.matrix.reject model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "payment.voucher.matrix.reject", "table_name": ""}
+{"text": "Show me the fields of stock.quant.package.", "response": "The stock.quant.package model has 40 fields: quant_ids, packaging_id, location_id, company_id, owner_id, weight, weight_uom_name, shipping_weight, color, qty, uom_id, move_location_id, package_measure_selection, package_weight, length, maximum_length, width, maximum_width, height, maximum_height, volume, maximum_volume, name, max_weight, package_status, warehouse_id, package_expiration_date_time, shipping_volume, owner_id_stock, location_id_new, filter_location_id_new, barcode_packaging, create_automatic, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, many2one: 11, float: 14, char: 4, integer: 2, selection: 2, date: 1, many2many: 1, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.quant.package", "table_name": ""}
+{"text": "Tell me about the account.asset.depreciation.line model.", "response": "The account.asset.depreciation.line model represents Asset depreciation line in the ERP system. It contains 19 fields and is used to manage asset depreciation line data. Key fields include: name, sequence, asset_id, parent_state, amount, remaining_value, depreciated_value, depreciation_date, move_id, move_check, move_posted_check, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.asset.depreciation.line", "table_name": ""}
+{"text": "Can you explain the purpose of pos.promotion.multilevel.condition?", "response": "The pos.promotion.multilevel.condition model represents Promotion Multi Level condition in the ERP system. It contains 11 fields and is used to manage promotion multi level condition data. Key fields include: active, product_id, minimum_quantity, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.promotion.multilevel.condition", "table_name": ""}
+{"text": "What data can be stored in product.warehouse.cost.wizard?", "response": "The product.warehouse.cost.wizard model has 10 fields: product_id, product_cost_line_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.warehouse.cost.wizard", "table_name": ""}
+{"text": "Tell me about the sh.model.fields.purchase.order.selection model.", "response": "The sh.model.fields.purchase.order.selection model represents Field Selection in the ERP system. It contains 11 fields and is used to manage field selection data. Key fields include: sh_field_po_id, value, name, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.model.fields.purchase.order.selection", "table_name": ""}
+{"text": "How is generate.pos.voucher.use.history used in the system?", "response": "The generate.pos.voucher.use.history model represents Histories Generate use voucher of customer in the ERP system. It contains 13 fields and is used to manage histories generate use voucher of customer data. Key fields include: pos_order_id, payment_id, voucher_id, value, used_date, cashier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "generate.pos.voucher.use.history", "table_name": ""}
+{"text": "What are the technical details of purchase.target.based.on?", "response": "The purchase.target.based.on model is defined in module: equip3_purchase_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.target.based.on", "table_name": ""}
+{"text": "How do I use the report.accounting_pdf_reports.report_agedpartnerbalance model?", "response": "To use the report.accounting_pdf_reports.report_agedpartnerbalance model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.accounting_pdf_reports.report_agedpartnerbalance", "table_name": ""}
+{"text": "What models are connected to barcode.configuration?", "response": "The barcode.configuration model has 3 relational fields: currency -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "barcode.configuration", "table_name": ""}
+{"text": "Describe the implementation of stock.inventory.approval.matrix.line.", "response": "The stock.inventory.approval.matrix.line model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.inventory.approval.matrix.line", "table_name": ""}
+{"text": "How does sh.mpo.merge.purchase.order.wizard relate to other models?", "response": "The sh.mpo.merge.purchase.order.wizard model has 5 relational fields: partner_id -> res.partner; purchase_order_id -> purchase.order; purchase_order_ids -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_order_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.mpo.merge.purchase.order.wizard", "table_name": ""}
+{"text": "What data can be stored in pos.combo.limit?", "response": "The pos.combo.limit model has 11 fields: product_tmpl_id, pos_categ_id, quantity_limited, default_product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 2, many2many: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.combo.limit", "table_name": ""}
+{"text": "What modules define website.seo.metadata?", "response": "The website.seo.metadata model is defined in module: website. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "website.seo.metadata", "table_name": ""}
+{"text": "How do I use the report.equip3_accounting_reports.equity_move model?", "response": "To use the report.equip3_accounting_reports.equity_move model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.equity_move", "table_name": ""}
+{"text": "Describe the field structure of base_import.tests.models.float.", "response": "The base_import.tests.models.float model has 10 fields: value, value2, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 1, monetary: 1, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.float", "table_name": ""}
+{"text": "What does the mail.template.preview model represent?", "response": "The mail.template.preview model represents Email Template Preview in the ERP system. It contains 22 fields and is used to manage email template preview data. Key fields include: mail_template_id, model_id, resource_ref, lang, no_record, error_msg, subject, email_from, email_to, email_cc, reply_to, scheduled_date, body_html, attachment_ids, partner_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mail.template.preview", "table_name": ""}
+{"text": "Show me the fields of asset.modify.", "response": "The asset.modify model has 12 fields: name, method_number, method_period, method_end, asset_method_time, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 3, date: 1, char: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "asset.modify", "table_name": ""}
+{"text": "Tell me about the mrp.bom.operation model.", "response": "The mrp.bom.operation model represents MRP BoM Operation in the ERP system. It contains 9 fields and is used to manage mrp bom operation data. Key fields include: sequence, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.bom.operation", "table_name": ""}
+{"text": "Which fields in sms.cancel are computed?", "response": "The sms.cancel model is defined in module: sms. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sms.cancel", "table_name": ""}
+{"text": "What are the relationships in sh.tsp.top.purchasing.product?", "response": "The sh.tsp.top.purchasing.product model has 3 relational fields: product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.tsp.top.purchasing.product", "table_name": ""}
+{"text": "How does equip3.reporting.asset.wizard relate to other models?", "response": "The equip3.reporting.asset.wizard model has 3 relational fields: year -> sh.fiscal.year; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "equip3.reporting.asset.wizard", "table_name": ""}
+{"text": "What are common use cases for tanda.terima.faktur?", "response": "To use the tanda.terima.faktur model, you need to provide values for required fields: move_type. Readonly fields: filter_account_move_ids, invoice_payments_widget, move_type, line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "tanda.terima.faktur", "table_name": ""}
+{"text": "Tell me about the wizard.scrap.order.report model.", "response": "The wizard.scrap.order.report model represents Wizard Scrap Order Report in the ERP system. It contains 13 fields and is used to manage wizard scrap order report data. Key fields include: company_id, start_date, end_date, state, name, data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "wizard.scrap.order.report", "table_name": ""}
+{"text": "What foreign keys exist in iap.account?", "response": "The iap.account model has 3 relational fields: company_ids -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "iap.account", "table_name": ""}
+{"text": "What are the relationships in report.sh_purchase_reports.sh_po_product_profit_doc?", "response": "The report.sh_purchase_reports.sh_po_product_profit_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_purchase_reports.sh_po_product_profit_doc", "table_name": ""}
+{"text": "How to create records in delivery.price.rule?", "response": "To use the delivery.price.rule model, you need to provide values for required fields: sequence, carrier_id, variable, operator, max_value, list_base_price, list_price, variable_factor. Readonly fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "delivery.price.rule", "table_name": ""}
+{"text": "Show me the relational structure of barcode.labels.", "response": "The barcode.labels model has 3 relational fields: product_get_ids -> barcode.product.lines; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "barcode.labels", "table_name": ""}
+{"text": "How is kpi.item implemented technically?", "response": "The kpi.item model is defined in module: kpi_scorecard. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kpi.item", "table_name": ""}
+{"text": "Describe the field structure of website.mass_mailing.popup.", "response": "The website.mass_mailing.popup model has 10 fields: mailing_list_id, website_id, popup_content, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, html: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "website.mass_mailing.popup", "table_name": ""}
+{"text": "How do I use the report.dynamic_accounts_report.day_book model?", "response": "To use the report.dynamic_accounts_report.day_book model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.day_book", "table_name": ""}
+{"text": "What modules define barcode.product.lines?", "response": "The barcode.product.lines model is defined in module: dynamic_barcode_labels. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "barcode.product.lines", "table_name": ""}
+{"text": "Which fields in generate.pos.voucher.wizard are computed?", "response": "The generate.pos.voucher.wizard model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "generate.pos.voucher.wizard", "table_name": ""}
+{"text": "What business logic is in resource.calendar.attendance?", "response": "To use the resource.calendar.attendance model, you need to provide values for required fields: name, dayofweek, hour_from, hour_to, calendar_id, day_period. Readonly fields: two_weeks_calendar, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "resource.calendar.attendance", "table_name": ""}
+{"text": "Can you explain the purpose of whatsapp.template?", "response": "The whatsapp.template model represents whatsapp.template in the ERP system. It contains 10 fields and is used to manage whatsapp.template data. Key fields include: name, message, is_default, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "whatsapp.template", "table_name": ""}
+{"text": "What business logic is in website.robots?", "response": "To use the website.robots 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "website.robots", "table_name": ""}
+{"text": "Which fields in gamification.karma.tracking are computed?", "response": "The gamification.karma.tracking model is defined in module: gamification. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "gamification.karma.tracking", "table_name": ""}
+{"text": "How to query project.task.type.delete.wizard data?", "response": "To use the project.task.type.delete.wizard model, you need to provide values for required fields: none. Readonly fields: tasks_count, stages_active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.task.type.delete.wizard", "table_name": ""}
+{"text": "What are the technical details of product.cross?", "response": "The product.cross model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.cross", "table_name": ""}
+{"text": "List all fields in the purchase.agreement.approval.matrix.lines model.", "response": "The purchase.agreement.approval.matrix.lines model has 20 fields: sequence, user_ids, minimum_approver, status, time, feedback, approved, approval, user_approved_ids, approval_matrix, sequence2, user_ids_domain, last_approved, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 5, many2many: 3, char: 2, datetime: 4, text: 1, boolean: 1, many2one: 4.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.agreement.approval.matrix.lines", "table_name": ""}
+{"text": "How does report.project.task.user relate to other models?", "response": "The report.project.task.user model has 5 relational fields: user_id -> res.users; project_id -> project.project; company_id -> res.company; partner_id -> res.partner; stage_id -> project.task.type. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.project.task.user", "table_name": ""}
+{"text": "How do I use the split.pr.line.wizard model?", "response": "To use the split.pr.line.wizard model, you need to provide values for required fields: none. Readonly fields: name, user_id, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "split.pr.line.wizard", "table_name": ""}
+{"text": "Describe the implementation of equip3.pos.membership.report.", "response": "The equip3.pos.membership.report model is defined in module: equip3_pos_membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "equip3.pos.membership.report", "table_name": ""}
+{"text": "Describe the lost.customer model in Odoo.", "response": "The lost.customer model represents lost.customer in the ERP system. It contains 9 fields and is used to manage lost.customer data. Key fields include: name, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "lost.customer", "table_name": ""}
+{"text": "Which fields in sh.purchase.payment.report.wizard are computed?", "response": "The sh.purchase.payment.report.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.payment.report.wizard", "table_name": ""}
+{"text": "How to query ir.qweb data?", "response": "To use the ir.qweb model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.qweb", "table_name": ""}
+{"text": "How do I use the checklist.reason model?", "response": "To use the checklist.reason model, you need to provide values for required fields: reason. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "checklist.reason", "table_name": ""}
+{"text": "Describe the field structure of snailmail.confirm.", "response": "The snailmail.confirm model has 4 fields: model_name, id, display_name, __last_update. Field types distribution: char: 2, integer: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "snailmail.confirm", "table_name": ""}
+{"text": "What fields does purchase.line.wiz have?", "response": "The purchase.line.wiz model has 9 fields: purchase_order_line_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.line.wiz", "table_name": ""}
+{"text": "Show me the fields of coupon.generate.wizard.", "response": "The coupon.generate.wizard model has 11 fields: nbr_coupons, generation_type, partners_domain, has_partner_email, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, selection: 1, char: 2, boolean: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "coupon.generate.wizard", "table_name": ""}
+{"text": "How does purchase.order.wizard relate to other models?", "response": "The purchase.order.wizard model has 6 relational fields: order_line -> purchase.order.line.wizard; partner_id -> res.partner; partner_ids -> res.partner; so_id -> sale.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.order.wizard", "table_name": ""}
+{"text": "What are the technical details of calendar.alarm_manager?", "response": "The calendar.alarm_manager model is defined in module: calendar. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "calendar.alarm_manager", "table_name": ""}
+{"text": "Can you explain the purpose of ir.demo?", "response": "The ir.demo model represents Demo in the ERP system. It contains 7 fields and is used to manage demo data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.demo", "table_name": ""}
+{"text": "How is setu.inventory.overstock.bi.report implemented technically?", "response": "The setu.inventory.overstock.bi.report model is defined in module: setu_advance_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "setu.inventory.overstock.bi.report", "table_name": ""}
+{"text": "Can you explain the purpose of account.journal.group?", "response": "The account.journal.group model represents Account Journal Group in the ERP system. It contains 11 fields and is used to manage account journal group data. Key fields include: name, company_id, excluded_journal_ids, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.journal.group", "table_name": ""}
+{"text": "List all fields in the payable.opening.balance model.", "response": "The payable.opening.balance model has 14 fields: partner_opening_bal_id, vendor_id, invoice, date, description, due_date, amount_due, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 3, date: 2, float: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "payable.opening.balance", "table_name": ""}
+{"text": "What methods are available in hr.employee.category?", "response": "The hr.employee.category model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hr.employee.category", "table_name": ""}
+{"text": "Show me the fields of mail.followers.", "response": "The mail.followers model has 11 fields: res_model, res_id, partner_id, channel_id, subtype_ids, name, email, is_active, id, display_name, __last_update. Field types distribution: char: 4, many2one_reference: 1, many2one: 2, many2many: 1, boolean: 1, integer: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.followers", "table_name": ""}
+{"text": "What are the technical details of update.historical.data?", "response": "The update.historical.data model is defined in module: equip3_update_historical. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "update.historical.data", "table_name": ""}
+{"text": "What is the void.order.line model?", "response": "The void.order.line model represents void.order.line in the ERP system. It contains 12 fields and is used to manage void.order.line data. Key fields include: name, session_id, order_id, void_uid, cashier_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "void.order.line", "table_name": ""}
+{"text": "Describe the field structure of purchase.order.wizard.", "response": "The purchase.order.wizard model has 17 fields: order_line, partner_id, date_planned, order_selection, sh_group_by_partner, sh_cancel_old_rfqs, sh_create_po, partner_ids, so_id, is_dropship, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, many2one: 4, datetime: 4, selection: 3, boolean: 2, many2many: 1, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.order.wizard", "table_name": ""}
+{"text": "What are the technical details of account.tour.upload.bill.email.confirm?", "response": "The account.tour.upload.bill.email.confirm model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.tour.upload.bill.email.confirm", "table_name": ""}
+{"text": "Describe the implementation of account.tax.group.", "response": "The account.tax.group model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.tax.group", "table_name": ""}
+{"text": "What are the relationships in account.payment.method?", "response": "The account.payment.method model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.payment.method", "table_name": ""}
+{"text": "What foreign keys exist in theme.ir.ui.view?", "response": "The theme.ir.ui.view model has 3 relational fields: copy_ids -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "theme.ir.ui.view", "table_name": ""}
+{"text": "How is invoice.recurring used in the system?", "response": "The invoice.recurring model represents Invoice Order Recurring in the ERP system. It contains 78 fields and is used to manage invoice order recurring data. Key fields include: name, partner_id, start_date, active, title, note, order_line, sh_move_line, last_generated_date, end_date, type, journal_id, company_id, state, recurring_interval, recurring_interval_unit, stop_recurring_interval, stop_recurring_interval_unit, signature, signed_by, signed_on, online_signature, invoice_filter_type_domain, sh_invoice_recurring_count, sh_bill_recurring_count, sh_cust_credit_recurring_count, sh_vendor_credit_recurring_count, sh_sale_receipt_recurring_count, sh_purchase_receipt_recurring_count, sh_journal_entry_recurring_count, created_by, created_date, branch_id, prepayment_journal, analytic_group_ids, subtotal, total, total_taxes, invoice_ids, remaining_journal_entry, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "invoice.recurring", "table_name": ""}
+{"text": "What fields does report.equip3_accounting_reports.debt_collection have?", "response": "The report.equip3_accounting_reports.debt_collection model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.debt_collection", "table_name": ""}
+{"text": "What fields does stock.putaway.rule have?", "response": "The stock.putaway.rule model has 16 fields: product_id, location_in_id, location_out_id, sequence, company_id, product_ids, check_product_ids, check_category_ids, category_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, integer: 2, many2many: 2, boolean: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.putaway.rule", "table_name": ""}
+{"text": "What modules define stock.inventory.approval.matrix.line?", "response": "The stock.inventory.approval.matrix.line model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.inventory.approval.matrix.line", "table_name": ""}
+{"text": "How to query report.stock.report_product_template_replenishment data?", "response": "To use the report.stock.report_product_template_replenishment model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.stock.report_product_template_replenishment", "table_name": ""}
+{"text": "What modules define product.warehouse.cost.wizard?", "response": "The product.warehouse.cost.wizard model is defined in module: equip3_accounting_stockoperation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.warehouse.cost.wizard", "table_name": ""}
+{"text": "What does the theme.utils model represent?", "response": "The theme.utils model represents Theme Utils in the ERP system. It contains 3 fields and is used to manage theme utils data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "theme.utils", "table_name": ""}
+{"text": "Show me the fields of ir.rule.", "response": "The ir.rule model has 17 fields: name, active, model_id, groups, domain_force, perm_read, perm_write, perm_create, perm_unlink, global, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 6, many2one: 3, many2many: 1, text: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.rule", "table_name": ""}
+{"text": "What modules define purchase.order.split?", "response": "The purchase.order.split model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.order.split", "table_name": ""}
+{"text": "What are common use cases for ir.logging?", "response": "To use the ir.logging model, you need to provide values for required fields: name, type, message, path, func, line. Readonly fields: create_uid, create_date, write_uid, write_date, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.logging", "table_name": ""}
+{"text": "What is the l10n_id_efaktur.efaktur.range model?", "response": "The l10n_id_efaktur.efaktur.range model represents Available E-faktur range in the ERP system. It contains 11 fields and is used to manage available e-faktur range data. Key fields include: company_id, max, min, available, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "l10n_id_efaktur.efaktur.range", "table_name": ""}
+{"text": "What business logic is in cancel.closing.entries?", "response": "To use the cancel.closing.entries 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cancel.closing.entries", "table_name": ""}
+{"text": "What does the purchase.request.line model represent?", "response": "The purchase.request.line model represents Purchase Request Line in the ERP system. It contains 98 fields and is used to manage purchase request line data. Key fields include: name, product_qty, request_id, company_id, analytic_account_id, requested_by, assigned_to, date_start, description, origin, is_editable, specifications, request_state, supplier_id, cancelled, purchased_qty, purchase_lines, purchase_state, move_dest_ids, orderpoint_id, purchase_request_allocation_ids, qty_in_progress, qty_done, qty_cancelled, qty_to_buy, pending_qty_to_receive, estimated_cost, currency_id, mr_line_id, cancelled_qty, branch_id, sequence, sequence2, remaning_qty, purchase_req_budget, rem_budget, purchase_req_state, assigned_to_partner_id, set_order, is_goods_orders, is_services_orders, price_total, dest_loc_id, picking_type_dest, current_qty, date_required, product_uom_id, product_uom_category_id, incoming_stock, purchase_req_budget_2, realized_amount, confirm_purchase_req_budget, confirm_realized_amount, confirm_budget_data, analytic_account_group_ids, purchase_order, agreement_id, agreement_state, tender_qty, tender_line_ids, purchase_order_line_ids, qty_received, is_assets_orders, product_id, barcode, merchendise_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.request.line", "table_name": ""}
+{"text": "How do I use the auditlog.http.request model?", "response": "To use the auditlog.http.request model, you need to provide values for required fields: none. Readonly fields: display_name, id, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "auditlog.http.request", "table_name": ""}
+{"text": "What does the sh.notification.logger model represent?", "response": "The sh.notification.logger model represents It keeps updated about the notification being sent in the ERP system. It contains 12 fields and is used to manage it keeps updated about the notification being sent data. Key fields include: name, error, datetime, base_config_id, status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.notification.logger", "table_name": ""}
+{"text": "List all fields in the res.branch model.", "response": "The res.branch model has 50 fields: analytic_tag_ids, name, company_id, telephone, address, street, street_2, city, state_id, country_id, zip_code, active_company_sequence, npwp, user_id, user_ids, is_external_link, config_ids, branch_code, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 4, char: 12, many2one: 9, text: 1, integer: 6, boolean: 6, one2many: 5, selection: 2, date: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.branch", "table_name": ""}
+{"text": "What are the relationships in pos.service.charge?", "response": "The pos.service.charge model has 5 relational fields: product_id -> product.product; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.service.charge", "table_name": ""}
+{"text": "What does the report.report_finished_good_rework model represent?", "response": "The report.report_finished_good_rework model represents Finished Good Rework Report in the ERP system. It contains 3 fields and is used to manage finished good rework report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.report_finished_good_rework", "table_name": ""}
+{"text": "How is stock.package.destination used in the system?", "response": "The stock.package.destination model represents Stock Package Destination in the ERP system. It contains 11 fields and is used to manage stock package destination data. Key fields include: picking_id, move_line_ids, location_dest_id, filtered_location, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.package.destination", "table_name": ""}
+{"text": "How to create records in product.image?", "response": "To use the product.image model, you need to provide values for required fields: name, image_1920. Readonly fields: embed_code, can_image_1024_be_zoomed, image_1024, image_512, image_256, image_128, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.image", "table_name": ""}
+{"text": "What foreign keys exist in order.driver.message?", "response": "The order.driver.message model has 4 relational fields: order_id -> sale.order; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "order.driver.message", "table_name": ""}
+{"text": "How to create records in approval.matrix.direct.purchase.line?", "response": "To use the approval.matrix.direct.purchase.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: sequence2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "approval.matrix.direct.purchase.line", "table_name": ""}
+{"text": "What foreign keys exist in account.user.reminder?", "response": "The account.user.reminder model has 5 relational fields: company_id -> res.company; branch_id -> res.branch; account_line_ids -> account.user.reminder.lines; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.user.reminder", "table_name": ""}
+{"text": "How do I use the new.customer model?", "response": "To use the new.customer 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "new.customer", "table_name": ""}
+{"text": "What operations can I perform on stock.immediate.transfer?", "response": "To use the stock.immediate.transfer 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.immediate.transfer", "table_name": ""}
+{"text": "What data can be stored in forecast.quantity?", "response": "The forecast.quantity model has 11 fields: schedule_date, reference, product_id, source_location, destination_location, forecast_qty, product_uom, state, id, display_name, __last_update. Field types distribution: datetime: 2, many2one: 2, char: 4, float: 1, selection: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "forecast.quantity", "table_name": ""}
+{"text": "What business logic is in hr.job?", "response": "To use the hr.job model, you need to provide values for required fields: name, state. Readonly fields: expected_employees, no_of_employee, state, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "hr.job", "table_name": ""}
+{"text": "How is report.sh_purchase_reports.sh_representative_report_doc used in the system?", "response": "The report.sh_purchase_reports.sh_representative_report_doc model represents purchase person report abstract model in the ERP system. It contains 3 fields and is used to manage purchase person report abstract model data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.sh_purchase_reports.sh_representative_report_doc", "table_name": ""}
+{"text": "What operations can I perform on partner.opening.balance?", "response": "To use the partner.opening.balance model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "partner.opening.balance", "table_name": ""}
+{"text": "How to create records in report.equip3_accounting_reports.customer_statement?", "response": "To use the report.equip3_accounting_reports.customer_statement model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_accounting_reports.customer_statement", "table_name": ""}
+{"text": "Which fields in stock.return.picking.inter.company are computed?", "response": "The stock.return.picking.inter.company model is defined in module: bi_inter_company_transfer. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.return.picking.inter.company", "table_name": ""}
+{"text": "What modules define purchase.change.request.line?", "response": "The purchase.change.request.line model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.change.request.line", "table_name": ""}
+{"text": "What operations can I perform on resource.test?", "response": "To use the resource.test model, you need to provide values for required fields: resource_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "resource.test", "table_name": ""}
+{"text": "What is the theme.ir.attachment model?", "response": "The theme.ir.attachment model represents Theme Attachments in the ERP system. It contains 11 fields and is used to manage theme attachments data. Key fields include: name, key, url, copy_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "theme.ir.attachment", "table_name": ""}
+{"text": "What models are connected to target.activity.line?", "response": "The target.activity.line model has 5 relational fields: user_id -> res.users; activity_id -> target.activity; activity_type -> mail.activity.type; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "target.activity.line", "table_name": ""}
+{"text": "What does the purchase.order.report model represent?", "response": "The purchase.order.report model represents Purchase Order Report in the ERP system. It contains 11 fields and is used to manage purchase order report data. Key fields include: start_date, end_date, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order.report", "table_name": ""}
+{"text": "What are the technical details of account.efaktur.generate?", "response": "The account.efaktur.generate model is defined in module: equip3_accounting_efaktur. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.efaktur.generate", "table_name": ""}
+{"text": "Show me the fields of account.fiscal.position.tax.", "response": "The account.fiscal.position.tax model has 11 fields: position_id, company_id, tax_src_id, tax_dest_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.fiscal.position.tax", "table_name": ""}
+{"text": "What modules define purchase.request.line.make.purchase.order?", "response": "The purchase.request.line.make.purchase.order model is defined in module: purchase_request. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.request.line.make.purchase.order", "table_name": ""}
+{"text": "What operations can I perform on create.purchase.request.direct.lines?", "response": "To use the create.purchase.request.direct.lines model, you need to provide values for required fields: wiz_id, name, product_uom_id. Readonly fields: wiz_id, rem_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "create.purchase.request.direct.lines", "table_name": ""}
+{"text": "Describe the field structure of s.curve.budget.", "response": "The s.curve.budget model has 16 fields: budget_to_analyze, crossovered_budget, budgetary_position, period_start_date, period_end_date, crossovered_purchase_budget, product_purchase_budget, crossovered_acount_budget, acount_account_budget, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, many2one: 5, many2many: 3, date: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "s.curve.budget", "table_name": ""}
+{"text": "Can you explain the purpose of sh.purchase.product.indent.wizard?", "response": "The sh.purchase.product.indent.wizard model represents Purchase Product Indent Wizard in the ERP system. It contains 14 fields and is used to manage purchase product indent wizard data. Key fields include: sh_start_date, sh_end_date, sh_partner_ids, sh_status, sh_category_ids, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.purchase.product.indent.wizard", "table_name": ""}
+{"text": "Describe the field structure of sms.template.preview.", "response": "The sms.template.preview model has 13 fields: sms_template_id, lang, model_id, body, resource_ref, no_record, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, selection: 1, char: 2, reference: 1, boolean: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sms.template.preview", "table_name": ""}
+{"text": "What models are connected to base.partner.merge.line?", "response": "The base.partner.merge.line model has 3 relational fields: wizard_id -> base.partner.merge.automatic.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.partner.merge.line", "table_name": ""}
+{"text": "What modules define account.deposit.reconcile?", "response": "The account.deposit.reconcile model is defined in module: equip3_accounting_deposit. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.deposit.reconcile", "table_name": ""}
+{"text": "What operations can I perform on ks.sales.forecast?", "response": "To use the ks.sales.forecast model, you need to provide values for required fields: ks_start_date, ks_end_date, ks_forecast_unit, ks_forecast_period. Readonly fields: ks_name, ks_default_forecast_method, ks_model, ks_is_predicted_method, ks_resp, ks_resd, ks_resq, ks_sp, ks_sd, ks_sq, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks.sales.forecast", "table_name": ""}
+{"text": "Tell me about the payment.acquirer model.", "response": "The payment.acquirer model represents Payment Acquirer in the ERP system. It contains 45 fields and is used to manage payment acquirer data. Key fields include: name, color, display_as, description, sequence, company_id, view_template_id, registration_view_template_id, state, capture_manually, journal_id, check_validity, country_ids, pre_msg, auth_msg, pending_msg, done_msg, cancel_msg, save_token, token_implemented, authorize_implemented, fees_implemented, fees_active, fees_dom_fixed, fees_dom_var, fees_int_fixed, fees_int_var, qr_code, module_id, module_state, module_to_buy, image_128, payment_icon_ids, payment_flow, inbound_payment_method_ids, provider, so_reference_type, website_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "payment.acquirer", "table_name": ""}
+{"text": "What is the account.partner.ageing model?", "response": "The account.partner.ageing model represents Parner Ageing Report in the ERP system. It contains 18 fields and is used to manage parner ageing report data. Key fields include: period_length, date_from, result_selection, partner_ids, partner_category_ids, section_num, journal_ids, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.partner.ageing", "table_name": ""}
+{"text": "What data can be stored in mail.thread.phone?", "response": "The mail.thread.phone model has 22 fields: phone_sanitized, phone_sanitized_blacklisted, phone_blacklisted, mobile_blacklisted, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, __last_update. Field types distribution: char: 2, boolean: 8, one2many: 3, many2many: 2, integer: 5, many2one: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.thread.phone", "table_name": ""}
+{"text": "How to create records in report.sh_po_tender_management.report_analyze_quotations?", "response": "To use the report.sh_po_tender_management.report_analyze_quotations model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_po_tender_management.report_analyze_quotations", "table_name": ""}
+{"text": "What methods are available in account.invoice.exchange?", "response": "The account.invoice.exchange model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.invoice.exchange", "table_name": ""}
+{"text": "What modules define report.point_of_sale.report_invoice?", "response": "The report.point_of_sale.report_invoice model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.point_of_sale.report_invoice", "table_name": ""}
+{"text": "Can you explain the purpose of sh.base.send.whatsapp.number.wizard?", "response": "The sh.base.send.whatsapp.number.wizard model represents Send whatsapp message wizard in the ERP system. It contains 11 fields and is used to manage send whatsapp message wizard data. Key fields include: partner_ids, whatsapp_mobile, message, crm_lead_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.base.send.whatsapp.number.wizard", "table_name": ""}
+{"text": "Which fields in approval.matrix.vendor.reject are computed?", "response": "The approval.matrix.vendor.reject model is defined in module: equip3_purchase_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "approval.matrix.vendor.reject", "table_name": ""}
+{"text": "Show me the fields of ir.qweb.field.image_url.", "response": "The ir.qweb.field.image_url model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.image_url", "table_name": ""}
+{"text": "How to query ir.model.constraint data?", "response": "To use the ir.model.constraint model, you need to provide values for required fields: name, model, module, type. Readonly fields: id, display_name, create_uid, write_uid, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.model.constraint", "table_name": ""}
+{"text": "How to query uom.uom data?", "response": "To use the uom.uom model, you need to provide values for required fields: name, category_id, factor, factor_inv, rounding, uom_type. Readonly fields: factor_inv, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "uom.uom", "table_name": ""}
+{"text": "What are the available fields for multiple.rfq?", "response": "The multiple.rfq model has 9 fields: vendor_ids, product_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "multiple.rfq", "table_name": ""}
+{"text": "What operations can I perform on setu.inventory.fsn.xyz.analysis.report?", "response": "To use the setu.inventory.fsn.xyz.analysis.report model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.fsn.xyz.analysis.report", "table_name": ""}
+{"text": "What are the available fields for product.warehouse.cost?", "response": "The product.warehouse.cost model has 10 fields: product_id, product_cost_line_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.warehouse.cost", "table_name": ""}
+{"text": "Describe the implementation of project.task.type.delete.wizard.", "response": "The project.task.type.delete.wizard model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "project.task.type.delete.wizard", "table_name": ""}
+{"text": "What are common use cases for account.asset.depreciation.line?", "response": "To use the account.asset.depreciation.line model, you need to provide values for required fields: name, sequence, asset_id, amount, remaining_value, depreciated_value, currency_id. Readonly fields: parent_state, move_check, move_posted_check, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.asset.depreciation.line", "table_name": ""}
+{"text": "Show me the fields of pos.sale.summary.wizard.", "response": "The pos.sale.summary.wizard model has 14 fields: start_dt, end_dt, report_type, only_summary, res_user_ids, company_id, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, char: 2, boolean: 1, many2many: 1, many2one: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.sale.summary.wizard", "table_name": ""}
+{"text": "What models are connected to sale.report?", "response": "The sale.report model has 22 relational fields: product_id -> product.product; product_uom -> uom.uom; partner_id -> res.partner; company_id -> res.company; user_id -> res.users; product_tmpl_id -> product.template; categ_id -> product.category; pricelist_id -> product.pricelist; analytic_account_id -> account.analytic.account; team_id -> crm.team; country_id -> res.country; industry_id -> res.partner.industry; commercial_partner_id -> res.partner; campaign_id -> utm.campaign; medium_id -> utm.medium; source_id -> utm.source; order_id -> sale.order; warehouse_id -> stock.warehouse; website_id -> website; branch_id -> res.branch; city_id -> res.country.city; state_id -> res.country.state. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.report", "table_name": ""}
+{"text": "What is the queue.jobs.kill model?", "response": "The queue.jobs.kill model represents Kill job processes and cancel jobs in the ERP system. It contains 8 fields and is used to manage kill job processes and cancel jobs data. Key fields include: job_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "queue.jobs.kill", "table_name": ""}
+{"text": "What data can be stored in warranty.tag?", "response": "The warranty.tag model has 9 fields: tag_name, tag_desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "warranty.tag", "table_name": ""}
+{"text": "Describe the many2many relations for split.pr.line.wizard.", "response": "The split.pr.line.wizard model has 7 relational fields: wizard_id -> split.pr.wizard; pr_line_id -> purchase.request.line; user_id -> res.users; new_user_id -> res.users; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "split.pr.line.wizard", "table_name": ""}
+{"text": "Show me the fields of account.tax.report.wizard.", "response": "The account.tax.report.wizard model has 13 fields: 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 types distribution: many2many: 1, date: 2, selection: 1, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.tax.report.wizard", "table_name": ""}
+{"text": "What are the available fields for mrp.production.backorder.line?", "response": "The mrp.production.backorder.line model has 10 fields: mrp_production_backorder_id, mrp_production_id, to_backorder, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, boolean: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.production.backorder.line", "table_name": ""}
+{"text": "Show me the fields of stock.picking.batch.validate.", "response": "The stock.picking.batch.validate model has 12 fields: name, warehouse_id, scheduled_date, user_id, stock_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, date: 1, one2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.picking.batch.validate", "table_name": ""}
+{"text": "How to query cancel.closing.entries data?", "response": "To use the cancel.closing.entries 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cancel.closing.entries", "table_name": ""}
+{"text": "What fields does crm.phonecall.report have?", "response": "The crm.phonecall.report model has 16 fields: user_id, team_id, priority, nbr_cases, state, create_date, delay_close, duration, delay_open, partner_id, company_id, opening_date, date_closed, id, display_name, __last_update. Field types distribution: many2one: 4, selection: 2, integer: 2, datetime: 4, float: 3, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.phonecall.report", "table_name": ""}
+{"text": "What business logic is in whatsapp.template?", "response": "To use the whatsapp.template model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "whatsapp.template", "table_name": ""}
+{"text": "How is list.product implemented technically?", "response": "The list.product model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "list.product", "table_name": ""}
+{"text": "What data can be stored in account.asset.depreciation.line?", "response": "The account.asset.depreciation.line model has 19 fields: name, sequence, asset_id, parent_state, amount, remaining_value, depreciated_value, depreciation_date, move_id, move_check, move_posted_check, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 5, selection: 1, float: 3, date: 1, boolean: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.asset.depreciation.line", "table_name": ""}
+{"text": "How do I use the account.setup.bank.manual.config model?", "response": "To use the account.setup.bank.manual.config model, you need to provide values for required fields: res_partner_bank_id, new_journal_name, acc_number, partner_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update, acc_type, sanitized_acc_number, company_id, journal_id. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.setup.bank.manual.config", "table_name": ""}
+{"text": "How to create records in payment.voucher.line?", "response": "To use the payment.voucher.line model, you need to provide values for required fields: none. Readonly fields: invoice_date, currency_id, state, voucher_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "payment.voucher.line", "table_name": ""}
+{"text": "How to create records in account.tax.repartition.line?", "response": "To use the account.tax.repartition.line model, you need to provide values for required fields: factor_percent, repartition_type. Readonly fields: factor, tax_id, tax_fiscal_country_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.tax.repartition.line", "table_name": ""}
+{"text": "What are the technical details of ir.qweb.field.integer?", "response": "The ir.qweb.field.integer model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.qweb.field.integer", "table_name": ""}
+{"text": "Which fields in stock.valuation.layer are computed?", "response": "The stock.valuation.layer model is defined in module: stock_account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.valuation.layer", "table_name": ""}
+{"text": "How is account.print.journal implemented technically?", "response": "The account.print.journal model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.print.journal", "table_name": ""}
+{"text": "List all fields in the crm.activity.report model.", "response": "The crm.activity.report model has 21 fields: date, lead_create_date, date_conversion, date_deadline, date_closed, author_id, user_id, team_id, lead_id, body, subtype_id, mail_activity_type_id, country_id, company_id, stage_id, partner_id, lead_type, active, id, display_name, __last_update. Field types distribution: datetime: 5, date: 1, many2one: 10, html: 1, selection: 1, boolean: 1, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "crm.activity.report", "table_name": ""}
+{"text": "How do I use the stock.package.destination model?", "response": "To use the stock.package.destination model, you need to provide values for required fields: picking_id, move_line_ids, location_dest_id. Readonly fields: move_line_ids, filtered_location, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.package.destination", "table_name": ""}
+{"text": "What methods are available in user.order.dic?", "response": "The user.order.dic model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "user.order.dic", "table_name": ""}
+{"text": "What are common use cases for sh.model.fields.purchase.order.selection?", "response": "To use the sh.model.fields.purchase.order.selection model, you need to provide values for required fields: value, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.model.fields.purchase.order.selection", "table_name": ""}
+{"text": "What models are connected to receipt.voucher?", "response": "The receipt.voucher model has 22 relational fields: create_by -> res.users; payment_ids -> account.payment; partner_id -> res.partner; partner_ids -> res.partner; bank_id -> account.journal; customer_invoice_ids -> account.move; currency_id -> res.currency; company_id -> res.company; branch_id -> res.branch; receipt_voucher_line_ids -> receipt.voucher.line; customer_allowed_ids -> account.move; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, customer_invoice_ids, customer_allowed_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "receipt.voucher", "table_name": ""}
+{"text": "How is combo.option.item implemented technically?", "response": "The combo.option.item model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "combo.option.item", "table_name": ""}
+{"text": "Describe the many2many relations for purchase.requisition.", "response": "The purchase.requisition model has 30 relational fields: user_id -> res.users; company_id -> res.company; purchase_ids -> purchase.order; line_ids -> purchase.requisition.line; product_id -> product.product; currency_id -> res.currency; warehouse_id -> stock.warehouse; picking_type_id -> stock.picking.type; purchase_id -> purchase.order; type_id -> purchase.requisition.type; purchase_request_id -> purchase.request; branch_id -> res.branch; account_tag_ids -> account.analytic.tag; destination_warehouse -> stock.warehouse; approval_matrix_id -> approval.matrix.blanket.order; approved_matrix_ids -> approval.matrix.blanket.order.line; approval_matrix_line_id -> approval.matrix.blanket.order.line; partner_id -> res.partner; vendor_id -> res.partner; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: account_tag_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.requisition", "table_name": ""}
+{"text": "Describe the many2many relations for vendor.evaluation.template.", "response": "The vendor.evaluation.template model has 3 relational fields: evaluation_lines -> vendor.evaluation.template.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "vendor.evaluation.template", "table_name": ""}
+{"text": "Describe the field structure of report.excel.param.", "response": "The report.excel.param model has 15 fields: sequence, report_excel_id, name, code, type_param, param_ir_model_id, wizard_param_ir_model_field_id, param_required, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 5, char: 3, selection: 1, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.excel.param", "table_name": ""}
+{"text": "What fields does queue.job.dashboard have?", "response": "The queue.job.dashboard model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "queue.job.dashboard", "table_name": ""}
+{"text": "Describe the field structure of qiscus.wa.template.content.", "response": "The qiscus.wa.template.content model has 13 fields: template_id, name, language, content_id, content, category, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 2, text: 1, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "qiscus.wa.template.content", "table_name": ""}
+{"text": "How to query sms.composer data?", "response": "To use the sms.composer model, you need to provide values for required fields: composition_mode, body. Readonly fields: res_ids_count, active_domain, active_domain_count, comment_single_recipient, recipient_valid_count, recipient_invalid_count, recipient_single_description, recipient_single_number, recipient_single_valid, sanitized_numbers, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sms.composer", "table_name": ""}
+{"text": "What are the relationships in mrp.production?", "response": "The mrp.production model has 43 relational fields: product_id -> product.product; allowed_product_ids -> product.product; product_tmpl_id -> product.template; product_uom_id -> uom.uom; lot_producing_id -> stock.production.lot; product_uom_category_id -> uom.category; picking_type_id -> stock.picking.type; location_src_id -> stock.location; location_dest_id -> stock.location; bom_id -> mrp.bom; move_raw_ids -> stock.move; move_finished_ids -> stock.move; move_byproduct_ids -> stock.move; finished_move_line_ids -> stock.move.line; workorder_ids -> mrp.workorder; move_dest_ids -> stock.move; user_id -> res.users; company_id -> res.company; procurement_group_id -> procurement.group; orderpoint_id -> stock.warehouse.orderpoint; scrap_ids -> stock.scrap; production_location_id -> stock.location; picking_ids -> stock.picking; sh_mrp_quality_check_ids -> sh.mrp.quality.check; sh_mrp_quality_alert_ids -> sh.mrp.quality.alert; sh_mrp_pass_fail_ids -> sh.mrp.pass.fail; sh_mrp_pics_ids -> sh.mrp.pics; sh_mrp_measurement_ids -> sh.mrp.measurement; sh_mrp_qc_measurement_ids -> sh.mrp.qc.measurement; attachment_ids -> ir.attachment; sh_mrp_quality_point_id -> sh.qc.point; partner_id -> res.partner; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: allowed_product_ids, picking_ids, attachment_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.production", "table_name": ""}
+{"text": "Tell me about the report.equip3_accounting_reports.cash_flow_statement model.", "response": "The report.equip3_accounting_reports.cash_flow_statement model represents report.equip3_accounting_reports.cash_flow_statement in the ERP system. It contains 3 fields and is used to manage report.equip3_accounting_reports.cash_flow_statement data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.cash_flow_statement", "table_name": ""}
+{"text": "List all fields in the account.budget.post model.", "response": "The account.budget.post model has 11 fields: name, account_ids, company_id, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2many: 1, many2one: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.budget.post", "table_name": ""}
+{"text": "What are common use cases for crm.lead.lost?", "response": "To use the crm.lead.lost 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.lead.lost", "table_name": ""}
+{"text": "How to create records in setu.inventory.fsn.xyz.analysis.report?", "response": "To use the setu.inventory.fsn.xyz.analysis.report model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.fsn.xyz.analysis.report", "table_name": ""}
+{"text": "List all fields in the res.config model.", "response": "The res.config model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.config", "table_name": ""}
+{"text": "How is hr.plan.activity.type implemented technically?", "response": "The hr.plan.activity.type model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hr.plan.activity.type", "table_name": ""}
+{"text": "Describe the implementation of account.reconcile.model.line.template.", "response": "The account.reconcile.model.line.template model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.reconcile.model.line.template", "table_name": ""}
+{"text": "How to create records in purchase.down.payment?", "response": "To use the purchase.down.payment model, you need to provide values for required fields: none. Readonly fields: is_service_work_order, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.down.payment", "table_name": ""}
+{"text": "How is account.financial.year.op implemented technically?", "response": "The account.financial.year.op model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.financial.year.op", "table_name": ""}
+{"text": "Describe the many2many relations for crm.sales.tracking.history.", "response": "The crm.sales.tracking.history model has 5 relational fields: sales_ids -> res.users; history_table_ids -> salesperson.tracking.history; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: sales_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.sales.tracking.history", "table_name": ""}
+{"text": "How do I use the uom.uom model?", "response": "To use the uom.uom model, you need to provide values for required fields: name, category_id, factor, factor_inv, rounding, uom_type. Readonly fields: factor_inv, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "uom.uom", "table_name": ""}
+{"text": "What modules define pos.coupon.program?", "response": "The pos.coupon.program model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.coupon.program", "table_name": ""}
+{"text": "How to create records in stock.valuation.adjustment.lines?", "response": "To use the stock.valuation.adjustment.lines model, you need to provide values for required fields: cost_id, product_id, quantity. Readonly fields: name, cost_line_id, move_id, final_cost, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.valuation.adjustment.lines", "table_name": ""}
+{"text": "What are the available fields for mail.alias.mixin?", "response": "The mail.alias.mixin model has 18 fields: alias_id, id, display_name, __last_update, alias_name, alias_model_id, alias_user_id, alias_defaults, alias_force_thread_id, alias_domain, alias_parent_model_id, alias_parent_thread_id, alias_bounced_content, alias_contact, create_uid, create_date, write_uid, write_date. Field types distribution: many2one: 6, integer: 3, char: 3, datetime: 3, text: 1, html: 1, selection: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.alias.mixin", "table_name": ""}
+{"text": "What modules define approval.matrix.blanket.order?", "response": "The approval.matrix.blanket.order model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "approval.matrix.blanket.order", "table_name": ""}
+{"text": "What are the technical details of auditlog.rule?", "response": "The auditlog.rule model is defined in module: auditlog. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "auditlog.rule", "table_name": ""}
+{"text": "How do I use the ks_dashboard_ninja.item_goal model?", "response": "To use the ks_dashboard_ninja.item_goal 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_dashboard_ninja.item_goal", "table_name": ""}
+{"text": "Show me the relational structure of sh.stock.move.global.check.", "response": "The sh.stock.move.global.check model has 7 relational fields: product_id -> product.product; sh_quality_point_id -> sh.qc.point; picking_id -> stock.picking; attachment_ids -> ir.attachment; move_id -> stock.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.stock.move.global.check", "table_name": ""}
+{"text": "Describe the field structure of account.asset.asset.", "response": "The account.asset.asset model has 86 fields: entry_count, name, code, value, currency_id, note, category_id, date, active, partner_id, method_number, method_period, method_end, method_progress_factor, value_residual, method_time, prorata, depreciation_line_ids, salvage_value, invoice_id, type, account_analytic_id, analytic_tag_ids, first_depreciation_manual_date, user_id, is_monthly_depreciation, is_reset_january, months_remaining, method, cut_off_asset_date, date_first_depreciation, fiscal_category_id, method_fiscal, asset_type, asset_type_1, sub_asset_type, non_building_type, is_monthly_depreciation_fiscal, is_reset_january_fiscal, months_remaining_fiscal, method_number_fiscal, method_period_fiscal, method_end_fiscal, depreciation_line_ids_fiscal, asset_history_lines_ids, asset_value_residual, account_cip_id, state, state1, state2, approval_matrix_id, approved_matrix_ids, is_approval_matrix, is_approve_button, approval_matrix_line_id, request_partner_id, company_id, branch_id, asset_sequence, product_id, fiscal_prorata_temporis, location, po_ref, asset_post_entries_count, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 14, char: 6, float: 5, many2one: 17, text: 1, date: 4, boolean: 14, selection: 12, one2many: 7, many2many: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.asset.asset", "table_name": ""}
+{"text": "Which fields in receipt.payment.line.debit are computed?", "response": "The receipt.payment.line.debit model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "receipt.payment.line.debit", "table_name": ""}
+{"text": "What fields does stock.warehouse.orderpoint have?", "response": "The stock.warehouse.orderpoint model has 114 fields: active, snoozed_until, product_tmpl_id, product_id, product_category_id, product_uom, product_uom_name, product_min_qty, product_max_qty, qty_multiple, group_id, allowed_location_ids, rule_ids, json_lead_days_popover, lead_days_date, allowed_route_ids, route_id, qty_on_hand, qty_forecast, qty_to_order, show_bom, bom_id, show_supplier, location_id, name, source_location_id, action_to_take, trigger, start_date, start_month, end_date, end_month, is_replenish_document_created, purchase_request_id, purchase_order_id, material_request_id, internal_transfer_id, replenish_document_status, is_mo_created, periods, run_rate_days, safety_stock, safety_stock_select, stock_days, responsible_id, branch_id, average_quantity_last_year, lead_days_last_year, average_quantity_run_rate_days, lead_days_run_rate_days, run_rate_type, company_id, warehouse_id, filter_warehouse_id, is_minimum_quantity, is_safety_stock_quantity, select_period, notification_user_ids, pr_status, rfq_status, itr_status, mr_status, from_days_before, run_rate_qty, lead_days, period_date, period_month, run_rate_period_before, run_rate_period_after, qty_check, is_low_stock, path, quantity_restock, is_quantity_restock, qty_restock, supplier_id, 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. Field types distribution: boolean: 17, date: 5, many2one: 25, char: 13, float: 16, one2many: 5, many2many: 7, selection: 16, integer: 6, text: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.warehouse.orderpoint", "table_name": ""}
+{"text": "How is mrp.quality.check.report implemented technically?", "response": "The mrp.quality.check.report model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.quality.check.report", "table_name": ""}
+{"text": "What fields does account.bank.statement.closebalance have?", "response": "The account.bank.statement.closebalance model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.bank.statement.closebalance", "table_name": ""}
+{"text": "Describe the implementation of sh.target.commision.new.", "response": "The sh.target.commision.new model is defined in module: equip3_sale_team_commission. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.target.commision.new", "table_name": ""}
+{"text": "What models are connected to product.expiry.config?", "response": "The product.expiry.config model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.expiry.config", "table_name": ""}
+{"text": "Describe the ir.default model in Odoo.", "response": "The ir.default model represents Default Values in the ERP system. It contains 12 fields and is used to manage default values data. Key fields include: field_id, user_id, company_id, condition, json_value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.default", "table_name": ""}
+{"text": "Describe the field structure of sh.payment.report.wizard.", "response": "The sh.payment.report.wizard model has 17 fields: date_start, date_end, state, user_ids, company_ids, company_id, currency_precision, user_data_dic, grand_journal_dic, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, selection: 1, many2many: 3, many2one: 3, integer: 2, one2many: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.payment.report.wizard", "table_name": ""}
+{"text": "What business logic is in report_excel_export_gen?", "response": "To use the report_excel_export_gen 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report_excel_export_gen", "table_name": ""}
+{"text": "What methods are available in membership.invoice?", "response": "The membership.invoice model is defined in module: membership. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "membership.invoice", "table_name": ""}
+{"text": "Describe the implementation of product.pricelist.", "response": "The product.pricelist model is defined in module: product. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.pricelist", "table_name": ""}
+{"text": "What operations can I perform on ai.memory?", "response": "To use the ai.memory model, you need to provide values for required fields: context, content, importance, collection_type, user_id. Readonly fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ai.memory", "table_name": ""}
+{"text": "Describe the field structure of mail.notification.", "response": "The mail.notification model has 15 fields: mail_message_id, mail_id, res_partner_id, notification_status, is_read, read_date, failure_reason, sms_id, sms_number, notification_type, letter_id, failure_type, id, display_name, __last_update. Field types distribution: many2one: 5, selection: 3, boolean: 1, datetime: 2, text: 1, char: 2, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.notification", "table_name": ""}
+{"text": "What are the relationships in stock.track.confirmation?", "response": "The stock.track.confirmation model has 4 relational fields: tracking_line_ids -> stock.track.line; inventory_id -> stock.inventory; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.track.confirmation", "table_name": ""}
+{"text": "What are the relationships in order.picking?", "response": "The order.picking model has 4 relational fields: move_id -> account.move; order_picking_line_ids -> order.picking.lines; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "order.picking", "table_name": ""}
+{"text": "What business logic is in service.work.order?", "response": "To use the service.work.order model, you need to provide values for required fields: none. Readonly fields: name, partner_id, account_analytic_tag_ids, date_planned, company_id, branch_id, checklist_ids, milestone_name, contract_term, move_id, account_move_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "service.work.order", "table_name": ""}
+{"text": "What data can be stored in invoice.template.footer?", "response": "The invoice.template.footer model has 10 fields: template_id, field_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "invoice.template.footer", "table_name": ""}
+{"text": "Describe the implementation of mail.thread.cc.", "response": "The mail.thread.cc model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.thread.cc", "table_name": ""}
+{"text": "What are the technical details of pos.promotion.tebus.murah?", "response": "The pos.promotion.tebus.murah model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.promotion.tebus.murah", "table_name": ""}
+{"text": "What foreign keys exist in theme.ir.attachment?", "response": "The theme.ir.attachment model has 3 relational fields: copy_ids -> ir.attachment; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "theme.ir.attachment", "table_name": ""}
+{"text": "How does sh.model.fields.global.selection relate to other models?", "response": "The sh.model.fields.global.selection model has 3 relational fields: sh_field_id -> sh.custom.field.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.model.fields.global.selection", "table_name": ""}
+{"text": "How to create records in pos.category?", "response": "To use the pos.category model, you need to provide values for required fields: name. Readonly fields: amount_footer, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.category", "table_name": ""}
+{"text": "What is the account.analytic.distribution model?", "response": "The account.analytic.distribution model represents Analytic Account Distribution in the ERP system. It contains 12 fields and is used to manage analytic account distribution data. Key fields include: account_id, percentage, name, tag_id, analytic_group_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.analytic.distribution", "table_name": ""}
+{"text": "What foreign keys exist in queue.requeue.job?", "response": "The queue.requeue.job model has 3 relational fields: job_ids -> queue.job; create_uid -> res.users; write_uid -> res.users. Many2many fields: job_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "queue.requeue.job", "table_name": ""}
+{"text": "Show me the relational structure of report.sh_sale_reports.sh_sale_invoice_summary_doc.", "response": "The report.sh_sale_reports.sh_sale_invoice_summary_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_sale_invoice_summary_doc", "table_name": ""}
+{"text": "Describe the implementation of material.request.show.stock.", "response": "The material.request.show.stock model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "material.request.show.stock", "table_name": ""}
+{"text": "What does the utm.source model represent?", "response": "The utm.source model represents UTM Source in the ERP system. It contains 8 fields and is used to manage utm source data. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "utm.source", "table_name": ""}
+{"text": "Describe the many2many relations for whatsapp.template.message.variable.", "response": "The whatsapp.template.message.variable model has 3 relational fields: wa_id -> whatsapp.template.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "whatsapp.template.message.variable", "table_name": ""}
+{"text": "How do I use the crm.lead.lost model?", "response": "To use the crm.lead.lost 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.lead.lost", "table_name": ""}
+{"text": "What are the relationships in base_import.tests.models.char.required?", "response": "The base_import.tests.models.char.required model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.char.required", "table_name": ""}
+{"text": "What are the technical details of receipt.voucher?", "response": "The receipt.voucher model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "receipt.voucher", "table_name": ""}
+{"text": "What are the available fields for account.move.reversal?", "response": "The account.move.reversal model has 18 fields: move_ids, new_move_ids, date_mode, date, reason, refund_method, journal_id, company_id, residual, currency_id, move_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, selection: 2, date: 1, char: 3, many2one: 5, monetary: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.move.reversal", "table_name": ""}
+{"text": "What data can be stored in ai.memory.export.import.wizard?", "response": "The ai.memory.export.import.wizard model has 11 fields: operation, import_file, import_filename, import_mode, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 2, binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ai.memory.export.import.wizard", "table_name": ""}
+{"text": "List all fields in the report.equip3_pos_report.report_top_selling model.", "response": "The report.equip3_pos_report.report_top_selling model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_pos_report.report_top_selling", "table_name": ""}
+{"text": "What foreign keys exist in pos.loyalty.rule?", "response": "The pos.loyalty.rule model has 6 relational fields: loyalty_id -> pos.loyalty; pos_loyalty_category_ids -> pos.loyalty.category; product_ids -> product.product; category_ids -> pos.category; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_loyalty_category_ids, product_ids, category_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.loyalty.rule", "table_name": ""}
+{"text": "Show me the relational structure of pos.sync.session.order.", "response": "The pos.sync.session.order model has 7 relational fields: line_ids -> pos.sync.session.order.line; pos_config_id -> pos.config; pos_session_id -> pos.session; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.sync.session.order", "table_name": ""}
+{"text": "What data can be stored in monthly.account.budget.lines?", "response": "The monthly.account.budget.lines model has 41 fields: monthly_budget_id, account_id, jan_month, feb_month, march_month, april_month, may_month, june_month, july_month, august_month, sep_month, oct_month, nov_month, dec_month, jan_actual, feb_actual, march_actual, april_actual, may_actual, june_actual, july_actual, august_actual, sep_actual, oct_actual, nov_actual, dec_actual, planned_amount, actual_amount, over_budget, account_plan_id, year_id, year_name, date_start, date_end, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 26, selection: 2, char: 2, date: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "monthly.account.budget.lines", "table_name": ""}
+{"text": "What data can be stored in combo.option.item?", "response": "The combo.option.item model has 11 fields: combo_option_id, product_id, product_variant_id, extra_price, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "combo.option.item", "table_name": ""}
+{"text": "How to create records in account.group.template?", "response": "To use the account.group.template model, you need to provide values for required fields: chart_template_id, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.group.template", "table_name": ""}
+{"text": "Show me the relational structure of report.account.report_invoice.", "response": "The report.account.report_invoice model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.account.report_invoice", "table_name": ""}
+{"text": "Describe the field structure of account.bank.statement.closebalance.", "response": "The account.bank.statement.closebalance model has 7 fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.bank.statement.closebalance", "table_name": ""}
+{"text": "Which fields in ir.actions.actions are computed?", "response": "The ir.actions.actions model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.actions.actions", "table_name": ""}
+{"text": "What modules define account.loan.line?", "response": "The account.loan.line model is defined in module: account_loan. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.loan.line", "table_name": ""}
+{"text": "How is base.module.uninstall used in the system?", "response": "The base.module.uninstall model represents Module Uninstall in the ERP system. It contains 11 fields and is used to manage module uninstall data. Key fields include: show_all, module_id, module_ids, model_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.module.uninstall", "table_name": ""}
+{"text": "Describe the field structure of report.stock.report_stock_rule.", "response": "The report.stock.report_stock_rule model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.stock.report_stock_rule", "table_name": ""}
+{"text": "Describe the implementation of mailing.trace.report.", "response": "The mailing.trace.report model is defined in module: mass_mailing. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mailing.trace.report", "table_name": ""}
+{"text": "Which fields in auditlog.log are computed?", "response": "The auditlog.log model is defined in module: auditlog. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "auditlog.log", "table_name": ""}
+{"text": "How to create records in return.inter.transfer.company.line?", "response": "To use the return.inter.transfer.company.line model, you need to provide values for required fields: none. Readonly fields: price_unit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "return.inter.transfer.company.line", "table_name": ""}
+{"text": "Show me the relational structure of barcode.product.lines.", "response": "The barcode.product.lines model has 6 relational fields: product_id -> product.product; lot_id -> stock.production.lot; wizard_id -> barcode.labels; barcode -> product.template.barcode; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "barcode.product.lines", "table_name": ""}
+{"text": "How do I use the replenishment.history.wizard model?", "response": "To use the replenishment.history.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "replenishment.history.wizard", "table_name": ""}
+{"text": "Show me the fields of mrp.labor.group.", "response": "The mrp.labor.group model has 13 fields: name, head_id, labor_ids, company_id, branch_id, is_branch_required, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 5, many2many: 1, boolean: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.labor.group", "table_name": ""}
+{"text": "What models are connected to report_excel_gen?", "response": "The report_excel_gen model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report_excel_gen", "table_name": ""}
+{"text": "What operations can I perform on account.account?", "response": "To use the account.account model, you need to provide values for required fields: name, code, user_type_id, company_id. Readonly fields: balance, credit, debit, initial_balance, used, internal_type, internal_group, company_id, group_id, root_id, opening_balance, is_off_balance, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.account", "table_name": ""}
+{"text": "What business logic is in rma.reject.reason?", "response": "To use the rma.reject.reason model, you need to provide values for required fields: reason. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "rma.reject.reason", "table_name": ""}
+{"text": "Show me the fields of update.historical.data.", "response": "The update.historical.data model has 57 fields: name, action, error_message, start_date, end_date, batch, limit, run_hour_from, run_hour_to, picking_return_id, list_data_double, list_data_double_count, picking_return_count, product_ids, list_data_issue, list_data_issue_quant, quant_ids_data, list_data_issue_count, warehouse_ids, list_data_quant_count, list_data_je_created_ids, list_data_je_count, list_data_product_count, list_data_issue_svl_double_create, list_data_issue_svl_double_create_count, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 11, selection: 3, text: 1, date: 4, integer: 16, many2one: 6, many2many: 4, one2many: 4, boolean: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "update.historical.data", "table_name": ""}
+{"text": "What fields does approval.matrix.vendor.reject have?", "response": "The approval.matrix.vendor.reject model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "approval.matrix.vendor.reject", "table_name": ""}
+{"text": "What operations can I perform on sh.push.notification?", "response": "To use the sh.push.notification 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.push.notification", "table_name": ""}
+{"text": "What business logic is in res.lang?", "response": "To use the res.lang model, you need to provide values for required fields: name, code, url_code, direction, date_format, time_format, week_start, grouping, decimal_point. Readonly fields: flag_image_url, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.lang", "table_name": ""}
+{"text": "What business logic is in ks_dashboard_item.multiplier?", "response": "To use the ks_dashboard_item.multiplier model, you need to provide values for required fields: none. Readonly fields: ks_model_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_dashboard_item.multiplier", "table_name": ""}
+{"text": "What are common use cases for setu.inventory.fsn.analysis.report?", "response": "To use the setu.inventory.fsn.analysis.report model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.fsn.analysis.report", "table_name": ""}
+{"text": "What foreign keys exist in equip3.reporting.asset.wizard?", "response": "The equip3.reporting.asset.wizard model has 3 relational fields: year -> sh.fiscal.year; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "equip3.reporting.asset.wizard", "table_name": ""}
+{"text": "What operations can I perform on sh.notification.logger?", "response": "To use the sh.notification.logger 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.notification.logger", "table_name": ""}
+{"text": "What are the technical details of ks.sales.forecast.report?", "response": "The ks.sales.forecast.report model is defined in module: ks_sales_forecast. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks.sales.forecast.report", "table_name": ""}
+{"text": "Show me the relational structure of rn.approval_matrix_line.", "response": "The rn.approval_matrix_line model has 7 relational fields: approver -> res.users; last_approved -> res.users; rn_approval_matrix_id1 -> rn.approval.matrix; picking_id -> stock.picking; approved_users -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: approver, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "rn.approval_matrix_line", "table_name": ""}
+{"text": "List all fields in the report.equip3_kitchen_reports.report_kitchen_production model.", "response": "The report.equip3_kitchen_reports.report_kitchen_production model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_kitchen_reports.report_kitchen_production", "table_name": ""}
+{"text": "How to query calendar.event.cancel.wizard data?", "response": "To use the calendar.event.cancel.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "calendar.event.cancel.wizard", "table_name": ""}
+{"text": "What methods are available in sh.sale.product.indent.xls?", "response": "The sh.sale.product.indent.xls model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.sale.product.indent.xls", "table_name": ""}
+{"text": "How to query sale.excel.report data?", "response": "To use the sale.excel.report model, you need to provide values for required fields: none. Readonly fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.excel.report", "table_name": ""}
+{"text": "What foreign keys exist in reference.purchase.price?", "response": "The reference.purchase.price model has 8 relational fields: branch_id -> res.branch; product_id -> product.product; product_tmpl_id -> product.template; available_product_id -> product.template; company_id -> res.company; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "reference.purchase.price", "table_name": ""}
+{"text": "What are the relationships in barcode.nomenclature?", "response": "The barcode.nomenclature model has 3 relational fields: rule_ids -> barcode.rule; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "barcode.nomenclature", "table_name": ""}
+{"text": "What does the limit.request.wizard model represent?", "response": "The limit.request.wizard model represents Limit Request Wizard in the ERP system. It contains 7 fields and is used to manage limit request wizard data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "limit.request.wizard", "table_name": ""}
+{"text": "What are the relationships in sh.split.rfq.wizard?", "response": "The sh.split.rfq.wizard model has 4 relational fields: purchase_order_id -> purchase.order; ps_order_ids -> purchase.order.split; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.split.rfq.wizard", "table_name": ""}
+{"text": "What are the relationships in vendor.evaluation?", "response": "The vendor.evaluation model has 19 relational fields: vendor -> res.partner; manager -> res.users; user_id -> res.users; evaluation_template_id -> vendor.evaluation.template; evaluation_eval_ids -> vendor.evaluation.template.eval; branch_id -> res.branch; company_id -> res.company; vendor_res -> res.partner; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "vendor.evaluation", "table_name": ""}
+{"text": "What are the relationships in z.report.wizard?", "response": "The z.report.wizard model has 5 relational fields: pos_session_ids -> pos.session; company_id -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_session_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "z.report.wizard", "table_name": ""}
+{"text": "What are the available fields for receipt.payment?", "response": "The receipt.payment model has 63 fields: name, partner_id, amount, journal_id, currency_id, clearing_account_id, move_id, date, payment_ref, memo, due_date, receive_date, clearing_date, company_id, branch_id, diff_amount, writeoff_acc_id, naration, create_uid, create_date, partner_type, line_credit_ids, line_debit_ids, state, total_amount_credit, total_amount_debit, payment_id_count, 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, write_uid, write_date, __last_update. Field types distribution: char: 9, many2one: 16, monetary: 4, date: 3, datetime: 6, text: 2, selection: 4, one2many: 6, integer: 6, boolean: 5, many2many: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "receipt.payment", "table_name": ""}
+{"text": "What are the technical details of stock.picking.to.batch?", "response": "The stock.picking.to.batch model is defined in module: stock_picking_batch. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.picking.to.batch", "table_name": ""}
+{"text": "What data can be stored in ir.model.data?", "response": "The ir.model.data model has 14 fields: name, complete_name, model, module, res_id, noupdate, reference, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 6, many2one_reference: 1, boolean: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.model.data", "table_name": ""}
+{"text": "Describe the implementation of pos.session.log.cashier.", "response": "The pos.session.log.cashier model is defined in module: equip3_pos_general. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.session.log.cashier", "table_name": ""}
+{"text": "What are the available fields for mass.editing.wizard?", "response": "The mass.editing.wizard model has 13 fields: selected_item_qty, remaining_item_qty, operation_description_info, operation_description_warning, operation_description_danger, message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 3, text: 4, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mass.editing.wizard", "table_name": ""}
+{"text": "What business logic is in mailing.contact?", "response": "To use the mailing.contact model, you need to provide values for required fields: none. Readonly fields: opt_out, email_normalized, is_blacklisted, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mailing.contact", "table_name": ""}
+{"text": "Show me the relational structure of report.accounting_pdf_reports.report_general_ledger.", "response": "The report.accounting_pdf_reports.report_general_ledger model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.accounting_pdf_reports.report_general_ledger", "table_name": ""}
+{"text": "Show me the relational structure of stock.rules.report.", "response": "The stock.rules.report model has 6 relational fields: product_id -> product.product; product_tmpl_id -> product.template; warehouse_ids -> stock.warehouse; so_route_ids -> stock.location.route; create_uid -> res.users; write_uid -> res.users. Many2many fields: warehouse_ids, so_route_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.rules.report", "table_name": ""}
+{"text": "What are the relationships in coupon.reward?", "response": "The coupon.reward model has 6 relational fields: reward_product_id -> product.product; discount_specific_product_ids -> product.product; reward_product_uom_id -> uom.uom; discount_line_product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: discount_specific_product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "coupon.reward", "table_name": ""}
+{"text": "How is new.customer used in the system?", "response": "The new.customer model represents new.customer in the ERP system. It contains 9 fields and is used to manage new.customer data. Key fields include: name, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "new.customer", "table_name": ""}
+{"text": "Describe the account.debt.collection model in Odoo.", "response": "The account.debt.collection model represents Debt Collection in the ERP system. It contains 51 fields and is used to manage debt collection data. Key fields include: name, partner_id, date, person_in_charge, currency_id, amount, start_date, end_date, deadline_date, branch_id, create_uid, create_date, line_debt_collection, state, is_pic, 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, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.debt.collection", "table_name": ""}
+{"text": "What methods are available in milestone.contract.template.checklist?", "response": "The milestone.contract.template.checklist model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "milestone.contract.template.checklist", "table_name": ""}
+{"text": "Show me the fields of extract.rfq.wizard.", "response": "The extract.rfq.wizard model has 8 fields: purchase_order_extract_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "extract.rfq.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for pos.promotion.multilevel.gift.", "response": "The pos.promotion.multilevel.gift model has 4 relational fields: product_id -> product.product; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.promotion.multilevel.gift", "table_name": ""}
+{"text": "Show me the relational structure of whatsapp.scan.qr.", "response": "The whatsapp.scan.qr model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "whatsapp.scan.qr", "table_name": ""}
+{"text": "What are the relationships in invoice.templates?", "response": "The invoice.templates model has 8 relational fields: invoice_header_ids -> ir.model.fields; invoice_table_ids -> ir.model.fields; invoice_footer_ids -> ir.model.fields; invoice_header_sequence_ids -> invoice.template.header; invoice_table_sequence_ids -> invoice.template.table; invoice_footer_sequence_ids -> invoice.template.footer; create_uid -> res.users; write_uid -> res.users. Many2many fields: invoice_header_ids, invoice_table_ids, invoice_footer_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "invoice.templates", "table_name": ""}
+{"text": "What fields does res.city have?", "response": "The res.city model has 11 fields: name, zipcode, country_id, state_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.city", "table_name": ""}
+{"text": "Describe the field structure of milestone.contract.template.checklist.", "response": "The milestone.contract.template.checklist model has 10 fields: template_id, name, desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "milestone.contract.template.checklist", "table_name": ""}
+{"text": "Describe the many2many relations for ir.exports.", "response": "The ir.exports model has 3 relational fields: export_fields -> ir.exports.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.exports", "table_name": ""}
+{"text": "Describe the implementation of res.country.group.", "response": "The res.country.group model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.country.group", "table_name": ""}
+{"text": "What models are connected to mrp.bom.tools?", "response": "The mrp.bom.tools model has 11 relational fields: bom_id -> mrp.bom; company_id -> res.company; workorder_id -> mrp.workorder; product_id -> product.product; uom_id -> uom.uom; operation_id -> mrp.routing.workcenter; allowed_operation_ids -> mrp.routing.workcenter; operation_two_ids -> mrp.bom.operation; operation_two_id -> mrp.bom.operation; create_uid -> res.users; write_uid -> res.users. Many2many fields: allowed_operation_ids, operation_two_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.bom.tools", "table_name": ""}
+{"text": "Describe the purchase.bill.union model in Odoo.", "response": "The purchase.bill.union model represents Purchases & Bills Union in the ERP system. It contains 12 fields and is used to manage purchases & bills union data. Key fields include: name, reference, partner_id, date, amount, currency_id, company_id, vendor_bill_id, purchase_order_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.bill.union", "table_name": ""}
+{"text": "How is snailmail.letter.missing.required.fields implemented technically?", "response": "The snailmail.letter.missing.required.fields model is defined in module: snailmail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "snailmail.letter.missing.required.fields", "table_name": ""}
+{"text": "How to query stock.location.route data?", "response": "To use the stock.location.route model, you need to provide values for required fields: name. Readonly fields: warehouse_domain_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.location.route", "table_name": ""}
+{"text": "What fields does mass.editing.line have?", "response": "The mass.editing.line model has 13 fields: sequence, server_action_id, model_id, field_id, widget_option, apply_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 5, char: 2, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mass.editing.line", "table_name": ""}
+{"text": "Can you explain the purpose of sh.stock.move.pass.fail?", "response": "The sh.stock.move.pass.fail model represents Stock Move Quality Measurement Pass Fail in the ERP system. It contains 11 fields and is used to manage stock move quality measurement pass fail data. Key fields include: product_id, sh_message, sh_quality_point_id, picking_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.stock.move.pass.fail", "table_name": ""}
+{"text": "Can you explain the purpose of account.pettycash.fund.close?", "response": "The account.pettycash.fund.close model represents Petty Cash Fund Closing Wizard in the ERP system. It contains 11 fields and is used to manage petty cash fund closing wizard data. Key fields include: fund, receivable_account, effective_date, close_balance, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.pettycash.fund.close", "table_name": ""}
+{"text": "What are the technical details of cust.credit.limit.data.line?", "response": "The cust.credit.limit.data.line model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "cust.credit.limit.data.line", "table_name": ""}
+{"text": "What modules define ir.actions.act_window?", "response": "The ir.actions.act_window model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.actions.act_window", "table_name": ""}
+{"text": "How to query mail.resend.cancel data?", "response": "To use the mail.resend.cancel model, you need to provide values for required fields: none. Readonly fields: help_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mail.resend.cancel", "table_name": ""}
+{"text": "Tell me about the website.menu model.", "response": "The website.menu model represents Website Menu in the ERP system. It contains 25 fields and is used to manage website menu data. Key fields include: name, url, page_id, new_window, sequence, website_id, parent_id, child_id, parent_path, is_visible, group_ids, is_mega_menu, mega_menu_content, mega_menu_classes, theme_template_id, is_display_in_delivery_control_app, user_logged, user_not_logged, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "website.menu", "table_name": ""}
+{"text": "Describe the implementation of global.search.", "response": "The global.search model is defined in module: sh_backmate_theme_adv. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "global.search", "table_name": ""}
+{"text": "What operations can I perform on milestone.contract.template.purchase?", "response": "To use the milestone.contract.template.purchase 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "milestone.contract.template.purchase", "table_name": ""}
+{"text": "What methods are available in ir.attachment?", "response": "The ir.attachment model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.attachment", "table_name": ""}
+{"text": "What business logic is in service.work.order.checklist?", "response": "To use the service.work.order.checklist model, you need to provide values for required fields: name. Readonly fields: state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "service.work.order.checklist", "table_name": ""}
+{"text": "What data can be stored in report.dynamic_accounts_report.balance_sheet?", "response": "The report.dynamic_accounts_report.balance_sheet model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.dynamic_accounts_report.balance_sheet", "table_name": ""}
+{"text": "How is board.board used in the system?", "response": "The board.board model represents Board in the ERP system. It contains 3 fields and is used to manage board data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "board.board", "table_name": ""}
+{"text": "What models are connected to account.cash.flow.statement?", "response": "The account.cash.flow.statement model has 7 relational fields: account_ids -> account.account; company_ids -> res.company; journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: account_ids, company_ids, journal_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.cash.flow.statement", "table_name": ""}
+{"text": "What are the relationships in account.report.general.ledger?", "response": "The account.report.general.ledger 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.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.report.general.ledger", "table_name": ""}
+{"text": "How does store.filters.groups relate to other models?", "response": "The store.filters.groups model has 3 relational fields: model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "store.filters.groups", "table_name": ""}
+{"text": "What data can be stored in account.move.reversal?", "response": "The account.move.reversal model has 18 fields: move_ids, new_move_ids, date_mode, date, reason, refund_method, journal_id, company_id, residual, currency_id, move_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, selection: 2, date: 1, char: 3, many2one: 5, monetary: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.move.reversal", "table_name": ""}
+{"text": "List all fields in the ai.data.cleanup model.", "response": "The ai.data.cleanup model has 23 fields: name, active, cleanup_interval_days, last_run, next_run, cleanup_old_sessions, session_age_days, cleanup_few_message_sessions, few_message_session_age_days, cleanup_orphaned_messages, cleanup_uploaded_attachments, uploaded_attachments_age_days, cleanup_old_generated_files, generated_files_age_days, cleanup_old_sandbox_folders, sandbox_folders_age_days, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 7, integer: 7, datetime: 5, many2one: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ai.data.cleanup", "table_name": ""}
+{"text": "What are common use cases for setu.inventory.xyz.analysis.report?", "response": "To use the setu.inventory.xyz.analysis.report model, you need to provide values for required fields: none. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.xyz.analysis.report", "table_name": ""}
+{"text": "Describe the field structure of report.account.report_hash_integrity.", "response": "The report.account.report_hash_integrity model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.account.report_hash_integrity", "table_name": ""}
+{"text": "What foreign keys exist in report.dynamic_accounts_report.partner_ledger?", "response": "The report.dynamic_accounts_report.partner_ledger model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.partner_ledger", "table_name": ""}
+{"text": "Can you explain the purpose of customer.deposit.report?", "response": "The customer.deposit.report model represents Customer Deposit Report in the ERP system. It contains 16 fields and is used to manage customer deposit report data. Key fields include: name, partner_id, amount, currency_id, remaining_amount, communication, move_id, return_deposit, payment_date, deposit_reconcile_journal_id, journal_id, deposit_account_id, used_amount, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "customer.deposit.report", "table_name": ""}
+{"text": "What methods are available in pos.promotion.price?", "response": "The pos.promotion.price model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.promotion.price", "table_name": ""}
+{"text": "Describe the choose.delivery.carrier model in Odoo.", "response": "The choose.delivery.carrier model represents Delivery Carrier Selection Wizard in the ERP system. It contains 18 fields and is used to manage delivery carrier selection wizard data. Key fields include: order_id, partner_id, carrier_id, delivery_type, delivery_price, display_price, currency_id, company_id, available_carrier_ids, invoicing_message, delivery_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "choose.delivery.carrier", "table_name": ""}
+{"text": "What foreign keys exist in sale.order.template?", "response": "The sale.order.template model has 7 relational fields: sale_order_template_line_ids -> sale.order.template.line; sale_order_template_option_ids -> sale.order.template.option; mail_template_id -> mail.template; company_id -> res.company; customer_ids -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: customer_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.order.template", "table_name": ""}
+{"text": "Describe the field structure of project.task.create.sale.order.", "response": "The project.task.create.sale.order model has 17 fields: link_selection, task_id, partner_id, product_id, price_unit, currency_id, commercial_partner_id, sale_order_id, sale_line_id, info_invoice, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, many2one: 9, float: 1, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.task.create.sale.order", "table_name": ""}
+{"text": "Describe the access.group model in Odoo.", "response": "The access.group model represents Access Group in the ERP system. It contains 10 fields and is used to manage access group data. Key fields include: name, user_ids, access_management_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "access.group", "table_name": ""}
+{"text": "How to create records in account.edi.document?", "response": "To use the account.edi.document model, you need to provide values for required fields: move_id, edi_format_id. Readonly fields: name, edi_format_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.edi.document", "table_name": ""}
+{"text": "Describe the account.account.template model in Odoo.", "response": "The account.account.template model represents Templates for Accounts in the ERP system. It contains 18 fields and is used to manage templates for accounts data. Key fields include: currency_id, code, user_type_id, reconcile, note, tax_ids, nocreate, chart_template_id, tag_ids, parent_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.account.template", "table_name": ""}
+{"text": "What are the available fields for invoice.template.table?", "response": "The invoice.template.table model has 10 fields: template_id, field_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, integer: 2, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "invoice.template.table", "table_name": ""}
+{"text": "Describe the many2many relations for account.cash.rounding.", "response": "The account.cash.rounding model has 5 relational fields: profit_account_id -> account.account; loss_account_id -> account.account; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.cash.rounding", "table_name": ""}
+{"text": "What data can be stored in base.document.layout?", "response": "The base.document.layout model has 29 fields: company_id, logo, preview_logo, report_header, report_footer, paperformat_id, external_report_layout_id, font, primary_color, secondary_color, custom_colors, logo_primary_color, logo_secondary_color, report_layout_id, preview, partner_id, phone, email, website, vat, name, country_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, binary: 2, text: 2, selection: 1, char: 10, boolean: 1, html: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.document.layout", "table_name": ""}
+{"text": "What is the purchase.agreement.comparison model?", "response": "The purchase.agreement.comparison model represents purchase.agreement.comparison in the ERP system. It contains 13 fields and is used to manage purchase.agreement.comparison data. Key fields include: agreement_id, partner_id, on_time_rate, fulfillment, final_point, final_star, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.agreement.comparison", "table_name": ""}
+{"text": "What models are connected to stock.picking.batch?", "response": "The stock.picking.batch model has 24 relational fields: user_id -> res.users; picking_ids -> stock.picking; allowed_picking_ids -> stock.picking; move_ids -> stock.move; move_line_ids -> stock.move.line; location_ids -> stock.location; warehouse_id -> stock.warehouse; company_id -> res.company; branch_id -> res.branch; filter_location_ids -> stock.location; picking_type_id -> stock.picking.type; partner_id -> res.partner; stock_picking_batch_ids -> stock.picking.batch.line; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: location_ids, filter_location_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.picking.batch", "table_name": ""}
+{"text": "What fields does wizard.asset.create have?", "response": "The wizard.asset.create model has 16 fields: date, first_depreciation_manual_date, salvage_value, method, method_time, prorata, cut_off_asset_date, method_number_fiscal, method_period_fiscal, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, float: 1, selection: 2, boolean: 1, integer: 4, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "wizard.asset.create", "table_name": ""}
+{"text": "Describe the field structure of pos.top.selling.wizard.", "response": "The pos.top.selling.wizard model has 14 fields: start_dt, end_dt, report_type, no_product, top_selling, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, char: 2, integer: 2, selection: 1, many2one: 4, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.top.selling.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for resource.resource.", "response": "The resource.resource model has 5 relational fields: company_id -> res.company; calendar_id -> resource.calendar; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "resource.resource", "table_name": ""}
+{"text": "What does the barcodes.barcode_events_mixin model represent?", "response": "The barcodes.barcode_events_mixin model represents Barcode Event Mixin in the ERP system. It contains 4 fields and is used to manage barcode event mixin data. Key fields include: _barcode_scanned, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "barcodes.barcode_events_mixin", "table_name": ""}
+{"text": "Describe the implementation of restaurant.printer.", "response": "The restaurant.printer model is defined in module: pos_restaurant. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "restaurant.printer", "table_name": ""}
+{"text": "What is the saleblanket.saleblanket model?", "response": "The saleblanket.saleblanket model represents Sale Blanket in the ERP system. It contains 85 fields and is used to manage sale blanket data. Key fields include: name, partner_id, pricelist_id, payment_term_id, current_user, sale_order_count, expiry_date, creation_date, user_id, order_line_count, state, currency_id, state1, state2, state3, bo_state, bo_state_1, company_id, current_company, branch_id, days_left, analytic_tag_ids, order_line_ids, qty, delivery_qty, remaining_qty, qty_invoiced, reason, delivery_status, approving_matrix_bo_sale_id, is_bo_approval_matrix, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, approved_matrix_ids, amount_untaxed, amount_tax, amount_total, analytic_accounting, invoice_address, delivery_address, is_product_filled, is_active_company, max_line_sequence, report_template_id1, report_template_id, amount_to_text, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "saleblanket.saleblanket", "table_name": ""}
+{"text": "What data can be stored in intrawarehouse.transfer.line?", "response": "The intrawarehouse.transfer.line model has 19 fields: intra_transfer_wizard_id, no, product_id, description, uom_id, source_loc_id, dest_loc_id, qty_transfer, filter_location_ids, warehouse_id, mr_id, mr_line_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 10, integer: 2, text: 1, float: 1, many2many: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "intrawarehouse.transfer.line", "table_name": ""}
+{"text": "Describe the implementation of followup.invoice.tmp.", "response": "The followup.invoice.tmp model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "followup.invoice.tmp", "table_name": ""}
+{"text": "Describe the many2many relations for payment.voucher.", "response": "The payment.voucher model has 26 relational fields: create_by -> res.users; partner_id -> res.partner; partner_ids -> res.partner; bank_id -> account.journal; vendor_bill_ids -> account.move; company_id -> res.company; request_partner_id -> res.partner; currency_id -> res.currency; line_ids -> payment.voucher.line; branch_id -> res.branch; payment_ids -> account.payment; approval_matrix_id -> approval.matrix.accounting; approved_matrix_ids -> approval.matrix.accounting.lines; approval_matrix_line_id -> approval.matrix.accounting.lines; vendor_allowed_ids -> account.move; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, vendor_bill_ids, vendor_allowed_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "payment.voucher", "table_name": ""}
+{"text": "What are the technical details of acrux.chat.message.wizard?", "response": "The acrux.chat.message.wizard model is defined in module: acrux_chat_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "acrux.chat.message.wizard", "table_name": ""}
+{"text": "Tell me about the report.excel model.", "response": "The report.excel model represents Report Excel in the ERP system. It contains 28 fields and is used to manage report excel data. Key fields include: name, active, out_file_name, data, doc_count, datas_fname, template_name_id, sheet_reference, description, description_report, root_model_id, ir_values_id, show_level, show_autofilter, report_excel_param_ids, report_id, report_excel_param_content, report_excel_section_ids, send_email, email_template_id, report_lang_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.excel", "table_name": ""}
+{"text": "What are the available fields for purchase.bill.union?", "response": "The purchase.bill.union model has 12 fields: name, reference, partner_id, date, amount, currency_id, company_id, vendor_bill_id, purchase_order_id, id, display_name, __last_update. Field types distribution: char: 3, many2one: 5, date: 1, float: 1, integer: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.bill.union", "table_name": ""}
+{"text": "Can you explain the purpose of auditlog.autovacuum?", "response": "The auditlog.autovacuum model represents Auditlog - Delete old logs in the ERP system. It contains 7 fields and is used to manage auditlog - delete old logs data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "auditlog.autovacuum", "table_name": ""}
+{"text": "Can you explain the purpose of account.efaktur?", "response": "The account.efaktur model represents account.efaktur in the ERP system. It contains 19 fields and is used to manage account.efaktur data. Key fields include: year, record_id, invoice_id, partner_id, invoice_date, company_id, is_pjap, is_used_pjap, branch_id, is_cancel, is_used, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.efaktur", "table_name": ""}
+{"text": "What models are connected to ks_custom_report.ks_report?", "response": "The ks_custom_report.ks_report model has 13 relational fields: ks_model_id -> ir.model; ks_cr_model_id -> ir.model; ks_tree_view_id -> ir.ui.view; ks_search_view_id -> ir.ui.view; ks_pivot_view_id -> ir.ui.view; ks_cr_column_ids -> ks_custom_report.ks_column; ks_cr_top_menu_id -> ir.ui.menu; ks_cr_group_access -> res.groups; ks_cr_menu_id -> ir.ui.menu; ks_cr_action_id -> ir.actions.act_window; ks_custom_query_report_column_ids -> ks.custom.query.report.column; create_uid -> res.users; write_uid -> res.users. Many2many fields: ks_cr_group_access.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks_custom_report.ks_report", "table_name": ""}
+{"text": "What fields does blanketwiz.blanketwiz have?", "response": "The blanketwiz.blanketwiz model has 8 fields: wiz_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "blanketwiz.blanketwiz", "table_name": ""}
+{"text": "What are the relationships in pos.session?", "response": "The pos.session model has 39 relational fields: company_id -> res.company; config_id -> pos.config; user_id -> res.users; currency_id -> res.currency; cash_journal_id -> account.journal; cash_register_id -> account.bank.statement; order_ids -> pos.order; statement_ids -> account.bank.statement; picking_ids -> stock.picking; move_id -> account.move; payment_method_ids -> pos.payment.method; move_id_old -> account.move; crm_team_id -> crm.team; pos_branch_id -> res.branch; employee_id -> hr.employee; order_log_ids -> pos.order.log; opened_uid -> res.users; pos_config_cashbox_lines_ids -> account.cashbox.line; pos_config_cashbox_clsosing_line_ids -> account.cashbox.line; cashier_id -> res.users; log_cashier_ids -> pos.session.log.cashier; order_with_receivable_invoice_ids -> pos.order; pos_session_cashbox_wizard_ids -> account.cashbox.wizard.line; cash_management_ids -> pos.cash.in.out; cash_history_ids -> pos.cashbox.history; gain_loss_move_id -> account.move; void_ids -> void.order.line; pos_session_bank_cashbox_wizard_ids -> account.cashbox.wizard.bank.line; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: payment_method_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.session", "table_name": ""}
+{"text": "What models are connected to stock.inventory?", "response": "The stock.inventory model has 32 relational fields: line_ids -> stock.inventory.line; move_ids -> stock.move; company_id -> res.company; product_ids -> product.product; warehouse_id -> stock.warehouse; user_id -> res.users; adjustment_account_id -> account.account; filtered_adjustment_account_id -> account.account; analytic_tag_ids -> account.analytic.tag; branch_id -> res.branch; approval_matrix_id -> stock.inventory.approval.matrix; approved_matrix_ids -> stock.inventory.approval.matrix.line; approval_matrix_line_id -> stock.inventory.approval.matrix.line; product_categories -> product.category; location_ids -> stock.location; uom_conversion_ids -> uom.conversion.history; wizard_id -> stock.inventory.wizard; pos_branch_id -> res.branch; account_move_ids -> account.move; user_id_1 -> res.users; user_id_2 -> res.users; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, filtered_adjustment_account_id, analytic_tag_ids, product_categories, location_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.inventory", "table_name": ""}
+{"text": "What data can be stored in assembly.production.record?", "response": "The assembly.production.record model has 84 fields: name, company_id, is_branch_required, product_id, product_tmpl_id, product_qty, rejected_qty, product_uom_id, product_uom_category_id, assembly_bom_id, branch_id, confirm_date, state, move_raw_ids, move_finished_ids, move_byproduct_ids, location_src_id, location_dest_id, picking_type_id, date_planned_start, date_planned_finished, date_deadline, procurement_group_id, move_dest_ids, production_location_id, warehouse_id, product_tracking, account_move_ids, purchase_request_ids, internal_transfer_count, disassembly_record_ids, expiry_days, product_use_expiration_date, finished_lot_ids, byproduct_lot_ids, rejected_lot_ids, show_submit_button, is_autogenerate, default_finished_lot_qty, default_rejected_lot_qty, show_byproduct_lot_tab, byproduct_manual_product_ids, default_byproduct_lot_qty, default_next_byproduct_product_id, any_byproduct_is_autogenerate, all_byproduct_is_autogenerate, component_consumed_qty, svl_value, bom_id, record_type, assembly_record_id, disassembly_remaining_qty, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, many2one: 21, boolean: 12, float: 7, datetime: 7, selection: 5, one2many: 14, integer: 7, many2many: 3, text: 1, date: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "assembly.production.record", "table_name": ""}
+{"text": "How to create records in ir.logging?", "response": "To use the ir.logging model, you need to provide values for required fields: name, type, message, path, func, line. Readonly fields: create_uid, create_date, write_uid, write_date, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.logging", "table_name": ""}
+{"text": "What models are connected to pos.cashbox.history?", "response": "The pos.cashbox.history model has 5 relational fields: opened_by_user_id -> res.users; pos_session_id -> pos.session; pos_config_id -> pos.config; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.cashbox.history", "table_name": ""}
+{"text": "What data can be stored in account.payment.term.line?", "response": "The account.payment.term.line model has 14 fields: value, value_amount, days, day_of_the_month, option, payment_id, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 2, float: 1, integer: 4, many2one: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.payment.term.line", "table_name": ""}
+{"text": "What business logic is in product.expiry.config?", "response": "To use the product.expiry.config model, you need to provide values for required fields: none. Readonly fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.expiry.config", "table_name": ""}
+{"text": "How to create records in cust.credit.limit.data?", "response": "To use the cust.credit.limit.data 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cust.credit.limit.data", "table_name": ""}
+{"text": "List all fields in the base.document.layout model.", "response": "The base.document.layout model has 29 fields: company_id, logo, preview_logo, report_header, report_footer, paperformat_id, external_report_layout_id, font, primary_color, secondary_color, custom_colors, logo_primary_color, logo_secondary_color, report_layout_id, preview, partner_id, phone, email, website, vat, name, country_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, binary: 2, text: 2, selection: 1, char: 10, boolean: 1, html: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.document.layout", "table_name": ""}
+{"text": "Describe the many2many relations for stock.rules.report.", "response": "The stock.rules.report model has 6 relational fields: product_id -> product.product; product_tmpl_id -> product.template; warehouse_ids -> stock.warehouse; so_route_ids -> stock.location.route; create_uid -> res.users; write_uid -> res.users. Many2many fields: warehouse_ids, so_route_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.rules.report", "table_name": ""}
+{"text": "Describe the sh.mrp.measurement model in Odoo.", "response": "The sh.mrp.measurement model represents MRP Quality Measurement in the ERP system. It contains 13 fields and is used to manage mrp quality measurement data. Key fields include: product_id, sh_message, sh_quality_point_id, sh_measure, mrp_id, workorder_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.mrp.measurement", "table_name": ""}
+{"text": "How is base_import.tests.models.o2m used in the system?", "response": "The base_import.tests.models.o2m model represents Tests : Base Import Model, One to Many in the ERP system. It contains 9 fields and is used to manage tests : base import model, one to many data. Key fields include: name, value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base_import.tests.models.o2m", "table_name": ""}
+{"text": "How is kitchen.cooking.list implemented technically?", "response": "The kitchen.cooking.list model is defined in module: equip3_kitchen_operations. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "kitchen.cooking.list", "table_name": ""}
+{"text": "Can you explain the purpose of gamification.badge.user.wizard?", "response": "The gamification.badge.user.wizard model represents Gamification User Badge Wizard in the ERP system. It contains 11 fields and is used to manage gamification user badge wizard data. Key fields include: badge_id, comment, employee_id, user_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "gamification.badge.user.wizard", "table_name": ""}
+{"text": "How does apps.installation.activity.log relate to other models?", "response": "The apps.installation.activity.log model has 3 relational fields: user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "apps.installation.activity.log", "table_name": ""}
+{"text": "What models are connected to accounting.matrix.reject?", "response": "The accounting.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "accounting.matrix.reject", "table_name": ""}
+{"text": "What fields does acrux.chat.select.conversation.wizard have?", "response": "The acrux.chat.select.conversation.wizard model has 8 fields: conversation_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "acrux.chat.select.conversation.wizard", "table_name": ""}
+{"text": "What operations can I perform on sale.commission.excel.report?", "response": "To use the sale.commission.excel.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.commission.excel.report", "table_name": ""}
+{"text": "How is stock.picking.batch.line implemented technically?", "response": "The stock.picking.batch.line model is defined in module: equip3_inventory_operations_countd. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.picking.batch.line", "table_name": ""}
+{"text": "What are the relationships in kpi.scorecard.line?", "response": "The kpi.scorecard.line model has 6 relational fields: kpi_id -> kpi.item; category_id -> kpi.category; period_id -> kpi.period; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kpi.scorecard.line", "table_name": ""}
+{"text": "Which fields in warranty.tag are computed?", "response": "The warranty.tag model is defined in module: bi_warranty_registration. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "warranty.tag", "table_name": ""}
+{"text": "What methods are available in account.report.partner.ledger?", "response": "The account.report.partner.ledger model is defined in module: accounting_pdf_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.report.partner.ledger", "table_name": ""}
+{"text": "How does stock.warn.insufficient.qty.scrap relate to other models?", "response": "The stock.warn.insufficient.qty.scrap model has 6 relational fields: scrap_id -> stock.scrap; product_id -> product.product; location_id -> stock.location; quant_ids -> stock.quant; create_uid -> res.users; write_uid -> res.users. Many2many fields: quant_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.warn.insufficient.qty.scrap", "table_name": ""}
+{"text": "Describe the implementation of asset.depreciation.confirmation.wizard.", "response": "The asset.depreciation.confirmation.wizard model is defined in module: om_account_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "asset.depreciation.confirmation.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for report.equip3_pos_report.report_closed_session.", "response": "The report.equip3_pos_report.report_closed_session model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_pos_report.report_closed_session", "table_name": ""}
+{"text": "What data can be stored in budget.purchase?", "response": "The budget.purchase model has 44 fields: name, parent_id, date_from, date_to, state, state1, state2, purchase_budget_line, company_id, branch_id, account_tag_ids, approval_matrix, request_partner_id, is_allowed_to_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, currency_id, purchase_lines_id, purchase_line_subtotal, date_today, is_use_theoretical_achievement, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 11, date: 3, selection: 3, one2many: 5, many2many: 3, boolean: 8, monetary: 1, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "budget.purchase", "table_name": ""}
+{"text": "What is the nsfp.registration model?", "response": "The nsfp.registration model represents nsfp.registration in the ERP system. It contains 15 fields and is used to manage nsfp.registration data. Key fields include: record_id, fiscal_year, start, end, last_number, registration_date, is_use, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "nsfp.registration", "table_name": ""}
+{"text": "How do I use the payable.opening.balance model?", "response": "To use the payable.opening.balance model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "payable.opening.balance", "table_name": ""}
+{"text": "How is vendor.evaluation used in the system?", "response": "The vendor.evaluation model represents Vendor Evaluation in the ERP system. It contains 108 fields and is used to manage vendor evaluation data. Key fields include: name, state, vendor, period_start, period_end, manager, is_manager, user_id, price_check, price_factor, price, price_cmt, delivery_check, delivery_factor, delivery, delivery_cmt, quality_check, quality_factor, quality, quality_cmt, document_check, document_factor, document, document_cmt, commitment_check, commitment_factor, commitment, commitment_cmt, dependability_check, dependability_factor, dependability, dependability_cmt, skill_check, skill_factor, skill, skill_cmt, support_check, support_factor, support, support_cmt, relation_check, relation_factor, relation, relation_cmt, other_check, other_factor, other, other_cmt, final_point, final_rate, on_time_rate, on_time_rate_check, on_time_rate_factor, on_time_rate_star, on_time_rate_cmt, fulfillment, fulfillment_check, fulfillment_factor, fulfillment_star, fulfillment_cmt, fulfillment_avg, on_time_rate_avg, final_point_avg, vendor_evaluation_count, evaluation_template_id, evaluation_eval_ids, email, business, date, final_cmt, branch_id, company_id, on_time_rate_res, fulfillment_res, vendor_res, final_point_res, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "vendor.evaluation", "table_name": ""}
+{"text": "Which fields in rfm.yearly.analysis.by.segment are computed?", "response": "The rfm.yearly.analysis.by.segment model is defined in module: setu_rfm_analysis. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "rfm.yearly.analysis.by.segment", "table_name": ""}
+{"text": "Describe the implementation of pos.combo.item.", "response": "The pos.combo.item model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.combo.item", "table_name": ""}
+{"text": "What data can be stored in report.equip3_accounting_reports.pettycash_analysis?", "response": "The report.equip3_accounting_reports.pettycash_analysis model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.pettycash_analysis", "table_name": ""}
+{"text": "Which fields in product.warehouse.cost are computed?", "response": "The product.warehouse.cost model is defined in module: equip3_accounting_stockoperation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.warehouse.cost", "table_name": ""}
+{"text": "What operations can I perform on pos.category?", "response": "To use the pos.category model, you need to provide values for required fields: name. Readonly fields: amount_footer, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.category", "table_name": ""}
+{"text": "What is the sh.purchase.category.wizard model?", "response": "The sh.purchase.category.wizard model represents Purchase By Category Wizard in the ERP system. It contains 12 fields and is used to manage purchase by category wizard data. Key fields include: sh_start_date, sh_end_date, sh_category_ids, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.purchase.category.wizard", "table_name": ""}
+{"text": "Describe the field structure of account.asset.category.fiscal.", "response": "The account.asset.category.fiscal model has 25 fields: asset_category_id, is_fiscal_asset_type, method_time, method_number, method_period, method_end, method, asset_type, asset_type_1, sub_asset_type, non_building_type, method_number_fiscal, prorata, cut_off_asset_date, is_monthly_depreciation, is_reset_january, double_declining_method_number, double_declining_method_period, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, boolean: 4, selection: 6, integer: 7, date: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.asset.category.fiscal", "table_name": ""}
+{"text": "What foreign keys exist in sh.target.commision.new?", "response": "The sh.target.commision.new model has 4 relational fields: commission_id -> sh.target.commision; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.target.commision.new", "table_name": ""}
+{"text": "What modules define assets.approval.matrix?", "response": "The assets.approval.matrix model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "assets.approval.matrix", "table_name": ""}
+{"text": "How do I use the sh.sale.product.profit.xls model?", "response": "To use the sh.sale.product.profit.xls model, you need to provide values for required fields: none. Readonly fields: file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.sale.product.profit.xls", "table_name": ""}
+{"text": "List all fields in the decimal.precision model.", "response": "The decimal.precision model has 9 fields: name, digits, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "decimal.precision", "table_name": ""}
+{"text": "What fields does base.language.export have?", "response": "The base.language.export model has 13 fields: name, lang, format, modules, data, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, selection: 3, many2many: 1, binary: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.language.export", "table_name": ""}
+{"text": "Describe the implementation of stock.scrap.", "response": "The stock.scrap model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.scrap", "table_name": ""}
+{"text": "What are the technical details of pos.promotion.discount.apply?", "response": "The pos.promotion.discount.apply model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.promotion.discount.apply", "table_name": ""}
+{"text": "Describe the field structure of purchase.order.report.", "response": "The purchase.order.report model has 11 fields: start_date, end_date, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2many: 2, integer: 1, char: 1, many2one: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.order.report", "table_name": ""}
+{"text": "What business logic is in stock.track.line?", "response": "To use the stock.track.line model, you need to provide values for required fields: none. Readonly fields: product_id, tracking, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.track.line", "table_name": ""}
+{"text": "How to query receipt.payment data?", "response": "To use the receipt.payment model, you need to provide values for required fields: partner_id, journal_id, currency_id, clearing_account_id, date. Readonly fields: name, partner_id, amount, currency_id, move_id, company_id, diff_amount, create_uid, create_date, total_amount_credit, total_amount_debit, payment_id_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, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "receipt.payment", "table_name": ""}
+{"text": "What operations can I perform on project.task.recurrence?", "response": "To use the project.task.recurrence 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.task.recurrence", "table_name": ""}
+{"text": "What are the technical details of mrp.bom.operation?", "response": "The mrp.bom.operation model is defined in module: equip3_manuf_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.bom.operation", "table_name": ""}
+{"text": "What are the relationships in base.language.export?", "response": "The base.language.export model has 3 relational fields: modules -> ir.module.module; create_uid -> res.users; write_uid -> res.users. Many2many fields: modules.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base.language.export", "table_name": ""}
+{"text": "What are the technical details of product.ratio.line?", "response": "The product.ratio.line model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.ratio.line", "table_name": ""}
+{"text": "What are the available fields for res.partner.rfm.segment.history?", "response": "The res.partner.rfm.segment.history model has 16 fields: partner_id, history_date, old_rfm_segment_id, new_rfm_segment_id, old_rfm_score_id, new_rfm_score_id, old_segment_rank, new_segment_rank, engagement_direction, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, date: 1, integer: 4, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.partner.rfm.segment.history", "table_name": ""}
+{"text": "What are the available fields for _unknown?", "response": "The _unknown model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "_unknown", "table_name": ""}
+{"text": "How does sh.sale.product.profit.wizard relate to other models?", "response": "The sh.sale.product.profit.wizard model has 7 relational fields: sh_partner_ids -> res.partner; sh_product_ids -> product.product; company_ids -> res.company; company_id -> res.company; user_order_dic -> user.order.dic; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_partner_ids, sh_product_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.sale.product.profit.wizard", "table_name": ""}
+{"text": "What methods are available in budget.budget?", "response": "The budget.budget model is defined in module: equip3_accounting_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "budget.budget", "table_name": ""}
+{"text": "What are the available fields for account.pettycash.fund.change?", "response": "The account.pettycash.fund.change model has 18 fields: fund, fund_name, custodian, fund_amount, new_amount, payable_account, receivable_account, effective_date, do_receivable, move, is_add_balance, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, char: 2, float: 2, date: 1, boolean: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.pettycash.fund.change", "table_name": ""}
+{"text": "What are the available fields for purchase.request.allocation?", "response": "The purchase.request.allocation model has 17 fields: purchase_request_line_id, company_id, stock_move_id, purchase_line_id, product_id, product_uom_id, requested_product_uom_qty, allocated_product_qty, open_product_qty, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 8, float: 3, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.request.allocation", "table_name": ""}
+{"text": "Describe the implementation of intrawarehouse.transfer.line.", "response": "The intrawarehouse.transfer.line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "intrawarehouse.transfer.line", "table_name": ""}
+{"text": "What is the _unknown model?", "response": "The _unknown model represents Unknown in the ERP system. It contains 3 fields and is used to manage unknown data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "_unknown", "table_name": ""}
+{"text": "What are the relationships in mail.activity.type?", "response": "The mail.activity.type model has 9 relational fields: create_uid -> res.users; res_model_id -> ir.model; default_next_type_id -> mail.activity.type; next_type_ids -> mail.activity.type; previous_type_ids -> mail.activity.type; mail_template_ids -> mail.template; default_user_id -> res.users; initial_res_model_id -> ir.model; write_uid -> res.users. Many2many fields: next_type_ids, previous_type_ids, mail_template_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.activity.type", "table_name": ""}
+{"text": "List all fields in the stock.inventory.approval.matrix.line model.", "response": "The stock.inventory.approval.matrix.line model has 34 fields: sequence, user_ids, minimum_approver, si_approval_matrix, st_inv_id, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 8, many2many: 4, many2one: 6, text: 1, datetime: 4, char: 2, boolean: 6, one2many: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.inventory.approval.matrix.line", "table_name": ""}
+{"text": "What are common use cases for theme.ir.attachment?", "response": "To use the theme.ir.attachment model, you need to provide values for required fields: name, key. Readonly fields: copy_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "theme.ir.attachment", "table_name": ""}
+{"text": "What operations can I perform on milestone.contract.template.checklist?", "response": "To use the milestone.contract.template.checklist 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "milestone.contract.template.checklist", "table_name": ""}
+{"text": "What modules define payment.voucher.matrix.reject?", "response": "The payment.voucher.matrix.reject model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "payment.voucher.matrix.reject", "table_name": ""}
+{"text": "Describe the implementation of mail.thread.phone.", "response": "The mail.thread.phone model is defined in module: phone_validation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.thread.phone", "table_name": ""}
+{"text": "How is change.password.wizard used in the system?", "response": "The change.password.wizard model represents Change Password Wizard in the ERP system. It contains 8 fields and is used to manage change password wizard data. Key fields include: user_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "change.password.wizard", "table_name": ""}
+{"text": "How to create records in access.domain.ah?", "response": "To use the access.domain.ah model, you need to provide values for required fields: model_id. Readonly fields: model_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "access.domain.ah", "table_name": ""}
+{"text": "Describe the field structure of ir.actions.actions.", "response": "The ir.actions.actions model has 14 fields: name, type, xml_id, help, binding_model_id, binding_type, binding_view_types, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, html: 1, many2one: 3, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.actions.actions", "table_name": ""}
+{"text": "What models are connected to purchase.detail.excel.extended?", "response": "The purchase.detail.excel.extended model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.detail.excel.extended", "table_name": ""}
+{"text": "Show me the relational structure of sh.purchase.payment.report.wizard.", "response": "The sh.purchase.payment.report.wizard model has 5 relational fields: user_ids -> res.users; company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, company_ids, branch_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.payment.report.wizard", "table_name": ""}
+{"text": "Tell me about the account.journal.group model.", "response": "The account.journal.group model represents Account Journal Group in the ERP system. It contains 11 fields and is used to manage account journal group data. Key fields include: name, company_id, excluded_journal_ids, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.journal.group", "table_name": ""}
+{"text": "What operations can I perform on purchase.order.history?", "response": "To use the purchase.order.history model, you need to provide values for required fields: none. Readonly fields: order_id, product_id, price_unit, product_qty, product_uom, currency_id, price_subtotal, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.order.history", "table_name": ""}
+{"text": "Show me the relational structure of account.bank.statement.", "response": "The account.bank.statement model has 21 relational fields: currency_id -> res.currency; journal_id -> account.journal; company_id -> res.company; line_ids -> account.bank.statement.line; move_line_ids -> account.move.line; user_id -> res.users; cashbox_start_id -> account.bank.statement.cashbox; cashbox_end_id -> account.bank.statement.cashbox; previous_statement_id -> account.bank.statement; pos_session_id -> pos.session; account_id -> account.account; branch_id -> res.branch; pos_branch_id -> res.branch; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.bank.statement", "table_name": ""}
+{"text": "What are the technical details of wizard.asset.create?", "response": "The wizard.asset.create model is defined in module: equip3_accounting_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "wizard.asset.create", "table_name": ""}
+{"text": "What operations can I perform on partial.quantity.done?", "response": "To use the partial.quantity.done 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "partial.quantity.done", "table_name": ""}
+{"text": "Describe the field structure of login.as.", "response": "The login.as model has 12 fields: group_id, user_id, group_ids, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, many2many: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "login.as", "table_name": ""}
+{"text": "What does the picking.return.line model represent?", "response": "The picking.return.line model represents picking.return.line in the ERP system. It contains 14 fields and is used to manage picking.return.line data. Key fields include: name, product_id, picking_id, purchase_id, sale_id, currency_id, price, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "picking.return.line", "table_name": ""}
+{"text": "What are the available fields for mrp.quality.alert.report?", "response": "The mrp.quality.alert.report model has 13 fields: date_from, date_to, product_ids, user_ids, stage_id, operation_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, many2many: 2, many2one: 3, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.quality.alert.report", "table_name": ""}
+{"text": "Describe the many2many relations for crm.merge.opportunity.", "response": "The crm.merge.opportunity model has 5 relational fields: opportunity_ids -> crm.lead; user_id -> res.users; team_id -> crm.team; create_uid -> res.users; write_uid -> res.users. Many2many fields: opportunity_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.merge.opportunity", "table_name": ""}
+{"text": "What modules define pos.product.bom.line?", "response": "The pos.product.bom.line model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.product.bom.line", "table_name": ""}
+{"text": "Describe the ir.qweb.field.duration model in Odoo.", "response": "The ir.qweb.field.duration model represents Qweb Field Duration in the ERP system. It contains 3 fields and is used to manage qweb field duration data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.qweb.field.duration", "table_name": ""}
+{"text": "Describe the sale.summary.commission.report model in Odoo.", "response": "The sale.summary.commission.report model represents sale.summary.commission.report in the ERP system. It contains 13 fields and is used to manage sale.summary.commission.report data. Key fields include: start_date, end_date, sales_persons, commision_type, company_ids, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.summary.commission.report", "table_name": ""}
+{"text": "Which fields in pos.cashbox.history are computed?", "response": "The pos.cashbox.history model is defined in module: equip3_pos_cashbox. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.cashbox.history", "table_name": ""}
+{"text": "What are the technical details of pos.coupon.generate.wizard?", "response": "The pos.coupon.generate.wizard model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.coupon.generate.wizard", "table_name": ""}
+{"text": "How is stock.backorder.confirmation implemented technically?", "response": "The stock.backorder.confirmation model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.backorder.confirmation", "table_name": ""}
+{"text": "What operations can I perform on project.task.create.sale.order?", "response": "To use the project.task.create.sale.order model, you need to provide values for required fields: link_selection, task_id, partner_id, product_id. Readonly fields: commercial_partner_id, info_invoice, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.task.create.sale.order", "table_name": ""}
+{"text": "What foreign keys exist in asset.cip.line?", "response": "The asset.cip.line model has 6 relational fields: product_id -> product.template; account_id -> account.account; cip_id -> asset.cip; move_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "asset.cip.line", "table_name": ""}
+{"text": "How to query sh.qc.alert.line data?", "response": "To use the sh.qc.alert.line model, you need to provide values for required fields: product_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.qc.alert.line", "table_name": ""}
+{"text": "What operations can I perform on warranty.tag?", "response": "To use the warranty.tag 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "warranty.tag", "table_name": ""}
+{"text": "Describe the implementation of account.payment.register.payment.difference.line.", "response": "The account.payment.register.payment.difference.line model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.payment.register.payment.difference.line", "table_name": ""}
+{"text": "What is the account.petty.cash.report model?", "response": "The account.petty.cash.report model represents Account Petty Cash Report in the ERP system. It contains 16 fields and is used to manage account petty cash report data. Key fields include: name, custodian_id, main_cash_account_id, journal_id, amount, balance, virtual_balance, company_id, branch_id, effective_date, create_uid, create_date, expense_amount, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.petty.cash.report", "table_name": ""}
+{"text": "What business logic is in purchase.bill.union?", "response": "To use the purchase.bill.union model, you need to provide values for required fields: none. Readonly fields: name, reference, partner_id, date, amount, currency_id, company_id, vendor_bill_id, purchase_order_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.bill.union", "table_name": ""}
+{"text": "What does the ir.model.constraint model represent?", "response": "The ir.model.constraint model represents Model Constraint in the ERP system. It contains 13 fields and is used to manage model constraint data. Key fields include: name, definition, message, model, module, type, write_date, create_date, id, display_name, create_uid, write_uid, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.model.constraint", "table_name": ""}
+{"text": "What is the ir.module.module model?", "response": "The ir.module.module model represents Module in the ERP system. It contains 41 fields and is used to manage module data. Key fields include: name, category_id, shortdesc, summary, description, description_html, author, maintainer, contributors, website, installed_version, latest_version, published_version, url, sequence, dependencies_id, exclusion_ids, auto_install, state, demo, license, menus_by_module, reports_by_module, views_by_module, application, icon, icon_image, to_buy, has_iap, version_status, imported, local_updatable, image_ids, is_installed_on_current_website, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.module.module", "table_name": ""}
+{"text": "What data can be stored in sh.sale.report.salesperson.wizard?", "response": "The sh.sale.report.salesperson.wizard model has 15 fields: date_start, date_end, user_ids, state, company_ids, company_id, user_order_dic, currency_precision, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2many: 2, selection: 1, many2one: 3, one2many: 1, integer: 2, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.sale.report.salesperson.wizard", "table_name": ""}
+{"text": "Describe the ir.attachment model in Odoo.", "response": "The ir.attachment model represents Ir attachment in the ERP system. It contains 42 fields and is used to manage ir attachment data. Key fields include: name, description, res_name, res_model, res_field, res_id, company_id, type, url, public, access_token, raw, datas, db_datas, store_fname, file_size, checksum, mimetype, index_content, local_url, image_src, image_width, image_height, original_id, website_url, website_id, key, theme_template_id, delete_old, datas_pdf, sh_is_notify, partner, email, sh_is_publish_in_portal, expiry_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.attachment", "table_name": ""}
+{"text": "Describe the pos.epson model in Odoo.", "response": "The pos.epson model represents Epson Printer, print without posbox in the ERP system. It contains 9 fields and is used to manage epson printer, print without posbox data. Key fields include: name, ip, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.epson", "table_name": ""}
+{"text": "How to create records in barcode.product.lines?", "response": "To use the barcode.product.lines model, you need to provide values for required fields: product_id, qty. Readonly fields: is_multi_barcode, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "barcode.product.lines", "table_name": ""}
+{"text": "What methods are available in replenish.wizard?", "response": "The replenish.wizard model is defined in module: equip3_accounting_pettycash. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "replenish.wizard", "table_name": ""}
+{"text": "What does the report.equip3_pos_report.report_sales_summary model represent?", "response": "The report.equip3_pos_report.report_sales_summary model represents POS Sale Summary Report in the ERP system. It contains 3 fields and is used to manage pos sale summary report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_pos_report.report_sales_summary", "table_name": ""}
+{"text": "Describe the implementation of invoice.recurring.", "response": "The invoice.recurring model is defined in module: sh_invoice_recurring. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.recurring", "table_name": ""}
+{"text": "What foreign keys exist in pos.loyalty?", "response": "The pos.loyalty model has 10 relational fields: rule_ids -> pos.loyalty.rule; reward_ids -> pos.loyalty.reward; product_redeem_ids -> pos.loyalty.reward; reward_redeem_ids -> pos.loyalty.reward; product_loyalty_id -> product.product; config_ids -> pos.config; pos_config_ids -> pos.config; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_config_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.loyalty", "table_name": ""}
+{"text": "Show me the relational structure of report.equip3_pos_report.report_open_session.", "response": "The report.equip3_pos_report.report_open_session model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_pos_report.report_open_session", "table_name": ""}
+{"text": "Describe the implementation of payable.opening.balance.", "response": "The payable.opening.balance model is defined in module: equip3_accounting_opening_balance. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "payable.opening.balance", "table_name": ""}
+{"text": "What data can be stored in expiring.product.calendar?", "response": "The expiring.product.calendar model has 8 fields: data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "expiring.product.calendar", "table_name": ""}
+{"text": "Which fields in nsfp.registration.wizard are computed?", "response": "The nsfp.registration.wizard model is defined in module: equip3_accounting_efaktur. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "nsfp.registration.wizard", "table_name": ""}
+{"text": "What modules define whatsapp.message.wizard?", "response": "The whatsapp.message.wizard model is defined in module: ss_whatsapp_connector. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "whatsapp.message.wizard", "table_name": ""}
+{"text": "What are the available fields for ir.model.access?", "response": "The ir.model.access model has 15 fields: name, active, model_id, group_id, perm_read, perm_write, perm_create, perm_unlink, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 5, many2one: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.model.access", "table_name": ""}
+{"text": "What models are connected to account.analytic.group?", "response": "The account.analytic.group model has 17 relational fields: children_ids -> account.analytic.group; parent_id -> account.analytic.group; company_id -> res.company; analytic_account_ids -> account.analytic.account; analyticnew_ids -> account.analytic.new; branch_id -> res.branch; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.analytic.group", "table_name": ""}
+{"text": "Describe the implementation of material.request.line.", "response": "The material.request.line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "material.request.line", "table_name": ""}
+{"text": "What business logic is in base.geo_provider?", "response": "To use the base.geo_provider model, you need to provide values for required fields: none. Readonly fields: tech_name, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.geo_provider", "table_name": ""}
+{"text": "What business logic is in portal.wizard.user?", "response": "To use the portal.wizard.user model, you need to provide values for required fields: wizard_id, partner_id. Readonly fields: partner_id, is_customer, is_vendor, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "portal.wizard.user", "table_name": ""}
+{"text": "How to create records in stock.lot.serialize?", "response": "To use the stock.lot.serialize 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.lot.serialize", "table_name": ""}
+{"text": "Can you explain the purpose of batch.shipping.line?", "response": "The batch.shipping.line model represents Batch Shipping Line in the ERP system. It contains 12 fields and is used to manage batch shipping line data. Key fields include: serial_number, picking_id, warehouse_id, batch_shipping_id, used_picking_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "batch.shipping.line", "table_name": ""}
+{"text": "Show me the relational structure of report.equip3_assembly_reports.report_assembly_production.", "response": "The report.equip3_assembly_reports.report_assembly_production model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.equip3_assembly_reports.report_assembly_production", "table_name": ""}
+{"text": "Describe the pos.product.bom model in Odoo.", "response": "The pos.product.bom model represents POS Product Bom in the ERP system. It contains 16 fields and is used to manage pos product bom data. Key fields include: product_id, name, product_tmpl_id, product_qty, product_uom_id, product_bom_line_ids, state, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.product.bom", "table_name": ""}
+{"text": "What are the technical details of product.template.attribute.exclusion?", "response": "The product.template.attribute.exclusion model is defined in module: product. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.template.attribute.exclusion", "table_name": ""}
+{"text": "How is report.accounting_pdf_reports.report_tax used in the system?", "response": "The report.accounting_pdf_reports.report_tax model represents Tax Report in the ERP system. It contains 3 fields and is used to manage tax report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.accounting_pdf_reports.report_tax", "table_name": ""}
+{"text": "How is calendar.attendee implemented technically?", "response": "The calendar.attendee model is defined in module: calendar. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "calendar.attendee", "table_name": ""}
+{"text": "What methods are available in credit.limit.product.brand?", "response": "The credit.limit.product.brand model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "credit.limit.product.brand", "table_name": ""}
+{"text": "What is the ir.logging model?", "response": "The ir.logging model represents Logging in the ERP system. It contains 15 fields and is used to manage logging data. Key fields include: create_uid, create_date, write_uid, write_date, name, type, dbname, level, message, path, func, line, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.logging", "table_name": ""}
+{"text": "What are the technical details of sh.purchase.analysis.xls?", "response": "The sh.purchase.analysis.xls model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.analysis.xls", "table_name": ""}
+{"text": "Tell me about the report.equip3_accounting_reports.financial_ratio_report model.", "response": "The report.equip3_accounting_reports.financial_ratio_report model represents report.equip3_accounting_reports.financial_ratio_report in the ERP system. It contains 3 fields and is used to manage report.equip3_accounting_reports.financial_ratio_report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_accounting_reports.financial_ratio_report", "table_name": ""}
+{"text": "What foreign keys exist in portal.wizard?", "response": "The portal.wizard model has 3 relational fields: user_ids -> portal.wizard.user; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "portal.wizard", "table_name": ""}
+{"text": "List all fields in the service.work.order model.", "response": "The service.work.order model has 26 fields: name, partner_id, account_analytic_tag_ids, date_planned, deadline_date, origin, company_id, branch_id, order_line, state, purchase_order_id, checklist_ids, purchase_line_milestone_id, milestone_name, contract_term, progress_paid, move_id, invoiced, account_move_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, many2one: 8, many2many: 1, datetime: 5, one2many: 2, selection: 1, float: 2, boolean: 1, integer: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "service.work.order", "table_name": ""}
+{"text": "What does the replenish.wizard model represent?", "response": "The replenish.wizard model represents Replenish Petty Cash Fund in the ERP system. It contains 11 fields and is used to manage replenish petty cash fund data. Key fields include: fund_id, effective_date, replenish_account_id, replenish_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "replenish.wizard", "table_name": ""}
+{"text": "What are the available fields for account.common.account.report?", "response": "The account.common.account.report model has 14 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 types distribution: selection: 2, many2many: 1, date: 2, many2one: 4, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.common.account.report", "table_name": ""}
+{"text": "What are common use cases for base_import.tests.models.complex?", "response": "To use the base_import.tests.models.complex model, you need to provide values for required fields: none. Readonly fields: f, m, c, currency_id, d, dt, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base_import.tests.models.complex", "table_name": ""}
+{"text": "How to create records in setu.inventory.fsn.analysis.bi.report?", "response": "To use the setu.inventory.fsn.analysis.bi.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.inventory.fsn.analysis.bi.report", "table_name": ""}
+{"text": "How to query account.financial.report data?", "response": "To use the account.financial.report model, you need to provide values for required fields: name, sign. Readonly fields: level, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.financial.report", "table_name": ""}
+{"text": "What operations can I perform on all.redeem.rule?", "response": "To use the all.redeem.rule 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "all.redeem.rule", "table_name": ""}
+{"text": "How does mail.resend.cancel relate to other models?", "response": "The mail.resend.cancel model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.resend.cancel", "table_name": ""}
+{"text": "What are the available fields for pos.product.attribute?", "response": "The pos.product.attribute model has 9 fields: sequence, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.product.attribute", "table_name": ""}
+{"text": "Tell me about the analytic.sale.order.line model.", "response": "The analytic.sale.order.line model represents Analytic Sale Order Lines in the ERP system. It contains 21 fields and is used to manage analytic sale order lines data. Key fields include: name, product_id, product_uom_qty, product_uom, price_unit, analytic_tag_ids, tax_ids, discount, subscription_product_line_id, not_subscription_product_line_id, price_subtotal, price_tax, price_total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "analytic.sale.order.line", "table_name": ""}
+{"text": "Show me the relational structure of account.fiscal.position.account.", "response": "The account.fiscal.position.account model has 6 relational fields: position_id -> account.fiscal.position; company_id -> res.company; account_src_id -> account.account; account_dest_id -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.fiscal.position.account", "table_name": ""}
+{"text": "What are the available fields for print.purchase.tender.report?", "response": "The print.purchase.tender.report model has 9 fields: selection, purchase_agreement_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, many2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "print.purchase.tender.report", "table_name": ""}
+{"text": "What foreign keys exist in report.sh_inventory_mrp_qc.quality_alert_doc?", "response": "The report.sh_inventory_mrp_qc.quality_alert_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_inventory_mrp_qc.quality_alert_doc", "table_name": ""}
+{"text": "Which fields in res.users.apikeys are computed?", "response": "The res.users.apikeys model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.apikeys", "table_name": ""}
+{"text": "Describe the many2many relations for vendor.evaluation.", "response": "The vendor.evaluation model has 19 relational fields: vendor -> res.partner; manager -> res.users; user_id -> res.users; evaluation_template_id -> vendor.evaluation.template; evaluation_eval_ids -> vendor.evaluation.template.eval; branch_id -> res.branch; company_id -> res.company; vendor_res -> res.partner; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "vendor.evaluation", "table_name": ""}
+{"text": "What operations can I perform on pos.qrcode?", "response": "To use the pos.qrcode model, you need to provide values for required fields: name, field_id, config_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.qrcode", "table_name": ""}
+{"text": "Can you explain the purpose of account.fiscal.position.tax?", "response": "The account.fiscal.position.tax model represents Tax Mapping of Fiscal Position in the ERP system. It contains 11 fields and is used to manage tax mapping of fiscal position data. Key fields include: position_id, company_id, tax_src_id, tax_dest_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.fiscal.position.tax", "table_name": ""}
+{"text": "What are the available fields for report.membership?", "response": "The report.membership model has 17 fields: start_date, date_to, num_waiting, num_invoiced, num_paid, tot_pending, tot_earned, partner_id, associate_member_id, membership_id, membership_state, user_id, company_id, quantity, id, display_name, __last_update. Field types distribution: date: 2, integer: 5, float: 2, many2one: 5, selection: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.membership", "table_name": ""}
+{"text": "Describe the field structure of stock.move.line.", "response": "The stock.move.line model has 64 fields: picking_id, move_id, company_id, product_id, product_uom_id, product_uom_category_id, product_qty, product_uom_qty, qty_done, package_id, package_level_id, lot_id, lot_name, date, owner_id, location_id, location_dest_id, lots_visible, picking_code, picking_type_use_create_lots, picking_type_use_existing_lots, state, is_initial_demand_editable, is_locked, consume_line_ids, produce_line_ids, reference, tracking, origin, picking_type_entire_packs, description_picking, workorder_id, production_id, expiration_date, scrap_return_move_id, is_double_product_usage, sale_price, sequence, move_line_sequence, product_type, quant_package_ids, result_package_id, is_quant_update, force_to_reserve_qty, source_picking_id, source_move_id, is_batch_shipping_packing, is_batch_shipping_delivery, assembly_id, scrap_sale_price, is_low_stock, description, kitchen_id, finish_good_rework_id, exp_date, remark, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 24, float: 6, char: 6, datetime: 6, boolean: 11, selection: 4, many2many: 3, text: 2, integer: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.move.line", "table_name": ""}
+{"text": "What models are connected to pos.coupon?", "response": "The pos.coupon model has 7 relational fields: product_ids -> product.product; coupon_program_id -> pos.coupon.program; company_id -> res.company; reward_product_ids -> product.product; use_history_ids -> pos.coupon.use.history; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids, reward_product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.coupon", "table_name": ""}
+{"text": "Show me the relational structure of stock.valuation.layer.", "response": "The stock.valuation.layer model has 19 relational fields: company_id -> res.company; product_id -> product.product; categ_id -> product.category; product_tmpl_id -> product.template; uom_id -> uom.uom; currency_id -> res.currency; stock_valuation_layer_id -> stock.valuation.layer; stock_valuation_layer_ids -> stock.valuation.layer; stock_move_id -> stock.move; account_move_id -> account.move; stock_landed_cost_id -> stock.landed.cost; secondary_uom -> uom.uom; warehouse_id -> stock.warehouse; location_id -> stock.location; new_warehouse_id -> stock.warehouse; new_location_id -> stock.location; new_inventory_id -> stock.inventory; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.valuation.layer", "table_name": ""}
+{"text": "How is rma.report used in the system?", "response": "The rma.report model represents RMA Statistics in the ERP system. It contains 22 fields and is used to manage rma statistics data. Key fields include: name, sale_id, picking_id, date, deadline_date, user_id, team_id, partner_id, company_id, state, product_id, product_tmpl_id, categ_id, delivered_qty, return_qty, replace_product_id, replace_qty, country_id, commercial_partner_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "rma.report", "table_name": ""}
+{"text": "What foreign keys exist in do.approval_matrix_line?", "response": "The do.approval_matrix_line model has 7 relational fields: approver -> res.users; last_approved -> res.users; do_approval_matrix_id1 -> do.approval.matrix; picking_id -> stock.picking; approved_users -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: approver, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "do.approval_matrix_line", "table_name": ""}
+{"text": "What operations can I perform on report.sh_sale_reports.sh_sale_details_report_doc?", "response": "To use the report.sh_sale_reports.sh_sale_details_report_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_sale_details_report_doc", "table_name": ""}
+{"text": "What foreign keys exist in portal.mixin?", "response": "The portal.mixin model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "portal.mixin", "table_name": ""}
+{"text": "How to create records in account.cash.flow.statement?", "response": "To use the account.cash.flow.statement model, you need to provide values for required fields: levels, comp_detail, type_report, journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.cash.flow.statement", "table_name": ""}
+{"text": "What models are connected to gamification.goal.definition?", "response": "The gamification.goal.definition model has 8 relational fields: model_id -> ir.model; model_inherited_ids -> ir.model; field_id -> ir.model.fields; field_date_id -> ir.model.fields; batch_distinctive_field -> ir.model.fields; action_id -> ir.actions.act_window; create_uid -> res.users; write_uid -> res.users. Many2many fields: model_inherited_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "gamification.goal.definition", "table_name": ""}
+{"text": "What methods are available in ir.fields.converter?", "response": "The ir.fields.converter model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.fields.converter", "table_name": ""}
+{"text": "How to query return.approval.matrix.line data?", "response": "To use the return.approval.matrix.line model, you need to provide values for required fields: approver. Readonly fields: sequence1, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "return.approval.matrix.line", "table_name": ""}
+{"text": "Show me the fields of ks.parameter.tuning.wizard.", "response": "The ks.parameter.tuning.wizard model has 21 fields: ks_forecast, ks_forecast_method, min_p, max_p, min_d, max_d, min_q, max_q, min_sp, max_sp, min_sd, max_sd, min_sq, max_sq, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, selection: 1, integer: 13, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ks.parameter.tuning.wizard", "table_name": ""}
+{"text": "What are the technical details of setu.rfm.score?", "response": "The setu.rfm.score model is defined in module: setu_rfm_analysis. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "setu.rfm.score", "table_name": ""}
+{"text": "Which fields in stock.immediate.transfer are computed?", "response": "The stock.immediate.transfer model is defined in module: stock. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.immediate.transfer", "table_name": ""}
+{"text": "How do I use the res.currency model?", "response": "To use the res.currency model, you need to provide values for required fields: name, symbol, company_id. Readonly fields: 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, display_rounding_warning, rate, conversion, decimal_places, date, tax_rate, tax_conversion, is_taxes_rate, converted_currency, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "res.currency", "table_name": ""}
+{"text": "Tell me about the assembly.safety.stock.line model.", "response": "The assembly.safety.stock.line model represents Assembly Safety Stock Management Line in the ERP system. It contains 10 fields and is used to manage assembly safety stock management line data. Key fields include: stock_id, product_id, product_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assembly.safety.stock.line", "table_name": ""}
+{"text": "What fields does purchase.agreement.line have?", "response": "The purchase.agreement.line model has 28 fields: agreement_id, sh_qty, sh_ordered_qty, sh_price_unit, company_id, schedule_date, sequence, sequence2, analytic_accounting, sh_product_description, sh_product_uom_id, product_uom_category_id, analytic_tag_ids, date_order, dest_warehouse_id, picking_type_id, set_single_delivery_date, set_single_delivery_destination, request_line_id, branch_id, sh_product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 11, float: 3, date: 2, integer: 3, boolean: 3, text: 1, many2many: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.agreement.line", "table_name": ""}
+{"text": "Describe the many2many relations for account.keterangan.tambahan.", "response": "The account.keterangan.tambahan model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.keterangan.tambahan", "table_name": ""}
+{"text": "What are the technical details of list.top.product?", "response": "The list.top.product model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "list.top.product", "table_name": ""}
+{"text": "What modules define pos.payment?", "response": "The pos.payment model is defined in module: point_of_sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.payment", "table_name": ""}
+{"text": "What modules define invoice.template.footer?", "response": "The invoice.template.footer model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "invoice.template.footer", "table_name": ""}
+{"text": "How does pos.details.wizard relate to other models?", "response": "The pos.details.wizard model has 3 relational fields: pos_config_ids -> pos.config; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_config_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.details.wizard", "table_name": ""}
+{"text": "What methods are available in ir.http?", "response": "The ir.http model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.http", "table_name": ""}
+{"text": "What modules define queue.job?", "response": "The queue.job model is defined in module: queue_job. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "queue.job", "table_name": ""}
+{"text": "What fields does stock.location.tag have?", "response": "The stock.location.tag model has 10 fields: name, color, opacity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 3, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.location.tag", "table_name": ""}
+{"text": "List all fields in the snailmail.confirm.invoice model.", "response": "The snailmail.confirm.invoice model has 9 fields: invoice_send_id, model_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "snailmail.confirm.invoice", "table_name": ""}
+{"text": "What business logic is in project.task.create.sale.order?", "response": "To use the project.task.create.sale.order model, you need to provide values for required fields: link_selection, task_id, partner_id, product_id. Readonly fields: commercial_partner_id, info_invoice, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.task.create.sale.order", "table_name": ""}
+{"text": "What does the account.bank.statement model represent?", "response": "The account.bank.statement model represents Bank Statement in the ERP system. It contains 56 fields and is used to manage bank statement data. Key fields include: name, reference, date, date_done, balance_start, balance_end_real, state, currency_id, journal_id, journal_type, company_id, total_entry_encoding, balance_end, difference, line_ids, move_line_ids, move_line_count, all_lines_reconciled, user_id, cashbox_start_id, cashbox_end_id, is_difference_zero, previous_statement_id, is_valid_balance_start, country_code, accounting_date, pos_session_id, account_id, branch_id, pos_branch_id, transaction, journal_entries_status, 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, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.bank.statement", "table_name": ""}
+{"text": "Can you explain the purpose of res.partner.category?", "response": "The res.partner.category model represents Partner Tags in the ERP system. It contains 14 fields and is used to manage partner tags data. Key fields include: name, color, parent_id, child_ids, active, parent_path, partner_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.partner.category", "table_name": ""}
+{"text": "What data can be stored in sh.base.send.whatsapp.message.wizard?", "response": "The sh.base.send.whatsapp.message.wizard model has 11 fields: partner_ids, message, attachment_ids, purchase_order_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, text: 1, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.base.send.whatsapp.message.wizard", "table_name": ""}
+{"text": "What business logic is in web.environment.ribbon.backend?", "response": "To use the web.environment.ribbon.backend model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "web.environment.ribbon.backend", "table_name": ""}
+{"text": "How is crm.merge.opportunity used in the system?", "response": "The crm.merge.opportunity model represents Merge Opportunities in the ERP system. It contains 10 fields and is used to manage merge opportunities data. Key fields include: opportunity_ids, user_id, team_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.merge.opportunity", "table_name": ""}
+{"text": "What models are connected to stock.lot.serialize.line?", "response": "The stock.lot.serialize.line model has 5 relational fields: stock_move_id -> stock.lot.serialize; move_id -> stock.move; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.lot.serialize.line", "table_name": ""}
+{"text": "Can you explain the purpose of hr.plan?", "response": "The hr.plan model represents plan in the ERP system. It contains 10 fields and is used to manage plan data. Key fields include: name, plan_activity_type_ids, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "hr.plan", "table_name": ""}
+{"text": "What operations can I perform on mr.approval.matrix.line?", "response": "To use the mr.approval.matrix.line model, you need to provide values for required fields: user_ids, minimum_approver. Readonly fields: sequence2, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mr.approval.matrix.line", "table_name": ""}
+{"text": "What data can be stored in stock.picking.batch.line?", "response": "The stock.picking.batch.line model has 18 fields: sequence, transfer_id, product_id, name, location_id, demand_qty, reserved_qty, done_qty, uom_id, picking_batch_id, origin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 7, char: 3, float: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.picking.batch.line", "table_name": ""}
+{"text": "Describe the res.users.log model in Odoo.", "response": "The res.users.log model represents Users Log in the ERP system. It contains 7 fields and is used to manage users log data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.users.log", "table_name": ""}
+{"text": "Describe the account.setup.bank.manual.config model in Odoo.", "response": "The account.setup.bank.manual.config model represents Bank setup manual config in the ERP system. It contains 30 fields and is used to manage bank setup manual config data. Key fields include: res_partner_bank_id, new_journal_name, linked_journal_id, bank_bic, num_journals_without_account, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, active, acc_type, acc_number, sanitized_acc_number, acc_holder_name, partner_id, bank_id, bank_name, sequence, currency_id, company_id, journal_id, aba_routing, acc_holder_email, acc_holder_type, acc_holder_resident, acc_holder_address.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.setup.bank.manual.config", "table_name": ""}
+{"text": "What business logic is in stock.backorder.confirmation.line?", "response": "To use the stock.backorder.confirmation.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.backorder.confirmation.line", "table_name": ""}
+{"text": "What does the phone.blacklist model represent?", "response": "The phone.blacklist model represents Phone Blacklist in the ERP system. It contains 24 fields and is used to manage phone blacklist data. Key fields include: number, active, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "phone.blacklist", "table_name": ""}
+{"text": "What methods are available in report.project.task.user?", "response": "The report.project.task.user model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.project.task.user", "table_name": ""}
+{"text": "How does purchase.request.wizard relate to other models?", "response": "The purchase.request.wizard model has 3 relational fields: pr_wizard_line -> purchase.request.wizard.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.request.wizard", "table_name": ""}
+{"text": "How to query opening.balance.line data?", "response": "To use the opening.balance.line model, you need to provide values for required fields: none. Readonly fields: company_id, company_currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "opening.balance.line", "table_name": ""}
+{"text": "How does crm.phonecall2phonecall relate to other models?", "response": "The crm.phonecall2phonecall model has 6 relational fields: user_id -> res.users; tag_ids -> crm.tag; team_id -> crm.team; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.phonecall2phonecall", "table_name": ""}
+{"text": "Which fields in purchase.agreement.approval.matrix.lines are computed?", "response": "The purchase.agreement.approval.matrix.lines model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.agreement.approval.matrix.lines", "table_name": ""}
+{"text": "List all fields in the sh.top.selling.products model.", "response": "The sh.top.selling.products model has 9 fields: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.top.selling.products", "table_name": ""}
+{"text": "List all fields in the report.sh_inventory_mrp_qc.quality_check_doc model.", "response": "The report.sh_inventory_mrp_qc.quality_check_doc model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.sh_inventory_mrp_qc.quality_check_doc", "table_name": ""}
+{"text": "How do I use the internal.transfer model?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "internal.transfer", "table_name": ""}
+{"text": "What business logic is in order.picking?", "response": "To use the order.picking 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "order.picking", "table_name": ""}
+{"text": "List all fields in the acrux.chat.message.wizard model.", "response": "The acrux.chat.message.wizard model has 20 fields: text, partner_id, conversation_id, connector_id, sale_id, message_mass_id, phone, is_crm, opportunity_id, whatsapp_template_id, crm_message_mass_id, mobile, attachment_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, many2one: 10, char: 3, boolean: 1, many2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "acrux.chat.message.wizard", "table_name": ""}
+{"text": "What are the available fields for vendor.payment.request?", "response": "The vendor.payment.request model has 16 fields: name, user_id, description, company_id, branch_id, component_line_id, state, amount_total, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 6, one2many: 1, selection: 1, float: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "vendor.payment.request", "table_name": ""}
+{"text": "What modules define rma.report?", "response": "The rma.report model is defined in module: dev_rma. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "rma.report", "table_name": ""}
+{"text": "How does inter.transfer.company.line relate to other models?", "response": "The inter.transfer.company.line model has 4 relational fields: internal_id -> inter.transfer.company; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "inter.transfer.company.line", "table_name": ""}
+{"text": "What models are connected to phone.blacklist.remove?", "response": "The phone.blacklist.remove model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "phone.blacklist.remove", "table_name": ""}
+{"text": "Describe the field structure of report_excel_import_wizard.", "response": "The report_excel_import_wizard model has 8 fields: data, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report_excel_import_wizard", "table_name": ""}
+{"text": "What business logic is in replenishment.history.wizard?", "response": "To use the replenishment.history.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "replenishment.history.wizard", "table_name": ""}
+{"text": "List all fields in the stock.return.picking.inter.company model.", "response": "The stock.return.picking.inter.company model has 12 fields: product_id, quantity, uom_id, wizard_id, move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.return.picking.inter.company", "table_name": ""}
+{"text": "Can you explain the purpose of hide.chatter?", "response": "The hide.chatter model represents Chatter Rights in the ERP system. It contains 13 fields and is used to manage chatter rights data. Key fields include: access_management_id, model_id, hide_chatter, hide_send_mail, hide_log_notes, hide_schedule_activity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "hide.chatter", "table_name": ""}
+{"text": "Show me the relational structure of mrp.bom.", "response": "The mrp.bom model has 22 relational fields: bom_line_ids -> mrp.bom.line; byproduct_ids -> mrp.bom.byproduct; product_uom_category_id -> uom.category; operation_ids -> mrp.routing.workcenter; picking_type_id -> stock.picking.type; product_id -> product.product; company_id -> res.company; product_uom_id -> uom.uom; branch_id -> res.branch; create_uid -> res.users; tool_ids -> mrp.bom.tools; operation_two_ids -> mrp.bom.operation; product_tmpl_id -> product.template; product_tmpl_ids -> product.template; product_ids -> product.product; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; write_uid -> res.users. Many2many fields: operation_two_ids, product_tmpl_ids, product_ids, message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mrp.bom", "table_name": ""}
+{"text": "List all fields in the calendar.event model.", "response": "The calendar.event model has 99 fields: name, attendee_status, display_time, start, stop, allday, start_date, stop_date, duration, description, privacy, location, show_as, res_id, res_model_id, res_model, activity_ids, message_ids, user_id, partner_id, active, categ_ids, attendee_ids, partner_ids, alarm_ids, is_highlighted, recurrency, recurrence_id, follow_recurrence, recurrence_update, rrule, rrule_type, event_tz, end_type, interval, count, mo, tu, we, th, fr, sa, su, month_by, day, weekday, byday, until, opportunity_id, phonecall_id, sign_in_location, sign_out_location, sign_in_date, sign_out_date, sign_in, sign_out, note_field, team_id, state, state_1, state_2, cancel_reason, opportunity_name, res_name, res_loc, meeting_salesperson_ids, is_hide_salesperson, dummy_boolean, user_ids, mandatory, partner_attendees_ids, reasons_reschedule, cancelled_reasons, meeting_overview, stage_id, meeting_count, quotation, final_quotation, message_is_follower, message_follower_ids, 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_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 13, selection: 14, datetime: 7, boolean: 22, date: 3, float: 1, text: 2, integer: 11, many2one: 12, one2many: 5, many2many: 8, html: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "calendar.event", "table_name": ""}
+{"text": "How to query hr.plan.activity.type data?", "response": "To use the hr.plan.activity.type model, you need to provide values for required fields: responsible. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "hr.plan.activity.type", "table_name": ""}
+{"text": "What methods are available in account.pettycash.fund.change?", "response": "The account.pettycash.fund.change model is defined in module: equip3_accounting_pettycash. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.pettycash.fund.change", "table_name": ""}
+{"text": "Show me the relational structure of queue.job.channel.", "response": "The queue.job.channel model has 4 relational fields: parent_id -> queue.job.channel; job_function_ids -> queue.job.function; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "queue.job.channel", "table_name": ""}
+{"text": "What fields does account.internal.transfer have?", "response": "The account.internal.transfer model has 68 fields: request_partner_id, bank_from_journal_id, bank_to_journal_id, transfer_in_transit, account_in_transit, transfer_desc, transfer_amount, currency_id, transfer_date, create_date, create_uid, company_id, branch_id, state, filter_branch_ids, administration, administration_account, administration_fee, has_reconciled_entries, approval_matrix_id, is_internal_approval_matrix, approved_matrix_ids, approval_matrix_line_id, is_approve_button, state1, state2, analytic_group_ids, apply_manual_currency_exchange, manual_currency_exchange_rate, manual_currency_exchange_inverse_rate, type_curr, name, 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, write_uid, write_date, __last_update. Field types distribution: many2one: 18, boolean: 11, text: 2, monetary: 2, date: 3, datetime: 3, selection: 6, many2many: 4, one2many: 5, float: 2, char: 7, integer: 5.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.internal.transfer", "table_name": ""}
+{"text": "Show me the relational structure of salesperson.tracking.history.", "response": "The salesperson.tracking.history model has 3 relational fields: tracking_history_id -> crm.sales.tracking.history; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "salesperson.tracking.history", "table_name": ""}
+{"text": "Describe the implementation of report.excel.section.", "response": "The report.excel.section model is defined in module: report_excel. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.excel.section", "table_name": ""}
+{"text": "Tell me about the global.search model.", "response": "The global.search model represents Global Search in the ERP system. It contains 11 fields and is used to manage global search data. Key fields include: model_id, field_ids, main_field_id, global_field_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "global.search", "table_name": ""}
+{"text": "How is vendor.evaluation implemented technically?", "response": "The vendor.evaluation model is defined in module: vendor_evaluation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "vendor.evaluation", "table_name": ""}
+{"text": "What operations can I perform on resource.resource?", "response": "To use the resource.resource model, you need to provide values for required fields: name, resource_type, time_efficiency, calendar_id, tz. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "resource.resource", "table_name": ""}
+{"text": "Describe the field structure of partner.blacklist.history.", "response": "The partner.blacklist.history model has 12 fields: user_id, type, reason, date, partner_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, selection: 1, char: 2, date: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "partner.blacklist.history", "table_name": ""}
+{"text": "How is receipt.voucher.line implemented technically?", "response": "The receipt.voucher.line model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "receipt.voucher.line", "table_name": ""}
+{"text": "What are the available fields for res.currency.rate?", "response": "The res.currency.rate model has 13 fields: name, currency_id, company_id, rate, conversion, mr_rate, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 1, many2one: 4, float: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.currency.rate", "table_name": ""}
+{"text": "What does the approval.matrix.sale.reject model represent?", "response": "The approval.matrix.sale.reject model represents approval.matrix.sale.reject in the ERP system. It contains 8 fields and is used to manage approval.matrix.sale.reject data. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.sale.reject", "table_name": ""}
+{"text": "What are the technical details of base.module.update?", "response": "The base.module.update model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base.module.update", "table_name": ""}
+{"text": "How to create records in ir.model.fields.selection?", "response": "To use the ir.model.fields.selection model, you need to provide values for required fields: field_id, value, name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.model.fields.selection", "table_name": ""}
+{"text": "How is purchase.request.allocation implemented technically?", "response": "The purchase.request.allocation model is defined in module: purchase_request. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.request.allocation", "table_name": ""}
+{"text": "How is account.cash.flow.statement used in the system?", "response": "The account.cash.flow.statement model represents account.cash.flow.statement in the ERP system. It contains 21 fields and is used to manage account.cash.flow.statement data. Key fields include: date_from, date_to, today, levels, account_ids, company_ids, comparison, previous, comp_detail, type_report, journal_ids, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.cash.flow.statement", "table_name": ""}
+{"text": "What modules define tax.report?", "response": "The tax.report model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "tax.report", "table_name": ""}
+{"text": "What are the relationships in invoice.template.footer?", "response": "The invoice.template.footer model has 4 relational fields: template_id -> invoice.templates; field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "invoice.template.footer", "table_name": ""}
+{"text": "What models are connected to acrux.chat.message.wizard?", "response": "The acrux.chat.message.wizard model has 11 relational fields: partner_id -> res.partner; conversation_id -> acrux.chat.conversation; connector_id -> acrux.chat.connector; sale_id -> sale.order; message_mass_id -> send.message.mass; opportunity_id -> crm.lead; whatsapp_template_id -> whatsapp.template; crm_message_mass_id -> crm.send.message.mass; attachment_ids -> ir.attachment; create_uid -> res.users; write_uid -> res.users. Many2many fields: attachment_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "acrux.chat.message.wizard", "table_name": ""}
+{"text": "How do I use the pos.generate.efaktur.invoice model?", "response": "To use the pos.generate.efaktur.invoice model, you need to provide values for required fields: none. Readonly fields: l10n_id_tax_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.generate.efaktur.invoice", "table_name": ""}
+{"text": "What fields does stock.inventory.wizard have?", "response": "The stock.inventory.wizard model has 8 fields: wizard_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.inventory.wizard", "table_name": ""}
+{"text": "Show me the relational structure of account.loan.generate.wizard.", "response": "The account.loan.generate.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.loan.generate.wizard", "table_name": ""}
+{"text": "How to query remove.pos.order data?", "response": "To use the remove.pos.order 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "remove.pos.order", "table_name": ""}
+{"text": "What models are connected to ks_dashboard_ninja.board_custom_filters?", "response": "The ks_dashboard_ninja.board_custom_filters model has 5 relational fields: ks_dashboard_board_id -> ks_dashboard_ninja.board; ks_model_id -> ir.model; ks_domain_field_id -> ir.model.fields; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ks_dashboard_ninja.board_custom_filters", "table_name": ""}
+{"text": "How does sale.margin.report.wizard relate to other models?", "response": "The sale.margin.report.wizard model has 5 relational fields: partner_ids -> res.partner; company_ids -> res.company; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: partner_ids, company_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.margin.report.wizard", "table_name": ""}
+{"text": "What business logic is in base.geocoder?", "response": "To use the base.geocoder model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base.geocoder", "table_name": ""}
+{"text": "How is account.unreconcile implemented technically?", "response": "The account.unreconcile model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.unreconcile", "table_name": ""}
+{"text": "What are the available fields for ir.qweb.field.integer?", "response": "The ir.qweb.field.integer model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.integer", "table_name": ""}
+{"text": "What methods are available in ir.actions.server?", "response": "The ir.actions.server model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.actions.server", "table_name": ""}
+{"text": "Describe the many2many relations for mail.shortcode.", "response": "The mail.shortcode model has 3 relational fields: message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "mail.shortcode", "table_name": ""}
+{"text": "How does base_import.tests.models.o2m relate to other models?", "response": "The base_import.tests.models.o2m model has 3 relational fields: value -> base_import.tests.models.o2m.child; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "base_import.tests.models.o2m", "table_name": ""}
+{"text": "Tell me about the order.picking model.", "response": "The order.picking model represents Order Picking in the ERP system. It contains 9 fields and is used to manage order picking data. Key fields include: move_id, order_picking_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "order.picking", "table_name": ""}
+{"text": "Tell me about the pos.sync.session.order model.", "response": "The pos.sync.session.order model represents Pos Sync Session Order in the ERP system. It contains 17 fields and is used to manage pos sync session order data. Key fields include: uid, data, name, database, state, line_ids, pos_config_id, pos_session_id, branch_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.sync.session.order", "table_name": ""}
+{"text": "What business logic is in crm.lead.scoring.frequency?", "response": "To use the crm.lead.scoring.frequency model, you need to provide values for required fields: none. Readonly fields: variable, value, won_count, lost_count, team_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.lead.scoring.frequency", "table_name": ""}
+{"text": "What business logic is in mrp.production.backorder?", "response": "To use the mrp.production.backorder model, you need to provide values for required fields: none. Readonly fields: show_backorder_lines, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mrp.production.backorder", "table_name": ""}
+{"text": "How is mrp.bom.line implemented technically?", "response": "The mrp.bom.line model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.bom.line", "table_name": ""}
+{"text": "What modules define res.users.qiscuss?", "response": "The res.users.qiscuss model is defined in module: equip3_crm_whatsapp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.qiscuss", "table_name": ""}
+{"text": "Describe the implementation of target.activity.line.", "response": "The target.activity.line model is defined in module: equip3_crm_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "target.activity.line", "table_name": ""}
+{"text": "How to create records in receipt.voucher?", "response": "To use the receipt.voucher model, you need to provide values for required fields: name, partner_ids, voucher_date, bank_id, customer_invoice_ids, currency_id, company_id, branch_id. Readonly fields: payment_count, name, state, amount, customer_allowed_ids, is_cutoff_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, id, display_name, create_uid, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "receipt.voucher", "table_name": ""}
+{"text": "Can you explain the purpose of extract.rfq.wizard?", "response": "The extract.rfq.wizard model represents Extract Rfq Wizard in the ERP system. It contains 8 fields and is used to manage extract rfq wizard data. Key fields include: purchase_order_extract_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "extract.rfq.wizard", "table_name": ""}
+{"text": "What are common use cases for account.efaktur?", "response": "To use the account.efaktur model, you need to provide values for required fields: company_id. Readonly fields: partner_id, company_id, branch_id, is_used, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.efaktur", "table_name": ""}
+{"text": "Describe the barcode.labels model in Odoo.", "response": "The barcode.labels model represents Barcode Labels in the ERP system. It contains 8 fields and is used to manage barcode labels data. Key fields include: product_get_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "barcode.labels", "table_name": ""}
+{"text": "What modules define res.country.group?", "response": "The res.country.group model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.country.group", "table_name": ""}
+{"text": "How do I use the report.equip3_pos_report.report_top_selling model?", "response": "To use the report.equip3_pos_report.report_top_selling model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_pos_report.report_top_selling", "table_name": ""}
+{"text": "Show me the fields of pos.zone.", "response": "The pos.zone model has 9 fields: name, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.zone", "table_name": ""}
+{"text": "What methods are available in ir.model.constraint?", "response": "The ir.model.constraint model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.model.constraint", "table_name": ""}
+{"text": "List all fields in the ir.module.module.exclusion model.", "response": "The ir.module.module.exclusion model has 11 fields: name, module_id, exclusion_id, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 4, selection: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.module.module.exclusion", "table_name": ""}
+{"text": "What modules define asset.asset.revalue?", "response": "The asset.asset.revalue model is defined in module: equip3_accounting_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "asset.asset.revalue", "table_name": ""}
+{"text": "What is the product.template.create.variant.line model?", "response": "The product.template.create.variant.line model represents Product Template Create Variant in the ERP system. It contains 11 fields and is used to manage product template create variant data. Key fields include: variant_id, attribute_id, value_ids, filter_value_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.template.create.variant.line", "table_name": ""}
+{"text": "What are the available fields for mass.editing.line?", "response": "The mass.editing.line model has 13 fields: sequence, server_action_id, model_id, field_id, widget_option, apply_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 5, char: 2, boolean: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mass.editing.line", "table_name": ""}
+{"text": "What foreign keys exist in account.invoice.to.draft?", "response": "The account.invoice.to.draft model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.invoice.to.draft", "table_name": ""}
+{"text": "Describe the implementation of report.sh_po_tender_management.report_analyze_quotations.", "response": "The report.sh_po_tender_management.report_analyze_quotations model is defined in module: sh_po_tender_management. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_po_tender_management.report_analyze_quotations", "table_name": ""}
+{"text": "Which fields in product.warehouse.price are computed?", "response": "The product.warehouse.price model is defined in module: allfresh_mod_costperwh. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.warehouse.price", "table_name": ""}
+{"text": "What foreign keys exist in sh.model.fields.purchase.order.selection?", "response": "The sh.model.fields.purchase.order.selection model has 3 relational fields: sh_field_po_id -> sh.custom.model.purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.model.fields.purchase.order.selection", "table_name": ""}
+{"text": "How is sh.custom.field.model implemented technically?", "response": "The sh.custom.field.model model is defined in module: sh_global_custom_fields. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.custom.field.model", "table_name": ""}
+{"text": "Describe the purchase.product.template.line model in Odoo.", "response": "The purchase.product.template.line model represents Purchase Product Template Line in the ERP system. It contains 14 fields and is used to manage purchase product template line data. Key fields include: name, description, ordered_qty, unit_price, product_uom, purchase_template_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.product.template.line", "table_name": ""}
+{"text": "How is base_import.tests.models.char implemented technically?", "response": "The base_import.tests.models.char model is defined in module: base_import. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "base_import.tests.models.char", "table_name": ""}
+{"text": "What are the technical details of nsfp.registration?", "response": "The nsfp.registration model is defined in module: equip3_accounting_efaktur. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "nsfp.registration", "table_name": ""}
+{"text": "What are the available fields for setu.inventory.turnover.analysis.report?", "response": "The setu.inventory.turnover.analysis.report model has 15 fields: stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, date: 2, many2many: 4, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.turnover.analysis.report", "table_name": ""}
+{"text": "What is the pos.session model?", "response": "The pos.session model represents Point of Sale Session in the ERP system. It contains 101 fields and is used to manage point of sale session data. Key fields include: company_id, config_id, name, user_id, currency_id, start_at, stop_at, sequence_number, cash_control, cash_journal_id, cash_register_id, cash_register_balance_start, cash_register_balance_end, cash_register_difference, cash_real_difference, cash_real_transaction, cash_real_expected, order_ids, order_count, statement_ids, failed_pickings, picking_count, picking_ids, rescue, move_id, payment_method_ids, total_payments_amount, is_in_company_currency, update_stock_at_closing, move_id_old, orderline_checked, crm_team_id, required_reinstall_cache, backup_session, pos_branch_id, employee_id, lock_state, order_log_ids, opened_at, opened_uid, last_login_time, login_number, state, cash_opening_balance, cash_closing_balance, is_closing_wizard, pos_config_cashbox_lines_ids, pos_config_cashbox_clsosing_line_ids, cash_register_balance_end_real, cashier_id, total_invoice_count, total_faktur_count, log_cashier_ids, is_multi_session, order_with_receivable_invoice_ids, pos_config_uuid, pos_session_cashbox_wizard_ids, cash_management_ids, cash_history_ids, gain_loss_move_id, is_pos_config_save_order_history_local, scheduler_invoice_finish_date, void_ids, bank_register_total_entry_encoding, cash_register_total_entry_encoding, bank_closing_balance, pos_session_bank_cashbox_wizard_ids, to_recompute, is_invoice_recreate, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.session", "table_name": ""}
+{"text": "What are the available fields for z.report.wizard?", "response": "The z.report.wizard model has 11 fields: pos_session_ids, report_type, company_id, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 1, char: 2, many2one: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "z.report.wizard", "table_name": ""}
+{"text": "Can you explain the purpose of customer.category?", "response": "The customer.category model represents Customer Category in the ERP system. It contains 9 fields and is used to manage customer category data. Key fields include: name, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "customer.category", "table_name": ""}
+{"text": "List all fields in the report.pos.order model.", "response": "The report.pos.order model has 36 fields: date, order_id, partner_id, product_id, product_tmpl_id, state, user_id, price_total, price_sub_total, total_discount, average_price, company_id, nbr_lines, product_qty, journal_id, delay_validation, product_categ_id, invoiced, config_id, pos_categ_id, pricelist_id, session_id, employee_id, pos_branch_id, promotion_count, promotion_id, hour_group_id, zone_id, voucher_id, voucher_count, voucher_value, analytic_account_id, cashier_id, id, display_name, __last_update. Field types distribution: datetime: 2, many2one: 20, selection: 1, float: 5, integer: 6, boolean: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.pos.order", "table_name": ""}
+{"text": "What modules define ai.chat.job?", "response": "The ai.chat.job model is defined in module: ai_chat_agent. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ai.chat.job", "table_name": ""}
+{"text": "What are the available fields for update.customer.segment?", "response": "The update.customer.segment model has 10 fields: date_begin, date_end, note, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "update.customer.segment", "table_name": ""}
+{"text": "What modules define analytic.sale.order.line?", "response": "The analytic.sale.order.line model is defined in module: contract_recurring_invoice_analytic. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "analytic.sale.order.line", "table_name": ""}
+{"text": "What foreign keys exist in purchase.order.line?", "response": "The purchase.order.line model has 38 relational fields: taxes_id -> account.tax; product_uom -> uom.uom; product_uom_category_id -> uom.category; product_id -> product.product; order_id -> purchase.order; account_analytic_id -> account.analytic.account; company_id -> res.company; invoice_lines -> account.move.line; currency_id -> res.currency; product_template_attribute_value_ids -> product.template.attribute.value; product_no_variant_attribute_value_ids -> product.template.attribute.value; move_ids -> stock.move; orderpoint_id -> stock.warehouse.orderpoint; move_dest_ids -> stock.move; agreement_id -> purchase.agreement; picking_type_id -> stock.picking.type; purchase_request_lines -> purchase.request.line; purchase_request_allocation_ids -> purchase.request.allocation; sale_order_id -> sale.order; sale_line_id -> sale.order.line; branch_id -> res.branch; purchase_budget_lines -> budget.purchase; branch_ids -> res.branch; available_product_ids -> product.template; destination_location_id -> stock.location; destination_warehouse_id -> stock.warehouse; request_line_id -> purchase.request.line; partner_id -> res.partner; route_id -> stock.location.route; analytic_tag_ids -> account.analytic.tag; payment_term_id -> account.payment.term; product_template_id -> product.template; purchase_order_id -> purchase.order; requisition_line_id -> purchase.requisition.line; agreement_line_id -> purchase.agreement.line; merchendise_id -> merchendise.code; create_uid -> res.users; write_uid -> res.users. Many2many fields: taxes_id, product_template_attribute_value_ids, product_no_variant_attribute_value_ids, purchase_request_lines, branch_ids, available_product_ids, analytic_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.order.line", "table_name": ""}
+{"text": "How is purchase.order.split used in the system?", "response": "The purchase.order.split model represents purchase.order.split in the ERP system. It contains 19 fields and is used to manage purchase.order.split data. Key fields include: tick, sequence, product_template_id, name, date_planned, product_qty, price_unit, destination_warehouse_id, split_id, purchase_line_id, product_uom, product_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order.split", "table_name": ""}
+{"text": "What fields does generate.opening.entries have?", "response": "The generate.opening.entries model has 12 fields: name, old_fiscal_year_id, new_fiscal_year_id, journal_id, period_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 6, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "generate.opening.entries", "table_name": ""}
+{"text": "What are the available fields for sh.sale.analysis.wizard?", "response": "The sh.sale.analysis.wizard model has 18 fields: sh_end_date, sh_status, report_by, sh_product_ids, company_ids, sh_partner_ids, company_id, sale_analysis_dic, sale_currency_id, sh_status_ids, sh_start_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, selection: 3, many2many: 3, many2one: 3, one2many: 1, integer: 2, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.sale.analysis.wizard", "table_name": ""}
+{"text": "How do I use the stock.inventory.approval.matrix model?", "response": "To use the stock.inventory.approval.matrix model, you need to provide values for required fields: name, company_id, warehouse_id. Readonly fields: company_id, branch_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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.inventory.approval.matrix", "table_name": ""}
+{"text": "What are the available fields for extract.rfq.wizard?", "response": "The extract.rfq.wizard model has 8 fields: purchase_order_extract_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: one2many: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "extract.rfq.wizard", "table_name": ""}
+{"text": "Describe the res.config model in Odoo.", "response": "The res.config model represents Config in the ERP system. It contains 7 fields and is used to manage config data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.config", "table_name": ""}
+{"text": "What methods are available in res.users.log?", "response": "The res.users.log model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.users.log", "table_name": ""}
+{"text": "List all fields in the sh.purchase.report.representative.wizard model.", "response": "The sh.purchase.report.representative.wizard model has 13 fields: date_start, date_end, user_ids, state, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2many: 3, selection: 1, integer: 1, char: 1, many2one: 2.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.purchase.report.representative.wizard", "table_name": ""}
+{"text": "How is account.loan.pay.amount used in the system?", "response": "The account.loan.pay.amount model represents Loan pay amount in the ERP system. It contains 13 fields and is used to manage loan pay amount data. Key fields include: loan_id, currency_id, cancel_loan, date, amount, fees, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.loan.pay.amount", "table_name": ""}
+{"text": "How do I use the ir.http model?", "response": "To use the ir.http model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.http", "table_name": ""}
+{"text": "What fields does return.approval.matrix.line have?", "response": "The return.approval.matrix.line model has 19 fields: sequence, sequence1, approver, minimal_approver, approval_status, time_stamp, last_approved, approved, return_approval_matrix_id1, picking_id, approved_users, dev_rma_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 4, many2many: 2, text: 1, datetime: 4, many2one: 6, boolean: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "return.approval.matrix.line", "table_name": ""}
+{"text": "What operations can I perform on auditlog.log.line?", "response": "To use the auditlog.log.line model, you need to provide values for required fields: none. Readonly fields: field_name, field_description, name, model_id, model_name, model_model, res_id, user_id, method, http_session_id, http_request_id, log_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "auditlog.log.line", "table_name": ""}
+{"text": "List all fields in the sh.stock.move.global.check model.", "response": "The sh.stock.move.global.check model has 16 fields: product_id, sh_message, sh_quality_point_id, picking_id, sh_measure, text_message, attachment_ids, type, move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, text: 2, float: 1, many2many: 1, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.stock.move.global.check", "table_name": ""}
+{"text": "How to create records in report.equip3_pos_report.report_closed_session?", "response": "To use the report.equip3_pos_report.report_closed_session model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.equip3_pos_report.report_closed_session", "table_name": ""}
+{"text": "What does the sh.mrp.quality.alert model represent?", "response": "The sh.mrp.quality.alert model represents Mrp Quality Alert in the ERP system. It contains 47 fields and is used to manage mrp quality alert data. Key fields include: name, title, product_id, lot_id, user_id, team_id, sh_priority, tag_ids, color, sh_description, partner_id, stage_id, mrp_id, workorder_id, company_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.mrp.quality.alert", "table_name": ""}
+{"text": "Which fields in sh.sale.invoice.summary.xls are computed?", "response": "The sh.sale.invoice.summary.xls model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.sale.invoice.summary.xls", "table_name": ""}
+{"text": "What data can be stored in mrp.workcenter?", "response": "The mrp.workcenter model has 72 fields: active, note, sequence, color, routing_line_ids, order_ids, workorder_count, workorder_ready_count, workorder_progress_count, workorder_pending_count, workorder_late_count, time_ids, working_state, blocked_time, productive_time, oee, performance, workcenter_load, costs_hour_account_id, name, location_id, location_finished_id, location_rejected_id, location_byproduct_id, oh_time, ov_material, costs_hour, branch_id, create_uid, alternative_workcenter_ids, code, company_id, time_efficiency, capacity, oee_target, time_start, time_stop, is_branch_required, resource_id, resource_calendar_id, tz, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 7, text: 1, integer: 13, one2many: 9, selection: 4, float: 10, many2one: 14, char: 6, many2many: 3, date: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mrp.workcenter", "table_name": ""}
+{"text": "What methods are available in account.loan.line?", "response": "The account.loan.line model is defined in module: account_loan. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.loan.line", "table_name": ""}
+{"text": "What does the account.balance.report model represent?", "response": "The account.balance.report model represents Trial Balance Report in the ERP system. It contains 14 fields and is used to manage trial balance report data. Key fields include: journal_ids, display_account, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.balance.report", "table_name": ""}
+{"text": "How is cancel.credit.limit used in the system?", "response": "The cancel.credit.limit model represents cancel.credit.limit in the ERP system. It contains 9 fields and is used to manage cancel.credit.limit data. Key fields include: limit_id, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "cancel.credit.limit", "table_name": ""}
+{"text": "Describe the implementation of account.analytic.group.", "response": "The account.analytic.group model is defined in module: analytic. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.analytic.group", "table_name": ""}
+{"text": "What are the relationships in sh.mpo.merge.purchase.order.wizard?", "response": "The sh.mpo.merge.purchase.order.wizard model has 5 relational fields: partner_id -> res.partner; purchase_order_id -> purchase.order; purchase_order_ids -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: purchase_order_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.mpo.merge.purchase.order.wizard", "table_name": ""}
+{"text": "List all fields in the hide.field model.", "response": "The hide.field model has 16 fields: access_management_id, model_id, field_id, invisible, readonly, required, external_link, create_option, edit_option, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, many2many: 1, boolean: 6, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "hide.field", "table_name": ""}
+{"text": "What models are connected to product.template.create.variant?", "response": "The product.template.create.variant model has 3 relational fields: variant_ids -> product.template.create.variant.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.template.create.variant", "table_name": ""}
+{"text": "List all fields in the pos.cashier.change.wizard model.", "response": "The pos.cashier.change.wizard model has 10 fields: start_datetime, end_datetime, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2one: 3, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.cashier.change.wizard", "table_name": ""}
+{"text": "What fields does report.equip3_pos_report.report_pos_payment have?", "response": "The report.equip3_pos_report.report_pos_payment model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_pos_report.report_pos_payment", "table_name": ""}
+{"text": "What data can be stored in sms.resend?", "response": "The sms.resend model has 12 fields: mail_message_id, recipient_ids, has_cancel, has_insufficient_credit, has_unregistered_account, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, one2many: 1, boolean: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sms.resend", "table_name": ""}
+{"text": "List all fields in the account.multipayment.credit model.", "response": "The account.multipayment.credit model has 22 fields: line_id, currency_id, invoice_id, account_id, invoice_date, invoice_date_due, original_amount, base_amount, original_unreconcile, base_unreconcile, is_full_reconcile, amount, payment_id, account_reverse_ids, account_reverse_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, date: 2, monetary: 5, boolean: 1, many2many: 1, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.multipayment.credit", "table_name": ""}
+{"text": "What business logic is in website.track?", "response": "To use the website.track model, you need to provide values for required fields: visitor_id, visit_datetime. Readonly fields: visitor_id, page_id, visit_datetime, product_id, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "website.track", "table_name": ""}
+{"text": "What are the relationships in queue.job.channel?", "response": "The queue.job.channel model has 4 relational fields: parent_id -> queue.job.channel; job_function_ids -> queue.job.function; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "queue.job.channel", "table_name": ""}
+{"text": "How does all.loyalty.setting relate to other models?", "response": "The all.loyalty.setting model has 5 relational fields: product_id -> product.product; redeem_ids -> all.redeem.rule; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "all.loyalty.setting", "table_name": ""}
+{"text": "Which fields in return.approval.matrix.line are computed?", "response": "The return.approval.matrix.line model is defined in module: allfresh_mod_inventory. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "return.approval.matrix.line", "table_name": ""}
+{"text": "How is report_excel_export_gen used in the system?", "response": "The report_excel_export_gen model represents   in the ERP system. It contains 7 fields and is used to manage   data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report_excel_export_gen", "table_name": ""}
+{"text": "How to query mrp.immediate.production data?", "response": "To use the mrp.immediate.production model, you need to provide values for required fields: none. Readonly fields: show_productions, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mrp.immediate.production", "table_name": ""}
+{"text": "What foreign keys exist in picking.return.line?", "response": "The picking.return.line model has 7 relational fields: product_id -> product.product; picking_id -> stock.picking; purchase_id -> purchase.order; sale_id -> sale.order; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "picking.return.line", "table_name": ""}
+{"text": "List all fields in the kpi.category model.", "response": "The kpi.category model has 22 fields: name, active, parent_id, child_ids, company_id, description, sequence, user_ids, user_group_ids, access_user_ids, edit_user_ids, edit_user_group_ids, edit_access_user_ids, help_notes, kpi_help_dummy, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 2, many2one: 4, one2many: 1, text: 1, integer: 2, many2many: 6, html: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "kpi.category", "table_name": ""}
+{"text": "Which fields in purchase.request.line are computed?", "response": "The purchase.request.line model is defined in module: purchase_request. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.request.line", "table_name": ""}
+{"text": "What are common use cases for account.account.type?", "response": "To use the account.account.type model, you need to provide values for required fields: name, type, company_id. Readonly fields: company_id, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.account.type", "table_name": ""}
+{"text": "What methods are available in blanket.approval.matrix?", "response": "The blanket.approval.matrix model is defined in module: equip3_sale_other_operation_cont. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "blanket.approval.matrix", "table_name": ""}
+{"text": "How does account.bank.statement.line.wizard relate to other models?", "response": "The account.bank.statement.line.wizard model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.bank.statement.line.wizard", "table_name": ""}
+{"text": "Show me the relational structure of _unknown.", "response": "The _unknown model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "_unknown", "table_name": ""}
+{"text": "What data can be stored in report.reordering?", "response": "The report.reordering model has 9 fields: warehouse_id, location_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.reordering", "table_name": ""}
+{"text": "What is the rating.parent.mixin model?", "response": "The rating.parent.mixin model represents Rating Parent Mixin in the ERP system. It contains 5 fields and is used to manage rating parent mixin data. Key fields include: rating_ids, rating_percentage_satisfaction, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "rating.parent.mixin", "table_name": ""}
+{"text": "How to create records in hr.employee?", "response": "To use the hr.employee model, you need to provide values for required fields: company_id, resource_id. Readonly fields: user_partner_id, is_address_home_a_company, private_email, subordinate_ids, currency_id, image_1024, image_512, image_256, image_128, 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, hr_presence_state, last_activity, last_activity_time, hr_icon_display, goal_ids, badge_ids, has_badges, child_all_count, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "hr.employee", "table_name": ""}
+{"text": "Show me the relational structure of accounting.matrix.reject.", "response": "The accounting.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "accounting.matrix.reject", "table_name": ""}
+{"text": "How does accounting.matrix.reject relate to other models?", "response": "The accounting.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "accounting.matrix.reject", "table_name": ""}
+{"text": "How to create records in stock.assign.serial?", "response": "To use the stock.assign.serial model, you need to provide values for required fields: product_id, move_id. Readonly fields: product_id, picking_type_code, serial_no, next_serial_number, is_serial_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "stock.assign.serial", "table_name": ""}
+{"text": "How to query ks_dashboard_ninja.board data?", "response": "To use the ks_dashboard_ninja.board 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_dashboard_ninja.board", "table_name": ""}
+{"text": "How to create records in account.tax.report.wizard?", "response": "To use the account.tax.report.wizard model, you need to provide values for required fields: journal_ids, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.tax.report.wizard", "table_name": ""}
+{"text": "What are the relationships in stock.quant.package?", "response": "The stock.quant.package model has 13 relational fields: quant_ids -> stock.quant; packaging_id -> product.packaging; location_id -> stock.location; company_id -> res.company; owner_id -> res.partner; uom_id -> uom.uom; move_location_id -> stock.location; warehouse_id -> stock.warehouse; owner_id_stock -> res.partner; location_id_new -> stock.location; filter_location_id_new -> stock.location; create_uid -> res.users; write_uid -> res.users. Many2many fields: filter_location_id_new.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.quant.package", "table_name": ""}
+{"text": "Tell me about the sh.push.notification model.", "response": "The sh.push.notification model represents Web Push Notification in the ERP system. It contains 11 fields and is used to manage web push notification data. Key fields include: user_id, user_type, datetime, register_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.push.notification", "table_name": ""}
+{"text": "What does the purchase.quotation.excel.extended model represent?", "response": "The purchase.quotation.excel.extended model represents Purchase Quotation Excel Extended in the ERP system. It contains 9 fields and is used to manage purchase quotation excel extended data. Key fields include: excel_file, file_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.quotation.excel.extended", "table_name": ""}
+{"text": "What does the hide.chatter model represent?", "response": "The hide.chatter model represents Chatter Rights in the ERP system. It contains 13 fields and is used to manage chatter rights data. Key fields include: access_management_id, model_id, hide_chatter, hide_send_mail, hide_log_notes, hide_schedule_activity, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "hide.chatter", "table_name": ""}
+{"text": "What data can be stored in base_import.tests.models.char.readonly?", "response": "The base_import.tests.models.char.readonly model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.char.readonly", "table_name": ""}
+{"text": "What are the technical details of ir.mail_server?", "response": "The ir.mail_server model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.mail_server", "table_name": ""}
+{"text": "How do I use the receipt.voucher model?", "response": "To use the receipt.voucher model, you need to provide values for required fields: name, partner_ids, voucher_date, bank_id, customer_invoice_ids, currency_id, company_id, branch_id. Readonly fields: payment_count, name, state, amount, customer_allowed_ids, is_cutoff_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, id, display_name, create_uid, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "receipt.voucher", "table_name": ""}
+{"text": "What foreign keys exist in whatsapp.template?", "response": "The whatsapp.template model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "whatsapp.template", "table_name": ""}
+{"text": "Show me the relational structure of account.cashbox.wizard.bank.line.", "response": "The account.cashbox.wizard.bank.line model has 8 relational fields: account_cashbox_wizard_bank_id -> account.cashbox.wizard; payment_method_id -> pos.payment.method; cashbox_id -> account.bank.statement.cashbox; currency_id -> res.currency; pos_config_id -> pos.config; pos_session_id -> pos.session; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.cashbox.wizard.bank.line", "table_name": ""}
+{"text": "What business logic is in generate.pos.voucher?", "response": "To use the generate.pos.voucher model, you need to provide values for required fields: start_date, end_date. Readonly fields: user_id, use_history_ids, no_of_used, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "generate.pos.voucher", "table_name": ""}
+{"text": "What does the acrux.chat.connector model represent?", "response": "The acrux.chat.connector model represents Connector Definition in the ERP system. It contains 38 fields and is used to manage connector definition data. Key fields include: name, sequence, message, company_id, team_id, verify, source, channel, endpoint, apikey, sandbox, uuid, time_to_respond, time_to_reasign, border_color, ca_app_name, ca_status, ca_status_txt, ca_qr_code, sale_report_id, connector_type, qc_app_name, qc_status, qc_status_txt, qc_qr_code, qc_channel, qc_channel_id, qc_sdk_token, qc_template_ids, qc_webhook_url, connection_status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "acrux.chat.connector", "table_name": ""}
+{"text": "What modules define repair.order.make_invoice?", "response": "The repair.order.make_invoice model is defined in module: repair. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "repair.order.make_invoice", "table_name": ""}
+{"text": "Describe the implementation of access.rights.profile.", "response": "The access.rights.profile model is defined in module: equip3_general_features. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "access.rights.profile", "table_name": ""}
+{"text": "What is the dev.rma.rma model?", "response": "The dev.rma.rma model represents RMA in the ERP system. It contains 84 fields and is used to manage rma data. Key fields include: name, date, deadline_date, user_id, team_id, email, phone, notes, rma_lines, priority, tags, reject_reason, incoming_id, delivery_id, new_sale_id, invoice_id, is_rma_due, subject, partner_id, warehouse_id, location_id, sale_id, purchase_id, branch_id, filter_location_ids, operation_type_id, picking_type_code, new_purchase_id, receipt_id, is_po, return_possible_date, is_return_order, picking_id, analytic_group_ids, action_type, reason, company_id, is_done_bill, invoice_ids, picking_ids, remark, amount_total, company_currency_id, amount_total_untaxed, tax_amount, return_approval_matrix_id, rma_approval_matrix, return_approval_matrix_line_id, state, is_approve_matrix, is_request_for_approval_show, is_approve_button_show, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "dev.rma.rma", "table_name": ""}
+{"text": "How to create records in report.excel.param?", "response": "To use the report.excel.param model, you need to provide values for required fields: name, code, type_param. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.excel.param", "table_name": ""}
+{"text": "Describe the base.partner.merge.line model in Odoo.", "response": "The base.partner.merge.line model represents Merge Partner Line in the ERP system. It contains 10 fields and is used to manage merge partner line data. Key fields include: wizard_id, min_id, aggr_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "base.partner.merge.line", "table_name": ""}
+{"text": "Describe the quality.alert.report model in Odoo.", "response": "The quality.alert.report model represents Quality Alert Report in the ERP system. It contains 12 fields and is used to manage quality alert report data. Key fields include: date_from, date_to, product_ids, user_ids, stage_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "quality.alert.report", "table_name": ""}
+{"text": "How is o2m.global.search.fields used in the system?", "response": "The o2m.global.search.fields model represents o2m.global.search.fields in the ERP system. It contains 14 fields and is used to manage o2m.global.search.fields data. Key fields include: sequence, name, field_id, global_o2m_search_id, model_id, related_model_id, ttype, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "o2m.global.search.fields", "table_name": ""}
+{"text": "List all fields in the field.conditional.access model.", "response": "The field.conditional.access model has 18 fields: access_management_id, model_id, model_name, attrs_field_id, domain_field_id, domain_field_relation, attrs_type, field_attrs, field_domain, apply_attrs, apply_field_domain, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, char: 5, selection: 1, boolean: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "field.conditional.access", "table_name": ""}
+{"text": "What is the cancel.supplier.memory model?", "response": "The cancel.supplier.memory model represents cancel.supplier.memory in the ERP system. It contains 9 fields and is used to manage cancel.supplier.memory data. Key fields include: supplier_id, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "cancel.supplier.memory", "table_name": ""}
+{"text": "What business logic is in service.level.agreement?", "response": "To use the service.level.agreement 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "service.level.agreement", "table_name": ""}
+{"text": "Tell me about the mrp.bom model.", "response": "The mrp.bom model represents Bill of Material in the ERP system. It contains 53 fields and is used to manage bill of material data. Key fields include: active, bom_line_ids, byproduct_ids, product_uom_category_id, sequence, operation_ids, ready_to_produce, picking_type_id, consumption, sh_bom_barcode_mobile, sh_bom_bm_is_cont_scan, code, type, product_id, product_qty, company_id, product_uom_id, branch_id, create_uid, forecast_cost, tool_ids, bom_tools, next_new_sequence, operation_two_ids, is_branch_required, use_operations, equip_bom_type, product_tmpl_id, type_product_bom, product_tmpl_ids, product_ids, product_name_display, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.bom", "table_name": ""}
+{"text": "What models are connected to recurring.move.line?", "response": "The recurring.move.line model has 6 relational fields: partner_id -> res.partner; recurring_id -> invoice.recurring; account_id -> account.account; analytic_group_ids -> account.analytic.tag; create_uid -> res.users; write_uid -> res.users. Many2many fields: analytic_group_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "recurring.move.line", "table_name": ""}
+{"text": "How to create records in pos.combo.limit?", "response": "To use the pos.combo.limit model, you need to provide values for required fields: product_tmpl_id, pos_categ_id, quantity_limited. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.combo.limit", "table_name": ""}
+{"text": "Describe the field structure of res.config.settings.", "response": "The res.config.settings model has 849 fields: user_default_rights, external_email_server_default, module_base_import, module_google_calendar, module_microsoft_calendar, module_google_drive, module_google_spreadsheet, module_auth_oauth, module_auth_ldap, module_base_gengo, module_account_inter_company_rules, module_pad, module_voip, module_web_unsplash, module_partner_autocomplete, module_base_geolocalize, module_google_recaptcha, report_footer, group_multi_currency, paperformat_id, external_report_layout_id, show_effect, company_count, active_user_count, language_count, company_name, company_informations, app_default_superbar_lazy_search, geoloc_provider_id, geoloc_provider_techname, geoloc_provider_googlemap_key, recaptcha_public_key, recaptcha_private_key, recaptcha_min_score, fail_counter, alias_domain, unsplash_access_key, app_system_name, app_show_lang, app_show_debug, app_show_documentation, app_show_documentation_dev, app_show_support, app_show_account, app_show_enterprise, app_show_share, app_show_poweredby, group_show_author_in_apps, module_odoo_referral, app_documentation_url, app_documentation_dev_url, app_support_url, app_account_title, app_account_url, app_enterprise_url, app_ribbon_name, auth_signup_reset_password, auth_signup_template_user_id, resource_calendar_id, module_hr_presence, module_hr_skills, hr_presence_control_login, hr_presence_control_email, hr_presence_control_ip, module_hr_attendance, hr_presence_control_email_amount, hr_presence_control_ip_list, hr_employee_self_edit, kpi_company_id, kpi_history_tolerance, show_kpi_help, group_discount_per_so_line, group_uom, group_product_variant, module_sale_product_configurator, module_sale_product_matrix, group_stock_packaging, group_product_pricelist, group_sale_pricelist, product_pricelist_setting, product_weight_in_lbs, product_volume_volume_in_cubic_feet, enable_menu_search, enable_web_push_notification, api_key, vapid, config_details, sh_multi_barcode_unique, is_sh_product_qrcode_generator_when_create, snailmail_color, snailmail_cover, snailmail_duplex, digest_emails, digest_id, company_id, sh_product_stock, sh_product_attribute, sh_product_image, sh_product_category, sh_product_code, sh_product_barcode, sh_product_sale_price, sh_product_sale_description, sh_touch_kyboard, sh_welcome_message, sh_message, sh_company_logo, sh_display, sh_display_view, sh_display_landscape, sh_display_portrait, sh_delay_screen, has_accounting_entries, currency_id, has_chart_of_accounts, chart_template_id, purchase_tax_id, tax_calculation_rounding_method, module_account_accountant, group_analytic_accounting, group_warning_account, group_cash_rounding, group_show_line_subtotals_tax_excluded, group_show_line_subtotals_tax_included, group_show_sale_receipts, group_show_purchase_receipts, show_line_subtotals_tax_selection, module_account_budget, module_account_payment, module_account_reports, module_account_check_printing, module_account_batch_payment, module_account_sepa, module_account_sepa_direct_debit, module_account_plaid, module_account_yodlee, module_account_bank_statement_import_qif, module_account_bank_statement_import_ofx, module_account_bank_statement_import_csv, module_account_bank_statement_import_camt, module_currency_rate_live, module_account_intrastat, module_product_margin, module_l10n_eu_service, module_account_taxcloud, module_account_invoice_extract, module_snailmail_account, tax_exigibility, tax_cash_basis_journal_id, account_cash_basis_base_account_id, qr_code, invoice_is_print, invoice_is_email, incoterm_id, invoice_terms, use_invoice_terms, country_code, crm_alias_prefix, generate_lead_from_alias, group_use_lead, group_use_recurring_revenues, module_crm_iap_lead, module_crm_iap_lead_website, module_crm_iap_lead_enrich, module_mail_client_extension, lead_enrich_auto, lead_mining_in_pipeline, predictive_lead_scoring_start_date, predictive_lead_scoring_start_date_str, predictive_lead_scoring_fields, predictive_lead_scoring_fields_str, group_mass_mailing_campaign, mass_mailing_outgoing_mail_server, mass_mailing_mail_server_id, show_blacklist_buttons, module_project_forecast, module_hr_timesheet, group_subtask_project, group_project_rating, group_project_recurring_tasks, module_product_expiry, group_stock_production_lot, group_lot_on_delivery_slip, group_stock_tracking_lot, group_stock_tracking_owner, group_stock_adv_location, group_warning_stock, group_stock_sign_delivery, module_stock_picking_batch, module_stock_barcode, stock_move_email_validation, stock_mail_confirmation_template_id, module_stock_sms, group_stock_multi_locations, website_id, website_name, website_domain, website_country_group_ids, website_company_id, website_logo, language_ids, website_language_count, website_default_lang_id, website_default_lang_code, specific_user_account, website_cookies_bar, google_analytics_key, google_management_client_id, google_management_client_secret, google_search_console, cdn_activated, cdn_url, cdn_filters, social_twitter, social_facebook, social_github, social_linkedin, social_youtube, social_instagram, has_social_network, favicon, social_default_image, google_maps_api_key, group_multi_website, has_google_analytics, has_google_analytics_dashboard, has_google_maps, has_google_search_console, has_default_share_image, account_check_printing_layout, account_check_printing_date_label, account_check_printing_multi_stub, account_check_printing_margin_top, account_check_printing_margin_left, account_check_printing_margin_right, vat_check_vies, group_show_form_view, picking_operation_type, sh_it_barcode_mobile_type, sh_it_bm_is_cont_scan, sh_it_bm_is_notify_on_success, sh_it_bm_is_notify_on_fail, sh_it_bm_is_sound_on_success, sh_it_bm_is_sound_on_fail, sh_it_bm_is_add_product, module_project_timesheet_synchro, module_project_timesheet_holidays, project_time_mode_id, timesheet_encode_uom_id, timesheet_min_duration, timesheet_rounding, is_encode_uom_days, manufacturing_lead, use_manufacturing_lead, group_mrp_byproducts, module_mrp_mps, module_mrp_plm, module_mrp_workorder, module_quality_control, module_mrp_subcontracting, group_mrp_routings, group_locked_by_default, group_expiry_date_on_delivery_slip, lock_confirmed_po, po_lock, po_order_approval, po_double_validation, po_double_validation_amount, company_currency_id, default_purchase_method, group_warning_purchase, module_account_3way_match, module_purchase_requisition, module_purchase_product_matrix, po_lead, use_po_lead, group_send_reminder, module_sg_bank_reconcile, module_sg_dbs_giro, sh_invoice_online_signature, sh_enable_approval, sh_restrict_for_close_period, invoice_is_snailmail, module_stock_landed_costs, stock_qty_forecast_method, stock_qty_forecast_interval, stock_qty_predicted_periods, stock_move_sms_validation, stock_sms_confirmation_template_id, channel_id, group_enable_discuss, group_disable_poll, app_stop_subscribe, inv_cost, is_cost_price_per_warehouse, fiscalyear_last_day, fiscalyear_last_month, period_lock_date, fiscalyear_lock_date, group_fiscal_year, sale_tax_id, module_pos_mercury, module_pos_adyen, module_pos_six, update_stock_quantities, module_stock_dropshipping, days_to_purchase, is_installed_sale, group_auto_done_setting, module_sale_margin, quotation_validity_days, use_quotation_validity_days, group_warning_sale, portal_confirmation_sign, portal_confirmation_pay, group_sale_delivery_address, group_proforma_sales, default_invoice_policy, deposit_default_product_id, auth_signup_uninvited, module_delivery, module_delivery_dhl, module_delivery_fedex, module_delivery_ups, module_delivery_usps, module_delivery_bpost, module_delivery_easypost, module_product_email_template, module_sale_coupon, module_sale_amazon, automatic_invoice, template_id, confirmation_template_id, sh_group_enable_report_section, group_enable_merge_purchase_order, po_operation_type, cancel_receipt, cancel_bill, group_enable_purchase_checklist, group_enable_purchase_custom_product_template, purchase_show_signature, chk_sign_confirm, purchase_enable_other_sign_option, sh_expiry_notification, sh_is_notify_vendor, sh_on_date_notify, enter_before_first_notify, enter_before_second_notify, enter_before_third_notify, enter_after_first_notify, enter_after_second_notify, enter_after_third_notify, attachment_email, group_enable_purchase_multi_product_adv, sh_purchase_configuration_limit, group_enable_purchase_order_history, item_limit_purchase, record_based_on_purchase, group_enable_purchase_price_history, purchase_order_information_in_message, purchase_product_detail_in_message, purchase_signature, purchase_display_in_message, po_send_pdf_in_message, sh_auto_add_followers, sh_portal_user_create, sh_tender_document_manage, sh_purchase_revision, is_enable_vendor_notification, user_ids, is_enable_auto_portal_user, is_enable_company_portal_user, is_enable_company_contact_portal_user, crm_default_team_id, crm_default_user_id, l10n_id_tax_address, l10n_id_tax_name, reminder_frequency, group_sale_order_template, company_so_template_id, module_sale_quotation_builder, security_lead, group_display_incoterm, group_lot_on_invoice, use_security_lead, default_picking_policy, sh_manage_tender_doc_portal, lc_journal_id, salesperson_id, salesteam_id, module_website_sale_delivery, sale_delivery_settings, group_delivery_invoice_address, module_website_sale_digital, module_website_sale_wishlist, module_website_sale_comparison, module_website_sale_stock, module_account, cart_recovery_mail_template, cart_abandoned_delay, mailsend_check, email_notification_days, res_user_ids, validate_picking, create_invoice, validate_invoice, allow_auto_intercompany, ks_forecast_method, use_sale_order_note, sale_order_note, keep_name_so, sh_sale_barcode_mobile_type, sh_sale_bm_is_cont_scan, sh_sale_bm_is_notify_on_success, sh_sale_bm_is_notify_on_fail, sh_sale_bm_is_sound_on_success, sh_sale_bm_is_sound_on_fail, sh_purchase_barcode_mobile_type, sh_purchase_bm_is_cont_scan, sh_purchase_bm_is_notify_on_success, sh_purchase_bm_is_notify_on_fail, sh_purchase_bm_is_sound_on_success, sh_purchase_bm_is_sound_on_fail, sh_invoice_barcode_mobile_type, sh_invoice_bm_is_cont_scan, sh_invoice_bm_is_notify_on_success, sh_invoice_bm_is_notify_on_fail, sh_invoice_bm_is_sound_on_success, sh_invoice_bm_is_sound_on_fail, sh_bom_barcode_mobile_type, sh_bom_bm_is_cont_scan, sh_bom_bm_is_notify_on_success, sh_bom_bm_is_notify_on_fail, sh_bom_bm_is_sound_on_success, sh_bom_bm_is_sound_on_fail, sh_stock_barcode_mobile_type, sh_stock_bm_is_cont_scan, sh_stock_bm_is_notify_on_success, sh_stock_bm_is_notify_on_fail, sh_stock_bm_is_sound_on_success, sh_stock_bm_is_sound_on_fail, sh_stock_bm_is_add_product, sh_inventory_adjt_barcode_mobile_type, sh_inventory_adjt_bm_is_cont_scan, sh_inventory_adjt_bm_is_notify_on_success, sh_inventory_adjt_bm_is_notify_on_fail, sh_inventory_adjt_bm_is_sound_on_success, sh_inventory_adjt_bm_is_sound_on_fail, sh_product_barcode_mobile_type, sh_product_bm_is_cont_scan, sh_product_bm_is_notify_on_success, sh_product_bm_is_notify_on_fail, sh_product_bm_is_sound_on_success, sh_product_bm_is_sound_on_fail, sh_product_bm_is_default_code, sh_product_bm_is_lst_price, sh_product_bm_is_qty_available, sh_product_bm_is_virtual_available, sh_global_document_search_is_enable, sh_global_document_search_is_sale, sh_global_document_search_is_purchase, sh_global_document_search_is_picking, sh_global_document_search_is_invoice, sh_global_document_search_is_product, sh_global_document_search_is_lot, sh_global_document_search_is_location, sh_global_document_search_action_target_type, sale_credit_limit_email_alerts, sale_email_specific_user_id, quot_to_po, so_to_po, inventory_availability, available_threshold, website_warehouse_id, down_payment_product_id, implementor_setting, general, purchase, sales, inventory, manufacturing, central_kitchen, human_resource, pos, simple_manufacturing, assembly, cutting, mining, agriculture, show_branch, past_x_days_sales, currency_exchange_journal_id, income_currency_exchange_account_id, expense_currency_exchange_account_id, unrealized_exchange_journal_id, income_unrealized_exchange_account_id, expense_unrealized_exchange_account_id, is_inverse_rate, is_taxes_rate, tax_discount_policy, sale_account_id, purchase_account_id, interest_income, interest_expense, deposit_reconcile_journal_id, journal_id, deposit_account_id, petty_cash_expense_account_id, overdue_template, tax_rounding_type, accounting, is_credit_note_approval_matrix, is_refund_approval_matrix, is_customer_deposit_approval_matrix, is_vendor_deposit_approval_matrix, is_receipt_giro_approval_matrix, is_payment_giro_approval_matrix, is_purchase_currency_approval_matrix, is_budget_approval_matrix, is_budget_change_req_approval_matrix, is_purchase_budget_approval_matrix, is_purchase_budget_change_req_approval_matrix, is_internal_transaction, is_analytic_groups_balance_sheet, is_assets_approving_matrix, is_cash_advance_approving_matrix, is_invoice_approval_matrix, is_bill_approval_matrix, is_other_income_approval_matrix, is_other_expense_approval_matrix, is_customer_multi_receipt_approval_matrix, is_vendor_multipayment_approval_matrix, is_receipt_approval_matrix, is_payment_approval_matrix, is_payment_voucher_approval_matrix, group_is_credit_note_approval_matrix, group_is_refund_approval_matrix, group_is_customer_deposit_approval_matrix, group_is_vendor_deposit_approval_matrix, group_is_receipt_giro_approval_matrix, group_is_payment_giro_approval_matrix, group_is_internal_transfer_approval_matrix, group_is_purchase_currency_approval_matrix, group_is_budget_approval_matrix, group_is_budget_change_req_approval_matrix, group_is_purchase_budget_approval_matrix, group_is_purchase_budget_change_req_approval_matrix, group_account_asset_category_fiscal, group_assets_approving_matrix, group_cash_advance_approval_matrix, group_is_invoice_approval_matrix, group_is_bill_approval_matrix, group_is_other_income_approval_matrix, group_is_other_expense_approval_matrix, group_is_customer_multi_receipt_approval_matrix, group_is_vendor_multipayment_approval_matrix, group_is_receipt_approval_matrix, group_is_payment_approval_matrix, group_is_payment_voucher_approval_matrix, module_om_account_budget, Use_received_date, customer_availability, automated_invoice_followup, followup_sending_date, reminder_interval_before, reminder_interval_before_unit, reminder_notification_before, reminder_interval_after, reminder_interval_after_unit, reminder_notification_after, invoice_bill_reminder, reminder_interval_before_invoice, reminder_interval_after_invoice, reminder_interval_before_unit_invoice, eminder_interval_after_unit_invoice, reminder_notification_before_invoice, reminder_notification_after_invoice, days_bill_before, days_bill_after, days_invoice_before, days_invoice_after, sending_date_bill_before, sending_date_bill_after, sending_date_invoice_before, sending_date_invoice_after, date_last_reminder_due_date, date_last_reminder_after_due_date, date_last_reminder_bill_due_date, date_last_reminder_bill_after_due_date, date_last_reminder_bill_before_due_date, is_invoice_cutoff_date, invoice_cutoff_date, post_discount_account, prefix_limit, is_material_request_approval_matrix, is_internal_transfer_approval_matrix, is_stock_count_approval, is_product_usage_approval, is_return_orders, return_type, is_inventory_adjustment_with_value, putaway_max_capacity, set_warehouse_sublevel, warehouse_sublevel_zone, warehouse_sublevel_shelf, warehouse_sublevel_rack, warehouse_sublevel_bin, group_is_three_dimension_warehouse, is_mbs_on_transfer_operations, is_mbs_on_product_usage, is_mbs_on_stock_count_and_inventory_adjustment, outgoing_routing_strategy, sort_quants_by, routing_order, is_receiving_notes_approval_matrix, is_adj_picking, is_delivery_order_approval_matrix, brand_setting, is_manufacturing_plan, allow_submit_purchase_request, allow_submit_material_request, mo_force_done, manufacturing_plan_conf, manufacturing_order_conf, mrp_plan_partial_availability, mp_auto_reserve_availability_materials, mo_auto_reserve_availability_materials, production_record_conf, mrp_production_partial_availability, mrp_submit_purchase_request, mrp_submit_material_request, mrp_force_done, manufacturing_mps, manufacturing_period, manufacturing_period_to_display, autogenerated_based_methods, send_wa_approval_notification_mrp, send_wa_approval_notification_mp, send_wa_approval_notification_mpr, is_vendor_approval_matrix, is_purchase_order_approval_matrix, is_purchase_request_approval_matrix, is_vendor_pricelist_approval_matrix, is_purchase_tender_approval_matrix, purchase_approval_matrix, is_blanket_order_approval_matrix, is_good_services_order, is_purchase_tender, is_blanket_order, is_direct_purchase_approval_matrix, is_pr_department, is_price_ratting_rfq_tender, retail, module_equip3_purchase_rental, is_product_brand_filter, is_product_vendor_pricelist_filter, is_service_work_order, is_purchase_request_assign_user, group_create_purchase_request_direct, is_customer_approval_matrix, is_customer_limit_matrix, is_over_limit_validation, is_bo_approval_matrix, show_sale_barcode_mobile_type, sh_sale_barcode_mobile_type_new, group_om_account_budget, credit_note_expiry_date, bom_tools, sale_order_multiple_pricelist, automatic_confirm_saleorder, automatic_invoice_create, is_delivery_acknowledgement, is_broadcast_order, module_pragmatic_portal_user, module_pragmatic_delivery_acknowledgement, module_pragmatic_website_cash_on_delivery, commission_pay_on, commission_calc, commission_pay_by, is_message_rn, send_notification_users_ids, bank_integrate_url, bank_integrate_username, bank_integrate_password, validate_api, accounting_budget_use_theoretical_achievement, is_pajak_express_integration, pajak_express_url, pajak_express_transaction_url, pajak_express_username, pajak_express_password, validate_api_first, validate_api_express, validate_api_express_fail, group_is_pajak_express_integration, is_call_bi_api, is_call_kemenkeu_api, token_kemenkeu_api, internal_type, ex_period, material_request, is_product_service_operation, is_product_service_operation_delivery, mr_expiry_days, itr_expiry_days, is_return_limit_policy, return_policy_days, is_display_warehouse_address, module_procurement_jit, is_warehouse_shipments, qty_can_minus, is_vendor_approval_email, is_vendor_approval_whatsapp, is_vendor_pricelist_approval_email, is_vendor_pricelist_approval_whatsapp, sale_matrix_config, is_total_amount, total_sequence, total_sequence_select, is_margin_amount, margin_sequence, margin_sequence_select, is_discount_amount, discount_sequence, discount_sequence_select, expired_date, multilevel_disc_sale, is_wa_so_approval, is_email_so_approval, show_select_product_button, lock_sale_order, product_pricelist_default, auto_mail, group_multi_do, whatsapp_instance_id, whatsapp_token, qr_code_image, whatsapp_authenticate, product_expiry, expiry_days_select, group_analytic_tags, pu_barcode_mobile_type, pu_bm_is_cont_scan, pu_bm_is_notify_on_success, pu_bm_is_notify_on_fail, pu_bm_is_sound_on_success, pu_bm_is_sound_on_fail, pu_bm_is_add_product, pr_expiry_notification, pr_on_date_notify, pr_enter_before_first_notify, pr_enter_after_first_notify, pr_expiry_date, pr_expiry_date_goods, pr_expiry_date_services, rfq_exp_date, po_exp_date, rfq_exp_date_goods, rfq_exp_date_services, po_exp_date_goods, po_exp_date_services, max_percentage, pr_qty_limit, multilevel_disc, is_email_notification_req, is_whatsapp_notification_req, vendor_purchase_limit, is_email_notification, is_whatsapp_notification, pr_order_average_price, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, customer_credit_limit, customer_max_invoice_overdue_days, customer_open_invoice_limit, is_over_credit_limit, over_credit_limit_sequence, over_credit_limit_sequence_select, is_invoice_overdue, invoice_overdue_sequence, invoice_overdue_sequence_select, open_invoice_limit, open_invoice_limit_sequence, open_invoice_limit_sequence_select, is_wa_overlimit_approval, is_email_overlimit_approval, is_email_notification_customer_credit, is_whatsapp_notification_customer_credit, group_use_multi_salesperson_on_leads, is_auto_follow_up, interval_number, interval_type, number_of_repetition, expired_lot_serial_no, is_auto_validate, scrap_income_id, scrap_expense_id, pt_expiry_notification, pt_on_date_notify, pt_enter_before_first_notify, pt_enter_after_first_notify, pt_expiry_date, bo_expiry_notification, bo_enter_before_first_notify, bo_enter_after_first_notify, pt_goods_order_expiry_date, pt_service_order_expiry_date, bo_goods_order_expiry_date, bo_service_order_expiry_date, is_email_notification_tender, is_whatsapp_notification_tender, is_email_notification_bo, is_whatsapp_notification_bo, notifications_expiry_voucher, notifications_time, bo_expiry_date, bo_before_exp_notify, bo_days_before_exp_notify, bo_on_date_notify, bo_approval_email_notify, bo_approval_wa_notify, is_order_rounding, order_rounding_type, rounding_multiplier, pos_product_discount1_id, apply_rounding_type, rounding_method_id, pos_def_receipt_template_id, is_pos_receivable, direct_control, qty_limit, budget_limit, is_email_notification_direct_purchase, is_whatsapp_notification_direct_purchase, is_post_closing_cashbox_value_in_session, allow_create_member_in_pos_screen, pkp_customer, membership_pluspoint_rounding, membership_pluspoint_rounding_type, membership_pluspoint_rounding_multiplier, is_pos_use_deposit, is_return_request_approval_matrix, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 535, text: 7, many2one: 61, integer: 71, char: 52, float: 16, selection: 85, date: 8, many2many: 6, binary: 4, monetary: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.config.settings", "table_name": ""}
+{"text": "What does the untaken.stock.line model represent?", "response": "The untaken.stock.line model represents Untaken Stock Line in the ERP system. It contains 11 fields and is used to manage untaken stock line data. Key fields include: product_id, quantity, product_unit_measure, untaken_stock_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "untaken.stock.line", "table_name": ""}
+{"text": "List all fields in the account.journal.group model.", "response": "The account.journal.group model has 11 fields: name, company_id, excluded_journal_ids, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, many2many: 1, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.journal.group", "table_name": ""}
+{"text": "What are common use cases for saleblanket.saleblanket?", "response": "To use the saleblanket.saleblanket model, you need to provide values for required fields: name, expiry_date, branch_id. Readonly fields: name, sale_order_count, creation_date, user_id, order_line_count, state, currency_id, state1, state2, state3, bo_state, bo_state_1, company_id, approving_matrix_bo_sale_id, is_bo_approval_matrix, is_approval_matrix_filled, is_approve_button, approval_matrix_line_id, approved_matrix_ids, amount_untaxed, amount_tax, amount_total, analytic_accounting, is_product_filled, max_line_sequence, report_template_id1, amount_to_text, activity_state, activity_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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "saleblanket.saleblanket", "table_name": ""}
+{"text": "How is hr.employee.public implemented technically?", "response": "The hr.employee.public model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hr.employee.public", "table_name": ""}
+{"text": "What are the technical details of itr.approval.matrix?", "response": "The itr.approval.matrix model is defined in module: equip3_inventory_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "itr.approval.matrix", "table_name": ""}
+{"text": "Describe the implementation of setu.stock.movement.report.", "response": "The setu.stock.movement.report model is defined in module: setu_advance_inventory_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "setu.stock.movement.report", "table_name": ""}
+{"text": "What models are connected to queue.jobs.to.done?", "response": "The queue.jobs.to.done model has 3 relational fields: job_ids -> queue.job; create_uid -> res.users; write_uid -> res.users. Many2many fields: job_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "queue.jobs.to.done", "table_name": ""}
+{"text": "What modules define ir.ui.view.custom?", "response": "The ir.ui.view.custom model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.ui.view.custom", "table_name": ""}
+{"text": "Describe the many2many relations for asset.cip.line.", "response": "The asset.cip.line model has 6 relational fields: product_id -> product.template; account_id -> account.account; cip_id -> asset.cip; move_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "asset.cip.line", "table_name": ""}
+{"text": "What are the technical details of pos.combo.item?", "response": "The pos.combo.item model is defined in module: equip3_pos_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "pos.combo.item", "table_name": ""}
+{"text": "What business logic is in base_import.tests.models.m2o.required?", "response": "To use the base_import.tests.models.m2o.required model, you need to provide values for required fields: value. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "base_import.tests.models.m2o.required", "table_name": ""}
+{"text": "How to create records in utm.source?", "response": "To use the utm.source 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "utm.source", "table_name": ""}
+{"text": "Show me the fields of setu.inventory.overstock.bi.report.", "response": "The setu.inventory.overstock.bi.report model has 31 fields: product_id, product_category_id, warehouse_id, company_id, sales, ads, qty_available, incoming, outgoing, forecasted_stock, demanded_qty, coverage_days, overstock_qty, overstock_value, wh_overstock_qty_per, wh_overstock_value_per, turnover_ratio, stock_movement, last_purchase_date, last_purchase_qty, last_purchase_price, currency_name, vendor_name, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, float: 15, char: 4, date: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.overstock.bi.report", "table_name": ""}
+{"text": "Show me the relational structure of sh.purchase.report.representative.wizard.", "response": "The sh.purchase.report.representative.wizard model has 5 relational fields: user_ids -> res.users; company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, company_ids, branch_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.report.representative.wizard", "table_name": ""}
+{"text": "How to query term.condition data?", "response": "To use the term.condition 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "term.condition", "table_name": ""}
+{"text": "How does x.report.wizard relate to other models?", "response": "The x.report.wizard model has 5 relational fields: pos_session_ids -> pos.session; branch_id -> res.branch; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: pos_session_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "x.report.wizard", "table_name": ""}
+{"text": "What modules define sh.top.customers.xls?", "response": "The sh.top.customers.xls model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.top.customers.xls", "table_name": ""}
+{"text": "What operations can I perform on ir.actions.act_window_close?", "response": "To use the ir.actions.act_window_close model, you need to provide values for required fields: type, name, binding_type. Readonly fields: xml_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ir.actions.act_window_close", "table_name": ""}
+{"text": "List all fields in the product.pricelist.item model.", "response": "The product.pricelist.item model has 39 fields: product_tmpl_id, product_id, categ_id, min_quantity, base, base_pricelist_id, pricelist_id, price_surcharge, price_discount, price_round, price_min_margin, price_max_margin, company_id, currency_id, active, date_start, date_end, compute_price, fixed_price, percent_price, price, minimum_price, maximum_price, new_price, pricelist_uom_id, uom_id, uom_ids, applied_on, pos_category_id, min_price, max_price, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 12, float: 12, selection: 3, boolean: 1, datetime: 5, char: 4, many2many: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.pricelist.item", "table_name": ""}
+{"text": "What fields does pos.account.cashbox.line have?", "response": "The pos.account.cashbox.line model has 11 fields: coin_value, number, subtotal, pos_config_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 2, integer: 2, many2one: 3, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.account.cashbox.line", "table_name": ""}
+{"text": "What are the relationships in expiry.picking.confirmation?", "response": "The expiry.picking.confirmation model has 6 relational fields: lot_ids -> stock.production.lot; picking_ids -> stock.picking; production_ids -> mrp.production; workorder_id -> mrp.workorder; create_uid -> res.users; write_uid -> res.users. Many2many fields: lot_ids, picking_ids, production_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "expiry.picking.confirmation", "table_name": ""}
+{"text": "What are the available fields for ir.qweb.field.float_time?", "response": "The ir.qweb.field.float_time model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.qweb.field.float_time", "table_name": ""}
+{"text": "What are the available fields for account.loan.post?", "response": "The account.loan.post model has 10 fields: loan_id, journal_id, account_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 5, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.loan.post", "table_name": ""}
+{"text": "What fields does setu.inventory.fsn.analysis.report have?", "response": "The setu.inventory.fsn.analysis.report model has 16 fields: stock_file_data, start_date, end_date, product_category_ids, product_ids, warehouse_ids, stock_movement_type, company_id, company_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: binary: 1, date: 2, many2many: 4, selection: 1, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.fsn.analysis.report", "table_name": ""}
+{"text": "List all fields in the ir.translation model.", "response": "The ir.translation model has 12 fields: name, res_id, lang, type, src, value, module, state, comments, id, display_name, __last_update. Field types distribution: char: 3, integer: 2, selection: 3, text: 3, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.translation", "table_name": ""}
+{"text": "Describe the field structure of report.stock.report_product_template_replenishment.", "response": "The report.stock.report_product_template_replenishment model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.stock.report_product_template_replenishment", "table_name": ""}
+{"text": "What are the available fields for report.excel.aggregate?", "response": "The report.excel.aggregate model has 9 fields: code, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.excel.aggregate", "table_name": ""}
+{"text": "What are common use cases for payment.sale.details.report?", "response": "To use the payment.sale.details.report 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "payment.sale.details.report", "table_name": ""}
+{"text": "What are the available fields for project.task.type.delete.wizard?", "response": "The project.task.type.delete.wizard model has 11 fields: project_ids, stage_ids, tasks_count, stages_active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2many: 2, integer: 2, boolean: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "project.task.type.delete.wizard", "table_name": ""}
+{"text": "How to create records in pos.promotion?", "response": "To use the pos.promotion model, you need to provide values for required fields: name, end_date, type, tebus_murah_brand_gift_based_on, start_date. Readonly fields: currency_id, no_of_used, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.promotion", "table_name": ""}
+{"text": "What data can be stored in pos.receipt.template?", "response": "The pos.receipt.template model has 28 fields: name, is_default, size, custom_size, is_need_header, receipt_header_text, is_need_footer, receipt_footer_text, is_receipt_disc_in_orderline, is_receipt_tax_include_orderline, is_receipt_serial_lot_info, is_receipt_savings_summary, savings_summary_text, is_receipt_product_code, preview_receipt, company_id, voucher_receipt_display, generate_voucher_id, is_voucher_receipt, is_show_discount_detail, is_receipt_member_info, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 11, selection: 2, float: 1, text: 3, html: 1, many2one: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.receipt.template", "table_name": ""}
+{"text": "What are the available fields for account.payment?", "response": "The account.payment model has 398 fields: partner_type, check_amount_in_words, check_manual_sequencing, check_number, name, payment_transaction_id, payment_token_id, related_partner_ids, is_prepayment, prepayment_journal_id, start_date, end_date, recurring_interval, recurring_interval_unit, stop_recurring_interval, stop_recurring_interval_unit, revenue_account, apply_manual_currency_exchange, manual_currency_exchange_rate, active_manual_currency_rate, user_id, move_id, is_reconciled, is_matched, partner_bank_id, is_internal_transfer, qr_code, payment_method_id, available_payment_method_ids, hide_payment_method, amount, payment_type, payment_reference, currency_id, partner_id, destination_account_id, reconciled_invoice_ids, reconciled_invoices_count, reconciled_bill_ids, reconciled_bills_count, reconciled_statement_ids, reconciled_statements_count, payment_method_code, show_partner_bank_account, require_partner_bank_account, country_code, voucher_id, receipt_voucher_id, branch_id, payment_receipt_approval_matrix_id, is_receipt_approval_matrix, is_approve_button, approved_matrix_ids, approval_matrix_line_id, approval_invoice_id, administration, analytic_group_ids, administration_account, administration_fee, payment_transaction_credit, payment_transaction_credit_count, payment_transaction_debit, payment_transaction_debit_count, reconcile_invisible, online_payment_status, estimasi_transfer, af_move_id, origin, pos_branch_id, pos_session_id, available_partner_bank_ids, is_pos_void_fixed, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, highest_name, ref, move_type, type_name, suitable_journal_ids, company_id, is_move_sent, payment_state, invoice_user_id, invoice_origin, invoice_source_email, preferred_payment_method_id, debit_origin_id, debit_note_ids, debit_note_count, edi_document_ids, edi_state, edi_error_count, edi_web_services_to_process, edi_show_cancel_button, edi_show_abandon_cancel_button, edi_error_message, edi_blocking_level, loan_line_id, loan_id, attn, signature, journal_bank_id, payment_proof, tax_payment_date, payment_fields_boolean, ppn, pph, tax_paid_status, file_name, payment_date, tax_payment_move_id, tax_pay_seprately_amount, is_edit_data, asset_depreciation_ids, transaction_ids, authorized_transaction_ids, purchase_vendor_bill_id, purchase_id, sh_invoice_recurring_order_id, period_id, fiscal_year, stock_move_id, stock_valuation_layer_ids, auto_reverse, auto_reverse_date, auto_reverse_journal_id, auto_reverse_date_mode, auto_reversal_entry_date, auto_reversed, to_delete_from_svl, pos_order_ids, team_id, partner_shipping_id, is_consignment, consignment_start_date, consignment_end_date, consignment_pos_ids, l10n_id_tax_number, l10n_id_attachment_id, l10n_id_csv_created, l10n_id_need_kode_transaksi, landed_costs_ids, landed_costs_visible, website_id, is_line, discount_method, discount_amount, discount_type, discount_amt, amount_untaxed, discount_amt_line, discount_account_id, discount_amount_line, warranty_invoice, warranty_reg_id, related_project_id, show_intrest, interest, check_date, check_month, repair_ids, sh_invoice_barcode_mobile, sh_invoice_bm_is_cont_scan, target_commission_id, commission_count, down_payment_amount, total_down_payment_amount, is_down_payment, down_payment_purchase_id, report_template_id1, report_template_id, amount_to_text, timesheet_ids, timesheet_count, approval_matrix_id, is_invoice_approval_matrix, state1, state2, is_register_payment_done, invoice_origin_id, invoice_origin_date, reason, ref_no, request_partner_id, is_fiscal_book_exclude, received_date, visible_received_date, to_approve_state_payment_count, show_name_warning, date, posted_before, to_check, journal_id, company_currency_id, line_ids, commercial_partner_id, payment_id, statement_line_id, amount_tax, amount_tax2, subtotal_amount, amount_total, amount_untaxed_signed, amount_tax_signed, amount_total_signed, amount_residual_signed, amount_by_group, tax_cash_basis_rec_id, tax_cash_basis_move_id, auto_post, reversed_entry_id, reversal_move_id, fiscal_position_id, invoice_date, invoice_date_due, invoice_payment_term_id, invoice_line_ids, invoice_incoterm_id, display_qr_code, qr_code_method, invoice_outstanding_credits_debits_widget, invoice_has_outstanding, invoice_payments_widget, invoice_vendor_bill_id, invoice_partner_display_name, invoice_cash_rounding_id, invoice_filter_type_domain, bank_partner_id, invoice_has_matching_suspense_amount, tax_lock_date_message, has_reconciled_entries, show_reset_to_draft_button, restrict_mode_hash_table, secure_sequence_number, inalterable_hash, string_to_hash, mr_show_analytic_account, journal_entries_template, analytic_tag_dynamic, credit_note_expiry_date, expiry_date, approvers_ids, approved_user_ids, internal_tf_id, reversal_avail, date_id, is_record_created, is_merge, is_merge_to, new_invoice_id, count_merged_invoice, is_button_update_invisible, narration, multi_discount, is_intercompany_transaction, account_asset_id, state, customer_deposit_ids, vendor_deposit_ids, status_code, nomor_seri, ebupot_id, code, check, check_invisible, total_tax_ppn, total_inv_ppn, subtotal_inv_ppn, tax_number_bupot, kode_dokumen, kode_seri, nomor_seri_bupot, check_invisible_ebupot, ebupot_template, l10n_id_replace_invoice_id, l10n_id_kode_transaksi, is_upload_djp, is_upload_djp_cn, pajak_express_id, approval_url, efaktur_url, nomor_dokumen_pendukung, hide_button_upload, hide_button_upload_cn, tipe_pembayaran, keterangan_tambahan, uang_muka, uang_muka_ppn, uang_muka_ppnbm, signature_country_id, signature_city_id, nomor_seri_domain, current_rate, is_company_curr, current_inverse_rate, inverse_rate_visible, amount_residual, tax_rate, taxes_base_price, sales_times_tax_rate, tax_applies_on, manual_currency_exchange_inverse_rate, currency_revaluation_id, children_ids, currency_revaluation_ref_id, currency_revaluation_count, pettycash_id, is_petty_cash_voucher, sale_order_reference_id, filter_sale_order_reference_ids, exchange_id, exchange_stage, exchange_date, exchange_status, assembly_id, stock_scrap_id, kitchen_id, purchase_order_id, swo, swo_ids, amount_swo, is_services_orders, finish_good_rework_id, sale_order_ids, filter_sale_order_ids, purchase_order_ids, filter_purchase_order_ids, picking_ids, filter_picking_ids, sale_order_ids_boolean, purchase_order_ids_boolean, picking_ids_boolean, cashback_line_ids, show_cashback, is_cn_from_cashback, so_cashback_id, is_dp, payments_date, manual_change_status_code, return_picking_ids, picking_id, nomor_seri_faktur_pajak_new, rma_id, receiving_note_names, receiving_note_dates, account_invoice_ids, sequence, pos_order_id, is_from_pos_receivable, is_from_pos_cash_management, is_from_pos_cash_difference, is_from_pos_umum, is_from_pos_member, is_from_pos_member_gabungan, is_from_pos_partner, is_pkp_record, deposit_account_journal_id, create_from_session_id, inventory_id, _barcode_scanned, campaign_id, source_id, medium_id, access_url, access_token, access_warning, sequence_prefix, sequence_number. Field types distribution: selection: 24, char: 49, boolean: 84, many2one: 100, many2many: 26, date: 20, integer: 23, float: 20, monetary: 14, one2many: 22, datetime: 4, text: 5, html: 4, binary: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.payment", "table_name": ""}
+{"text": "Which fields in rma.report are computed?", "response": "The rma.report model is defined in module: dev_rma. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "rma.report", "table_name": ""}
+{"text": "What business logic is in sh.correct.qc.measurement?", "response": "To use the sh.correct.qc.measurement model, you need to provide values for required fields: none. Readonly fields: sh_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.correct.qc.measurement", "table_name": ""}
+{"text": "What modules define report.sh_sale_reports.sh_sale_details_report_doc?", "response": "The report.sh_sale_reports.sh_sale_details_report_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_sale_details_report_doc", "table_name": ""}
+{"text": "What models are connected to crm.phonecall2phonecall?", "response": "The crm.phonecall2phonecall model has 6 relational fields: user_id -> res.users; tag_ids -> crm.tag; team_id -> crm.team; partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.phonecall2phonecall", "table_name": ""}
+{"text": "What business logic is in pos.payment.method.mdr?", "response": "To use the pos.payment.method.mdr 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.payment.method.mdr", "table_name": ""}
+{"text": "Describe the field structure of res.country.group.", "response": "The res.country.group model has 10 fields: name, country_ids, pricelist_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2many: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "res.country.group", "table_name": ""}
+{"text": "How do I use the theme.website.page model?", "response": "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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "theme.website.page", "table_name": ""}
+{"text": "What are the technical details of void.order.line?", "response": "The void.order.line model is defined in module: allfresh_mod_pos. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "void.order.line", "table_name": ""}
+{"text": "What models are connected to sh.report.template?", "response": "The sh.report.template model has 4 relational fields: section_line -> sh.report.section; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.report.template", "table_name": ""}
+{"text": "What are the relationships in intrawarehouse.transfer?", "response": "The intrawarehouse.transfer model has 3 relational fields: interawarehouse_transfer_ids -> intrawarehouse.transfer.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "intrawarehouse.transfer", "table_name": ""}
+{"text": "What does the global.search model represent?", "response": "The global.search model represents Global Search in the ERP system. It contains 11 fields and is used to manage global search data. Key fields include: model_id, field_ids, main_field_id, global_field_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "global.search", "table_name": ""}
+{"text": "What business logic is in account.invoice.to.draft?", "response": "To use the account.invoice.to.draft 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.invoice.to.draft", "table_name": ""}
+{"text": "Which fields in mail.blacklist are computed?", "response": "The mail.blacklist model is defined in module: mail. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mail.blacklist", "table_name": ""}
+{"text": "What does the account.partner.ledger model represent?", "response": "The account.partner.ledger model represents Partner Ledger Report in the ERP system. It contains 21 fields and is used to manage partner ledger report data. Key fields include: journal_ids, account_ids, display_account, partner_ids, partner_category_ids, reconciled, account_type_ids, show_all_transaction, expand, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.partner.ledger", "table_name": ""}
+{"text": "Describe the implementation of sale.data.margin.line.", "response": "The sale.data.margin.line model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.data.margin.line", "table_name": ""}
+{"text": "Which fields in account.payment.method are computed?", "response": "The account.payment.method model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.payment.method", "table_name": ""}
+{"text": "Describe the many2many relations for picking.order.", "response": "The picking.order model has 27 relational fields: delivery_boy -> res.partner; sale_order -> sale.order; invoice -> account.move; picking -> stock.picking; partner_id -> res.partner; pos_order_id -> pos.order; pos_partner_id -> res.partner; state_id -> res.country.state; country_id -> res.country; bank_statement_ids -> pos.payment; lines -> picking.order.line; session_id -> pos.session; cashier -> res.users; warehouse_id -> stock.warehouse; transaction_id -> payment.transaction; stage_id -> order.stage; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "picking.order", "table_name": ""}
+{"text": "Tell me about the sh.qc.measurement.line model.", "response": "The sh.qc.measurement.line model represents Quality Measurement Line in the ERP system. It contains 14 fields and is used to manage quality measurement line data. Key fields include: measurement_id, product_id, sh_measure, sh_text, state, quality_point_id, type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.qc.measurement.line", "table_name": ""}
+{"text": "Which fields in account.move.line are computed?", "response": "The account.move.line model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.move.line", "table_name": ""}
+{"text": "How does stock.lot.serialize relate to other models?", "response": "The stock.lot.serialize model has 4 relational fields: picking_id -> stock.picking; stock_move_line_ids -> stock.lot.serialize.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.lot.serialize", "table_name": ""}
+{"text": "What modules define purchase.tender.create.wizard?", "response": "The purchase.tender.create.wizard model is defined in module: equip3_purchase_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.tender.create.wizard", "table_name": ""}
+{"text": "What are common use cases for sh.quality.alert?", "response": "To use the sh.quality.alert model, you need to provide values for required fields: product_id, user_id, team_id. Readonly fields: name, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sh.quality.alert", "table_name": ""}
+{"text": "How to query report.accounting_pdf_reports.report_tax data?", "response": "To use the report.accounting_pdf_reports.report_tax model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.accounting_pdf_reports.report_tax", "table_name": ""}
+{"text": "How to create records in expiry.picking.confirmation?", "response": "To use the expiry.picking.confirmation model, you need to provide values for required fields: lot_ids. Readonly fields: lot_ids, picking_ids, description, show_lots, production_ids, workorder_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "expiry.picking.confirmation", "table_name": ""}
+{"text": "What is the mailing.contact model?", "response": "The mailing.contact model represents Mailing Contact in the ERP system. It contains 34 fields and is used to manage mailing contact data. Key fields include: name, company_name, title_id, email, list_ids, subscription_list_ids, country_id, tag_ids, opt_out, email_normalized, is_blacklisted, message_bounce, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mailing.contact", "table_name": ""}
+{"text": "How is website used in the system?", "response": "The website model represents Website in the ERP system. It contains 64 fields and is used to manage website data. Key fields include: name, domain, country_group_ids, company_id, language_ids, default_lang_id, auto_redirect_lang, cookies_bar, logo, social_twitter, social_facebook, social_github, social_linkedin, social_youtube, social_instagram, social_default_image, has_social_default_image, google_analytics_key, google_management_client_id, google_management_client_secret, google_search_console, google_maps_api_key, user_id, cdn_activated, cdn_url, cdn_filters, partner_id, menu_id, homepage_id, custom_code_head, custom_code_footer, robots_txt, favicon, theme_id, specific_user_account, auth_signup_uninvited, channel_id, is_enable_vendor_notification, user_ids, is_enable_auto_portal_user, is_enable_company_portal_user, is_enable_company_contact_portal_user, crm_default_team_id, crm_default_user_id, karma_profile_min, pricelist_id, currency_id, salesperson_id, salesteam_id, pricelist_ids, all_pricelist_ids, cart_recovery_mail_template_id, cart_abandoned_delay, shop_ppg, shop_ppr, shop_extra_field_ids, warehouse_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "website", "table_name": ""}
+{"text": "List all fields in the combo.option model.", "response": "The combo.option model has 14 fields: combo_name, item_ids, image_1920, image_1024, image_512, image_256, image_128, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, one2many: 1, binary: 5, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "combo.option", "table_name": ""}
+{"text": "How is account.analytic.new implemented technically?", "response": "The account.analytic.new model is defined in module: equip3_accounting_analytical. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.analytic.new", "table_name": ""}
+{"text": "Describe the field structure of account.group.template.", "response": "The account.group.template model has 12 fields: parent_id, code_prefix_start, code_prefix_end, chart_template_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 4, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.group.template", "table_name": ""}
+{"text": "What models are connected to product.warehouse.cost.wizard?", "response": "The product.warehouse.cost.wizard model has 5 relational fields: product_id -> product.product; product_cost_line_ids -> product.warehouse.cost.wizard.line; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.warehouse.cost.wizard", "table_name": ""}
+{"text": "What business logic is in credit.limit.approval?", "response": "To use the credit.limit.approval model, you need to provide values for required fields: none. Readonly fields: sequence2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "credit.limit.approval", "table_name": ""}
+{"text": "How do I use the assembly.safety.stock.line model?", "response": "To use the assembly.safety.stock.line model, you need to provide values for required fields: stock_id, product_id, product_qty. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "assembly.safety.stock.line", "table_name": ""}
+{"text": "Which fields in res.config are computed?", "response": "The res.config model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "res.config", "table_name": ""}
+{"text": "Show me the fields of rn.matrix.reject.", "response": "The rn.matrix.reject model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "rn.matrix.reject", "table_name": ""}
+{"text": "How is export.retur.pajak.masukan implemented technically?", "response": "The export.retur.pajak.masukan model is defined in module: equip3_accounting_efaktur. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "export.retur.pajak.masukan", "table_name": ""}
+{"text": "Describe the field structure of report.membership.", "response": "The report.membership model has 17 fields: start_date, date_to, num_waiting, num_invoiced, num_paid, tot_pending, tot_earned, partner_id, associate_member_id, membership_id, membership_state, user_id, company_id, quantity, id, display_name, __last_update. Field types distribution: date: 2, integer: 5, float: 2, many2one: 5, selection: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.membership", "table_name": ""}
+{"text": "How do I use the snailmail.letter.cancel model?", "response": "To use the snailmail.letter.cancel model, you need to provide values for required fields: none. Readonly fields: help_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "snailmail.letter.cancel", "table_name": ""}
+{"text": "What foreign keys exist in assign.pr.wizard?", "response": "The assign.pr.wizard model has 4 relational fields: pr_ids -> purchase.request.line; line_ids -> assign.pr.line.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: pr_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "assign.pr.wizard", "table_name": ""}
+{"text": "How is gamification.challenge implemented technically?", "response": "The gamification.challenge model is defined in module: gamification. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "gamification.challenge", "table_name": ""}
+{"text": "What business logic is in meetings.salespersons?", "response": "To use the meetings.salespersons 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "meetings.salespersons", "table_name": ""}
+{"text": "Show me the fields of product.cross.", "response": "The product.cross model has 13 fields: product_tmpl_id, product_id, list_price, quantity, discount_type, discount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, float: 3, selection: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.cross", "table_name": ""}
+{"text": "Which fields in approval.matrix.purchase.order are computed?", "response": "The approval.matrix.purchase.order model is defined in module: equip3_purchase_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "approval.matrix.purchase.order", "table_name": ""}
+{"text": "Describe the many2many relations for report.excel.section.", "response": "The report.excel.section model has 9 relational fields: report_excel_id -> report.excel; parent_id -> report.excel.section; children_ids -> report.excel.section; report_excel_fields_ids -> report.excel.fields; root_model_related_field_id -> ir.model.fields; root_model_id -> ir.model; report_excel_fields_sql_ids -> report.excel.fields.sql; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.excel.section", "table_name": ""}
+{"text": "What are common use cases for snailmail.letter.cancel?", "response": "To use the snailmail.letter.cancel model, you need to provide values for required fields: none. Readonly fields: help_message, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "snailmail.letter.cancel", "table_name": ""}
+{"text": "Describe the many2many relations for report.sh_sale_reports.sh_sale_product_indent_doc.", "response": "The report.sh_sale_reports.sh_sale_product_indent_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_sale_product_indent_doc", "table_name": ""}
+{"text": "How to create records in fetchmail.server?", "response": "To use the fetchmail.server model, you need to provide values for required fields: name, server_type. Readonly fields: state, server, port, date, user, password, priority, message_ids, configuration, script, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "fetchmail.server", "table_name": ""}
+{"text": "How does sh.purchase.category.wizard relate to other models?", "response": "The sh.purchase.category.wizard model has 5 relational fields: sh_category_ids -> product.category; company_ids -> res.company; branch_ids -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_category_ids, company_ids, branch_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.category.wizard", "table_name": ""}
+{"text": "Describe the pos.order.location model in Odoo.", "response": "The pos.order.location model represents POS Order Locaton in the ERP system. It contains 7 fields and is used to manage pos order locaton data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.order.location", "table_name": ""}
+{"text": "How to create records in purchase.change.request.wizard?", "response": "To use the purchase.change.request.wizard model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.change.request.wizard", "table_name": ""}
+{"text": "How do I use the pos.gift.card.recharge model?", "response": "To use the pos.gift.card.recharge model, you need to provide values for required fields: none. Readonly fields: card_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.gift.card.recharge", "table_name": ""}
+{"text": "What models are connected to do.matrix.reject?", "response": "The do.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "do.matrix.reject", "table_name": ""}
+{"text": "What are the technical details of sh.purchase.report.representative.wizard?", "response": "The sh.purchase.report.representative.wizard model is defined in module: sh_purchase_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.purchase.report.representative.wizard", "table_name": ""}
+{"text": "Describe the mr.approval.matrix.line model in Odoo.", "response": "The mr.approval.matrix.line model represents Material Approval Matrix Line in the ERP system. It contains 34 fields and is used to manage material approval matrix line data. Key fields include: sequence, user_ids, minimum_approver, mr_approval_matrix, approved_users, state_char, time_stamp, feedback, last_approved, approved, sequence2, mr_matrix_id, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mr.approval.matrix.line", "table_name": ""}
+{"text": "How to create records in mass.editing.line?", "response": "To use the mass.editing.line model, you need to provide values for required fields: server_action_id, field_id. Readonly fields: model_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mass.editing.line", "table_name": ""}
+{"text": "What foreign keys exist in quality.check.report?", "response": "The quality.check.report model has 3 relational fields: product_ids -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "quality.check.report", "table_name": ""}
+{"text": "What does the crm.lead.type model represent?", "response": "The crm.lead.type model represents Crm Lead Type in the ERP system. It contains 8 fields and is used to manage crm lead type data. Key fields include: description, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "crm.lead.type", "table_name": ""}
+{"text": "Which fields in product.warranty are computed?", "response": "The product.warranty model is defined in module: bi_warranty_registration. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "product.warranty", "table_name": ""}
+{"text": "What business logic is in sale.adv.wizard.product.line.specific?", "response": "To use the sale.adv.wizard.product.line.specific model, you need to provide values for required fields: none. Readonly fields: default_code, standard_price, uom_po_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sale.adv.wizard.product.line.specific", "table_name": ""}
+{"text": "What operations can I perform on hr.employee.category?", "response": "To use the hr.employee.category 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "hr.employee.category", "table_name": ""}
+{"text": "How is sh.notification.logger used in the system?", "response": "The sh.notification.logger model represents It keeps updated about the notification being sent in the ERP system. It contains 12 fields and is used to manage it keeps updated about the notification being sent data. Key fields include: name, error, datetime, base_config_id, status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.notification.logger", "table_name": ""}
+{"text": "What operations can I perform on crm.lead?", "response": "To use the crm.lead model, you need to provide values for required fields: type, name, branch_id. Readonly fields: user_email, user_login, kanban_state, activity_date_deadline_my, prorated_revenue, recurring_revenue_monthly, recurring_revenue_monthly_prorated, company_currency, date_closed, date_action_last, date_open, date_last_stage_update, date_conversion, partner_is_blacklisted, phone_state, email_state, automated_probability, is_automated_probability, meeting_count, ribbon_message, phonecall_count, visitor_page_count, visitor_sessions_count, sale_amount_total, sale_order_count, one_metting, is_due_date, multiple_metting, einstein_score, einstein_score_text, automated_probability_new, dummy_boolean, one_metting_int, multiple_metting_int, activity_count, only_one_meeting, quotation_count, is_similar, similar_leads_count, day_open, day_close, tag, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, email_normalized, is_blacklisted, 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, phone_sanitized, phone_sanitized_blacklisted, phone_blacklisted, mobile_blacklisted, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "crm.lead", "table_name": ""}
+{"text": "What are the technical details of sale.advance.payment.inv?", "response": "The sale.advance.payment.inv model is defined in module: sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.advance.payment.inv", "table_name": ""}
+{"text": "What does the queue.job model represent?", "response": "The queue.job model represents Queue Job in the ERP system. It contains 63 fields and is used to manage queue job data. Key fields include: uuid, graph_uuid, user_id, company_id, name, model_name, method_name, record_ids, records, dependencies, dependency_graph, graph_jobs_count, args, kwargs, func_string, state, priority, exc_name, exc_message, exc_info, result, date_created, date_started, date_enqueued, date_done, exec_time, date_cancelled, eta, retry, max_retries, channel_method_name, job_function_id, channel, identity_key, worker_pid, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "queue.job", "table_name": ""}
+{"text": "What modules define whatsapp.template.message?", "response": "The whatsapp.template.message model is defined in module: equip3_accounting_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "whatsapp.template.message", "table_name": ""}
+{"text": "How does efaktur.export relate to other models?", "response": "The efaktur.export model has 4 relational fields: partner_id -> res.partner; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "efaktur.export", "table_name": ""}
+{"text": "What is the ir.actions.act_window.view model?", "response": "The ir.actions.act_window.view model represents Action Window View in the ERP system. It contains 12 fields and is used to manage action window view data. Key fields include: sequence, view_id, act_window_id, multi, view_mode, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.actions.act_window.view", "table_name": ""}
+{"text": "List all fields in the im_livechat.report.channel model.", "response": "The im_livechat.report.channel model has 25 fields: uuid, channel_id, channel_name, technical_name, livechat_channel_id, start_date, start_hour, day_number, time_to_answer, start_date_hour, duration, nbr_speaker, nbr_message, is_without_answer, days_of_activity, is_anonymous, country_id, is_happy, rating, rating_text, is_unrated, partner_id, id, display_name, __last_update. Field types distribution: char: 8, many2one: 4, datetime: 2, float: 2, integer: 9.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "im_livechat.report.channel", "table_name": ""}
+{"text": "What are the technical details of sparse_fields.test?", "response": "The sparse_fields.test model is defined in module: base_sparse_field. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sparse_fields.test", "table_name": ""}
+{"text": "Can you explain the purpose of pos.gift.card?", "response": "The pos.gift.card model represents Used to Create Gift card. in the ERP system. It contains 17 fields and is used to manage used to create gift card. data. Key fields include: card_no, card_value, card_type, customer_id, issue_date, expire_date, is_active, Paid, used_line, recharge_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.gift.card", "table_name": ""}
+{"text": "How does sh.model.fields.purchase.order.selection relate to other models?", "response": "The sh.model.fields.purchase.order.selection model has 3 relational fields: sh_field_po_id -> sh.custom.model.purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.model.fields.purchase.order.selection", "table_name": ""}
+{"text": "How do I use the vendor.evaluation.rating model?", "response": "To use the vendor.evaluation.rating model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "vendor.evaluation.rating", "table_name": ""}
+{"text": "What are the relationships in warranty.claim.category?", "response": "The warranty.claim.category model has 3 relational fields: team_id -> crm.team; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "warranty.claim.category", "table_name": ""}
+{"text": "Can you explain the purpose of report.accounting_pdf_reports.report_trialbalance?", "response": "The report.accounting_pdf_reports.report_trialbalance model represents Trial Balance Report in the ERP system. It contains 3 fields and is used to manage trial balance report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.accounting_pdf_reports.report_trialbalance", "table_name": ""}
+{"text": "What fields does sh.tsp.top.selling.product have?", "response": "The sh.tsp.top.selling.product model has 9 fields: product_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, float: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.tsp.top.selling.product", "table_name": ""}
+{"text": "Describe the purchase.order.line model in Odoo.", "response": "The purchase.order.line model represents Purchase Order Line in the ERP system. It contains 130 fields and is used to manage purchase order line data. Key fields include: name, product_qty, product_uom_qty, taxes_id, product_uom, product_uom_category_id, product_id, price_unit, price_tax, order_id, account_analytic_id, company_id, state, invoice_lines, qty_invoiced, qty_received, qty_received_manual, qty_to_invoice, currency_id, date_order, display_type, is_configurable_product, product_template_attribute_value_ids, product_no_variant_attribute_value_ids, qty_received_method, move_ids, orderpoint_id, move_dest_ids, product_description_variants, propagate_cancel, tick, status, agreement_id, cancel_lines, sh_tender_note, picking_type_id, purchase_request_lines, purchase_request_allocation_ids, sale_order_id, sale_line_id, discount_method, discount_type, discount_amount, discount_amt, branch_id, is_down_payment, purchase_req_budget, realized_amount, confirm_purchase_req_budget, confirm_realized_amount, confirm_budget_data, purchase_budget_lines, planned, is_vendor_pricelist_line, branch_ids, gross_total, price_unit_uom, available_product_ids, last_purchased_price, last_customer_purchase_price, destination_location_id, destination_warehouse_id, date_planned, delivery_ref, vendor_bills_ref, request_line_id, readonly_price, sequence, sequence2, avg_price, current_qty, incoming_stock, actual_progress, remaining_progress, progress_paid, date_received, reference_purchase_price, purchase_line_cost_saving, total_cost_saving, cost_saving_percentage, partner_id, price_subtotal, price_total, total_price, discounted_value, state_delivery, state_inv, multi_discount, product_type, virtual_available_at_date, scheduled_date, forecast_expected_date, free_qty_today, qty_available_today, qty_to_deliver, is_mto, display_qty_widget, route_id, analytic_tag_ids, bid, cost_saving, payment_term_id, base_price, update_base, lead_time, feedback, company_size, capital_revenue, base_quantity, product_template_id, purchase_order_id, is_goods_orders, is_services_orders, requisition_line_id, agreement_line_id, sh_product_description, dp_line, is_reward_line, price_reduce, is_assets_orders, barcode, merchendise_id, persentase_antar_badan, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order.line", "table_name": ""}
+{"text": "What data can be stored in mailing.mailing.test?", "response": "The mailing.mailing.test model has 9 fields: email_to, mass_mailing_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mailing.mailing.test", "table_name": ""}
+{"text": "How is resource.test implemented technically?", "response": "The resource.test model is defined in module: resource. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "resource.test", "table_name": ""}
+{"text": "How to query acrux.chat.connector data?", "response": "To use the acrux.chat.connector model, you need to provide values for required fields: name, sequence, company_id, endpoint, apikey, uuid, border_color, sale_report_id, connector_type, qc_channel. Readonly fields: qc_webhook_url, connection_status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "acrux.chat.connector", "table_name": ""}
+{"text": "What models are connected to pick.product.replenish?", "response": "The pick.product.replenish model has 4 relational fields: product_id -> product.product; product_tmpl_id -> product.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pick.product.replenish", "table_name": ""}
+{"text": "What are the technical details of cancel.credit.limit?", "response": "The cancel.credit.limit model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "cancel.credit.limit", "table_name": ""}
+{"text": "Describe the field structure of monthly.account.budget.", "response": "The monthly.account.budget model has 13 fields: account_plan_id, year, year_id, company_id, name, budget_account_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, integer: 2, many2one: 4, char: 2, one2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "monthly.account.budget", "table_name": ""}
+{"text": "Describe the implementation of sh.notification.logger.", "response": "The sh.notification.logger model is defined in module: sh_backmate_theme_adv. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.notification.logger", "table_name": ""}
+{"text": "List all fields in the stock.picking.batch.line model.", "response": "The stock.picking.batch.line model has 18 fields: sequence, transfer_id, product_id, name, location_id, demand_qty, reserved_qty, done_qty, uom_id, picking_batch_id, origin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2one: 7, char: 3, float: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.picking.batch.line", "table_name": ""}
+{"text": "What modules define crm.activity.report?", "response": "The crm.activity.report model is defined in module: crm. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "crm.activity.report", "table_name": ""}
+{"text": "What operations can I perform on pos.coupon.apply.code?", "response": "To use the pos.coupon.apply.code model, you need to provide values for required fields: coupon_code. Readonly fields: coupon_code, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.coupon.apply.code", "table_name": ""}
+{"text": "Describe the field structure of report.account.report_invoice.", "response": "The report.account.report_invoice model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.account.report_invoice", "table_name": ""}
+{"text": "What methods are available in account.analytic.distribution?", "response": "The account.analytic.distribution model is defined in module: analytic. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.analytic.distribution", "table_name": ""}
+{"text": "What business logic is in ai.data.cleanup?", "response": "To use the ai.data.cleanup model, you need to provide values for required fields: name. Readonly fields: next_run, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ai.data.cleanup", "table_name": ""}
+{"text": "Describe the field structure of hr.job.", "response": "The hr.job model has 33 fields: name, expected_employees, no_of_employee, no_of_recruitment, no_of_hired_employee, employee_ids, description, requirements, department_id, company_id, state, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 9, one2many: 4, text: 2, many2one: 5, selection: 1, boolean: 5, many2many: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "hr.job", "table_name": ""}
+{"text": "What is the queue.job.dashboard model?", "response": "The queue.job.dashboard model represents Queue Job Dashboard in the ERP system. It contains 3 fields and is used to manage queue job dashboard data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "queue.job.dashboard", "table_name": ""}
+{"text": "Tell me about the sh.fiscal.year model.", "response": "The sh.fiscal.year model represents Fiscal Year in the ERP system. It contains 18 fields and is used to manage fiscal year data. Key fields include: name, code, date_start, date_end, period_ids, state, company_id, branch_id, hide_button, move_id, summary_move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.fiscal.year", "table_name": ""}
+{"text": "What are the available fields for report.equip3_pos_report.report_closed_session?", "response": "The report.equip3_pos_report.report_closed_session model has 3 fields: id, display_name, __last_update. Field types distribution: integer: 1, char: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "report.equip3_pos_report.report_closed_session", "table_name": ""}
+{"text": "What business logic is in cluster.area?", "response": "To use the cluster.area model, you need to provide values for required fields: name, warehouse_id, company_id. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cluster.area", "table_name": ""}
+{"text": "What does the fetchmail.server model represent?", "response": "The fetchmail.server model represents Incoming Mail Server in the ERP system. It contains 24 fields and is used to manage incoming mail server data. Key fields include: name, active, state, server, port, server_type, is_ssl, attach, original, date, user, password, object_id, priority, message_ids, configuration, script, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "fetchmail.server", "table_name": ""}
+{"text": "List all fields in the stock.valuation.layer model.", "response": "The stock.valuation.layer model has 33 fields: company_id, product_id, categ_id, product_tmpl_id, quantity, uom_id, currency_id, unit_cost, value, remaining_qty, remaining_value, description, stock_valuation_layer_id, stock_valuation_layer_ids, stock_move_id, account_move_id, stock_landed_cost_id, secondary_uom, qty_of_secondary_uom, date, warehouse_id, location_id, new_warehouse_id, new_location_id, new_inventory_id, move_internal_type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 18, float: 3, monetary: 3, char: 2, one2many: 1, datetime: 4, selection: 1, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "stock.valuation.layer", "table_name": ""}
+{"text": "What data can be stored in base_import.tests.models.char.states?", "response": "The base_import.tests.models.char.states model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.char.states", "table_name": ""}
+{"text": "What operations can I perform on report.dynamic_accounts_report.partner_ledger?", "response": "To use the report.dynamic_accounts_report.partner_ledger model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.dynamic_accounts_report.partner_ledger", "table_name": ""}
+{"text": "How does asset.cip relate to other models?", "response": "The asset.cip model has 8 relational fields: asset_category -> account.asset.category; cip_account -> account.account; lines -> asset.cip.line; currency -> res.currency; move_id -> account.move; branch_id -> res.branch; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "asset.cip", "table_name": ""}
+{"text": "Describe the field structure of pos.zone.", "response": "The pos.zone model has 9 fields: name, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.zone", "table_name": ""}
+{"text": "Describe the implementation of account.tour.upload.bill.", "response": "The account.tour.upload.bill model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.tour.upload.bill", "table_name": ""}
+{"text": "What modules define assets.approval.reject?", "response": "The assets.approval.reject model is defined in module: equip3_accounting_asset. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "assets.approval.reject", "table_name": ""}
+{"text": "What foreign keys exist in crm.lead.salesperson.lines?", "response": "The crm.lead.salesperson.lines model has 4 relational fields: salesperson_id -> res.users; lead_id -> crm.lead; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.lead.salesperson.lines", "table_name": ""}
+{"text": "Describe the many2many relations for res.partner.", "response": "The res.partner model has 97 relational fields: title -> res.partner.title; parent_id -> res.partner; child_ids -> res.partner; same_vat_partner_id -> res.partner; bank_ids -> res.partner.bank; category_id -> res.partner.category; state_id -> res.country.state; country_id -> res.country; industry_id -> res.partner.industry; user_ids -> res.users; commercial_partner_id -> res.partner; self -> res.partner; channel_ids -> mail.channel; user_id -> res.users; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; currency_id -> res.currency; property_account_position_id -> account.fiscal.position; property_payment_term_id -> account.payment.term; property_supplier_payment_term_id -> account.payment.term; ref_company_ids -> res.company; invoice_ids -> account.move; contract_ids -> account.analytic.account; team_id -> crm.team; opportunity_ids -> crm.lead; meeting_ids -> calendar.event; task_ids -> project.task; property_stock_customer -> stock.location; property_stock_supplier -> stock.location; website_id -> website; visitor_ids -> website.visitor; property_payment_method_id -> account.payment.method; phonecall_ids -> crm.phonecall; associate_member -> res.partner; member_lines -> membership.membership_line; payment_token_ids -> payment.token; property_purchase_currency_id -> res.currency; purchase_line_ids -> purchase.order.line; sale_order_ids -> sale.order; vendor_product_categ_ids -> product.category; last_website_so_id -> sale.order; contact_ids -> acrux.chat.conversation; related_company_id -> res.company; property_delivery_carrier_id -> delivery.carrier; report_template_id1 -> ir.actions.report; report_template_id -> ir.actions.report; report_sale_template_id1 -> ir.actions.report; report_sale_template_id -> ir.actions.report; report_po_template_id1 -> ir.actions.report; report_po_template_id -> ir.actions.report; report_rfq_template_id -> ir.actions.report; report_delivery_template_id1 -> ir.actions.report; report_delivery_template_id -> ir.actions.report; report_picking_template_id -> ir.actions.report; rfm_segment_id -> setu.rfm.segment; rfm_score_id -> setu.rfm.score; partner_segment_history_ids -> res.partner.rfm.segment.history; loyalty_history_ids -> all.loyalty.history; interest_vendor_account_payable -> account.account; interest_customer_account_receivable -> account.account; debtor_id -> customer.degree.trust; customer_category -> customer.category; property_product_pricelist -> product.pricelist; res_city_id -> res.country.city; city_id -> res.city; preferred_location -> stock.location; approved_user_ids -> res.users; branch_id -> res.branch; approving_matrix_vendor_id -> approval.matrix.vendor; approved_matrix_ids -> approval.matrix.vendor.line; approval_matrix_line_id -> approval.matrix.vendor.line; request_partner_id -> res.partner; blacklist_history_ids -> partner.blacklist.history; report_pr_template_id -> ir.actions.report; product_brand_ids -> credit.limit.product.brand; filter_brand_ids -> product.brand; discount_id -> pos.global.discount; group_ids -> res.partner.group; pos_order_ids -> pos.order; pos_partner_type_id -> res.partner.type; pos_branch_id -> res.branch; customer_target_id -> customer.target; customer_voucher_ids -> customer.voucher; pos_loyalty_type -> pos.loyalty.category; pos_loyalty_point_ids -> pos.loyalty.point; property_account_payable_id -> account.account; property_account_receivable_id -> account.account; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: category_id, channel_ids, message_partner_ids, message_channel_ids, meeting_ids, vendor_product_categ_ids, approved_user_ids, filter_brand_ids, group_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.partner", "table_name": ""}
+{"text": "How is approval.matrix.vendor used in the system?", "response": "The approval.matrix.vendor model represents Approval Matrix Vendor in the ERP system. It contains 11 fields and is used to manage approval matrix vendor data. Key fields include: name, company_id, branch_id, approval_matrix_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "approval.matrix.vendor", "table_name": ""}
+{"text": "Show me the fields of rn.approval_matrix_line.", "response": "The rn.approval_matrix_line model has 20 fields: sequence, sequence1, approver, minimal_approver, approval_status, feedback, time_stamp, last_approved, approved, rn_approval_matrix_id1, picking_id, approved_users, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 4, many2many: 2, text: 2, char: 2, datetime: 4, many2one: 5, boolean: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "rn.approval_matrix_line", "table_name": ""}
+{"text": "What does the budget.change.req.line model represent?", "response": "The budget.change.req.line model represents Budget Change Request Line in the ERP system. It contains 11 fields and is used to manage budget change request line data. Key fields include: budget_change_req_id, budgetary_position_id, planned_amount, new_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "budget.change.req.line", "table_name": ""}
+{"text": "What models are connected to res.partner.bank?", "response": "The res.partner.bank model has 7 relational fields: partner_id -> res.partner; bank_id -> res.bank; currency_id -> res.currency; company_id -> res.company; journal_id -> account.journal; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "res.partner.bank", "table_name": ""}
+{"text": "How to query lost.product data?", "response": "To use the lost.product 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "lost.product", "table_name": ""}
+{"text": "Describe the field structure of phone.blacklist.", "response": "The phone.blacklist model has 24 fields: number, active, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, boolean: 6, one2many: 3, many2many: 2, integer: 5, many2one: 3, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "phone.blacklist", "table_name": ""}
+{"text": "What modules define sh.mrp.quality.check?", "response": "The sh.mrp.quality.check model is defined in module: sh_inventory_mrp_qc. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sh.mrp.quality.check", "table_name": ""}
+{"text": "What are the relationships in resource.test?", "response": "The resource.test model has 5 relational fields: resource_id -> resource.resource; company_id -> res.company; resource_calendar_id -> resource.calendar; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "resource.test", "table_name": ""}
+{"text": "Can you explain the purpose of purchase.order.line.extract?", "response": "The purchase.order.line.extract model represents Purchase Order Line Extract in the ERP system. It contains 18 fields and is used to manage purchase order line extract data. Key fields include: sequence, tick, product_template_id, name, date_planned, product_qty, price_unit, destination_warehouse_id, extract_id, product_id, product_uom, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "purchase.order.line.extract", "table_name": ""}
+{"text": "What does the pos.gift.card model represent?", "response": "The pos.gift.card model represents Used to Create Gift card. in the ERP system. It contains 17 fields and is used to manage used to create gift card. data. Key fields include: card_no, card_value, card_type, customer_id, issue_date, expire_date, is_active, Paid, used_line, recharge_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.gift.card", "table_name": ""}
+{"text": "What data can be stored in sh.purchase.tags?", "response": "The sh.purchase.tags model has 9 fields: name, color, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 2, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sh.purchase.tags", "table_name": ""}
+{"text": "What foreign keys exist in ir.actions.act_window?", "response": "The ir.actions.act_window model has 7 relational fields: view_id -> ir.ui.view; view_ids -> ir.actions.act_window.view; groups_id -> res.groups; search_view_id -> ir.ui.view; binding_model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: groups_id.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ir.actions.act_window", "table_name": ""}
+{"text": "Describe the field structure of account.account.type.", "response": "The account.account.type model has 39 fields: name, include_initial_balance, type, internal_group, note, company_id, branch_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, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 5, boolean: 6, selection: 4, text: 1, many2one: 7, one2many: 4, date: 2, many2many: 2, integer: 5, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.account.type", "table_name": ""}
+{"text": "Show me the fields of generate.pos.voucher.wizard.", "response": "The generate.pos.voucher.wizard model has 9 fields: no_of_voucher, amount_of_usage, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 3, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "generate.pos.voucher.wizard", "table_name": ""}
+{"text": "What fields does account.efaktur have?", "response": "The account.efaktur model has 19 fields: year, record_id, invoice_id, partner_id, invoice_date, company_id, is_pjap, is_used_pjap, branch_id, is_cancel, is_used, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, integer: 2, one2many: 1, date: 1, boolean: 4, char: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.efaktur", "table_name": ""}
+{"text": "Tell me about the internal.transfer.line model.", "response": "The internal.transfer.line model represents Internal Transfer Line in the ERP system. It contains 34 fields and is used to manage internal transfer line data. Key fields include: qty_cancel, product_line, product_id, qty, uom, source_location_id, destination_location_id, transfer_qty, return_qty, total_trf, scheduled_date, filter_source_loc, filter_dest_loc, current_qty, filter_available_product_ids, analytic_account_group_ids, status, description, mr_line_id, source_document, requested_by, company_id, picking_id, itr_in_progress_qty, itr_remaining_qty, sequence, current_dest_qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "internal.transfer.line", "table_name": ""}
+{"text": "Which fields in change.password.wizard are computed?", "response": "The change.password.wizard model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "change.password.wizard", "table_name": ""}
+{"text": "How is ks.message.wizard implemented technically?", "response": "The ks.message.wizard model is defined in module: ks_sales_forecast. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ks.message.wizard", "table_name": ""}
+{"text": "What methods are available in project.task.type?", "response": "The project.task.type model is defined in module: project. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "project.task.type", "table_name": ""}
+{"text": "What are the technical details of budget.change.req?", "response": "The budget.change.req model is defined in module: equip3_accounting_budget. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "budget.change.req", "table_name": ""}
+{"text": "What are the available fields for account.fiscal.position.account?", "response": "The account.fiscal.position.account model has 11 fields: position_id, company_id, account_src_id, account_dest_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 6, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.fiscal.position.account", "table_name": ""}
+{"text": "What are common use cases for pos.qrcode?", "response": "To use the pos.qrcode model, you need to provide values for required fields: name, field_id, config_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.qrcode", "table_name": ""}
+{"text": "Describe the asset.asset.revalue model in Odoo.", "response": "The asset.asset.revalue model represents Asset Revaluation in the ERP system. It contains 22 fields and is used to manage asset revaluation data. Key fields include: reason, asset_id, remaining_value, amount, journal_id, method_number, method_period, user_id, date, prev_method_number, prev_method_period, dispose_price, company_id, company_currency_id, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "asset.asset.revalue", "table_name": ""}
+{"text": "What fields does ir.model.fields.selection have?", "response": "The ir.model.fields.selection model has 11 fields: field_id, value, name, sequence, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "ir.model.fields.selection", "table_name": ""}
+{"text": "What operations can I perform on pos.tag?", "response": "To use the pos.tag 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.tag", "table_name": ""}
+{"text": "What is the account.reconciliation.widget model?", "response": "The account.reconciliation.widget model represents Account Reconciliation widget in the ERP system. It contains 3 fields and is used to manage account reconciliation widget data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.reconciliation.widget", "table_name": ""}
+{"text": "What fields does product.pricelist have?", "response": "The product.pricelist model has 25 fields: name, active, item_ids, currency_id, sequence, country_group_ids, discount_policy, website_id, code, selectable, pricelist_history_ids, from_date, to_date, customer_category, company_id, barcode, is_external_link, pos_config_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 4, boolean: 3, one2many: 2, many2one: 6, integer: 2, many2many: 2, selection: 1, datetime: 5.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "product.pricelist", "table_name": ""}
+{"text": "Describe the field structure of journal.payment.report.", "response": "The journal.payment.report model has 10 fields: name, total, report_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, float: 1, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "journal.payment.report", "table_name": ""}
+{"text": "What does the mrp.bom.byproduct model represent?", "response": "The mrp.bom.byproduct model represents Byproduct in the ERP system. It contains 20 fields and is used to manage byproduct data. Key fields include: product_id, company_id, product_qty, product_uom_id, bom_id, allowed_operation_ids, operation_id, allocated_cost, cost, operation_two_ids, operation_two_id, assembly_allocated_cost, kitchen_allocated_cost, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.bom.byproduct", "table_name": ""}
+{"text": "What are common use cases for return.inter.transfer.company.line?", "response": "To use the return.inter.transfer.company.line model, you need to provide values for required fields: none. Readonly fields: price_unit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "return.inter.transfer.company.line", "table_name": ""}
+{"text": "What modules define internal.transfer.line?", "response": "The internal.transfer.line model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "internal.transfer.line", "table_name": ""}
+{"text": "How does whatsapp.template.message.variable relate to other models?", "response": "The whatsapp.template.message.variable model has 3 relational fields: wa_id -> whatsapp.template.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "whatsapp.template.message.variable", "table_name": ""}
+{"text": "How is mrp.consumption.warning used in the system?", "response": "The mrp.consumption.warning model represents Wizard in case of consumption in warning/strict and more component has been used for a MO (related to the bom) in the ERP system. It contains 11 fields and is used to manage wizard in case of consumption in warning/strict and more component has been used for a mo (related to the bom) data. Key fields include: mrp_production_ids, mrp_production_count, consumption, mrp_consumption_warning_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "mrp.consumption.warning", "table_name": ""}
+{"text": "What fields does account.keterangan.tambahan have?", "response": "The account.keterangan.tambahan model has 10 fields: angka, name, jenis_transaksi, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, text: 1, selection: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.keterangan.tambahan", "table_name": ""}
+{"text": "Can you explain the purpose of pos.report.category?", "response": "The pos.report.category model represents POS Report Category in the ERP system. It contains 7 fields and is used to manage pos report category data. Key fields include: id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.report.category", "table_name": ""}
+{"text": "What models are connected to account.cashbox.wizard.line?", "response": "The account.cashbox.wizard.line model has 7 relational fields: account_cashbox_wizard_id -> account.cashbox.wizard; cashbox_id -> account.bank.statement.cashbox; currency_id -> res.currency; pos_config_id -> pos.config; pos_session_id -> pos.session; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.cashbox.wizard.line", "table_name": ""}
+{"text": "How is reject.picking.order used in the system?", "response": "The reject.picking.order model represents reject.picking.order in the ERP system. It contains 12 fields and is used to manage reject.picking.order data. Key fields include: driver_id, picking_id, assign_date, reject_date, reject_reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "reject.picking.order", "table_name": ""}
+{"text": "What foreign keys exist in opening.balance?", "response": "The opening.balance model has 6 relational fields: company_id -> res.company; journal_id -> account.journal; partner_id -> res.partner; line_ids -> opening.balance.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "opening.balance", "table_name": ""}
+{"text": "How does pos.promotion.discount.apply relate to other models?", "response": "The pos.promotion.discount.apply model has 4 relational fields: product_id -> product.product; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.promotion.discount.apply", "table_name": ""}
+{"text": "What are the available fields for account.aged.trial.balance?", "response": "The account.aged.trial.balance model has 15 fields: period_length, journal_ids, date_from, result_selection, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: integer: 2, many2many: 1, date: 2, selection: 2, many2one: 4, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.aged.trial.balance", "table_name": ""}
+{"text": "Describe the many2many relations for purchase.line.wiz.", "response": "The purchase.line.wiz model has 3 relational fields: purchase_order_line_id -> purchase.order.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "purchase.line.wiz", "table_name": ""}
+{"text": "What are the relationships in create.purchase.request.direct?", "response": "The create.purchase.request.direct model has 6 relational fields: supplier_id -> res.partner; item_ids -> create.purchase.request.direct.lines; journal_id -> account.journal; purchase_order_id -> purchase.order; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "create.purchase.request.direct", "table_name": ""}
+{"text": "Can you explain the purpose of ir.cron?", "response": "The ir.cron model represents Scheduled Actions in the ERP system. It contains 56 fields and is used to manage scheduled actions data. Key fields include: ir_actions_server_id, cron_name, user_id, active, interval_number, interval_type, numbercall, doall, nextcall, lastcall, priority, id, display_name, create_uid, create_date, write_uid, write_date, __last_update, name, type, sequence, model_id, model_name, code, child_ids, crud_model_id, crud_model_name, link_field_id, fields_lines, groups_id, mass_edit_line_ids, mass_edit_apply_domain_in_lines, mass_edit_message, partner_ids, channel_ids, template_id, activity_type_id, activity_summary, activity_note, activity_date_deadline_range, activity_date_deadline_range_type, activity_user_type, activity_user_id, activity_user_field_name, usage, state, sms_template_id, sms_mass_keep_log, xml_id, website_path, website_url, website_published, help, binding_model_id, binding_type, binding_view_types.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ir.cron", "table_name": ""}
+{"text": "What foreign keys exist in ms.query?", "response": "The ms.query model has 8 relational fields: message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "ms.query", "table_name": ""}
+{"text": "What operations can I perform on cancel.tender.memory?", "response": "To use the cancel.tender.memory model, you need to provide values for required fields: tender_id, reason. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cancel.tender.memory", "table_name": ""}
+{"text": "What data can be stored in list.order?", "response": "The list.order model has 28 fields: order_dic_id, order_number, order_date, total, due_amount, cust_dic_id, invoice_number, invoice_date, invoice_currency_id, salesperson, sale_currency_id, sale_amount, paid_amount, balance_amount, product, customer, qty, cost, sale_price, profit, margin, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 6, datetime: 5, float: 10, integer: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "list.order", "table_name": ""}
+{"text": "What models are connected to bve.view?", "response": "The bve.view model has 9 relational fields: line_ids -> bve.view.line; field_ids -> bve.view.line; relation_ids -> bve.view.line; action_id -> ir.actions.act_window; view_id -> ir.ui.view; group_ids -> res.groups; user_ids -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: group_ids, user_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "bve.view", "table_name": ""}
+{"text": "Show me the relational structure of stock.return.picking.", "response": "The stock.return.picking model has 10 relational fields: picking_id -> stock.picking; product_return_moves -> stock.return.picking.line; original_location_id -> stock.location; parent_location_id -> stock.location; company_id -> res.company; location_id -> stock.location; return_reason -> return.reason; return_line_ids -> stock.return.move.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.return.picking", "table_name": ""}
+{"text": "Which fields in tax.sale.details.report are computed?", "response": "The tax.sale.details.report model is defined in module: equip3_sale_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "tax.sale.details.report", "table_name": ""}
+{"text": "How is warranty.claim.category implemented technically?", "response": "The warranty.claim.category model is defined in module: bi_warranty_registration. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "warranty.claim.category", "table_name": ""}
+{"text": "What models are connected to hide.chatter?", "response": "The hide.chatter model has 4 relational fields: access_management_id -> access.management; model_id -> ir.model; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "hide.chatter", "table_name": ""}
+{"text": "What are the relationships in stock.valuation.adjustment.lines?", "response": "The stock.valuation.adjustment.lines model has 7 relational fields: cost_id -> stock.landed.cost; cost_line_id -> stock.landed.cost.lines; move_id -> stock.move; product_id -> product.product; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.valuation.adjustment.lines", "table_name": ""}
+{"text": "How do I use the mr.internal_transfer model?", "response": "To use the mr.internal_transfer 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "mr.internal_transfer", "table_name": ""}
+{"text": "Describe the many2many relations for report.excel.fields.sql.", "response": "The report.excel.fields.sql model has 3 relational fields: report_excel_section_id -> report.excel.section; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.excel.fields.sql", "table_name": ""}
+{"text": "What models are connected to account.tax.template?", "response": "The account.tax.template model has 8 relational fields: chart_template_id -> account.chart.template; children_tax_ids -> account.tax.template; invoice_repartition_line_ids -> account.tax.repartition.line.template; refund_repartition_line_ids -> account.tax.repartition.line.template; tax_group_id -> account.tax.group; cash_basis_transition_account_id -> account.account.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: children_tax_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.tax.template", "table_name": ""}
+{"text": "Describe the product.uom.price model in Odoo.", "response": "The product.uom.price model represents Management product price each unit in the ERP system. It contains 9 fields and is used to manage management product price each unit data. Key fields include: uom_id, product_tmpl_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "product.uom.price", "table_name": ""}
+{"text": "What operations can I perform on procurement.group?", "response": "To use the procurement.group model, you need to provide values for required fields: name, move_type. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "procurement.group", "table_name": ""}
+{"text": "Which fields in ir.qweb.field.image are computed?", "response": "The ir.qweb.field.image model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.qweb.field.image", "table_name": ""}
+{"text": "Describe the implementation of mrp.unbuild.", "response": "The mrp.unbuild model is defined in module: mrp. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "mrp.unbuild", "table_name": ""}
+{"text": "What modules define stock.day.average?", "response": "The stock.day.average model is defined in module: equip3_inventory_control. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.day.average", "table_name": ""}
+{"text": "Describe the sale.order.cancel model in Odoo.", "response": "The sale.order.cancel model represents Sales Order Cancel in the ERP system. It contains 10 fields and is used to manage sales order cancel data. Key fields include: order_id, display_invoice_alert, display_delivery_alert, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.order.cancel", "table_name": ""}
+{"text": "What fields does whatsapp.message.wizard have?", "response": "The whatsapp.message.wizard model has 16 fields: user_id, mobile_number, message, model, template_id, message_send, attachment_ids, crm_lead, company_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 4, text: 1, boolean: 2, many2many: 1, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "whatsapp.message.wizard", "table_name": ""}
+{"text": "What operations can I perform on product.expiry.config?", "response": "To use the product.expiry.config model, you need to provide values for required fields: none. Readonly fields: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "product.expiry.config", "table_name": ""}
+{"text": "What modules define report.dynamic_accounts_report.trial_balance?", "response": "The report.dynamic_accounts_report.trial_balance model is defined in module: dynamic_accounts_report. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.dynamic_accounts_report.trial_balance", "table_name": ""}
+{"text": "What are the available fields for qiscus.wa.template.content?", "response": "The qiscus.wa.template.content model has 13 fields: template_id, name, language, content_id, content, category, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, char: 3, integer: 2, text: 1, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "qiscus.wa.template.content", "table_name": ""}
+{"text": "What are common use cases for kpi.period.value?", "response": "To use the kpi.period.value model, you need to provide values for required fields: period_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "kpi.period.value", "table_name": ""}
+{"text": "How is account.debt.collection.line used in the system?", "response": "The account.debt.collection.line model represents Debt Collection Line in the ERP system. It contains 28 fields and is used to manage debt collection line data. Key fields include: debt_collection_id, invoice_id, invoice_date, currency_id, amount_invoice, amount_residual, state, journal_id, date, amount, is_full_collect, payment_id, is_pic_line, user_id, partner_id, deadline_date, invoice_due_date, total_due_date, debt_coll_pic, invoice_week_number, invoice_week_start, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.debt.collection.line", "table_name": ""}
+{"text": "Describe the field structure of list.top.product.", "response": "The list.top.product model has 10 fields: name, qty, top_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, float: 1, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "list.top.product", "table_name": ""}
+{"text": "Show me the fields of print.prenumbered.checks.", "response": "The print.prenumbered.checks model has 8 fields: next_check_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "print.prenumbered.checks", "table_name": ""}
+{"text": "What models are connected to crm.lead2opportunity.partner?", "response": "The crm.lead2opportunity.partner model has 7 relational fields: lead_id -> crm.lead; duplicated_lead_ids -> crm.lead; partner_id -> res.partner; user_id -> res.users; team_id -> crm.team; create_uid -> res.users; write_uid -> res.users. Many2many fields: duplicated_lead_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "crm.lead2opportunity.partner", "table_name": ""}
+{"text": "What data can be stored in mr.internal_transfer?", "response": "The mr.internal_transfer model has 9 fields: source_warehouse_id, ir_wizard_line, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, one2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mr.internal_transfer", "table_name": ""}
+{"text": "What are the available fields for store.filters.groups?", "response": "The store.filters.groups model has 11 fields: model_id, node_option, attribute_name, attribute_string, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, selection: 1, char: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "store.filters.groups", "table_name": ""}
+{"text": "How do I use the followup.invoice.tmp model?", "response": "To use the followup.invoice.tmp model, you need to provide values for required fields: none. Readonly fields: overdue_template, total_overdue, 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, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "followup.invoice.tmp", "table_name": ""}
+{"text": "How is decimal.precision used in the system?", "response": "The decimal.precision model represents Decimal Precision in the ERP system. It contains 9 fields and is used to manage decimal precision data. Key fields include: name, digits, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "decimal.precision", "table_name": ""}
+{"text": "How does account.day.book relate to other models?", "response": "The account.day.book model has 5 relational fields: company_id -> res.company; journal_ids -> account.journal; account_ids -> account.account; create_uid -> res.users; write_uid -> res.users. Many2many fields: journal_ids, account_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.day.book", "table_name": ""}
+{"text": "How does product.uom.price relate to other models?", "response": "The product.uom.price model has 4 relational fields: uom_id -> uom.uom; product_tmpl_id -> product.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "product.uom.price", "table_name": ""}
+{"text": "How to create records in purchase.order?", "response": "To use the purchase.order model, you need to provide values for required fields: picking_type_id, name, currency_id, company_id, branch_id, date_order, partner_invoice_id, partner_id. Readonly fields: date_approve, invoice_count, invoice_ids, invoice_status, date_calendar_start, currency_rate, mail_reminder_confirmed, mail_reception_confirmed, picking_count, picking_ids, default_location_dest_id_usage, is_shipped, effective_date, on_time_rate, complete_state, custom_checklist, purchase_show_signature, chk_sign_confirm, purchase_show_enable_other_sign, document_count, text_message, po_extract_id, po_split_id, po_extract_count, po_split_count, sh_fully_ship, sh_partially_ship, sh_fully_paid, sh_partially_paid, sh_hidden_compute_field, cancel_lines, sh_msg, po_count, sh_purchase_revision_config, visible_eval, mrp_production_count, sale_order_count, inter_transfer_count, discount_amt, discount_amt_line, sh_purchase_bm_is_cont_scan, sh_sale_order_id, total_invoices_amount, hide_create_bill, payment_status, down_payment_amount, total_down_payment_amount, report_template_id1, amount_to_text, is_vendor_pricelist, is_hold_purchase_order, approval_matrix_id, is_approval_matrix, state1, po_state, approved_matrix_ids, is_approve_button, approval_matrix_line_id, company_id, analytic_accounting, readonly_price, timezone_date, name2, is_group_good_services_order, have_product_service, swo_count, is_taxes, actual_progress, remaining_progress, progress_paid, available_partner_invoice_ids, is_product_brand_filter, is_service_work_order, is_purchase_vendor_rating_warning, is_product_service_operation_receiving, show_analytic_tags, amount_untaxed, amount_tax, amount_total, discount_amt_before, discount_amt_line_before, amount_subtotal, bo_count, multilevel_disc, vendor_invoice_documents_count, tender_scope, price_rating, is_btn_approval_matrix, state, is_blanket_cancel, days_to_approve, direct_approval_matrix_id, is_approval_matrix_direct, approved_matrix_direct_ids, approved_matrix_direct_id, state_direct_on, state_direct_off, is_approve_button_direct, client_order_ref, is_dropship, is_sale_order, customer_partner_id, customer_location_partner_id, branch_ids, persentase_antar_badan, form_view_opened, 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.order", "table_name": ""}
+{"text": "How is barcode.rule implemented technically?", "response": "The barcode.rule model is defined in module: barcodes. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "barcode.rule", "table_name": ""}
+{"text": "What modules define ir.actions.client?", "response": "The ir.actions.client model is defined in module: base. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "ir.actions.client", "table_name": ""}
+{"text": "How do I use the overhead.time model?", "response": "To use the overhead.time 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "overhead.time", "table_name": ""}
+{"text": "Describe the many2many relations for checklist.reason.", "response": "The checklist.reason model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "checklist.reason", "table_name": ""}
+{"text": "How to create records in advertisement.images?", "response": "To use the advertisement.images 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "advertisement.images", "table_name": ""}
+{"text": "Show me the relational structure of sh.purchase.bill.summary.xls.", "response": "The sh.purchase.bill.summary.xls model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.bill.summary.xls", "table_name": ""}
+{"text": "What are the available fields for pos.loyalty.category?", "response": "The pos.loyalty.category model has 20 fields: name, code, active, from_point, to_point, coefficient, member_card, card_template_barcode, card_template_qrcode, card_template_barcode_name, card_template_qrcode_name, member_card_preview, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 6, boolean: 1, float: 3, selection: 1, binary: 2, many2one: 3, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.loyalty.category", "table_name": ""}
+{"text": "What are the technical details of convert.revenue?", "response": "The convert.revenue model is defined in module: equip3_accounting_deposit. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "convert.revenue", "table_name": ""}
+{"text": "What models are connected to report.sh_sale_reports.sh_sale_product_indent_doc?", "response": "The report.sh_sale_reports.sh_sale_product_indent_doc model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_sale_product_indent_doc", "table_name": ""}
+{"text": "What fields does account.invoice.exchange.approval.wizard have?", "response": "The account.invoice.exchange.approval.wizard model has 8 fields: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.invoice.exchange.approval.wizard", "table_name": ""}
+{"text": "Which fields in warranty.claim.stage are computed?", "response": "The warranty.claim.stage model is defined in module: bi_warranty_registration. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "warranty.claim.stage", "table_name": ""}
+{"text": "What methods are available in hr.employee.base?", "response": "The hr.employee.base model is defined in module: hr. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "hr.employee.base", "table_name": ""}
+{"text": "What are the relationships in account.fiscal.position.account.template?", "response": "The account.fiscal.position.account.template model has 5 relational fields: position_id -> account.fiscal.position.template; account_src_id -> account.account.template; account_dest_id -> account.account.template; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "account.fiscal.position.account.template", "table_name": ""}
+{"text": "How to create records in invoice.template.table?", "response": "To use the invoice.template.table model, you need to provide values for required fields: template_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "invoice.template.table", "table_name": ""}
+{"text": "What fields does pos.loyalty.history.update.point have?", "response": "The pos.loyalty.history.update.point model has 12 fields: type_apply, total_orders, total_point, pos_order_ids, parent_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: selection: 1, float: 2, many2many: 1, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.loyalty.history.update.point", "table_name": ""}
+{"text": "How does meetings.salespersons relate to other models?", "response": "The meetings.salespersons model has 4 relational fields: salesperson_id -> res.users; calendar_event_id -> calendar.event; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "meetings.salespersons", "table_name": ""}
+{"text": "What fields does procurement.group have?", "response": "The procurement.group model has 13 fields: partner_id, name, move_type, stock_move_ids, mrp_production_ids, sale_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 4, char: 2, selection: 1, one2many: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "procurement.group", "table_name": ""}
+{"text": "Describe the implementation of allfresh.consignment.report.", "response": "The allfresh.consignment.report model is defined in module: allfresh_mod_consignment. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "allfresh.consignment.report", "table_name": ""}
+{"text": "What foreign keys exist in resource.test?", "response": "The resource.test model has 5 relational fields: resource_id -> resource.resource; company_id -> res.company; resource_calendar_id -> resource.calendar; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "resource.test", "table_name": ""}
+{"text": "What models are connected to assets.approval.matrix?", "response": "The assets.approval.matrix model has 17 relational fields: company_id -> res.company; branch_id -> res.branch; assets_approval_matrix_line_ids -> assets.approval.matrix.line; campaign_id -> utm.campaign; source_id -> utm.source; medium_id -> utm.medium; activity_ids -> mail.activity; activity_user_id -> res.users; activity_type_id -> mail.activity.type; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "assets.approval.matrix", "table_name": ""}
+{"text": "What are the available fields for base.language.export?", "response": "The base.language.export model has 13 fields: name, lang, format, modules, data, state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, selection: 3, many2many: 1, binary: 1, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base.language.export", "table_name": ""}
+{"text": "Describe the setu.inventory.overstock.bi.report model in Odoo.", "response": "The setu.inventory.overstock.bi.report model represents setu.inventory.overstock.bi.report in the ERP system. It contains 31 fields and is used to manage setu.inventory.overstock.bi.report data. Key fields include: product_id, product_category_id, warehouse_id, company_id, sales, ads, qty_available, incoming, outgoing, forecasted_stock, demanded_qty, coverage_days, overstock_qty, overstock_value, wh_overstock_qty_per, wh_overstock_value_per, turnover_ratio, stock_movement, last_purchase_date, last_purchase_qty, last_purchase_price, currency_name, vendor_name, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "setu.inventory.overstock.bi.report", "table_name": ""}
+{"text": "Describe the acrux.chat.connector model in Odoo.", "response": "The acrux.chat.connector model represents Connector Definition in the ERP system. It contains 38 fields and is used to manage connector definition data. Key fields include: name, sequence, message, company_id, team_id, verify, source, channel, endpoint, apikey, sandbox, uuid, time_to_respond, time_to_reasign, border_color, ca_app_name, ca_status, ca_status_txt, ca_qr_code, sale_report_id, connector_type, qc_app_name, qc_status, qc_status_txt, qc_qr_code, qc_channel, qc_channel_id, qc_sdk_token, qc_template_ids, qc_webhook_url, connection_status, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "acrux.chat.connector", "table_name": ""}
+{"text": "Which fields in acrux.chat.conversation are computed?", "response": "The acrux.chat.conversation model is defined in module: acrux_chat. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "acrux.chat.conversation", "table_name": ""}
+{"text": "What operations can I perform on access.group?", "response": "To use the access.group 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "access.group", "table_name": ""}
+{"text": "Show me the relational structure of barcodes.barcode_events_mixin.", "response": "The barcodes.barcode_events_mixin model has no explicit relational fields defined in its field metadata.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "barcodes.barcode_events_mixin", "table_name": ""}
+{"text": "How is pos.promotion used in the system?", "response": "The pos.promotion model represents Management Promotion on pos in the ERP system. It contains 101 fields and is used to manage management promotion on pos data. Key fields include: sequence, name, end_date, amount_total, type, method, discount_first_order, product_id, discount_order_ids, discount_category_ids, discount_quantity_ids, gift_condition_ids, gift_free_ids, discount_condition_ids, discount_apply_ids, multilevel_condition_ids, multilevel_gift_ids, price_ids, special_category_ids, discount_lowest_price, max_discount_amount_lowest_price, multi_buy_ids, promotion_specific_product_ids, tebus_murah_product_ids, product_ids, minimum_items, special_customer_ids, promotion_birthday, promotion_birthday_type, promotion_group, promotion_group_ids, state, pos_branch_ids, payment_method_ids, special_days, is_payment_method, monday, tuesday, wednesday, thursday, friday, saturday, sunday, special_times, from_time, to_time, is_stack, stack_type, pos_apply, is_card_payment, card_payment_id, card_payment_ids, new_type, new_based_on, tebus_murah_selected_brand_apply_and_or, tebus_murah_total_order_apply_and_or, new_based_on_free_item, new_based_on_tebus_murah, new_discount, discount_fixed_amount_lp, discount_fixed_amount_fo, branch_id, promotion_based_on_brand_ids, tebus_murah_selected_brand_ids, tebus_murah_brand_gift_based_on, tebus_murah_brand_min_amount_qty, tebus_murah_total_order_min_qty, tebus_murah_brand_min_amount, tebus_murah_brand_min_qty, tebus_murah_brand_ids, discount_apply_and_or, discount_apply_min_amount, discount_apply_min_qty, discount_fix_amount_all_product, free_item_apply_and_or, free_item_apply_min_amount, free_item_apply_min_qty, tebus_murah_apply_and_or, tebus_murah_apply_min_amount, tebus_murah_apply_min_qty, is_multi_level_promotion, promotion_product_discount_id, company_id, currency_id, no_of_usage, no_of_used, active, is_priority, field_name, note, pos_loyalty_category, pos_loyalty_category_ids, start_date, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.promotion", "table_name": ""}
+{"text": "Describe the bi.product.pack model in Odoo.", "response": "The bi.product.pack model represents bi.product.pack in the ERP system. It contains 14 fields and is used to manage bi.product.pack data. Key fields include: product_id, qty_uom, bi_product_template, bi_image, price, uom_id, name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "bi.product.pack", "table_name": ""}
+{"text": "What are the relationships in whatsapp.scan.qr?", "response": "The whatsapp.scan.qr model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "whatsapp.scan.qr", "table_name": ""}
+{"text": "How is report.equip3_pos_report.report_sales_summary used in the system?", "response": "The report.equip3_pos_report.report_sales_summary model represents POS Sale Summary Report in the ERP system. It contains 3 fields and is used to manage pos sale summary report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_pos_report.report_sales_summary", "table_name": ""}
+{"text": "What is the assets.approval.matrix model?", "response": "The assets.approval.matrix model represents Assets Approval Matrix in the ERP system. It contains 43 fields and is used to manage assets approval matrix data. Key fields include: name, company_id, branch_id, assets_approval_matrix_line_ids, is_assets_approval, 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.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "assets.approval.matrix", "table_name": ""}
+{"text": "Describe the field structure of inter.transfer.company.", "response": "The inter.transfer.company model has 24 fields: sale_id, sale_count, invoice_count, bill_count, invoice_id, purchase_id, purchase_count, return_id, return_count, name, state, from_warehouse, currency_id, to_warehouse, pricelist_id, apply_type, product_lines, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, integer: 6, many2many: 1, char: 2, selection: 2, one2many: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "inter.transfer.company", "table_name": ""}
+{"text": "What are common use cases for setu.rfm.segment?", "response": "To use the setu.rfm.segment model, you need to provide values for required fields: none. Readonly fields: total_mailing, total_customers, total_orders, total_revenue, open_lead_count, open_rfq_count, total_customers_ratio, total_orders_ratio, total_revenue_ratio, desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "setu.rfm.segment", "table_name": ""}
+{"text": "What business logic is in pos.coupon?", "response": "To use the pos.coupon model, you need to provide values for required fields: name, type_apply, sequence_generate_method, reward_type. Readonly fields: name, no_of_used, use_history_ids, product_display_name, reward_product_display_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "pos.coupon", "table_name": ""}
+{"text": "Can you explain the purpose of gamification.challenge?", "response": "The gamification.challenge model represents Gamification Challenge in the ERP system. It contains 47 fields and is used to manage gamification challenge data. Key fields include: name, description, state, manager_id, user_ids, user_domain, period, start_date, end_date, invited_user_ids, line_ids, reward_id, reward_first_id, reward_second_id, reward_third_id, reward_failure, reward_realtime, visibility_mode, report_message_frequency, report_message_group_id, report_template_id, remind_update_delay, last_report_date, next_report_date, challenge_category, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "gamification.challenge", "table_name": ""}
+{"text": "Tell me about the payment.icon model.", "response": "The payment.icon model represents Payment Icon in the ERP system. It contains 11 fields and is used to manage payment icon data. Key fields include: name, acquirer_ids, image, image_payment_form, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "payment.icon", "table_name": ""}
+{"text": "What is the account.root model?", "response": "The account.root model represents Account codes first 2 digits in the ERP system. It contains 6 fields and is used to manage account codes first 2 digits data. Key fields include: name, parent_id, company_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.root", "table_name": ""}
+{"text": "What data can be stored in quality.alert.report?", "response": "The quality.alert.report model has 12 fields: date_from, date_to, product_ids, user_ids, stage_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: date: 2, many2many: 2, many2one: 3, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "quality.alert.report", "table_name": ""}
+{"text": "Describe the field structure of mail.alias.", "response": "The mail.alias model has 17 fields: alias_name, alias_model_id, alias_user_id, alias_defaults, alias_force_thread_id, alias_domain, alias_parent_model_id, alias_parent_thread_id, alias_bounced_content, alias_contact, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 3, many2one: 5, text: 1, integer: 3, html: 1, selection: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.alias", "table_name": ""}
+{"text": "Describe the implementation of opening.balance.line.", "response": "The opening.balance.line model is defined in module: equip3_accounting_opening_balance. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "opening.balance.line", "table_name": ""}
+{"text": "What foreign keys exist in sh.sale.analysis.wizard?", "response": "The sh.sale.analysis.wizard model has 7 relational fields: sh_product_ids -> product.product; company_ids -> res.company; sh_partner_ids -> res.partner; company_id -> res.company; sale_analysis_dic -> user.order.dic; create_uid -> res.users; write_uid -> res.users. Many2many fields: sh_product_ids, company_ids, sh_partner_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.sale.analysis.wizard", "table_name": ""}
+{"text": "Which fields in expiry.picking.confirmation are computed?", "response": "The expiry.picking.confirmation model is defined in module: product_expiry. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "expiry.picking.confirmation", "table_name": ""}
+{"text": "Which fields in rn.approval.matrix are computed?", "response": "The rn.approval.matrix model is defined in module: equip3_inventory_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "rn.approval.matrix", "table_name": ""}
+{"text": "Can you explain the purpose of stock.warn.insufficient.qty.repair?", "response": "The stock.warn.insufficient.qty.repair model represents Warn Insufficient Repair Quantity in the ERP system. It contains 13 fields and is used to manage warn insufficient repair quantity data. Key fields include: repair_id, product_id, location_id, quant_ids, quantity, product_uom_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "stock.warn.insufficient.qty.repair", "table_name": ""}
+{"text": "What operations can I perform on cust.credit.limit.data.line?", "response": "To use the cust.credit.limit.data.line 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "cust.credit.limit.data.line", "table_name": ""}
+{"text": "Describe the field structure of sms.template.", "response": "The sms.template model has 18 fields: name, model_id, model, body, sidebar_action_id, lang, model_object_field, sub_object, sub_model_object_field, null_value, copyvalue, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 7, many2one: 7, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "sms.template", "table_name": ""}
+{"text": "What data can be stored in pos.promotion.price?", "response": "The pos.promotion.price model has 12 fields: active, product_id, minimum_quantity, price_down, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: boolean: 1, many2one: 4, float: 2, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.promotion.price", "table_name": ""}
+{"text": "What are the relationships in do.matrix.reject?", "response": "The do.matrix.reject model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "do.matrix.reject", "table_name": ""}
+{"text": "What does the sale.adv.wizard.product.line model represent?", "response": "The sale.adv.wizard.product.line model represents Sale Multi Product Selection Advanced Wizard Product Line in the ERP system. It contains 13 fields and is used to manage sale multi product selection advanced wizard product line data. Key fields include: sale_adv_wizard_id, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sale.adv.wizard.product.line", "table_name": ""}
+{"text": "How is limit.request implemented technically?", "response": "The limit.request model is defined in module: equip3_sale_other_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "limit.request", "table_name": ""}
+{"text": "Show me the fields of account.petty.cash.report.", "response": "The account.petty.cash.report model has 16 fields: name, custodian_id, main_cash_account_id, journal_id, amount, balance, virtual_balance, company_id, branch_id, effective_date, create_uid, create_date, expense_amount, id, display_name, __last_update. Field types distribution: char: 2, many2one: 6, float: 4, date: 1, datetime: 2, integer: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "account.petty.cash.report", "table_name": ""}
+{"text": "What are the technical details of report.sale.report_saleproforma?", "response": "The report.sale.report_saleproforma model is defined in module: sale. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sale.report_saleproforma", "table_name": ""}
+{"text": "How do I use the report.sh_sale_reports.sh_top_selling_product_doc model?", "response": "To use the report.sh_sale_reports.sh_top_selling_product_doc model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "report.sh_sale_reports.sh_top_selling_product_doc", "table_name": ""}
+{"text": "What methods are available in account.unreconcile?", "response": "The account.unreconcile model is defined in module: account. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.unreconcile", "table_name": ""}
+{"text": "Show me the relational structure of auditlog.http.request.", "response": "The auditlog.http.request model has 5 relational fields: user_id -> res.users; http_session_id -> auditlog.http.session; log_ids -> auditlog.log; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "auditlog.http.request", "table_name": ""}
+{"text": "How does sale.adv.wizard relate to other models?", "response": "The sale.adv.wizard model has 5 relational fields: product_ids -> sale.adv.wizard.product.line; product_attr_ids -> product.attribute.value; specific_product_ids -> sale.adv.wizard.product.line.specific; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_attr_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sale.adv.wizard", "table_name": ""}
+{"text": "Describe the gamification.karma.tracking model in Odoo.", "response": "The gamification.karma.tracking model represents Track Karma Changes in the ERP system. It contains 12 fields and is used to manage track karma changes data. Key fields include: user_id, old_value, new_value, consolidated, tracking_date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "gamification.karma.tracking", "table_name": ""}
+{"text": "What does the res.partner.category model represent?", "response": "The res.partner.category model represents Partner Tags in the ERP system. It contains 14 fields and is used to manage partner tags data. Key fields include: name, color, parent_id, child_ids, active, parent_path, partner_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "res.partner.category", "table_name": ""}
+{"text": "Describe the field structure of purchase.team.analysis.", "response": "The purchase.team.analysis model has 20 fields: days_to_approve, purchase_order_duration_to_confirm, amount_saved_from_cost_savings, number_of_successful_cost_savings, avg_amount_saved_from_cost_savings, avg_number_of_successful_cost_savings, user_id, purchase_ids, kpi_target, cost_saving_percentage, amount_purchased, cost_saving, branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: float: 10, many2one: 4, many2many: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "purchase.team.analysis", "table_name": ""}
+{"text": "What fields does link.tracker.click have?", "response": "The link.tracker.click model has 13 fields: campaign_id, link_id, ip, country_id, mailing_trace_id, mass_mailing_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "link.tracker.click", "table_name": ""}
+{"text": "How to create records in project.create.invoice?", "response": "To use the project.create.invoice model, you need to provide values for required fields: project_id, sale_order_id. Readonly fields: _candidate_orders, amount_to_invoice, currency_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "project.create.invoice", "table_name": ""}
+{"text": "What models are connected to pos.order.line.promotion?", "response": "The pos.order.line.promotion model has 4 relational fields: pos_order_line_id -> pos.order.line; promotion_id -> pos.promotion; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pos.order.line.promotion", "table_name": ""}
+{"text": "What is the inter.transfer.company.line model?", "response": "The inter.transfer.company.line model represents inter.transfer.company.line in the ERP system. It contains 11 fields and is used to manage inter.transfer.company.line data. Key fields include: internal_id, product_id, quantity, price_unit, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "inter.transfer.company.line", "table_name": ""}
+{"text": "What methods are available in account.ebupot?", "response": "The account.ebupot model is defined in module: equip3_accounting_efaktur. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.ebupot", "table_name": ""}
+{"text": "How is report.equip3_inventory_reports.expiring_product_calendar used in the system?", "response": "The report.equip3_inventory_reports.expiring_product_calendar model represents Expiring Product Calendar Report in the ERP system. It contains 3 fields and is used to manage expiring product calendar report data. Key fields include: id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.equip3_inventory_reports.expiring_product_calendar", "table_name": ""}
+{"text": "What models are connected to picking.order.line?", "response": "The picking.order.line model has 4 relational fields: picking_order_id -> picking.order; product_id -> product.product; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "picking.order.line", "table_name": ""}
+{"text": "What operations can I perform on sms.template.preview?", "response": "To use the sms.template.preview model, you need to provide values for required fields: sms_template_id. Readonly fields: model_id, body, no_record, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "sms.template.preview", "table_name": ""}
+{"text": "Tell me about the pos.promotion.discount.order model.", "response": "The pos.promotion.discount.order model represents Promotion each total order in the ERP system. It contains 15 fields and is used to manage promotion each total order data. Key fields include: active, minimum_amount, discount, discount2, multi_discount, max_discount_amount, discount_fixed_amount, promotion_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.promotion.discount.order", "table_name": ""}
+{"text": "What business logic is in account.deposit.reconcile?", "response": "To use the account.deposit.reconcile 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "account.deposit.reconcile", "table_name": ""}
+{"text": "Can you explain the purpose of opening.balance.line?", "response": "The opening.balance.line model represents opening.balance.line in the ERP system. It contains 15 fields and is used to manage opening.balance.line data. Key fields include: move_id, company_id, account_id, partner_id, company_currency_id, debit, credit, date_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "opening.balance.line", "table_name": ""}
+{"text": "Show me the relational structure of kpi.measure.", "response": "The kpi.measure model has 7 relational fields: model_id -> ir.model; date_field_ids -> ir.model.fields; measure_field_id -> ir.model.fields; company_field_id -> ir.model.fields; item_ids -> kpi.measure.item; create_uid -> res.users; write_uid -> res.users. Many2many fields: date_field_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "kpi.measure", "table_name": ""}
+{"text": "What is the project.task.type model?", "response": "The project.task.type model represents Task Stage in the ERP system. It contains 21 fields and is used to manage task stage data. Key fields include: active, name, description, sequence, project_ids, legend_blocked, legend_done, legend_normal, mail_template_id, fold, rating_template_id, auto_validation_kanban_state, is_closed, disabled_rating_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "project.task.type", "table_name": ""}
+{"text": "How to query purchase.request.allocation data?", "response": "To use the purchase.request.allocation model, you need to provide values for required fields: purchase_request_line_id, product_uom_id. Readonly fields: company_id, product_id, product_uom_id, open_product_qty, purchase_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "purchase.request.allocation", "table_name": ""}
+{"text": "Can you explain the purpose of pos.loyalty.history.update.point?", "response": "The pos.loyalty.history.update.point model represents POS Loyalty History Update Point in the ERP system. It contains 12 fields and is used to manage pos loyalty history update point data. Key fields include: type_apply, total_orders, total_point, pos_order_ids, parent_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.loyalty.history.update.point", "table_name": ""}
+{"text": "How does setu.inventory.outofstock.bi.report relate to other models?", "response": "The setu.inventory.outofstock.bi.report model has 7 relational fields: product_id -> product.product; product_category_id -> product.category; warehouse_id -> stock.warehouse; company_id -> res.company; wizard_id -> setu.inventory.outofstock.report; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "setu.inventory.outofstock.bi.report", "table_name": ""}
+{"text": "What is the pos.voucher.report model?", "response": "The pos.voucher.report model represents POS Voucher Report in the ERP system. It contains 14 fields and is used to manage pos voucher report data. Key fields include: name, used_date, number, code, pos_order_id, config_id, session_id, apply_type, amount, pos_branch_id, company_id, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "pos.voucher.report", "table_name": ""}
+{"text": "How does sh.purchase.product.profit.xls relate to other models?", "response": "The sh.purchase.product.profit.xls model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "sh.purchase.product.profit.xls", "table_name": ""}
+{"text": "How do I use the rfm.yearly.analysis.by.segment model?", "response": "To use the rfm.yearly.analysis.by.segment model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "rfm.yearly.analysis.by.segment", "table_name": ""}
+{"text": "List all fields in the mail.activity model.", "response": "The mail.activity model has 31 fields: res_model_id, res_model, res_id, res_name, activity_type_id, activity_category, activity_decoration, icon, summary, note, date_deadline, automated, user_id, request_partner_id, state, recommended_activity_type_id, previous_activity_type_id, has_recommended_activities, mail_template_ids, force_next, can_write, calendar_event_id, attachment_ids, is_attachment_required, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 9, char: 5, many2one_reference: 1, selection: 3, html: 1, date: 1, boolean: 5, many2many: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "mail.activity", "table_name": ""}
+{"text": "What modules define queue.job.dashboard?", "response": "The queue.job.dashboard model is defined in module: queue_job. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "queue.job.dashboard", "table_name": ""}
+{"text": "What does the account.cashbox.wizard model represent?", "response": "The account.cashbox.wizard model represents account.cashbox.wizard in the ERP system. It contains 14 fields and is used to manage account.cashbox.wizard data. Key fields include: pos_session_id, line_ids, amount_total, is_closing_wizard, is_validate, is_return, line_bank_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "account.cashbox.wizard", "table_name": ""}
+{"text": "What fields does customer.deposit.report have?", "response": "The customer.deposit.report model has 16 fields: name, partner_id, amount, currency_id, remaining_amount, communication, move_id, return_deposit, payment_date, deposit_reconcile_journal_id, journal_id, deposit_account_id, used_amount, id, display_name, __last_update. Field types distribution: char: 3, many2one: 7, monetary: 3, date: 1, integer: 1, datetime: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "customer.deposit.report", "table_name": ""}
+{"text": "How is dev.credit.note.wizard implemented technically?", "response": "The dev.credit.note.wizard model is defined in module: dev_rma. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "dev.credit.note.wizard", "table_name": ""}
+{"text": "Describe the many2many relations for stock.inventory.line.", "response": "The stock.inventory.line model has 21 relational fields: inventory_id -> stock.inventory; partner_id -> res.partner; product_id -> product.product; product_uom_id -> uom.uom; categ_id -> product.category; package_id -> stock.quant.package; prod_lot_id -> stock.production.lot; company_id -> res.company; location_id -> stock.location; adjustment_account_id -> account.account; filtered_adjustment_account_id -> account.account; analytic_tag_ids -> account.analytic.tag; uom_id -> uom.uom; category_uom_id -> uom.category; wizard_id -> stock.inventory.wizard; currency_id -> res.currency; user_id_1 -> res.users; user_id_2 -> res.users; current_user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: filtered_adjustment_account_id, analytic_tag_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "stock.inventory.line", "table_name": ""}
+{"text": "Which fields in account.equity.move are computed?", "response": "The account.equity.move model is defined in module: equip3_accounting_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "account.equity.move", "table_name": ""}
+{"text": "Describe the implementation of queue.job.channel.", "response": "The queue.job.channel model is defined in module: queue_job. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "queue.job.channel", "table_name": ""}
+{"text": "Describe the implementation of target.kpi.", "response": "The target.kpi model is defined in module: equip3_purchase_masterdata. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "target.kpi", "table_name": ""}
+{"text": "What are the technical details of sale.adv.wizard.product.line.specific?", "response": "The sale.adv.wizard.product.line.specific model is defined in module: equip3_sale_operation. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "sale.adv.wizard.product.line.specific", "table_name": ""}
+{"text": "What are common use cases for rating.mixin?", "response": "To use the rating.mixin model, you need to provide values for required fields: none. Readonly fields: rating_ids, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, id, display_name, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "rating.mixin", "table_name": ""}
+{"text": "What modules define report.sh_sale_reports.sh_salesperson_report_doc?", "response": "The report.sh_sale_reports.sh_salesperson_report_doc model is defined in module: sh_sale_reports. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "report.sh_sale_reports.sh_salesperson_report_doc", "table_name": ""}
+{"text": "What is the ks.parameter.tuning.wizard model?", "response": "The ks.parameter.tuning.wizard model represents Parameter Tuner in the ERP system. It contains 21 fields and is used to manage parameter tuner data. Key fields include: ks_forecast, ks_forecast_method, min_p, max_p, min_d, max_d, min_q, max_q, min_sp, max_sp, min_sd, max_sd, min_sq, max_sq, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "ks.parameter.tuning.wizard", "table_name": ""}
+{"text": "What are the relationships in approval.matrix.accounting.lines?", "response": "The approval.matrix.accounting.lines model has 18 relational fields: user_ids -> res.users; approval_matrix_id -> approval.matrix.accounting; approved_users -> res.users; last_approved -> res.users; move_id -> account.move; receipt_id -> account.payment; multi_receipt_id -> account.multipayment; voucher_id -> account.voucher; payment_voc_id -> payment.voucher; acc_internal_transfer_id -> account.internal.transfer; account_budget_request_id -> budget.change.req; account_budget_id -> crossovered.budget; budget_purchase_id -> budget.purchase; account_budget_req_id -> purchase.change.request; customer_deposit_id -> customer.deposit; acc_vendor_deposit_id -> vendor.deposit; create_uid -> res.users; write_uid -> res.users. Many2many fields: user_ids, approved_users.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "approval.matrix.accounting.lines", "table_name": ""}
+{"text": "How is purchase.down.payment implemented technically?", "response": "The purchase.down.payment model is defined in module: dev_purchase_down_payment. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "purchase.down.payment", "table_name": ""}
+{"text": "What foreign keys exist in budget.budget?", "response": "The budget.budget model has 12 relational fields: parent_id -> budget.budget; user_id -> res.users; budget_budget_line -> budget.budget.budget.line; company_id -> res.company; message_follower_ids -> mail.followers; message_partner_ids -> res.partner; message_channel_ids -> mail.channel; message_ids -> mail.message; message_main_attachment_id -> ir.attachment; website_message_ids -> mail.message; create_uid -> res.users; write_uid -> res.users. Many2many fields: message_partner_ids, message_channel_ids.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "budget.budget", "table_name": ""}
+{"text": "List all fields in the force.done.memory model.", "response": "The force.done.memory model has 11 fields: blanket_id, qty, remaining_qty, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 3, float: 2, text: 1, integer: 1, char: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "force.done.memory", "table_name": ""}
+{"text": "Can you explain the purpose of sh.purchase.bill.summary.wizard?", "response": "The sh.purchase.bill.summary.wizard model represents Purchase Bill Summary Wizard in the ERP system. It contains 13 fields and is used to manage purchase bill summary wizard data. Key fields include: sh_start_date, sh_end_date, sh_partner_ids, sh_status, company_ids, branch_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "sh.purchase.bill.summary.wizard", "table_name": ""}
+{"text": "What modules define stock.location.tag?", "response": "The stock.location.tag model is defined in module: stock_3dbase. It has 0 computed fields: . Stored computed fields: none.", "source": "orm_introspection", "category": "technical", "complexity_level": "advanced", "model_name": "stock.location.tag", "table_name": ""}
+{"text": "List all fields in the setu.inventory.fsn.analysis.bi.report model.", "response": "The setu.inventory.fsn.analysis.bi.report model has 18 fields: product_id, product_category_id, warehouse_id, company_id, opening_stock, closing_stock, average_stock, sales, turnover_ratio, stock_movement, wizard_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: many2one: 7, float: 5, char: 2, integer: 1, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "setu.inventory.fsn.analysis.bi.report", "table_name": ""}
+{"text": "Describe the wizard.vendor.deposit model in Odoo.", "response": "The wizard.vendor.deposit model represents Wizard Vendor Deposit in the ERP system. It contains 9 fields and is used to manage wizard vendor deposit data. Key fields include: reason, add_amount, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "wizard.vendor.deposit", "table_name": ""}
+{"text": "What data can be stored in pos.cashier.change.wizard?", "response": "The pos.cashier.change.wizard model has 10 fields: start_datetime, end_datetime, pos_branch_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: datetime: 5, many2one: 3, integer: 1, char: 1.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "pos.cashier.change.wizard", "table_name": ""}
+{"text": "What are common use cases for ks_dashboard_ninja.child_board?", "response": "To use the ks_dashboard_ninja.child_board model, you need to provide values for required fields: company_id. Readonly fields: ks_dashboard_menu_name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "ks_dashboard_ninja.child_board", "table_name": ""}
+{"text": "How is report.project.task.user used in the system?", "response": "The report.project.task.user model represents Tasks Analysis in the ERP system. It contains 23 fields and is used to manage tasks analysis data. Key fields include: name, user_id, date_assign, date_end, date_deadline, date_last_stage_update, project_id, working_days_close, working_days_open, delay_endings_days, nbr, priority, state, company_id, partner_id, stage_id, hours_planned, hours_effective, remaining_hours, progress, id, display_name, __last_update.", "source": "orm_introspection", "category": "basic_info", "complexity_level": "basic", "model_name": "report.project.task.user", "table_name": ""}
+{"text": "How do I use the restaurant.floor model?", "response": "To use the restaurant.floor 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. The model supports standard CRUD operations through the ORM.", "source": "orm_introspection", "category": "usage", "complexity_level": "intermediate", "model_name": "restaurant.floor", "table_name": ""}
+{"text": "List all fields in the base_import.tests.models.char model.", "response": "The base_import.tests.models.char model has 8 fields: value, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field types distribution: char: 2, integer: 1, many2one: 2, datetime: 3.", "source": "orm_introspection", "category": "field_inquiry", "complexity_level": "basic", "model_name": "base_import.tests.models.char", "table_name": ""}
+{"text": "Describe the many2many relations for pmps.adv.wizard.product.line.specific.", "response": "The pmps.adv.wizard.product.line.specific model has 5 relational fields: pmps_adv_wizard_id_specific -> pmps.adv.wizard; product_id -> product.product; uom_po_id -> uom.uom; create_uid -> res.users; write_uid -> res.users. Many2many fields: none.", "source": "orm_introspection", "category": "relationship", "complexity_level": "intermediate", "model_name": "pmps.adv.wizard.product.line.specific", "table_name": ""}
\ No newline at end of file