What field types are used in project.task? or Describe the field structure of project.task.

Response: The project.task model has 142 fields. Field types distribution: boolean: 32, char: 19, html: 1, selection: 16, integer: 13, many2one: 21, many2many: 4, datetime: 6, date: 4, float: 15, one2many: 8, text: 2, binary: 1. Computed fields: 106. Field details: active (boolean) [module: project]; name (char) [required] [module: project]; description (html) [module: project]; priority (selection) [module: project]; sequence (integer) [module: project]; stage_id (many2one) -> project.task.type [compute: _compute_stage_id] [stored] [module: project]; tag_ids (many2many) -> project.tags [module: project]; kanban_state (selection) [required] [module: project]; kanban_state_label (char) [readonly] [compute: _compute_kanban_state_label] [not stored] [module: project]; create_date (datetime) [readonly] [module: project]; write_date (datetime) [readonly] [module: project]; date_end (datetime) [module: project]; date_assign (datetime) [readonly] [module: project]; date_deadline (date) [module: project]; date_last_stage_update (datetime) [readonly] [module: project]; project_id (many2one) -> project.project [compute: _compute_project_id] [stored] [module: project]; planned_hours (float) [module: project]; subtask_planned_hours (float) [readonly] [compute: _compute_subtask_planned_hours] [not stored] [module: project]; user_id (many2one) -> res.users [module: project]; partner_id (many2one) -> res.partner [compute: _compute_partner_id] [stored] [module: project]; partner_is_company (boolean) [readonly] [compute: <bound method Field._compute_related of project.task.partner_is_company>] [not stored] [module: project] [related: partner_id.is_company]; commercial_partner_id (many2one) [readonly] -> res.partner [compute: <bound method Field._compute_related of project.task.commercial_partner_id>] [not stored] [module: project] [related: partner_id.commercial_partner_id]; partner_email (char) [compute: _compute_partner_email] [stored] [module: project] [inverse: _inverse_partner_email]; partner_phone (char) [compute: _compute_partner_phone] [stored] [module: project] [inverse: _inverse_partner_phone]; ribbon_message (char) [readonly] [compute: _compute_ribbon_message] [not stored] [module: project]; partner_city (char) [compute: <bound method Field._compute_related of project.task.partner_city>] [not stored] [module: project] [related: partner_id.city] [inverse: <bound method Field._inverse_related of project.task.partner_city>]; manager_id (many2one) [readonly] -> res.users [compute: <bound method Field._compute_related of project.task.manager_id>] [not stored] [module: project] [related: project_id.user_id]; company_id (many2one) [required] -> res.company [compute: _compute_company_id] [stored] [module: project]; color (integer) [module: project]; user_email (char) [readonly] [compute: <bound method Field._compute_related of project.task.user_email>] [not stored] [module: project] [related: user_id.email]; attachment_ids (one2many) [readonly] -> ir.attachment [compute: _compute_attachment_ids] [not stored] [module: project]; displayed_image_id (many2one) -> ir.attachment [module: project]; legend_blocked (char) [readonly] [compute: <bound method Field._compute_related of project.task.legend_blocked>] [not stored] [module: project] [related: stage_id.legend_blocked]; legend_done (char) [readonly] [compute: <bound method Field._compute_related of project.task.legend_done>] [not stored] [module: project] [related: stage_id.legend_done]; legend_normal (char) [readonly] [compute: <bound method Field._compute_related of project.task.legend_normal>] [not stored] [module: project] [related: stage_id.legend_normal]; is_closed (boolean) [readonly] [compute: <bound method Field._compute_related of project.task.is_closed>] [not stored] [module: project] [related: stage_id.is_closed]; parent_id (many2one) -> project.task [module: project]; child_ids (one2many) -> project.task [module: project]; subtask_project_id (many2one) [readonly] -> project.project [compute: <bound method Field._compute_related of project.task.subtask_project_id>] [not stored] [module: project] [related: project_id.subtask_project_id]; allow_subtasks (boolean) [readonly] [compute: <bound method Field._compute_related of project.task.allow_subtasks>] [not stored] [module: project] [related: project_id.allow_subtasks]; subtask_count (integer) [readonly] [compute: _compute_subtask_count] [not stored] [module: project]; email_from (char) [compute: _compute_email_from] [stored] [module: project]; allowed_user_ids (many2many) -> res.users [compute: _compute_allowed_user_ids] [stored] [module: project]; project_privacy_visibility (selection) [readonly] [compute: <bound method Field._compute_related of project.task.project_privacy_visibility>] [not stored] [module: project] [related: project_id.privacy_visibility]; working_hours_open (float) [readonly] [compute: _compute_elapsed] [stored] [module: project]; working_hours_close (float) [readonly] [compute: _compute_elapsed] [stored] [module: project]; working_days_open (float) [readonly] [compute: _compute_elapsed] [stored] [module: project]; working_days_close (float) [readonly] [compute: _compute_elapsed] [stored] [module: project]; website_message_ids (one2many) -> mail.message [module: project]; allow_recurring_tasks (boolean) [readonly] [compute: <bound method Field._compute_related of project.task.allow_recurring_tasks>] [not stored] [module: project] [related: project_id.allow_recurring_tasks]; recurring_task (boolean) [module: project]; recurring_count (integer) [readonly] [compute: _compute_recurring_count] [not stored] [module: project]; recurrence_id (many2one) -> project.task.recurrence [module: project]; recurrence_update (selection) [module: project]; recurrence_message (char) [readonly] [compute: _compute_recurrence_message] [not stored] [module: project]; repeat_interval (integer) [compute: _compute_repeat] [not stored] [module: project]; repeat_unit (selection) [compute: _compute_repeat] [not stored] [module: project]; repeat_type (selection) [compute: _compute_repeat] [not stored] [module: project]; repeat_until (date) [compute: _compute_repeat] [not stored] [module: project]; repeat_number (integer) [compute: _compute_repeat] [not stored] [module: project]; repeat_on_month (selection) [compute: _compute_repeat] [not stored] [module: project]; repeat_on_year (selection) [compute: _compute_repeat] [not stored] [module: project]; mon (boolean) [compute: _compute_repeat] [not stored] [module: project]; tue (boolean) [compute: _compute_repeat] [not stored] [module: project]; wed (boolean) [compute: _compute_repeat] [not stored] [module: project]; thu (boolean) [compute: _compute_repeat] [not stored] [module: project]; fri (boolean) [compute: _compute_repeat] [not stored] [module: project]; sat (boolean) [compute: _compute_repeat] [not stored] [module: project]; sun (boolean) [compute: _compute_repeat] [not stored] [module: project]; repeat_day (selection) [compute: _compute_repeat] [not stored] [module: project]; repeat_week (selection) [compute: _compute_repeat] [not stored] [module: project]; repeat_weekday (selection) [compute: _compute_repeat] [not stored] [module: project]; repeat_month (selection) [compute: _compute_repeat] [not stored] [module: project]; repeat_show_dow (boolean) [readonly] [compute: _compute_repeat_visibility] [not stored] [module: project]; repeat_show_day (boolean) [readonly] [compute: _compute_repeat_visibility] [not stored] [module: project]; repeat_show_week (boolean) [readonly] [compute: _compute_repeat_visibility] [not stored] [module: project]; repeat_show_month (boolean) [readonly] [compute: _compute_repeat_visibility] [not stored] [module: project]; analytic_account_active (boolean) [readonly] [compute: _compute_analytic_account_active] [not stored] [module: hr_timesheet]; allow_timesheets (boolean) [readonly] [compute: <bound method Field._compute_related of project.task.allow_timesheets>] [not stored] [module: hr_timesheet] [related: project_id.allow_timesheets]; remaining_hours (float) [readonly] [compute: _compute_remaining_hours] [stored] [module: hr_timesheet]; effective_hours (float) [readonly] [compute: _compute_effective_hours] [stored] [module: hr_timesheet]; total_hours_spent (float) [readonly] [compute: _compute_total_hours_spent] [stored] [module: hr_timesheet]; progress (float) [readonly] [compute: _compute_progress_hours] [stored] [module: hr_timesheet]; overtime (float) [readonly] [compute: _compute_progress_hours] [stored] [module: hr_timesheet]; subtask_effective_hours (float) [readonly] [compute: _compute_subtask_effective_hours] [stored] [module: hr_timesheet]; timesheet_ids (one2many) -> account.analytic.line [module: hr_timesheet]; encode_uom_in_days (boolean) [readonly] [compute: _compute_encode_uom_in_days] [not stored] [module: hr_timesheet]; sale_line_id (many2one) -> sale.order.line [compute: _compute_sale_line] [stored] [module: sale_project]; project_sale_order_id (many2one) [readonly] -> sale.order [compute: <bound method Field._compute_related of project.task.project_sale_order_id>] [not stored] [module: sale_project] [related: project_id.sale_order_id]; invoice_count (integer) [readonly] [compute: <bound method Field._compute_related of project.task.invoice_count>] [not stored] [module: sale_project] [related: sale_order_id.invoice_count]; task_to_invoice (boolean) [readonly] [compute: _compute_task_to_invoice] [not stored] [module: sale_project]; sale_order_id (many2one) -> sale.order [compute: _compute_sale_order_id] [stored] [module: sale_timesheet]; analytic_account_id (many2one) [readonly] -> account.analytic.account [compute: <bound method Field._compute_related of project.task.analytic_account_id>] [not stored] [module: sale_timesheet] [related: sale_order_id.analytic_account_id]; bill_type (selection) [readonly] [compute: <bound method Field._compute_related of project.task.bill_type>] [not stored] [module: sale_timesheet] [related: project_id.bill_type]; pricing_type (selection) [readonly] [compute: <bound method Field._compute_related of project.task.pricing_type>] [not stored] [module: sale_timesheet] [related: project_id.pricing_type]; is_project_map_empty (boolean) [readonly] [compute: _compute_is_project_map_empty] [not stored] [module: sale_timesheet]; has_multi_sol (boolean) [readonly] [compute: _compute_has_multi_sol] [not stored] [module: sale_timesheet]; allow_billable (boolean) [readonly] [compute: <bound method Field._compute_related of project.task.allow_billable>] [not stored] [module: sale_timesheet] [related: project_id.allow_billable]; display_create_order (boolean) [readonly] [compute: _compute_display_create_order] [not stored] [module: sale_timesheet]; timesheet_product_id (many2one) -> product.product [module: sale_timesheet]; non_allow_billable (boolean) [module: sale_timesheet]; remaining_hours_so (float) [readonly] [compute: _compute_remaining_hours_so] [not stored] [module: sale_timesheet]; remaining_hours_available (boolean) [readonly] [compute: <bound method Field._compute_related of project.task.remaining_hours_available>] [not stored] [module: sale_timesheet] [related: sale_line_id.remaining_hours_available]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of project.task.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of project.task.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of project.task.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of project.task.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of project.task.activity_type_icon>] [not stored] [module: mail] [related: activity_ids.icon]; activity_date_deadline (date) [readonly] [compute: _compute_activity_date_deadline] [not stored] [module: mail]; my_activity_date_deadline (date) [readonly] [compute: _compute_my_activity_date_deadline] [not stored] [module: mail]; activity_summary (char) [compute: <bound method Field._compute_related of project.task.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of project.task.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; email_cc (char) [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; rating_ids (one2many) -> rating.rating [module: rating]; rating_last_value (float) [readonly] [compute: _compute_rating_last_value] [stored] [module: rating]; rating_last_feedback (text) [readonly] [compute: <bound method Field._compute_related of project.task.rating_last_feedback>] [not stored] [module: rating] [related: rating_ids.feedback]; rating_last_image (binary) [readonly] [compute: <bound method Field._compute_related of project.task.rating_last_image>] [not stored] [module: rating] [related: rating_ids.rating_image]; rating_count (integer) [readonly] [compute: _compute_rating_stats] [not stored] [module: rating]; rating_avg (float) [readonly] [compute: _compute_rating_stats] [not stored] [module: rating]; access_url (char) [readonly] [compute: _compute_access_url] [not stored] [module: portal]; access_token (char) [module: portal]; access_warning (text) [readonly] [compute: _compute_access_warning] [not stored] [module: portal]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What methods are available in export.retur.pajak.masukan? or Which fields in export.retur.pajak.masukan are computed?

Response: The export.retur.pajak.masukan model is defined in module: equip3_accounting_efaktur. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _checkvalid, confirm.


How to work with report.equip3_accounting_operation.report_statement_temp fields? or 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. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Describe the many2many relations for product.attribute.value. or How does product.attribute.value relate to other models?

Response: The product.attribute.value model has 4 relational fields: attribute_id -> product.attribute; pav_attribute_line_ids -> product.template.attribute.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: pav_attribute_line_ids. One2many fields: none.


Describe the columns of digest_digest. or What columns have default values in digest_digest?

Response: Columns in digest_digest: id (integer) [NOT NULL] [DEFAULT: nextval('digest_digest_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; periodicity (character varying) [NOT NULL] [COMMENT: Periodicity]; next_run_date (date) [COMMENT: Next Send Date]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; state (character varying) [COMMENT: Status]; kpi_res_users_connected (boolean) [COMMENT: Connected Users]; kpi_mail_message_total (boolean) [COMMENT: Messages]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; kpi_account_total_revenue (boolean) [COMMENT: Revenue]; kpi_all_sale_total (boolean) [COMMENT: All Sales]; kpi_crm_lead_created (boolean) [COMMENT: New Leads/Opportunities]; kpi_crm_opportunities_won (boolean) [COMMENT: Opportunities Won]; kpi_livechat_rating (boolean) [COMMENT: % of Happiness]; kpi_livechat_conversations (boolean) [COMMENT: Conversations handled]; kpi_livechat_response (boolean) [COMMENT: Time to answer(sec)]; kpi_project_task_opened (boolean) [COMMENT: Open Tasks]; kpi_website_sale_total (boolean) [COMMENT: eCommerce Sales]; kpi_pos_total (boolean) [COMMENT: POS Sales]. Total columns: 22. Statistics: 19 nullable, 1 with defaults, 0 with length constraints.


List all fields in the web.environment.ribbon.backend model. or What fields does web.environment.ribbon.backend have?

Response: The web.environment.ribbon.backend model has 3 fields. Field types distribution: integer: 1, char: 1, datetime: 1. Computed fields: 2. Field details: id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


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

Response: The product_category_setu_inventory_age_breakdown_report_rel table has 2 columns and 2 foreign key relationships. It stores data related to product category setu inventory age breakdown report rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


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

Response: Foreign keys in res_country: address_view_id -> ir_ui_view.id [constraint: res_country_address_view_id_fkey]; create_uid -> res_users.id [constraint: res_country_create_uid_fkey]; currency_id -> res_currency.id [constraint: res_country_currency_id_fkey]; write_uid -> res_users.id [constraint: res_country_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: ir_ui_view, res_currency, res_users.


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

Response: Columns in hr_plan_activity_type: id (integer) [NOT NULL] [DEFAULT: nextval('hr_plan_activity_type_id_seq'::regclass)] [PRECISION: 32]; activity_type_id (integer) [PRECISION: 32] [COMMENT: Activity Type]; summary (character varying) [COMMENT: Summary]; responsible (character varying) [NOT NULL] [COMMENT: Responsible]; responsible_id (integer) [PRECISION: 32] [COMMENT: Responsible Person]; note (text) [COMMENT: Note]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 10. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


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

Response: Columns in account_move_template_line: id (integer) [NOT NULL] [DEFAULT: nextval('account_move_template_line_id_seq'::regclass)] [PRECISION: 32]; move_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Journal Entry]; move_name (character varying) [COMMENT: Number]; date (date) [COMMENT: Date]; ref (character varying) [COMMENT: Reference]; parent_state (character varying) [COMMENT: Status]; journal_id (integer) [PRECISION: 32] [COMMENT: Journal]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; company_currency_id (integer) [PRECISION: 32] [COMMENT: Company Currency]; account_id (integer) [PRECISION: 32] [COMMENT: Account]; account_root_id (integer) [PRECISION: 32] [COMMENT: Account Root]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; name (character varying) [COMMENT: Label]; quantity (numeric) [COMMENT: Quantity]; price_unit (numeric) [COMMENT: Unit Price]; discount (numeric) [COMMENT: Discount (%)]; debit (numeric) [COMMENT: Debit]; credit (numeric) [COMMENT: Credit]; balance (numeric) [COMMENT: Balance]; amount_currency (numeric) [COMMENT: Amount in Currency]; price_subtotal (numeric) [COMMENT: Subtotal]; price_total (numeric) [COMMENT: Total]; reconciled (boolean) [COMMENT: Reconciled]; blocked (boolean) [COMMENT: No Follow-up]; date_maturity (date) [COMMENT: Due Date]; currency_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Currency]; partner_id (integer) [PRECISION: 32] [COMMENT: Partner]; product_uom_id (integer) [PRECISION: 32] [COMMENT: Unit of Measure]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; reconcile_model_id (integer) [PRECISION: 32] [COMMENT: Reconciliation Model]; payment_id (integer) [PRECISION: 32] [COMMENT: Originator Payment]; statement_line_id (integer) [PRECISION: 32] [COMMENT: Originator Statement Line]; statement_id (integer) [PRECISION: 32] [COMMENT: Statement]; tax_line_id (integer) [PRECISION: 32] [COMMENT: Originator Tax]; tax_group_id (integer) [PRECISION: 32] [COMMENT: Originator tax group]; tax_base_amount (numeric) [COMMENT: Base Amount]; tax_exigible (boolean) [COMMENT: Appears in VAT report]; tax_repartition_line_id (integer) [PRECISION: 32] [COMMENT: Originator Tax Distribution Line]; tax_audit (character varying) [COMMENT: Tax Audit String]; amount_residual (numeric) [COMMENT: Residual Amount]; amount_residual_currency (numeric) [COMMENT: Residual Amount in Currency]; full_reconcile_id (integer) [PRECISION: 32] [COMMENT: Matching]; matching_number (character varying) [COMMENT: Matching #]; analytic_account_id (integer) [PRECISION: 32] [COMMENT: Analytic Account]; display_type (character varying) [COMMENT: Display Type]; is_rounding_line (boolean) [COMMENT: Is Rounding Line]; exclude_from_invoice_tab (boolean) [COMMENT: Exclude From Invoice Tab]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 51. Statistics: 48 nullable, 1 with defaults, 0 with length constraints.


What fields are available in stock_move_line? or What columns have default values in stock_move_line?

Response: Columns in stock_move_line: id (integer) [NOT NULL] [DEFAULT: nextval('stock_move_line_id_seq'::regclass)] [PRECISION: 32]; picking_id (integer) [PRECISION: 32] [COMMENT: Transfer]; move_id (integer) [PRECISION: 32] [COMMENT: Stock Move]; company_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Company]; product_id (integer) [PRECISION: 32] [COMMENT: Product]; product_uom_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Unit of Measure]; product_qty (numeric) [COMMENT: Real Reserved Quantity]; product_uom_qty (numeric) [NOT NULL] [COMMENT: Reserved]; qty_done (numeric) [COMMENT: Done]; package_id (integer) [PRECISION: 32] [COMMENT: Source Package]; package_level_id (integer) [PRECISION: 32] [COMMENT: Package Level]; lot_id (integer) [PRECISION: 32] [COMMENT: Lot/Serial Number]; lot_name (character varying) [COMMENT: Lot/Serial Number Name]; result_package_id (integer) [PRECISION: 32] [COMMENT: Destination Package]; date (timestamp without time zone) [NOT NULL] [COMMENT: Date]; owner_id (integer) [PRECISION: 32] [COMMENT: From Owner]; location_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: From]; location_dest_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: To]; state (character varying) [COMMENT: Status]; reference (character varying) [COMMENT: Reference]; description_picking (text) [COMMENT: Description picking]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; expiration_date (timestamp without time zone) [COMMENT: Expiration Date]; workorder_id (integer) [PRECISION: 32] [COMMENT: Work Order]; production_id (integer) [PRECISION: 32] [COMMENT: Production Order]; sequence (character varying) [COMMENT: Sequence]; move_line_sequence (integer) [PRECISION: 32] [COMMENT: No]; is_quant_update (boolean) [COMMENT: Quant Update]; force_to_reserve_qty (numeric) [COMMENT: Force To Reserve Qty]; source_move_id (integer) [PRECISION: 32] [COMMENT: Source Move]; scrap_sale_price (double precision) [PRECISION: 53] [COMMENT: Sale Price]; is_low_stock (boolean) [COMMENT: Is Low Stock]; exp_date (timestamp without time zone) [COMMENT: Expiration Time]; kitchen_id (integer) [PRECISION: 32] [COMMENT: Kitchen Order]; finish_good_rework_id (integer) [PRECISION: 32] [COMMENT: Kitchen Order]; assembly_id (integer) [PRECISION: 32] [COMMENT: Asemble Order]; remark (text) [COMMENT: Remark]; pos_branch_id (integer) [PRECISION: 32] [COMMENT: Branch]; scrap_return_move_id (integer) [PRECISION: 32] [COMMENT: Scrap Return ID]. Total columns: 42. Statistics: 35 nullable, 1 with defaults, 0 with length constraints.


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

