ActivitiesParticipants
Getdetails of activities participants
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.
- Id supports the '=' operator.
- Done supports the '=' operator.
- Type supports the '=, IN' operators.
- UserId supports the '=' operator.
- FilterId supports the '=' operator.
- StartDate supports the '=' operator.
- EndDate supports the '=' operator.
For example, the following query is processed server side:
SELECT * FROM ActivitiesParticipants WHERE Id = 246
SELECT * FROM ActivitiesParticipants WHERE Done = 0
SELECT * FROM ActivitiesParticipants WHERE Type IN ('deadline','call')
SELECT * FROM ActivitiesParticipants WHERE EndDate = '2021-12-24'
SELECT * FROM ActivitiesParticipants WHERE UserId = 8230170
Columns
| Name | Type | Description |
| PersonId [KEY] | Integer | PersonId |
| Id | Integer | Activities ID. |
| PrimaryFlag | Boolean | PrimaryFlag |
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 |
| Type | String | Type of the Activity This is in correlation with the key_string parameter of ActivityTypes When value for type is not set, it will be given a default value Call
The default value is Call. |
| Done | Boolean | Whether the Activity is done or not 0 = Not done 1 = Done If omitted returns both Done and Not done activities
The allowed values are 0, 1. |
| FilterId | Integer | The ID of the Filter to use |
| StartDate | String | Use the Activity due date where you wish to begin fetching Activities from Insert due date in YYYY-MM-DD format |
| EndDate | String | Use the Activity due date where you wish to stop fetching Activities from Insert due date in YYYY-MM-DD format |
| UserId | String | UserId |