Entity forms missing after upgrading to CRM2011 from CRM4: CRM2011 On-Premise

Tutte le risposte

• martedì 10 gennaio 2012 10:50

   

   
  

  0
  On which Update Rollup version was your crm 4.0 org?

  ---

  Carsten Groth http://carstengroth.wordpress.com Microsoft Certified Technology Specialist
  • Risposta
  • Citazione

   
• martedì 10 gennaio 2012 11:08

   

   
  

  0
  The database I've been testing the upgrade with is currently patched to CRM Rollup 17, which I believe should be supported.  However, I'll try installing the latest rollup and report back.
  • Risposta
  • Citazione

   
• martedì 10 gennaio 2012 11:54

   

   
  

  0

  I´ve tested back to UR19 and it works with that

  ---

  Carsten Groth http://carstengroth.wordpress.com Microsoft Certified Technology Specialist
  • Risposta
  • Citazione

   
• martedì 10 gennaio 2012 15:13

   

   
  

  0

  If you setup a new web server & SQL Server for CRM 2011, I had a lot of luck doing the following:

  1. Install a Fresh Copy of CRM 2011 on the new server

  2. Setup an empty/default Org

  3. Backup & Restore CRM 4.0 Organization database to the new SQL Server

  4. Import the Restored Organization to CRM 2011 for the Upgrade

  I'm not saying this is necessarily a fix all for this, but in the past I've just experienced very good results upgrading this way when a new server is available for CRM, even with very complicated customizations. 

  Jeremy

  • Risposta
  • Citazione

   
• mercoledì 11 gennaio 2012 10:59

   

   
  

  0

  Hi Jeremy,

  Thanks for your reply.  The process you suggested is the one that I am following due to the fact that our CRM4 server is 32bit.

  Cheers,

  Adrian

  • Risposta
  • Citazione

   
• mercoledì 11 gennaio 2012 15:08

   

   
  

  0

  Adrian,

  I had I read the main line in your first post I would've realized that, sorry about that.  Are you applying Update Rollup 5 to the the CRM 2011 instance before importing the organization or are you just starting with the media install (no rollup) and then importing?

  Also, was this 4.0 environment at any point and upgrade from CRM 3.0?

  THanks,

  Jeremy

  • Risposta
  • Citazione

   
• giovedì 12 gennaio 2012 19:33

   

   
  

  0

  Hi Jeremy,

  I'm upgrading using the latest CRM 2011 installer, which should already got Rollup 5 applied - at least the version number matches the post Rollup 5 version number according to the Microsoft CRM Rollups information page.

  The organisation was created in CRM4 and NOT upgraded from CRM3.

  Cheers,

  Adrian

  • Risposta
  • Citazione

   
• venerdì 13 gennaio 2012 10:15

   

   
  

  0

  I have tried creating a blank CRM4 organisation (SANDBOX) and import just 4 custom entities from my main organisation (LIVE).  1 which had import correctly with the forms appearing in CRM2011 and 3 that had missing forms.

  I then followed the same upgrade procedure as I had done before: 1. copy SANDBOX_MSCRM database to new SQL server instance; 2. import SANDBOX into CRM2011.

  In this case the entity that had worked in the initial upgrade tests also worked in this test.  The other 3 entities still had missing forms but they were in the SystemForms table in the database but parented to the wrong entities.

  Finally, I tried creating another CRM4 organisation (SANDBOX2) and imported the 3 that had missing forms above.  I then followed the same upgrade procedure.  This time, the 3 entities had the forms correctly upgraded and attached in CRM2011.

  In each of these cases there have been no errors reported in the CRM 2011 upgrade log.  I have been over the CRM4 customisations xml with a fine tooth comb and cannot find any issues with it. The XML validates against the schema and all the ids appear to be present and correct. 

  Today I shall be applying CRM4 Rollup 20 to my development environment and re-testing the upgrade. I will report back if there are any new developments.

   

  • Risposta
  • Citazione

   
• venerdì 13 gennaio 2012 16:34

   

   
  

  0
  I have tried installing CRM4 Rollup 20 and manually installing CRM2011 Rollup 5.  The issue still exists so I have raised a support call with Microsoft to get it resolved.
  • Risposta
  • Citazione

   
• venerdì 13 gennaio 2012 22:45

   

   
  

  0

  AdrianRitchie,

   

  I would be interested in knowing how you resolved this issue.   Can you post once you have a solution?

   

  Regards, SK

  
  

  • Modificato stevenmk venerdì 13 gennaio 2012 22:46
  •  
  • Risposta
  • Citazione

   
• martedì 24 gennaio 2012 15:52

   

   
  

  0

  We're still testing to identify a complete solution (I'm running import at the moment) but one thing that was noticed is that some of the form tabs and sections had missing label descriptions.  These are required values when entered via the CRM4 Customisations UI.  Quite how they became empty is unknown as we have only ever used CRM4 and only with the based english language.

  I've fixed the missing labels in Visual Studio with the help of TTXPathNavigator (http://visualstudiogallery.msdn.microsoft.com/c5d4671c-2e29-4452-b039-6f931b7b1155) and the following XPath queries to find the missing labels:

  //tab/labels/label[@description=""]
  //section/labels/label[@description=""]
  

   

  I'll post another reply when I make further progress

  • Risposta
  • Citazione

   
