Description: The three-letter ISO 4217 currency code associated with the usage record when multiple currencies are enabled.
LastActivityDate
Type: date
Properties: Filter, Group, Nillable, Sort
Description: The timestamp of when a user had last associated a task or event action with the usage record.
LastReferencedDate
Type: dateTime
Properties: Filter, Nillable, Sort
Description: The timestamp when the current user last accessed a usage record indirectly, for example, through a list view or related record.
LastViewedDate
Type: dateTime
Properties: Filter, Nillable, Sort
Description: The timestamp when the current user last viewed a usage record. If this value is null, it’s possible that the user only accessed the usage record or a related list view (LastReferencedDate), but not viewed the usage record itself.
Name
Type: string
Properties: Autonumber, Defaulted on create, Filter, idLookup, Sort
Description: Required. The name of the usage record.
OwnerId
Type: reference
Properties: Create, Defaulted on create, Filter, Group, Sort, Update
Description: Required. The ID of the record owner.
Description: This field is filled in based on the consumption schedule. Usages are evaluated against usage summaries where the matching ID, matching attribute, and unit of measure fields align. When the charge type is usage, legacy usage pricing does not consider this field.
Description: Required. A usage and a usage summary are linked through a lookup relationship. For the usage to be included in the usage summary, both records must have the same matching ID.
blng__Notes__c
Type: textarea
Properties: Create, Nillable, Update
Description: Additional information or comments related to the usage record.
Description: The order product associated with the usage record. This association helps in tracking the usage of a product that’s ordered, which is essential for billing and invoicing purposes.
Description: When users enter a prerated amount on a usage record, Salesforce Billing uses that value for the usage’s total rather than the standard calculation of usage.
Description: Populated from the consumption schedule. Usages are rated against usage summaries where the matching ID, matching attribute, and unit of measure fields match. When the charge type is usage, legacy usage pricing ignores this field.
Description: A usage summary’s unit price is based on where the summary’s total quantity falls within the price schedule. When you use volume price schedules, your usage records and usage summary all have the same unit price. But for tiered price schedules, your usages could have different unit prices than the usage summary based on how their quantity ranges fall in each price tier.
j