Reviewing the Packages CSV#
The Packages CSV creates groupings of one or more option references to associate with a Package. A name for the package is required, followed by an arbitrary number of Ids from the Options CSV file to associate with that package. Open the CSV file and review how this file is structured:
The first row is a header, and should not contain any options. What is entered into this row will not impact the resulting JSON output.
Column A should contain a unique ID for the Package.
Column B should contain a unique name for the Package.
Columns C and onward should contain an ID from the Options CSV. Any number of columns may be added.
Here are some examples of Packages from the Concept Car asset:
Id |
Name |
Carpaint |
Wheel_Colors |
Light_strip_color |
Int_leather |
Int_leather_dash |
Int_Trim_Color |
Stitch_Color |
Screen_Color |
0 |
Blanco |
17 |
89 |
32 |
45 |
55 |
66 |
35 |
80 |
1 |
BlueSilver |
18 |
88 |
34 |
47 |
57 |
63 |
35 |
80 |
2 |
Hornet |
19 |
82 |
33 |
48 |
58 |
69 |
37 |
76 |
Compare the completed CSV files to the Concept Car asset to better understand the correlation between the Concept Car variants and the Options and Packages CSVs. Options may be added or removed by modifying the CSV file.
The structure of this CSV varies, depending on workflows and requirements. This script may be customized and automated to populate the CSV programmatically or integrate custom solutions.