Summary
Field-by-field reference for the RDLA Faculty Resource Use object (Faculty_Resource_Uses__c): labels, API names, data types, how each field is populated, and picklist values.
Body
Field-by-field reference for the RDLA Faculty Resource Use object (Faculty_Resource_Uses__c). Junction recording a faculty member's use of a Research Database, used on the Intellectual Contribution side.
Part of the RDLA field definitions. For the step-by-step user guides, see Research Database Lifecycle - RDLA.
- Relationships: Lookup to Contact (faculty member) and two lookups to Faculty Resource (Research Database, Intellectual Contribution). Name is auto-number FRU-{000000}. RDLA_Admin also grants FLS on Class__c, which now has a field file in local source.
Fields
| Field / API Name | Type | Entry | Description | Picklist Values |
Class Class__c | Lookup(Class) | | The class the faculty member used the database. | |
Faculty Member Faculty_Member__c | Lookup(Contact) | | | |
Faculty Resource Use Name Name | Auto Number | Automatic | System field | |
Intellectual Contribution Intellectual_Contribution__c | Lookup(Faculty Resource) | | | |
Research Database Research_Database__c | Lookup(Faculty Resource) | | | |
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.