tag:blogger.com,1999:blog-1130513157270490637.post7061399664303567551..comments2014-09-26T06:37:33.116-07:00Comments on MSCRM Dynamics 2011 Tips: CRM 2011: Changing an entity from organization owned to team or user owned without droppingAli Youssefihttp://www.blogger.com/profile/12576061374075857211noreply@blogger.comBlogger13125tag:blogger.com,1999:blog-1130513157270490637.post-88162201576748714272013-05-14T04:15:23.518-07:002013-05-14T04:15:23.518-07:00Are you really sure you done this successfully? If...Are you really sure you done this successfully? If you missed out anything, can you please add??? Thanksdumboohttps://www.blogger.com/profile/15938544087904557550noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-18176402755662391052013-02-25T07:50:44.388-08:002013-02-25T07:50:44.388-08:00great questions, I'd be very interested in the...great questions, I'd be very interested in the answers if anyone out there is succeeding with this process in CRM 2011 Update 11+.Benhttps://www.blogger.com/profile/16371002312267421048noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-51391335216517046972013-02-22T12:50:12.946-08:002013-02-22T12:50:12.946-08:00uh oh. I get the same error in on premise even aft...uh oh. I get the same error in on premise even after the sql applied.<br /><br />To second igkum1709's questions, <br />In step 5, I deleted the node.<br />In step 7, I deleted the EntityRelationship Name='organization_myOrgEntity'> node and copied the team_### node and the owner_### and the user_### node (all 3).Benhttps://www.blogger.com/profile/16371002312267421048noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-43518540999023328922013-02-22T09:30:54.450-08:002013-02-22T09:30:54.450-08:00Just to close the loop, I ended up giving up when ...Just to close the loop, I ended up giving up when I saw this message, after changing the "Cascade link type" to "RemoveLink" and getting this error message:<br /><br />"The schema name is invalid or missing. Custom attribute, entity, option set and relationship names must start with a valid customization prefix. The prefix for a solution component should match the prefix that is specified for the publisher of the solution."Benhttps://www.blogger.com/profile/16371002312267421048noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-28833906872431208372013-02-22T09:28:28.040-08:002013-02-22T09:28:28.040-08:00good idea, I see the different savedquery for &quo...good idea, I see the different savedquery for "My Enity's" view.<br />Adding that went well, leading to a new error message: <br /> "The entity relationship role of the referencing entity is required when creating a new one-to-many entity relationship business_unit_new_entityname."<br /><br />So I added EntityRelationshipRoles (I found these from another entity... not entirely sure if there is something there I can tweak).<br /><br />And that leads to a different error again: <br /> "Cascade link type 'NoCascade' is invalid for Delete."<br /><br />Why is NoCascade invalid? Because it is not a valid option for delete in CUSTOM entities. This is taking me down the road as if this was a custom entity relationship, not a system relationship, which I am trying to trick it to believe. <br /><br />All this said, this is an online org! So really it is a pointless endevour, I guess I just had to confirm myself the hard way.<br /><br />I will try again in an on-premise environment and make the required sql changes.Benhttps://www.blogger.com/profile/16371002312267421048noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-76846906893418237662013-02-14T08:32:35.082-08:002013-02-14T08:32:35.082-08:00I've tried it with a 1:1-copy of the entity, u...I've tried it with a 1:1-copy of the entity, update the OwnershipTypeMask in the SQL database and get the error 'Object reference not set to an instance of an object' on the entity. What are you doing different than me?<br />On step 5: Do you delete the <attribute PhysicalName='OrganizationId'> node?<br />On step 7: Do you delete the <EntityRelationship Name='organization_myOrgEntity'> node? And copy only the team_### node or the owner_### and user_### node too?igkum1709https://www.blogger.com/profile/10303150810218246908noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-53942963996530917102013-02-14T08:27:15.411-08:002013-02-14T08:27:15.411-08:00This comment has been removed by the author.igkum1709https://www.blogger.com/profile/10303150810218246908noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-5181522424243554122013-02-13T12:18:30.798-08:002013-02-13T12:18:30.798-08:00Review the customizations xml, more specifically, ...Review the customizations xml, more specifically, the formXml and view section. There is probably a reference to the organization and/or a reference needed for a user/team.<br />I would suggest creating a new user owned entity and reviewing the form and view sections of the customizations.xml. If you notice a lookup for user, copy that node and add to the entity you want to change.<br />HTH.Ali Youssefihttps://www.blogger.com/profile/12576061374075857211noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-46771617522886420082013-02-13T12:02:29.152-08:002013-02-13T12:02:29.152-08:00"Entity Owner cannot be a referenced entity b..."Entity Owner cannot be a referenced entity because it does not have a lookup saved query" -- I'm trying online and get stuck here. I think I'm SOL.Benhttps://www.blogger.com/profile/16371002312267421048noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-35764503079505073142013-02-13T08:15:25.900-08:002013-02-13T08:15:25.900-08:00I'm using on premise and get the error too whi...I'm using on premise and get the error too while importing. Is there a trick or something to do this without deleting the entity?igkum1709https://www.blogger.com/profile/10303150810218246908noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-24576773116583751482012-07-06T05:41:40.844-07:002012-07-06T05:41:40.844-07:00if you are using on premise, then above solution w...if you are using on premise, then above solution will work. But if you are using on line, then you have to delete the entity first before reimporting the solutionNutrinohttps://www.blogger.com/profile/18084381974433205088noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-51847815412402234092012-06-20T11:27:40.258-07:002012-06-20T11:27:40.258-07:00I get the same error.
Is there a table other tha...I get the same error. <br /><br />Is there a table other than MetadataShema.Entity that needs to be updated?toinehttps://www.blogger.com/profile/01294798969069494027noreply@blogger.comtag:blogger.com,1999:blog-1130513157270490637.post-35129020753708674252012-06-11T05:14:11.817-07:002012-06-11T05:14:11.817-07:00Hi,
I have gone through all the steps you highlig...Hi,<br /><br />I have gone through all the steps you highlighted on this post but I am getting this error "Object reference not set to an instance of an object". Can you please advise. NyikoN'wana Mamahttps://www.blogger.com/profile/10182585347785528207noreply@blogger.com