Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics CRM forum
Unanswered

Problems with solution update and attribute dependencies

Posted on by 10

Hello everyone,

I got stuck in a solution upgrade process. We have one "Base Customization Solution" which we use to transfer in the follwoing order between the environments:

1 Dev (Starting point "Base Customization Solution" is unmanged)

2 Test/UAT (Import "Base Customization Solution" as managed solution)

3 Production (Import "Base Customization Solution" as managed solution, this is same solution as for Test/UAT)

The import is normally done by using the Update Option and everything works fine.

This time we want to use the upgrade option, because we want to remove old optionset values/status reason values. I know that this option can be more difficult, because of dependencies, I created a forth environment with a copy of Test/UAT.

The import itself works fine and we end up with two solutions:

  1. Base Customization Solution
  2. Base Customization Solution Upgrade

But during applying the update/delete the old solution we get an error:

This solution cannot be uninstalled because the 'Attribute' with id 'd7908f96-8b98-44c8-9087-f051dd75ba57(xxx_customerassetid)' is required by the 'Base Customizations Solution Upgrade' solution. Uninstall the Base Customizations Solution Upgrade solution and try again.

I checked the customizations.xml to be sure, that the mentoined attribute is contained in that solution and for me it is looking fine. See XML at the bottom.

For me it looks like, if the fields have the same name on the same entity, but not recognized there were the same.

<Entity>
<Name LocalizedName="Machine" OriginalName="Customer Asset">msdyn_customerasset</Name>
.
.
.
<attribute PhysicalName="xxx_CustomerAssetId">
<Type>lookup</Type>
<Name>xxx_customerassetid</Name>
<LogicalName>xxx_customerassetid</LogicalName>
<RequiredLevel>none</RequiredLevel>
<DisplayMask>ValidForAdvancedFind|ValidForForm|ValidForGrid</DisplayMask>
<ValidForUpdateApi>1</ValidForUpdateApi>
<ValidForReadApi>1</ValidForReadApi>
<ValidForCreateApi>1</ValidForCreateApi>
<IsCustomField>1</IsCustomField>
<IsAuditEnabled>0</IsAuditEnabled>
<IsSecured>0</IsSecured>
<IntroducedVersion>0.0.0.0</IntroducedVersion>
<IsCustomizable>1</IsCustomizable>
<IsRenameable>1</IsRenameable>
<CanModifySearchSettings>1</CanModifySearchSettings>
<CanModifyRequirementLevelSettings>1</CanModifyRequirementLevelSettings>
<CanModifyAdditionalSettings>1</CanModifyAdditionalSettings>
<SourceType>0</SourceType>
<IsGlobalFilterEnabled>0</IsGlobalFilterEnabled>
<IsSortableEnabled>0</IsSortableEnabled>
<CanModifyGlobalFilterSettings>1</CanModifyGlobalFilterSettings>
<CanModifyIsSortableSettings>1</CanModifyIsSortableSettings>
<IsDataSourceSecret>0</IsDataSourceSecret>
<AutoNumberFormat/>
<IsSearchable>0</IsSearchable>
<IsFilterable>0</IsFilterable>
<IsRetrievable>0</IsRetrievable>
<IsLocalizable>0</IsLocalizable>
<LookupStyle>single</LookupStyle>
<LookupTypes/>
<displaynames>
<displayname description="Machine" languagecode="1033"/>
<displayname description="Maschine" languagecode="1031"/>
<displayname description="Machine" languagecode="1045"/>
</displaynames>
<Descriptions>
<Description description="Unique identifier for Demonstration associated with Customer Asset." languagecode="1033"/>
<Description description="" languagecode="1045"/>
<Description description="" languagecode="1031"/>
</Descriptions>
</attribute>
</Entity>

One test i did was:

  1. Create/Clone the Test/UAT environment again
  2. Import "Base Customization Solution" as Update to cloned environment (worked fine)
  3. Make a change small change on dev
  4. Export the solution again as managed
  5. Import the solution from step 4 as upgrade into cloned environment

This provides me the same results.

Any ideas how can get more information/hint to tackle this problem ?

Best regards

Christian

Categories:
  • HakiTosh Profile Picture
    HakiTosh 10 on at
    RE: Problems with solution update and attribute dependencies

    Some additional information:

    The attribute which is causing the error is part of a relation (it is a selfreference on the customer asset entity).

    If i have a look on our Dev Environment into the solution the relation is contained in the solution.

    If i download the solution, I open the contained customization.xml in notepad++ and search for the relationname. I can not find it.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Anton Venter – Community Spotlight

Kudos to our October Community Star of the month!

Announcing Our 2024 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Dynamics 365 Community Newsletter - September 2024

Check out the latest community news

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,532 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 228,501 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans