Question

A customer has an eCommerce site and Imports data into three data extensions daily; 'Orders', 'Order_Details' and 'Products'

the data extension contains the following information:
• Orders: OrderId, CustomerId, OrderNumber, OrderDate, OrderTotal, GrandTotal
• Order_Details: ProductId, OrderId, Qty, UnitPrice, ExtendedPrice, Discount
• Products: ProductId, SKU, Name, Description, Cost, Price

What two actions should be taken in Data Designer?
A. Create a one-to-one relationship between Orders and order_Details
B. Create a one-to-one relationship between the contact record and Order_Details
C. Create a one-to-one relationship between Order_Details and Products
D. Create a one-to-many relationship between Orders and Order_Details

Answer 1

The two actions that should be taken in Data Designer are creating a one-to-many relationship between 'Orders' and 'Order_Details', and between 'Order_Details' and 'Products' to accurately reflect the relationships of an order having multiple items and products being part of many order details.

Step-by-step explanation:

In Data Designer, to address the task of establishing relationships between the eCommerce site data extensions 'Orders', 'Order_Details', and 'Products', you would need to take specific actions.

Firstly, the right approach would be to create a one-to-many relationship between 'Orders' and 'Order_Details' (D). This is because a single order can potentially have multiple items; hence multiple order details entries. Therefore, each OrderId in 'Orders' can be linked to many entries in 'Order_Details'.

Secondly, create a one-to-many relationship between 'Order_Details' and 'Products' (C). Every product can appear in multiple order details but each line in 'Order_Details' refers to one product. So, a one-to-many relationship from 'Products' to 'Order_Details' accurately represents this association where one ProductId in 'Products' corresponds to several entries in 'Order_Details'.