Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Odata queries from our power app fails when listing related virtual entities with the message: "code":"0x80040224","message":"Invalid URI: The Uri string is too long.".
We are using the Microsoft.XRM.DataProvider.OData.V4.Plugins so the virtual entities can be resolved and shown in the power app.
We have a table in the power app where each row is related to N Virtual entities in another system and there is a form that lists the N virtual entities for a given row. It work fine when there are a few virtual entities but it quickly falls apart as the number grows.
It makes sense that the Uri would become too long if it puts all the Uids from the N:N relation in the query string to enable the other system to filter and page the virtual entities. All that is needed is to POST the query instead. The Odata endpoint that is queried for the virtual entities supports POST as well as GET but I don't see how I can get my power app to POST it instead.
Hello, you can check the URI because URI has a max length. For large chunks of data is recommended to send it in JSON format.
Community Support Team - Esteban
If this Post helps, then please consider Accept as solution to help the other members find it more quickly.
Yeah, I know the url gets too long but I didn't write the OData data provider plugin which is maknig the query, I just wrote the service it is trying to send the query to. And the query will become massive, there is no way around that, so putting it in the url makes no sense. I just want the plugin to POST the query instead.
I really don't want to have to write my own OData dataprovider plugin.
Business Applications communities