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 and save copies of your important jobs

Key Resources

• Search for articles on specific errors if 
  • Receiving specific errors when launching Visual Integrator
  • Creating a Visual Integrator import job
  • Testing or running a Visual Integrator import job
• Importing into Business Framework data entry files
• Importing into legacy data entry files select the modules depending on your Sage 100 version
• For Payroll imports, refer to How to import into Legacy Payroll Data Entry
• For other imports into specific tables, search the knowledgebase for articles specific to you're importing task

General pointers for Business Framework data entry import

• Receiving errors importing from the Excel source file?
  • Save the Excel file as .CSV and select this file as your source
     NOTE: It's possible to get undesired results using an Excel source file 
• Have an existing file with Excel source selected?
  
  • Create a new import job into the same table 
  • Choose the copy feature to copy the original import job 
  • Specify the .CSV source file 
• It's common to get undesired import results when assigning ALL header fields (ASSN operation)
  • VI looks for the header field value to change
  • Have a least one header field with a value from the REPL (replace) operation
• Manually test entering data into the data entry task (outside VI)
  • Only include fields on your import job that you must manually enter
  • Also fields that automatically get populated but you need to overwrite
  • Don't include fields that auto-populate if you aren't manually overwriting their values
     NOTE: Like Work Center and Activity Code for Product Management or Pay Rate for Payroll, etc.) 
  • Manually entering sample data into the related data entry task also confirms if you're missing any fields
• Use uppercase for Yes/No fields if the value will appear in uppercase. Avoid lowercase in that case
• A best practice is to manually key in a sample data entry. Find the resulting data in the data file before beginning the import

Important information

• We don't recommend File Assigns. It's unnecessary for most fields and will result in odd or blank values
• Keep the number of fields on the import to a minimum
• Manually create the process to what fields you need. Refer to How to import into Business Framework data entry files
• Verify you've mapped key fields correctly in the table and the headers in your source file
• Read values into Temp fields, assign fields, or use calculations to get correct results

How to determine the required fields for Legacy import jobs
How to import into Legacy Payroll Data Entry using the Visual Integrator module