Suggest a new Idea

    • 138

      CRM 2013: Add new custom PriceListItem View

      Suggested by O. MüllerUnder Review 17
      Category: Core Sales


      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.


    • 88

      Convert Lead dialog box - we want it back!

      Suggested by Thomas ThyenPlanned 10
      Category: Core Sales

      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 (

      We - and much more important our customers - want this functionality back!

    • 40

      MVP Bug: Cannot add process stage name to Outlook views

      Suggested by Joel LindstromUnder Review 3
      Category: Core Sales

      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.

    • 38

      Enable customization for some entities: Quote Product, Opportunity Product, Customer Address, Price List Item

      Suggested by AILEEN GUSNINew 4
      Category: Core Sales

      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.

    • 28

      Allow customizations to "Close Opportunity" form

      Suggested by Thomas McKinnieUnder Review 6
      Category: Core Sales

      Allow customizers ability to add/remove attributes on the "Close" form just like on the regular opportunity form.

    • 27

      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, ...

      Suggested by Holger LöbelPlanned 10
      Category: Core Sales

      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.

    • 26

      Editable Grid in "Opportunity Product" and "Quote Product" entities

      Suggested by Giovanni VergariNew 6
      Category: Core Sales

      We just updated to Dynamics 365 to enable the Etitable Grid feature on our tenant, just to discover that it is not applicable to "Opportunity product" and "Quote product" entities.

      My company need it to be able to use the "product" entity to add the product information to the quote, including the price from the pricelist. Then need to be able to manually insert a unit price, based on personal calculations and very specific situation. This price is what in the end will be used to calculate totals and will be the price given to the our final customer. Normally to calculate the "net price" we apply a percent discount to the list price, other times the "net price" is manually decided.

      None of the above is possible with the standard entities. Etitable grids should solve all the above easly.

      Is it possible to let the organization add this Editable Grid control to "Opportunity Product" and "Quote product" entities?

    • 25

      MVP Bug: CRM for Tablets requires quick create be enabled for system entities

      Suggested by Joel LindstromUnder Review 1
      Category: Core Sales

      If you disable quick create on standard system entities in CRM 2013 SP1, you will intermittently receive the following error when creating records:
      "Sorry, something went wrong. Please try again, or restart the app. Error Code: 0X0."
      Microsoft support confirmed that this is due to quick create forms being disabled in support case #114061711542708.

      this is bad for several reasons:
      1. This limitation is not documented, and there is potential for many users to find themselves with this error with no explanation of what is causing it and nothing showing in the trace logs.
      2. There are some very valid reasons to disable quick create. Biggest one is if you have an entity like opportunities where you need to create the record and then immediately add related records. with quick create enabled, you have to close the record then reopen it to add related records like opportunity products. By enabling quick create for the tablet app, you force users of all interfaces to use quick create, making it more cumbersome to create complex records with relationships.

    • 24

      Allow Duplicate Detection Rules on Additional Entities - Such as Addresses

      Suggested by Scott SewellUnder Review 2
      Category: Core Sales

      My customer needs duplicate detection on the Address entity - but it's not available to the duplicate detection feature.

      The desired change would allow duplicates to be detected on Addresses and other objects not currently supported.

    • 23

      Add Custom Lookups to Opportunity Product, Quote, Order and Invoice Line Item

      Suggested by Mark SCOTTUnder Review 3
      Category: Core Sales

      It should be possible to create custom lookup to an Opportunity Product, Quote Line Item, Order Line Item or Invoice Line Item. This would reduce significantly the occasions when a custom entity is used instead of the standard line items in complex solutions.