In the Carrier PreSettings tab, you can specify codes from your ERP system that can be used to select a specific location, actor, subcarrier, product, and services to produce a shipment. To learn more about using expressions, please go to the article: Using expressions in your import setup.
The fields in the example above are of the type Field.Īdding expressions to your import setup gives you the possibility to set up different rules and compare and switch values in different fields. Choose between a normal field and an expression. When adding a field, you must choose the field type. You can add or delete fields by clicking the Fields button. If you have a field in your file that should be ignored by On-premises, you can keep the value Unknown->Unknown. In the screen below, all fields have been mapped.You can search in the drop-down list by typing. Map the fields by clicking on each line in the Shipment Field column and selecting the matching On-premises field from the drop-down list.Choose Select file, locate a file and click Preview to see a list of all the fields in the file. This is easier to do if you have a sample file from your system. Now you must map the fields in your files to fields in On-premises.Click the Unit button to specify your units and click OK. Different systems use different units, so it is important to specify the units used in your files.(To use XML files, you must click the Select button and specify an XSLT file).
Specify the Character separator used in your files.This article explains the settings needed for a basic import setup. The Import Setup tab contains a lot of functionality.
GET PAST FILEDROP REGISTER SCREEN HOW TO
You must tell On-premises how to read the files from your system by specifying the character separator and how to map the fields in the file to fields in On-premises. You can choose to automatically delete it, move it to the recycle bin or move it to a specified folder. In the After Import section, you must select what should happen after On-premises has processed a file.Multiple sources will be processed one by one. The number of threads corresponds to the number of files that can be imported simultaneously from the same source folder. Threads are used to process several files simultaneously.It is possible to add multiple source folders. Click New and specify a Source Folder where On-premises pick up the files from your system.The integration is only active when this checkbox is checked, and it must be active to make any changes. Right-click on the right-hand side of the screen and select New > Import Setup. It can be placed on either Installation, Location, or Actor level. Go to Setup and select where you want to place the import setup.If you are using XML files, the import transforms the files based on an XSLT stylesheet which you must specify. This format is easy to work with but DeliveryHub supports almost any format including flat text files, standard field length, Excel, and XML. We have used a CSV file in the examples below. On-premises will monitor the folder and as soon as a recognizable file is available in the import folder, On-premises will import and read the file, and either delete it or move it to a backup folder after processing. The system must be able to create a file and drop it in a shared folder that both systems have access to. On-premises can import orders from any system that can provide a file. Please contact our customer service if you need help to configure your integration or if you have questions regarding the advanced configuration possibilities. This article will explain how to set up a basic filedrop integration in nShift On-premises. The filedrop integration (Import Setup) in On-premises has a lot of advanced possibilities and can be configured to fit almost any setup. The majority of nShift customers have some kind of integration between DeliveryHub and their ERP, WMS, or other systems.