• martedì 24 gennaio 2012 17:42

   

   
  

  0

  Fixing the missing section and tab labels didn't resolve the issue.

  However, I may have identified another cause, the entities that had missing forms after the upgrade also had duplicate section and tab ids in the CRM4 customizations.xml.  I identified these with the following XSLT and SQL and then fixed the problems with TTXPathNavigator in Visual Studio:

  XSLT:

  <?xml version="1.0" encoding="utf-8"?>
  <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
      xmlns:msxsl="urn:schemas-microsoft-com:xslt" exclude-result-prefixes="msxsl"
  >
      <xsl:output method="text" />
  
      <xsl:template match="*" xml:space="preserve">
        truncate table sectionids
        truncate table tabids
        <xsl:apply-templates select="//section" />
        <xsl:apply-templates select="//tab" />
      </xsl:template>
  
    <xsl:template match="tab" xml:space="preserve">
      insert into tabids (id, entity, objecttypecode) values  ('<xsl:value-of select="@id"/>', '<xsl:value-of select="ancestor::entity/@name"/>', '<xsl:value-of select="ancestor::Entity/ObjectTypeCode"/>')</xsl:template>
    
    <xsl:template match="section" xml:space="preserve">
      insert into sectionids (id, entity, objecttypecode) values  ('<xsl:value-of select="@id"/>', '<xsl:value-of select="ancestor::entity/@name"/>', '<xsl:value-of select="ancestor::Entity/ObjectTypeCode"/>')</xsl:template>
  </xsl:stylesheet>
  

  SQL:

  SELECT xpath = '//section[@id="{'+LOWER([id])+'}"]/@id', COUNT(id) FROM sectionids group by id having COUNT(id) > 1
  union
  SELECT xpath = '//tab[@id="{'+LOWER([id])+'}"]/@id', COUNT(id) FROM tabids group by id having COUNT(id) > 1
  

  I'm running the import into CRM2011 at the moment and will post another update once that is complete.  I would have expected to have received error messages about this in the import log but I suspect the import wizard is catching exceptions and not always logging them.

  • Risposta
  • Citazione

   
• martedì 24 gennaio 2012 19:11

   

   
  

  0

  Testing the import having fixed the tab and section ids still didn't fix the issue.  However, using the same approach as above I have also found duplicate form ids.  I have fixed these and am re-running the import into CRM 2011.

  I was warned by Microsoft Support that editing the customizations.xml is not supported.  This contradicts this MSDN page which states that modifications to the FormXml areas of the customizations.xml file is supported: http://msdn.microsoft.com/en-us/library/cc906201.aspx

  My investigations indicate that in CRM4 the uniqueness of the ids in the XML is not varified but in CRM 2011 the storage of structure define in the CRM4 customizations.xml does require the ids to be unique.  Unforunately the import wizard does not appear to log these errors.

  • Risposta
  • Citazione

   
• giovedì 26 gennaio 2012 23:43

   

   
  

  0

  Directly editing the customizations.xml is not supported. Do you remember what other customizations you have made?   Did you add any form/field event handlers?

  Thanks,

  Mike

  • Risposta
  • Citazione

   
• venerdì 27 gennaio 2012 07:15

   

   
  

  0

  Hi Mike,

   

  The MSDN documentation states that the FormXml areas of the CRM4 customizations.xml can be modified directly in the Customizations.xml outside of the CRM UI. 

  This is stated on this MSDN page: http://msdn.microsoft.com/en-us/library/cc906232.aspx

  
  

  I am awaiting confirmation from my support case engineer that what I have done will be supported.

  Kind regards,

  Adrian

   

  
  

  • Modificato AdrianRitchie venerdì 27 gennaio 2012 07:16 Fixed url
  •  
  • Risposta
  • Citazione

   
• mercoledì 18 luglio 2012 07:00

   

   
  

  0

  Hi Adrian

  Do you find the solution of the problem I am also facing the same issue after upgrading to CRM 2011

  Thanks,

  Safdar Shah

  • Risposta
  • Citazione

   
• giovedì 19 luglio 2012 06:23

   

   
  

  0

  Hi All,

  Anyone can have solution of this problem?

  Regards,

  Safdar Shah

  • Risposta
  • Citazione

   
• venerdì 20 luglio 2012 09:28

   

   
  

  0

  Hi Safdar,

  The problem in my case was due to duplicate Form, Tab and Section Ids in the CRM4 customisations.xml being duplicated across entities.  To resolve the problem I had to export the customisations from CRM4, change the Guids and re-import it into CRM4.  When I then performed the upgrade to CRM2011 the forms for the entities appeared.

  My post with the XSLT helps you find the duplicate Guids in the FormXML section but it's a manual process to replace them.

  Before anyone complains about that being not supported by Microsoft, I spoke to Microsoft Support about it and they said that my database would still be supported after the upgrade.

  Cheers,

  Adrian

  • Risposta
  • Citazione