xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse 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
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/Check In Inspection — entity reference
REFERENCE · Last reviewed

Check In Inspection — entity reference

The header record for taking custody of a customer asset at the start of a job: who brought it in, when, which asset and account, the service advisor, and optional pick-up/drop-off logistics. It is not a goods-receipt inspection (that is InspectionLine on the procurement side); it is the vehicle/equipment condition record raised against an Asset, and its damage findings live in child CheckInInspectionLine rows. It has no server-side handler at all - creation, editing and status are pure metadata CRUD - so every effect comes from the client: the web and mobile Check-In Inspection widget writes the lines, and the field-service visit activity flow creates the header and links it with ServiceOrderId. Note the two independent links to a service order: this entity's own ServiceOrderId (what the visit flow writes) and ServiceOrder.CheckInInspectionId (a separate manual link no code sets).

Fields

FieldLabelTypeRequiredWhat it does
AccountIdAccountLookup → Account
AgeingAgeingCalculatedA boolean, not an age in days - despite the name it cannot hold a duration.
AssetIdAssetLookup → Asset
BranchIdBranchLookup → Branch
CheckInDateTimeCheck-In Date TimeDateAndTime
CheckInInspectionCheck-In InspectionNumberYesIgnore it entirely when building queries, filters or layouts - referencing it will fail rather than return a value.
CheckInTypeCheck-In TypePickListClassifies why the asset was taken in. The picklist ships with only 'Service', yet the field-service visit activity flow writes 'Field Service', a value that is not in the list - so expect at least those two values in practice and do not assume the picklist is exhaustive. Values: Service.
CheckOutDateTimeCheck-Out Date TimeDateAndTime
ContactAddressIdContact AddressLookup → ContactAddress
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DocumentDateDocument DateDate
DropoffAddressDrop-off AddressMultiLineTextA free-text address string, entirely separate from the DropOffAddressId identifier field; neither is derived from the other and no code keeps them consistent. Use it as a typed-in note, not as a resolvable address record.
DropOffAddressIdDrop Off AddressLookupA bare identifier with no declared related entity and no navigation on the domain type, so unlike ContactAddressId it does not resolve to an address record and cannot be expanded in a query.
DropOffDateTimeDrop Off Date TimeDateAndTime
ExternalIdExternalText, unique
IdIdGuidYes
IsDropoffRequiredIs Drop-off RequiredBooleanYesNon-nullable, so it must be supplied on create; it declares whether the asset has to be returned to a drop-off address rather than collected. The field-service visit path always sends false because on-site work never involves a drop-off. It only marks intent - nothing schedules, validates or blocks on the drop-off address or date.
MobileNumberMobile NumberText
ModifiedByIdModified ByLookup → UserAccount
NameNameTextYes
OpportunityIdOpportunityLookup → Opportunity
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → Account
PickUpByIdPick Up ByLookupIntended to name whoever collected the asset, but it is a bare identifier with no declared related entity and no navigation on the domain type, so it does not resolve to a Resource, contact or user. It cannot be expanded or joined - only compared as a raw value.
PickUpDateTimePick Up Date TimeDateAndTime
RecordTypeIdRecord TypeGuid, hidden
RemarksRemarksText
ServiceAdvisorIdService AdvisorLookup → ResourceThe Resource who owns the customer relationship for this check-in. It is a Resource lookup, so it resolves to the person master used across service, payroll and field work - not to a user account.
ServiceOrderIdService OrderLookup → ServiceOrderPoints at the service order this check-in belongs to, and this is the direction the field-service visit flow actually populates when it raises a check-in during a visit. Do not confuse it with ServiceOrder.CheckInInspectionId, the reverse link on the service order, which no code path writes - the two can disagree.
ServiceTypeIdService Type (Depreciated)LookupDeprecated - the label itself carries the marker. It is a bare identifier column with no declared lookup target and no navigation on the domain type, so it cannot be joined to a service-type record; treat any value found here as legacy data.
StatusStatusPickListFree text with a picklist offering Draft, Checked-In and Checked-Out, but no code enforces it and no transition logic exists. Values: Checked-In, Draft, Checked-Out.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes
UsageReadingUsage ReadingNumberThe asset's meter reading captured at check-in (odometer-style whole units), written by the field-service visit activity form when the technician enters one. It is stored only - nothing validates it against the asset's previous reading and nothing downstream consumes it for service-interval or warranty calculations.
UsageReadingHoursUsage Reading (Hours)NumberThe hour-meter counterpart of UsageReading for assets measured in running hours rather than distance, also captured by the field-service visit activity form. Both are plain integers with no unit recorded, and neither is compared against the asset's history or used by any downstream calculation.
VerifiedOkVerified OkBooleanYesA user-set flag asserting the asset was received in acceptable condition. Nothing computes it: no code path reads or writes it, and in particular it is not derived from whether any CheckInInspectionLine findings exist, so it can be true on an inspection full of recorded damage.
VerifiedWithDiscrepanciesVerified With DiscrepanciesBooleanYesA user-set flag asserting the asset was received but with issues noted. Like its counterpart it is purely declarative - no code reads or writes it, and it is not reconciled against the recorded inspection lines, so the two verified flags can both be set or both be clear.

Actions

ActionLabelTypeWhat it does
BulkDeleteDeleteDeleteDelete the selected records.
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete in a list page
EditEditEditEdit
EditinLineEditEditEdit in page.
EditInLine2EditEditInlineEditInLine
EditInLineHeaderEditEditInlineEditInLineHeader
NewNewNewInlineNew

Validations

ValidationApplies toError messageNotes
XM_CheckInDateTimeValidationRuleCheckInDateTime, ErrorCheckInDate Time can not be less then Today.CheckInDate Time can not be less then Today.
XM_DocumentDateValidationRuleDocumentDate, ErrorDocument date can not be less than Today.Document date can not be less than Today.
Usage Reading Validation RuleUsageReading, ErrorUsage Reading cannot be less than zeroPrevents zero or negative usage reading