Filter by checking two different option setsįilter query= optionsetfieldname1 eq optionsetnumericvalue1 or optionsetfieldname2 eq optionsetnumericvalue2Į.g. if I have to filter where ‘Topic’ contains ‘New’ and ‘Interested’ my filter would be contains(subject,’new’) and contains(subject,’interested’)ĩ.Filter an option set checking two or more valuesġ0. Contains with ‘AND’ on same text fieldįilter query= contains(textfield1name,’value1′) and contains(textfield1name,’value2′)Į.g. if I have to filter where ‘Rating’ contains either ‘Hot’ or ‘Warm’ data my filter would be leadqualitycode eq 1 or leadqualitycode eq 2Ĩ. if I have to filter where ‘Job title’ contains ‘Manager’ or ‘Consultant’ my filter would be contains(jobtitle,’manager’) or contains(jobtitle,’consultant’)Į.g. if I have to filter lead’s with rating ‘Hot’ (value =1) my filter would be leadqualitycode ne 1įilter query= contains(field1name,’value1′) or contains(field1name,’value2′)įilter query= optionsetfieldname1 eq optionsetnumericvalue1 or optionsetfieldname1 eq optionsetnumericvalue2Į.g. Note: As per my understanding, you can’t check option set label in ODATA filter but you can in filter array.įilter query= optionsetfieldschemaname ne optionsetnumericvalueĮ.g.
if I have to filter lead’s with rating ‘Hot’ (value =1) my filter would be leadqualitycode eq 1 This one is for option set fields like Rating, Lead Source, Industry, Type etc.įilter query= optionsetfieldschemaname eq optionsetnumericvalueĮ.g.
if I have to filter where ‘Rating’ does not contains data or is blank my filter would be leadqualitycode eq null if I have to filter where ‘Job title’ does not contains data or is blank my filter would be jobtitle eq nullĮ.g. if I have to filter where ‘Rating’ contains data or is not blank my filter would be leadqualitycode ne nullįilter query= textfieldschemaname eq nullįilter query= optionsetfieldschemaname eq nullĮ.g. if I have to filter where ‘Job title’ contains data or is not blank my filter would be jobtitle ne nullĮ.g. This one is for both text and option set fieldsįilter query= textfieldschemaname ne nullįilter query= optionsetfieldschemaname ne nullĮ.g. if I have to check that the ‘Subject/Topic’ of a Lead record does not contains ‘New’ in it my filter would be not contains(subject,’new’) if I have to check whether the ‘Subject/Topic’ of a Lead record contains ‘New’ in it my filter would be contains(subject,’new’)įilter query= not contains(textfieldschemaname,’value’)Į.g. This one is for text fields like Topic, Subject, Phone, City, Street 1 etc.įilter query= contains(textfieldschemaname,’value’)Į.g. Sequence: In most queries the sequence of the components remains like ‘fieldname operator fieldvalue’ but in some cases like contains/does not contains sequence and structure changes to ‘operator(fieldname,’fieldvalue’)’ This post will talk about the following two filter types you need while building a flow:īefore we commence with the filters, i will try to explain you the components of ODATA filter query: 1.Field or Column Name But here we are moving forward and learning together to be able to work with Flows.
Most of this bottleneck is because as non-technical people we don’t what ‘ODATA Query’ is?Ĭoming from Dynamics 365 background, I never required such filters for native workflows of D365. I am sure as a Business user or a functional consultant, you must have had a situation where you needed someone technical to complete your flow. We all know how easy it is to create a flow ( Watch #TGIF Episode 2 here, if not already). This blog is to help fellow consultants to start their journey on Power Automate.
0 kommentar(er)
