Appearance
AttributeFile Schema
File: AttributeFile.json
Purpose: Defines attribute metadata for all entity types in the inRiver export
Format: JSON array of entity type definitions
Structure
json
[
{
"EntityTypeId": "string",
"Attributes": [
{
"AttributeId": "string",
"Name": {
"stringMap": { "en": "Display Name", "es": "...", "fr-CA": "..." }
},
"SortOrder": number,
"DataType": "string",
"AvailableFieldsets": [
{ "Id": "string", "Name": { "stringMap": { "en": "..." } } }
],
"IsMultiValue": boolean,
"AllowedValues": { "key": "Display Name", ... }
}
]
}
]IsMultiValue and AllowedValues are only present on CVL-type attributes.
Entity Types
The AttributeFile contains attribute definitions for 5 entity types:
| Entity Type | Attributes | CVL (AllowedValues) | Multi-Value |
|---|---|---|---|
| Channel | 3 | 1 | 0 |
| ChannelNode | 19 | 1 | 0 |
| Product | 21 | 10 | 1 |
| Item | 1,022 | 195 | 24 |
| Resource | 11 | 2 | 0 |
Data Types
String— Plain textBoolean— True/false flagsInteger— Whole numbersDouble— Decimal valuesLocaleString— Multi-language text (e.g.,{"en": "...", "es": "...", "fr-CA": "..."})CVLString— Controlled Value List (hasAllowedValuesmapping)File— File reference
CVL Attributes (AllowedValues)
Attributes with DataType: "CVLString" include an AllowedValues object mapping internal keys to display names. These serve as the lookup for resolving coded values in entity exports.
json
{
"AttributeId": "ItemANSIStandards",
"Name": {
"stringMap": {
"en": "ANSI Standards",
"fr-CA": "Normes ANSI",
"es": "Estándares ANSI"
}
},
"SortOrder": 625,
"DataType": "CVLString",
"AvailableFieldsets": [
{ "Id": "ItemLaddersandAccessories", "Name": { "stringMap": { "en": "Ladders and Accessories" } } }
],
"IsMultiValue": true,
"AllowedValues": {
"A14.52007": "A14.5 (2007)",
"OSHA": "OSHA",
"Type1": "Type 1"
}
}When IsMultiValue: true, the entity export value is a multi-select CVL (keys/values arrays). When false, it's a single-select CVL (key/value object).
Multi-Value CVL Examples (Item)
ItemANSIStandards(7 values)- A14.5 (2007), OSHA, A14.2-2017 6.2.4, A14.2 (2007), ...3 more
ItemApprovals(35 values)- CUL Listed, UL Listed, UL Recognized, ETL Listed, ...31 more
ItemBasisOfRotationView(4 values)- Lead End, Shaft End, Drive End, Power End
ItemBeltSection(7 values)- 4L or A, 5L or B; 4L or A; 3L; 5L or B, ...3 more
ItemCondenserLocation(3 values)- Outdoor, Indoor, Indoor or Outdoor
Single-Value CVL Examples (Item)
ItemAHRIUsage(5 values)- Indoor AHU, Outdoor, Packaged, Indoor Coil, ...1 more
ItemAirFlowDirection(11 values)- Horizontal, Multi-Position, Vertical, Convertible, ...7 more
ItemBasicItemInformationBypassRequestStatus(3 values)- Bypass Requested, Bypass Granted, Bypass Denied
Key Attributes by Entity
Item (1,022 attributes)
High-volume entity with extensive attribute set including:
- Product identification (ItemManufacturerItemNo, ItemUPCCode, ItemEANCode)
- Dimensions and weight (Imperial measurements)
- Inventory data (ItemOnHandQtyInAllWatscoSubs)
- Business unit flags (per-BU e-commerce activation)
- Supplier information
- Rebate and pricing data
- 195 CVL attributes with full key→display name mappings
ChannelNode (19 attributes)
Navigation and categorization attributes:
- ChannelNodeName (LocaleString)
- ChannelNodeActiveInEcommerce (Boolean)
- Per-business-unit activation flags (CECA, CECPD, CEFL, etc.)
- SEO metadata (MetaTitle, MetaDescription, MetaKeywords)
Product (21 attributes)
Product-level attributes linking to items and resources:
- ProductId, ProductMainSupplier, ProductShortDescription
- Taxonomy references (ProductWatscoTaxonomy1–4)
- 10 CVL attributes including manufacturer
Resource (11 attributes)
Media asset metadata:
| Attribute | DataType | Notes |
|---|---|---|
| ResourceTitle | String | Display title |
| ResourceResourceType | CVLString | 60 values — maps codes to Image_Type names |
| ResourceFileId | File | Internal file reference |
| ResourceFilename | String | Original filename |
| ResourceMimeType | String | e.g., "jpeg", "pdf" |
| ResourceContentHash | String | SHA-256 hash |
| ResourcePublishedStatus | CVLString | 3 values: NotPublished, PublishedToBlobStorage, DoNotPublish |
| ResourceSourceURL | String | Origin URL |
| ResourceName | String | Resource name |
| ResourceAcceptedFile | Boolean | Acceptance flag |
| ResourceImportProcessed | Boolean | Import processing flag |
ResourceResourceType CVL (60 values)
This CVL maps abbreviated codes to the human-readable Image_Type names used in the legacy Heiler PIM export:
| Code | Display Name |
|---|---|
normal | Standard image |
ai1–ai4 | Alt Image 1–4 |
ai | Application Image |
ccs | Catalog Cut Sheets |
cl, cl2, cl3 | Consumer Literature 1–3 |
cc1–cc3 | Consumer Catalog 1–3 |
ss | Specification Sheet |
ss1–ss3 | Submittal Sheet 1–3 |
subs | Submittal Sheet |
ii, ii1–ii3 | Installation Instructions 1–3 |
uci | Use & Care Instructions |
sm, sm1–sm3 | Service Manual 1–3 |
msdss, msdss1, msdss2 | MSDS Sheet, Alt1, Alt2 |
sds1–sds4 | Safety Data Sheet 1–4 |
ahri | AHRI Certification |
logo | Logo |
pl | Parts List |
explodedview | Parts Exploded View |
ed | Engineered Document |
fwc | Florida Wind Code |
ibw | Illustration (B&W) |
ic | Illustration (Color) |
tax | Tax Certificate |
war | Warranty Document |
wd | Wiring Diagrams |
vid1–vid4 | Video 1–4 |
vp | Video Production |
data_sheet | Data sheet |
hcl, hdata_sheet, hii, hpl, hss, hsubs | Historical variants |
MainImage | Main Image |
Silo | Silo |
AssemblyInstructions | Assembly Instructions |
Notable absence: Spin/360 images (Row1–3, 24–36 frames) from the Heiler export are not represented in this CVL.
Localization Coverage
The Name field provides localized display names via stringMap:
| Entity Type | EN | ES | FR-CA |
|---|---|---|---|
| Channel | 3 (100%) | 0 | 0 |
| ChannelNode | 19 (100%) | 0 | 0 |
| Product | 21 (100%) | 0 | 0 |
| Item | 1,022 (100%) | 703 (69%) | 605 (59%) |
| Resource | 11 (100%) | 0 | 0 |
Compared to Heiler PIM (17,223 attrs with 98% ES, 82% FR coverage), the inRiver Item translations are still growing. Channel/Product/Resource attributes currently have English only.
Related Files
- See product.md for Product entity structure
- See channel-node.md for ChannelNode entity structure
- See ../technical-spec for CVL field specifications