A look at MS CRM 5.0
Features for End Users:
Ribbon Menu – RibbonMenu as in Office 20007 will appear on top of the form in MS CRM 5.0. A customizer can still customize the toolbar and add user defined buttons to this menu by modifying ISV.Config file.
Modified Enity Forms - In CRM 4.0, tabs were used to display and group data but in MS CRM 5.0 there would be a navigation on the left hand side of the form.
Data Filtering – User would be able to filter data in Views forms by clicking and selectin the Grid Headers.
Charts – Charting feature would be available. See below:
Team Ownership – In CRM 4.0, entities were either owned by User or Organization. But in MS CRM 5.0 there will be Team Owned entities with role-based security model.
Native SharePoint Integration – There is an integration support with Windows SharePoint Services for document management. It includes site & document library provisioning, document metadata, item security, and check-in/check-out capabilities.
New Features for Administrators
Flexible Form Layout - We now have much more flexibility in how forms are laid out, for example, we can position sections side-by-side, as well as field labels on top, left or right of each field. Best of all, we can now configure "In-Line Sub-Grids" for child records, so a combination of IFrames & JScript is no longer required to make this work.
Filtered Lookups - One of the most requested features has finally made it into the product. Whilst customizing the form, you can choose a pre-defined view or better still you can filter by a related lookup on the same form.
Form Headers & Footers - Now that all tabs, sections and fields appear on a single, scrolling form, it is quite possible the form will get become quite long and you will end up scrolling up and down more often to find the information you require. In order to make the most commonly required visible at all times, you can now place these fields in a header or footer so that they will always be displayed regardless of the scrolling.
Solution Management - With CRM 4.0, you had to implement a manual process when customizing your solution, to make sure that you didn't overwrite previous customizations, or disrupt any 3rd party ISV solutions. In CRM5 we had now added the concept of solutions.
A solution is a defined set of entity customizations, workflows, e-mail templates, security roles, plug-ins etc. that can be managed as a single unit. Each solution is version controlled so presumably your can have multiple versions of the same solution installed, and roll-back to a previous version if necessary.
You can also define solution dependencies where one solution can only be installed if another solution is also installed. For example, you might have a base solution for your whole organisation, with a departmental specific solution built on top of it.
Namespace collision is avoided by defining publishers, with each publisher having a unique namespace. This avoids the common issue where the default namespace "new_" is used for all customizations, leading to potential namespace conflicts.
One final plus point is that you can now specify which attributes will be exported as part of a solution, rather than having no choice but to export the whole entity.
Multiple Option Sets - Otherwise known as "Global Picklists", you can define these at the solution level, and re-use them across multiple entities.
Drag & Drop Form Editor - One of the most time consuming customization tasks in CRM 4.0 is the form design. Every time you want to add, remove or re-position tabs, sections and attributes, you have to go through a multi-click process. With CRM5, you can now drag and drop all elements of a form, speeding up the process considerably
Audit - Although not explicitly mentioned during the sessions, I spotted an "auditing" setting on the attribute designer form, allowing you to turn auditing on or off.
New Features for Developers:
Custom Code Sandbox - There is a new server role for running custom plug-in code and custom workflow activities without requiring full trust. This means that it will be possible to run custom code in the CRM Online environment and achieve true parity between On-Premise, Partner-Hosted and Microsoft-Hosted deployments.
Plug-In Transaction Support - In CRM 4.0 you could register a plug-in to run either before (pre-event) or after (post-event) the CRM platform operation. However, you were not able to run as part of the transaction itself, so you had to right your own compensation logic in the event the CRM platform operation failed. CRM5 addresses this limitation, and you can now choose to register you plug-in as part of the platform operation. The CRM5 plug-in registration tool has been modified to support this.
Automatic Plug-In Profiling - CRM5 will keep track of how a plug-in is executing, what resources it consumes, if it is causing unexpected exceptions and whether or not it is violating security constraints. If a particular plug-in fails a number of times it is automatically disabled from executing, helping to maintain system integrity.
I want to add here only that also the CRM Workflow side will be improved a lot and the WF usage will be extended.
Do you remember how many times we've asked the Team to have filtered lookups? So natural request I think... In CRM 5.0 we'll have this feature!!
I have also a personal request: I hope on improvements regarding data import and data migration. CRM 4.0 helps a lot on data migration but it's not always so easy to migrate large amount of data from a custom system to CRM (due to the import processes that sometimes are "freezing").
Some time back I saw these feature listing on Simon Hutson's post on MS CRM 5.0. Also for complete list of features with screen shots refer here also.
