I am new to xrm toolbox
how I can achieve this
so you should have one parent Filter
then two child filter (one with and, the other one with OR)
then add conditions in each filters
<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="true" >
<entity name="documents" >
<attribute name="documentsid" />
<attribute name="name" />
<attribute name="section" />
<attribute name="filetype" />
<attribute name="documentlink" />
<attribute name="createdon" />
<attribute name="assessmentid" />
<attribute name="contractorid" />
<attribute name="uploadeddate" />
<filter type="and" >
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="assessmentid" operator="not-null" />
</filter>
</entity>
</fetch>
<entity name="documents" >
<attribute name="documentsid" />
<attribute name="name" />
<attribute name="section" />
<attribute name="filetype" />
<attribute name="documentlink" />
<attribute name="createdon" />
<attribute name="assessmentid" />
<attribute name="contractorid" />
<attribute name="uploadeddate" />
<filter type="and" >
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="assessmentid" operator="not-null" />
</filter>
</entity>
</fetch>
<filter type="and" >
<filter type="and" >
<condition attribute="statecode" operator="eq" value="0" />
</filter>
<filter type="or" >
<condition attribute="contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="assessmentid" operator="not-null" />
</filter>
</filter>
<filter type="and" >
<condition attribute="statecode" operator="eq" value="0" />
</filter>
<filter type="or" >
<condition attribute="contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="assessmentid" operator="not-null" />
</filter>
</filter>
<filter type="and" >
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="gdit_contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="gdit_assessmentid" operator="not-null" />
<filter type="or">
<condition attribute="FType" operator="eq" value="something" />
</filter>
</filter>
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="gdit_contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="gdit_assessmentid" operator="not-null" />
<filter type="or">
<condition attribute="FType" operator="eq" value="something" />
</filter>
</filter>
<filter type="or" >
<filter type="and" >
<condition attribute="statecode" operator="eq" value="0" />
</filter>
<filter type="and" >
<condition attribute="contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="assessmentid" operator="not-null" />
</filter>
</filter>
<filter type="and" >
<condition attribute="statecode" operator="eq" value="0" />
</filter>
<filter type="and" >
<condition attribute="contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="assessmentid" operator="not-null" />
</filter>
</filter>
here is more what you are after I guess
oh ok I see
so your filter is ok but just add as many Ftype condition as needed
<filter type="and" >
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="gdit_contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="gdit_assessmentid" operator="not-null" />
<filter type="or">
<condition attribute="FType" operator="eq" value="something" />
<condition attribute="FType" operator="eq" value="something1" />
</filter>
</filter>
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="gdit_contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="gdit_assessmentid" operator="not-null" />
<filter type="or">
<condition attribute="FType" operator="eq" value="something" />
<condition attribute="FType" operator="eq" value="something1" />
</filter>
</filter>
I hope this is fine
<filter type="and" >
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="gdit_contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="gdit_assessmentid" operator="not-null" />
<condition attribute="FType" operator="in" >
</condition >
</filter>
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="gdit_contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="gdit_assessmentid" operator="not-null" />
<condition attribute="FType" operator="in" >
</condition >
</filter>
<filter type="and" >
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="gdit_contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="gdit_assessmentid" operator="not-null" />
<condition attribute="FType" operator="in" >
<value>something1</value>
<value>something2</value>
</condition >
</filter>
<condition attribute="statecode" operator="eq" value="0" />
<condition attribute="gdit_contractorid" operator="eq" value="82F2B18C-C42A-E711-8104-5065F38B26A1" />
<condition attribute="gdit_assessmentid" operator="not-null" />
<condition attribute="FType" operator="in" >
<value>something1</value>
<value>something2</value>
</condition >
</filter>
I'm entering a meeting, have a good day
but the "Save View" option is disbaled.
How do I save the view into CRM ?
@rappen hi. Hope your well, trying to create a view with fetchxml. i want to view all resolved cases where an email received has attached to the case after it has been resolved. typical customer behavior of replying to non-reply emails from crm, so the customer complains that nothing is being done but since we don't have visibility as the email attaches to the resolved case. tried to create this with advanced find and fetchxml without success. Any ideas
Hi!
I understand your problem... The hard part here is that you want to compare
I don't see how you can solve this with a query. I think you have to create a workflow that triggers on create email, and then check if regarding case has been resolved. If so, you could either re-open the case, create a task for this email, or something like that.
Makes sense?
I understand your problem... The hard part here is that you want to compare
email.createdon with case.resolutiondate. And FetchXML does not support conditions comparing two field values.I don't see how you can solve this with a query. I think you have to create a workflow that triggers on create email, and then check if regarding case has been resolved. If so, you could either re-open the case, create a task for this email, or something like that.
Makes sense?
