Adding custom fields to Opportunity Close form in Dynamics 365 CRM

June 26, 2022 priyeshwagh777 dynamics 365 administration, Dynamics 365 CE custom fields on opportunity close form, dynamics 365 crm opportunity close, opportunity close form

Here’s how you can add your custom fields on the Opportunity Close form!!

It ends up being a Quick Create form instead of a modal dialog box. Let’s look at how we can enable this simple setting.

App Settings in Sales Hub

Here’s how you can enable having custom field on the Opportunity Closing form –

Navigate to the SiteMap where you can change the area to App Settings.
Then, navigate to Leads + Opportunity management and look for Opportunity Closing sub-menu. There’s you’ll find the option about Opportunity Closing.
When this is turned OFF, you’ll see the usual Opportunity Closing form as below –

And using the close buttons will show you the usual Opportunity Close form.
You can turn this setting ON.

Adding Custom fields to Closing Opportunity form

Here’s how you can now add customer fields to the Opportunity Closing form once you’ve turned this setting ON in the App Settings area.

You can look for the Opportunity Close Quick Create Form in the Customization.
Then, navigate to the Opportunity Close Quick Create form.
In the Opportunity Close form, you can then add your custom fields you might have created in the Fields of Opportunity Close entity.

And when you Close the Opportunity, you’ll see a Quick Create form instead of the usual modal dialog box.
So, you can just Save and Close like a usual record and the Opportunity itself will be closed.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Flows stuck in Waiting state | Concurrency control and Degree of Parallelism in a Power Automate

June 19, 2022 priyeshwagh777 Power Automate concurrency control in power automate, degree of parallelism, flow stuck in waiting, waiting flow run

In case you are using Flows that triggers frequently and have steps in them your Flows to wait for a response, like Approvals.

Scenario

Let’s say you have Flows which use Approvals – These need to wait till the recipients respond to the Approval on their Emails

The Flow which is waiting for an Approval response will be in Running state
And if you open them, you’ll see this –
And that makes the other Flow runs after that “Waiting” to even start.
And that’s because the Flow trigger has something called as Concurrency turned on and has a certain Degree of Parallelism set which we’ll see in the section below.

Concurrency Control and Degree of Parallelism

The reason the other Flow runs were waiting because the Flow Trigger had the Concurrency control turned ON and the Degree of Parallelism set to a certain number between 1 to 100

Open settings on the Flow trigger.
You’ll find that the Concurrency is turn ON. And the Degree of Parallelism is set to a certain number.
The number set is the count of Flow Runs that are allowed to Run at once and others will be waiting.
In this case, only 1 Flow Run was allowed. Hence, the others were waiting.
You can now try to turn this off.
Now, when you try to turn this OFF and then save the Flow, you’ll see this error message –
“Flow save failed with code ‘CannotDisableTriggerConcurrency’ and message ‘The trigger ‘When_a_row_is_added,_modified_or_deleted’ of current version of workflow ‘fd33f44a-d6ad-4f06-bbf8-a693b316fa31′ has concurrency runtime configuration specified. Trigger concurrency runtime configuration cannot be removed once specified.’“
Hence, this has to be taken care at the beginning when you start designing your Flow. Or, you can use Undo to revert till the step when you turned this ON.
When Concurrency control is turned off, Flow runs can continue to run in parallel without limitations or dependency on other Flow runs.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Add Post Configuration and Post Rule Configuration entities in D365 Sales Hub Settings

June 12, 2022 priyeshwagh777 dynamics 365 administration auto post in dynamics 365 crm, post configuration, post rule configuration

In case the Post Configuration (msdyn_postconfig) and Post Rule Configuration (msdyn_postruleconfig) are missing in your Sales Hub SiteMap, here’s how you can add them somewhere in the Settings area in the SiteMap –

Like this, the Post entities don’t exist by default in the expected App Settings area and in fact are present in the default classic Settings are in Dynamics 365 CRM

Add Entities to the App

First, you’ll need to add the Entities to the Sales Hub app since they don’t appear by default –

In editing Components in the App, search for the Post Configuration (msdyn_postconfig) and Post Rule Configuration (msdyn_postruleconfig) –
Tick them and then Save so that you can later add them to SiteMap.
Add the Post Configuration (msdyn_postconfig) entity.

And Post Rule Configuration (msdyn_postruleconfig)
Once both of them have been checked, Save and then add them to the Settings area. Probably create a new Area and then add these 2 entities in them.
Save and Publish the SiteMap changes too and refresh the Sales Hub App.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Edit Settings SiteMap in classic Dynamics 365 CRM UI | [Quick Tip]

June 12, 2022 priyeshwagh777 dynamics 365 administration old sitemap in dynamics 365 crm, settings area in sitemap, sitemap in dynamics 365 crm

Now that we are moving everything to the Unified Interface across all Apps in Dynamics 365 CRM, in case you still need to edit the old Settings area in your SiteMap in the Dynamics 365 CRM classic UI.

Here’s how to find the

Edit Old Settings SiteMap in class

Here’s how you edit the classic Settings area in your classic UI in Dynamics 365 CRM. It’s presumed you are a System Administrator / System Customizer –

Create a blank Solution and save it.
Then, click on Components on the left hand menu and then Add Existing as you used to previous do to add different components in the solution.
Then, select SiteMap.
Then, look for the SiteMap which doesn’t have any App Name written next to it.
Now, you can see the Settings area which you can modify, Save and Publish your changes.