AccountGroupId | Account Group | Lookup | | Scoping a van run to a set of outlets is done through the linked visit plan and route, not here. |
BranchId | Branch | Lookup | | |
CashDiscrepancyReason | Cash Discrepancy Reason | Text | | |
CashExpected | Cash Expected | Currency | | What the rep should hand in at day end. It is not typed: the day-end rollup overwrites it with the sum of the adjusted amounts of the invoices raised on the run, so it is a computed figure that any manual edit will be discarded on the next rollup. |
CashReceived | Cash Received | Currency | | What the dispatcher actually took at reconciliation, entered by hand. The platform records it beside CashExpected but does not compare them or raise anything on a shortfall - explaining a gap is the purpose of CashDiscrepancyReason. |
CreatedById | Created By | Lookup → UserAccount | Yes | |
CreatedDateTime | Created Date | DateAndTime | Yes | |
DocumentDate | Document Date | Date | | |
ExecutiveResourceId | Executive Resource | ExternalId | | The rep executing the van run; it is what the generated visit plan is assigned to and executed by. Distinct from the record's owner. |
Id | Id | Guid | Yes | |
IsLoadReleased | Is Load Released | Boolean | Yes | |
IsPlanReleased | Is Plan Released | Boolean | Yes | |
IsUnloadReleased | Is Unload Released | Boolean | Yes | |
ModifiedById | Modified By | Lookup → UserAccount | Yes | |
Name | Document Number | Text | Yes | The run's document number, auto-numbered from the tenant's document-name settings. It is also the stem of every artefact the run generates - the load, take-in and unload transfers and their lines are all named from it, which is how they can be traced back to the run. |
OwnerId | Owner | Lookup → UserAccount | Yes | |
PartnerAccountId | Partner Account | Lookup → Account | | |
PerformLoad | Perform Load | Boolean | Yes | The rep's confirmation that stock is physically on the van: on save it creates an inward Transfer for each line's received quantity carrying the take-in damage, shortage and excess figures, sets status to TakenIn, stamps TakenInDateTime, queues the invoice-processor job, and clears itself. Despite the name it is the take-in step, not the dispatcher's release. |
PerformReleaseLoad | Perform Release Load | Boolean | Yes | Setting this true is what dispatches the run: on save the platform creates an outward depot-to-van Transfer for the planned line quantities, sets the run's status to Released, marks IsLoadReleased and clears this flag again. If van capacity checking is set to block and the load exceeds the van, the whole save fails and nothing is released; in warn mode it releases anyway and stamps the overload onto the transfer's label. |
PerformReleaseUnload | Perform Release Unload | Boolean | Yes | The dispatcher's day-end return: on save it creates an inward van-to-depot Transfer for each line's check-in received quantity with the check-in damage, shortage and excess figures, sets status to Reconciled, stamps ReconciledDateTime, marks IsUnloadReleased and clears itself. |
PerformReleaseVisitPlan | Perform Release Visit Plan | Boolean | Yes | Creates the linked visit plan for the run - a fully formed plan named after the run and dated to its document date, typed as a van-sales plan and assigned to the executive resource - then links it, marks IsPlanReleased and clears itself. |
PerformUnload | Perform Unload | Boolean | Yes | Triggers the cash and sales rollup at day end: the run's invoice collections are written onto its FieldSalesInvoice rows and totalled into CashExpected, and sold quantities are accumulated from the invoice lines onto the matching FieldSalesLines. Unlike the other four trigger flags this one is never reset to false by the handler, so it stays set after firing and re-fires on any later save of the record. |
ReconciledDateTime | Reconciled At | DateAndTime | | |
RecordTypeId | Record Type | Guid, hidden | | |
ResourceId | Resource | Lookup | | The rep on the run is ExecutiveResourceId, which is the field that actually persists and flows into the generated visit plan. |
SourceStorageLocationId | Source Storage Location | ExternalId | | The depot the load is drawn from: the source of the outward load transfer and the destination of the unload transfer, the mirror of StorageLocationId which is the van. |
Status | Status | PickList | | Where the run has got to. The service writes exactly four values in sequence - Draft, Released, TakenIn and Reconciled - as the trigger flags fire. The seeded picklist offers a different vocabulary (loaded, unloaded, draft) that does not match what the code writes, so filter on the values above rather than on the option list. Values: Loaded, Unloaded, Draft. |
StorageLocationId | Storage Location | Lookup | | The van itself, modelled as a mobile StorageLocation - it is the destination of the load transfer and the source of the unload transfer, and its declared weight and volume capacity are what the capacity check measures the planned load against. The depot the stock comes from is SourceStorageLocationId, not this. |
TakenInDateTime | Taken In At | DateAndTime | | |
Type | Type | PickList | | Values: Van Delivery, Ready Stock Sales, Pre-Bill. |
UIProps | UI Props | Text | | |
UpdatedDateTime | Modified Date | DateAndTime | Yes | |
VisitPlanId | Visit Plan | Lookup | | |
VisitRouteGroupId | Visit Route Group | Lookup | | |
VisitTaskTemplateId | Visit Task Template | Lookup | | |
