search

WARPTechnologiesLimited / XRMSolutionAssistant

A tool offering functions to help with managing exported Microsoft CRM solution files.
6 stars 2 forks source link

MissingDependency keys create noise #5

Open LycraLout opened 4 years ago

LycraLout commented 4 years ago

The Sorter is successfully and consistently sorting the MissingDependencies collection in Solution.xml. However, the keys given to the items are not consistent, therefore many false positive changes are picked up on solution extract. For example:

Developer A

<MissingDependency>
        <Required key="1454" type="50" schemaName="opportunity:RibbonDiffXml" parentSchemaName="ribboncustomization" parentDisplayName="Application Ribbons" solution="msdynce_SalesPatch201904 (9.0.1908.3007)" />
        <Dependent key="1455" type="50" schemaName="opportunity:RibbonDiffXml" parentSchemaName="ribboncustomization" parentDisplayName="Application Ribbons" />
</MissingDependency>

Developer B

<MissingDependency>
        <Required key="1487" type="50" schemaName="opportunity:RibbonDiffXml" parentSchemaName="ribboncustomization" parentDisplayName="Application Ribbons" solution="msdynce_Sales (9.0.4.0076)" />
        <Dependent key="1488" type="50" schemaName="opportunity:RibbonDiffXml" parentSchemaName="ribboncustomization" parentDisplayName="Application Ribbons" />
</MissingDependency>
jynxeh commented 3 years ago

I notice these lines are referencing different solutions - was this just a bad example or is the system actually deliberately changing these?

LycraLout commented 1 year ago

Keys are no longer used in the solution file. This is not a problem for v9 solutions.