Nodes=rsMaster,rsSecondary

Datetime fields must use the format “yyyyMMdd HHmm".

Specifies whether the X Dispatch Internet User's password has been encrypted. Most of the time, this should be set to true.

rsMaster|EncryptedPassword=0,1

Password for the X Dispatch Internet User used for placing orders.

rsMaster|Password=0,testpassword

X Dispatch Internet User to use for placing the orders.

rsMaster|UserID=0,ximport-mckesso

Customer ID used to place the order.

rsMaster|CustID=0,1218

DelayImport is a parameter to delay the processing of a file by a set number of seconds.

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

NameSpacePrefix is a parameter that can be required in some xml inbound documents. If this is being used you will also need to use NameSpaceUri.

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

NameSpaceUri is a parameter that can be required in some xml inbound documents. If this is being used you will also need to use NameSpacePrefix .

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

ReplaceContent is a parameter to replace in the document with the matching value with an empty string.

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

ReImport is a parameter to reimport the processing of a file in the processed directory that does not have a .proc file.

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

The e-mail address to which X Import will send a report about the import process for the current input file. Multiple email addresses should be comma separated. This works for both On Demand and Routed.

ReportEmail=text@cxtsoftware.com

The address to use for the current route stop.

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

The BOL (Bill of Lading) data to which route stops may be associated.  

Maximum length = 50.

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

If a fixed RouteID is not set, and CustRouteID/CustSecondary lookup is not utilized or fails to find a match, the database tries to find the lowest OrderTypeID that contains a destination sort rule and uses that sort rule to try and determine the route. 

RouteSortRuleID allows you to explicitly set the route sort rule used to set the route in that case.  This means you can use an existing route sort rule instead of setting up translations or can set a specific sort rule to use as a fallback should the route translations fail.

On a dynamic route stop, it is possible to set a specific GL account to assign to that stop.  In order to override the GL account for an imported route stop, set this optional field to the ID of the GL Account you wish to use as the override.

This value sets the rate chart override lookup value, to be checked against values in the X Stream Route Mappings section. If the values match, the Translation field of the route mappings will be used as the stamp rate chart ID for rating all items on that route stop, rather than the customer’s default stamp rate chart ID.

This value sets the rate chart secondary override lookup value, to be checked against values in the X Stream Route Mappings section’s Reference2 field, and if the values match, the Translation field of the route mappings will be used as the stamp rate chart ID for rating all items on that route stop, rather than the customer’s default stamp rate chart ID. If specified, this will be required in order to match. 

Whether address should be geocoded to retrieve latitude and longitude, as well as validate the postal code up to 9 digits. This should generally be set to true. 

rsMaster|GeoCode=0,1

The name to use for the imported route stop.

The master node name should always be set to “ProcessRouteASN”

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”)

The time at which this stop should be scheduled.

The time at which this stop should be scheduled if the StopTime set to “0,” which will set it to a blank value. 

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

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.

Flag determines if stops Consolidate. Set to '1' to turn on consolidation.  Intended to consolidate stops from separate ASN files that would have consolidated if they were contained in the same ASN file.  RouteID, PostDate, CustID, Address, City, State, Zip are used to identify stop to consolidate with. This searches any route for consolidation keys newer than 30 days from current date. The behavior will allow stops to be created and NOT consolidate.Mapping

Please note that this feature only works if the RouteID is being passed in from the ASN directly.  If Route Mappings and/or Route Sort Rules are utilized, the Consolidation will fail.

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.

The following 'ODSyncField' fields are available to match for synchronization with on demand orders.  Each field is optional.  If a match is found the stop is not imported.  The field name is 'rsMaster|ODSyncField' prepended to the XINI field name found in the on demand section of this document.

When used, returns at the minimum the specified value information when the address does not validate as an exact match.

Valid types are:

1. LatLonMin - return the new lat/long coordinates only. (keeps old address.)
2. AddressMin - return the new address only. (keeps old lat/long data.)

rsMaster|ValidationFailOver=0,LatLonMin

The FK field sets the foreign 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 secondary node name should always be set to “Parcel”

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”

DataPath=E:\ximport\CardinalOD
DataMask=XML
ProcPath=e:\ximport\Processed
ErrPath=e:\ximport\Error
URL=http://127.0.0.1/XMLListener.asp
Delimiter=XML
NumLinesSkipped=0
 
Nodes=rsMaster,rsSecondary
 
rsMaster|UserID=0,test
rsMaster|Password=0,TESTTEST
rsMaster|EncryptedPassword=0,1
rsMaster|CustID=0,1218
rsMaster|CustRouteID=230,6
rsMaster|CustSecondaryLookup=0,x
rsMaster|ContractID=0,69290
rsMaster|NodeName=0,ProcessRouteASN
rsMaster|PK=Route$RouteNumber,Route/Stop$StopNumber,Route/Stop/Customer$CustomerNumber
rsMaster|BaseNode=/CardinalDistributionShipmentFile/Shipment
rsMaster|Address=Route/Stop/Customer$CustomerAddress
rsMaster|City=Route/Stop/Customer$CustomerCity
rsMaster|GeoCode=0,1
rsMaster|Name=Route/Stop/Customer$CustomerName1
rsMaster|PostDate=Route/Stop/Customer$InvoiceDate
rsMaster|Reference1=Route/Stop/Customer$CustomerNumber
rsMaster|State=Route/Stop/Customer$CustomerState
rsMaster|StopNotes=Route/Stop/Customer$CustomerName2
rsMaster|StopTime=0,12:00
rsMaster|Zip=Route/Stop/Customer$CustomerZip
 
rsSecondary|NodeName=0,Parcel
rsSecondary|PK=Route/Stop/Customer/ToteCase$ToteCaseID
rsSecondary|FK=Route$RouteNumber,Route/Stop$StopNumber,Route/Stop/Customer$CustomerNumber
rsSecondary|ParcelReference=Route/Stop/Customer/ToteCase$ToteCaseID
rsSecondary|ParcelPieces=1