Skip to main content

Notifications

Customer experience | Sales, Customer Insights,...
Answered

Creating measures from 2 Entities

(0) ShareShare
ReportReport
Posted on by 87

Hi, 

In the past, I could combine 2 different entities to create measures (i.e. lifetime spend = total price of PoS purchases + total price of online purchases). 

However, with the new Customer Insights release, this seems not to be possible anymore. How do I solve this?

Thanks in advance

  • Verified answer
    Wayne Wang Profile Picture
    Wayne Wang on at
    RE: Creating measures from 2 Entities

    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

  • Mleu Profile Picture
    Mleu 55 on at
    RE: Creating measures from 2 Entities

    Hi Wayne,

    I am facing the same issue. But I know that it is possible to make such calculation as I've seen it on one of the live sessions a couple of weeks ago. I can't seem to remember how the tutor was able to do it as I was in a rush. Could you provide us steps by using Contoso dataset as an example ?

  • rdj Profile Picture
    rdj 87 on at
    RE: Creating measures from 2 Entities

    Hi,

    Many thanks for the acknowledgement of the issue and changes. But do you have any suggestions on how to solve this issue OR if there is any thread related to this? How do I get the "total lifetime spent" from both PoS and Web purchases?

    I tried to link the 2 separate entities (not the Customer Entity, but PoS and Web Purchases) by using "LoyaltyID". However, this also didn't work.

    Thanks for shedding some more lights.

    Best regards,

    Reddy

  • Suggested answer
    Wayne Wang Profile Picture
    Wayne Wang on at
    RE: Creating measures from 2 Entities

    Hello rdj,

    Thanks for the question. Yes, you are right that the redesigned Measure Builder doesn't allow a calculation mapping attributes from entities that are on different entity paths, i.e. the paths of relationship connecting the entity with the Customer Entity.

    The reason is that this type of calculations tend to be error prone, so we decided to tighten the restriction on entities that can be mapped, plus added an error message/warning at the top.

    Hope this helps. Please let me know if you have any further question.

    Best,

    Wayne

  • Wayne Wang Profile Picture
    Wayne Wang on at
    RE: Creating measures from 2 Entities

    Hello rdj,

    Thanks for the question. Yes, you are right that the redesigned Measure Builder doesn't allow a calculation mapping attributes from entities that are on different entity paths, i.e. the paths of relationship connecting the entity with the Customer Entity.

    The reason is that this type of calculations tend to be error prone, so we decided to tighten the restriction on entities that can be mapped, plus added an error message/warning at the top.

    Hope this helps. Please let me know if you have any further question.

    Best,

    Wayne

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Congratulations to the January Top 10 leaders!

Check out the January community rock stars...

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,160 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 230,962 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans