FetchXML with Web API Fails When Using Multiple link-entity Elements

(1) Share

Report

Posted on by CU26111754-0

I am using FetchXML queries with the Web API in Power Pages to retrieve data with multiple link-entity elements. According to the documentation, FetchXML supports up to 10 link-entity elements. However, when I include more than 1 link-entity in my FetchXML query, I receive a "Web API is not available" or similar error. The query works fine with a single link-entity, but adding more causes it to fail.

var fetchXml = `<fetch count="10" page="1" returntotalrecordcount="true">
  <entity name="primary_entity">
    <attribute name="recordid" />
    <link-entity name="related_entity_1" from="id" to="related_id_1" alias="alias1" link-type="outer">
      <attribute name="field1" />
    </link-entity>
    <link-entity name="related_entity_2" from="id" to="related_id_2" alias="alias2" link-type="outer">
      <attribute name="field2" />
    </link-entity>
  </entity>
</fetch>`;
$.ajax({
    type: "GET",
    url: "/_api/primary_entities?fetchXml=" + encodeURIComponent(fetchXml),
    success: function (res) {
        console.log(res);
    },
    error: function (xhr) {
        console.error(xhr.responseText);
    }
});

Here it works for when use one link-entity but for two it states web api is not available.

Is there a specific limitation when using multiple link-entity elements in FetchXML through the Web API?

Categories:

General

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Fubar 8,112 Super User 2025 Season 2 on at

Like (0)

Report

FetchXML with Web API Fails When Using Multiple link-entity Elements

Not sure if this is the issue or not, but there is a known issue with complex queries when the system adds the extra pieces for the Table Permissions (i.e. it adjusts your query to add the permissions scope like account and contact scope).

https://learn.microsoft.com/en-us/power-pages/configure/web-api-overview#known-issues

You can test this by setting table permissions to Global as global does not alter the query.

My other thought would be that it may not like it as they are both Outer joins - but if thats the case may be more of a bug..

Was this reply helpful? Yes No
CU26111754-0 30 on at

Like (1)

Report

FetchXML with Web API Fails When Using Multiple link-entity Elements

I have created the xml using fetchxmlbuilder. From this fetch if i remove one entity then its work fine.

Also the error “Web Api is not available” i encountered come when site settings is not available but in this i have ensure that they are created.

Was this reply helpful? Yes No
bscarlavai33 632 Super User 2025 Season 2 on at

Like (1)

Report

FetchXML with Web API Fails When Using Multiple link-entity Elements

That should be fine. Maybe there is some sort of syntax issue.

Are you able to run your Fetch XML using XrmToolBox and see if it returns a result? https://www.xrmtoolbox.com/plugins/Cinteros.Xrm.FetchXmlBuilder/

Was this reply helpful? Yes No

Community site session details

FetchXML with Web API Fails When Using Multiple link-entity Elements

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

MS.Ragavendar – Community Spotlight

Congratulations to the August Top 10 Community Leaders!

Leaderboard > Power Pages

Featured topics

Product updates

Community site session details

FetchXML with Web API Fails When Using Multiple link-entity Elements

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

MS.Ragavendar – Community Spotlight

Congratulations to the August Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Power Pages

Featured topics

Product updates