Enhance Accessibility with Pinning Capabilities in Your Timeline

The feature to pin and unpin activities, like important tasks, to the top of a timeline ensures these items are both prominently visible and easily accessible. This functionality removes the need for agents to sift through an entire timeline for specific information. By pinning key activities, agents can drastically reduce the time spent navigating through less pertinent data.

To discover all the features of the timeline, you can click on the provided link.

Let’s delve into the backend process to assess the feasibility of automating this feature. Imagine a scenario where certain tasks are automatically pinned when a record is created, allowing users to immediately act on them.

The necessary data to pin activities to the timeline is stored in an elastic table named “msdyn_timelinepin” For automatic pinning to function, five crucial fields must be correctly set up when a record is created:

  1. msdyn_formrecordid (Form Record ID): Identifies the record to which the activity is tagged, such as an account or contact.
  2. msdyn_pinnedrecordid (Pinned Record ID): Identifies the pinned record on the timeline, i.e., the activity ID of the task, phone call, notes, etc.
  3. msdyn_pinnedrecordlogicalname (Pinned Record Logical Name): Specifies the entity logical name of the pinned record on the timeline, like annotation, task, or phone call.
  4. partitionid (Partition ID): Represents a logical partition ID, which consists of a set of records with the same partition ID, formulated as {msdyn_formrecordid}+{msdyn_timelinecontrolid}.
  5. msdyn_timelinecontrolid (Timeline Control ID): The ID of the timeline control for the pinned item, found in the form XML.
  6. ttlinseconds (Time to Live): The lifespan of the pin in seconds, with a default setting of 31,536,000 (one year).

Here is an example of how the request might look:

{
  "msdyn_formrecordid": "4dee02de-ddd2-ee11-904d-000d3a7a0005",
  "msdyn_timelinecontrolid": "a605255b-09a0-4c82-8a53-1b2a2038348c",
  "msdyn_pinnedrecordid": "bbcb9ddb-f00c-ef11-9f89-0022481864a7",
  "msdyn_pinnedrecordlogicalname": "annotation",
  "ttlinseconds": 31536000,
  "partitionid": "4dee02de-ddd2-ee11-904d-000d3a7a0005+a605255b-09a0-4c82-8a53-1b2a2038348c"
}

Leave a comment