Is there an example/template of Job Cost's Import Estimate?
Description

 

Cause

Resolution

General Information

  • Each import record has fields that are required
    Example: The Job header record needs an asterisk followed by the job ID (*,07-123,)
  • For check box columns, use a 1 for a value of checked and use 0 or a blank value for not checked
  • Include quotes around text fields if they include characters that can cause a field break, such as a comma
  • You can use the Windows Notepad application to open the attached jce file

The attached template includes the Job record, Cost Code records, and Category records. The first field in each row defines the record type.

    • * = Job Record (Required)
    • P = Cost Code record (Optional)
      The P records are only required if adding new cost codes to the job or when tracking Production Units
    • C = Category Record (Required)

Attachment: FISHLODG.JCE

Attachment: FISHLODG.xlsx

For more information about the import estimate record layouts, see Job Cost, Help, Help Topics, Index tab, Importing, estimate file.

Information about Extras

If your import contains extras that you didn't set up yet, include the extra record before the cost code/category record in the file. Otherwise, the import ignores information in the extra record (like address or city) and Job Cost creates the extra without a description.

To import category records for multiple extras, include the extra record before the category record. If the values are for different jobs, then include the job record, then the extra record, then the category record.

Information about Dates

The date format in the import file must match the date format your system uses.

Example: In the United States, 05/10/25 represents May 10, 2025, but in Canada 05/10/25 represents October 5, 2025.

Information about Custom Fields

If your import file includes custom fields from the job setup, you need to include Row ID and Row Version as fields on the format. The system populates the field automatically, but the placeholders must be in the text file.

This includes custom fields on the Job, Extra, Cost Code, or Category records.

Import Rejections

When you import files into Job Cost, you may get rejection messages. Multiple rejections can be misleading because one rejection can cause other rejections. Check Job Cost Help or the Sage Knowledgebase for more information on these errors.

 

Steps to duplicate
Related Solutions