CAUTION: • Use the Role Security settings to restrict users from accessing Import Job maintenance to prevent accidental deletion. Have users run the Import Jobs from the Job Select menu. • Use the Job Export function in Visual Integrator to export (save) copies of your important VI jobs.

Key Resources

• If you are receiving specific errors when launching Visual Integrator, when creating a Visual Integrator import job, or when testing or running a Visual Integrator import job, search for articles on those specific errors.
• If you are importing into Business Framework data entry files, use the article How to import into Business Framework data entry files for Sage 100 (especially for modules in Sage 100 2018 and later).
• If you are importing into Legacy data entry files, see How to determine required fields for Legacy import jobs (select modules depending on Sage 100 version).
• For Payroll imports, see How to import into Legacy Payroll Data Entry using the Visual Integrator module" for more details
• For other imports into specific tables and tasks, search the knowledgebase for articles specific to your own importing tasks.

General pointers for Business Framework data entry import

• If you're receiving errors importing from the Excel source file, try saving the Excel file as .CSV (Comma Deliminated Value *.csv) and select this file as your source - it is possible to get undesired results using an Excel source file. If you have an existing import job with Excel source selected, create a new import job into the same table and choose the Copy feature to copy the original import job but this time specify the .CSV source file (File Type: Deliminated, Delimeter: ,)
• It is common to get undesired import results when assigning ALL header fields (ASSN operation), as VI looks for header field values to change. Therefore, you should have at least 1 header field with a value from the REPL (replace) operation.
• Test manually entering data into the data entry task (outside Visual Integrator) and ONLY include fields on your import job that must be manually entered and also fields that automatically get populated but you need to overwrite. You generally don't need to include fields that auto-populate if you aren't manually overwriting their values (like Work Center and Activity Code for Production Management or Pay Rate for Payroll, etc.). As these fields auto-populate, only specify those fields in the import job if you need to change the defaults.
  • Manually entering sample data into the related data entry task also confirms if you are missing any necessary fields in your import job
• If you are assigning a Yes/No field, do not use lowercase if the value is intended to be Upper Case as this may not be automatically converted.
• A best practice is to manually key in a sample data entry and find the resulting data in the data file, before beginning the import. Data files may have similar fields and this approach can prevent importing to the wrong field.

 NOTE: 

• The File Assigns is not recommended as it's unnecessary for most fields and may result in "odd" or blank values. Keep the number of fields on the import to a minimum. You can manually create the process to see what minimal fields are needed. See How to import into Business Framework data entry files for Sage 100.
• Verify that the key fields in the table you are importing into and the headers in your source file are correctly mapped.
• You may need to read values into Temp fields, assign fields, or even use Calculations to get the correct results. Some values may require adding additional fields on your import to get the desired totals.