Threaded Messages
Threaded message records are messages posted by an employee about an object of a supported type. Currently, the only supported type in the SuiteProjects Pro is Project. For a description of threaded messages in the SuiteProjects Pro UI, see Project Discussions.
Available methods
None — To work with threaded messages, use the endpoints and methods specific to the object the threaded messages are associated with.
ThreadedMessage object properties
A project discussion message is a message posted by an employee about a project.
The ThreadedMessage
object has the following properties:
Property |
Description |
Type |
Read-only |
Query allowed |
Sorting allowed |
---|---|---|---|---|---|
|
The body of the message. |
string |
— |
Yes |
— |
|
The date the message was created. |
string |
Yes |
Yes |
— |
|
The internal ID of the employee who deleted the message. |
integer($int64) |
Yes |
Yes |
— |
|
A 1/0 field indicating if the message was edited. |
Boolean |
Yes |
Yes |
— |
|
The unique internal identifier of the message. |
integer($int64) |
Yes |
Yes |
— |
|
The internal ID of the record in the table |
integer($int64) |
Yes |
Yes |
— |
|
If the message is a reply to another message, the internal ID of the message that this message is replying to. |
number($float) |
Yes |
Yes |
— |
|
The name of the table including the record associated with the message. |
string |
Yes |
Yes |
— |
|
The date the message was last updated or modified. |
string |
Yes |
Yes |
— |
|
The internal ID of the employee associated with the message — the employee who posted the message |
integer($int64) |
Yes |
Yes |
— |
Access to certain object types and object attributes depend on the business logic configured for your SuiteProjects Pro account. It may vary depending on the role and access privileges associated with the access token and with the user who authorized the application.
Required and read-only attributes also depend on the business logic configured for each specific SuiteProjects Pro account. Some fields such as id
, created
, and updated
are system-generated and always read-only.