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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Field Mappings

(0) ShareShare
ReportReport
Posted on by 341

Hi Folks,

We are seeing an issue where Lookup Fields mapped during record creation are appearing as "No Name".  Microsoft fix for this is to delete the mapping and create it again.  I tested this in the default solution and it does resolve the issue.

we are using managed solutions so i deleted several of the other problematic field mappings from the default solution and then imported a solution with new field mappings, however the relationships haven't been updated with these, and no new mappings have been created.

is this expected behaviour?

thanks in advance

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Alex Fun Wei Jie Profile Picture
    33,628 on at

    Hi,

    is the primary key of that lookup field contain value? if it is contain value, then this is not an expected value, you should contact Microsoft support for this.

    But, before that, you can check, is there any JS that will trigger on load? if yes, try to disable them , if the issue still exist, contact Microsoft support asap, else you have to debug your JS.

  • smcconnell Profile Picture
    341 on at

    Hi Fun,

    apologies if I've misunderstood the answer, however the issues isn't that the fields don't map when i create a record.  the issue is when i deploy the solution containing the new field mappings i've created, when i open the relationship in the target environment the mappings haven't been created.

  • Alex Fun Wei Jie Profile Picture
    33,628 on at

    Hi,

    I misunderstood your problem. When you deploy the solution, which item did you include inside the solution?

  • smcconnell Profile Picture
    341 on at

    thanks for quick reply.

    the solution contains Entity A and B, solution A and B, and the mappings.

    if i create a new mapping in the source environment and deploy it, it gets created.  however if i delete a mapping in the target environment, then try to deploy that mapping again from the source environment it isn't created.

  • Verified answer
    RaviKashyap Profile Picture
    55,410 Moderator on at

    Hi,

    I think this is because once the component is installed as managed, you can delete it by importing the updated solution. You can refer this blog for more details-

    community.dynamics.com/.../crm-2011-deleting-attributes-entities-relationships-or-optionsets-from-managed-solutions

    Hope this helps.

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…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans