I am creating an app from a data source with 4098 records. Is there any limitation of record to that the data source can have a certain number of records only. Is there any way this can be solved?
I began encountering this same error today after updating Project Service Automation to 3.x. Specifically, I encounter this error when attempting to connect to the msdyn_project entity.
Could you please share a bit more about the data source used within your app? Is it a Dynamics 365 Entity?
Currently, I could not reproduce your issue on my side.
I have found similar issue with you, please check the following thread:
I think it is a known limit that the Saved queries, charts, and visualizations can have a maximum of 10 unique calculated fields.
More details about the Calculated fields limits, please check the following article:
Please check if the number of unique calculated fields in your Dynamics 365 Entity is more than 10.
Yes, the calculated fields are more than 10. The app is working on the dev environment but not in the production. I won't be able to share my datasource in the forum. Is it any way I can talk share the issue with someone is private?
In my case the number of calculated fields exceeds 10 in both my production and sandbox environments. However, the problem only occurs in the sandbox environment after updating Project Service Automation to 3.0.
I would also point out that this also affect Power BI queries and Microsoft Flow references. Queries to the msdyn_project entity now return the same error message of "Number of calculated fields in query exceeded maximum limit of 10."
Since the ShowColumns function appears to be non-delegable, are there other methods for specificy the return of only certain attributes - in the same way I would normally call the web api for D365?
Yes. Actually two solutions.
One, was that it just fixed itself. I suspect there must have been a bug in the API that got fixed in a later update.
Two - and this was my temporay workaround until it got fixed - was to create a custom connector in PowerApps to D365. With that I could specifify only certain field to come in to the app and didn't hit the 10 field limit. I followed thttps://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/walkthrough-register-dyna... , https://docs.microsoft.com/en-us/connectors/custom-connectors/define-blank, and https://docs.microsoft.com/en-us/connectors/custom-connectors/define-postman-collection. It was an educational experience.
Thanks for the feedback, @r529 .
Using a custom connector seems a bit too much for me. I managed to get rid of some calculated fields one or another way to get down to 10 - but I would rather have avoided that.
I don't know if it is a bug or not - but having a limit of calculated fields related to queries in a Production instance and not in Sandbox is really not a nice surprise to get close to go-live