CTP3 for MS CRM 5.0 now available!!

-

CTP3 for MS CRM 5.0 now available!!
The main features offered by CRM 5.0 include:
1. Features for end users

  • Enhanced Navigation - A “Fluent UI” like Office 2007
  • Single Page Forms - Single scrolling page, “quick access” navigation shortcuts and less pop-ups and clicks to complete common task
  • Data Filtering –In-line filtering like Excel, visualization of numeric data using in-line charts and availability of drill through charts
  • WSS integration -Document management, site and document library provisioning and check-in check-out capabilities.
  • Team ownership for entities

2. Features for Administrators and Customizers

  • Filtered Lookups :)
  • Solution Management -A single unit solution (a defined set of entity customizations, workflows, e-mail templates, security roles, plug-ins etc.), version controlled solution and ability to specify selected attributes for exporting
  • “Global Picklists” at solution level that are re-usable across multiple entities.
  • Drag and Drop form editor
  • New server role for running custom code
  • Plug-In Transaction support
  • .Net 4.0 Support out of the box
  • LINQ for CRM

Read more about CRM 5 at
http://blogs.msdn.com/crm/archive/2008/12/18/an-early-look-at-crm-5.aspx
and CTP3 for CRM 5 at http://blogs.msdn.com/crm/archive/2010/03/25/microsoft-dynamics-crm5-technology-preview-released-worldwide-on-premises-and-online.aspx

Comments

Post a Comment

Popular posts from this blog

The key specified to compute a hash value is expired, only active keys are valid.

-
Ever accessed Microsoft Dynamics CRM and got the error “The key specified to compute a hash value is expired, only active keys are valid.” The error logged in the trace is as follows: MSCRM Error Report: -------------------------------------------------------------------------------------------------------- Error: Exception of type 'System.Web.HttpUnhandledException' was thrown. Error Number: 0x8004A106 Error Message: The key specified to compute a hash value is expired, only active keys are valid. Expired Key : CrmKey(Id:d0879dd3-7f9d-de11-a5c4-0003ff392bd3, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmWRPCTokenKey, Expired:True, ValidOn:09/09/2009 20:32:01, ExpiresOn:10/12/2009 20:31:55, CreatedOn:09/09/2009 20:32:01, CreatedBy:NT AUTHORITY\NETWORK SERVICE. Error Details: The key specified to compute a hash value is expired, only active keys are valid. Expired Key : CrmKey(Id:d0879dd3-7f9d-de11-a5c4-0003ff392bd3, ScaleGroupId:00000000-0000-0000-0000-000000000
Read more

IFD Implementation for custom web pages and Anonymous Access

-
When deploying my custom web pages for an IFD deployment, I got a FileLoadException (Exception from HRESULT: 0x80131401) on accessing the page in the browser. Basically, this issue arose since anonymous access was somehow disabled for the “ISV/CustomPages” application in IIS while by default it is enabled for the Microsoft Dynamics CRM website. This implied that my custom web site was using Windows NT Authentication, while the Microsoft Dynamics CRM Website was enabled for anonymous access. Hence, I got “Loading this assembly would produce a different grant set from other instances” on accessing any of my web pages from within MS CRM. Simply turning on anonymous access for my custom website did the trick and rendered all my custom web pages correctly :)
Read more

Using CRM Services to create or update records in large numbers

-
Recently, I implemented a plug in code which invoked auto creation of records from a contacts list (rather marketing lists based on MS CRM contacts) for my custom entity. The code worked well but it hanged whenever I considered a marketing list of more than 3000 contacts. The error logged read: Only one usage of each socket address (protocol/network address/port) is normally permitted. Basically, the error was thrown when the creation process exhausted the limit of socket connections allowed by the IIS and the SDK still polled for another connection and consequentially timed out after a certain number of records were created. A quick workaround for this is to change the following entries in the registry: HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort to 65534AndHKLM\System\CurrentControlSet\Services\Tcpip\Parameters\TCPTimedWaitDelay to be 30 The link : http://dmcrm.blogspot.com/2008/07/updating-records-in-mass-via-sdk.html also mentions a resolution of this by us
Read more