Nodes=rsMaster,rsSecondary

Datetime fields must use the format “yyyyMMdd HHmm".

DelayImport=180  # This is for 3 minutes  60*3 = 180

NameSpacePrefix =ns2  # This data would be found at the root element in the xml doc

NameSpaceUri =http://internal.amazon.com/TrailerInfo  # This data would be found at the root element in the xml doc

ReplaceContent =:TrailerInfo xmlns:“http://www.schema.com”  # This will remove any match for this string to be set to the empty string “”

ReImport=1  # Default is 0 ( no reimport ).

ReportEmail=text@cxtsoftware.com

The address to use for the current route stop.

The address line 2 to use for the current route stop.

rsMaster|BOL=0,ABC123geo

The city to use for the current route stop.

The primary reference for looking up route translations (See Configuration: X Import Translations.)

The secondary reference for looking up route translations (See Configuration: X Import Translations.)

Requires X Dispatch 11.1 or newer.

This functionality makes use of the “Auto assign pickup to route by rule” and “Auto assign delivery to route by rule” options on the Order Type edit form in X Dispatch.

Requires X Dispatch 11.1 or newer.

Requires X Dispatch 11.3.4 or newer.

Requires X Dispatch 15.2.0 or newer.

This does not work with a hardcoded value in the .XASN configuration.

rsMaster|GeoCode=0,1

The name to use for the imported route stop.

rsMaster|NodeName=0,ProcessRouteASN

The number of pieces on the order. If this is not specified or is less than the number of parcels sent in for the route stop, the piece count will be set by the number of parcels specified in the request

The PK field sets the primary key for linking the rsMaster and rsSecondary data sets. rsMaster|PK should match rsSecondary|FK. The best fields to use for the primary key will generally be the original tracking or order number from the ASN.

The 4-digit postal code extension for the stop.

The date on which this route stop should be posted.

User-defined reference field 1.

User-defined reference field 2.

The route ID onto which the route stops should be placed (See Configuration: X Import Translations, 486342739, 486342739.)

The sequence number for the route stops. Generally, it is better to leave this item out of your configuration file and let the stops be auto sequenced on import. As such, if you wish for stops to sequence on your specified value here, then you must disable auto sequencing.

The state to use for the imported route stop.

Stop-specific notes (e.g., “Dock 12”)

This field can be set to “0,” which will set it to blank value and utilize the stop time preferred mappings or the current system time (at time of import).

If this field is not set, then the system will use the current system time (at time of import).

The stop type. Defaults to 1 (Delivery) if not specified or if an invalid stop type (anything other than 0-6) is specified.

The net weight of all parcels on this route stop. If this field is not specified, the cumulative weight of all parcels sent in will be used instead.

The postal code of the route stop.Secondary

If you specify an ItemID here, you must specify a quantity for the item in rsMaster|Accessorial1Quantity. 

rsMaster|Accessorial1ID = 8

If you specify a quantity here, you must specify an ItemID for the item in rsMaster|Accessorial1ID. 

rsMaster|Accessorial1Quantity = 1

If you specify an ItemID here, you must specify a quantity for the item in rsMaster|Accessorial2Quantity. 

rsMaster|Accessorial2ID=0,10 

If you specify a quantity here, you must specify an ItemID for the item in rsMaster|Accessorial2ID. 

rsMaster|Accessorial2Quantity = 0,4

User data field 1.

User data field 2.

User data field 3.

User data field 4.

User data field 5.

User data field 6.

Min stop time.

Max stop time.

Short remarks.

Long remarks.

Email pod.

Secondary lookup for X Mobile.

Force Location Barcode (Mobile Secondary Lookup) checkbox, for Nextstop Mobile workflow. 

rsMaster|ForceLocationScan=0,true

When configured as true, this feature sets the driver requirement to perform a location scan for the route stop.

Customer route ID.

Customer stop ID.

Customer account ID.

Route pay override.

rsMaster|RouteOverride=0,5.00

The following will add an Override Settlement of $0.00 if LD is present in the S502 element but if not, will not function at all. Replace the 0 with a dollar amount if you want to include an Else scenario: rsMaster|RouteOverride=IIF(S502;"LD";"0.00";0)The following will add an Override Settlement of $0.00 if LD is present in the S502 element but if not, will not function at all. Replace the 0 with a dollar amount if you want to include an Else scenario: rsMaster|RouteOverride=IIF(S502;"LD";"0.00";0)

Flag that determines if the route stops should be auto sequenced. True value is '1', False value is '0'. Defaults to '1' if the value is omitted from the file.

Data: AdvancedFallbackLookup1 is stored in tblOrderRouteStops in the AdvancedFallbackLookup1 column. It is the ALF1 field under the miscellaneous tab in X Dispatch.

Data: AdvancedFallbackLookup2 is stored in tblOrderRouteStops in the AdvancedFallbackLookup2 column. It is the ALF2 field under the miscellaneous tab in X Dispatch.

Data: RateChartOverrideLookup is stored in tblOrderRouteStops in the RateChartOverrideLookup column. It is the Rate Chart Lookup under field under the miscellaneous tab in X Dispatch.

rsMaster|ConsolidateStops=0,1

Intended to consolidate stops between ASN files. Use any string to set consolidation value - can be at any level.

