Customer Effective Blog

« Installing Windows SharePoint Services 3.0 on the same server as Microsoft Dynamics CRM 4.0 | Main | Custom Toolbars and Buttons Not Showing Up in Microsoft Dynamics CRM 4.0 »

June 20, 2008

Custom Entity Name & Outlook Offline Synchronization Failure

CRM allows the developer to create custom entities with the same name as an out-of-box entity provided the out-of-box entity is first renamed. For example, in the scenario were a custom opportunity product entity is needed, the existing entity can be renamed to XXXOpportunity Product (plural name to XXXOpportunity Products) and then the new entity can be published. In 3.0 there are no issues, but with 4.0, synchronization to an offline client will fail.

To get around the issue the custom entity can be renamed and published, synchronization can be completed, and then the entity can be renamed back. This of course is not a practical solution. A best solution for now is to just rename your custom entity with a name that is not the same as an out-of-box entity. Microsoft is working on the fix.

Posted by David Frattalone on June 20, 2008 at 07:37 AM | Permalink

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00e54fb34b6f883300e5537dd8668834

Listed below are links to weblogs that reference Custom Entity Name & Outlook Offline Synchronization Failure:

Comments

Nice post! Internet marketing is indeed gained popularity and has earned its spot of being a money making IT field.

Posted by: Jeff Paul Scam | February 03, 2009 at 02:40 AM

Great..A best band-aid for now is to aloof rename my custom article with a name that is not the aforementioned as an out-of-box entity.

Posted by: Vimax | June 07, 2010 at 10:30 AM

Verify your Comment

Previewing your Comment

Posted by: |

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:

Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.