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

Visit Route — entity reference

The beat master: a named, reusable journey whose outlets are child VisitRouteStop rows and whose recurrence drives visit-plan generation (weekday flags plus weekNumbers, or a cron expression that overrides them). Owned either by a person (resourceId) or, in position-based assignment, by a seat (positionId) - in the latter case resourceId is a system-maintained cache of the seat's current holder. Carries defaults that flow to plans and their visits (visitPurpose, visitTaskTemplateId, partnerAccountId, accountGroupId, itemGroupId) and holds the stored orderings of its stops as child RouteSequence runs. Grouped under a VisitRouteGroup for territory planning.

Fields

FieldLabelTypeRequiredWhat it does
AccountGroupIdAccount GroupLookup → AccountGroup
CoverageMidpointDistanceCoverage Midpoint Distance (KM)Number
CoverageMidpointLocationCoverage Midpoint LocationGeoLocation
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
DayNumbersDay NumbersTextCSV of ISO weekday numbers (1=Monday..7=Sunday) kept two-way in sync with the seven boolean day flags by the handler: editing the CSV rewrites the flags and vice versa. Together with weekNumbers it drives when plans are generated for the route, unless scheduleCron overrides.
EffectiveFromEffective FromDateAndTime
EffectiveToEffective ToDateAndTime
FridayAvailableFriday AvailableBoolean
IdIdGuidYes
IsActiveActiveBoolean
ItemGroupIdItem GroupLookup → ItemGroup
ModifiedByIdModified ByLookup → UserAccountYes
MondayAvailableMonday AvailableBoolean
NameNameText
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountGroupIdPartner Account GroupLookup → AccountGroup
PartnerAccountIdPartner AccountLookup → Account
PositionIdPositionLookup → PositionThe seat that owns this route. When set, Resource is kept in sync with the seat's current holder automatically.
RecordTypeIdRecord TypeGuid, hidden
RemarksRemarksText
ResourceIdResourceLookup → ResourceThe route's owning salesperson. On seat-owned routes (positionId set) this is a derived cache of the seat's current holder and is restamped automatically on handovers - do not treat a manual edit as durable there.
RouteNameRoute NameLongMultiLineText
RoutingPriorityRouting PriorityPickListValues: Shortest Distance, Shortest Time.
SaturdayAvailableSaturday AvailableBoolean
StartTimeStart TimeTimeOnly
SundayAvailableSunday AvailableBoolean
ThursdayAvailableThursday AvailableBoolean
TuesdayAvailableTuesday AvailableBoolean
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes
VisitPurposeVisit PurposePickListValues: Service Touch, Order Capture, Order Delivery, Field Service, Product Demo, Courtesy Visit, Payment Collection.
VisitRouteGroupIdVisit Route GroupLookup → VisitRouteGroup
VisitTaskTemplateIdVisit Task TemplateLookup → VisitTaskTemplateDefault execution playbook for the route: copied onto plans created from the route and from there onto generated visits (a stop-level template overrides it per stop).
WednesdayAvailableWednesday AvailableBoolean
WeekNumbersWeek NumbersTextRestricts plan generation to specific weeks of the month alongside the weekday flags; ignored when scheduleCron is set.

Actions

ActionLabelTypeWhat it does
AssignPositionsFromOwnersAssign Positions from OwnersServerAction (AssignPositionsFromOwners)Converts person-owned routes to seat ownership: finds each route executive's Position (their open Executive Position mapping), creating the Position and mapping when none exists, then stamps the route. Idempotent - routes already on a position are skipped
BulkDeleteDeleteDeleteDelete
CloneCloneServerAction (Clone)Create a copy of this record
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete
EditEditEditEdit
EditInLineEditEditInlineEdit
EditInListEditEditInlineEdit In List Header
EditPopupEditEditEdit
NewNewNewNew
OptimizeRouteSequenceOptimize Route SequenceServerAction (OptimizeRouteSequence)Paid road-network optimization of the route's APPROVED stops via the configured routing provider, appended as the new current Optimized RouteSequence - unlike the nearest-neighbour runs its distance and duration are real driving totals. The planner picks the new order up on the next plan creation; already-generated plans are untouched. Geo-less stops trail in authored order. Fails validation (without spending a provider request) when the provider is unconfigured or the route has no approved, geocoded stops.
RecomputeRouteSequencesRecompute SequencesServerAction (RecomputeRouteSequences)Refreshes the route's stored orderings in the RouteSequence source of record: one route-generic Optimized run (free nearest-neighbour over the approved stops' coordinates) plus MostlyFollowed runs computed from actual visit history - route-generic and one per salesperson with started-visit history. Each new run becomes current within its family; superseded runs keep their rows as history. Costs no external provider request.

Validations

ValidationApplies toError messageNotes
Effective From Field ValidationEffectiveFrom, Error, inactiveEffective From date cannot be in the past.Effective From date cannot be in the past.

Lookup filters

FilterLookup fieldNotes
Partner AccountPartnerAccountId
ActiveResourceResourceId