Thanks for elaborating!
So if you want to map attribute of TotalPrice from both the entities of POSPurchases and OnlinePurchases, the requirement is that POSPurchases and OnlinePurchases must be linked by the same relationship path to Customer Profile entity.
The new Measure Builder tightened the restriction because mapping from entities on different relationship paths could cause errors. This said, after hearing your feedback, the team is now working to find the room of loosening the restriction, with which you can still map entities from different relationship paths yet ensure the result is correct.
In the meantime, I'd recommend you use this bypass method:
1. Create Measure_1 = SUM of total price of POSPurchases (but add another calculation to make it as Customer Measure*)
2. Create Measure_2 = SUM of total price of OnlinePurchases (but add another calculation to make it as Customer measure*)
3. Create Measure_3 = SUM of Measure_1** (select the attribute: SUM of total price of POSPurchases calculation) + Measure_2 (select the attribute: SUM of total price of OnlinePurchases calculation)
Measure_3 should be able to give you the result of the total sum of prices from both Pos and Online sources
** Do it as Measure-on-Measure (MoM), by mapping attribute from the tab of 'Measures' (rather than Attribute) in the mapping side panel
* Currently, Measure-on-Measure doesn't support Customer Attribute yet, so you'd need to make the measure as Customer Measure to use MoM for calculation.
Hope the above helps.
Thanks,
Wayne