rsMaster|ConsolidationText=230,6;236,6  # fixed width file: column 230, length=6 and column 236, length = 6.
rsMaster|ConsolidationText=1  # eg: 1 = column in csv file
rsMaster|ConsolidationText=APPEND(18,NOW&08:00|DAYFLOOR);APPEND(5," | ");APPEND(6,230,12)  # date and values (12 characters starting at position 230) separated by a pipe

ConsolidationText creates record in database in cxtData.dbo.tblOrderRouteStops_Consolidated. ConsolidationText should include the date since the consolidation text will try to look up anything that matches within the last 30 days.

rsMaster|ODSyncFieldCustID

rsMaster|ODSyncFieldBillingGroup

rsMaster|ODSyncFieldBillOfLading

rsMaster|ODSyncFieldDeliverDate

rsMaster|ODSyncFieldDestAddress

rsMaster|ODSyncFieldDestCity

rsMaster|ODSyncFieldDestComments

rsMaster|ODSyncFieldDestContactPhone

rsMaster|ODSyncFieldDestName

rsMaster|ODSyncFieldDestPlus4

rsMaster|ODSyncFieldDestState

rsMaster|ODSyncFieldDestSuite

rsMaster|ODSyncFieldDestZip

rsMaster|ODSyncFieldEmailOrderConfirmationChecked

rsMaster|ODSyncFieldEmailPOD

rsMaster|ODSyncFieldEmailPODChecked

rsMaster|ODSyncFieldEmailPOPChecked

rsMaster|ODSyncFieldMasterBillOfLading

rsMaster|ODSyncFieldOrderType

rsMaster|ODSyncFieldOriginAddress

rsMaster|ODSyncFieldOriginCity

rsMaster|ODSyncFieldOriginComments

rsMaster|ODSyncFieldOriginName

rsMaster|ODSyncFieldOriginPlus4

rsMaster|ODSyncFieldOriginState

rsMaster|ODSyncFieldOriginSuite

rsMaster|ODSyncFieldOriginZip

rsMaster|ODSyncFieldOverrideDeliveryTimeFrom

rsMaster|ODSyncFieldOverrideDeliveryTimeTo

rsMaster|ODSyncFieldOverrideReadyTimeFrom

rsMaster|ODSyncFieldOverrideReadyTimeTo

rsMaster|ODSyncFieldParcelPieces

rsMaster|ODSyncFieldParcelWeight

rsMaster|ODSyncFieldPickupDate

rsMaster|ODSyncFieldReference1

rsMaster|ODSyncFieldReference2

rsMaster|ODSyncFieldReportEmail

rsMaster|ODSyncFieldServiceType

rsMaster|ODSyncFieldSpecialInst

rsMaster|ODSyncFieldUserField0

rsMaster|ODSyncFieldUserField1

rsMaster|ODSyncFieldUserField2

rsMaster|ODSyncFieldUserField3

rsMaster|ODSyncFieldUserField4

rsMaster|ODSyncFieldUserField5

rsMaster|ODSyncFieldUserField6

rsMaster|ODSyncFieldUserField7

rsMaster|ODSyncFieldUserField8

rsMaster|ODSyncFieldUserField9

rsMaster|ODSyncFieldUserField10

rsMaster|ODSyncFieldUserField11

rsMaster|ODSyncFieldUserField12

rsMaster|ValidationFailOver=0,LatLonMin

The goecode bit needs to be turned on for the LatLonMin ValidationFailOver process to return lat/lon coordinates.

rsMaster|GeoCode=0,1

This value might exist above the location of the parcel node.  If this is the case, you can use the “../” notation to pull data from a node that exists above the parcel node.

rsSecondary|NodeName=0,Parcel

The number of pieces or items contained within this parcel.

Parcel-level barcode.

The carrier-defined parcel type to use for the imported parcel.  The ParcelType text can be the numeric ParcelTypeID from tblParcelTypes or the Description from tblParcelTypes - Description performs a wildcard search and used the first ParcelTypeID found where the Description contains the ParcelType text.

The weight associated with this parcel.

The PK field on the secondary node is used when aggregating parcels onto route stops. Generally, this item should be set to a unique parcel-level barcode, or a combination of route, stop, or any other uniquely identifying information.

Description of the parcel.

Secondary reference field for the parcel.

Secondary reference field for the parcel. This sets the Parcel Consolidation Barcode.

This sets the Parcel Consolidation Barcode 2

This is a dynamic field, which will store any amount of data as properties in a JSON object in the database. The [...] above can be replaced with any string and used as many times as needed. Data can be queried using a function that engineering has created. 

Example

Using the following in a XASN will store data as a property in a JSON object. 

rsMaster|MiscData|testfield1=0,sampledata

Execute

SELECT dbo.ParseJSONField(MiscData, 'testfield1') AS testfield1 FROM tblAdditionalData

Returns
“sampledata”

Example

Using the following in a XASN will store data as a property in a JSON object. 

rsMaster|MiscData|IntegrationData1=0,SampleA
rsMaster|MiscData|IntegrationData2=0,SampleB
rsMaster|MiscData|IntegrationData3=0,SampleC

Execute

SELECT
	dbo.ParseJSONField(MiscData, 'IntegrationData1’) AS [Column1]
	dbo.ParseJSONField(MiscData, 'IntegrationData2’) AS [Column2]
	dbo.ParseJSONField(MiscData, 'IntegrationData3’) AS [Column3]
FROM tblAdditionalData

Returns
“tblAdditionalData.PKID = tblOrderRouteStops.PKID”