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/Leave Request — entity reference
REFERENCE · Last reviewed

Leave Request — entity reference

A person's request for time off across a date range, keyed on Resource and never on Employee. Once it reads Approved the row has real effects: the payroll attendance calculation counts overlapping days of an unpaid leave type as Loss of Pay and shrinks payable days, mobile attendance reports the person as on leave for the day, and scheduling drops them from bookable-resource capacity. It never touches Leave Entitlement in any way.

Fields

FieldLabelTypeRequiredWhat it does
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DaysDaysCalculatedNot a day count despite the name - it is a boolean half-day flag, and the payroll attendance calculation halves the request's calendar span when it is true. It is also declared in metadata as a calculated field yet carries no formula, so nothing derives it; it is a plain stored bit.
FromDateFrom DateDate
IdIdGuidYes
LeaveTypeIdLeave TypeLookup
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYes
OwnerIdOwnerLookup → UserAccountYes
ReasonReasonMultiLineText
RecordTypeIdRecord TypeGuid, hidden
ResourceIdResourceLookup → ResourceLeave is keyed on the Resource, not on Employee, so a leave request exists for people who have no payroll Employee record at all. Payroll reaches this row from the Resource side after resolving the employee it is paying.
StatusStatusPickListPayroll and mobile attendance accept Approved or approved; scheduling accepts only the exact-case Approved. Any other wording leaves the request without effect anywhere in the platform. Values: Pending, Approved, Rejected, Cancelled.
ToDateTo DateDateThe last day of the absence, and inclusive: payroll counts the span as this date minus From Date plus one day, clipped to the payroll period being calculated. A single-day request therefore has From Date and To Date equal.
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

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.
NewNewNewNew