If you run this query it actually executes, so the innards of CRM has support for the RowAggregate on the attribute node.
More precisely the fetch was taken from an out-of-the-box "Active Accounts" view.
<fetch version='1.0' output-format='xml-platform' mapping='logical' >
<entity name='account' >
<attribute name='name' />
<attribute name='address1_city' />
<order attribute='name' descending='false' />
<attribute name='primarycontactid' />
<attribute name='telephone1' />
<filter type='and' >
<condition attribute='statecode' operator='eq' value='0' />
</filter>
<link-entity alias='accountprimarycontactidcontactcontactid' name='contact' from='contactid' to='primarycontactid' link-type='outer' visible='false' >
<attribute name='emailaddress1' />
</link-entity>
<attribute name='accountid' />
</entity>
</fetch>
(Sorry about the delay, I'm currently at eXtreme365 in Dubrovnik)
The FetchType object is created from the FetchXML in this method: https://github.com/Innofactor/FetchXMLBuilder/blob/master/FetchXmlBuilder/DockControls/TreeBuilderControl.cs#L202-L212
The FetchType class is generated from the fetch.xsd schema file provided by Microsoft: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/org-service/fetchxml-schema
I use this cmd file to generate the class from the schema: https://github.com/Innofactor/FetchXMLBuilder/blob/master/FetchXmlBuilder/Resources/XSD%20fetch.cs.cmd
Hope this helps!
In this fetch, the UI complains that "entityname" is invalid in the condition which I believe I see in the example given. Haven't gotten much past that. I see that my filters may need work, but this syntax issues has me stumped
<fetch mapping="logical" version="1.0" distinct="true" output-format="xml-platform" >
<entity name="contact" >
<attribute name="fullname" />
<attribute name="xyz_studentid" />
<attribute name="contactid" />
<filter type="and" >
<condition value="0" attribute="statecode" operator="eq" />
<condition value="1" attribute="xyz_isstudent" operator="eq" />
</filter>
<link-entity name="xyz_enrollment" to="contactid" from="xyz_student" alias="Fut" link-type="outer" />
<link-entity name="xyz_enrollment" to="contactid" from="xyz_student" alias="Prev" >
<filter type="or" >
<filter type="and" >
<condition entityname="Prev" attribute="xyz_code" operator="in" >
<value>{E165DCFC-785B-E711-8119-E0071B669EB1}</value>
<value>{E065DCFC-785B-E711-8119-E0071B669EB1}</value>
</condition>
<condition entityname="Prev" value="802430000" attribute="xyz_enrollmentstatus" operator="eq" />
</filter>
<filter type="and" >
<condition entityname="Fit" attribute="xyz_code" operator="in" >
<value>{EA65DCFC-785B-E711-8119-E0071B669EB1}</value>
<value>{E865DCFC-785B-E711-8119-E0071B669EB1}</value>
<value>{E665DCFC-785B-E711-8119-E0071B669EB1}</value>
<value>{E365DCFC-785B-E711-8119-E0071B669EB1}</value>
</condition>
<condition entityname="Fut" value="802430000" attribute="xyz_enrollmentstatus" operator="eq" />
</filter>
</filter>
</link-entity>
</entity>
</fetch>
Can anyone help with a quick FetchXML question...
<fetch top="1" >
<entity name="systemuser" >
<attribute name="systemuserid" />
<attribute name="businessunitid" />
</entity>
</fetch>
Nice'n'easy, yeah? A couple of attributes from the first systemuser record...
<resultset morerecords="0" >
<result>
<systemuserid>{DC650CAB-C453-E611-941D-00155D731475}</systemuserid>
<businessunitid dsc="" name="MRWA" type="10" >{6BB9164F-865F-E211-953C-02BFAC106E42}</businessunitid>
</result>
</resultset>
Is there any way I can suppress the @name, @dsc, @type attributes of businessunitid from being sent by the FetchXML? In my "real" use cases, i'm using FetchXML to populate a datamart and the sending across of this type of lookup data for all my rows is wasting bandwidth!
