Roster Member Assignment
A Roster Member can be assigned to a Territory. The assignment exists to drive CRM and the customer's internal reporting. The integration with Veeva CRM uses this assignment to link the CRM user with the Territory's other assignments, such as Accounts. Align’s Roster Member supports the inclusion of people who do not exist in CRM.
The objects referenced by Roster Member Assignment are: roster_member__aln and territory__aln. Each record has a Start Date & End Date to indicate the life of the assignment.
Roster Member assignments display as a related list on the Territory detail view. They can be created, edited, and deleted manually via the UI. The same actions can be done using the delimited import process. The assignment can be pushed to Veeva CRM.
To view assignment details, select the Name field within the entity's Related Lists section. The assignment detail view includes an option to edit the assignment.
Set the Send to CRM field to Yes to integrate the assignment with CRM.
A Roster Member can have multiple active Territory assignments for a given day.
- The assignment's start and end dates must fall within the Territory's start and end dates
When editing an assignment, the start, end, and send to CRM dates may be altered within the following parameters:
The End Date value cannot be changed to a future date if the assignment was sent to CRM and then removed, as indicated by the CRM is Deleted field value
The Start Date value cannot be changed to a future date if the assignment has been sent to CRM. Align assumes the assignment was sent when the current date is after the Start Date and before the End Date and the Send to CRM field is set to Yes.
The Send to CRM field value cannot be changed to No after the assignment is sent to CRM. Align assumes the assignment was sent to CRM when the current date is after the Start Date and before the End Date and the Send to CRM field is set to Yes.
Controlling Roster Member Start and End Dates
To better track the actual start and end dates during which a Roster Member can be aligned to a territory, Align allows Admins to create custom start and end date fields on the CRM User object and map the custom fields to Align’s Roster Member start_date__aln and end_date__aln fields. This feature provides greater control over the default field mapping.
Because the start_date__aln and end_date__aln fields are required in Align, they default to the following values unless custom mapping is set:
- The start_date__aln field on the roster_member__aln object defaults to the CreatedDate field value on the User object
- The end_date__aln field on the roster_member__aln object defaults to a value of 2099-12-31
For example, Sarah Jones needs to track the exact date John Adams can be aligned to a territory. Sarah creates fields to contain the information in CRM and then maps the start_date__aln and end_date__aln fields to those CRM fields.
If either the start_date__aln or end_date__aln field is mapped to a CRM field without a value when upserting information, Vault rejects the upsert attempt.