This article covers importing Outfits and their components by CSV file into Creative Force. For general information on Outfits, their components, & more, please see the main Outfit Overview article.
Import Outfits by File
Besides manual creation via the Outfit menu, you can also create Outfits by importing data from a sheet.
⚠️ Important: Pre-defined Outfits can only be brought into the system at the time of import; you cannot create Outfits via 'Add Product Requests' in the Job screen once they have already been added to the system.
When preparing to import Outfit Data via a file, you must have the minimum required information in your file, which includes: Primary Product, Secondary Products, and Outfit Code.
Data Mapping
Then, make sure to map those columns from your file to the relevant Data Property in Creative Force.
Data | Property to Map |
Primary Product | Product Code (Main Product) |
Secondary Products | Product Code (Outfit Product) |
Outfit Code | Outfit Code |
Outfit Product Role | Product Role (Outfit Product) |
Outfit Product Role
An additional Outfit Product role can be mapped with the data on your sheet. The available values for this property are:
Mandatory: means that it is not allowed to be removed from the outfit.
Replaceable: means that it is allowed to be removed from the outfit, so you can edit the outfit at a later stage.
Example Data
Here is an example of how your sheet could look:
Notes
The products that are mapped to the Outfit Product Property that have not existed in the system before will be imported as styling items, which means these items will not have any production data. Learn more.
If an Outfit Product Role is not mapped during import, it will default to being Mandatory and can not be removed from the outfit after import.