Response: Columns in res_users_apikeys: id (integer) [NOT NULL] [DEFAULT: nextval('res_users_apikeys_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL]; user_id (integer) [NOT NULL] [PRECISION: 32]; scope (character varying); index (character varying) [LENGTH: 8]; key (character varying); create_date (timestamp without time zone) [DEFAULT: timezone('utc'::text, now())]. Total columns: 7. Statistics: 4 nullable, 2 with defaults, 1 with length constraints.


Show me the relational structure of invoice.recurring. or What models are connected to invoice.recurring?

Response: The invoice.recurring model has 23 relational fields: partner_id -> res.partner; order_line -> invoice.recurring.line; sh_move_line -> recurring.move.line; journal_id -> account.journal; company_id -> res.company; created_by -> res.users; branch_id -> res.branch; analytic_group_ids -> account.analytic.tag; invoice_ids -> account.move; 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_group_ids, invoice_ids, message_partner_ids, message_channel_ids. One2many fields: order_line, sh_move_line, activity_ids, message_follower_ids, message_ids, website_message_ids.


Tell me about the purchase.report model. or What does the purchase.report model represent?

Response: The purchase.report model represents Purchase Report in the ERP system. It contains 38 fields and is used to manage purchase report data. Defined in module: purchase. Key fields include: date_order, state, product_id, partner_id, date_approve, product_uom, company_id, currency_id, user_id, delay, delay_pass, avg_days_to_purchase, price_total, price_average, nbr_lines, category_id, product_tmpl_id, country_id, fiscal_position_id, account_analytic_id, commercial_partner_id, weight, volume, order_id, untaxed_total, qty_ordered, qty_received, qty_billed, qty_to_be_billed, team_id, picking_type_id, avg_receipt_delay, effective_date, branch_id, days_to_approve, id, display_name, __last_update.


Describe the implementation of project.create.invoice. or Which fields in project.create.invoice are computed?

Response: The project.create.invoice model is defined in module: sale_timesheet. It has 5 computed fields: _candidate_orders, amount_to_invoice, currency_id, display_name, __last_update. Stored computed fields: none. Related fields: currency_id -> sale_order_id.currency_id. Original module methods: default_get, _compute_candidate_orders, _compute_amount_to_invoice, action_create_invoice.


What operations can I perform on purchase.order.report? or How to work with purchase.order.report fields?

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. Field usage details: start_date [required] [has_default]; end_date [required] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How to query base_import.mapping data? or What business logic is in base_import.mapping?

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. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: The budget_budget_budget_line table has 14 columns and 6 foreign key relationships. It stores data related to budget budget budget line in the system. The table has 2 indexes for performance optimization. Column types: integer: 7, date: 3, numeric: 1, character varying: 1, timestamp without time zone: 2. Nullable columns: 9, columns with defaults: 1.


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

Response: Foreign keys in sale_adv_wizard_product_line: create_uid -> res_users.id [constraint: sale_adv_wizard_product_line_create_uid_fkey]; product_id -> product_product.id [constraint: sale_adv_wizard_product_line_product_id_fkey]; sale_adv_wizard_id -> sale_adv_wizard.id [constraint: sale_adv_wizard_product_line_sale_adv_wizard_id_fkey]; write_uid -> res_users.id [constraint: sale_adv_wizard_product_line_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: product_product, res_users, sale_adv_wizard.


What models are connected to res.users.log? or List all relational fields in res.users.log.

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


What business logic is in account.multipayment.debit? or How to create records in account.multipayment.debit?

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


What does the change.password.user model represent? or What is the change.password.user model?

Response: The change.password.user model represents User, Change Password Wizard in the ERP system. It contains 11 fields and is used to manage user, change password wizard data. Defined in module: base. Key fields include: wizard_id, user_id, user_login, new_passwd, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


Can you explain the purpose of sale.order.pricelist.wizard.line? or Describe the sale.order.pricelist.wizard.line model in Odoo.

Response: The sale.order.pricelist.wizard.line model represents Pricelist Wizard in the ERP system. It contains 15 fields and is used to manage pricelist wizard data. Defined in module: sh_sale_pricelist. Key fields include: pricelist_id, sh_pricelist_id, sh_unit_measure, sh_unit_price, sh_unit_cost, sh_margin, sh_margin_per, line_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the website.robots model? or Can you explain the purpose of website.robots?

Response: The website.robots model represents Robots.txt Editor in the ERP system. It contains 8 fields and is used to manage robots.txt editor data. Defined in module: website. Key fields include: content, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the account.pettycash.voucher.wizard.line model? or How is account.pettycash.voucher.wizard.line used in the system?

Response: The account.pettycash.voucher.wizard.line model represents Account Petty Cash Voucher Wizard Line in the ERP system. It contains 21 fields and is used to manage account petty cash voucher wizard line data. Defined in module: equip3_accounting_pettycash. Key fields include: line_id, product_id, name, expense_account, quantity, price_unit, tax_ids, taxes, price_total, amount, currency_id, company_id, partner_id, expense_account_state, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What are the column types in setu_inventory_xyz_analysis_report? or What fields are available in setu_inventory_xyz_analysis_report?

Response: Columns in setu_inventory_xyz_analysis_report: id (integer) [NOT NULL] [DEFAULT: nextval('setu_inventory_xyz_analysis_report_id_seq'::regclass)] [PRECISION: 32]; inventory_analysis_type (character varying) [COMMENT: XYZ Classification]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; company_id (integer) [PRECISION: 32] [COMMENT: Company]. Total columns: 7. Statistics: 6 nullable, 1 with defaults, 0 with length constraints.


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

Response: Columns in purchase_request_wizard: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_request_wizard_id_seq'::regclass)] [PRECISION: 32]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 5. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


How does sh.purchase.product.indent.wizard relate to other models? or What one2many fields are in 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. One2many fields: none.


What foreign keys exist in account.payment.reconcile.line? or What are the relationships in account.payment.reconcile.line?

Response: The account.payment.reconcile.line model has 6 relational fields: reconcile_line_id -> account.payment.reconcile; currency_id -> res.currency; partner_id -> res.partner; invoice_id -> account.move; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


How to query pos.gift.card.use data? or What are common use cases for pos.gift.card.use?

Response: To use the pos.gift.card.use 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. Field usage details: card_id [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: Columns in ir_ui_view: id (integer) [NOT NULL] [DEFAULT: nextval('ir_ui_view_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: View Name]; model (character varying) [COMMENT: Model]; key (character varying) [COMMENT: Key]; priority (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Sequence]; type (character varying) [COMMENT: View Type]; arch_db (text) [COMMENT: Arch Blob]; arch_fs (character varying) [COMMENT: Arch Filename]; arch_updated (boolean) [COMMENT: Modified Architecture]; arch_prev (text) [COMMENT: Previous View Architecture]; inherit_id (integer) [PRECISION: 32] [COMMENT: Inherited View]; field_parent (character varying) [COMMENT: Child Field]; mode (character varying) [NOT NULL] [COMMENT: View inheritance mode]; active (boolean) [COMMENT: Active]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]; customize_show (boolean) [COMMENT: Show As Optional Inherit]; website_meta_title (character varying) [COMMENT: Website meta title]; website_meta_description (text) [COMMENT: Website meta description]; website_meta_keywords (character varying) [COMMENT: Website meta keywords]; website_meta_og_img (character varying) [COMMENT: Website opengraph image]; seo_name (character varying) [COMMENT: Seo name]; website_id (integer) [PRECISION: 32] [COMMENT: Website]; track (boolean) [COMMENT: Track]; visibility (character varying) [COMMENT: Visibility]; visibility_password (character varying) [COMMENT: Visibility Password]; theme_template_id (integer) [PRECISION: 32] [COMMENT: Theme Template]. Total columns: 29. Statistics: 25 nullable, 1 with defaults, 0 with length constraints.


What tables are connected to service_work_order_line? or Describe the relational structure of service_work_order_line.

Response: Foreign keys in service_work_order_line: create_uid -> res_users.id [constraint: service_work_order_line_create_uid_fkey]; order_line_id -> purchase_order_line.id [constraint: service_work_order_line_order_line_id_fkey]; product_id -> product_product.id [constraint: service_work_order_line_product_id_fkey]; swo_id -> service_work_order.id [constraint: service_work_order_line_swo_id_fkey]; write_uid -> res_users.id [constraint: service_work_order_line_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: product_product, service_work_order, purchase_order_line, res_users.


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

Response: Foreign keys in credit_note_product_lines: create_uid -> res_users.id [constraint: credit_note_product_lines_create_uid_fkey]; credit_note_id -> dev_credit_note_wizard.id [constraint: credit_note_product_lines_credit_note_id_fkey]; product_id -> product_product.id [constraint: credit_note_product_lines_product_id_fkey]; purchase_line_id -> purchase_order_line.id [constraint: credit_note_product_lines_purchase_line_id_fkey]; sale_line_id -> sale_order_line.id [constraint: credit_note_product_lines_sale_line_id_fkey]; write_uid -> res_users.id [constraint: credit_note_product_lines_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: product_product, dev_credit_note_wizard, purchase_order_line, res_users, sale_order_line.


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

Response: Columns in ir_sequence_date_range: id (integer) [NOT NULL] [DEFAULT: nextval('ir_sequence_date_range_id_seq'::regclass)] [PRECISION: 32]; date_from (date) [NOT NULL] [COMMENT: From]; date_to (date) [NOT NULL] [COMMENT: To]; sequence_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Main Sequence]; number_next (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Next Number]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 9. Statistics: 4 nullable, 1 with defaults, 0 with length constraints.


How is asset.depreciation.confirmation.wizard used in the system? or 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. Defined in module: om_account_asset. Key fields include: date, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How do I use the sh.sale.analysis.wizard model? or How to create records in 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. Field usage details: sh_end_date [required] [has_default]; sh_partner_ids [required]; sh_start_date [required] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How many columns are in project_tags_project_task_rel? or What columns does project_tags_project_task_rel have?

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


What does the internal.transfer.line model represent? or 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. Defined in module: equip3_inventory_operation. 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.


Which columns are nullable in purchase_report_representative_xls? or What data types are used in purchase_report_representative_xls?

Response: Columns in purchase_report_representative_xls: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_report_representative_xls_id_seq'::regclass)] [PRECISION: 32]; file_name (character varying) [LENGTH: 64] [COMMENT: Excel File]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 6. Statistics: 5 nullable, 1 with defaults, 1 with length constraints.


What are the relationships in fast.financial.report.query? or Describe the many2many relations for fast.financial.report.query.

Response: The fast.financial.report.query model has no explicit relational fields defined in its field metadata.


Tell me about the partial.quantity.done model. or Describe the partial.quantity.done model in Odoo.

Response: The partial.quantity.done model represents Partial Quantity Done in the ERP system. It contains 10 fields and is used to manage partial quantity done data. Defined in module: equip3_inventory_operation. Key fields include: product_id, done_qty, move_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The crm_quotation_partner table has 8 columns and 4 foreign key relationships. It stores data related to crm quotation partner 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: 5, columns with defaults: 1.


Tell me about the sh.account.period model. or Can you explain the purpose of sh.account.period?

Response: The sh.account.period model represents Fiscal Period in the ERP system. It contains 17 fields and is used to manage fiscal period data. Defined in module: sh_sync_fiscal_year. Key fields include: name, code, date_start, date_end, fiscal_year_id, special, state, branch_id, valid_value, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What indexes exist on pos_category_config_rel? or How many columns are in pos_category_config_rel?

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


What field types are used in sh.report.section? or What fields does sh.report.section have?

Response: The sh.report.section model has 19 fields. Field types distribution: char: 4, selection: 2, text: 1, html: 1, many2one: 3, many2many: 1, integer: 3, boolean: 1, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: sh_all_in_one_purchase_tools]; type (selection) [required] [module: sh_all_in_one_purchase_tools]; content_text (text) [module: sh_all_in_one_purchase_tools]; content_html (html) [module: sh_all_in_one_purchase_tools]; type_id (many2one) -> sh.report.template [module: sh_all_in_one_purchase_tools]; check_ids (many2many) -> sh.edit.title [module: sh_all_in_one_purchase_tools]; text_size (integer) [required] [module: sh_all_in_one_purchase_tools]; color (char) [module: sh_all_in_one_purchase_tools]; borders (boolean) [module: sh_all_in_one_purchase_tools]; border_size (integer) [required] [module: sh_all_in_one_purchase_tools]; border_style (selection) [required] [module: sh_all_in_one_purchase_tools]; border_color (char) [required] [module: sh_all_in_one_purchase_tools]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


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

Response: Foreign keys in account_aged_trial_balance: company_id -> res_company.id [constraint: account_aged_trial_balance_company_id_fkey]; create_uid -> res_users.id [constraint: account_aged_trial_balance_create_uid_fkey]; report_currency_id -> res_currency.id [constraint: account_aged_trial_balance_report_currency_id_fkey]; write_uid -> res_users.id [constraint: account_aged_trial_balance_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_currency, res_users, res_company.


How do I use the acrux.chat.connector model? or 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. Field usage details: name [required]; sequence [required] [has_default]; company_id [required] [has_default]; endpoint [required] [has_default]; apikey [required] [has_default]; uuid [required] [has_default] [no_copy]; border_color [required] [has_default]; sale_report_id [required] [has_default]; connector_type [required] [has_default]; qc_channel [required] [has_default]; qc_webhook_url [readonly]; connection_status [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What tables are connected to res_users_identitycheck? or Describe the relational structure of res_users_identitycheck.

Response: Foreign keys in res_users_identitycheck: create_uid -> res_users.id [constraint: res_users_identitycheck_create_uid_fkey]; write_uid -> res_users.id [constraint: res_users_identitycheck_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Describe the many2many relations for barcode.configuration. or What one2many fields are in 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. One2many fields: none.


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

Response: The pos_order table has 104 columns and 36 foreign key relationships. It stores data related to pos order in the system. The table has 6 indexes for performance optimization. Column types: integer: 40, character varying: 13, timestamp without time zone: 7, numeric: 9, text: 2, boolean: 23, double precision: 9, date: 1. Nullable columns: 95, columns with defaults: 1.


What methods are available in account.user.reminder.lines? or How is account.user.reminder.lines implemented technically?

Response: The account.user.reminder.lines model is defined in module: equip3_accounting_masterdata. It has 3 computed fields: sequence2, display_name, __last_update. Stored computed fields: sequence2. Related fields: sequence2 -> sequence. Original module methods: default_get, unlink, create.


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

Response: Foreign keys in config_stock_picking_type_rel: config_id -> pos_config.id [constraint: config_stock_picking_type_rel_config_id_fkey]; stock_picking_type_id -> stock_picking_type.id [constraint: config_stock_picking_type_rel_stock_picking_type_id_fkey]. Total foreign key relationships: 2. Referenced tables: stock_picking_type, pos_config.


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

Response: Foreign keys in pos_promotion_tebus_murah_specific_product_rel: pos_promotion_tebus_murah_id -> pos_promotion_tebus_murah.id [constraint: pos_promotion_tebus_murah_spe_pos_promotion_tebus_murah_id_fkey]; product_id -> product_product.id [constraint: pos_promotion_tebus_murah_specific_product_rel_product_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, pos_promotion_tebus_murah.


List all constraint names in sh_custom_tab_purchase. or What are the foreign keys in sh_custom_tab_purchase?

Response: Foreign keys in sh_custom_tab_purchase: create_uid -> res_users.id [constraint: sh_custom_tab_purchase_create_uid_fkey]; view_id -> ir_ui_view.id [constraint: sh_custom_tab_purchase_view_id_fkey]; write_uid -> res_users.id [constraint: sh_custom_tab_purchase_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: ir_ui_view, res_users.


Can you explain the purpose of stock.immediate.transfer? or What is the stock.immediate.transfer model?

Response: The stock.immediate.transfer model represents Immediate Transfer in the ERP system. It contains 10 fields and is used to manage immediate transfer data. Defined in module: stock. Key fields include: pick_ids, show_transfers, immediate_transfer_line_ids, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What does the coupon.reward model represent? or Can you explain the purpose of coupon.reward?

Response: The coupon.reward model represents Coupon Reward in the ERP system. It contains 19 fields and is used to manage coupon reward data. Defined in module: coupon. 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.


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

Response: Foreign keys in ir_ui_menu: create_uid -> res_users.id [constraint: ir_ui_menu_create_uid_fkey]; equip_category_id -> ir_ui_menu_category.id [constraint: ir_ui_menu_equip_category_id_fkey]; parent_id -> ir_ui_menu.id [constraint: ir_ui_menu_parent_id_fkey]; write_uid -> res_users.id [constraint: ir_ui_menu_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: ir_ui_menu, ir_ui_menu_category, res_users.


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

Response: Foreign keys in finish_good_rework: bom_id -> mrp_bom.id [constraint: finish_good_rework_bom_id_fkey]; branch_id -> res_branch.id [constraint: finish_good_rework_branch_id_fkey]; company_id -> res_company.id [constraint: finish_good_rework_company_id_fkey]; create_uid -> res_users.id [constraint: finish_good_rework_create_uid_fkey]; location_dest_id -> stock_location.id [constraint: finish_good_rework_location_dest_id_fkey]; location_src_id -> stock_location.id [constraint: finish_good_rework_location_src_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: finish_good_rework_message_main_attachment_id_fkey]; picking_type_id -> stock_picking_type.id [constraint: finish_good_rework_picking_type_id_fkey]; procurement_group_id -> procurement_group.id [constraint: finish_good_rework_procurement_group_id_fkey]; product_uom_id -> uom_uom.id [constraint: finish_good_rework_product_uom_id_fkey]; production_location_id -> stock_location.id [constraint: finish_good_rework_production_location_id_fkey]; warehouse_id -> stock_warehouse.id [constraint: finish_good_rework_warehouse_id_fkey]; write_uid -> res_users.id [constraint: finish_good_rework_write_uid_fkey]. Total foreign key relationships: 13. Referenced tables: stock_warehouse, mrp_bom, stock_picking_type, stock_location, res_company, ir_attachment, res_users, procurement_group, res_branch, uom_uom.


Describe the implementation of purchase.target.based.on. or What modules define purchase.target.based.on?

Response: The purchase.target.based.on model is defined in module: equip3_purchase_masterdata. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


What are the available fields for purchase.down.payment? or What fields does purchase.down.payment have?

Response: The purchase.down.payment model has 20 fields. Field types distribution: selection: 4, boolean: 5, float: 2, many2one: 3, many2many: 1, integer: 1, char: 1, datetime: 3. Computed fields: 3. Field details: down_payment_by (selection) [module: dev_purchase_down_payment]; is_down_payment_by_received (boolean) [module: dev_purchase_down_payment]; down_payment_by_received (selection) [module: dev_purchase_down_payment]; is_down_payment_by_ordered (boolean) [module: dev_purchase_down_payment]; down_payment_by_ordered (selection) [module: dev_purchase_down_payment]; down_payment_by_billable (selection) [module: dev_purchase_down_payment]; is_down_payment_by_billable (boolean) [module: dev_purchase_down_payment]; amount (float) [module: dev_purchase_down_payment]; purchase_id (many2one) -> purchase.order [module: dev_purchase_down_payment]; is_services_orders (boolean) [module: equip3_purchase_operation]; is_service_work_order (boolean) [readonly] [compute: _compute_is_service_work_order] [not stored] [module: equip3_purchase_operation]; swo_ids (many2many) -> service.work.order [module: equip3_purchase_operation]; payable_progress (float) [module: equip3_purchase_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What columns have default values in crm_lead_crm_lead2opportunity_partner_rel? or Describe the columns of crm_lead_crm_lead2opportunity_partner_rel.

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


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

Response: Columns in sh_mrp_quality_alert: id (integer) [NOT NULL] [DEFAULT: nextval('sh_mrp_quality_alert_id_seq'::regclass)] [PRECISION: 32]; message_main_attachment_id (integer) [PRECISION: 32] [COMMENT: Main Attachment]; name (character varying) [COMMENT: Name]; title (character varying) [COMMENT: Title]; product_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Product]; lot_id (integer) [PRECISION: 32] [COMMENT: Lot Number]; user_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Responsible]; team_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Team]; sh_priority (character varying) [COMMENT: Priority]; color (integer) [PRECISION: 32] [COMMENT: Color Index]; sh_description (text) [COMMENT: Description]; partner_id (integer) [PRECISION: 32] [COMMENT: Partner]; stage_id (integer) [PRECISION: 32] [COMMENT: Stage]; mrp_id (integer) [PRECISION: 32] [COMMENT: Manufacturing Ref.]; workorder_id (integer) [PRECISION: 32] [COMMENT: Work Order]; company_id (integer) [PRECISION: 32] [COMMENT: Company]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 20. Statistics: 16 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in pos_config_sellers_rel: config_id -> pos_config.id [constraint: pos_config_sellers_rel_config_id_fkey]; user_id -> res_users.id [constraint: pos_config_sellers_rel_user_id_fkey]. Total foreign key relationships: 2. Referenced tables: pos_config, res_users.


What methods are available in report.accounting_pdf_reports.report_trialbalance? or What modules define report.accounting_pdf_reports.report_trialbalance?

Response: The report.accounting_pdf_reports.report_trialbalance model is defined in module: accounting_pdf_reports. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _get_accounts, _get_report_values.


List all constraint names in res_partner_sh_sale_product_indent_wizard_rel. or What are the foreign keys in res_partner_sh_sale_product_indent_wizard_rel?

Response: Foreign keys in res_partner_sh_sale_product_indent_wizard_rel: sh_sale_product_indent_wizard_id -> sh_sale_product_indent_wizard.id [constraint: res_partner_sh_sale_product_i_sh_sale_product_indent_wizar_fkey]; res_partner_id -> res_partner.id [constraint: res_partner_sh_sale_product_indent_wizard_r_res_partner_id_fkey]. Total foreign key relationships: 2. Referenced tables: sh_sale_product_indent_wizard, res_partner.


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

Response: The resource_test table has 9 columns and 5 foreign key relationships. It stores data related to resource test in the system. The table has 4 indexes for performance optimization. Column types: integer: 6, character varying: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


What is the pos.global.discount model? or Can you explain the purpose of pos.global.discount?

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. Defined in module: equip3_pos_masterdata. 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.


What computed fields exist in report.stock.report_stock_rule? or What fields does report.stock.report_stock_rule have?

Response: The report.stock.report_stock_rule model has 3 fields. Field types distribution: integer: 1, char: 1, datetime: 1. Computed fields: 2. Field details: id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


List all constraint names in account_journal. or What tables does account_journal reference?

Response: Foreign keys in account_journal: alias_id -> mail_alias.id [constraint: account_journal_alias_id_fkey]; bank_account_id -> res_partner_bank.id [constraint: account_journal_bank_account_id_fkey]; branch_id -> res_branch.id [constraint: account_journal_branch_id_fkey]; check_sequence_id -> ir_sequence.id [constraint: account_journal_check_sequence_id_fkey]; company_id -> res_company.id [constraint: account_journal_company_id_fkey]; create_uid -> res_users.id [constraint: account_journal_create_uid_fkey]; currency_id -> res_currency.id [constraint: account_journal_currency_id_fkey]; default_account_id -> account_account.id [constraint: account_journal_default_account_id_fkey]; loss_account_id -> account_account.id [constraint: account_journal_loss_account_id_fkey]; message_main_attachment_id -> ir_attachment.id [constraint: account_journal_message_main_attachment_id_fkey]; payment_credit_account_id -> account_account.id [constraint: account_journal_payment_credit_account_id_fkey]; payment_debit_account_id -> account_account.id [constraint: account_journal_payment_debit_account_id_fkey]; profit_account_id -> account_account.id [constraint: account_journal_profit_account_id_fkey]; refund_sequence_id -> ir_sequence.id [constraint: account_journal_refund_sequence_id_fkey]; sale_activity_type_id -> mail_activity_type.id [constraint: account_journal_sale_activity_type_id_fkey]; sale_activity_user_id -> res_users.id [constraint: account_journal_sale_activity_user_id_fkey]; secure_sequence_id -> ir_sequence.id [constraint: account_journal_secure_sequence_id_fkey]; sequence_id -> ir_sequence.id [constraint: account_journal_sequence_id_fkey]; suspense_account_id -> account_account.id [constraint: account_journal_suspense_account_id_fkey]; write_uid -> res_users.id [constraint: account_journal_write_uid_fkey]. Total foreign key relationships: 20. Referenced tables: res_partner_bank, res_company, ir_sequence, account_account, ir_attachment, res_currency, res_users, mail_activity_type, res_branch, mail_alias.


List all columns in _unknown_budget_scurve_rel. or What columns have default values in _unknown_budget_scurve_rel?

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


What are the length constraints in pos_loyalty_pos_config_rel? or Describe the columns of pos_loyalty_pos_config_rel.

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


What fields are available in queue_job_queue_jobs_cancel_rel? or What columns have default values in queue_job_queue_jobs_cancel_rel?

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


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

Response: Columns in account_analytic_tag_account_asset_category_rel: account_asset_category_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.


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

Response: Foreign keys in account_pettycash_voucher_rel: voucher_id -> account_pettycash_fund_reconcile.id [constraint: account_pettycash_voucher_rel_voucher_id_fkey]; wizard_id -> account_pettycash_voucher_wizard.id [constraint: account_pettycash_voucher_rel_wizard_id_fkey]. Total foreign key relationships: 2. Referenced tables: account_pettycash_fund_reconcile, account_pettycash_voucher_wizard.


What foreign keys exist in stock.backorder.confirmation? or What models are connected to stock.backorder.confirmation?

Response: The stock.backorder.confirmation model has 4 relational fields: pick_ids -> stock.picking; backorder_confirmation_line_ids -> stock.backorder.confirmation.line; create_uid -> res.users; write_uid -> res.users. Many2many fields: pick_ids. One2many fields: backorder_confirmation_line_ids.


What are the column types in calendar_contacts? or Describe the columns of calendar_contacts.

Response: Columns in calendar_contacts: id (integer) [NOT NULL] [DEFAULT: nextval('calendar_contacts_id_seq'::regclass)] [PRECISION: 32]; user_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Me]; partner_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Employee]; active (boolean) [COMMENT: Active]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 5 nullable, 1 with defaults, 0 with length constraints.


How to work with budget.change.req fields? or What fields are readonly in 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. Field usage details: name [readonly]; requested_id [required]; budget_std_id [required]; date [required]; state [required] [readonly] [has_default] [no_copy]; approval_matrix [readonly] [computed] [no_copy]; is_allowed_to_approval_matrix [readonly] [computed] [no_copy]; approval_matrix_line_id [readonly] [computed] [no_copy]; is_approve_button [readonly] [computed] [no_copy]; company_id [required] [readonly] [has_default]; currency_id [readonly]; state1 [readonly] [computed] [no_copy]; state2 [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: The account_bank_statement_import_journal_creation table has 6 columns and 3 foreign key relationships. It stores data related to account bank statement import journal creation in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, timestamp without time zone: 2. Nullable columns: 4, columns with defaults: 1.


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

Response: The res_company_sh_purchase_analysis_wizard_rel table has 2 columns and 2 foreign key relationships. It stores data related to res company sh purchase analysis wizard rel in the system. The table has 4 indexes for performance optimization. Column types: integer: 2. Nullable columns: 0, columns with defaults: 0.


What are the length constraints in ks_dashboard_ninja_item_action? or Show me the column structure of ks_dashboard_ninja_item_action.

Response: Columns in ks_dashboard_ninja_item_action: id (integer) [NOT NULL] [DEFAULT: nextval('ks_dashboard_ninja_item_action_id_seq'::regclass)] [PRECISION: 32]; ks_item_action_field (integer) [PRECISION: 32] [COMMENT: Action Group By]; ks_item_action_date_groupby (character varying) [COMMENT: Group By Date]; ks_chart_type (character varying) [COMMENT: Item Type]; ks_dashboard_item_id (integer) [PRECISION: 32] [COMMENT: Dashboard Item]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; ks_record_limit (integer) [PRECISION: 32] [COMMENT: Record Limit]; ks_sort_by_field (integer) [PRECISION: 32] [COMMENT: Sort By Field]; ks_sort_by_order (character varying) [COMMENT: Sort Order]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 13. Statistics: 12 nullable, 1 with defaults, 0 with length constraints.


Describe the many2many relations for payment.icon. or What models are connected to 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. One2many fields: none.


How is pos.qrcode implemented technically? or What methods are available in pos.qrcode?

Response: The pos.qrcode 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: onchange_field_id.


How is assign.pr.line.wizard used in the system? or Can you explain the purpose of assign.pr.line.wizard?

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. Defined in module: equip3_purchase_operation. 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.


What models are connected to mrp.bom.operation? or Describe the many2many relations for mrp.bom.operation.

Response: The mrp.bom.operation model has 2 relational fields: create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What are the relationships in product.sale.details.report? or Describe the many2many relations for product.sale.details.report.

Response: The product.sale.details.report model has 4 relational fields: product_id -> product.product; details_id -> sh.sale.details.report.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What foreign keys exist in report.equip3_pos_report.report_pos_payment? or List all relational fields in 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.


What fields are available in crm_quotation_partner? or What are the length constraints in crm_quotation_partner?

Response: Columns in crm_quotation_partner: id (integer) [NOT NULL] [DEFAULT: nextval('crm_quotation_partner_id_seq'::regclass)] [PRECISION: 32]; action (character varying) [NOT NULL] [COMMENT: Quotation Customer]; lead_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Associated Lead]; partner_id (integer) [PRECISION: 32] [COMMENT: Customer]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 8. Statistics: 5 nullable, 1 with defaults, 0 with length constraints.


What are the column types in purchase_tender_create_wizard_res_partner_rel? or Which columns are nullable in purchase_tender_create_wizard_res_partner_rel?

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


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

Response: The product_sale_details_report table has 13 columns and 4 foreign key relationships. It stores data related to product sale details report in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, character varying: 3, double precision: 3, timestamp without time zone: 2. Nullable columns: 12, columns with defaults: 1.


How to work with customer.order.dic fields? or What business logic is in 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. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How to work with res.users.tag fields? or What fields are readonly in res.users.tag?

Response: To use the res.users.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. Field usage details: name [required]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


How to create records in pos.order.line? or What are common use cases for pos.order.line?

Response: To use the pos.order.line model, you need to provide values for required fields: name, product_id, price_subtotal, price_subtotal_incl, order_id, item_state. Readonly fields: company_id, price_subtotal, price_subtotal_incl, tax_ids, tax_ids_after_fiscal_position, currency_id, promotion, promotion_id, promotion_reason, coupon_program_id, coupon_id, coupon_ids, promotion_stack_data, partner_id, order_uid, session_info, uid, margin, margin_percent, purchase_price, config_id, pos_branch_id, analytic_account_id, uom_id, not_returnable, returnable_by_categories, last_supplier_id, plus_point, plus_point_no_rounding, redeem_point, redeem_point_no_rounding, state_related, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: company_id [readonly] [computed] [no_copy]; name [required] [no_copy]; product_id [required]; price_subtotal [required] [readonly]; price_subtotal_incl [required] [readonly]; order_id [required]; tax_ids [readonly]; tax_ids_after_fiscal_position [readonly] [computed] [no_copy]; currency_id [readonly] [computed] [no_copy]; promotion [readonly]; promotion_id [readonly]; promotion_reason [readonly]; coupon_program_id [readonly]; coupon_id [readonly]; coupon_ids [readonly]; promotion_stack_data [readonly] [computed] [no_copy]; partner_id [readonly] [computed] [no_copy]; order_uid [readonly]; session_info [readonly]; uid [readonly]; margin [readonly] [computed] [no_copy]; margin_percent [readonly] [computed] [no_copy]; purchase_price [readonly] [computed] [no_copy]; config_id [readonly] [computed] [no_copy]; pos_branch_id [readonly] [computed] [no_copy]; analytic_account_id [readonly] [computed] [no_copy]; uom_id [readonly]; not_returnable [readonly] [computed] [no_copy]; returnable_by_categories [readonly] [computed] [has_default] [no_copy]; last_supplier_id [readonly] [computed] [no_copy]; item_state [required] [has_default]; plus_point [readonly]; plus_point_no_rounding [readonly]; redeem_point [readonly]; redeem_point_no_rounding [readonly]; state_related [readonly] [computed] [no_copy]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What computed fields exist in mail.blacklist.remove? or What are the available fields for mail.blacklist.remove?

Response: The mail.blacklist.remove model has 9 fields. Field types distribution: char: 3, integer: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: email (char) [required] [readonly] [module: mail]; reason (char) [module: mail]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Describe the columns of purchase_agreement_comparison. or Which columns are nullable in purchase_agreement_comparison?

Response: Columns in purchase_agreement_comparison: id (integer) [NOT NULL] [DEFAULT: nextval('purchase_agreement_comparison_id_seq'::regclass)] [PRECISION: 32]; agreement_id (integer) [PRECISION: 32] [COMMENT: Tender]; partner_id (integer) [PRECISION: 32] [COMMENT: Vendor]; on_time_rate (double precision) [PRECISION: 53] [COMMENT: Delivery on Schedule (%)]; fulfillment (double precision) [PRECISION: 53] [COMMENT: Fulfillment (%)]; final_point (double precision) [PRECISION: 53] [COMMENT: Final Point]; final_star (character varying) [COMMENT: Vendor Rate]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 11. Statistics: 10 nullable, 1 with defaults, 0 with length constraints.


Show me the foreign key constraints of change_password_wizard. or Describe the relational structure of change_password_wizard.

Response: Foreign keys in change_password_wizard: create_uid -> res_users.id [constraint: change_password_wizard_create_uid_fkey]; write_uid -> res_users.id [constraint: change_password_wizard_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Explain the mail_activity_rel table schema. or What is the mail_activity_rel table?

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


Describe the account.loan model in Odoo. or How is account.loan used in the system?

Response: The account.loan model represents Loan in the ERP system. It contains 66 fields and is used to manage loan data. Defined in module: account_loan. Key fields include: name, partner_id, company_id, state, line_ids, periods, method_period, start_date, rate, 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, product_id, interests_product_id, move_ids, pending_principal_amount, payment_amount, interests_amount, post_invoice, short_term_loan_account_id, long_term_loan_account_id, interest_expenses_account_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.


What fields are readonly in mail.mail? or How to create records in 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. Field usage details: mail_message_id [required]; references [readonly]; state [readonly] [has_default] [no_copy]; failure_reason [readonly]; fetchmail_server_id [readonly]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]; subject [computed]; date [computed]; body [computed]; description [readonly] [computed] [no_copy]; attachment_ids [computed]; parent_id [computed]; child_ids [computed] [no_copy]; model [computed]; res_id [computed]; record_name [computed]; subtype_id [computed]; mail_activity_type_id [computed]; is_internal [computed]; email_from [computed]; author_id [computed]; author_avatar [computed] [no_copy]; partner_ids [computed]; notified_partner_ids [computed]; needaction [readonly] [computed] [no_copy]; has_error [readonly] [computed] [no_copy]; channel_ids [computed]; notification_ids [computed] [no_copy]; starred_partner_ids [computed]; starred [readonly] [computed] [no_copy]; tracking_value_ids [computed] [no_copy]; no_auto_thread [computed]; message_id [readonly] [computed] [no_copy]; reply_to [computed]; mail_server_id [computed]; moderation_status [computed]; moderator_id [computed]; need_moderation [readonly] [computed] [no_copy]; email_layout_xmlid [computed] [no_copy]; add_sign [computed]; mail_ids [computed] [no_copy]; canned_response_ids [computed] [no_copy]; rating_ids [computed] [no_copy]; rating_value [readonly] [computed] [no_copy]; has_sms_error [readonly] [computed] [no_copy]; snailmail_error [readonly] [computed] [no_copy]; letter_ids [computed] [no_copy]; message_type [required] [computed]. The model supports standard CRUD operations through the ORM.


What does the payment.voucher model represent? or Can you explain the purpose of payment.voucher?

Response: The payment.voucher model represents Payment Voucher in the ERP system. It contains 63 fields and is used to manage payment voucher data. Defined in module: equip3_accounting_operation. Key fields include: 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.


Which columns are nullable in website_rewrite? or What data types are used in website_rewrite?

Response: Columns in website_rewrite: id (integer) [NOT NULL] [DEFAULT: nextval('website_rewrite_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; website_id (integer) [PRECISION: 32] [COMMENT: Website]; active (boolean) [COMMENT: Active]; url_from (character varying) [COMMENT: URL from]; route_id (integer) [PRECISION: 32] [COMMENT: Route]; url_to (character varying) [COMMENT: URL to]; redirect_type (character varying) [COMMENT: Action]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; create_uid (integer) [PRECISION: 32] [COMMENT: Created by]; create_date (timestamp without time zone) [COMMENT: Created on]; write_uid (integer) [PRECISION: 32] [COMMENT: Last Updated by]; write_date (timestamp without time zone) [COMMENT: Last Updated on]. Total columns: 13. Statistics: 11 nullable, 1 with defaults, 0 with length constraints.


Can you explain the purpose of stock.return.picking.inter.company? or How is stock.return.picking.inter.company used in the system?

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. Defined in module: bi_inter_company_transfer. 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.


What fields does tanda.terima.faktur have? or Describe the field structure of tanda.terima.faktur.

Response: The tanda.terima.faktur model has 16 fields. Field types distribution: selection: 2, many2many: 2, many2one: 3, date: 2, text: 1, one2many: 1, integer: 1, char: 1, datetime: 3. Computed fields: 4. Field details: type_account (selection) [module: allfresh_tanda_terima_faktur]; account_move_ids (many2many) -> account.move [module: allfresh_tanda_terima_faktur]; partner_id (many2one) -> res.partner [module: allfresh_tanda_terima_faktur]; start_date (date) [module: allfresh_tanda_terima_faktur]; end_date (date) [module: allfresh_tanda_terima_faktur]; filter_account_move_ids (many2many) [readonly] -> account.move [compute: _compute_filter_account_move] [not stored] [module: allfresh_tanda_terima_faktur]; invoice_payments_widget (text) [readonly] [compute: _compute_payments_widget_reconciled_info] [not stored] [module: allfresh_tanda_terima_faktur]; move_type (selection) [required] [readonly] [module: allfresh_tanda_terima_faktur]; line_ids (one2many) [readonly] -> account.move.line [module: allfresh_tanda_terima_faktur]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Tell me about the ks_dashboard_ninja.board_defined_filters model. or What does the ks_dashboard_ninja.board_defined_filters model represent?

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. Defined in module: ks_dashboard_ninja. 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.


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

Response: Columns in excel_report_stock_product_rel: excel_report_stock_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.


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

Response: The setu_inventory_fsn_analysis_bi_report table has 16 columns and 7 foreign key relationships. It stores data related to setu inventory fsn analysis bi report in the system. The table has 1 indexes for performance optimization. Column types: integer: 8, double precision: 5, character varying: 1, timestamp without time zone: 2. Nullable columns: 15, columns with defaults: 1.


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

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


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

Response: The sh_mrp_quality_check table has 17 columns and 8 foreign key relationships. It stores data related to sh mrp quality check in the system. The table has 3 indexes for performance optimization. Column types: integer: 9, character varying: 3, date: 1, double precision: 1, text: 1, timestamp without time zone: 2. Nullable columns: 16, columns with defaults: 1.


What is the phone_blacklist_remove table? or Explain the phone_blacklist_remove table schema.

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


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

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


List all relational fields in crossovered.budget. or Describe the many2many relations for crossovered.budget.

Response: The crossovered.budget model has 19 relational fields: user_id -> res.users; crossovered_budget_line -> crossovered.budget.lines; company_id -> res.company; approval_matrix -> approval.matrix.accounting; request_partner_id -> res.partner; approved_matrix_ids -> approval.matrix.accounting.lines; approval_matrix_line_id -> approval.matrix.accounting.lines; currency_id -> res.currency; parent_id -> crossovered.budget; branch_id -> res.branch; account_tag_ids -> account.analytic.tag; 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. One2many fields: crossovered_budget_line, approved_matrix_ids, message_follower_ids, message_ids, website_message_ids.


What computed fields exist in report.membership? or What data can be stored in report.membership?

Response: The report.membership model has 17 fields. Field types distribution: date: 2, integer: 5, float: 2, many2one: 5, selection: 1, char: 1, datetime: 1. Computed fields: 2. Field details: start_date (date) [readonly] [module: membership]; date_to (date) [readonly] [module: membership]; num_waiting (integer) [readonly] [module: membership]; num_invoiced (integer) [readonly] [module: membership]; num_paid (integer) [readonly] [module: membership]; tot_pending (float) [readonly] [module: membership]; tot_earned (float) [readonly] [module: membership]; partner_id (many2one) [readonly] -> res.partner [module: membership]; associate_member_id (many2one) [readonly] -> res.partner [module: membership]; membership_id (many2one) [readonly] -> product.product [module: membership]; membership_state (selection) [readonly] [module: membership]; user_id (many2one) [readonly] -> res.users [module: membership]; company_id (many2one) [readonly] -> res.company [module: membership]; quantity (integer) [readonly] [module: membership]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field] [not stored] [module: None].


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

Response: Foreign keys in res_partner_industry: create_uid -> res_users.id [constraint: res_partner_industry_create_uid_fkey]; write_uid -> res_users.id [constraint: res_partner_industry_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: Foreign keys in queue_job_function: channel_id -> queue_job_channel.id [constraint: queue_job_function_channel_id_fkey]; model_id -> ir_model.id [constraint: queue_job_function_model_id_fkey]. Total foreign key relationships: 2. Referenced tables: ir_model, queue_job_channel.