RDLA Field Definitions

Field-by-field reference for the Salesforce objects behind the Research Database Lifecycle (RDLA). Each object has its own article listing every field's label, API name, data type, how it gets its value, what it means, and its picklist values. For the step-by-step user guides, see Research Database Lifecycle - RDLA.

Objects

ObjectAPI NamePurposeRelationshipsFields
Faculty ResourceFaculty_Resource__cDatabase record with the details of the specific database.Lookup to Account (vendor record)57
Faculty Resource ConnectionFaculty_Resource_Connection__cA faculty member (or other Contact record) relationship to the Faculty Resource. Database Users, Database Funders, New Database Request, Cornell Stakeholders, Cornell Contacts.Lookup to Contact (faculty/faculty sponsor, student database user record), Faculty Resource objects27
Faculty Resource AccessFaculty_Resource_Access__cDatabase access records, which control the form the faculty database access requestors must answer to request database access. Each database has their own set of FRA records.Lookup to Faculty Resource object13
Faculty Resource Access MetFaculty_Resource_Access_Met__cRecords created by database requestors requesting access to the Database. Connect the FRA to the FRC.Lookup to Faculty Resource Access, Faculty Resource Connection objects11
Faculty Resource UseFaculty_Resource_Uses__cJunction recording a faculty member's use of a Research Database, used on the Intellectual Contribution side.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.5
ContractContract__cThe overarching contract between Cornell and the database vendor to dictate payment, access, etc. Is not necessarily renewed at the end of the contract term, but can continue unless needs changing. Generally all databases have a contract, even donated/free databases.Lookup to Faculty Resource, Account (vendor record) objects21
QuoteQuote__cThe start of the database purchase/renewal process. Funding can be assigned via the Quote Calculator and emails can be sent to faculty funders regarding funding the database purchase.18
InvoiceInvoice__cThe (generally yearly but could be other frequency) payment due by Cornell to fund the use of the database.Lookup to Faculty Resource, Contract objects15
Fund SourceFund_Source__cThe type of fund used to pay for the database. These are standalone records that can be reused across databases (or other objects in the future).No lookups - this is an independent object that represents outbound funds (funds we pay for a reason tracked within Salesforce).9
Fund Source UseFund_Source_Use__cThe actual use of a Fund Source to pay for a database. Can indicate a specific Faculty Funder. An FSU can be linked to a Contract/Invoice, or only to the FR (for example, as a Cost Share).Master Detail - owned by Fund Source, lookup to Contact (faculty funder), Faculty Resource, Contract, Invoice22
AffiliationAffiliation__cThe 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.Junction object - Account and Contact, lookup to Faculty Resource15

Reading the field tables

  • 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.
Was this helpful?
0 reviews
Print Article

Related Articles (12)

Field-by-field reference for the RDLA Affiliation object (Affiliation__c): labels, API names, data types, how each field is populated, and picklist values.
Field-by-field reference for the RDLA Contract object (Contract__c): labels, API names, data types, how each field is populated, and picklist values.
Field-by-field reference for the RDLA Faculty Resource object (Faculty_Resource__c): labels, API names, data types, how each field is populated, and picklist values.
Field-by-field reference for the RDLA Faculty Resource Access object (Faculty_Resource_Access__c): labels, API names, data types, how each field is populated, and picklist values.
Field-by-field reference for the RDLA Faculty Resource Access Met object (Faculty_Resource_Access_Met__c): labels, API names, data types, how each field is populated, and picklist values.
Field-by-field reference for the RDLA Faculty Resource Connection object (Faculty_Resource_Connection__c): labels, API names, data types, how each field is populated, and picklist values.
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.
Field-by-field reference for the RDLA Fund Source object (Fund_Source__c): labels, API names, data types, how each field is populated, and picklist values.
Field-by-field reference for the RDLA Fund Source Use object (Fund_Source_Use__c): labels, API names, data types, how each field is populated, and picklist values.
Field-by-field reference for the RDLA Invoice object (Invoice__c): labels, API names, data types, how each field is populated, and picklist values.
Field-by-field reference for the RDLA Quote object (Quote__c): labels, API names, data types, how each field is populated, and picklist values.
Contains all documentation for the Research Database Lifecycle in Salesforce.