A .NET service using the Organization service must return the total estimated revenue of open opportunities grouped by owner, computed by Dataverse on the server rather than by downloading every opportunity row. Which approach meets the requirement?
Select an answer to reveal the explanation.
Short Explanation
Distinct removes duplicate rows; it doesn't add anything up. When you need sums by owner done on the server, you want an aggregate query with a sum and a groupby. The trap is anything that leaves the math to your code.
Full Explanation
FetchXML supports server-side aggregation. Setting aggregate to true on the fetch element and defining one attribute with aggregate set to sum on estimatedvalue and another with groupby set to true on ownerid makes Dataverse compute one total per owner and return only those grouped rows. Filtering on the open state keeps the scope to open opportunities. Because the calculation happens in the database, the service transfers a handful of rows rather than every opportunity, which satisfies the requirement. Setting Distinct on a QueryExpression removes duplicate rows from the result based on the selected columns; it does not calculate totals, so rows with different revenue values would all still be returned. A FetchXML query with distinct set to true on ownerid returns a list of owners but no totals, and summing in the service would require downloading the revenue values separately, which is exactly what the requirement rules out. TopCount limits the total number of rows returned by the query, not the number per owner, and it does not produce sums. Exam caveat: aggregate queries are subject to a record limit on the rows aggregated, so very large datasets can return an aggregate limit error and may need narrower filters or other approaches. Operational check: execute the FetchXML through RetrieveMultiple and confirm the result contains one row per owner with an aliased sum value.