Firms Import Notes
When you import firm information, the import process adds a new firm record in DPS for each firm in the .CSV file that does not already exist in DPS.
You can import any standard or custom data that you enter on any tabs in the Firms hub, with the general exception of fields in grids. However, you can import multiple addresses for a given firm.
Import Availability
This import is available to any enterprise that uses DPS, regardless of the modules that are activated.
Required Fields
To create or update a firm record, you must import the firm name in an import field that is mapped to the Name field in DPS.
If the import process sets Available for Use in Processing to Y or Yes for a firm, you must also map values to the Vendor Number and Vendor Type fields.
If DPS is set up for multiple companies, also include a value for a field that is mapped to the DPS Company field. That value can be either the exact company name or company code for an existing company in DPS for which you are creating the firm. (You can run the import multiple times for the same firm to add vendor information for each company.)
Record Validation
- Same firm name
- Same firm number
- Same vendor number
If it finds no match, the import process creates a new firm. If it finds a match and you selected the Update duplicate records option, it updates the existing record based on the data in the import file record.
Parent Firm
To establish a parent and subsidiary relationships between two firms, map either the firm name or firm number of the parent firm to the DPS Parent Firm field when you import its subsidiary firms. The parent firm must already exist in DPS when you import its subsidiaries.
Firm Addresses
In DPS, you can have multiple addresses for a single firm. When you import firms, you can assign multiple addresses by including one import record for the firm for each address.
For example, to import a firm with a primary address and a different address for billing and payments, include the primary address in the first import record. Map the street address, city, state, and postal code values in the import file to the corresponding DPS address fields, and map an import field containing Y or Yes to the DPS Primary field.
In a second import record for the same firm, include the address data for billing and payments, and map import fields containing Y or Yes to the DPS Billing field and Payment field. This second record can be in the same import file as the first firm record, or it can be in a separate file that you import later. In either case, however, select the Update Duplicate Records option in the Import Firms from CSV dialog box when you run the import process.
Internal Primary Key
If you are integrating Maconomy with DPS and you need to import firms into DPS, you can import the internal primary key for the firm records if that is necessary to ensure that the integration works correctly. To do so, make sure your import file contains the correct primary keys, and map that field in your import file to the Internal Primary Key field in the Import Firms from CSV dialog box.
Warning: The primary key field is an internal database field that is not visible in the Firms hub. You should only import into the primary key field if you understand the database structure and fully understand that importing into this field may impact the integrity of your database. You should back up your database before importing into this field.
The Internal Primary Key import field was added to support users with the specific data requirement described above. If that situation does not apply to you, do not import data into this field. To import the firm numbers or vendor numbers that are visible in the Firms hub, map them instead to the Firm Number field or Vendor Number field.