For the global data workflow (Exercise #6), we combined the…

For the global data workflow (Exercise #6), we combined the “automation global data” as the left input and “global data entity list” as the right input using the Alteryx join tool (using entity ID and entity number). Which of the following are true? Select all that apply. 

In ICE #9 “join2” we left join our “join1” table and the cus…

In ICE #9 “join2” we left join our “join1” table and the customer invoices table using the InvoiceID variable. If instead we use a inner join, we find that 1 observation is excluded from the join1 table. This means that there must be a sales order from join1 where InvoiceID is null. 

In ICE #9 “join4” we combine the join3 table and the custome…

In ICE #9 “join4” we combine the join3 table and the customer master table using the variable CustID and in inner join. This results in a table with 1,168 observations. If we instead link this tables using a left join and the TerritoryID variable, we get a table with 18,937 observations. In this joined table, there are observations where the customerID from the join3 table does not equal the customerID from the customer master table. 

In the KPMG revenue case (ICE #9), we first filtered observa…

In the KPMG revenue case (ICE #9), we first filtered observations for shipments made in 2017 and the “aggregated” sales transactions by TerritoryID, Shipping Month, and whether the sale is related to the new product (#7123).  We then outputted this data as a csv file. The grouped data has 5*12*2 = 120 observations.