web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / msdyn_AssetCommon diff...
Customer experience | Sales, Customer Insights,...
Suggested Answer

msdyn_AssetCommon different versions in different instances after wave 2 update - stopping solution import

(0) ShareShare
ReportReport
Posted on by Fubar 2,761

Was trying to import a solution file from another environment, but import failed due to a missing control.  The error is telling me the dependency control is in the source one environment from the msdyn_AssetCommon v1.0.6.37 (visible in Solution History) but in the target environment I can only see msdyn_AssetCommon v1.0.0.30

In the source environment msdyn_AssetCommon v1.0.6.37 (was updated over the weekend), but the target solution file was not updated (both environments are Wave 2 2020 with same version numbers on the About screen).

Anyone know where msdyn_AssetCommon is coming from so I can update it to be the same in both environments?

I have the same question (0)
  • Suggested answer
    Stefan Cojocaru Profile Picture
    Stefan Cojocaru on at

    Hi there!

    The msdyn_AssetCommon solution is part of the Dynamics 365 Field Service app:

    docs.microsoft.com/.../uninstall-field-service

    You can check to see if there is an update available for Field Service using the steps in this guide: docs.microsoft.com/.../upgrade-field-service

    If no update is available, you can raise a support case to force an update of those solutions.

    Hope this helps!

  • Fubar Profile Picture
    Fubar 2,761 on at

    @Stefan Cojocaru

    thanks for your response, however neither environment has had Field Service installed (and it doesn't show Field Service under the Resources area).  

    Note, in CRM I cannot actually see a solution file for msdyn_CommonAsset but I do see it being installed in the Solution History (and only installed not removed later etc).  When I do the Solution Import the failure tells me there is a dependency on a TreeView control on Account and says its from  msdyn_CommonAsset v1.0.6.37 (in the target environments solution history it shows msdyn_CommonAsset v1.0.0.30).

  • Suggested answer
    Stefan Cojocaru Profile Picture
    Stefan Cojocaru on at

    Hi there,

    Yes, since it's a Microsoft internal solution it's not visible in the default list of solutions. You can run the following Web API query to confirm it's there: <org url>/api/data/v9.1/solutions.

    Both versions (in DEV and target) seem to be pretty old, the newest one appears to be version 1.0.0.91.

    The recommended approach would be to go back into the DEV environment and to remove this TreeView control from the solution, to avoid such a dependency. Another possible option would be to raise a support case to force an update for those internal solutions. That would have to be done for both environments since neither appears to be running the newest version.

    Hope this helps!

  • Fubar Profile Picture
    Fubar 2,761 on at

    Stefan,

    Have logged a support ticket earlier today 2010130030000383

    We didn't add the TreeView control (Microsoft have somewhere) and we can't see dependencies to Controls so we haven't been able to quickly locate where it is being used.

    Note: one of them is v1.0.6.37

  • Savas Profile Picture
    Savas 40 on at

    Hi,

    Did you find any solution for this issue?

    I'm receiving the same dependency error when deploying...

  • Fubar Profile Picture
    Fubar 2,761 on at

    Savas, Log a support ticket with Microsoft.  Our problem appears to have been an issue with MSFT rolling out Wave 2 and not rolling out all the file updates across all the instances correctly in our Region.

  • Suggested answer
    Roberto Ilidio Profile Picture
    Roberto Ilidio on at

    Hi, 

    In summary:

    1. check the version of internal solution msdyn_AssetCommon, in both, source and target organization, using web api query below:

    https://<YOUR_ORG>/api/data/v9.1/solutions?$select=uniquename,version,modifiedon&$filter=contains(uniquename,'msdyn_AssetCommon')

    2. If there is a mismatch in the solution version between the organizations, it means that this solution was not updated yet in one of your instances. Note that this update will occurs automatically at some point in time. However, if it is urgent, raise a ticket to Microsoft requesting support to apply app update for msdynce_ServiceAnchor , which will update solution msdyn_AssetCommon to version 1.0.6.37

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 81 Super User 2025 Season 2

#2
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 49 Most Valuable Professional

#3
#ManoVerse Profile Picture

#ManoVerse 40

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans