UserActivityDetails
Generated schema file.
Table Specific Information
Select
The cmdlet will use the Act! CRM API to process WHERE clause conditions built with the following column and operator. UserId is required to make a request and the rest of the filter is executed client-side within the cmdlet.
- Date supports the '=,>,<,>=,<=' operators.
- TypeId supports the '=' operator.
- UserId supports the '=' operator.
The cmdlet processes other filters client-side within the cmdlet. For example, the following queries are processed server side:
SELECT * FROM UserActivityDetails where UserId = 'b7c23fa5-6cd3-4bcd-a036-f8bbb85ba760'
Columns
| Name | Type | Description |
| ActivityId | String | Activity Id |
| ContactName | String | Contact Name |
| Location | String | Location |
| Regarding | String | Regarding |
| Type | String | Type |
| UserName | String | User Name |
| TypeId | String | Type Id |
| 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 |
| Date | Datetime | Date Range of Activities By User |