CRM 2011 ALM solution packager Organization to Organization Differences

Question

My team and I use the SolutionPackager tool from the CRM SDK to release solutions at CRM 2011.

We face many challenges; for example, the order in which languages ​​are exported depends on each organization, another problem was that the entity type code of each object also depends on each organization, etc. etc.

In my team, we also use the same UR (Update Rollup) 6 organizations, each of which develops its own virtual machine for development, all virtual machines have the same configuration, the same language packs, I mean, we also work in those same environments. But now we are facing another problem that we cannot understand. From one organization, say, OrgA, I export a solution, apply a solution package, and then from one of our objects, I get XML as:

<attribute PhysicalName="OrganizationId"> <Type>lookup</Type> <Name>organizationid</Name> <LogicalName>organizationid</LogicalName> <RequiredLevel>none</RequiredLevel> <ImeMode>auto</ImeMode> <ValidForReadApi>1</ValidForReadApi> <IsCustomField>0</IsCustomField> <IsAuditEnabled>1</IsAuditEnabled> <IsSecured>0</IsSecured> <IsCustomizable>1</IsCustomizable> <IsRenameable>1</IsRenameable> <CanModifySearchSettings>1</CanModifySearchSettings> <CanModifyRequirementLevelSettings>1</CanModifyRequirementLevelSettings> <CanModifyAdditionalSettings>1</CanModifyAdditionalSettings> <ReferencedEntityObjectTypeCode>1019</ReferencedEntityObjectTypeCode> <LookupStyle>single</LookupStyle> <LookupTypes /> <displaynames> <displayname description="Organisations-ID" languagecode="1031" /> <displayname description="Organization Id" languagecode="1033" /> <displayname description="ID d'organisation " languagecode="1036" /> <displayname description="ID da Organização" languagecode="1046" /> <displayname description="Id. de la organización" languagecode="3082" /> </displaynames> <Descriptions> <Description description="Eindeutiger Bezeichner für die Organisation." languagecode="1031" /> <Description description="Unique identifier for the organization" languagecode="1033" /> <Description description="Identificateur unique de l'organisation" languagecode="1036" /> <Description description="Identificador exclusivo da organização" languagecode="1046" /> <Description description="Identificador único de la organización." languagecode="3082" /> </Descriptions> </attribute> 

The problem is that from another organization, say OrgB, I export the SAME solution, and when I go to XML for the same object as before, this file does NOT contain a line

 <LookupStyle>single</LookupStyle> 

A solution from both organizations IS SUCH USED that the configuration is also the same, so my question is why when I export the solution, each VM / Organization generates a different XML file?

Answer 1

We experienced the same glitch in our project. I think the problem is that single is the default value of <LookupStyle> (in other words <LookupStyle/> == <LookupStyle>single</LookupStyle> . Thus, from the user interface it might seem that the configuration of both organizations is the same (on actually), but the data stored in the database is different. Unfortunately, the export of the solution takes into account only what is stored in the database. I am absolutely sure that exporting / importing the solution with this object will not help. What can help, is to save the object.

Btw - I found this package comparison approach very useful. Only I use BeyondCompare ...