Datasets:
Dataset Preview
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
[{'expected': SplitInfo(name='train', num_bytes=0, num_examples=9066, shard_lengths=None, dataset_name=None), 'recorded': SplitInfo(name='train', num_bytes=11027216, num_examples=11346, shard_lengths=None, dataset_name='hashmicro-allfresh')}, {'expected': SplitInfo(name='validation', num_bytes=0, num_examples=4999, shard_lengths=None, dataset_name=None), 'recorded': SplitInfo(name='validation', num_bytes=2578763, num_examples=2719, shard_lengths=None, dataset_name='hashmicro-allfresh')}]
Error code: UnexpectedError
Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
text string | response string | source string | category string | complexity_level string | model_name string | table_name string |
|---|---|---|---|---|---|---|
What tables are connected to pos_promotion_specific_product? or Describe the relational structure of pos_promotion_specific_product. | Foreign keys in pos_promotion_specific_product: create_uid -> res_users.id [constraint: pos_promotion_specific_product_create_uid_fkey]; product_id -> product_product.id [constraint: pos_promotion_specific_product_product_id_fkey]; promotion_id -> pos_promotion.id [constraint: pos_promotion_specific_product_promotion_i... | sql_introspection | relationships | intermediate | pos_promotion_specific_product | |
What is the approval.matrix.blanket.order model? or Describe the approval.matrix.blanket.order model in Odoo. | The approval.matrix.blanket.order model represents Approval Matrix Blanket Order in the ERP system. It contains 44 fields and is used to manage approval matrix blanket order data. Defined in module: equip3_purchase_other_operation. Key fields include: name, company_id, branch_id, approval_matrix_blanket_order_line_ids,... | orm_introspection | basic_info | basic | approval.matrix.blanket.order | |
What fields does account.tax have? or Describe the field structure of account.tax. | The account.tax model has 58 fields. Field types distribution: many2one: 11, boolean: 13, char: 7, selection: 6, many2many: 3, integer: 6, float: 1, one2many: 6, date: 2, datetime: 3. Computed fields: 25. Field details: tax_paid_account (many2one) -> account.account [module: equip3_accounting_taxoperation]; price_inclu... | orm_introspection | field_inquiry | basic | account.tax | |
Describe the free.product.lines model in Odoo. or Tell me about the free.product.lines model. | The free.product.lines model represents Free Product Lines in the ERP system. It contains 12 fields and is used to manage free product lines data. Defined in module: equip3_sale_loyalty. Key fields include: product_id, description, quantity, uom_id, customer_target_id, id, display_name, create_uid, create_date, write_u... | orm_introspection | basic_info | basic | free.product.lines | |
What field types are used in account.report.general.ledger? or What are the available fields for account.report.general.ledger? | The account.report.general.ledger model has 16 fields. Field types distribution: boolean: 1, selection: 3, many2many: 1, date: 2, many2one: 4, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: initial_balance (boolean) [module: accounting_pdf_reports]; sortby (selection) [required] [module: accountin... | orm_introspection | field_inquiry | basic | account.report.general.ledger | |
How do I use the account.trial.balance model? or What operations can I perform on account.trial.balance? | To use the account.trial.balance model, you need to provide values for required fields: journal_ids, display_account, consolidate, all_account, target_move, company_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: journal_ids [required] [has_defa... | orm_introspection | usage | intermediate | account.trial.balance | |
How do I use the approval.matrix.vendor model? or What operations can I perform on approval.matrix.vendor? | To use the approval.matrix.vendor model, you need to provide values for required fields: name, company_id, branch_id. Readonly fields: company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required]; company_id [required] [readonly] [has_default]; branch... | orm_introspection | usage | intermediate | approval.matrix.vendor | |
Which columns are nullable in sms_template_preview? or What data types are used in sms_template_preview? | Columns in sms_template_preview: id (integer) [NOT NULL] [DEFAULT: nextval('sms_template_preview_id_seq'::regclass)] [PRECISION: 32]; sms_template_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Sms Template]; lang (character varying) [COMMENT: Template Preview Language]; resource_ref (character varying) [COMMENT: Re... | sql_introspection | columns | basic | sms_template_preview | |
Tell me about the sh_sale_category_xls table. or Explain the sh_sale_category_xls table schema. | The sh_sale_category_xls table has 6 columns and 2 foreign key relationships. It stores data related to sh sale category xls in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, character varying: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1. | sql_introspection | structure | basic | sh_sale_category_xls | |
How does pos.payment.report relate to other models? or Show me the relational structure of pos.payment.report. | The pos.payment.report model has 8 relational fields: payment_method_id -> pos.payment.method; config_id -> pos.config; order_id -> pos.order; session_id -> pos.session; company_id -> res.company; pos_branch_id -> res.branch; currency_id -> res.currency; partner_id -> res.partner. Many2many fields: none. One2many field... | orm_introspection | relationship | intermediate | pos.payment.report | |
Describe the implementation of partial.quantity.done. or What modules define partial.quantity.done? | The partial.quantity.done model is defined in module: equip3_inventory_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_confirm_partial_quantity. | orm_introspection | technical | advanced | partial.quantity.done | |
What are the foreign keys in stock_valuation_layer? or What tables does stock_valuation_layer reference? | Foreign keys in stock_valuation_layer: account_move_id -> account_move.id [constraint: stock_valuation_layer_account_move_id_fkey]; company_id -> res_company.id [constraint: stock_valuation_layer_company_id_fkey]; create_uid -> res_users.id [constraint: stock_valuation_layer_create_uid_fkey]; location_id -> stock_locat... | sql_introspection | relationships | intermediate | stock_valuation_layer | |
What columns have default values in stock_rules_report_stock_warehouse_rel? or What are the length constraints in stock_rules_report_stock_warehouse_rel? | Columns in stock_rules_report_stock_warehouse_rel: stock_rules_report_id (integer) [NOT NULL] [PRECISION: 32]; stock_warehouse_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints. | sql_introspection | columns | basic | stock_rules_report_stock_warehouse_rel | |
Can you explain the purpose of vendor.deposit.amount.wizard? or What does the vendor.deposit.amount.wizard model represent? | The vendor.deposit.amount.wizard model represents vendor deposit amount wizard in the ERP system. It contains 13 fields and is used to manage vendor deposit amount wizard data. Defined in module: equip3_accounting_deposit. Key fields include: currency_id, deposit_amount, final_amount, final_remaining_amount, is_vendor_... | orm_introspection | basic_info | basic | vendor.deposit.amount.wizard | |
What are the length constraints in pos_loyalty_point_product_product_rel? or What are the column types in pos_loyalty_point_product_product_rel? | Columns in pos_loyalty_point_product_product_rel: loyalty_point_id (integer) [NOT NULL] [PRECISION: 32]; product_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints. | sql_introspection | columns | basic | pos_loyalty_point_product_product_rel | |
What are the available fields for target.activity.line? or Which fields are required in target.activity.line? | The target.activity.line model has 13 fields. Field types distribution: many2one: 5, integer: 2, float: 2, char: 1, datetime: 3. Computed fields: 5. Field details: user_id (many2one) [readonly] -> res.users [compute: <bound method Field._compute_related of target.activity.line.user_id>] [not stored] [module: equip3_crm... | orm_introspection | field_inquiry | basic | target.activity.line | |
What methods are available in wizard.product.bundle.bi? or Describe the implementation of wizard.product.bundle.bi. | The wizard.product.bundle.bi model is defined in module: dynamic_product_bundle. It has 3 computed fields: bi_pack_ids, display_name, __last_update. Stored computed fields: none. Related fields: bi_pack_ids -> product_id.bi_pack_ids. Original module methods: button_add_product_bundle_bi. | orm_introspection | technical | advanced | wizard.product.bundle.bi | |
What data can be stored in purchase.order? or What field types are used in purchase.order? | The purchase.order model has 266 fields. Field types distribution: selection: 19, char: 30, datetime: 11, many2one: 49, one2many: 15, text: 5, integer: 19, many2many: 13, float: 21, boolean: 72, binary: 1, monetary: 7, html: 2, date: 2. Computed fields: 117. Field details: priority (selection) [module: purchase]; origi... | orm_introspection | field_inquiry | basic | purchase.order | |
How many columns are in x_report_wizard? or What columns does x_report_wizard have? | The x_report_wizard table has 8 columns and 4 foreign key relationships. It stores data related to x report wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1. | sql_introspection | structure | basic | x_report_wizard | |
Show me the column structure of account_move_invoice_printout_editor_rel. or List all columns in account_move_invoice_printout_editor_rel. | Columns in account_move_invoice_printout_editor_rel: invoice_printout_editor_id (integer) [NOT NULL] [PRECISION: 32]; account_move_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints. | sql_introspection | columns | basic | account_move_invoice_printout_editor_rel | |
Tell me about the website_sale_payment_acquirer_onboarding_wizard table. or How many columns are in website_sale_payment_acquirer_onboarding_wizard? | The website_sale_payment_acquirer_onboarding_wizard table has 16 columns and 2 foreign key relationships. It stores data related to website sale payment acquirer onboarding wizard in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, character varying: 10, text: 1, timestamp wit... | sql_introspection | structure | basic | website_sale_payment_acquirer_onboarding_wizard | |
What computed fields exist in report.eq_scrap_order_report.scrap_order_report? or Show me the fields of report.eq_scrap_order_report.scrap_order_report. | The report.eq_scrap_order_report.scrap_order_report model has 3 fields. Field types distribution: integer: 1, char: 1, datetime: 1. Computed fields: 2. Field details: id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datet... | orm_introspection | field_inquiry | basic | report.eq_scrap_order_report.scrap_order_report | |
Describe the product.template.barcode model in Odoo. or Can you explain the purpose of product.template.barcode? | The product.template.barcode model represents Product Barcode in the ERP system. It contains 13 fields and is used to manage product barcode data. Defined in module: sh_product_multi_barcode. Key fields include: product_id, name, product_uom_id, product_uom_category_id, uom_id, active, id, display_name, create_uid, cre... | orm_introspection | basic_info | basic | product.template.barcode | |
Tell me about the internal_location_matrix_rel table. or What indexes exist on internal_location_matrix_rel? | The internal_location_matrix_rel table has 2 columns and 2 foreign key relationships. It stores data related to internal location matrix rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0. | sql_introspection | structure | basic | internal_location_matrix_rel | |
What fields are available in print_prenumbered_checks? or What data types are used in print_prenumbered_checks? | Columns in print_prenumbered_checks: id (integer) [NOT NULL] [DEFAULT: nextval('print_prenumbered_checks_id_seq'::regclass)] [PRECISION: 32]; next_check_number (character varying) [NOT NULL] [COMMENT: Next Check Number]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zon... | sql_introspection | columns | basic | print_prenumbered_checks | |
List all constraint names in acrux_chat_message_wizard. or What relationships exist for acrux_chat_message_wizard? | Foreign keys in acrux_chat_message_wizard: connector_id -> acrux_chat_connector.id [constraint: acrux_chat_message_wizard_connector_id_fkey]; conversation_id -> acrux_chat_conversation.id [constraint: acrux_chat_message_wizard_conversation_id_fkey]; create_uid -> res_users.id [constraint: acrux_chat_message_wizard_crea... | sql_introspection | relationships | intermediate | acrux_chat_message_wizard | |
List all constraint names in utm_tag_rel. or What relationships exist for utm_tag_rel? | Foreign keys in utm_tag_rel: campaign_id -> utm_tag.id [constraint: utm_tag_rel_campaign_id_fkey]; tag_id -> utm_campaign.id [constraint: utm_tag_rel_tag_id_fkey]. Total foreign key relationships: 2. Referenced tables: utm_tag, utm_campaign. | sql_introspection | relationships | intermediate | utm_tag_rel | |
How to work with update.qty fields? or How to create records in update.qty? | To use the update.qty model, you need to provide values for required fields: sh_qty. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: sh_qty [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [... | orm_introspection | usage | intermediate | update.qty | |
What fields are readonly in access.rights.profile? or How to create records in access.rights.profile? | To use the access.rights.profile model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly];... | orm_introspection | usage | intermediate | access.rights.profile | |
What is the purchase_order_sh_purchase_update_mass_tag_wizard_rel table? or Tell me about the purchase_order_sh_purchase_update_mass_tag_wizard_rel table. | The purchase_order_sh_purchase_update_mass_tag_wizard_rel table has 2 columns and 2 foreign key relationships. It stores data related to purchase order sh purchase update mass tag wizard rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with ... | sql_introspection | structure | basic | purchase_order_sh_purchase_update_mass_tag_wizard_rel | |
What are the column types in repair_tags? or What data types are used in repair_tags? | Columns in repair_tags: id (integer) [NOT NULL] [DEFAULT: nextval('repair_tags_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Tag Name]; color (integer) [PRECISION: 32] [COMMENT: Color Index]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without ... | sql_introspection | columns | basic | repair_tags | |
Describe the field structure of base_import.tests.models.complex. or What fields does base_import.tests.models.complex have? | The base_import.tests.models.complex model has 13 fields. Field types distribution: float: 1, monetary: 1, char: 2, many2one: 3, date: 1, datetime: 4, integer: 1. Computed fields: 2. Field details: f (float) [readonly] [module: base_import]; m (monetary) [readonly] [module: base_import]; c (char) [readonly] [module: ba... | orm_introspection | field_inquiry | basic | base_import.tests.models.complex | |
What business logic is in convert.revenue? or What are common use cases for convert.revenue? | To use the convert.revenue model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write... | orm_introspection | usage | intermediate | convert.revenue | |
Which columns are nullable in restore_lead_type? or Describe the columns of restore_lead_type. | Columns in restore_lead_type: id (integer) [NOT NULL] [DEFAULT: nextval('restore_lead_type_id_seq'::regclass)] [PRECISION: 32]; lead_type_id (integer) [PRECISION: 32] [COMMENT: Lead Type]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_... | sql_introspection | columns | basic | restore_lead_type | |
Describe the implementation of pos.profit.and.loss. or How is pos.profit.and.loss implemented technically? | The pos.profit.and.loss model is defined in module: equip3_pos_report. It has 3 computed fields: product_uom_id, display_name, __last_update. Stored computed fields: none. Related fields: product_uom_id -> pos_order_line_id.product_uom_id. Original module methods: init. | orm_introspection | technical | advanced | pos.profit.and.loss | |
Describe the relational structure of vendor_pricelist_approval_matrix. or List all constraint names in vendor_pricelist_approval_matrix. | Foreign keys in vendor_pricelist_approval_matrix: branch_id -> res_branch.id [constraint: vendor_pricelist_approval_matrix_branch_id_fkey]; company_id -> res_company.id [constraint: vendor_pricelist_approval_matrix_company_id_fkey]; create_uid -> res_users.id [constraint: vendor_pricelist_approval_matrix_create_uid_fke... | sql_introspection | relationships | intermediate | vendor_pricelist_approval_matrix | |
Tell me about the mrp_bom_tools table. or What is stored in mrp_bom_tools? | The mrp_bom_tools table has 13 columns and 9 foreign key relationships. It stores data related to mrp bom tools in the system. The table has 2 indexes for performance optimization. Column types: integer: 10, numeric: 1, timestamp without time zone: 2. Nullable columns: 8, columns with defaults: 1. | sql_introspection | structure | basic | mrp_bom_tools | |
Which columns are nullable in account_journal_customer_deposit_rel? or What data types are used in account_journal_customer_deposit_rel? | Columns in account_journal_customer_deposit_rel: customer_deposit_id (integer) [NOT NULL] [PRECISION: 32]; account_journal_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints. | sql_introspection | columns | basic | account_journal_customer_deposit_rel | |
Describe the columns of account_bank_statement_integrate. or List all columns in account_bank_statement_integrate. | Columns in account_bank_statement_integrate: id (integer) [NOT NULL] [DEFAULT: nextval('account_bank_statement_integrate_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Number]; journal_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Bank Journal]; date_from (date) [NOT NULL] [COMMENT: Start D... | sql_introspection | columns | basic | account_bank_statement_integrate | |
What relationships exist for stock_return_picking_inter_company? or What are the foreign keys in stock_return_picking_inter_company? | Foreign keys in stock_return_picking_inter_company: create_uid -> res_users.id [constraint: stock_return_picking_inter_company_create_uid_fkey]; move_id -> stock_move.id [constraint: stock_return_picking_inter_company_move_id_fkey]; product_id -> product_product.id [constraint: stock_return_picking_inter_company_produc... | sql_introspection | relationships | intermediate | stock_return_picking_inter_company | |
What are the column types in website_visitor? or What fields are available in website_visitor? | Columns in website_visitor: id (integer) [NOT NULL] [DEFAULT: nextval('website_visitor_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [COMMENT: Name]; access_token (character varying) [NOT NULL] [COMMENT: Access Token]; active (boolean) [COMMENT: Active]; website_id (integer) [PRECISION: 32] [COMMENT: We... | sql_introspection | columns | basic | website_visitor | |
Describe the many2many relations for account.balance.report. or What foreign keys exist in account.balance.report? | The account.balance.report model has 5 relational fields: journal_ids -> account.journal; report_currency_id -> res.currency; company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: journal_ids. One2many fields: none. | orm_introspection | relationship | intermediate | account.balance.report | |
What relationships exist for account_reconcile_model_line? or Describe the relational structure of account_reconcile_model_line. | Foreign keys in account_reconcile_model_line: account_id -> account_account.id [constraint: account_reconcile_model_line_account_id_fkey]; analytic_account_id -> account_analytic_account.id [constraint: account_reconcile_model_line_analytic_account_id_fkey]; company_id -> res_company.id [constraint: account_reconcile_m... | sql_introspection | relationships | intermediate | account_reconcile_model_line | |
What foreign keys exist in website? or How does website relate to other models? | The website model has 24 relational fields: country_group_ids -> res.country.group; company_id -> res.company; language_ids -> res.lang; default_lang_id -> res.lang; user_id -> res.users; partner_id -> res.partner; menu_id -> website.menu; homepage_id -> website.page; theme_id -> ir.module.module; channel_id -> im_live... | orm_introspection | relationship | intermediate | website | |
What is the account.deposit.reconcile model? or What does the account.deposit.reconcile model represent? | The account.deposit.reconcile model represents account.deposit.reconcile in the ERP system. It contains 9 fields and is used to manage account.deposit.reconcile data. Defined in module: equip3_accounting_deposit. Key fields include: date, allocation_line_ids, id, display_name, create_uid, create_date, write_uid, write_... | orm_introspection | basic_info | basic | account.deposit.reconcile | |
What fields are available in ir_demo_failure_wizard? or Which columns are nullable in ir_demo_failure_wizard? | Columns in ir_demo_failure_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('ir_demo_failure_wizard_id_seq'::regclass)] [PRECISION: 32]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Update... | sql_introspection | columns | basic | ir_demo_failure_wizard | |
List all fields in the account.aged.trial.balance model. or What fields does account.aged.trial.balance have? | The account.aged.trial.balance model has 15 fields. Field types distribution: integer: 2, many2many: 1, date: 2, selection: 2, many2one: 4, char: 1, datetime: 3. Computed fields: 2. Field details: period_length (integer) [required] [module: accounting_pdf_reports]; journal_ids (many2many) [required] -> account.journal ... | orm_introspection | field_inquiry | basic | account.aged.trial.balance | |
What are the length constraints in account_resequence_wizard? or What columns have default values in account_resequence_wizard? | Columns in account_resequence_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('account_resequence_wizard_id_seq'::regclass)] [PRECISION: 32]; first_date (date) [COMMENT: First Date]; end_date (date) [COMMENT: End Date]; first_name (character varying) [NOT NULL] [COMMENT: First New Sequence]; ordering (character varyi... | sql_introspection | columns | basic | account_resequence_wizard | |
What is the pos_account_cashbox_line table? or Explain the pos_account_cashbox_line table schema. | The pos_account_cashbox_line table has 8 columns and 3 foreign key relationships. It stores data related to pos account cashbox line in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, numeric: 1, timestamp without time zone: 2. Nullable columns: 6, columns with defaults: 1. | sql_introspection | structure | basic | pos_account_cashbox_line | |
Explain the bi_product_pack table schema. or Describe the bi_product_pack table structure. | The bi_product_pack table has 8 columns and 4 foreign key relationships. It stores data related to bi product pack in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, double precision: 1, timestamp without time zone: 2. Nullable columns: 5, columns with defaults: 1. | sql_introspection | structure | basic | bi_product_pack | |
Show me the relational structure of pos.voucher.report. or What foreign keys exist in pos.voucher.report? | The pos.voucher.report model has 5 relational fields: pos_order_id -> pos.order; config_id -> pos.config; session_id -> pos.session; pos_branch_id -> res.branch; company_id -> res.company. Many2many fields: none. One2many fields: none. | orm_introspection | relationship | intermediate | pos.voucher.report | |
What business logic is in pos.generate.efaktur? or What fields are readonly in pos.generate.efaktur? | To use the pos.generate.efaktur model, you need to provide values for required fields: name. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required] [has_default] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create... | orm_introspection | usage | intermediate | pos.generate.efaktur | |
How to create records in internal.transfer? or What business logic is in internal.transfer? | To use the internal.transfer model, you need to provide values for required fields: requested_by, scheduled_date. Readonly fields: name, source_document, state1, state2, state3, operation_type_in_id, operation_type_out_id, operation_count, internal_transfer_line_total, itr_approval_matrix_id, is_itr_approval_matrix, ap... | orm_introspection | usage | intermediate | internal.transfer | |
What operations can I perform on ir.default? or What are common use cases for ir.default? | To use the ir.default model, you need to provide values for required fields: field_id, json_value. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: field_id [required]; json_value [required]; id [readonly]; display_name [readonly] [computed] [no_copy... | orm_introspection | usage | intermediate | ir.default | |
How does accounting_flow_wizard relate to other tables? or What tables are connected to accounting_flow_wizard? | Foreign keys in accounting_flow_wizard: create_uid -> res_users.id [constraint: accounting_flow_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: accounting_flow_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users. | sql_introspection | relationships | intermediate | accounting_flow_wizard | |
What columns have default values in account_analytic_tag_invoice_recurring_rel? or What are the length constraints in account_analytic_tag_invoice_recurring_rel? | Columns in account_analytic_tag_invoice_recurring_rel: invoice_recurring_id (integer) [NOT NULL] [PRECISION: 32]; account_analytic_tag_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints. | sql_introspection | columns | basic | account_analytic_tag_invoice_recurring_rel | |
What are the foreign keys in sh_fiscal_year? or What tables does sh_fiscal_year reference? | Foreign keys in sh_fiscal_year: branch_id -> res_branch.id [constraint: sh_fiscal_year_branch_id_fkey]; company_id -> res_company.id [constraint: sh_fiscal_year_company_id_fkey]; create_uid -> res_users.id [constraint: sh_fiscal_year_create_uid_fkey]; move_id -> account_move.id [constraint: sh_fiscal_year_move_id_fkey]... | sql_introspection | relationships | intermediate | sh_fiscal_year | |
What are the foreign keys in account_report_partner_ledger? or What tables does account_report_partner_ledger reference? | Foreign keys in account_report_partner_ledger: company_id -> res_company.id [constraint: account_report_partner_ledger_company_id_fkey]; create_uid -> res_users.id [constraint: account_report_partner_ledger_create_uid_fkey]; report_currency_id -> res_currency.id [constraint: account_report_partner_ledger_report_currenc... | sql_introspection | relationships | intermediate | account_report_partner_ledger | |
What operations can I perform on account.common.account.report? or What fields are readonly in account.common.account.report? | To use the account.common.account.report model, you need to provide values for required fields: display_account, journal_ids, target_move, company_id. Readonly fields: display_account, journal_ids, date_from, date_to, target_move, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, wri... | orm_introspection | usage | intermediate | account.common.account.report | |
How to create records in analytic.sale.order.line? or What business logic is in analytic.sale.order.line? | To use the analytic.sale.order.line model, you need to provide values for required fields: product_id, product_uom_qty, product_uom. Readonly fields: name, product_uom, price_subtotal, price_tax, price_total, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [rea... | orm_introspection | usage | intermediate | analytic.sale.order.line | |
What fields are available in sale_order_repair? or Describe the columns of sale_order_repair. | Columns in sale_order_repair: id (integer) [NOT NULL] [DEFAULT: nextval('sale_order_repair_id_seq'::regclass)] [PRECISION: 32]; repair_type (character varying) [COMMENT: Repair Type]; is_return_required (boolean) [COMMENT: Return the repaired parts ]; return_sale_order_id (integer) [PRECISION: 32] [COMMENT: Return Sale... | sql_introspection | columns | basic | sale_order_repair | |
List all fields in the approval.reject model. or What field types are used in approval.reject? | The approval.reject model has 8 fields. Field types distribution: text: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: reason (text) [required] [module: equip3_purchase_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_nam... | orm_introspection | field_inquiry | basic | approval.reject | |
What are the foreign keys in purchase_target_based_on_target_kpi_rel? or Describe the relational structure of purchase_target_based_on_target_kpi_rel. | Foreign keys in purchase_target_based_on_target_kpi_rel: purchase_target_based_on_id -> purchase_target_based_on.id [constraint: purchase_target_based_on_targe_purchase_target_based_on_id_fkey]; target_kpi_id -> target_kpi.id [constraint: purchase_target_based_on_target_kpi_rel_target_kpi_id_fkey]. Total foreign key re... | sql_introspection | relationships | intermediate | purchase_target_based_on_target_kpi_rel | |
How to work with sh.base.send.whatsapp.number.wizard fields? or What business logic is in sh.base.send.whatsapp.number.wizard? | To use the sh.base.send.whatsapp.number.wizard model, you need to provide values for required fields: whatsapp_mobile, message. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: whatsapp_mobile [required]; message [required]; id [readonly]; display_na... | orm_introspection | usage | intermediate | sh.base.send.whatsapp.number.wizard | |
Explain the account_analytic_tag_purchase_requisition_line_rel table schema. or What columns does account_analytic_tag_purchase_requisition_line_rel have? | The account_analytic_tag_purchase_requisition_line_rel table has 2 columns and 2 foreign key relationships. It stores data related to account analytic tag purchase requisition line rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaul... | sql_introspection | structure | basic | account_analytic_tag_purchase_requisition_line_rel | |
What tables are connected to locattion_matrix_rel_id? or What tables does locattion_matrix_rel_id reference? | Foreign keys in locattion_matrix_rel_id: loc_id -> rn_approval_matrix.id [constraint: locattion_matrix_rel_id_loc_id_fkey]; stock_location_id -> stock_location.id [constraint: locattion_matrix_rel_id_stock_location_id_fkey]. Total foreign key relationships: 2. Referenced tables: rn_approval_matrix, stock_location. | sql_introspection | relationships | intermediate | locattion_matrix_rel_id | |
Show me the fields of account.tax.template. or List all fields in the account.tax.template model. | The account.tax.template model has 25 fields. Field types distribution: many2one: 5, selection: 4, boolean: 4, many2many: 1, integer: 2, float: 1, one2many: 2, char: 3, datetime: 3. Computed fields: 2. Field details: chart_template_id (many2one) [required] -> account.chart.template [module: account]; type_tax_use (sele... | orm_introspection | field_inquiry | basic | account.tax.template | |
What computed fields exist in account.user.reminder.lines? or Describe the field structure of account.user.reminder.lines. | The account.user.reminder.lines model has 11 fields. Field types distribution: many2one: 3, many2many: 1, integer: 3, char: 1, datetime: 3. Computed fields: 3. Field details: account_line_id (many2one) -> account.user.reminder [module: equip3_accounting_masterdata]; user_ids (many2many) [required] -> res.users [module:... | orm_introspection | field_inquiry | basic | account.user.reminder.lines | |
Describe the many2many relations for calendar.attendee. or What are the relationships in calendar.attendee? | The calendar.attendee model has 5 relational fields: event_id -> calendar.event; partner_id -> res.partner; recurrence_id -> calendar.recurrence; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none. | orm_introspection | relationship | intermediate | calendar.attendee | |
What models are connected to ks.sales.forecast.result? or How does ks.sales.forecast.result relate to other models? | The ks.sales.forecast.result model has 5 relational fields: ks_forecast_id -> ks.sales.forecast; ks_product_id -> product.product; ks_partner_id -> res.partner; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none. | orm_introspection | relationship | intermediate | ks.sales.forecast.result | |
How is mail.followers used in the system? or Tell me about the mail.followers model. | The mail.followers model represents Document Followers in the ERP system. It contains 11 fields and is used to manage document followers data. Defined in module: mail. Key fields include: res_model, res_id, partner_id, channel_id, subtype_ids, name, email, is_active, id, display_name, __last_update. | orm_introspection | basic_info | basic | mail.followers | |
List all constraint names in assign_pr_wizard_purchase_request_line_rel. or What tables does assign_pr_wizard_purchase_request_line_rel reference? | Foreign keys in assign_pr_wizard_purchase_request_line_rel: assign_pr_wizard_id -> assign_pr_wizard.id [constraint: assign_pr_wizard_purchase_request_line_assign_pr_wizard_id_fkey]; purchase_request_line_id -> purchase_request_line.id [constraint: assign_pr_wizard_purchase_request_purchase_request_line_id_fkey]. Total ... | sql_introspection | relationships | intermediate | assign_pr_wizard_purchase_request_line_rel | |
How do I use the itr.approval.matrix model? or What operations can I perform on itr.approval.matrix? | To use the itr.approval.matrix model, you need to provide values for required fields: name, company_id, warehouse_id. Readonly fields: company_id, approval_line_count, activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_i... | orm_introspection | usage | intermediate | itr.approval.matrix | |
List all columns in pos_generate_efaktur_invoice. or What fields are available in pos_generate_efaktur_invoice? | Columns in pos_generate_efaktur_invoice: id (integer) [NOT NULL] [DEFAULT: nextval('pos_generate_efaktur_invoice_id_seq'::regclass)] [PRECISION: 32]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT:... | sql_introspection | columns | basic | pos_generate_efaktur_invoice | |
What computed fields exist in snailmail.letter.format.error? or What data can be stored in snailmail.letter.format.error? | The snailmail.letter.format.error model has 9 fields. Field types distribution: many2one: 3, boolean: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: message_id (many2one) -> mail.message [module: snailmail]; snailmail_cover (boolean) [module: snailmail]; id (integer) [readonly] [module: None]; ... | orm_introspection | field_inquiry | basic | snailmail.letter.format.error | |
What are common use cases for sh.pwa.config? or What fields are readonly in sh.pwa.config? | To use the sh.pwa.config model, you need to provide values for required fields: name, short_name, display. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [required] [has_default]; short_name [required] [has_default]; display [required] [has_de... | orm_introspection | usage | intermediate | sh.pwa.config | |
Show me the column structure of do_matrix_reject. or What columns have default values in do_matrix_reject? | Columns in do_matrix_reject: id (integer) [NOT NULL] [DEFAULT: nextval('do_matrix_reject_id_seq'::regclass)] [PRECISION: 32]; reason (text) [COMMENT: Reason]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] ... | sql_introspection | columns | basic | do_matrix_reject | |
List all relational fields in reset.view.arch.wizard. or What one2many fields are in reset.view.arch.wizard? | The reset.view.arch.wizard model has 4 relational fields: view_id -> ir.ui.view; compare_view_id -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none. | orm_introspection | relationship | intermediate | reset.view.arch.wizard | |
What modules define pos.cashbox.history? or Which fields in pos.cashbox.history are computed? | The pos.cashbox.history model is defined in module: equip3_pos_cashbox. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: save_balance_history. | orm_introspection | technical | advanced | pos.cashbox.history | |
What is stored in cust_deposit_history_rel? or Tell me about the cust_deposit_history_rel table. | The cust_deposit_history_rel table has 2 columns and 2 foreign key relationships. It stores data related to cust deposit history rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0. | sql_introspection | structure | basic | cust_deposit_history_rel | |
What are the column types in theme_ir_ui_view? or List all columns in theme_ir_ui_view. | Columns in theme_ir_ui_view: id (integer) [NOT NULL] [DEFAULT: nextval('theme_ir_ui_view_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; key (character varying) [COMMENT: Key]; type (character varying) [COMMENT: Type]; priority (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Pri... | sql_introspection | columns | basic | theme_ir_ui_view | |
What operations can I perform on crm.lead2opportunity.partner? or What are common use cases for crm.lead2opportunity.partner? | To use the crm.lead2opportunity.partner model, you need to provide values for required fields: lead_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: name [computed]; action [computed]; lead_id [required]; duplicated_lead_ids [computed]; partner_i... | orm_introspection | usage | intermediate | crm.lead2opportunity.partner | |
List all columns in project_project. or What are the column types in project_project? | Columns in project_project: id (integer) [NOT NULL] [DEFAULT: nextval('project_project_id_seq'::regclass)] [PRECISION: 32]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; access_token (character varying) [COMMENT: Security Token]; name (character varying) [NOT NULL] [COMMENT: Name]; de... | sql_introspection | columns | basic | project_project | |
What operations can I perform on pos.payment.method.key? or What business logic is in pos.payment.method.key? | To use the pos.payment.method.key model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]... | orm_introspection | usage | intermediate | pos.payment.method.key | |
What are the relationships in mrp.workorder? or What one2many fields are in mrp.workorder? | The mrp.workorder model has 28 relational fields: workcenter_id -> mrp.workcenter; product_id -> product.product; product_uom_id -> uom.uom; production_id -> mrp.production; production_bom_id -> mrp.bom; company_id -> res.company; leave_id -> resource.calendar.leaves; operation_id -> mrp.routing.workcenter; move_raw_id... | orm_introspection | relationship | intermediate | mrp.workorder | |
What business logic is in website.seo.metadata? or How to query website.seo.metadata data? | To use the website.seo.metadata model, you need to provide values for required fields: none. Readonly fields: is_seo_optimized, id, display_name, __last_update. Field usage details: is_seo_optimized [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [c... | orm_introspection | usage | intermediate | website.seo.metadata | |
Describe the columns of ks_message_wizard. or What are the column types in ks_message_wizard? | Columns in ks_message_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('ks_message_wizard_id_seq'::regclass)] [PRECISION: 32]; name (text) [COMMENT: Message]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32]... | sql_introspection | columns | basic | ks_message_wizard | |
What are the length constraints in pos_category_branch_rel? or Show me the column structure of pos_category_branch_rel. | Columns in pos_category_branch_rel: categ_id (integer) [NOT NULL] [PRECISION: 32]; branch_id (integer) [NOT NULL] [PRECISION: 32]. Total columns: 2. Statistics: 0 nullable, 0 with defaults, 0 with length constraints. | sql_introspection | columns | basic | pos_category_branch_rel | |
Which fields are required in product.attribute.custom.value? or What computed fields exist in product.attribute.custom.value? | The product.attribute.custom.value model has 11 fields. Field types distribution: char: 3, many2one: 4, integer: 1, datetime: 3. Computed fields: 3. Field details: name (char) [readonly] [compute: _compute_name] [not stored] [module: product]; custom_product_template_attribute_value_id (many2one) [required] -> product.... | orm_introspection | field_inquiry | basic | product.attribute.custom.value | |
What modules define cancel.tender.memory? or What is the module hierarchy for cancel.tender.memory? | The cancel.tender.memory model is defined in module: equip3_purchase_other_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: action_cancel_tender. | orm_introspection | technical | advanced | cancel.tender.memory | |
How does setu_inventory_xyz_analysis_bi_report relate to other tables? or Describe the relational structure of setu_inventory_xyz_analysis_bi_report. | Foreign keys in setu_inventory_xyz_analysis_bi_report: company_id -> res_company.id [constraint: setu_inventory_xyz_analysis_bi_report_company_id_fkey]; create_uid -> res_users.id [constraint: setu_inventory_xyz_analysis_bi_report_create_uid_fkey]; product_category_id -> product_category.id [constraint: setu_inventory_... | sql_introspection | relationships | intermediate | setu_inventory_xyz_analysis_bi_report | |
How to query stock.warehouse.orderpoint data? or What fields are readonly in stock.warehouse.orderpoint? | To use the stock.warehouse.orderpoint model, you need to provide values for required fields: product_id, product_min_qty, product_max_qty, qty_multiple, name, trigger, company_id, warehouse_id. Readonly fields: product_tmpl_id, product_category_id, product_uom, product_uom_name, allowed_location_ids, rule_ids, json_lea... | orm_introspection | usage | intermediate | stock.warehouse.orderpoint | |
What modules define report.equip3_pos_report.report_pos_payment? or What methods are available in report.equip3_pos_report.report_pos_payment? | The report.equip3_pos_report.report_pos_payment model is defined in module: equip3_pos_report. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _get_report_values. | orm_introspection | technical | advanced | report.equip3_pos_report.report_pos_payment | |
Show me the foreign key constraints of product_template_attribute_line. or Describe the relational structure of product_template_attribute_line. | Foreign keys in product_template_attribute_line: attribute_id -> product_attribute.id [constraint: product_template_attribute_line_attribute_id_fkey]; create_uid -> res_users.id [constraint: product_template_attribute_line_create_uid_fkey]; product_tmpl_id -> product_template.id [constraint: product_template_attribute_... | sql_introspection | relationships | intermediate | product_template_attribute_line | |
What indexes exist on stock_inventory_wizard_line? or Tell me about the stock_inventory_wizard_line table. | The stock_inventory_wizard_line table has 20 columns and 9 foreign key relationships. It stores data related to stock inventory wizard line in the system. The table has 1 indexes for performance optimization. Column types: integer: 11, character varying: 2, double precision: 3, boolean: 2, timestamp without time zone: ... | sql_introspection | structure | basic | stock_inventory_wizard_line | |
What are the technical details of pos.promotion.tebus.murah? or How is pos.promotion.tebus.murah implemented technically? | The pos.promotion.tebus.murah model is defined in module: equip3_pos_masterdata. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: create, write. | orm_introspection | technical | advanced | pos.promotion.tebus.murah | |
What are the foreign keys in website_track? or List all constraint names in website_track. | Foreign keys in website_track: page_id -> website_page.id [constraint: website_track_page_id_fkey]; product_id -> product_product.id [constraint: website_track_product_id_fkey]; visitor_id -> website_visitor.id [constraint: website_track_visitor_id_fkey]. Total foreign key relationships: 3. Referenced tables: product_p... | sql_introspection | relationships | intermediate | website_track | |
How to create records in theme.website.page? or What business logic is in theme.website.page? | To use the theme.website.page model, you need to provide values for required fields: view_id. Readonly fields: copy_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: view_id [required]; copy_ids [readonly] [no_copy]; id [readonly]; display_name [readonly] [comput... | orm_introspection | usage | intermediate | theme.website.page | |
What one2many fields are in kitchen.cooking.list? or How does kitchen.cooking.list relate to other models? | The kitchen.cooking.list model has 5 relational fields: company_id -> res.company; warehouse_id -> stock.warehouse; product_ids -> kitchen.cooking.list.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: product_ids. | orm_introspection | relationship | intermediate | kitchen.cooking.list | |
What are common use cases for account.deposit.return? or How to create records in account.deposit.return? | To use the account.deposit.return model, you need to provide values for required fields: return_amount, journal_id. Readonly fields: payment_difference, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: return_amount [required]; journal_id [required]; payment_differen... | orm_introspection | usage | intermediate | account.deposit.return |
End of preview.
Odoo/HashMicro Training Dataset
This dataset contains question-answer pairs generated from Odoo/HashMicro ERP system for training conversational AI models.
Dataset Details
Dataset Description
This synthetic dataset was automatically generated from Odoo/HashMicro ERP system database schema and model introspection. It contains 14065 examples covering various aspects of the ERP system including models, fields, relationships, and database structure.
- Curated by: Odoo/HashMicro Training Data Generator
- Language(s): English
- License: MIT
Dataset Sources
- Repository: Generated from Odoo/HashMicro ERP system
- Generator: AI Chat Agent Training Data Wizard
Uses
Direct Use
This dataset is designed for:
- Training conversational AI models about Odoo/HashMicro ERP systems
- Fine-tuning language models for ERP-specific question answering
- Creating chatbots that can assist with Odoo/HashMicro system queries
Out-of-Scope Use
This dataset should not be used for:
- General purpose question answering outside of ERP domain
- Production systems without proper validation
- Any use case requiring real user data
Dataset Structure
The dataset contains the following fields:
text: The input question about Odoo/HashMicro systemresponse: The corresponding answersource: Data source (orm_introspection or sql_introspection)category: Question category (basic_info, field_inquiry, relationship, technical, usage)complexity_level: Complexity level (basic, intermediate, advanced)model_name: Odoo model name (for ORM-based examples)table_name: Database table name (for SQL-based examples)
Data Splits
- Train: 9066 examples
- Validation: 4999 examples
Categories
The dataset covers the following categories: Various ERP-related topics
Sources
Data was generated from: Odoo/HashMicro system introspection
Complexity Levels
Basic to advanced levels
Dataset Creation
Curation Rationale
This dataset was created to enable AI models to understand and respond to questions about Odoo/HashMicro ERP systems. The synthetic generation ensures comprehensive coverage of system components while maintaining consistency and accuracy.
Source Data
Data Collection and Processing
Data was automatically generated through:
- ORM introspection of Odoo models and fields
- SQL schema analysis of database tables and relationships
- Automated question-answer pair generation using predefined patterns
- Quality scoring and filtering based on relevance and completeness
Who are the source data producers?
The source data comes from the Odoo/HashMicro ERP system itself through automated introspection and schema analysis.
Bias, Risks, and Limitations
- Dataset is synthetically generated and may not cover all real-world use cases
- Limited to the specific Odoo/HashMicro system configuration used for generation
- May contain technical jargon specific to ERP systems
- Quality depends on the underlying system's data completeness
Recommendations
Users should:
- Validate model outputs against actual system behavior
- Consider fine-tuning on domain-specific data for production use
- Be aware that synthetic data may not capture all nuances of real user queries
Citation
BibTeX:
@dataset{odoo_hashmicro_training_dataset,
title={Odoo/HashMicro Training Dataset},
author={AI Chat Agent Training Data Generator},
year={2024},
url={Generated from Odoo/HashMicro ERP system}
}
Dataset Card Contact
Generated by Odoo/HashMicro AI Chat Agent Training Data Wizard
- Downloads last month
- 12