{"id":23025,"date":"2020-03-04T11:04:19","date_gmt":"2020-03-04T11:04:19","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=23025"},"modified":"2020-04-02T05:48:06","modified_gmt":"2020-04-02T05:48:06","slug":"forecasts-goals-in-a-new-look","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2020\/03\/forecasts-goals-in-a-new-look\/","title":{"rendered":"Sales Forecast for Dynamics 365 Sales – 2020 Release Wave 1 – Goals in a new look"},"content":{"rendered":"

Goals were introduced as an accelerator the first time around way back in CRM 4 or CRM 2011 days and it continued to be included as a part of the Sales offering within Dynamics 365 CRM till date with little to no update to this feature over the years. Honestly this was one area on the sitemap I never bothered to click all these years.<\/p>\n

And today I see Forecasts, in the same Goals area, well the Goal section gets a new flashy title too \u2018Performance Management\u2019.<\/p>\n

\"Forecasts\"<\/p>\n

I did have to read through the documentation<\/a> to understand how this works, but it follows the same concept as the Goals feature. You set Targets\/Goals for the period and evaluate performance against the set Targets.<\/p>\n

Forecast for both configuration and evaluating the results is now available in a more visual format compared to the record-based design of the earlier feature.<\/p>\n

Forecasting understands that targets are assigned and evaluated either based on teams and user hierarchy or regional and territory based. These are the two types of forecasts that is allowed to be defined as at the time of writing this article.<\/p>\n

\"Forecasts\"<\/p>\n

Looks to be a very limited version for now as this currently only supports Opportunity entity which is also the most common entity for forecasting.<\/p>\n

Org Chart Forecast<\/strong><\/h2>\n

In this you choose the users at the top of the hierarchy. Using the Manager lookup on the user entity, the entire hierarchy of users is auto selected.<\/p>\n

\"Forecasts\"<\/p>\n

Territory Forecast<\/strong><\/h2>\n

Make sure to enable Territory hierarchy before you create a forecast using this template. Customize the Territory entity \u00e0 Choose the hierarchy defined in the hierarchy settings.<\/p>\n

\"Forecasts\"<\/p>\n

Edit the setting to bring up the following form.<\/p>\n

Click on the hyperlink to Make a relationship enabled for hierarchies.<\/p>\n

\"Forecasts\"<\/p>\n

With that done, selecting the Territory Forecast will bring up the following settings:<\/p>\n

\"Forecasts\"<\/p>\n

Choose the Territories at the top of the hierarchy in this case.<\/p>\n

The rest of the steps remain the same for both types of Forecast.<\/p>\n

Set the time period, it could be monthly or quarterly.<\/p>\n

As you proceed, the next step is to choose the security roles that are allowed to view the forecast.<\/p>\n

\"Forecasts\"<\/p>\n

Layout Step, this got me a little confused. This is where you define the rollup fields and criteria for your forecasts.<\/p>\n

To classify the actuals against various stage of the business process, you can select the optionset field that defines the stages.<\/p>\n

Microsoft ships Forecast Category as a custom attribute along with predefined optionset values. I choose the same field here for simplicity. But you could choose any other optionset field of your choice.<\/p>\n

\"Forecasts\"<\/p>\n

The layout preview auto-refreshes to list out the report view for you.<\/p>\n

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

Click on the ellipsis of each of the columns added to configure the rollup definition for the column.<\/p>\n

\"Forecasts\"<\/p>\n

And these are the important properties of each column.<\/p>\n

\"Forecasts\"<\/p>\n

Rollup the value of Est. Revenue field where Forecast category = Pipeline and Est. Close date is within the forecast period defined in the first step.<\/p>\n

The layout designer also has the ability to add custom columns choosing the Add Column option.<\/p>\n

Below I have configured a new column to include the title of each of the users in the report.<\/p>\n

Choosing the type as \u2018Hierarchy related\u2019 allows you to select the fields from the hierarchy entity, in case of org chart type of Forecast it is User.<\/p>\n

\"Forecasts\"<\/p>\n

In the final set, we activate the forecast and then you have the ability to upload an excel file with the forecast targets for the users.<\/p>\n

\"Forecasts\"<\/p>\n

Do make sure to complete the configuration in the previous steps before you activate the forecast. While it allows you to de-activate the forecast and the edit forecast option is also available, all the layout columns are disabled, so you cannot really make any edits to the forecast other than upload revised targets from this tab.<\/p>\n

To upload the targets, first download the template. The template will include columns for all the users selected in the previous steps for whom the targets need to be defined.<\/p>\n

\"Forecasts\"<\/p>\n

The first tab includes the quota for each individual user. In the second tab you can set the target for the top-level records, in this case users.<\/p>\n

With this you are all set to use the new Forecasting feature.<\/p>\n

The Forecast report\/visualization needs to be added manually to the sitemap. Add a sub-area to the site map that points to the following URL:<\/p>\n

\/main.aspx?pagetype=control&controlName=ForecastingControls.FieldControls.ForecastGridPage<\/strong><\/p>\n

And voila, here you are;<\/p>\n

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

Use the Recalculate button at the top right for on-demand recalculation for the latest values.<\/p>\n

I couldn\u2019t get the Trend and Flow tab to work.<\/p>\n

Now the same could be visualized using the KANBAN control to get the details of the opportunities in each of these forecast stages for each of the users.<\/p>\n

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

You can download this Kanban control for your datasets from here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Goals were introduced as an accelerator the first time around way back in CRM 4 or CRM 2011 days and it continued to be included as a part of the Sales offering within Dynamics 365 CRM till date with little to no update to this feature over the years. Honestly this was one area on\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":23236,"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":[13,16,18,19],"tags":[],"class_list":["post-23025","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-customizations","category-dynamics-365","category-dynamics-365-v9-2","category-dynamics-crm"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/23025","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=23025"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/23025\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/23236"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=23025"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=23025"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=23025"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}