hello I am Masha from Kraus fuse and in this video we will take a look at cross fuse file importer utility and how to use it out of box ServiceNow has the option to import a file from a remote location this option is good if you are importing this file from an FTP or an FTPS server so if you have data behind your corporate firewall and you don't want to set up an FTP server to publish it out on the internet cross views scheduled file importer will give you the ability to keep your data on your network and make it available to your ServiceNow instance for import via image server let's see how it works in the lab that left nav under system import sets application locate file import section and click on cross views file import module here you will see two records that were generated as an example but let's go ahead and create a new record let's give it a name under data source tab we need to provide a mid server where our data is located as well as the file path our location on that mid server of the data that we're importing this can be a local path or a remote path with a map drive on the right hand side we have an option to specify the pre scriptor and post script that will run for import prescript allows you to specify a script that will run on the mid server before the data is imported think of this as if the script is being run in the terminal window of the mid server itself typically the script will trigger the data generation process and assuming that this script has created the file specified in the file location field we should be ready to run our import and for the example sakes this script could look something like this PostScript allows you to specify a script that will run on the mid server after the data has been imported to ServiceNow again it is like this script is being ran in the terminal window of the mid server itself and you might use it to delete the file on the mid server that was imported to ServiceNow or maybe to move that file to a processed folder and that example could look something like this whether you choose to run pre script or post script please keep in mind the OS setters running on the mid server and tailor these scripts or commands accordingly for this example we will not be using either one of this so I will go ahead and clear out the options and let's move on to the data target tab where we will specify the import set table where we want our results to go to and we'll have an option to specify the user that we want the process to run as and for my example I will go ahead and clear it out under schedule tab we have an option to specify the schedule we want our import to run on and these are standard options and I'm going to go ahead and select on-demand for my example and save our record now we have a complete file import record we are ready to run our import we'll go ahead and click execute now at which point the mid server will grab the data specified in our file location path and import that data into service now if we refresh our accused related list here we will see two records there will be an output record that is in process state and input record that is in ready state let's navigate to the input record here we'll see some debug information as well as the steps that were taken during the process and the response status code in this kated case it is 200 which means success if there were any errors generated during the import process they would be reflected here since our import was successful let's go ahead and check out the results in our import set table we see the records that were imported from our file on mid server and now they are ready for the next step of being transformed into our target table