Field-by-field reference for the RDLA Affiliation object (Affiliation__c). The relationship of a Contact to an Account, in this case the vendor contact's relationship to their company as a Database Contact for their company for the specific database.
Part of the RDLA field definitions. For the step-by-step user guides, see Research Database Lifecycle - RDLA.
- Record type: Affiliation Record Type
- Relationships: Junction object - Account and Contact, lookup to Faculty Resource
Fields
| Field / API Name | Type | Entry | Description | Picklist Values |
|---|
Account
Account__c | Master-Detail(Account) | Automatic | The vendor company that owns the database. Any changes would be a new affiliation | |
Affiliation Name
Name | Auto Number | Automatic | Autopopulated record name | |
Affiliation Notes/Description
Description__c | Long Text Area(32768) | User | Used for internal notes and descriptions for the individual affiliation.
Notes about the affiliation relationship | |
Company Name
Company_Name__c | Formula (Text) | Automatic | | |
Contact
Contact__c | Master-Detail(Contact) | Automatic | The vendor contact that is the point person for the database relationship. Any changes would be a new affiliation. | |
Contact Name
Contact_Name__c | Formula (Text) | Automatic | | |
Contact Title
Contact_Title__c | Formula (Text) | Automatic | | |
Current
Current__c | Formula (Checkbox) | Automatic | Formula that calculates if the affiliation is current, based on start/end date | |
End Date
End_Date__c | Date | Automatic, editable | Date the affiliation relationship ends | |
Faculty Resource
Faculty_Resource__c | Lookup(Faculty Resource) | Automatic | Faculty Resource associated with the affiliation. For example, the vendor contact associated with a database.
The database with which the vendor has a relationship. Any changes would be a new affiliation. | |
Record Type
RecordTypeId | Record Type | Automatic | system field, Affiliation Record Type | |
Role
Role__c | Picklist | Automatic | The role the contact holds in relation to the account.
The relationship of the contact to the vendor in terms of the database. Any changes would be a new affiliation. | Board Member
Chair
Co-Chair
Cornell Account Team Member
Database Vendor Contact
Employee
Executive Champion
Former Cornell Account Team Member
Former Employee
Former Key Champion
HR Grad Lead
HR Undergrad Lead
Hotel Ezra Cornell
Key Contact
Matching Gift Champion
Member
Other
Strategy Champion
Team Lead |
Role - Other
Role_Other__c | Text(255) | | | |
Start Date
Start_Date__c | Date | Automatic, editable | Date the affiliation relationship starts | |
Status
Status__c | Picklist | | The current status of the contact's relationship to the account, as defined by this affiliation. | Active
Current
Emeritus
Former
Interim
On Leave
Prospect
Remove
Retired |
Reading the field table
- Entry – User: typed or picked by a person. Automatic: set by Salesforce (a formula, a flow, or the system) and not editable. Automatic, editable: set automatically but can be changed by hand. Not editable: cannot be changed once the record exists.
- Notes in italics describe how the field is used in the RDLA process.
- Picklist values are the ones available on the RDLA record type.
- The standard Salesforce fields Record ID (Id), Created By, Created Date, Last Modified By, Last Modified Date and Owner are on every object and are not listed.