You’re offline. This is a read only version of the page.
33
Hi community,
I want to use some different virtual entities/tables from D365 F&O for a PowerApp I am designing.
Previously I was using a standard entity, but in D365 I've got a warning, that some fields are disabled by a configuration key.
And in Dataverse - sometimes - I get the error "An error has occurred. Something went wrong. Please try again. 10:17:11 - Paging is not supported for queries with temporary tables."
In Microsoft FAQs I've found the following: " I'm getting an error that paging is not supported. How do I work around this?
When running a query against a virtual entity you may get an error response with the message, "Paging is not supported for queries with temporary tables." This is by design. The error will be returned if the query includes any temporary tables. If this error is returned, you will need to determine which temporary tables are included in the query, and then modify the query to exclude the temporary table. Disabled configuration keys may also cause this error. The default virtual entities provided in the Dynamics 365 ERP Virtual Entities solution do not include temporary tables when all configurations are enabled. However, when a configuration key is not enabled for the backing table of an entity, the physical table is replaced with a temporary table so the system doesn't need to be recompiled for schema changes. This results in a temporary table included in the virtual entity query. In these scenarios the solution is to enable the associated configuration key to resolve the error.
For additional information about the impact of configuration keys on data entities, see Configuration keys and data entities."
We don't want to enable the configuration keys, that's why we have developed a new entity, without the fields. But after designing a view and trying to use this view in the canvas app, I am getting the same error again for new customized entity. Has someone maybe experienced the same situation or has an idea how to handle this?
BR Franziska
In the end the recommended workaround of Microsoft was to develop custom entities from scratch with only the needed fields. Our first tries of developing a custom entity failed, because we had only removed the problematic fields and we probably missed some problematic datasources, which should have been removed as well.
I have the same issue.
#1
stampcoin
17
#2
mmbr1606
15
Super User 2025 Season 1
#3
ankit_singhal
11
Super User 2025 Season 1
Share
Report
All responses (
Answers (
