Solved: Azure Logic Apps to D365 F&O flow results in different data type in D365 compared to Logic Apps

Question

Solved: Azure Logic Apps to D365 F&O flow results in different data type in D365 compared to Logic Apps

Jun Ting Ho 141

My team is trying to use Azure Logic Apps to List Items Present in a Table in Dynamics 365 Finance & Operations using filterQuery. However, for some of the filter queries, we encounter errors where the data type in D365 is different from the one in Logic Apps, resulting in incompatible types. The fields throwing errors have data types in D365 "enum" and "bool" respectively. Is there a simple way to resolve this error?

Accepted answer

1 additional answer

Your answer

Answer 1

Leo Erlandsson 1,661

Hi,

Some people are reporting success on filtering on Microsoft.Dynamics.DataEntities.NoYes columns.

Could you please provide what your query looks like?

I've seen some reporting that e.g. Column eq 1 works.
And some reporting that e.g.
Column eq Microsoft.Dynamics.DataEntities.NoYes’Yes’

works.

Please see:
https://erpcoder.blog/2021/02/08/filter-on-noyes-field-in-dynamics-365-flow-connector/

Br,
Leo

Maria Lee 26 Reputation points

2021-03-15T15:43:01.917+00:00

Hi @Leo Erlandsson , thank you so much for reaching out with your suggestion and I will give it a go.

For more context, our current requirement is that the filterquery is dynamic , so what I am doing is appending continuously all required filters to a string in such a manner using a loop:

I'm currently trying to think of a way to append the syntax in the image above such that the Microsoft.Dynamics.DataEntities.NoYes requirement (for bool values) and Microsoft.Dynamics.DataEntities.<fieldName> requirements can be passed through the Filter Query for D365.

Please let me know if you have a better solution, thanks!

Edit: It works and the problem has been solved, thank you very much
MayankBargali-MSFT 70,941 Reputation points Moderator

2021-03-16T04:46:51.907+00:00

@Maria Lee The above looks good.

Answer 2

MayankBargali-MSFT 70,941 Moderator

Hi @Jun Ting Ho

As per the error message looks like your filter query has a filter on the column of Microsoft.Dynamics.DataEntities.NoYes type and another column of string type.
You cannot filter on the NoYes type as per the error message. As per the connector action, List items present in table the ODATA filter query restricts the entries returned (e.g. stringColumn eq 'string' OR numberColumn lt 123).

Maria Lee 26 Reputation points

2021-03-15T13:44:16.897+00:00

Hi @MayankBargali-MSFT

I am @Jun Ting Ho 's teammate. I would like to ask, in that case, is there a method to accomplish either:
(a) data conversion from edm.string to Microsoft.Dynamics.DataEntities.NoYes, or
(b) any other workaround that I could take in the edm.string into the filter query such that I would bypass the error message shown above?

Thank you!
MayankBargali-MSFT 70,941 Reputation points Moderator

2021-03-16T04:44:54.68+00:00

@Maria Lee Thanks for sharing the details.
You need to filter with 'yourcolumn' eq Microsoft.Dynamics.DataEntities.NoYes'yourvaluecomparion No or Yes'

Share via

Solved: Azure Logic Apps to D365 F&O flow results in different data type in D365 compared to Logic Apps

1 additional answer

Your answer