Web Api queries using fetchXml and aliases suddenly stopped working

(0) Share

Report

Posted on by khaack

Hi all,

We have some queries against the D365 v9.0 api that use fetchXml that have suddenly stopped working today or over the weekend without any code changes. The fetchXml joins the Account table to itself using aliases, and the aliases are used in the '$select' portion of the api call as well, but today we're getting the error:
"Can not resolve the segment identifier 'aliasname.fieldname' in query option". Anyone know what might be going on? Was something changed on the back-end that would break this?

For example, the fetchXML may look something like this:

and the api call would look something like this:

https://xxx.dynamics.com/api/data/V9.0/accounts?$select=accountid,name,parent.name,parent.accountid,grandparent.name,grandparent.accountid&fetchXml=[data from above]

and it will fail saying:
"Can not resolve the segment identifier 'parent.name' in query option"

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Pradeep Rai 5,489 Moderator on at

Like (0)

Report
Copy link

Link copied!
Hi,

Above fetchXML looks good because when i run this on FETCHXML Builder in XRMToolbox then it shows the proper value.

Now regarding Odata query: odata query does not support multiple link entity as shown in below screenshot:

So, instead of Odata query please use Xrm.WebAPI,retrieveMultipleRecords as shown below:

Code:
var fetchXml = "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""; Xrm.WebApi.retrieveMultipleRecords("account", "?fetchXml=" fetchXml).then( function success(result) { for (var i = 0; i < result.entities.length; i ) { console.log(result.entities[i]); } // perform additional operations on retrieved records }, function (error) { console.log(error.message); // handle error conditions } );

Hope this helps.

Thanks,
Pradeep.

Please mark this as VERIFIED, if it helps.

Was this reply helpful? Yes No