Import Setup Data screen
Use the Import Setup Data screen to import setup data from Microsoft Excel (XLSX) or TSV files.
- Contact
- Customer
- Vendor
Because of dependencies that exist among different types of data, it is recommended that you run each import type in the order listed above. For example, you must import the chart of accounts before you can import contacts; you must import contacts before you can import customers; and so on.
To import from Excel, use the Viewpoint Estimating import templates. Most import templates contain multiple worksheets, allowing you to import primary records from one worksheet and detail records from the others.
If you have exported data from a Viewpoint legacy product, the import data may be in one or more TSV files. When you import from a TSV file, Viewpoint Estimating converts the file to Excel before retrieving and validating the data. If errors are found, you can make corrections to the data directly within the Excel file and run the process again.
Viewpoint Estimating uses specific key fields for each import type to uniquely identify records and prevent duplicates. For example, when retrieving and validating customer data in the import file, the application uses the Customer field value to uniquely identify each customer in the file and prevent duplicate customer records in the system.
Viewpoint Estimating also uses the key fields to link detail records in the import file to primary records. If a detail record does not match a primary record based on key field values, the detail record is marked as “orphaned” during the validation process. You can stop the import and make corrections to the orphaned records directly within the import file. If you continue with the import without correcting orphaned records in the import file, the orphaned records will not be imported. You will have to manually enter the orphaned records into the system.
Excel needs VBA macro language support to complete the actionYou may need to minimize the application to see this message. To work around this issue, install the Visual Basic for Applications component.