Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Export Unmanaged Solut...
Microsoft Dynamics CRM (Archived)

Export Unmanaged Solution - Error Message 'The specified field does not exist in Microsoft Dynamics 365'

(0) ShareShare
ReportReport
Posted on by Chris Vine

Hi All,

Has anyone seen when exporting an 'unmanaged solution' the following error

Query Builder Error
The specified field does not exist in Microsoft Dynamics 365.
Show technical details

The download log file doesn't enable so I cannot download more information about the error.

Clicking on the Show technical details

The specified field does not exist in Microsoft Dynamics 365.

I've added all 'required components' manually on all entities and I still get the error. Any ideas?

 

*This post is locked for comments

  • Stanley Lai Profile Picture
    Stanley Lai 295 on at
    RE: Export Unmanaged Solution - Error Message 'The specified field does not exist in Microsoft Dynamics 365'

    Refer to this article to use the SDK to remove the offending fields from the solution:

    https://bettercrm.blog/2017/07/17/query-builder-error-when-exporting-solution-in-dynamics-365/

  • Seattle CRM Profile Picture
    Seattle CRM 45 on at
    RE: Export Unmanaged Solution - Error Message 'The specified field does not exist in Microsoft Dynamics 365'

    Chris,

    Are you still experiencing this issue? I'm curious to what your solution was if resolved.

  • EmployeeOcta Profile Picture
    EmployeeOcta on at
    RE: Export Unmanaged Solution - Error Message 'The specified field does not exist in Microsoft Dynamics 365'

    Hello Chris Vine,

    I am agree with Saad.

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Export Unmanaged Solution - Error Message 'The specified field does not exist in Microsoft Dynamics 365'

    Have you used any fetchxml in the entities of the solution. If yes, Then check if fetchxml is correct. I think Fetchxml is using some field which is not present in the system.

    I would suggest you to create a new solution and add entities one by one and export the solution  and see if the error comes. This will help to isolate from which entity  issue is coming from.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans