Differences
This shows you the differences between two versions of the page.
|
gt3:loads:import:defined:bulkhandler [31/05/2012 01:57] Ian Davidson [Finishing the Import] |
gt3:loads:import:defined:bulkhandler [20/08/2018 04:24] (current) |
||
|---|---|---|---|
| Line 40: | Line 40: | ||
| * Click //Cancel// to abort the import altogether; for example you might not have realised this file has previously been imported. | * Click //Cancel// to abort the import altogether; for example you might not have realised this file has previously been imported. | ||
| - | In any event a record noting the duplicate and your action will be saved in the [[bulkhandler#The Import Error Log|import error log]]. | + | In any event a record noting the duplicate and your action will be saved in the [[bulkhandler#Managing Import Log Files|import log file]]. |
| If you select the //Use the next auto Load Number// option you'll not be prompted about this because Grain Trader ensures a Load Number is not duplicated. | If you select the //Use the next auto Load Number// option you'll not be prompted about this because Grain Trader ensures a Load Number is not duplicated. | ||
| Line 50: | Line 50: | ||
| * Click //Yes// to save the load with the same Ticket Number. Select this option only if you are certain this load has not been imported before; the duplicate Ticket Number must just be a coincidence. Note that if you have also selected to use the Ticket Number as the Load Number as described above, and a load with that Load Number already exists you will be prompted again about the duplicate Load Number, as described above. | * Click //Yes// to save the load with the same Ticket Number. Select this option only if you are certain this load has not been imported before; the duplicate Ticket Number must just be a coincidence. Note that if you have also selected to use the Ticket Number as the Load Number as described above, and a load with that Load Number already exists you will be prompted again about the duplicate Load Number, as described above. | ||
| - | * Click //No// to skip this load and continue; for example you've imported this file before, have corrected some errors and are now re-importing it. A record noting the duplicate and your action will be saved in the [[bulkhandler#The Import Error Log|import error log]]. | + | * Click //No// to skip this load and continue; for example you've imported this file before, have corrected some errors and are now re-importing it. A record noting the duplicate and your action will be saved in the [[bulkhandler#Managing Import Log Files|import log file]]. |
| - | * Click //Cancel// to abort the import altogether; for example you might not have realised this file has previously been imported. A record noting the duplicate and your action will be saved in the [[bulkhandler#The Import Error Log|import error log]]. | + | * Click //Cancel// to abort the import altogether; for example you might not have realised this file has previously been imported. A record noting the duplicate and your action will be saved in the [[bulkhandler#Managing Import Log Files|import log file]]. |
| - | If you select the //Don't import the load; just log it and skip to the next one// option the record will just be skipped; for example you've imported this file before, have corrected some errors and are now re-importing it. A record noting the duplicate and your action will be saved in the [[bulkhandler#The Import Error Log|import error log]]. | + | If you select the //Don't import the load; just log it and skip to the next one// option the record will just be skipped; for example you've imported this file before, have corrected some errors and are now re-importing it. A record noting the duplicate and your action will be saved in the [[bulkhandler#Managing Import Log Files|import log file]]. |
| ===Contract Mismatch Options=== | ===Contract Mismatch Options=== | ||
| Line 63: | Line 63: | ||
| Take one of the following actions: | Take one of the following actions: | ||
| - | * Click //Yes// to save the load and use this contract anyway. This is the equivalent of clicking the //Show All// button on the Load window in Grain Trader and selecting a Contract with a different Commodity on it. The [[bulkhandler#The Import Error Log|import error log]] record will include a notation that you should check the details for this load. | + | * Click //Yes// to save the load and use this contract anyway. This is the equivalent of clicking the //Show All// button on the Load window in Grain Trader and selecting a Contract with a different Commodity on it. The [[bulkhandler#Managing Import Log Files|import log file]] record will include a notation that you should check the details for this load. |
| * Click //No// to import the load but ignore the imported contract, leaving the Grain Trader Load without a Contract. | * Click //No// to import the load but ignore the imported contract, leaving the Grain Trader Load without a Contract. | ||
| * Click //Cancel// to skip the load altogether. | * Click //Cancel// to skip the load altogether. | ||
| - | In any event the details of the load and your action will be recorded in the [[bulkhandler#The Import Error Log|import error log]]. | + | In any event the details of the load and your action will be recorded in the [[bulkhandler#Managing Import Log Files|import log file]]. |
| The remaining three options on this panel have the same actions as the three responses above, except that the action will be taken automatically and no prompt will be raised. | The remaining three options on this panel have the same actions as the three responses above, except that the action will be taken automatically and no prompt will be raised. | ||
| Line 74: | Line 74: | ||
| If a load being imported contains data for a Metric for which you have not recorded a cross-reference value as described in [[gt3:loads:import:defined:gtimportsetup#matching metrics|Matching Metrics]], this checkbox governs the program's action. | If a load being imported contains data for a Metric for which you have not recorded a cross-reference value as described in [[gt3:loads:import:defined:gtimportsetup#matching metrics|Matching Metrics]], this checkbox governs the program's action. | ||
| - | * If the checkbox is unticked a record will be stored in the [[bulkhandler#The Import Error Log|import error log]]. | + | * If the checkbox is unticked a record will be stored in the [[bulkhandler#Managing Import Log Files|import log file]]. |
| * If the checkbox is ticked, no error will be logged and the data will be ignored. | * If the checkbox is ticked, no error will be logged and the data will be ignored. | ||
| Line 84: | Line 84: | ||
| {{ :gt3:loads:import:importfinishedwitherrors.png?nolink |}} | {{ :gt3:loads:import:importfinishedwitherrors.png?nolink |}} | ||
| - | If no errors or warnings have been logged the dialog will just advise you of the number of records imported successfully; no error log will have been created. Otherwise the dialog will also advise you how many warnings or errors were logged and prompt you to review the log file straight away, as shown in the sample image above. You should always review the log if it exists to ensure you haven't missed importing any loads - for example if a Commodity, Supplier or Storage could not be matched to the import data. You can also review and manage log files later as described in the [[bulkhandler#The Import Error Log]] section below. | + | If no errors or warnings have been logged the dialog will just advise you of the number of records imported successfully. A log file will still have been created; it will contain the basic details such as the name of the imported file and number of loads successfully imported, so that you can review it later to see what was done. Otherwise the dialog will also advise you how many warnings or errors were logged and prompt you to review the log file straight away, as shown in the sample image above. You should always review the log if it exists to ensure you haven't missed importing any loads - for example if a Commodity, Supplier or Storage could not be matched to the import data. You can also review and manage log files later as described in the [[bulkhandler#Managing Import Log Files]] section below. |
| If you find errors such as missing NGR numbers or cross-references, you can fix these issues in Grain Trader then re-import the same file, making sure that the [[bulkhandler#Import Options|import options]] you have selected and/or responses to prompts will avoid duplicating loads. | If you find errors such as missing NGR numbers or cross-references, you can fix these issues in Grain Trader then re-import the same file, making sure that the [[bulkhandler#Import Options|import options]] you have selected and/or responses to prompts will avoid duplicating loads. | ||
| Line 90: | Line 90: | ||
| You should also be sure to check any loads whose contract was changed, to make sure the correct pricing has been applied to the commodity imported. | You should also be sure to check any loads whose contract was changed, to make sure the correct pricing has been applied to the commodity imported. | ||
| - | If there were no errors ar warnings the Defined Format file that contained the loads just imported will be moved from its original location to a folder beneath the folder where your Grain Trader database resides, ie: | + | If there were no errors or warnings the Defined Format file that contained the loads just imported will be moved from its original location to a folder beneath the folder where your Grain Trader database resides, ie: |
| ''{your database folder}\Archived Import Files'' | ''{your database folder}\Archived Import Files'' | ||
| - | You can manage the archived Import files later as described in the [[bulkhandler#Managing Archived Import Files]] section below. | + | so as to make it more difficult to accidentally re-import the same file. If errors or warnings occurred the file will not be moved. You can manage the archived Import files later as described in the [[bulkhandler#Managing Archived Import Files]] section below. |
| All imported loads are created as saved loads, and you can review and change them before processing them as normal. | All imported loads are created as saved loads, and you can review and change them before processing them as normal. | ||
| - | ==== The Import Error Log ==== | + | ==== Managing Import Log Files ==== |
| - | As mentioned a number of times in the documentation above, information about various errors, warnings and actions taken during the import process is saved to a log file. These files are located in the same folder as the Grain Trader database into which the loads are being imported and are named according to the following format: {Database Name} Bulk Handler Import {yyyy-mm-dd}.log where {Database Name} is the name part of your database (.mdb) file, without the .mdb, and {yyyy-mm-dd} represents the date. It follows that one log file will be created for each combination of a database into which you import loads and the date on which you do the import. Multiple imports on one day into the same database just keep appending information to the same log file. Each import session is clearly defined and includes details such as the file being imported, the date and time and the selected import file format. | + | As mentioned a number of times in the documentation above, information about the Defined Format File being imported, together with various errors, warnings and actions taken during the import process is saved to a log file. These files are located in a folder beneath the folder where the Grain Trader database into which the loads are being imported resides, ie: |
| - | You should always review the error log if one is generated by your import, to ensure you haven't missed any loads (for example, due to NGR numbers, commodities or storages that can't be matched to your Grain Trader equivalents). Similarly, even if loads have been imported there might be missing Metric data, different Contract numbers and so on. | + | ''{your database folder}\Import Log Files'' |
| - | You can either review an error log if one exists on completion of the import process by clicking OK at the prompt, as described in [[bulk#Finishing the Import]] above, or from the Error Logs tab on the **Import Loads From Bulk Handler File** window. | + | and are named according to the following format: {Database Name} Defined Format Import {yyyy-mm-dd}.log where {Database Name} is the name part of your database (.mdb) file, without the .mdb, and {yyyy-mm-dd} represents the date. It follows that one log file will be created for each combination of a database into which you import loads and the date on which you do the import. Multiple imports on one day into the same database just keep appending information to the same log file. Each import session is clearly defined and includes details such as the file being imported, the date and time and the selected import file format. |
| - | {{ :gt3:loads:import:importloadsmanagelogs.png?nolink |}} | + | You should always review the log file if errors or warnings occurred during your import, to ensure you haven't missed any loads (for example, due to NGR numbers, commodities or storages that can't be matched to your Grain Trader equivalents). Similarly, even if loads have been imported there might be missing Metric data, different Contract numbers and so on. |
| - | The default folder being viewed is that in which the database that is currently open in Grain Trader resides, which is the same folder that log files relating to imports into this database will be created. However if you have multiple databases in different folders you can also use the browse (...) button to select a different folder if needed to manage the log files (if any) in that location. | + | You can either review the log file on completion of the import process by clicking OK at the prompt, as described in [[bulkhandler#Finishing the Import]] above, or from the Log Files tab on the **Import Loads From Defined Format File** window. |
| + | |||
| + | {{ :gt3:loads:import:importmanagelogs.png?nolink |}} | ||
| + | |||
| + | The default folder being viewed is that in which log files relating to imports into this database will be created. However if you have multiple databases in different folders you can also use the browse (...) button to select a different folder if needed to manage the log files (if any) in that location. | ||
| Select one or more rows in the grid and click either //View// to review the log file in your plain text editor (eg Notepad), or //Delete// to delete them. | Select one or more rows in the grid and click either //View// to review the log file in your plain text editor (eg Notepad), or //Delete// to delete them. | ||
| + | |||
| + | ==== Managing Archived Import Files ==== | ||
| + | As mentioned above, when you have imported a Defined Format file without errors or warnings it will be moved into the archive folder to make it easier to avoid re-importing the same file at a later date. This folder is located beneath that in which the Grain Trader database into which the loads are being imported resides, ie: | ||
| + | |||
| + | ''{your database folder}\Archived Import Files'' | ||
| + | |||
| + | You can manage these archived files from the Archived Import Files tab on the **Import Loads From Defined Format File** window. | ||
| + | |||
| + | {{ :gt3:loads:import:importmanagearchived.png?nolink |}} | ||
| + | |||
| + | The default folder being viewed is that into which the import files relating to imports into this database will be moved. However if you have multiple databases in different folders you can also use the browse (...) button to select a different folder if needed to manage the archived import files (if any) in that location. | ||
| + | |||
| + | Select one or more rows in the grid and click //Delete// to delete them. | ||