Forum Discussion

Rich Koneval's avatar
Rich Koneval
Brass Contributor
Mar 28, 2019

Flow Action - Convert Word Document to PDF

I'm trying to use the Convert Word Document to PDF action in a Flow. There are three parameters that have to be entered: Location - the SharePoint Site Document Library - Library where the documen...
Microsoft Flow
sips1's avatar
sips1
Copper Contributor
Nov 27, 2019

VFXPro I used the dynamic field "Name" in the File field and it worked.

 

I create a new file based upon another i.e. a template then use the Convert Word Document to PDF specifying the dynamic field "Name" of the new file to convert.

 

The file being converted uses quick parts and SharePoint metadata so the contents are dynamic.

 

Thanks,

 

sips1

VFXPro's avatar
VFXPro
Brass Contributor
Dec 18, 2019
sips1, can you export your flow and send it over? or screenshots? I tried every combination... There must be something different... Thanks.
  • VFXPro's avatar
    VFXPro
    Brass Contributor
    Dec 18, 2019

    VFXPro 

     

    Hi all.. 

    I decided a simple workaround was in order.  I simply copy the file into OneDrive for business as a temporary location, use the "Convert file from OneDrive for Business" into PDF passing the Identifier as a variable" then create the PDF into sharepoint, and delete my temporary file from ODfB.  🙂  It's more moving parts, but it works just fine until this issue is fixed.

    • Roghan's avatar
      Roghan
      Copper Contributor
      Jan 12, 2020

      VFXPro 

       

      Thanks for sharing, I am stuck on this exact issue too and am unable to convert a Word Doc to PDF within Sharepoint. Has there been any developments in the mean time? 

      If not, is it possible you paste the flow you've developed as a workaround which you have discussed? would be good to mimick it myself in the interim till an MS solution is developed.

       

       

      • ThreeTen22's avatar
        ThreeTen22
        Copper Contributor
        Feb 02, 2020

        After some substantial trial and error I believe this usually happens when a file has been created, but isn't "ready yet".  Its as if its returning the file properties that can work with Sharepoint's REST API, without actually determining if the information can be discovered by Microsoft's graph API (which I am now convinced is what that action is using).

         

        A workaround I have found is to wrap the action in a while loop with a success and failure branch.  On failure, wait 10 seconds and then restart the loop.  It isn't perfect of course,  but 99% of the time it fails once or twice, then goes through