Firms Import Fields
When you import firm information, the import process adds a new firm record in DPS for each firm in the .CSV file who does not already exist in DPS.
Imported Firm Information
You can import any standard or custom data that you enter on any tabs in the Firms area, with the exception of fields in grids.
Note that if the proper data match between fields is not allowed, the record will not be imported from the .CSV file and an error will be recorded to alert you of the issue.
The following table provides notes about some of the imported fields. (This is not a complete list of the fields you can import).
Field | Notes |
---|---|
Firm Name | This field is required. You must map this field in order to import a firm. |
Firm Number |
The import process checks for an existing firm number. Duplicates are identified by matching on one of the following:
If the number matches, the record in the .CSV file is considered a duplicate. If no match is found, the firm number is displayed in the New Firm Records dialog box so you can indicate if you want a firm record created for it in DPS. You must also consider
DPSautonumbering settings when importing a firm:
|
Vendor Number |
The import process checks for a vendor number. The Vendor Number must match the designated key format for this field and cannot apply autonumbering. The import process checks for an existing record. Duplicates are identified by matching on one of the following:
If the name or number match, the record in the .CSV file is considered a duplicate. If no match is found, the firm number is displayed in the New Firm Records dialog box so you can indicate if you want a firm record created for it in DPS. |
Type | There are several different checkboxes that may be in use to indicate the type of firm. For example, client, vendor, government agency, etc. |
Market | This field displays the firm's market. |
Owner |
The import process checks for employee names as follows:
If there are multiple matches, the record is not imported and you will be notified of the issue in the error log. The import continues through the rest of the records in your source file. |
Status | Firm status defaults to Active if not mapped. |
Recommend | This field is selected if the firm is recommended for future work. |
Description | This memo field displays a description of the firm. |
Relationship | This list field displays the firm's relationship with your firm. |
Prior Work | This checkbox indicates if the firm has previously done work with your firm. |
Speciality | This memo field lists the firm's specialty. |
Annual Revenue | This numeric field displays the amount of the firm's annual revenue. |
Parent Firm | This field must match the number of levels established in Settings. Firm hierarchies created must adhere to the maximum number of levels established in Settings. |
Socioeconomic checkboxes | These checkboxes represent any business development programs for small and minority-owned businesses for which the firm is eligible. |
Organization | If your firm uses organizations, you have the option to assign vendor type firms to organizations. Each value in the organization field in your .CSV file must match an existing organization name exactly. If the organization for an opportunity you are importing does not match an existing organization, the opportunity is imported but the Organization field is left blank. |
Drop-down fields | A field in the .CSV file that is mapped to a field in DPS that has a drop-down list of valid values must contain a value that exactly matches one of those valid values. If the value in the import file does not match a valid value for the field in DPS, the record will not be imported from the .CSV file and an error will be recorded to alert you of the issue. The import continues through the rest of the records in your source file. |
Custom fields (general) | The format of data to be imported into a custom field must be compatible with the type of custom field. For example, you can only import numeric data into a number field. If the format is not correct, the contact is not imported and you will be notified of the issue in the error log. The import continues through the rest of the records in your source file. |
Custom date field | Dates to be imported into a custom date field should be in the date format specified in the My Preferences dialog box of the person who runs the import process. For example, if your date preferences are set to include the month before the day, then the dates in the import source file should also have the month before the day. |
Custom drop-down field | Values to be imported into a custom drop-down field must match one of the standard values for that field. If a value does not match a standard value, the record is not imported and you will be notified of the issue in the error log. The import continues through the rest of the records in your source file.
However, you can choose to not limit any drop-down to the list of values, which means users can enter a value that is not in a list. If that option is selected, then the record is imported with that value but the value is not added to the list of values for the field properties. |
Custom lookup field | Values to be imported into a custom lookup field must match a name exactly. For employee or contact lookups, they must match either a first name + last name + firm or preferred name + last name + firm. For a firm lookup, they must match either a firm name or alias. If there is no match, the record is not imported and you will be notified of the issue in the error log. The import continues through the rest of the records in your source file. |
Custom check boxes | Custom check boxes are selected (checked) if the imported value is either Yes or Y and are not selected if the value is No or N. |