Reports

(2) Share

Report

Posted on by CU29080825-0

An error occurred during report processing
Qure excutin failed for dataset ClosedRefferalsReport
The entity name doesnot exist please specify an existing name the entity servicerequest
Cannot be found specify a valid and try again
The entity with a name= servicerequest with namemapping=’Logical’ was not found in the MetadataCache.LazyDynamicMetadataCache with version 17000151 and timestamp 17000151

Categories:

Dynamics 365 general

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Abdul Wahab 12,119 Moderator on at

Like (0)

Report

Reports

Error Breakdown

“The entity with a name= servicerequest … was not found in the MetadataCache”
This is coming from SQL Server Reporting Services (SSRS) / FetchXML-based report in Dynamics 365 CE (CRM).
It means the report’s dataset is pointing to an entity (table) called servicerequest.
But in your Dataverse environment, no table with logical name = servicerequest exists.

Common Causes
Entity/Table renamed or removed
Maybe servicerequest was renamed in the solution (e.g., now it’s msdyn_servicerequest or a custom prefix).
Different Environment
Report was built in Dev/Test where the entity existed, but in Production it doesn’t.
Solution Upgrade
If you upgraded a managed solution, the entity might have been deprecated or replaced.
Caching / Metadata mismatch
Sometimes SSRS or the ReportServer keeps old metadata.

Fixes / Workarounds
1. Check actual entity name in Dataverse

Go to Advanced Settings → Customizations → Customize the System → Entities (or Tables in modern UI).

Look for the logical name of your table.

Verify if servicerequest exists or if it’s named differently (e.g., incident, new_servicerequest).

2. Update the report’s FetchXML

If the entity has a different logical name, open the report’s RDL file.

Update the dataset’s FetchXML query, replacing servicerequest with the actual logical name.

3. Confirm with XrmToolBox

Use Metadata Browser in XrmToolBox.

Search for servicerequest → if not found, identify the correct entity.

4. Re-deploy report

After fixing the dataset, re-upload the report to CRM.

5. If it’s just cache (rare case)

Restart the SSRS service (SQL Server Reporting Services).

Clear metadata cache.

Abdul Wahab
Direct: +923323281237
Email: abdulwahabubit@outlook.com
LinkedIn: https://www.linkedin.com/in/abdul-wahab-a5b8b011a/
Twitter: https://twitter.com/Abdulwahabubit
GitHub: https://github.com/AbdulWahabWarind
YouTube: https://www.youtube.com/channel/UCBjgLqLK_2kU-3bwo4McrTw

Was this reply helpful? Yes No