Hey Team,
I have a few questions around the Dynamics CRM Connector for flow. - Do you have any documentation or info relating to how far the results for the ODATA filters have been implemented?
(e.g. Will it recognise this as a collection?
Cheers!
Solved! Go to Solution.
Hi Ojward,
It seems that ODATA filter query function has not been implemented yet, as flow is being improved and developed, you could submit a flow idea at “Flow Ideas”.
The link of "Flow Ideas" is:
https://powerusers.microsoft.com/t5/Flow-Ideas/Add-Branching-Logic-to-Flow/idi-p/1600
Best regards,
Mabel Mao
Hi Ojward,
It seems that ODATA filter query function has not been implemented yet, as flow is being improved and developed, you could submit a flow idea at “Flow Ideas”.
The link of "Flow Ideas" is:
https://powerusers.microsoft.com/t5/Flow-Ideas/Add-Branching-Logic-to-Flow/idi-p/1600
Best regards,
Mabel Mao
Hi, could you provide an example of a filter? I'm having some real issues and there is nothing online.
Same issue for me here. It is really frustrating having no samples about the odata filtering.
I tried to get a filter running for a small xrm sample with a new entity registrations.
Nevertheless I get this error:
A binary operator with incompatible types was detected. Found operand types 'Microsoft.Dynamics.CRM.new_event' and 'Edm.Guid' for operator kind 'Equal'.\",\r\n \"innererror\": {\r\n \"message\": \"A binary operator with incompatible types was detected.
This leads me to the question, how can I filter with guids? Is there an option for casting?
Hi Tofi,
I actually figured it out in my case. I had to use single quotes i.e.
Address1_City eq 'Redmond'
I don't know if this will help you in your case.
Hi trevor,
Thanks for your response :).
In case of filtering for a guid it does not help :(. Nevertheless you are right by filtering for string values it is correct to use single quotes.
var query = "/api/data/v8.2/customeraddresses?$select=line1,line2,line3,stateorprovince,postalcode,city,country,county&$filter=parentid_account/accountid eq " + AccountId + " and addressnumber eq 1";
worked for me
_new_fieldnameid_value eq cc0f7474-cac6-e611-80ee-5065f38b03d1