Importing User Defined Fields

Is importing UDF information any different than other system fields related to the same record?

No, however, the ability to add, delete, or modify UDFs at any time may complicate new or existing import processes.

How do I include a UDF in my DEF file?

To import UDF data, the UDF must be added to the definition file.

Add the FieldID to the appropriate section of your DEF file and indicate the location of the data in the text file like you would any other field you were importing. Note that the context section of the definition file contains the [Context Type]_[Field Name] (referred to as the FieldID) of each field that will be imported into the system.

How do I identify the FieldID for a newly created UDF?

To determine the FieldID, with Administrative user rights, print a User Defined Field List report (Reports>Lists>User Defined Fields) and include "Context ID" in the report body. The format should appear in the Definition file exactly as it shows in the report including punctuation. For example: To import "Award Date" for Grants, the Context ID should read: "Segment Code:2:AwardDate".

Are there any special rules for importing records containing UDFs?

No, UDFs follow the same rules as other fields with the same data type. For example, a Date UDF will have the same DEF file rules (such as masking and default values) as an Effective Date field. Note that UDFs cannot be independently imported.

How many decimal places can a UDF have with a field type of number?

A UDF with the field type of number can have up to five decimal places.

When do decimal indicators work with UDFs?

Decimal indicators only work when a UDF has the field type of currency.

What happens if a UDF with a field type of currency or number are not given a value in the data file?

These field types always default to 0.00 value when no value exists in the data file. Note that no blanks are allowed for these field types.