Deletion State Codes Fields Preventing Solution Import


If you have upgraded a CRM database from 4.0. to 2011 you may have some leftover fields that end in dsc.  These fields can later on come back to haunt you by showing up as missing components when import a solution into 2011. The fields will always end in “dsc” as you can see in the image below.
image

John Hoven has written a SQL script which will remove these attributes from the database.  After removing them re-export the solution and attempt the import again.
-- Delete the custom DSC attributes from the database.
 
DELETE a 
--select A.LogicalName  
FROM   metadataschema.attribute a 
      
INNER JOIN metadataschema.entity e 
        
ON e.entityid = a.entityid 
WHERE  a.attributeof IS NOT NULL 
      
AND a.attributetypeid = '00000000-0000-0000-00AA-110000000019' 
      
AND a.logicalname LIKE '%dsc' 
      
AND a.iscustomfield = 1 
-- Delete the dsc attribute map columns
DELETE am 
--select AM.*  
FROM   dependencybase db 
      
INNER JOIN dependencynodebase dnb 
        
ON db.dependentcomponentnodeid = dnb.dependencynodeid 
      
INNER JOIN attributemapbase am 
        
ON am.attributemapid = dnb.objectid 
WHERE  db.requiredcomponentnodeid IN (SELECT dnb.dependencynodeid 
                                     
FROM   dependencynodebase dnb 
                                            
LEFT JOIN metadataschema.attribute 
                                                      
a 
                                              
ON dnb.objectid = a.attributeid 
                                     
WHERE  dnb.componenttype = 2 
                                            
AND a.logicalname IS NULL) 
-- delete attribute map required dependencies on dsc columns 
DELETE db 
FROM   dependencybase db 
      
INNER JOIN dependencynodebase dnb 
        
ON db.dependentcomponentnodeid = dnb.dependencynodeid 
WHERE  db.dependentcomponentnodeid IN (SELECT dnb.dependencynodeid 
                                      
FROM   dependencynodebase dnb 
                                             
LEFT JOIN metadataschema.attribute 
                                                       
a 
                                               
ON dnb.objectid = a.attributeid 
                                      
WHERE  dnb.componenttype = 2 
                                             
AND a.logicalname IS NULL) 
-- Delete the attribute dependencies on dsc columns 
DELETE db 
FROM   dependencybase db 
      
INNER JOIN dependencynodebase dnb 
        
ON db.dependentcomponentnodeid = dnb.dependencynodeid 
WHERE  db.requiredcomponentnodeid IN (SELECT dnb.dependencynodeid 
                                     
FROM   dependencynodebase dnb 
                                            
LEFT JOIN metadataschema.attribute 
                                                       a 
                                              
ON dnb.objectid = a.attributeid 
                                     
WHERE  dnb.componenttype = 2 
                                            
AND a.logicalname IS NULL) 
-- Delete the dependency nodes 
DELETE dnb 
-- select A.LogicalName  
FROM   dependencynodebase dnb 
      
LEFT JOIN metadataschema.attribute a 
        
ON dnb.objectid = a.attributeid 
WHERE  dnb.componenttype = 2 
      
AND a.logicalname IS NULL

Comments

Popular posts from this blog

Add User As Local Administrator On Domain Controller

Calling Dataverse Web API in PowerShell using Client Credentials

Windows Server 2008R2 VMs Shut Down After 1 to 2 Hours