Introduction

The goal is to setup a database with relations between nodes. That can be a product database or a location database. The critical point is: The relation should hold data as well.

SalesChannel C --- (Price K) --- Product A --- (Price X) --- Supplier V
SalesChannel D --- (Price L) --- Product A --- (Price Y) --- Supplier W

From this data, a view/table should be generated which displays all information correct without duplicates.

Notes:

Commerce couldn't hold data in the relation, even though product variations seem to aim at this scenario.
Entitiy Reference (as well as other reference modules) seem unable to store data in a reference as well.
Views and Relation alone are insufficient since a view of all products will generate duplicates if relations with their data and endpoints are to be displayed as well.

Assumptions:

For this tutorial experience with Views and Relation is required.

Modules needed

Views
Relation
EVA
Views Field View

Instruction

After enabling the required modules, the three content types can be created which is pretty straight forward.