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

Response: Columns in ir_act_server: id (integer) [NOT NULL] [DEFAULT: nextval('ir_actions_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL]; type (character varying) [NOT NULL]; help (text); binding_model_id (integer) [PRECISION: 32]; binding_type (character varying) [NOT NULL]; binding_view_types (character varying); create_uid (integer) [PRECISION: 32]; create_date (timestamp without time zone); write_uid (integer) [PRECISION: 32]; write_date (timestamp without time zone); usage (character varying) [NOT NULL] [COMMENT: Usage]; state (character varying) [NOT NULL] [COMMENT: Action To Do]; sequence (integer) [PRECISION: 32] [COMMENT: Sequence]; model_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Model]; model_name (character varying) [COMMENT: Model Name]; code (text) [COMMENT: Python Code]; crud_model_id (integer) [PRECISION: 32] [COMMENT: Target Model]; link_field_id (integer) [PRECISION: 32] [COMMENT: Link Field]; template_id (integer) [PRECISION: 32] [COMMENT: Email Template]; activity_type_id (integer) [PRECISION: 32] [COMMENT: Activity]; activity_summary (character varying) [COMMENT: Summary]; activity_note (text) [COMMENT: Note]; activity_date_deadline_range (integer) [PRECISION: 32] [COMMENT: Due Date In]; activity_date_deadline_range_type (character varying) [COMMENT: Due type]; activity_user_type (character varying) [NOT NULL] [COMMENT: Activity User Type]; activity_user_id (integer) [PRECISION: 32] [COMMENT: Responsible]; activity_user_field_name (character varying) [COMMENT: User field name]; sms_template_id (integer) [PRECISION: 32] [COMMENT: SMS Template]; sms_mass_keep_log (boolean) [COMMENT: Log as Note]; website_path (character varying) [COMMENT: Website Path]; website_published (boolean) [COMMENT: Available on the Website]; mass_edit_message (text) [COMMENT: Message]. Total columns: 33. Statistics: 25 nullable, 1 with defaults, 0 with length constraints.


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

Response: Foreign keys in res_company_sh_purchase_product_indent_wizard_rel: sh_purchase_product_indent_wizard_id -> sh_purchase_product_indent_wizard.id [constraint: res_company_sh_purchase_produ_sh_purchase_product_indent_w_fkey]; res_company_id -> res_company.id [constraint: res_company_sh_purchase_product_indent_wiza_res_company_id_fkey]. Total foreign key relationships: 2. Referenced tables: res_company, sh_purchase_product_indent_wizard.


Describe the report.stock.report_stock_rule model in Odoo. or What does the report.stock.report_stock_rule model represent?

Response: The report.stock.report_stock_rule model represents Stock rule report in the ERP system. It contains 3 fields and is used to manage stock rule report data. Defined in module: stock. Key fields include: id, display_name, __last_update.


What foreign keys exist in ai.memory? or What models are connected to ai.memory?

Response: The ai.memory model has 4 relational fields: session_id -> ai.chat.session; user_id -> res.users; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


Which fields in replenish.wizard are computed? or What methods are defined in replenish.wizard original module?

Response: The replenish.wizard model is defined in module: equip3_accounting_pettycash. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: _get_fund, replenish_fund.


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

Response: Foreign keys in s_curve_budget: create_uid -> res_users.id [constraint: s_curve_budget_create_uid_fkey]; crossovered_acount_budget -> monthly_account_budget.id [constraint: s_curve_budget_crossovered_acount_budget_fkey]; crossovered_budget -> crossovered_budget.id [constraint: s_curve_budget_crossovered_budget_fkey]; crossovered_purchase_budget -> budget_purchase.id [constraint: s_curve_budget_crossovered_purchase_budget_fkey]; write_uid -> res_users.id [constraint: s_curve_budget_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: budget_purchase, crossovered_budget, monthly_account_budget, res_users.


What modules define export.partner.csv? or Which fields in export.partner.csv are computed?

Response: The export.partner.csv model is defined in module: equip3_accounting_efaktur. It has 27 computed fields: product_id_csv_created, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, sequence_prefix, sequence_number, display_name, __last_update. Stored computed fields: sequence_prefix, sequence_number. Related fields: activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary. Original module methods: _compute_csv_created, download_csv, download_efaktur, _generate_efaktur, _generate_efaktur_invoice.


What does the res.users.tag model represent? or Describe the res.users.tag model in Odoo.

Response: The res.users.tag model represents User Tag in the ERP system. It contains 8 fields and is used to manage user tag data. Defined in module: report_user_access_right. Key fields include: name, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The account_chart_template table has 35 columns and 23 foreign key relationships. It stores data related to account chart template in the system. The table has 1 indexes for performance optimization. Column types: integer: 25, character varying: 5, boolean: 3, timestamp without time zone: 2. Nullable columns: 28, columns with defaults: 1.


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

Response: The hr_department table has 14 columns and 6 foreign key relationships. It stores data related to hr department in the system. The table has 4 indexes for performance optimization. Column types: integer: 8, character varying: 2, boolean: 1, text: 1, timestamp without time zone: 2. Nullable columns: 12, columns with defaults: 1.


What are the relationships in account.deposit.return? or List all relational fields in account.deposit.return.

Response: The account.deposit.return model has 6 relational fields: journal_id -> account.journal; diff_amount_account_id -> account.account; customer_deposit_id -> customer.deposit; vendor_deposit_id -> vendor.deposit; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What data can be stored in website.page? or What computed fields exist in website.page?

Response: The website.page model has 58 fields. Field types distribution: char: 17, many2one: 8, boolean: 14, datetime: 4, one2many: 3, integer: 3, text: 5, many2many: 1, selection: 3. Computed fields: 40. Field details: url (char) [module: website]; view_id (many2one) [required] -> ir.ui.view [module: website]; website_indexed (boolean) [module: website]; date_publish (datetime) [module: website]; menu_ids (one2many) -> website.menu [module: website]; is_homepage (boolean) [compute: _compute_homepage] [not stored] [module: website] [inverse: _set_homepage]; is_visible (boolean) [readonly] [compute: _compute_visible] [not stored] [module: website]; cache_time (integer) [module: website]; cache_key_expr (char) [module: website]; header_overlay (boolean) [module: website]; header_color (char) [module: website]; header_visible (boolean) [module: website]; footer_visible (boolean) [module: website]; website_id (many2one) -> website [compute: <bound method Field._compute_related of website.page.website_id>] [stored] [module: website] [related: view_id.website_id] [inverse: <bound method Field._inverse_related of website.page.website_id>]; arch (text) [compute: <bound method Field._compute_related of website.page.arch>] [not stored] [module: website] [related: view_id.arch] [inverse: <bound method Field._inverse_related of website.page.arch>]; theme_template_id (many2one) -> theme.website.page [module: website]; website_published (boolean) [compute: _compute_website_published] [not stored] [module: website] [inverse: _inverse_website_published]; is_published (boolean) [module: website]; can_publish (boolean) [readonly] [compute: _compute_can_publish] [not stored] [module: website]; website_url (char) [readonly] [compute: _compute_website_url] [not stored] [module: website]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None]; name (char) [required] [compute: <bound method Field._compute_related of website.page.name>] [not stored] [module: None] [related: view_id.name] [inverse: <bound method Field._inverse_related of website.page.name>]; model (char) [compute: <bound method Field._compute_related of website.page.model>] [not stored] [module: None] [related: view_id.model] [inverse: <bound method Field._inverse_related of website.page.model>]; key (char) [compute: <bound method Field._compute_related of website.page.key>] [not stored] [module: None] [related: view_id.key] [inverse: <bound method Field._inverse_related of website.page.key>]; priority (integer) [required] [compute: <bound method Field._compute_related of website.page.priority>] [not stored] [module: None] [related: view_id.priority] [inverse: <bound method Field._inverse_related of website.page.priority>]; arch_base (text) [compute: <bound method Field._compute_related of website.page.arch_base>] [not stored] [module: None] [related: view_id.arch_base] [inverse: <bound method Field._inverse_related of website.page.arch_base>]; arch_db (text) [compute: <bound method Field._compute_related of website.page.arch_db>] [not stored] [module: None] [related: view_id.arch_db] [inverse: <bound method Field._inverse_related of website.page.arch_db>]; arch_fs (char) [compute: <bound method Field._compute_related of website.page.arch_fs>] [not stored] [module: None] [related: view_id.arch_fs] [inverse: <bound method Field._inverse_related of website.page.arch_fs>]; arch_updated (boolean) [compute: <bound method Field._compute_related of website.page.arch_updated>] [not stored] [module: None] [related: view_id.arch_updated] [inverse: <bound method Field._inverse_related of website.page.arch_updated>]; arch_prev (text) [compute: <bound method Field._compute_related of website.page.arch_prev>] [not stored] [module: None] [related: view_id.arch_prev] [inverse: <bound method Field._inverse_related of website.page.arch_prev>]; inherit_id (many2one) -> ir.ui.view [compute: <bound method Field._compute_related of website.page.inherit_id>] [not stored] [module: None] [related: view_id.inherit_id] [inverse: <bound method Field._inverse_related of website.page.inherit_id>]; inherit_children_ids (one2many) -> ir.ui.view [compute: <bound method Field._compute_related of website.page.inherit_children_ids>] [not stored] [module: None] [related: view_id.inherit_children_ids] [inverse: <bound method Field._inverse_related of website.page.inherit_children_ids>]; field_parent (char) [compute: <bound method Field._compute_related of website.page.field_parent>] [not stored] [module: None] [related: view_id.field_parent] [inverse: <bound method Field._inverse_related of website.page.field_parent>]; model_data_id (many2one) [readonly] -> ir.model.data [compute: <bound method Field._compute_related of website.page.model_data_id>] [not stored] [module: None] [related: view_id.model_data_id] [inverse: <bound method Field._inverse_related of website.page.model_data_id>]; xml_id (char) [readonly] [compute: <bound method Field._compute_related of website.page.xml_id>] [not stored] [module: None] [related: view_id.xml_id] [inverse: <bound method Field._inverse_related of website.page.xml_id>]; groups_id (many2many) -> res.groups [compute: <bound method Field._compute_related of website.page.groups_id>] [not stored] [module: None] [related: view_id.groups_id] [inverse: <bound method Field._inverse_related of website.page.groups_id>]; mode (selection) [required] [compute: <bound method Field._compute_related of website.page.mode>] [not stored] [module: None] [related: view_id.mode] [inverse: <bound method Field._inverse_related of website.page.mode>]; active (boolean) [compute: <bound method Field._compute_related of website.page.active>] [not stored] [module: None] [related: view_id.active] [inverse: <bound method Field._inverse_related of website.page.active>]; customize_show (boolean) [compute: <bound method Field._compute_related of website.page.customize_show>] [not stored] [module: None] [related: view_id.customize_show] [inverse: <bound method Field._inverse_related of website.page.customize_show>]; is_seo_optimized (boolean) [readonly] [compute: <bound method Field._compute_related of website.page.is_seo_optimized>] [not stored] [module: None] [related: view_id.is_seo_optimized] [inverse: <bound method Field._inverse_related of website.page.is_seo_optimized>]; website_meta_title (char) [compute: <bound method Field._compute_related of website.page.website_meta_title>] [not stored] [module: None] [related: view_id.website_meta_title] [inverse: <bound method Field._inverse_related of website.page.website_meta_title>]; website_meta_description (text) [compute: <bound method Field._compute_related of website.page.website_meta_description>] [not stored] [module: None] [related: view_id.website_meta_description] [inverse: <bound method Field._inverse_related of website.page.website_meta_description>]; website_meta_keywords (char) [compute: <bound method Field._compute_related of website.page.website_meta_keywords>] [not stored] [module: None] [related: view_id.website_meta_keywords] [inverse: <bound method Field._inverse_related of website.page.website_meta_keywords>]; website_meta_og_img (char) [compute: <bound method Field._compute_related of website.page.website_meta_og_img>] [not stored] [module: None] [related: view_id.website_meta_og_img] [inverse: <bound method Field._inverse_related of website.page.website_meta_og_img>]; seo_name (char) [compute: <bound method Field._compute_related of website.page.seo_name>] [not stored] [module: None] [related: view_id.seo_name] [inverse: <bound method Field._inverse_related of website.page.seo_name>]; page_ids (one2many) -> website.page [compute: <bound method Field._compute_related of website.page.page_ids>] [not stored] [module: None] [related: view_id.page_ids] [inverse: <bound method Field._inverse_related of website.page.page_ids>]; first_page_id (many2one) [readonly] -> website.page [compute: <bound method Field._compute_related of website.page.first_page_id>] [not stored] [module: None] [related: view_id.first_page_id] [inverse: <bound method Field._inverse_related of website.page.first_page_id>]; track (boolean) [compute: <bound method Field._compute_related of website.page.track>] [not stored] [module: None] [related: view_id.track] [inverse: <bound method Field._inverse_related of website.page.track>]; visibility (selection) [compute: <bound method Field._compute_related of website.page.visibility>] [not stored] [module: None] [related: view_id.visibility] [inverse: <bound method Field._inverse_related of website.page.visibility>]; visibility_password (char) [compute: <bound method Field._compute_related of website.page.visibility_password>] [not stored] [module: None] [related: view_id.visibility_password] [inverse: <bound method Field._inverse_related of website.page.visibility_password>]; visibility_password_display (char) [compute: <bound method Field._compute_related of website.page.visibility_password_display>] [not stored] [module: None] [related: view_id.visibility_password_display] [inverse: <bound method Field._inverse_related of website.page.visibility_password_display>]; type (selection) [compute: <bound method Field._compute_related of website.page.type>] [not stored] [module: None] [related: view_id.type] [inverse: <bound method Field._inverse_related of website.page.type>].


How to create records in stock.valuation.layer? or How do I use the stock.valuation.layer model?

Response: To use the stock.valuation.layer model, you need to provide values for required fields: company_id, product_id, uom_id, currency_id, new_warehouse_id, new_location_id. Readonly fields: company_id, product_id, categ_id, product_tmpl_id, quantity, uom_id, currency_id, unit_cost, value, remaining_qty, remaining_value, description, stock_valuation_layer_id, stock_move_id, account_move_id, secondary_uom, qty_of_secondary_uom, date, warehouse_id, new_warehouse_id, new_location_id, new_inventory_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: company_id [required] [readonly]; product_id [required] [readonly]; categ_id [readonly] [computed] [no_copy]; product_tmpl_id [readonly] [computed] [no_copy]; quantity [readonly]; uom_id [required] [readonly] [computed] [no_copy]; currency_id [required] [readonly] [computed] [no_copy]; unit_cost [readonly]; value [readonly]; remaining_qty [readonly]; remaining_value [readonly]; description [readonly]; stock_valuation_layer_id [readonly]; stock_move_id [readonly]; account_move_id [readonly]; secondary_uom [readonly] [computed] [no_copy]; qty_of_secondary_uom [readonly] [computed] [no_copy]; date [readonly] [computed] [no_copy]; warehouse_id [readonly] [computed] [no_copy]; new_warehouse_id [required] [readonly]; new_location_id [required] [readonly]; new_inventory_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 is the base_update_translations table? or What is stored in base_update_translations?

Response: The base_update_translations table has 6 columns and 2 foreign key relationships. It stores data related to base update translations in the system. The table has 1 indexes for performance optimization. Column types: integer: 3, character varying: 1, timestamp without time zone: 2. Nullable columns: 4, columns with defaults: 1.


Describe the many2many relations for theme.ir.ui.view. or What are the relationships in theme.ir.ui.view?

Response: The theme.ir.ui.view model has 3 relational fields: copy_ids -> ir.ui.view; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: copy_ids.


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

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


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

Response: Foreign keys in calendar_event_type: create_uid -> res_users.id [constraint: calendar_event_type_create_uid_fkey]; write_uid -> res_users.id [constraint: calendar_event_type_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: Foreign keys in ir_translation: lang -> res_lang.code [constraint: ir_translation_lang_fkey_res_lang]. Total foreign key relationships: 1. Referenced tables: res_lang.


What are the technical details of project.task? or Describe the implementation of project.task.

Response: The project.task model is defined in module: project. It has 106 computed fields: stage_id, kanban_state_label, project_id, subtask_planned_hours, partner_id, partner_is_company, commercial_partner_id, partner_email, partner_phone, ribbon_message, partner_city, manager_id, company_id, user_email, attachment_ids, legend_blocked, legend_done, legend_normal, is_closed, subtask_project_id, allow_subtasks, subtask_count, email_from, allowed_user_ids, project_privacy_visibility, working_hours_open, working_hours_close, working_days_open, working_days_close, allow_recurring_tasks, recurring_count, recurrence_message, repeat_interval, repeat_unit, repeat_type, repeat_until, repeat_number, repeat_on_month, repeat_on_year, mon, tue, wed, thu, fri, sat, sun, repeat_day, repeat_week, repeat_weekday, repeat_month, repeat_show_dow, repeat_show_day, repeat_show_week, repeat_show_month, analytic_account_active, allow_timesheets, remaining_hours, effective_hours, total_hours_spent, progress, overtime, subtask_effective_hours, encode_uom_in_days, sale_line_id, project_sale_order_id, invoice_count, task_to_invoice, sale_order_id, analytic_account_id, bill_type, pricing_type, is_project_map_empty, has_multi_sol, allow_billable, display_create_order, remaining_hours_so, remaining_hours_available, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, rating_last_value, rating_last_feedback, rating_last_image, rating_count, rating_avg, access_url, access_warning, display_name, __last_update. Stored computed fields: stage_id, project_id, partner_id, partner_email, partner_phone, company_id, email_from, allowed_user_ids, working_hours_open, working_hours_close, working_days_open, working_days_close, remaining_hours, effective_hours, total_hours_spent, progress, overtime, subtask_effective_hours, sale_line_id, sale_order_id, rating_last_value. Related fields: partner_is_company -> partner_id.is_company, commercial_partner_id -> partner_id.commercial_partner_id, partner_city -> partner_id.city, manager_id -> project_id.user_id, user_email -> user_id.email, legend_blocked -> stage_id.legend_blocked, legend_done -> stage_id.legend_done, legend_normal -> stage_id.legend_normal, is_closed -> stage_id.is_closed, subtask_project_id -> project_id.subtask_project_id, allow_subtasks -> project_id.allow_subtasks, project_privacy_visibility -> project_id.privacy_visibility, allow_recurring_tasks -> project_id.allow_recurring_tasks, allow_timesheets -> project_id.allow_timesheets, project_sale_order_id -> project_id.sale_order_id, invoice_count -> sale_order_id.invoice_count, analytic_account_id -> sale_order_id.analytic_account_id, bill_type -> project_id.bill_type, pricing_type -> project_id.pricing_type, allow_billable -> project_id.allow_billable, remaining_hours_available -> sale_line_id.remaining_hours_available, activity_user_id -> activity_ids.user_id, activity_type_id -> activity_ids.activity_type_id, activity_type_icon -> activity_ids.icon, activity_summary -> activity_ids.summary, rating_last_feedback -> rating_ids.feedback, rating_last_image -> rating_ids.rating_image. Original module methods: _populate_factories, _populate, _populate_set_children_tasks, _get_default_stage_id, _default_company_id, _read_group_stage_ids, _get_recurrence_fields, _compute_repeat_visibility, _compute_repeat, _get_weekdays, _compute_recurrence_message, _is_recurrence_valid, _compute_recurring_count, _compute_partner_email, _inverse_partner_email, _compute_partner_phone, _inverse_partner_phone, _compute_ribbon_message, _check_parent_id, _check_no_portal_allowed, _compute_attachment_ids, _compute_allowed_user_ids, _compute_elapsed, _compute_kanban_state_label, _compute_access_url, _compute_access_warning, _compute_subtask_planned_hours, _compute_subtask_count, _onchange_task_company, _compute_company_id, _compute_stage_id, copy, get_empty_list_help, message_subscribe, stage_find, default_get, create, write, update_date_end, unlink, _compute_partner_id, _compute_email_from, _compute_project_id, _track_template, _creation_subtype, _track_subtype, _notify_get_groups, _notify_get_reply_to, email_split, message_new, message_update, _message_get_suggested_recipients, _notify_email_header_dict, _message_post_after_hook, action_assign_to_me, _get_all_subtasks, action_open_parent_task, action_subtask, action_recurring_tasks, _send_task_rating_mail, rating_get_partner_id, rating_apply, _rating_get_parent_field_name.


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

Response: Foreign keys in pos_sync_session_order_line: create_uid -> res_users.id [constraint: pos_sync_session_order_line_create_uid_fkey]; parent_id -> pos_sync_session_order.id [constraint: pos_sync_session_order_line_parent_id_fkey]; pos_session_id -> pos_session.id [constraint: pos_sync_session_order_line_pos_session_id_fkey]; write_uid -> res_users.id [constraint: pos_sync_session_order_line_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: pos_session, pos_sync_session_order, res_users.


List all constraint names in pos_sale_summary_wizard. or Describe the relational structure of pos_sale_summary_wizard.

Response: Foreign keys in pos_sale_summary_wizard: company_id -> res_company.id [constraint: pos_sale_summary_wizard_company_id_fkey]; create_uid -> res_users.id [constraint: pos_sale_summary_wizard_create_uid_fkey]; pos_branch_id -> res_branch.id [constraint: pos_sale_summary_wizard_pos_branch_id_fkey]; write_uid -> res_users.id [constraint: pos_sale_summary_wizard_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_branch, res_users, res_company.


Describe the field structure of pos.cache.database. or What data can be stored in pos.cache.database?

Response: The pos.cache.database model has 10 fields. Field types distribution: char: 3, boolean: 1, integer: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: res_id (char) [module: equip3_pos_masterdata]; res_model (char) [module: equip3_pos_masterdata]; deleted (boolean) [module: equip3_pos_masterdata]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


How is stock.picking.type.dashboard used in the system? or Can you explain the purpose of stock.picking.type.dashboard?

Response: The stock.picking.type.dashboard model represents Stock Picking Type Dashboard in the ERP system. It contains 51 fields and is used to manage stock picking type dashboard data. Defined in module: equip3_inventory_operation. Key fields include: name, warehouse_id, code, company_id, stock_picking_type_ids, count_picking, count_picking_ready, count_picking_draft, count_picking_waiting, count_picking_late, count_picking_backorders, color, is_manufacturing, campaign_id, source_id, medium_id, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, access_url, access_token, access_warning, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in res_currency_tax: company_id -> res_company.id [constraint: res_currency_tax_company_id_fkey]; create_uid -> res_users.id [constraint: res_currency_tax_create_uid_fkey]; currency_id -> res_currency.id [constraint: res_currency_tax_currency_id_fkey]; write_uid -> res_users.id [constraint: res_currency_tax_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_currency, res_users, res_company.


What is the asp.asm.stock model? or Tell me about the asp.asm.stock model.

Response: The asp.asm.stock model represents Adjustment Stock in the ERP system. It contains 46 fields and is used to manage adjustment stock data. Defined in module: allfresh_mod_asm_asp. Key fields include: name, inv_ref, state, warehouse_id, company_id, user_id, analytic_tag_ids, line_ids, move_ids, branch_id, adjustmentt_type, remark, domain_warehouse_id, product_ids, activity_ids, activity_state, activity_user_id, activity_type_id, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_summary, activity_exception_decoration, activity_exception_icon, message_is_follower, message_follower_ids, message_partner_ids, message_channel_ids, message_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_main_attachment_id, website_message_ids, message_has_sms_error, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


What are common use cases for crm.phonecall? or What operations can I perform on crm.phonecall?

Response: To use the crm.phonecall model, you need to provide values for required fields: name, direction. Readonly fields: date_action_last, date_action_next, create_date, date_open, date_closed, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, id, display_name, create_uid, write_uid, write_date, __last_update. Field usage details: date_action_last [readonly]; date_action_next [readonly]; create_date [readonly]; date_open [readonly]; name [required]; date_closed [readonly]; direction [required] [has_default]; 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]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What one2many fields are in sh.purchase.tags? or List all relational fields in sh.purchase.tags.

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


What computed fields exist in product.template.attribute.exclusion? or What field types are used in product.template.attribute.exclusion?

Response: The product.template.attribute.exclusion model has 10 fields. Field types distribution: many2one: 4, many2many: 1, integer: 1, char: 1, datetime: 3. Computed fields: 2. Field details: product_template_attribute_value_id (many2one) -> product.template.attribute.value [module: product]; product_tmpl_id (many2one) [required] -> product.template [module: product]; value_ids (many2many) -> product.template.attribute.value [module: product]; 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 models are connected to wizard.scrap.order.report? or What foreign keys exist in wizard.scrap.order.report?

Response: The wizard.scrap.order.report model has 3 relational fields: company_id -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What operations can I perform on cust.credit.limit.data.line? or How do I use the cust.credit.limit.data.line model?

Response: To use the cust.credit.limit.data.line model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What computed fields exist in stock.orderpoint.snooze? or What fields does stock.orderpoint.snooze have?

Response: The stock.orderpoint.snooze model has 10 fields. Field types distribution: many2many: 1, selection: 1, date: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: orderpoint_ids (many2many) -> stock.warehouse.orderpoint [module: stock]; predefined_date (selection) [module: stock]; snoozed_until (date) [module: stock]; 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 indexes exist on res_company_setu_inventory_overstock_report_rel? or What columns does res_company_setu_inventory_overstock_report_rel have?

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


Which fields are required in pos.remote.session? or What field types are used in pos.remote.session?

Response: The pos.remote.session model has 10 fields. Field types distribution: text: 1, many2many: 1, selection: 1, integer: 1, char: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: message (text) [module: equip3_pos_general]; config_ids (many2many) [required] -> pos.config [module: equip3_pos_general]; action (selection) [required] [module: equip3_pos_general]; 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 field structure of calendar.event.type. or What data can be stored in calendar.event.type?

Response: The calendar.event.type model has 9 fields. Field types distribution: char: 2, boolean: 1, integer: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: name (char) [required] [module: calendar]; leads_meeting (boolean) [module: equip3_crm_operation]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What are the relationships in ks.message.wizard? or Describe the many2many relations for ks.message.wizard.

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


Which fields in report.stock.quantity.new are computed? or What methods are available in report.stock.quantity.new?

Response: The report.stock.quantity.new model is defined in module: equip3_inventory_reports. It has 3 computed fields: product_tmpl_id, display_name, __last_update. Stored computed fields: none. Related fields: product_tmpl_id -> product_id.product_tmpl_id. Original module methods: init, read_group.


What operations can I perform on customer.statement? or How to create records in customer.statement?

Response: To use the customer.statement model, you need to provide values for required fields: journal_ids, target_move, company_id. Readonly fields: activity_state, activity_type_icon, activity_date_deadline, my_activity_date_deadline, activity_exception_decoration, activity_exception_icon, message_is_follower, message_partner_ids, message_channel_ids, message_unread, message_unread_counter, message_needaction, message_needaction_counter, message_has_error, message_has_error_counter, message_attachment_count, message_has_sms_error, access_url, access_warning, sequence_prefix, sequence_number, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: activity_state [readonly] [computed] [no_copy]; activity_user_id [computed] [no_copy]; activity_type_id [computed] [no_copy]; activity_type_icon [readonly] [computed] [no_copy]; activity_date_deadline [readonly] [computed] [no_copy]; my_activity_date_deadline [readonly] [computed] [no_copy]; activity_summary [computed] [no_copy]; activity_exception_decoration [readonly] [computed] [no_copy]; activity_exception_icon [readonly] [computed] [no_copy]; message_is_follower [readonly] [computed] [no_copy]; message_partner_ids [readonly] [computed] [no_copy]; message_channel_ids [readonly] [computed] [no_copy]; message_unread [readonly] [computed] [no_copy]; message_unread_counter [readonly] [computed] [no_copy]; message_needaction [readonly] [computed] [no_copy]; message_needaction_counter [readonly] [computed] [no_copy]; message_has_error [readonly] [computed] [no_copy]; message_has_error_counter [readonly] [computed] [no_copy]; message_attachment_count [readonly] [computed] [no_copy]; message_has_sms_error [readonly] [computed] [no_copy]; access_url [readonly] [computed] [no_copy]; access_warning [readonly] [computed] [no_copy]; sequence_prefix [readonly] [computed] [no_copy]; sequence_number [readonly] [computed] [no_copy]; journal_ids [required] [has_default]; target_move [required] [has_default]; company_id [required] [has_default]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


Tell me about the sale.adv.wizard.product.line.specific model. or How is sale.adv.wizard.product.line.specific used in the system?

Response: The sale.adv.wizard.product.line.specific model represents Sale Multi Pro Selection Adv Wizard Pro Line Specific in the ERP system. It contains 13 fields and is used to manage sale multi pro selection adv wizard pro line specific data. Defined in module: equip3_sale_operation. Key fields include: sale_adv_wizard_id_specific, product_id, default_code, standard_price, uom_po_id, qty, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What fields does vendor.deposit.report have? or What data can be stored in vendor.deposit.report?

Response: The vendor.deposit.report model has 16 fields. Field types distribution: char: 3, many2one: 7, monetary: 3, date: 1, integer: 1, datetime: 1. Computed fields: 2. Field details: name (char) [module: equip3_accounting_reports]; partner_id (many2one) [required] -> res.partner [module: equip3_accounting_reports]; currency_id (many2one) [required] -> res.currency [module: equip3_accounting_reports]; amount (monetary) [required] [module: equip3_accounting_reports]; remaining_amount (monetary) [module: equip3_accounting_reports]; communication (char) [module: equip3_accounting_reports]; deposit_move_id (many2one) [required] -> account.move [module: equip3_accounting_reports]; return_deposit (many2one) -> account.move [module: equip3_accounting_reports]; payment_date (date) [required] [module: equip3_accounting_reports]; deposit_reconcile_journal_id (many2one) [required] -> account.journal [module: equip3_accounting_reports]; journal_id (many2one) -> account.journal [module: equip3_accounting_reports]; deposit_account_id (many2one) -> account.account [module: equip3_accounting_reports]; used_amount (monetary) [module: equip3_accounting_reports]; 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].


Describe the implementation of ks_dashboard_ninja.board. or What is the module hierarchy for ks_dashboard_ninja.board?

Response: The ks_dashboard_ninja.board model is defined in module: ks_dashboard_ninja. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: ks_date_validation, create, ks_date_filter_selection_onchange, write, unlink, ks_get_grid_config, ks_fetch_dashboard_data, ks_fetch_item, ks_fetch_item_data, ks_set_date, ks_get_list_view_data_offset, ks_view_items_view, ks_export_item, ks_export_item_data, ks_import_item, ks_dashboard_export, ks_import_dashboard, ks_create_item, ks_prepare_item, update_child_board, ks_prepare_dashboard_domain, ks_prepare_dashboard_pre_domain, ks_prepare_dashboard_custom_domain.


Describe the relational structure of account_move_stock_picking_rel. or What tables does account_move_stock_picking_rel reference?

Response: Foreign keys in account_move_stock_picking_rel: account_move_id -> account_move.id [constraint: account_move_stock_picking_rel_account_move_id_fkey]; stock_picking_id -> stock_picking.id [constraint: account_move_stock_picking_rel_stock_picking_id_fkey]. Total foreign key relationships: 2. Referenced tables: stock_picking, account_move.


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

Response: Foreign keys in approved_users_scrap_patner_rel: scrap_id -> stock_scrap_approval_matrix_line.id [constraint: approved_users_scrap_patner_rel_scrap_id_fkey]; user_id -> res_users.id [constraint: approved_users_scrap_patner_rel_user_id_fkey]. Total foreign key relationships: 2. Referenced tables: stock_scrap_approval_matrix_line, res_users.


Describe the many2many relations for list.top.product. or Show me the relational structure of list.top.product.

Response: The list.top.product model has 3 relational fields: top_id -> sh.tsp.top.selling.product.wizard; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


What field types are used in budget.purchase.lines? or Describe the field structure of budget.purchase.lines.

Response: The budget.purchase.lines model has 30 fields. Field types distribution: char: 3, many2one: 11, date: 3, monetary: 5, float: 1, boolean: 1, selection: 1, many2many: 1, integer: 1, datetime: 3. Computed fields: 13. Field details: name (char) [readonly] [compute: _compute_line_name] [not stored] [module: equip3_accounting_budget]; purchase_budget_id (many2one) [required] -> budget.purchase [module: equip3_accounting_budget]; analytic_account_id (many2one) -> account.analytic.account [module: equip3_accounting_budget]; analytic_group_id (many2one) [readonly] -> account.analytic.group [compute: <bound method Field._compute_related of budget.purchase.lines.analytic_group_id>] [not stored] [module: equip3_accounting_budget] [related: analytic_account_id.group_id]; product_budget (many2one) -> account.budget.post [module: equip3_accounting_budget]; date_from (date) [required] [module: equip3_accounting_budget]; date_to (date) [required] [module: equip3_accounting_budget]; paid_date (date) [module: equip3_accounting_budget]; currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of budget.purchase.lines.currency_id>] [not stored] [module: equip3_accounting_budget] [related: company_id.currency_id]; planned_amount (monetary) [required] [module: equip3_accounting_budget]; practical_amount (monetary) [readonly] [compute: _compute_fields_practical] [not stored] [module: equip3_accounting_budget]; practical_amount_temp (monetary) [module: equip3_accounting_budget]; remaining_amount (monetary) [readonly] [compute: _compute_remaining_amount] [stored] [module: equip3_accounting_budget]; theoritical_amount (monetary) [readonly] [compute: _compute_theoritical_amount] [stored] [module: equip3_accounting_budget]; percentage (float) [readonly] [compute: _compute_percentage] [stored] [module: equip3_accounting_budget]; company_id (many2one) [readonly] -> res.company [compute: <bound method Field._compute_related of budget.purchase.lines.company_id>] [stored] [module: equip3_accounting_budget] [related: purchase_budget_id.company_id]; is_above_budget (boolean) [readonly] [compute: _is_above_budget] [not stored] [module: equip3_accounting_budget]; purchase_budget_state (selection) [readonly] [compute: <bound method Field._compute_related of budget.purchase.lines.purchase_budget_state>] [stored] [module: equip3_accounting_budget] [related: purchase_budget_id.state]; parent_analytic_account_id (many2one) -> account.analytic.account [module: equip3_accounting_budget]; account_tag_ids (many2many) [readonly] -> account.analytic.tag [compute: <bound method Field._compute_related of budget.purchase.lines.account_tag_ids>] [not stored] [module: equip3_accounting_budget] [related: purchase_budget_id.account_tag_ids]; product_id (many2one) -> product.product [module: equip3_accounting_budget]; purchase_order_line_budget_id (many2one) -> purchase.order.line [module: equip3_accounting_budget]; eer (char) [module: equip3_accounting_budget]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


What is stored in pos_qrcode? or Tell me about the pos_qrcode table.

Response: The pos_qrcode table has 8 columns and 4 foreign key relationships. It stores data related to pos qrcode 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: 4, columns with defaults: 1.


Tell me about the ir.fields.converter model. or Can you explain the purpose of ir.fields.converter?

Response: The ir.fields.converter model represents Fields Converter in the ERP system. It contains 3 fields and is used to manage fields converter data. Defined in module: base. Key fields include: id, display_name, __last_update.


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

Response: Foreign keys in reward_product_rel: product_id -> product_product.id [constraint: reward_product_rel_product_id_fkey]; reward_id -> pos_loyalty_reward.id [constraint: reward_product_rel_reward_id_fkey]. Total foreign key relationships: 2. Referenced tables: product_product, pos_loyalty_reward.


What fields are available in account_tour_upload_bill_email_confirm? or What data types are used in account_tour_upload_bill_email_confirm?

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


Describe the many2many relations for project.tags. or List all relational fields in project.tags.

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


List all constraint names in invoice_confirmation_availability. or How does invoice_confirmation_availability relate to other tables?

Response: Foreign keys in invoice_confirmation_availability: create_uid -> res_users.id [constraint: invoice_confirmation_availability_create_uid_fkey]; invoice_id -> account_move.id [constraint: invoice_confirmation_availability_invoice_id_fkey]; write_uid -> res_users.id [constraint: invoice_confirmation_availability_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, account_move.


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

Response: Foreign keys in approval_matrix_sale_order_lines: approval_matrix -> approval_matrix_sale_order.id [constraint: approval_matrix_sale_order_lines_approval_matrix_fkey]; bo_order_id -> saleblanket_saleblanket.id [constraint: approval_matrix_sale_order_lines_bo_order_id_fkey]; create_uid -> res_users.id [constraint: approval_matrix_sale_order_lines_create_uid_fkey]; last_approved -> res_users.id [constraint: approval_matrix_sale_order_lines_last_approved_fkey]; order_id -> sale_order.id [constraint: approval_matrix_sale_order_lines_order_id_fkey]; write_uid -> res_users.id [constraint: approval_matrix_sale_order_lines_write_uid_fkey]. Total foreign key relationships: 6. Referenced tables: res_users, approval_matrix_sale_order, saleblanket_saleblanket, sale_order.


What relationships exist for mrp_workcenter_productivity_loss_type? or Describe the relational structure of mrp_workcenter_productivity_loss_type.

Response: Foreign keys in mrp_workcenter_productivity_loss_type: create_uid -> res_users.id [constraint: mrp_workcenter_productivity_loss_type_create_uid_fkey]; write_uid -> res_users.id [constraint: mrp_workcenter_productivity_loss_type_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: Foreign keys in pos_combo_item: create_uid -> res_users.id [constraint: pos_combo_item_create_uid_fkey]; product_combo_id -> product_template.id [constraint: pos_combo_item_product_combo_id_fkey]; product_id -> product_product.id [constraint: pos_combo_item_product_id_fkey]; uom_id -> uom_uom.id [constraint: pos_combo_item_uom_id_fkey]; write_uid -> res_users.id [constraint: pos_combo_item_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: product_product, res_users, uom_uom, product_template.


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

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


How does mail.resend.message relate to other models? or What one2many fields are in mail.resend.message?

Response: The mail.resend.message model has 5 relational fields: mail_message_id -> mail.message; partner_ids -> mail.resend.partner; notification_ids -> mail.notification; create_uid -> res.users; write_uid -> res.users. Many2many fields: notification_ids. One2many fields: partner_ids.


Which fields are stored computed fields in pos.combo.item? or Which fields in pos.combo.item are computed?

Response: The pos.combo.item model is defined in module: equip3_pos_masterdata. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: create, write, onchange_product_id.


How does quotation.amount relate to other models? or Describe the many2many relations for quotation.amount.

Response: The quotation.amount model has 4 relational fields: order_id -> sale.order; currency_id -> res.currency; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: Foreign keys in base_import_import: create_uid -> res_users.id [constraint: base_import_import_create_uid_fkey]; write_uid -> res_users.id [constraint: base_import_import_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


How to create records in sale.order.repair.line? or How to work with sale.order.repair.line fields?

Response: To use the sale.order.repair.line model, you need to provide values for required fields: none. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


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

Response: Foreign keys in sh_custom_model_purchase_order: create_uid -> res_users.id [constraint: sh_custom_model_purchase_order_create_uid_fkey]; inherit_view_obj -> ir_ui_view.id [constraint: sh_custom_model_purchase_order_inherit_view_obj_fkey]; ir_model_fields_obj -> ir_model_fields.id [constraint: sh_custom_model_purchase_order_ir_model_fields_obj_fkey]; ir_ui_view_obj -> ir_ui_view.id [constraint: sh_custom_model_purchase_order_ir_ui_view_obj_fkey]; model_id -> ir_model.id [constraint: sh_custom_model_purchase_order_model_id_fkey]; ref_model_id -> ir_model.id [constraint: sh_custom_model_purchase_order_ref_model_id_fkey]; related_field_id -> ir_model_fields.id [constraint: sh_custom_model_purchase_order_related_field_id_fkey]; relation_field_id -> ir_model_fields.id [constraint: sh_custom_model_purchase_order_relation_field_id_fkey]; serialization_field_id -> ir_model_fields.id [constraint: sh_custom_model_purchase_order_serialization_field_id_fkey]; sh_position_field -> ir_model_fields.id [constraint: sh_custom_model_purchase_order_sh_position_field_fkey]; write_uid -> res_users.id [constraint: sh_custom_model_purchase_order_write_uid_fkey]. Total foreign key relationships: 11. Referenced tables: ir_model, ir_ui_view, res_users, ir_model_fields.


Show me the fields of report.equip3_pos_report.report_open_session. or What data can be stored in report.equip3_pos_report.report_open_session?

Response: The report.equip3_pos_report.report_open_session 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].


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

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


How does stock.warn.insufficient.qty.unbuild relate to other models? or List all relational fields in stock.warn.insufficient.qty.unbuild.

Response: The stock.warn.insufficient.qty.unbuild model has 6 relational fields: unbuild_id -> mrp.unbuild; product_id -> product.product; location_id -> stock.location; quant_ids -> stock.quant; create_uid -> res.users; write_uid -> res.users. Many2many fields: quant_ids. One2many fields: none.


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

Response: Foreign keys in sh_back_theme_config_settings: create_uid -> res_users.id [constraint: sh_back_theme_config_settings_create_uid_fkey]; write_uid -> res_users.id [constraint: sh_back_theme_config_settings_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


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

Response: Foreign keys in cluster_area: company_id -> res_company.id [constraint: cluster_area_company_id_fkey]; create_uid -> res_users.id [constraint: cluster_area_create_uid_fkey]; write_uid -> res_users.id [constraint: cluster_area_write_uid_fkey]. Total foreign key relationships: 3. Referenced tables: res_users, res_company.


What data types are used in asset_cip? or What fields are available in asset_cip?

Response: Columns in asset_cip: id (integer) [NOT NULL] [DEFAULT: nextval('asset_cip_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Name]; asset_name (character varying) [NOT NULL] [COMMENT: Asset Name]; asset_category (integer) [PRECISION: 32] [COMMENT: Asset Category]; cip_account (integer) [PRECISION: 32] [COMMENT: Cip Account]; state (character varying) [COMMENT: Status]; currency (integer) [PRECISION: 32] [COMMENT: Currency]; move_id (integer) [PRECISION: 32] [COMMENT: Move]; branch_id (integer) [PRECISION: 32] [COMMENT: Branch]; 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: 10 nullable, 1 with defaults, 0 with length constraints.


How is rma.reject.reason used in the system? or What is the rma.reject.reason model?

Response: The rma.reject.reason model represents Reject Reason in the ERP system. It contains 8 fields and is used to manage reject reason data. Defined in module: dev_rma. Key fields include: reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


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

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


What data can be stored in account.automatic.entry.wizard? or Show me the fields of account.automatic.entry.wizard.

Response: The account.automatic.entry.wizard model has 22 fields. Field types distribution: selection: 2, text: 2, many2many: 1, date: 1, many2one: 8, float: 1, monetary: 1, boolean: 1, integer: 1, char: 1, datetime: 3. Computed fields: 12. Field details: action (selection) [required] [module: account]; move_data (text) [readonly] [compute: _compute_move_data] [not stored] [module: account]; preview_move_data (text) [readonly] [compute: _compute_preview_move_data] [not stored] [module: account]; move_line_ids (many2many) -> account.move.line [module: account]; date (date) [required] [module: account]; company_id (many2one) [required] [readonly] -> res.company [module: account]; company_currency_id (many2one) [readonly] -> res.currency [compute: <bound method Field._compute_related of account.automatic.entry.wizard.company_currency_id>] [not stored] [module: account] [related: company_id.currency_id]; percentage (float) [compute: _compute_percentage] [stored] [module: account]; total_amount (monetary) [compute: _compute_total_amount] [stored] [module: account]; journal_id (many2one) [required] -> account.journal [compute: <bound method Field._compute_related of account.automatic.entry.wizard.journal_id>] [not stored] [module: account] [related: company_id.automatic_entry_default_journal_id] [inverse: <bound method Field._inverse_related of account.automatic.entry.wizard.journal_id>]; account_type (selection) [readonly] [compute: _compute_account_type] [stored] [module: account]; expense_accrual_account (many2one) -> account.account [compute: <bound method Field._compute_related of account.automatic.entry.wizard.expense_accrual_account>] [not stored] [module: account] [related: company_id.expense_accrual_account_id] [inverse: <bound method Field._inverse_related of account.automatic.entry.wizard.expense_accrual_account>]; revenue_accrual_account (many2one) -> account.account [compute: <bound method Field._compute_related of account.automatic.entry.wizard.revenue_accrual_account>] [not stored] [module: account] [related: company_id.revenue_accrual_account_id] [inverse: <bound method Field._inverse_related of account.automatic.entry.wizard.revenue_accrual_account>]; destination_account_id (many2one) -> account.account [module: account]; display_currency_helper (boolean) [readonly] [compute: _compute_display_currency_helper] [not stored] [module: account]; 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].


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

Response: The pos_voucher_use_history table has 11 columns and 6 foreign key relationships. It stores data related to pos voucher use history in the system. The table has 1 indexes for performance optimization. Column types: integer: 7, double precision: 1, timestamp without time zone: 3. Nullable columns: 7, columns with defaults: 1.


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

Response: Foreign keys in account_partner_ageing: company_id -> res_company.id [constraint: account_partner_ageing_company_id_fkey]; create_uid -> res_users.id [constraint: account_partner_ageing_create_uid_fkey]; report_currency_id -> res_currency.id [constraint: account_partner_ageing_report_currency_id_fkey]; write_uid -> res_users.id [constraint: account_partner_ageing_write_uid_fkey]. Total foreign key relationships: 4. Referenced tables: res_currency, res_users, res_company.


What methods are available in account.payment.register.payment.difference.line? or Which fields in account.payment.register.payment.difference.line are computed?

Response: The account.payment.register.payment.difference.line model is defined in module: equip3_accounting_operation. It has 4 computed fields: currency_id, payment_difference, display_name, __last_update. Stored computed fields: none. Related fields: currency_id -> payment_register_id.currency_id. Original module methods: .


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

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


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

Response: The project_delete_wizard table has 5 columns and 2 foreign key relationships. It stores data related to project delete wizard 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.


What relationships exist for utm_source? or Describe the relational structure of utm_source.

Response: Foreign keys in utm_source: create_uid -> res_users.id [constraint: utm_source_create_uid_fkey]; write_uid -> res_users.id [constraint: utm_source_write_uid_fkey]. Total foreign key relationships: 2. Referenced tables: res_users.


Describe the field structure of sh.purchase.category.xls. or What field types are used in sh.purchase.category.xls?

Response: The sh.purchase.category.xls model has 9 fields. Field types distribution: binary: 1, char: 2, integer: 1, many2one: 2, datetime: 3. Computed fields: 2. Field details: excel_file (binary) [module: sh_purchase_reports]; file_name (char) [readonly] [module: sh_purchase_reports]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].


Describe the calendar.contacts model in Odoo. or How is calendar.contacts used in the system?

Response: The calendar.contacts model represents Calendar Contacts in the ERP system. It contains 10 fields and is used to manage calendar contacts data. Defined in module: calendar. Key fields include: user_id, partner_id, active, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

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


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

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


Show me the relational structure of setu.inventory.outofstock.report. or Describe the many2many relations for setu.inventory.outofstock.report.

Response: The setu.inventory.outofstock.report model has 7 relational fields: product_category_ids -> product.category; product_ids -> product.product; warehouse_ids -> stock.warehouse; company_id -> res.company; company_ids -> res.company; create_uid -> res.users; write_uid -> res.users. Many2many fields: product_category_ids, product_ids, warehouse_ids, company_ids. One2many fields: none.


What fields are readonly in setu.rfm.segment? or What operations can I perform on setu.rfm.segment?

Response: To use the setu.rfm.segment model, you need to provide values for required fields: none. Readonly fields: total_mailing, total_customers, total_orders, total_revenue, open_lead_count, open_rfq_count, total_customers_ratio, total_orders_ratio, total_revenue_ratio, desc, id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: total_mailing [readonly] [computed] [no_copy]; total_customers [readonly] [computed] [no_copy]; total_orders [readonly] [computed] [no_copy]; total_revenue [readonly] [computed] [no_copy]; open_lead_count [readonly] [computed] [no_copy]; open_rfq_count [readonly] [computed] [no_copy]; total_customers_ratio [readonly] [computed] [no_copy]; total_orders_ratio [readonly] [computed] [no_copy]; total_revenue_ratio [readonly] [computed] [no_copy]; desc [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 is stored in sh_push_notification? or Tell me about the sh_push_notification table.

Response: The sh_push_notification table has 9 columns and 3 foreign key relationships. It stores data related to sh push notification in the system. The table has 1 indexes for performance optimization. Column types: integer: 4, character varying: 2, timestamp without time zone: 3. Nullable columns: 8, columns with defaults: 1.


Describe the account.general.ledger model in Odoo. or Tell me about the account.general.ledger model.

Response: The account.general.ledger model represents General Ledger Report in the ERP system. It contains 22 fields and is used to manage general ledger report data. Defined in module: dynamic_accounts_report. Key fields include: journal_ids, account_ids, account_tag_ids, analytic_ids, analytic_tag_ids, display_account, titles, target_move, all_account, filter_detail, expand, date_from, date_to, report_currency_id, company_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What is the crm.lead.lost model? or Describe the crm.lead.lost model in Odoo.

Response: The crm.lead.lost model represents Get Lost Reason in the ERP system. It contains 8 fields and is used to manage get lost reason data. Defined in module: crm. Key fields include: lost_reason_id, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: Foreign keys in report_reordering_view: create_uid -> res_users.id [constraint: report_reordering_view_create_uid_fkey]; location_id -> stock_location.id [constraint: report_reordering_view_location_id_fkey]; product_id -> product_product.id [constraint: report_reordering_view_product_id_fkey]; wizard_id -> report_reordering.id [constraint: report_reordering_view_wizard_id_fkey]; write_uid -> res_users.id [constraint: report_reordering_view_write_uid_fkey]. Total foreign key relationships: 5. Referenced tables: product_product, report_reordering, res_users, stock_location.


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

Response: The choose_delivery_package table has 8 columns and 4 foreign key relationships. It stores data related to choose delivery package in the system. The table has 1 indexes for performance optimization. Column types: integer: 5, double precision: 1, timestamp without time zone: 2. Nullable columns: 7, columns with defaults: 1.


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

Response: Columns in calendar_event_res_partners_rel: calendar_event_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.


What does the account.user.reminder.lines model represent? or Tell me about the account.user.reminder.lines model.

Response: The account.user.reminder.lines model represents Account USer Reminder Lines in the ERP system. It contains 11 fields and is used to manage account user reminder lines data. Defined in module: equip3_accounting_masterdata. Key fields include: account_line_id, user_ids, sequence, sequence2, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


What data types are used in account_loan_pay_amount? or What fields are available in account_loan_pay_amount?

Response: Columns in account_loan_pay_amount: id (integer) [NOT NULL] [DEFAULT: nextval('account_loan_pay_amount_id_seq'::regclass)] [PRECISION: 32]; loan_id (integer) [NOT NULL] [PRECISION: 32] [COMMENT: Loan]; cancel_loan (boolean) [COMMENT: Cancel Loan]; date (date) [NOT NULL] [COMMENT: Date]; amount (numeric) [COMMENT: Amount to reduce from Principal]; fees (numeric) [COMMENT: Bank fees]; 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: 7 nullable, 1 with defaults, 0 with length constraints.


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

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


What computed fields exist in report.sh_sale_reports.sh_salesperson_report_doc? or Which fields are required in report.sh_sale_reports.sh_salesperson_report_doc?

Response: The report.sh_sale_reports.sh_salesperson_report_doc 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].


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

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


List all relational fields in res.partner.group. or Describe the many2many relations for res.partner.group.

Response: The res.partner.group model has 3 relational fields: pricelist_id -> product.pricelist; create_uid -> res.users; write_uid -> res.users. Many2many fields: none. One2many fields: none.


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

Response: Columns in ir_translation: id (integer) [NOT NULL] [DEFAULT: nextval('ir_translation_id_seq'::regclass)] [PRECISION: 32]; name (character varying) [NOT NULL] [COMMENT: Translated field]; res_id (integer) [PRECISION: 32] [COMMENT: Record ID]; lang (character varying) [COMMENT: Language]; type (character varying) [COMMENT: Type]; src (text) [COMMENT: Internal Source]; value (text) [COMMENT: Translation Value]; module (character varying) [COMMENT: Module]; state (character varying) [COMMENT: Status]; comments (text) [COMMENT: Translation comments]. Total columns: 10. Statistics: 8 nullable, 1 with defaults, 0 with length constraints.


What methods are defined in journal.payment.report original module? or What are the technical details of journal.payment.report?

Response: The journal.payment.report model is defined in module: equip3_sale_report. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


What does the sh.target.commision.new model represent? or Describe the sh.target.commision.new model in Odoo.

Response: The sh.target.commision.new model represents sh.target.commision.new in the ERP system. It contains 18 fields and is used to manage sh.target.commision.new data. Defined in module: equip3_sale_team_commission. Key fields include: commission_id, name, user_id, main_target, current_achievement, current_achievement_formula, curr_achieve, target_based_on, target_on, to_date, type, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


How is purchase.team.analysis implemented technically? or What methods are available in purchase.team.analysis?

Response: The purchase.team.analysis model is defined in module: equip3_purchase_report. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


How is mail.blacklist.remove used in the system? or Describe the mail.blacklist.remove model in Odoo.

Response: The mail.blacklist.remove model represents Remove email from blacklist wizard in the ERP system. It contains 9 fields and is used to manage remove email from blacklist wizard data. Defined in module: mail. Key fields include: email, reason, id, display_name, create_uid, create_date, write_uid, write_date, __last_update.


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

Response: The res_partner_sh_purchase_product_indent_wizard_rel table has 2 columns and 2 foreign key relationships. It stores data related to res partner sh purchase product indent 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 methods are defined in res.mail.activity original module? or Which fields in res.mail.activity are computed?

Response: The res.mail.activity model is defined in module: equip3_crm_operation. It has 2 computed fields: display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


What are common use cases for report.base.report_irmodulereference? or How to work with report.base.report_irmodulereference fields?

Response: To use the report.base.report_irmodulereference model, you need to provide values for required fields: none. Readonly fields: id, display_name, __last_update. 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.


What operations can I perform on project.create.sale.order.line? or How to query project.create.sale.order.line data?

Response: To use the project.create.sale.order.line model, you need to provide values for required fields: wizard_id. Readonly fields: id, display_name, create_uid, create_date, write_uid, write_date, __last_update. Field usage details: wizard_id [required]; sale_line_id [computed]; id [readonly]; display_name [readonly] [computed] [no_copy]; create_uid [readonly]; create_date [readonly]; write_uid [readonly]; write_date [readonly]; __last_update [readonly] [computed] [no_copy]. The model supports standard CRUD operations through the ORM.


What modules define purchase.custom.checklist.template? or What methods are available in purchase.custom.checklist.template?

Response: The purchase.custom.checklist.template model is defined in module: sh_all_in_one_purchase_tools. It has 3 computed fields: order_type, display_name, __last_update. Stored computed fields: none. Related fields: none. Original module methods: .


What computed fields exist in sh.target.commision? or List all fields in the sh.target.commision model.

Response: The sh.target.commision model has 76 fields. Field types distribution: float: 15, boolean: 9, integer: 6, many2many: 5, many2one: 12, char: 7, selection: 9, date: 4, one2many: 5, text: 1, datetime: 3. Computed fields: 37. Field details: achieved_sales_target (float) [readonly] [compute: compute_targets] [not stored] [module: sh_sales_commission_target]; achieved_collection_target (float) [readonly] [compute: compute_targets] [not stored] [module: sh_sales_commission_target]; remaining_sales_target (float) [readonly] [compute: compute_targets] [not stored] [module: sh_sales_commission_target]; remaining_collection_target (float) [readonly] [compute: compute_targets] [not stored] [module: sh_sales_commission_target]; sales_target_achieved (boolean) [readonly] [compute: compute_targets] [not stored] [module: sh_sales_commission_target]; active (boolean) [module: sh_sales_commission_target]; bill_count (integer) [readonly] [compute: compute_bill_count] [not stored] [module: sh_sales_commission_target]; bill_ids (many2many) [readonly] -> account.move [compute: compute__bill_ids] [not stored] [module: sh_sales_commission_target]; sales_team (many2one) -> crm.team [module: equip3_sale_team_commission]; company_id (many2one) [required] -> res.company [module: equip3_sale_team_commission]; name (char) [readonly] [module: equip3_sale_team_commission]; user_id (many2one) [required] -> res.users [module: equip3_sale_team_commission]; type (selection) [module: equip3_sale_team_commission]; product_ids (many2many) -> product.product [module: equip3_sale_team_commission]; category_ids (many2many) -> product.category [module: equip3_sale_team_commission]; brand_id (many2one) -> product.brand [module: equip3_sale_team_commission]; commision_calculator (selection) [required] [module: equip3_sale_team_commission]; from_date (date) [required] [module: equip3_sale_team_commission]; to_date (date) [required] [module: equip3_sale_team_commission]; target_on (selection) [required] [module: equip3_sale_team_commission]; percentage_on (selection) [module: equip3_sale_team_commission]; commision_detail_line (one2many) -> sh.commision.detail [module: equip3_sale_team_commission]; collection_target_achieved (boolean) [readonly] [compute: compute_targets] [not stored] [module: equip3_sale_team_commission]; sales_target (float) [module: equip3_sale_team_commission]; collection_target (float) [module: equip3_sale_team_commission]; sales_actual (float) [module: equip3_sale_team_commission]; collection_actual (float) [module: equip3_sale_team_commission]; deduction (float) [readonly] [compute: _compute_deduction] [not stored] [module: equip3_sale_team_commission]; main_traget (float) [required] [module: equip3_sale_team_commission]; current_achievement (float) [readonly] [compute: _compute_curr_achieve] [stored] [module: equip3_sale_team_commission]; current_commission (float) [readonly] [compute: _compute_curr_achieve] [stored] [module: equip3_sale_team_commission]; curr_achieve (float) [readonly] [compute: _compute_curr_achieve] [not stored] [module: equip3_sale_team_commission]; current_achievement_formula (float) [module: equip3_sale_team_commission]; target_left (float) [readonly] [compute: _compute_curr_achieve] [not stored] [module: equip3_sale_team_commission]; target_based_on (selection) [required] [module: equip3_sale_team_commission]; target_based_on1 (selection) [required] [module: equip3_sale_team_commission]; target_based_on2 (selection) [required] [module: equip3_sale_team_commission]; is_target_posted (boolean) [module: equip3_sale_team_commission]; campaign_id (many2one) -> utm.campaign [module: utm]; source_id (many2one) -> utm.source [module: utm]; medium_id (many2one) -> utm.medium [module: utm]; activity_ids (one2many) -> mail.activity [module: mail]; activity_state (selection) [readonly] [compute: _compute_activity_state] [not stored] [module: mail]; activity_user_id (many2one) -> res.users [compute: <bound method Field._compute_related of sh.target.commision.activity_user_id>] [not stored] [module: mail] [related: activity_ids.user_id] [inverse: <bound method Field._inverse_related of sh.target.commision.activity_user_id>]; activity_type_id (many2one) -> mail.activity.type [compute: <bound method Field._compute_related of sh.target.commision.activity_type_id>] [not stored] [module: mail] [related: activity_ids.activity_type_id] [inverse: <bound method Field._inverse_related of sh.target.commision.activity_type_id>]; activity_type_icon (char) [readonly] [compute: <bound method Field._compute_related of sh.target.commision.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 sh.target.commision.activity_summary>] [not stored] [module: mail] [related: activity_ids.summary] [inverse: <bound method Field._inverse_related of sh.target.commision.activity_summary>]; activity_exception_decoration (selection) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; activity_exception_icon (char) [readonly] [compute: _compute_activity_exception_type] [not stored] [module: mail]; message_is_follower (boolean) [readonly] [compute: _compute_is_follower] [not stored] [module: mail]; message_follower_ids (one2many) -> mail.followers [module: mail]; message_partner_ids (many2many) [readonly] -> res.partner [compute: _get_followers] [not stored] [module: mail]; message_channel_ids (many2many) [readonly] -> mail.channel [compute: _get_followers] [not stored] [module: mail]; message_ids (one2many) -> mail.message [module: mail]; message_unread (boolean) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_unread_counter (integer) [readonly] [compute: _get_message_unread] [not stored] [module: mail]; message_needaction (boolean) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_needaction_counter (integer) [readonly] [compute: _get_message_needaction] [not stored] [module: mail]; message_has_error (boolean) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_has_error_counter (integer) [readonly] [compute: _compute_message_has_error] [not stored] [module: mail]; message_attachment_count (integer) [readonly] [compute: _compute_message_attachment_count] [not stored] [module: mail]; message_main_attachment_id (many2one) -> ir.attachment [module: mail]; website_message_ids (one2many) -> mail.message [module: portal]; message_has_sms_error (boolean) [readonly] [compute: _compute_message_has_sms_error] [not stored] [module: sms]; access_url (char) [readonly] [compute: _compute_access_url] [not stored] [module: portal]; access_token (char) [module: portal]; access_warning (text) [readonly] [compute: _compute_access_warning] [not stored] [module: portal]; id (integer) [readonly] [module: None]; display_name (char) [readonly] [compute: _compute_display_name] [not stored] [module: None]; create_uid (many2one) [readonly] -> res.users [module: None]; create_date (datetime) [readonly] [module: None]; write_uid (many2one) [readonly] -> res.users [module: None]; write_date (datetime) [readonly] [module: None]; __last_update (datetime) [readonly] [compute: compute_concurrency_field_with_access] [not stored] [module: None].