PersonsUpdatesAttendees
Get details of Deals Activities Attendees.
Select
The adapter will use the API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the adapter.
- PersonId supports the '=' operator.
- AllChanges supports the '=' operator.
- Items supports the '=,IN' operators.
For example, the following query is processed server side:
SELECT * FROM PersonsUpdatesAttendees WHERE PersonId = 246
SELECT * FROM PersonsUpdatesAttendees WHERE PersonId = 10 AND AllChanges = 1
SELECT * FROM PersonsUpdatesAttendees WHERE PersonId = 10 AND Items IN ('activity','plannedActivity')
Columns
| Name | Type | Description |
| PersonId [KEY] | Integer | PersonId. |
| EmailAddress | String | EmailAddress. |
| IsOrganizer | Integer | IsOrganizer. |
| Name | String | Name. |
| Status | String | Status. |
| UserId | String | UserId. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| AllChanges | String | Whether to show custom field updates or not.
The allowed values are 1. |
| Items | String | Item specific updates.
The allowed values are activity, plannedActivity, note, file, change, deal, follower, participant, mailMessage, mailMessageWithAttachment, invoice, activityFile, document. |