Join our Community in its new Home - The Datorama Trailblazer Community Group!

It's been an amazing 3 years coming together in this forum to collaborate, innovate, support, and inspire each other about our shared usage of Datorama. While this is not quite a goodbye, we are excited to announce that we are getting a fresh start in our new home within the Salesforce Trailblazer Community. We have a ton of fun new content planned and you may even see the revival of some of our most popular posts from the past few years.

We’ll be keeping this group around for a bit for you to peruse, but as of November 15, we will no longer be allowing new posts or comments. Be sure to join our new group at to keep the conversation going.

We can’t wait to see you there!

Query Performance


  • Hi @Tanvi ,

    We do not have this documented as it is different in every specific case.

    The performance of mapped measurements and dimensions is always superior (faster) than calculated and filtered measurements, since there are not additional calculations during the Query.

    Most of the time filtered measurements are better than calculated measurements, since you can include very complex conditions and additional calculation. If the complexity of the calculated measurement is the same as adding a filter, then both perform the same.

    Another key difference between (Calculated measurements, Filtered measurements, and Calculated dimensions) versus (Mapped measurements and Mapped dimensions) is that in order to calculate correctly, all available values for the given measurement and/or dimension are Queried by the Calculated entities. On the other hand, when Querying Mapped entities, only the relevant values are called. Hence, the Query is longer with additional calculations.

    Let me know if you need anything else. ;)

Sign In or Register to comment.