To import a new job in Creative Force browse to 'Jobs' in the top bar menu and hit 'import job'.
Select a job file on your computer and drag it in the area as indicated in the job import wizard. Alternatively, you can click 'browse your computer' to select a file directly.
Once the job file is dropped or selected, hit 'next' to enter the job information.
Note: Today we support the import of jobs with as following file-types: .csv, .xls, .xlsx, .json
Enter the job information in the following screen. Make sure to select the correct client and add a job name as the minimum required information. Hit 'next' to move on to the data mapping of the job file.
Note: You can add as many custom job information as you like. Add additional job properties in your studio settings - https://help.creativeforce.io/en/articles/3529716-properties.
After entering the job information, the data from the job file needs to be mapped to be correctly imported to Creative Force. You'll find the columns from the job file on the left-hand side and the Creative Force data properties on the right-hand side of the following screen.
Map the correct data properties for each of the columns in the job data.
Mandatory to map:
- Product code (Main product) - The unique identifier for the product.
Recommended to map:
- Sample barcode (Main product) - The unique identifier for the product sample
- Category (Main product) - The unique identifier for the Style Guide to be mapped on job import
- All columns that are required to perform the automatic naming.
Hit 'import' to finish the job import.
Note: The mapping will be saved on the client level after the first import. It can be adjusted at any time.
Once the job is successfully imported you'll be directed to the job details. In the job details we are a running a import analytics to surface potential issues:
The import analytic is an additional check to the Job import flow to verify if the imported Job contains:
- products, that have already been produced in previous jobs
- products, that failed to be mapped to a Style Guide
- products, that miss property data which is required for the final asset naming
- products/outfits that are redundant in the import file
If one or more of the above-mentioned conditions are correct, we show a dedicated warning to support resolving the cases.
Note: Dismissing the warning will not solve the mentioned issue. The user should resolve all mentioned issues first, before dismissing the warning.