SBX - Search With Button

SBX - Forum Post Title

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

Microsoft Dynamics CRM Forum

Chris Vine asked a question on 7 Mar 2017 10:40 PM
My Badges

Question Status

Suggested Answer

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?

 

Reply
Mohd Saad Akhtar responded on 7 Mar 2017 10:55 PM
My Badges
Suggested Answer

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.

Reply
EmployeeOcta responded on 7 Mar 2017 11:23 PM
My Badges

Hello Chris Vine,

I am agree with Saad.

Reply
Mike Smith responded on 6 Apr 2017 12:29 AM
My Badges

Chris,

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

Reply
Stanley Lai responded on 7 Aug 2017 12:33 AM
My Badges

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/

Reply
Mohd Saad Akhtar responded on 7 Mar 2017 10:55 PM
My Badges
Suggested Answer

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.

Reply

SBX - Two Col Forum

SBX - Migrated JS