Applying Option set selection to many rows based on an aggregated row

[PowerAppsRule]

Hello

Pretend I have a aggregated row that represents an employees expense like this.

Person         |  Exp Title,      | Department   | Expense

John Smith  | Home Office | Technology   | $300

This $300 dollar expense is a aggregation of 3 lines each for $100.

Store               | Department   | Expense

Best Buy          | Technology   | $100

Staples            | Technology   | $100

Office Depot   | Technology   | $100

Problem: I want a manager to be able to approve the expense by looking at the $300 summary level and NOT at the $100 detail level. In a model driven app, how do I take the managers feedback provided on the $300 row and spread it across the 3 detail lines?

*****EDIT*****

Thank you for the suggestions. I left out a critical element in my above prompt.

A critical piece is the the ability to edit the detail level data approvals. Therefore the suggested solutions will not work the data needs to be in both tables, and not just a lookup from one table to another. For example, using the above data, the manager may approve the $300 dollar expense but needs the ability to look at the detail lines (usually in the 10's of thousands of rows) and change some of them. Say the manager approves of all lines in that group except Best Buy. With a reference to another table the data doesn't live in the detail table for detail level edits.  

[poweractivate]

@PowerAppsRule 

If the aggregate row AND the separate rows were two different Tables (formerly Entities) in Dataverse (formerly Common Data Service) then:
You could consider having a One to Many Relationship from the One side being the aggregate and the Many side being the line items. Next, take the three line items, and in the Lookup Field for all three of them, indicate that aggregate record. Finally, attach the feedback only to the One side (the aggregate record). The associated line items can be accessed from the aggregate record directly due to the one to many relationship, removing the need to add the feedback to the individual line items.

Other than the above, we are unsure about the nature of the aggregate and the line items. For the purposes of this question we just presumed they were different Tables (formerly Entities) in Dataverse (formerly Common Data Service). For your purposes, you may have to give more details about the underlying data set as we were actually not sure about how this aspect is set up in your case.

[v-siky-msft]

Hi @PowerAppsRule ,

Just as @poweractivate  said, if you have established the 1:N relationship between two tables, to view the related feedback in details table view from the aggregated row, please try add the feedback field in Related Tab into the View. For instance:

In addition, in Form, use Quick View Component to view the form data of related tables(aggregated row)

Hope this helps.

Sik