This is specific to an example from a third party solution called Anthology Reach. The goal is to display Applications(Entity) with Decisions(Entity) based on a specific Academic Period(Entity). They wanted to include Fields from both the Contact and Decision Entity in their column headers. There does not seem to be a way to drill down across relationships to add all of the below desired columns into one View regardless of whether the Base Entity is selected as Contact, Application, or Decision. Columns desired: External Identifier (Contact), Application Name(Application), Application Submitted (Application) , Decision Status (Decision), Review Status (Application). The desired output can be done in a Report. The columns available for selection in a View do not allow Decision related columns to be added to the header due to the M:1 Relationship between Decision and Application. The customer is aware this would create duplicate rows to be returned per Contact when creating a View with Application as the Base Entity due to multiple Decisions existing for each Application. They want the data to be returned like this.