{"id":31821,"date":"2022-06-13T16:19:01","date_gmt":"2022-06-13T10:49:01","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=31821"},"modified":"2022-06-13T16:19:01","modified_gmt":"2022-06-13T10:49:01","slug":"exploring-additional-filtering-capabilities-in-sales-forecasting","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2022\/06\/exploring-additional-filtering-capabilities-in-sales-forecasting\/","title":{"rendered":"Exploring additional filtering capabilities in Sales Forecasting"},"content":{"rendered":"

Introduction<\/h2>\n

The sales forecasting feature of Dynamics 365 is useful for sellers and their managers to track the sales performance against Targets & Quotas.
\nRecently when I was exploring the sales forecasting feature of Dynamics 365 in 2022 release wave1, I came across many enhancements in the forecast configuration.
\nIn the previous blog, we have already seen enhanced configuration steps for using sales forecasting in the organization. In this blog, we will explore the enhanced filtering capabilities.
\nLet us consider one scenario where I would like to forecast the opportunity records based on the user hierarchy. This can be implemented by selecting \u201cHierarchy Entity\u201d as User as shown below:<\/p>\n

\"Sales<\/p>\n

Let us quickly jump into the \u201cFilter Data\u201d configuration steps enhancements as the rest of the configuration steps have already been explained in the previous blog already.
\nEarlier, under the \u201cFilter Data\u201d configuration tab we were not able to add filters related to both the hierarchy entity and rollup entity at a time. With this advanced filtering capability, we are now able to filter data for both rollup entities as well as hierarchical entities more accurately.
\nYou can refer to the below screenshot to get an idea of the filter data feature.<\/p>\n

\"Sales<\/p>\n

Why is filtering needed?<\/strong><\/p>\n

Suppose Alan Cook (Sales Head of Africa Territory) wants to view the opportunity forecast data specifically belonging to Africa Territory. This can be achieved through \u201chierarchy filters\u201d.
\nFurther, Alan cook wants only those opportunities to be considered for calculating forecast which belongs to Fabrikam Inc. and whose estimated revenue value is greater than or equal to $1000000. This can be achieved through \u201croll up filters\u201d. You can find more details in this doc.<\/p>\n

Scenario-<\/strong><\/p>\n

Alan Cook wants to view the forecast data of his organization for the Africa territory only, and for the opportunities related only to Fabrikam, Inc. (Potential Customer), and with revenue of greater than or equal to $100000. The configuration steps to achieve this scenario is given below:
\n1. Under the \u201cFilter Data\u201d configuration tab, add one row under \u201cAdd Hierarchical filters\u201d.
\n2. Define the criteria like territory equal to Africa. By defining this only those opportunity records will be considered whose owners belong to the user hierarchy with territory as Africa.<\/p>\n

\"Sales<\/p>\n

3. Define the criteria like Potential customer belongs to Fabrikam, Inc and estimated revenue greater than or equal to $1000000. By defining this only those opportunity records will be considered whose owners belong to the user hierarchy with the territory as Africa.<\/p>\n

\"Sales<\/p>\n

Forecast layout changes:<\/strong>
\nWhen the forecast is activated, the query will be executed to filter the records inside forecast for the above defined conditions.
\nIf a parent record is suffixed with (group) in the forecast layout, it means that the parent record is filtered out. You can refer to the below screenshot:
\n\"Sales
\nPost configuration you can observe the below changes in the Opportunity Forecast View.
\nWith Applying Rollup Filters in the forecast configuration, we can see all the Opportunity records shown are only related with Fabrikam, Inc. and having Est. Revenue greater than or equal to $100000.<\/p>\n

\"Sales<\/p>\n

NOTE:<\/strong>
\n\u25cf We cannot edit or modify Filters after Activating the Forecast.
\n\u25cf If we want to apply the filter on an existing forecast, first we need to clone the Forecast configuration, apply the required filters, and then activate it.
\nFilters button available on forecast layout:<\/strong>
\nIf you additionally want to apply an additional filter on the underlying records present then there is a button available as shown in the below screenshot:<\/p>\n

\"Sales<\/p>\n

By clicking on Filters button, you can define the criteria for filtering:<\/p>\n

\"Sales<\/p>\n

The underlying records will be filtered to show only opportunity records whose estimated revenue is greater than or equal to $5000000 as shown below:<\/p>\n

\"Sales<\/p>\n

NOTE: If any user present in the hierarchy changed the territory to other than Africa then as defined the hierarchical filter condition is violated hence forecast data no longer will be displayed on the sales forecast after it.
\nAs we have seen, all the forecast data belonging to all users of the African regions are present as shown below:<\/p>\n

\"Sales<\/p>\n

Let say the user \u201cGabriela Joseph\u201d has changed its Territory from Africa to any other. For this reason, his forecast data won\u2019t be displayed after that. It gets removed, after recalculating the data or by refreshing the page.<\/p>\n

\"Sales<\/p>\n

Conclusion<\/h2>\n

With the help of these additional \u201cHierarchy\u201d and \u201cRollup\u201d filters, we can add filters to refine the opportunities or Opportunity Product (Rollup entity) and hierarchies (Like User, Account, Territory, etc.) that participate in calculating the forecast values.<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction The sales forecasting feature of Dynamics 365 is useful for sellers and their managers to track the sales performance against Targets & Quotas. Recently when I was exploring the sales forecasting feature of Dynamics 365 in 2022 release wave1, I came across many enhancements in the forecast configuration. In the previous blog, we have\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[18,2361],"tags":[2325],"class_list":["post-31821","post","type-post","status-publish","format-standard","hentry","category-dynamics-365-v9-2","category-technical","tag-sales-forecasting"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/31821","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=31821"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/31821\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=31821"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=31821"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=31821"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}