• Provide Deployment service in plugins

    The ability to access the Deployment service from a plugin in the same way the Organanzation service is provided through the Service Provider context.

  • Customization of user interface UI style ( branding, themes, header)

    A user can select a Color theme in Outlook such as Blue, Silver or Black, which then affects CRM forms, this is by design. We should be able to select the same options in CRM if this feature is available, why only allow it to be selected in Outlook under Editor options and not CRM System Settings.

  • Changing a view in a Lookup dialog auto selects the first row in the grid

    Changing a view in a Lookup auto selects the first row in the grid. This is behaviour which does not match the initial load of a lookup dialog.

    No row should be selected even when a user selects a new view.

  • CRM 2011 Developer toolkit single project or file deploy

    The CRM 2011 Developer toolkit should allow a user to right click and deploy a single project or file instead of the whole solution.

    This affects multiple developers working on the same solution.

  • Multiple forms: The form used to save a record should be held against record

    When a user selects a specific form and saves the record it should always reopen using the same form (unless security or viewid is present). Currently when opening a record the form loaded is the most recent one used for the specific entity (for the same user.

    The scenario is that you have a contact of type Individual, I enter the details and save. I then go and open an existing contact record of type trust which has its own specific form, the Individual form loads.

    Javascript can be used during the onload event to change to the correct form but you end up with 2 form loads which causes the form to flicker and produces a time lag not acceptable by end users.

    Ideally the form id should be stored against the entity record when saved.

  • More advanced Sharing capability

    There should be more granular access settings for Sharing within CRM. Either applied from the users' own security role settings or when defining a share.

    Currently, if Sharing is set to a record of type Entity A then all associated entities records are also shared based on the cascading behaviour of the relationship. Ideally, if you set one of the associated entities to a different business unit I would hope to have security applied that would check if I have Org/Bus Unit or User level Sharing access for that entity. For example if I have User Level access for Entity B then I should not see this record when it's in a different business Unit when I have a Share added to its parent Entity A in another Business Unit.


  • Show Ribbon when Form loaded in IFRAME using URL addressable forms and views.

    If you load a form or view in an IFRAME the Ribbon does not show. The areas where the ribbon should be is just a grey area.

    A scenario where this is useful is when creating wizard type interfaces using Silverlight or HTML pages to guide a user through specific steps. Dialogs are not comparable to this solution.

    Another scenario is advanced Silverlight dashboards with embedded fiorms and views in browser controls or HTML pages.


  • CRM- 4.0 Customer Field (customer lookup, multi-entity lookup (regarding))

    The ability to add a lookup control to a form that can have multiple types associated with it. This can also be extended to allow multiple selections to be added to the Lookup instead of a single selections.

    This behaviour will provide functionality that covers Customer, Regarding and Activity Party style Lookup controls.

  • Activity Rollup Cascade Behaviour

    New cascade behaviour to enable rollup of activities for parent entity relationships. This would allow a parent entity to view activities of its children in the same way Account and Contact offer this feature. This would allow custom entities to obtain the same richness as built in features.

  • Multiple Parents Allowed

    The ability to have multiple parent relationships per entity. There could possibly be a parental order aswell.