Closed Roland80 closed 1 year ago
When you convert a FetchXML to Power Automate parameters and a filter contains a lookup to a specific record, the GUID is missing single quotes. Example FetchXML:
<fetch> <entity name="account"> <filter> <condition attribute="accountid" operator="eq" value="3fee3d59-68c9-ed11-b597-0022489b41c4" uitype="account" /> </filter> </entity> </fetch>
Example Filter parameter: (accountid eq 3fee3d59-68c9-ed11-b597-0022489b41c4)
(accountid eq 3fee3d59-68c9-ed11-b597-0022489b41c4)
The List rows action expects there to be single quotes around the GUID, as it's a string-type column rather than an integer.
Will look into this issue. 👍
Sorry, that shouldn’t have auto-closed just yet. Fix is done in the upstream package, will get a PR shortly to include it in FXB
Fixed in submodule by @MarkMpn.
When you convert a FetchXML to Power Automate parameters and a filter contains a lookup to a specific record, the GUID is missing single quotes. Example FetchXML:
Example Filter parameter:
(accountid eq 3fee3d59-68c9-ed11-b597-0022489b41c4)
The List rows action expects there to be single quotes around the GUID, as it's a string-type column rather than an integer.