Table of Contents
- Why do I see an error when trying to add a custom object as an Activity Type?
- I deleted an Activity Type. Why is the Field Mapping still showing up?
- Why can't I add "Call" as an Activity Type?
- Are Emails just a kind of Task?
- Why can I add multiple Activity Types of the same object?
Why do I see an error when trying to add a custom object as an Activity Type?
If your custom object has the same name as a packaged Litify object (such as "Treatment," "Damage," etc.), the Activity Timeline may not be able to tell them apart. In that case, you will see an error like the one below:
To resolve this issue, change the API name of your custom object to something different than simply "[Label]__c". For example:
- May cause an error: Treatment__c
- Will work fine: Treatment1__c
I deleted an Activity Type. Why is the Field Mapping still showing up?
When you remove an Activity Type, your preferences for how to map the fields from that object remain.
These preferences will not be applied unless the Activity Type is re-added to a Timeline Object at some point in the future.
Why can't I add "Call" as an Activity Type?
Calls are actually a special kind of Task, rather than a separate object. If you add the Task object as an Activity Type, you'll also get Call.
The Activity Timeline lets users filter these "Task Subtypes" separately.
Are Emails just a kind of Task?
Emails, like Calls, are normally treated by Salesforce as a subtype of Task. The Activity Timeline hides these Task Email records from users, to prevent a situation where duplicate emails could appear.
Email records should be added as their own Activity Type using the EmailMessage object.
Why can I add multiple Activity Types of the same object?
The Activity Timeline relies on a specific lookup field (FROM the Activity Type, and pointing TO the Timeline Object) to define each Activity Type.
For example, setting up the Damage object as an Activity Type on the Matter Timeline Object requires you to confirm that the two objects are connected by the Matter lookup field on the Damage object:
In some cases, there may be multiple lookups between the same two objects. This is the case on the Insurance object, which includes multiple lookups to the Role object (representing the policy holder, insurance company, adjuster, etc.).
When multiple lookups exist, each of those relationships must be created as a separate Activity Type.
For example, when adding the Insurance object as an Activity Type on the Role Timeline Object, each of those lookups must be set up separately: