XML working in FetchXML Builder but flow fails in power automate

(0) Share

Report

Posted on by louisa lane

200

I'm trying to build a schedule flow to send an email when an estimated close date is within the next 14 days. The XML works fine and pulls through the correct data in Fetch XML Builder but doesn't work in the power automate schedule flow. I've used the XML from the view i want to look at in Dynamics and it shows the correct opportunities in the builder so not sure why it isn't working in the flow.

Any suggestions would be appreciated as I'm not experienced in XML and seem to be going round in circles trying to work it out.

Thanks

I have the same question (0)

All responses (3)

Answers (0)

meelamri 13,216 User Group Leader on at

Like (0)

Report

RE: XML working in FetchXML Builder but flow fails in power automate

Hi,

Please share your flow and the error message..

Was this reply helpful? Yes No
louisa lane 200 on at

Like (0)

Report

RE: XML working in FetchXML Builder but flow fails in power automate

This is the error message

Syntax error: character '<' is not valid at position 0 in '<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false" >

<entity name="opportunity" >

<attribute name="name" />

<attribute name="estimatedvalue" />

<attribute name="estimatedclosedate" />

<attribute name="ownerid" />

<attribute name="statuscode" />

<attribute name="new_referraldate" />

<attribute name="new_forecast" />

<order attribute="estimatedclosedate" descending="false" />

<filter type="and" >

<condition attribute="statecode" operator="eq" value="0" />

<condition attribute="estimatedclosedate" operator="next-x-days" value="14" />

</filter>

<attribute name="opportunityid" />

</entity>

</fetch>

'.

This is the step which we seem to fail at and get the above error.

Thanks

Was this reply helpful? Yes No
Thomas David Dayman 11,323 on at

Like (0)

Report

RE: XML working in FetchXML Builder but flow fails in power automate

Can you try and use the Dataverse connections instead of the deprecated connections?

Maybe this might be the issue

Was this reply helpful? Yes No