CRM2011 does not allow Partial Opportunity Closure (ID #3324)
Most CRM products offer an out of box capability to close part of opportunity as win and part as loss (for a multi product or service opportunity). The products also enable the end user to store multiple competitors on the opportunity. This is a very common business requirement. This feature i...
Dynamics CRM doesn't provide shared record view (even at entity level) (ID #3325)
How effective does CRM displays shared Opportunity (record)? In CRM 4.0 and also in CRM 2011 records shared with users/team are displayed in view along with the existing records (which the user owns it or have access to view it). However the requirement from the customer is, a) Whether it's p...
Dynamics CRM doesn't provide shared record view (even at entity level) (ID #3325)
Additional sharing functionality is required to meet customer requirements. 1> Views to show all the records shared to the user through a team or directly 2> Performing the sharing operation from a workflow 3> A direct way of seeing the list of users or teams that the record is shared with. u...
Workflow support for Associate and DisAssociate event from a workflow in CRM 2011 (ID #3391)
Customer requirement was to perform some async operation post association or disassociation on a particular entity on a particular relationship for example to be able to track when a contact get associated to an account record or get dis associated form the account record, either for a notifi...
CRM doesn’t provide ability to select a pre-defined as a field for a lookup display. (ID #3674)
In CRM when a lookup field is created, by default primary field of the referenced entity is displayed as a lookup attribute (say Account.Name). It is always a common requirement from customer to display fields other than primary attribute as a lookup attribute (say Account.AccountNumber). CRM ...
Dynamics CRM 2011 does not support customizing the system in non base language (ID #3675)
Dynamics CRM 2011 does not support customizing the system in non base language. In practical scenarios the customer's CRM implementation might have geographically distributed developer teams which might want to work and develop CRM customization collaboratively which is not possible currently....
Microsoft Dynamics CRM 2011 Report wizard has a lot of limitations to be adapted easily (ID #3698)
Dynamics CRM offers very limited feature set on Report development using its existing wizard. Most often we rely on SSRS tools to develop the Reports required by customers, however simple they may be, because our Report wizard lacks a lot of features. Custom report development in Online versio...
CRM Readonly Form Look and Feel (ID #3765)
As per current design in CRM 2011, if user has read permission on an entity, all the fields on the form look disabled and Grey. since user has no write permission already the edit ribbon button is removed, then why again disable every field. same happens with associated grids too, if user has...
Dynamics CRM currently lacks ability to clearly identify/visualise which Solution layer a component is being presented from in a multi-solution Enterprise deployment (ID #3931)
In enterprise scale projects comprising multiple managed CRM Solutions, it is crucial to have the ability to determine the effect (and intended effect) of layering solutions. Which field(s) get exposed or hidden due to the layering of solutions and how they are managed by solution framework is...
Dynamics CRM API accessible to systems other than .NET (ID #4006)
Today it is really hard to integrate Dynamics CRM 2011 with Java based systems such as SAP PI, TIBCO EAI, etc ...
The CRM is at the heart of the IT and most of our customers or prospect do not rely only on Microsoft based technologies (BizTalk, etc) .... This is a blocker for a lot of presa...