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) / LOOKUP CONTROL ERROR a...
Microsoft Dynamics CRM (Archived)

LOOKUP CONTROL ERROR after CRM Update to version 8.2.5.0004

(0) ShareShare
ReportReport
Posted on by bernhards 423

We get this error after the update to the latest 8 version. The error appears in the email entity, when someone tried to add the email to the queue. I also encoutered this error on the test machine that has the same version. What I tried:

  • Deactivated all Plugins for the Entities queueitem, email
  • Disabled the Form JS logic

It seems like the error only effects the webinterface and the E-mail got still added to the queue. Has anybody else encountered this problem? I'm close to report this as bug to MS. The error appears in Chrome and IE.

emailcontrolerror.png

*This post is locked for comments

  • Avinashmane25 Profile Picture
    Avinashmane25 30 on at

    you may be trying to add those record which is not entity type of lookup filters.

    first, check the lookup filters entities and try to add the record  

  • Verified answer
    Daniel Wikell Profile Picture
    Daniel Wikell 2,360 on at

    Hi

    There is a known issue from this update with the "from"-field on the email entity.

    You can fix this by editing the customization-xml for the email entity:

    1. Create a solution

    2. Add the "from" field from the existing Email entity

    3. Export the solution as unmanaged

    4. Unzip the file "customizations.xml"

    5. Edit the file and add the missing lookup types according to my attached image

    6. Re-add the modified customizations.xml file to the zip.

    7. Import the zip solution into CRM and publish all changes

    email_5F00_lookuptypes_5F00_missing.png

  • bernhards Profile Picture
    bernhards 423 on at

    Hello,

    thanks for your quick answer. I exported the solution now. The values did look ok, I would say:

    solutionlookup.png

  • bernhards Profile Picture
    bernhards 423 on at

    Ok, I just tried to remove the LookupTypes -> import the solution -> add it again, and import again. This did not fix the issue.

  • bernhards Profile Picture
    bernhards 423 on at

    Thanks for your answer but I don't understand what you mean. The error appears for a received email, when we try to add that to the queue. The same e-mail also failed to automatically generate a queueitem.

  • Daniel Wikell Profile Picture
    Daniel Wikell 2,360 on at

    Alright so that probably means that there could be more fields affected by the same upgrade bug. The from field was the culprit in our case so that's why I assumed it to be the same here.

    The error is the same, in that the form xml is corrupt and is missing a lookuptype in one of the fields.

    Kindly repeat the steps above but add the entire email entity instead of just the from field.

    Scan each field of type lookup or type partylist and see if you can locate which other field is having this problem.

    The lookup types to add in my posted solution is specific to the from field since the from field can be from either a User or a Queue. If you are missing the lookuptypes on another field you'll have to check which types of entities are valid for that field and adjust the lookuptype codes accordingly.

  • bernhards Profile Picture
    bernhards 423 on at

    Thanks for your reply. I added all lookups and partylists now in the solution and exported them. The exported solution is missing some fields "createdon", "createdby",.. but I hope this is the normal behavior.  But I'm missing a CRM XML that is not comprimized. Do partylists need a LookupType entry?

    For the following fields the LookupType entry is missing: bcc, regardingobjectid, to

  • Suggested answer
    bernhards Profile Picture
    bernhards 423 on at

    Ok, I fixed the issue. It was coming from the "from" field. I compared the metadata with the bbc field and found out that it is missing the TypeCode to the contact. Here is what I added to it:

                  <LookupTypes>
                <LookupType id="00000000-0000-0000-0000-000000000000">9700</LookupType>
                <LookupType id="00000000-0000-0000-0000-000000000000">8</LookupType>
                <LookupType id="00000000-0000-0000-0000-000000000000">2</LookupType>
                <LookupType id="00000000-0000-0000-0000-000000000000">1</LookupType>
                <LookupType id="00000000-0000-0000-0000-000000000000">4</LookupType>
                <LookupType id="00000000-0000-0000-0000-000000000000">4000</LookupType>
                <LookupType id="00000000-0000-0000-0000-000000000000">2020</LookupType>
                <LookupType id="00000000-0000-0000-0000-000000000000">9953</LookupType>
              </LookupTypes>


    Imported the solution again, and finally it is fixed! In my case the missing TypeCode (2) to the contact was causing this issue.

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
ScottDurow Profile Picture

ScottDurow 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans