| | The following file formats support importing of custom fields:
Since the names given to custom fields are unique to each company, they are not shown in the documented file format. Instead, you can refer to these fields using their ordinal position. For example, the Commitment record of the JCCommitment file format shows that there are 145 fields. The 146th field would be the first custom field (if any) and the 147th field would be the second custom field and so forth. To refer to a custom field using its number, use the column number for the column name (e.g., "16").
Example:
=TSIMPORT("JCCommitment","","Commitment",A1,"Commitment",A1,"CommitmentType",1,"Description",B1,"APVendor",C1,"146",D1)
The above example tells Office Connector Import to place the value from cell D1 in the first custom field ("146").
The following table provides the number of the first custom field for the various records that support importing of custom fields:
JCCommitment
| Record Type | Column# of First Custom Field |
|---|
| Commitment | 146 |
| CommitmentItem | 19 |
| CommitmentCO | 20 | JCEstimate
| Record Type | Column# of First Custom Field |
|---|
| Job | 16 |
| Extra | 9 |
| CostCode | 16 |
| Category | 16 |
| Note - | It is not necessary to include all of the field names leading up to the first custom field. Only write data to the fields that you are actually intending to populate. Fields may be included in the TSImport function in any order. Office Connector Import will make sure they are written to the import file in the correct position. |
|---|
|