Write-in products cannot be added to Quote or Order

Recently I have come across an issue, where the CRM users complain that they cannot add Write-in products to the Quotes and Orders.
It was a CRM 2016, which was upgraded from CRM 2011. In this case, we need to check the forms and the subgrids.

The write-in products can be added only to the grid which has the CRM default name, if you have there something else, then change it to the correct one.

For quotes - quotedetailsGrid
For orders - salesorderdetailsGrid

Also note that for Orders, you can only add new product if the pricing is not locked. Click on Use current pricing if you have the pricing lock on.

Happy CRM day,
Michal

Create Case Privileges

Lat post was about privileges for the opportunities, this time it is something similar, but for Cases.
As I mentioned, I was trying to hide all unsed entities by modifying the security roles. However, the users were not able to create new cases:-(

The SDK for Microsoft Dynamics CRM 2016 says that for creating Case (Incident) you need to have these:

incident

prvAppendIncident prvAppendToAccount prvCreateIncident

Full list of what is required for creating records is here: https://msdn.microsoft.com/en-us/library/gg328108.aspx

However, this is not correct, because users were still not able to create opportunities.

The first error was:

<Message>Principal user (Id=, type=8) is missing prvReadEntitlement privilege (Id=0925bd85-61f1-485c-b34f-240504216bd1)</Message>

So I added the read privilege for Entitlement, even though we are not using them in our CRM.

Again I wish that things like these would be documented!

Happy CRM day,

Michal

Create Opportunity Privileges

Microsoft Dynamics CRM security model is very complex and setting up a security role can be real pain.
What is the most frustrating point for me is the fact, that sometimes you have to grant privileges that do not make any sense.

My recent experience with this can be helpful for anyone. I was setting up CRM online 2016 for one customer and they are using just accounts, contacts, opportunities and cases.

I was trying to hide all unsed entities by modifying the security roles. However, the users were not able to create new opportunities :-(

The SDK for Microsoft Dynamics CRM 2016 says that for creating opportunity you need to have these:

opportunity

prvAppendOpportunity prvAppendToContact prvCreateOpportunity

Full list of what is required for creating records is here:

https://msdn.microsoft.com/en-us/library/gg328108.aspx

However, this is not correct, because users were still not able to create opportunities.

The first error was:

<Message>Principal user (Id=, type=8) is missing prvReadProduct privilege (Id=60d420ca-7a88-4c0d-8286-c425b527fa98)</Message>

So I added the read privilege for Product, but why is it required? There are no products in the CRM!

Then the CRM said: <Message>Principal user (Id=, type=8) is missing prvReadConnection privilege (Id=919f6df3-97bf-4897-82f1-9d67749eab3a)</Message>

So I had to add a read privilege for Connection entity. Again I ask why? There are not connection in the CRM and we don't want to use.

I only wish that things like this would be in the documentation, it would save so much time when customizing the CRM.

Happy CRM day,

Michal