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) / import solution says i...
Microsoft Dynamics CRM (Archived)

import solution says it's missing lookup name fields

(0) ShareShare
ReportReport
Posted on by Martin Donnelly 1,030
Account (preferredequipmentidname)
 preferredequipmentidname Field Order (Customer)
Account (tp_address2_country_lookupname) tp_address2_country_lookupname Field

Account (tp_Account_Address1_Country_Lookup)

As we all know, there is no way to add this internal field to a solution.  What is puzzling is, why these two?  There are plenty of other custom and OOTB lookups in the solution?

PS- I wasn't the one who prescribed the suffix "lookup" to the second one

*This post is locked for comments

I have the same question (0)
  • Dynamics Objects 365 Profile Picture
    Dynamics Objects 365 550 on at

    Are these two fields created separately for the two orgs? Source and Target?

  • talk2.gauravb Profile Picture
    talk2.gauravb 120 on at

    Have you imported any other solution in your CRM, if you are not sure from where these fields are added. I will recommend to go to database and execute below query to find out it is part of which solution and whom it has been last modified.

    select s.SolutionIdName,s.ModifiedOn,u.FullName

    from SolutionComponent s

    left outer join SystemUser u on u.SystemUserId=s.ModifiedBy

    where s.ObjectId=

    (select a.EntityId from Attribute a where a.LogicalName='[ATTRIBUTELOGICALNAME]')

    order by s.ModifiedOn desc

  • Suggested answer
    Joseph McGregor Macdonald Profile Picture
    Joseph McGregor Mac... 597 on at

    Hi mardukes

    I experienced this error once when I had only the lookup field inside a solution and tried to deploy it. It mysteriously resolved after I removed the field out of the solution, then added it in again by adding the N:1 relationship, rather than the lookup field into the solution. Adding the relationship rather than the lookup field seemed to trigger some internal process which added both the dependent lookup field, as well as the name reference you refer to

    Not sure this will work for you, but perhaps try something along the lines as I have described and see if it works

  • Martin Donnelly Profile Picture
    Martin Donnelly 1,030 on at

    Does anyone have any other suggestions where to look.  I'm seeing the export saying two lookup names are missing, new_discountpricebookidname and new_shippingmethodidname (3 times.)

    • those strings don't come up anywhere in the customizations xml of the solution
    • only one of them, shipping, shows up in the solution xml (if both showed up I'd hack it)
    • I run through the exercise of removing the lookups from the solution, bringing them back and accepting the inclusion of the lookup names (I've even declined it to no avail)
    • I've checked for references in views
    • even reviewed the relationship mappings

    Wondering why one type 2 would require another type 2:

    Think Microsoft support could fix 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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans