Trouble with Dynamics Get List with ODATA query

[MD789]

I'm trying to use Flow to extract an email address from the body of a calendar event, identify the matching client, and create a new appointment record in Dynamics under that client's account. I managed to parse the calendar object and am able to extract the email address. However, I can't seem to make "List Records" to accept my ODATA query. It works if I type a specific email address between single quotes. However, when I use the string function (either inside the query or as dynamic content defined by a previous Compose step) I get no results. If I don't use single quotes around the dynamic content then I get an error. I spent several hours on this and couldn't make it work, would really appreciate any help I can get at this point.

[v-bacao-msft]

Hi @MD789,

Could you provide the details of the email address from the body of a calendar event?

Could you provide details of  substring() function and output of it?

I did a simple test on my side, although I don't know how you extract the email address from the body, but as long as it is a standard email address, it should not be the cause of this issue.

I think you could test from these aspects, you may know the cause of the problem.

1. First, the content format filled in Filter Query is roughly similar to: emailaddress1 eq ‘Dynamic content’, single quotes must be added, otherwise it does not meet the specifications.

Please make sure that the content format enclosed in single quotes is the correct message format, and there are no additional symbols, such as semicolons.

The content of the correct Filter Query output should look like this:

2.Please make sure that there is a matching emailaddress1 in your Entity, otherwise there will be no value output even if the Flow configuration is correct.

Or you can use Filter Query first to determine whether the emailaddress1 contains a matching email, or it may be another field.

This is my simple test and it works fine.

Please take a try and let me know if issue still exist.

Best Regards,

Barry

[MD789 · Accepted solution]

Thank you for the detailed reply. The field is there and there were single quotes around the function. I eventually figured out the issue: The single quotes should NOT be added after the function is inserted into the query. Instead, I needed to type two single quotes without any space between them, then place the cursor between the quotes and then insert the function. Now it works!