Power Community

Power Community

Dealing with Query Builder Errors when exporting solution in Dynamics 365

Query Builder Error

The specified field does not exist in Microsoft Dynamics 365. If you contact support, please provide the technical details.


If you are experiencing a Query Builder errors on exporting your Dynamics 365 Managed Solutions, the causes are likely an orphaned record in the database after deleting an attribute that was not removed by the system. I have been experiencing this more frequently as of late, and can be resolved by removing the offending attribute with a webapi request. In order to identify the orphaned attribute you will need to download the error log, providing the guid of the offending attribute as shown below;


The attribute with AttributeId = ‘741b7baa-4560-4615-b0b8-09f3f25fb291’ was not found in the MetadataCache. MetadataCacheDetails: ProviderType=Dynamic, StandardCache=True, IsLoadedInStagedContext = False, Timestamp=4651630, MinActiveRowVersion=4651630

Please proceed with caution, only remove this attribute if you believe your query Builder error occurred after deleting attributes from your schema. You should open a support request if you are encountering orphaned records, Once you have confirmed you can complete the following steps to remove the orphaned record.

Query Builder Error – The attribute with AttributeId = ‘bd7fc97b-8b3d-4f66-ba8e-0df23bf391d0’ was not found in the Metadatacache

1) Install Postman Extension for Chrome

2) Install Postman Interceptor Extension for Chrome

3) Enable the Postman Intercepted as shown below;


Open another Chrome browser and login to Dynamics, this will help Postman to authenticate with the Dynamics 365 API in order to easily  perform your query

Now your ready to submit your remove solution component request as shown below;

Post: Https://365saturday.crm.dynamics.com/api/data/v9.1/RemoveSolutionComponent

Body of the Request should contain the solution componentid as shown below;


“SolutionComponent” : {

“solutioncomponentid”: “bd7fc97b-8b3d-4f66-ba8e-0df23bf391d0”

“ComponentType” :2 ,

“SolutionUniqueName” :”RazDynamics”

Set The Headers;

OData-MaxVersion            4.0

OData-Version                   4.0

Content-Type                     application/json


The Response shown above shows the request was performed successfully

Now when you try exporting your solution you will no longer receive the Query Builder Error

- Advertisement -spot_img


Please enter your comment!
Please enter your name here

- Advertisement - Advertisement

Latest News

WhatsApp + Dynamics 365 CRM: Your Secret to Christmas Marketing Success

The holiday season is a busy time for businesses, and Christmas🎄 is no exception. With so much competition for...

More Articles Like This

- Advertisement -spot_img