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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Failed import managed ...
Microsoft Dynamics CRM (Archived)

Failed import managed solution due to missing component(EntityRelationship idname, field idname)

(0) ShareShare
ReportReport
Posted on by Community Member

We are getting error and missing components(lookup field) while import managed solution from Test environment from Dev.

Example: test_sourceidname field is missing and its required by "Company Name" lookup field . Kindly help on this.

*This post is locked for comments

I have the same question (0)
  • Hussein Wahba Profile Picture
    Hussein Wahba 223 on at

    The information you provided is not enough but anyway you can add the field to your solution and try again, this field may be needed by the lookup because of the configured mapping in the lookup relation.

  • Suggested answer
    Temmy Wahyu Raharjo Profile Picture
    Temmy Wahyu Raharjo 2,916 on at

    When you are adding lookup (relationship) from entity a to entity b. Both entity should be in the solution because of both of those entities has a new relationship.

  • Suggested answer
    gdas Profile Picture
    gdas 50,091 Moderator on at

    Hi ,

    If my understanding is correct there is some dependent field is missing for your  entity where "test_sourceidname " field is available , so first go to your unmanaged solution and then removed the entity from unmanaged solution and then add entity again. Make sure while adding entity in unmanaged solution you will get a window where you need to select "Add All Asset" and select Metadata . After that you will get another popup  related " required component "  select yes I want to add all require component .

    Once you add your entity in unmanaged  solution then export again managed solution and try to import again.

    Hope this helps .

  • Suggested answer
    Mahendar Pal Profile Picture
    Mahendar Pal 45,095 on at

    You need to add all the dependent components, you can select that field and click on show dependency, which will list out all the dependent field for your company look and then you can add them to your solution.

  • NielsL Profile Picture
    NielsL 262 on at

    Rajalax,

    Did you find a solution to this issue? I'm getting the same error with these name fields related to lookups. 

  • Suggested answer
    Dynamics365 Rocker Profile Picture
    Dynamics365 Rocker 7,755 on at

    It seems, test_sourceidname field also new and it is not in target environment.

    Add required components while doing export of solution and then import.

  • NielsL Profile Picture
    NielsL 262 on at

    I think the "idname" field, is a field that is created behind the scenes for lookup fields by the system - so you can't add it to the solution as you can't select in anywhere.

    E.g. I have field name sem_coachid which is a lookup field in my solution:

    3125.Capture2.PNG

    When I try to export the solution I get an error saying that sem_coachidname is missing:

    3125.Capture2.PNG

    This is not a field you can see anywhere, so I believe that is a field created in the background by the system when you create a lookup field. E.g. there's no display name. 

    So the question is, how do you add that to a solution? 

    3125.Capture3.PNG

  • Suggested answer
    gotdibbs Profile Picture
    gotdibbs 45 on at

    Just came across this issue ourselves. What I ended up doing was using the solution packager to pull apart an export with just this entity in it. I couldn't find that attribute (presumably because it's completely virtual), but I did find it referenced in several views. The views were querying something like this "<condition attribute='pre_blahidname' operator='like' value='Test%' />", what we did was switch these views to use a link to the related entity and query on its primary attribute from there. That way the condition on the virtual attribute goes away.

  • NielsL Profile Picture
    NielsL 262 on at

    Microsoft came up with a fix that were used in our orgs. 

    If someone experience this refer to Support request ID 2107160050000204. They came up with a fix that will be rolled out to all orgs at a later point. 

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans