Activities

Delete, and query information regarding activities.

Table-Specific Information

Select

The provider uses the Zoho CRM API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client-side within the provider.

DueDate supports the '=' operator.
ClosedTime supports the '=' operator.
Location supports the '=, LIKE' operators.
From supports the '=' operator.
To supports the '=' operator.
Check-InTime supports the '=' operator.
Check-InComment supports the '=, LIKE'.
Check-InSub-Locality supports the '=, LIKE' operators.
Check-InCity supports the '=, LIKE' operators.
Check-InState supports the '=, LIKE' operators.
Check-InCountry supports the '=, LIKE' operators.
ZipCode supports the '=, LIKE' operators.
Check-InAddress supports the '=, LIKE' operators.
CheckedInStatus supports the '=, LIKE' operators.
CallStartTime supports the '=' operator.
CallDuration supports the '=, LIKE' operators.
CallResult supports the '=, LIKE' operators.
Reminder supports the '=, LIKE' operators.
CallStatus supports the '=, LIKE' operators.
Subject supports the '=, LIKE' operators.
CreatedTime supports the '=' operator.
ModifiedTime supports the '=' operator.
ActivityType supports the '=, LIKE' operators.
Description supports the '=, LIKE' operators.

For example, the following queries are processed server side:

SELECT * FROM Activities WHERE Id = '3152079000000154214'

SELECT * FROM Activities WHERE Subject = 'event'

Delete

You must specify the Id in the WHERE clause when executing a delete against this table.

DELETE FROM Activities WHERE Id = '3152079000000156229'

Columns


Name	Type	ReadOnly	Description
Id [KEY]	String	False
ActivityOwner_Id	String	False
ActivityOwner_Name	String	False
Subject	String	False
CreatedBy_Id	String	False
CreatedBy_Name	String	False
ModifiedBy_Id	String	False
ModifiedBy_Name	String	False
CreatedAt	Datetime	False
ModifiedAt	Datetime	False
ActivityType	String	False
ContactName_Id	String	False
ContactName_Name	String	False
RelatedTo_Id	String	False
RelatedTo_Name	String	False
Description	String	False
DueDate	Date	False
Status	String	False
Priority	String	False
Tag	String	False
Repeat_Id	String	False
Repeat_Name	String	False
ClosedTime	Datetime	False
Locked	Bool	True
CallType	String	False
OutgoingCallStatus	String	False
CallStartTime	Datetime	False
CallDuration	String	False
DialledNumber	String	True
CallerID	String	True
Reminder	String	False
VoiceRecording	String	False
CallDuration(inseconds)	Int	False
ScheduledinCRM	String	True
CTIEntry	Bool	False
CallPurpose	String	False
CallAgenda	String	False
CallResult	String	False
Location	String	False
Allday	Bool	False
From	Datetime	False
To	Datetime	False
Participants	String	False
Check-InTime	Datetime	True
Check-InBy_Id	String	False
Check-InBy_Name	String	False
Check-InComment	String	True
Check-InSub-Locality	String	True
Check-InCity	String	True
Check-InState	String	True
Check-InCountry	String	True
Latitude	String	True
Longitude	String	True
ZipCode	String	True
Check-InAddress	String	True
CheckedInStatus	String	True

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.