In an organisations that originated in CRM 1.2, after upgrading to CRM 2013 some accounts could not be opened, with an 'Unexpected error' message. The trace log showed:
Crm Exception: Message: An unexpected error occurred., ErrorCode: -2147220970, InnerException: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Crm.BusinessEntities.RecordDisabledMergedNotificationGenerator.BusinessLogic(IBusinessEntity entity, IOrganizationContext context, NotificationAdder notificationAdder)
The records that had the error had a null value in the merged attribute. Setting this to 0 fixed the problem
Either the CRM 2013 upgrade process should set the merged attribute to zero if it is null, or the CRM code should not error if merged is null
Comments
Thanks for the feedback this product suggestion looks like it is a bug not a suggestion. We have made note of the issue, this item will be closed out as postponed and this is a bug not a feature. Please use the following link https://community.dynamics.com/crm/p/support.aspx to enter a support case if you would like to make sure to have the issue tracked more closely. Thanks for the feedback. Larry
Category: Account, Contact, Calendar and Activity Management
Administrator
Thank you for submitting your idea to our ideas portal. We appreciate your contribution and the time you took to share it with us. We have shipped many enhancements since this idea was posted and it is likely that it has been resolved. If not, kindly reopen. Thank you again for your continued support.