xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
Auto DMSConsumer Goods DMSSales Force Automation (SFA) FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Document Service Contract Line — entity reference
REFERENCE · Last reviewed

Document Service Contract Line — entity reference

A retired design for recording which component items a service contract covers on an individual opportunity, sales order or sales invoice line. It cannot hold data: the platform has no storage table for it, so any attempt to save one is refused, and it is in no seeded app or page. Nothing in the platform reads or writes it. Contract scope is kept in two other places instead: the service contract definition's own lines (the components the definition covers) and, once the contract is sold and its invoice posted, the scope lines on the asset's service contract. Opportunity, quote and service order lines link to a contract through their Item Service Contract field.

Fields

FieldLabelTypeRequiredWhat it does
ComponentItemIdComponent ItemLookupThe component item this line would have covered. Not stored and not read. The components a contract covers are the Component Item values on the service contract definition's lines.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
IdIdGuidYes
IsInScopeIs In ScopeBooleanYesMeant to mark the component as included in or excluded from cover. Not stored and not read. Contracts have no exclusion lists: a component counts as covered only when it is listed on the definition's lines.
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYesRequired on the form, but no record of this type can be saved, so nothing is ever named.
OpportunityLineIdOpportunity LineLookupThe opportunity line this record would have belonged to. Not stored. An opportunity line names its contract in its own Item Service Contract field.
OwnerIdOwnerLookup → UserAccountYes
QuantityQuantityNumberThe quantity of the component that would have been covered. Not stored and not read. Quantity limits are checked against the pending quantity on the asset service contract's scope lines.
RecordTypeIdRecord TypeGuid, hidden
SaleInvoiceLineIdSale Invoice LineLookupThe sales invoice line this record would have belonged to. Not stored. Selling a contract item on an invoice line with an asset, then running the invoice's inventory posting, creates the asset's service contract and copies the definition's lines onto it.
SaleOrderLineIdSale Order LineLookupThe sales order line this record would have belonged to. Not stored and not read.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
BulkDeleteDeleteDeleteDelete
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete
EditEditEditEdit
EditInLineEditEditEdit
NewNewNewNew