Databases
StackOverflow2013
Postsdbo
POCRM 2011 ALM solution packager Differences from organization to organization
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCRM 2011 ALM solution packager Differences from organization to organization
    primarykey
    data
    text
    <p>My team and I are using the SolutionPackager tool from the CRM SDK to being able to version CRM 2011 solutions.</p> <p>We’ve come through many problems; for example the order in which the languages are exported depends on each organization, another problem was the entity type code of each entity also depends on each organization, etc., etc.</p> <p>In my team we also use the same kind of organizations UR (Update Rollup) 6, each develop have its Virtual Machine to develop, all VMs have the same configuration, the same languages packs installed, I mean, we also work in the same environments. But now we are facing another problem that we cannot figure out. From one organization, let’s say OrgA, I export a solution, apply the solution packager and then from one of our entities I get an XML like:</p> <pre class="lang-xml prettyprint-override"><code>&lt;attribute PhysicalName="OrganizationId"&gt; &lt;Type&gt;lookup&lt;/Type&gt; &lt;Name&gt;organizationid&lt;/Name&gt; &lt;LogicalName&gt;organizationid&lt;/LogicalName&gt; &lt;RequiredLevel&gt;none&lt;/RequiredLevel&gt; &lt;ImeMode&gt;auto&lt;/ImeMode&gt; &lt;ValidForReadApi&gt;1&lt;/ValidForReadApi&gt; &lt;IsCustomField&gt;0&lt;/IsCustomField&gt; &lt;IsAuditEnabled&gt;1&lt;/IsAuditEnabled&gt; &lt;IsSecured&gt;0&lt;/IsSecured&gt; &lt;IsCustomizable&gt;1&lt;/IsCustomizable&gt; &lt;IsRenameable&gt;1&lt;/IsRenameable&gt; &lt;CanModifySearchSettings&gt;1&lt;/CanModifySearchSettings&gt; &lt;CanModifyRequirementLevelSettings&gt;1&lt;/CanModifyRequirementLevelSettings&gt; &lt;CanModifyAdditionalSettings&gt;1&lt;/CanModifyAdditionalSettings&gt; &lt;ReferencedEntityObjectTypeCode&gt;1019&lt;/ReferencedEntityObjectTypeCode&gt; &lt;LookupStyle&gt;single&lt;/LookupStyle&gt; &lt;LookupTypes /&gt; &lt;displaynames&gt; &lt;displayname description="Organisations-ID" languagecode="1031" /&gt; &lt;displayname description="Organization Id" languagecode="1033" /&gt; &lt;displayname description="ID d'organisation " languagecode="1036" /&gt; &lt;displayname description="ID da Organização" languagecode="1046" /&gt; &lt;displayname description="Id. de la organización" languagecode="3082" /&gt; &lt;/displaynames&gt; &lt;Descriptions&gt; &lt;Description description="Eindeutiger Bezeichner für die Organisation." languagecode="1031" /&gt; &lt;Description description="Unique identifier for the organization" languagecode="1033" /&gt; &lt;Description description="Identificateur unique de l'organisation" languagecode="1036" /&gt; &lt;Description description="Identificador exclusivo da organização" languagecode="1046" /&gt; &lt;Description description="Identificador único de la organización." languagecode="3082" /&gt; &lt;/Descriptions&gt; &lt;/attribute&gt; </code></pre> <p>The problem is, that from another organization, let’s say OrgB, I export THE SAME solution and when I go to the XML for same entity as before, that file does NOT contain the line </p> <pre class="lang-xml prettyprint-override"><code>&lt;LookupStyle&gt;single&lt;/LookupStyle&gt; </code></pre> <p>The solution from both organization IS THE SAME, the configuration is also the same, so my question is why when I export the solution each VM/Organization generate a different XML file?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USshytikov
    1. USSantiago
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POCRM 2011 ALM solution packager Differences from organization to organization
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCRM 2011 ALM solution packager Differences from organization to organization
      1. USJoris Van Regemortel
      1. VTFavorite
    3. VO
      singulars
      1. POCRM 2011 ALM solution packager Differences from organization to organization
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload