Description: The three-letter ISO 4217 currency code associated with the usage summary 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 summary record.
LastReferencedDate
Type: dateTime
Properties: Filter, Nillable, Sort
Description: The timestamp when the current user last accessed a usage summary 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 summary record. If this value is null, it’s possible that the user only accessed the usage summary record or a related list view (LastReferencedDate), but not viewed the usage summary record itself.
Name
Type: string
Properties: Autonumber, Defaulted on create, Filter, idLookup, Sort
Description: Required. The name of the usage summary record.
OwnerId
Type: reference
Properties: Create, Defaulted on create, Filter, Group, Sort, Update
Description: Required. The ID of the record owner.
Description: The total quantity of this summary’s usage that Salesforce Billing has billed. The billed quantity can contain usage from one or more usage records.
Description: Populated from the consumption schedule. Usages are rated against usage summaries where the matching ID, matching attribute, and unit of measure match. When charge type is usage, legacy usage pricing ignores this field.
Description: Salesforce Billing uploads usage only to usage summaries with matching IDs. Create a workflow rule that populates your usages and usage summaries based on certain criteria.
Description: The date that this usage summary is due for billing. The target date on an invoice run must be after this date for the usage summary to be invoiced. When you use bill now, the effective target date must be after this date.
blng__Notes__c
Type: textarea
Properties: Create, Nillable, Update
Description: Additional information or comments related to the usage summary record.
Description: The order product associated with the usage summary record. This association helps in tracking the usage of a product that’s ordered, which is essential for billing and invoicing purposes.
Description: When the status is set to Canceled, the usage summary does not load any additional usage, and the unique IDis cleared. Despite this, the usage summary can still be invoiced, as invoicing isn’t blocked.
Description: Salesforce Billing automatically calculates your summary’s start and end dates based on your order product’s next billing date and billing frequency. However, you can enter a date in this field to override the default summary end date.
Description: Salesforce Billing automatically calculates your summary’s start and end dates based on your order product’s next billing date and billing frequency. However, you can enter a date in this field to override the default summary start date.
Description: The total amount value of prerated usage across all of this summary’s usage records. 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.
Description: The total quantity value of prerated usage across all of this summary’s usage records. 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.
Description: The subtotal amount for a usage summary record.
blng__SummaryEndDate__c
Type: date
Properties: Create, Filter, Group, Sort, Update
Description: Required. Salesforce Billing includes usage in a usage summary if the records have matching IDs and the usage’s processing date falls within the summary’s start and end dates.
blng__SummaryStartDate__c
Type: date
Properties: Create, Filter, Group, Sort, Update
Description: Required. Salesforce Billing includes usage in a usage summary if the records have matching IDs and the usage’s processing date falls within the summary’s start and end dates.
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 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 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