Validating on Dataport

We have a customer that imports a lot of information via dataports that we have set up. This information is in the form of flat text files from other systems. The problem we have is that in order to check the information coming in we have the validate option turned on. But the systems that export these files do not seem to do as much validation as they occasionally export incorrect info e.g invalid item numbers. As one of these is a stocktake import into the Phys Inventory Journal that can take a few mins to run if you get an invalid item number after 4 minutes Navision errors and you have to start again. Which can be frustrating. Can anybody think of a way of doing this better say a dataport that can write errors to a file and continue so that you dont have to try the dataport time and again just to get one error at a time? Simon

Simon You can of course write to a text file as the dataport is running, or dump the data from the current record into another table with the same definition. This brings about coding on the dataport, and the use of the AutoSave/Validate etc options. I find that in 99% of cases its more effective and reliable to turn those options off, copy the dataport fields into a new record via code, complete and validation and checks in code and then insert the records with code. This produces an initial increase in work but allows for changes and flexibility later, especially when you beign to think about dumping records with errors to file or other tables etc… Craig Bradney Project Manager - Technical Navision Solutions & Services Deloitte Growth Solutions Deloitte Touche Tohmatsu P:+61-2-9322-7796 F:+61-2-9322-7502 E:craig_bradney@deloitte.com.au