What is wrong with this query regarding DISTINCT field retrieval

(0) Share

Report

Posted on by Community Member Microsoft Employee

I got the following response from odata rest API when using distinct, so that I can pull the unique values of a specific column within the contact entity type.

api/data/v8.0/contacts?fetchXml=<fetch mapping="logical" distinct="true" version="1.0">

'select' and 'expand' cannot be both null or empty."

Does any one know how to get unique values a specific columns in LCMS 2016 web API?

Thanks in advance

*This post is locked for comments

All responses (4)

Answers (0)

Community Member Microsoft Employee on at

Like (0)

Report

RE: What is wrong with this query regarding DISTINCT field retrieval

In FetchXML query you should have at least one attribute from entity which is not null to resolve this issue like Id.

<attribute name='contactid' />

if that works mark as verified.

Thank you,

Dhruv.

Microsoft Certified Professional
Nirmal_CRM 175 on at

Like (0)

Report

RE: What is wrong with this query regarding DISTINCT field retrieval

Hi Mohammad,

Were you able to solve this issue ? If yes, could you please let me know how ?

Regards,

Nirmal
Community Member Microsoft Employee on at

Like (0)

Report

RE: What is wrong with this query regarding DISTINCT field retrieval

Thank you Alex. Same here no documentation about this limitation.
ashlega 34,475 on at

Like (0)

Report

RE: What is wrong with this query regarding DISTINCT field retrieval

Hi Mohammed,

exactly the same request works fine in 365, so it might be some sort of limitation in 2016, but I could not find anything related to it here:

msdn.microsoft.com/.../mt628816.aspx