Navigation: Schema: mail > Tables

message

Message

Catalog: Odoo

Schema: mail

Documentation:

Override MailMessage class in order to add a new type: SMS messages.

Those messages comes with their own notification method, using SMS

gateway.

The data in this table is partitioned per value of the column.

This is a read-only table. The Odoo API may not support changing the data or the Invantive SQL driver for Odoo does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Odoo API.

Table Columns

The columns of the table message are shown below. Each column has an SQL data type.

Name	Data Type	Label	Required	Documentation
attachment_ids	string		☐
author_avatar	byte[]	Author's avatar	☐
author_guest_id_label	string		☐
author_guest_id	string		☐
author_id_label	string		☐	Author of the message. If not set, email_from may hold an email address that did not match any partner.
author_id	string		☐	Author of the message. If not set, email_from may hold an email address that did not match any partner.
body	string	Contents	☐
canned_response_ids	string		☐
child_ids	string		☐
create_date	datetime	Created on	☐
create_uid_label	string		☐
create_uid	string		☐
date	datetime	Date	☐
description	string	Short description	☐	Message description: either the subject, or the beginning of the body
display_name	string	Display Name	☐
email_add_signature	boolean	Email Add Signature	☐
email_from	string	From	☐	Email address of the sender. This field is set when no matching partner is found and replaces the author_id field in the chatter.
email_layout_xmlid	string	Layout	☐
has_error	boolean	Has error	☐
has_sms_error	boolean	Has SMS error	☐
id	int32	ID	☐
is_current_user_or_guest_author	boolean	Is Current User Or Guest Author	☐
is_internal	boolean	Employee Only	☐	Hide to public / portal users, independently from subtype configuration.
letter_ids	string		☐
link_preview_ids	string		☐
mail_activity_type_id_label	string		☐
mail_activity_type_id	string		☐
mail_ids	string		☐
mail_server_id_label	string		☐
mail_server_id	string		☐
message_id	string	Message-Id	☐	Message unique identifier
message_type	string	Type	☑	Message type: email for email message, notification for system message, comment for other messages such as user replies
model	string	Related Document Model	☐
needaction	boolean	Need Action	☐
notification_ids	string		☐
notified_partner_ids	string		☐
parent_id_label	string		☐
parent_id	string		☐
partner_ids	string		☐
preview	string	Preview	☐	The text-only beginning of the body used as email preview.
rating_ids	string		☐
rating_value	decimal	Rating Value	☐
reaction_ids	string		☐
record_name	string	Message Record Name	☐
reply_to_force_new	boolean	No threading for answers	☐	If true, answers do not go in the original document discussion thread. Instead, it will check for the reply_to in tracking message-id and redirected accordingly. This has an impact on the generated message-id.
reply_to	string	Reply-To	☐	Reply email address. Setting the reply_to bypasses the automatic thread creation.
res_id	int32	Related Document ID	☐
snailmail_error	boolean	Snailmail message in error	☐
starred_partner_ids	string		☐
starred	boolean	Starred	☐	Current user has a starred notification linked to this message
subject	string	Subject	☐
subtype_id_label	string		☐
subtype_id	string		☐
tracking_value_ids	string		☐	Tracked values are stored in a separate model. This field allow to reconstruct the tracking and to generate statistics on the model.
write_date	datetime	Last Updated on	☐
write_uid_label	string		☐
write_uid	string		☐

01-03-2023 15:29 Version 22.1.135-BETA+3826

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Odoo API Data Model

message

Table Columns

Important Safety and Usage Information