it would be very handy to allow adding a new view to price list elements.
In our case we need to show the price list items like this:
ProductName | Price | Unit
But for whatever reason the views are not customizable at all, neither I can add my own view.
According to this** blog: "By design, whenever any entity metadata is changed all duplicate rules associated with that entity are unpublished."
Please, please change this design.
I'm dealing with a client now that has 9MB of -open- leads because they (seem to) constantly tinker with the Lead form and weren't aware that the duplicate detection rules weren't active.
After applying the latest Product Update related to the December 2012 Service Update for Microsoft Dynamics CRM Online, users may notice that the lead Qualify button no longer presents the Convert Lead dialog box. A new Opportunity is being created an opened, there is no chance to get the old behavior:-(
Described in KB-Article KB 2808201 (http://support.microsoft.com/kb/2808201)
We - and much more important our customers - want this functionality back!
Our duplicate detection rules keep unpublishing themselves. I'm assuming it happens when a solution is deployed -> http://www.madronasg.com/blog/duplicate-detection-rules-automatically-unpublished
So my suggestion is that system automatically re-publish the duplicate detection rules when a solution is published. Or give the admin the option to automatically republish the rules.
If you have a view that has business process flow enabled and you add the related process stage name to a view, the view will display that column in web client, but will not display it in Outlook.
Microsoft Dynamics CRM 2013 disables the Duplicate detection rules at the start of importing the customizations but does not re-enable them whether the Import succeeds or fails.
Introduce lead conversion options and make dynamics better for B2B-sales >> User can chose how he wants to convert a lead - only into a contact, into an opportunity and a contact, ...
Dynamics is focused on a 1:1 relation between a lead and an opportunity. This is not very helpful for B2B-sales. I give you two examples, why this is very inconvenient:
1) Frequently, I have multiple persons (=leads) in an potential customer organization that I try to get in contact with. If an opportunity arises from these leads, usually its only one opportunity, but more than one of the leads are involved in the same oportunity! Thus, I want to qualify one of the leads to create the opportunity, and want to convert the other leads into contacts to assign them to the opportunity - as it is not possible to assign leads to opportunities.
2) Very often I have the case that I cannot qualify a lead, as no opportunity arises. However, I want to keep the person in my database for e.g. mailing purposes. Then, I don't want to have this person not as a lead anymore, as there are no sales activites and leads should be used to prioritize sales. However, I want to have him as a contact. Thus, I need a way to convert a lead into a contact without
Suggested solution: when qualifying a lead, it must be possible to chose which entity is created from this lead. Here, two options are enough: a) opportunity and contact b) only contact.
The forced creation of an opportunity is not useful for B2B-Sales with many persons involved.
Keeping Data viable, clean and free of duplicates is one of the most challenging issues for any sized business running a CRM system. Add Soundex (en.wikipedia.org/wiki/Soundex) and add "Merge" when a duplicate is found so that the user can quickly either merge what they have just entered field by field with the existing contact or make changes. CardScan IP had an incredible field by field merge and perhaps InsideView also has some IP. Leverage the advanced awesome that exists instead of reinventing from scratch.
Enable customization for some entities: Quote Product, Opportunity Product, Customer Address, Price List Item
Dear MS CRM Team,
You made great enhancement for every rollup and for sure, the SP1 enhancement as well.
It will be greater and more powerful, if CRM open for customization for some entities.
For example: I have requirement from client to link Quote Product to multiple Address and multiple Commission record (custom entity), so it means that I need to have 1:N Relationship from Quote Product to those entities.
So what I am doing now is hardcode, provide 10 fields to let users key in, but somehow, they want to key in more than 10 inputs, so I ned unlimited input that can be achieved by providing 1:N Relationship and just add the subgrid.
This is also happened for Opportunity Product and Price List Item as well.
They are only open for N:N Relationship which is not suitable for this case, they only one 1 to N.
And then for the Price List Item, they also want to add some additional fields.
And for the Customer Address, they want to have lookup field, currently, we cannot add relationship to Customer Address.