inRiver Documentation

Appearance

Assumptions ​

This document captures assumptions made about the inRiver export format based on available sample data.

Entity Relationships ​

Channel Entity ​

Assumption: A Channel entity type exists as a parent/container for ChannelNode entities.

Evidence:

  • AttributeFile defines a "Channel" entity type with attributes (ChannelName, ChannelPublished)
  • No sample Channel files provided in e-commerce export

Impact: ERD includes Channel as the root of the category hierarchy, but actual relationship structure is inferred.

Business Unit Handling ​

E-commerce Exports are Business-Unit-Specific ​

Assumption: E-commerce exports are generated per business unit, eliminating the need for BusinessUnitOverride entities.

Evidence:

  • BI export samples include BusinessUnitOverrides array with per-BU data (BAK, CEFL, ECM, GEM)
  • E-commerce export samples do not include BusinessUnitOverride entities
  • Item attributes include per-BU flags (e.g., ChannelNodeActiveinEcommerceCEFL)

Rationale: Each business unit receives a separate export containing only their relevant data, rather than a single export with overrides for all business units.

Impact:

  • E-commerce integrations process single-BU exports
  • No need to filter or apply BusinessUnitOverride logic
  • Simpler data model for e-commerce consumers

Cardinality ​

Product to Item Relationship ​

Assumption: One Product can contain multiple Items (1:many)

Evidence:

  • Product entity has Items array property
  • Sample shows Product 19456 with 1 Item, but structure supports multiple

ChannelNode to Product Relationship ​

Assumption: Many-to-many relationship between ChannelNode and Product

Evidence:

  • Product 19456 has InboundLinks from 2 different ChannelNodes (50714, 50715)
  • Products can appear in multiple categories
  • ChannelNodes can contain multiple products

Entity to Resource Relationship ​

Assumption: Both Product and Item entities can have multiple Resources (1:many for each)

Evidence:

  • Product 19456 has 3 Product-level Resources
  • Item 3424 has 3 Item-level Resources
  • Resources are nested within their parent entity

Last Updated: February 20, 2026