Merge Error 'No Attribute'

At a client we received an error 'No Attribute' while trying to merge 2 accounts. In the trace logs the error said: 'owninguser field not known in custom entity'.
Apparently this was caused by the parental relationship between account and a custom entity. After changing the parental relationship to a referential (restrict delete), the merging worked fine.

I did some searching on the internet and it seems that Microsoft is aware of the bug and working on a hotfix, but no release date is yet known.

Kevin Dosseray

Comments

Post a Comment

Popular posts from this blog

New CRM 2011 VM on PartnerSource

Microsoft released a Virtual Machine for CRM 2011 on PartnerSource. The VM includes CRM 2011, SharePoint, Exchange, Outlook client and XRM scenarios such as portals. Please note that the VM must be run on a 64bit server with Hyper-V. You can download it here: https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUID={060C9677-229D-49E1-9F00-95E56D9F1657}&NRORIGINALURL=/partnersource/deployment/methodology/vpc/MSD_CRM2011VirtualMachine&NRCACHEHINT=Guest&wa=wsignin1.0
Read more

Disable CRM Form through JavaScript

I often get the question how to disable a form, so here it is: The trick is to disable all the fields that are on the form. You can do this by using the following JavaScript: if (crmForm.FormType == 2) { for( var i = 0 ; i { if( crmForm.all[ i ].req) crmForm.all[ i ].Disabled = true; } } In the code I check if the form is in the update modus (FormType == 2), because I don't think that disabling a form while in create modus makes much sense. In the real world you'd probably disable a form depending on the value of another field. Would you like to keep some fields editable, you can do the following: if (crmForm.FormType == 2) { for( var i = 0 ; i { if( crmForm.all[ i ].req && crmForm.all[i].id != "name") crmForm.all[ i ].Disabled = true; } } Here I disable all fields except the name field (crmForm.all[i].id != "name"). You can add other fields according to your needs. Just make sure you use the sc...
Read more

CRM 2011 together with the Scribe Adapter for CRM 4.0

So you upgraded your CRM 4.0 to CRM 2011, but still use the CRM 4.0 Adapter in your Scribe integrations (Scribe Adapter for CRM 2011 will be released the end of March 2011). No worries: if you don't use hosted CRM, your integrations will still work. The Scribe Adapter for MSCRM 4.0 works with all CRM 2011 entities that existed in MS CRM 4.0. So as long as you don't use new CRM 2011 functionality (Connections, Sharepoint, Auditing...) in your integrations and it is a CRM 2011 On Premise or a CRM 2011 online version, you can use the MSCRM 4.0 Adapter without any problems. As we all know, the old MSCRM 4.0 endpoint is still accessible in CRM 2011, so the compatibility sounds logical. The reason that you can't use the adapter in a CRM 2011 hosted environment is because of the Claims Based authentication used in this environment. The authenticaton is not supported by the old adapter. This will be no problem with the new CRM 2011 adapter. Please note that you will need a...
Read more