Power automate not working after transferring Jotform to new account.

  • Profile Image
    Enlighted_INC
    Asked on June 13, 2020 at 09:05 PM

    Hello

    I previously received tech support from you for Jotform uploads to SharePoint, via Power Automate. This was working well prior to you moving the form to this account.

    I have re-created a new flow in power automate with the new Jotform account.

    I cannot get it to work in the new account.

    The form is "NEW PROJECT STARTUP"

    Please advise


    Old Account - S_Lorusso

    shawn.lorusso@enlightedinc.com


    Link to what you had me set up on the old account.

    https://www.jotform.com/answers/2358500-How-to-Create-Uploaded-Files-from-Form-to-Sharepoint-through-Power-Automate#14


  • Profile Image
    roneet
    Answered on June 13, 2020 at 11:07 PM

    I would suggest you clone the form in your account and then create a new workflow as directed by my colleague in the previous thread.

    Let us know how it goes.

    Thanks.

  • Profile Image
    Enlighted_INC
    Answered on June 14, 2020 at 08:43 AM

    Ok still does not work with clone.

     

    This is what is said in the error message.

     

    BODY 

    {
      "error": {
        "code"502,
        "source""flow-apim-msmanaged-na-northcentralus-01.azure-apim.net",
        "clientRequestId""13bd2960-2fd7-4768-bffe-1959f9d0bc02",
        "message""BadGateway",
        "innerError": {
          "status"500,
          "message""Illegal characters in path.\r\nclientRequestId: 13bd2960-2fd7-4768-bffe-1959f9d0bc02\r\nserviceRequestId: 13bd2960-2fd7-4768-bffe-1959f9d0bc02"
        }
      }
    }
     
    1592138865error.png
     
     
    THIS IS THE CODE WHERE THE ERROR IS HAPPENING, AT SHAREPOINT "CREATE FILE" 
     
    {
        "inputs": {
            "host": {
                "connection": {
                    "name""@parameters('$connections')['shared_sharepointonline']['connectionId']"
                }
            },
            "method""post",
            "body""@body('HTTP_2')",
            "path""/datasets/@{encodeURIComponent(encodeURIComponent('https://enlighted.sharepoint.com/sites/external/External Requests'))}/files",
            "queries": {
                "folderPath""/ER  Field Service Requests/@{triggerBody()?['11 - Project / Site name:']}",
                "name""@triggerBody()?['114 - RCP']",
                "queryParametersSingleEncoded"true
            },
            "authentication""@parameters('$authentication')",
            "retryPolicy": {
                "type""none"
            }
        },
        "runtimeConfiguration": {
            "contentTransfer": {
                "transferMode""Chunked"
            }
        },
        "metadata": {
            "flowSystemMetadata": {
                "swaggerOperationId""CreateFile"
            }
        }
    }
  • Profile Image
    EltonCris
    Answered on June 14, 2020 at 11:37 AM

    I made a test on my end but I couldn't reproduce the problem. Everything went through just fine.

    I suggest you review each of the actions again. Perhaps you might have missed something.

    Some of the important parts to take note are the following;

    ** Since the form is moved, make sure to re-connect the account that currently holds the form on Power Automate.

    ** On Jotform's action, it should be on Text format

    ** Make sure you copy the same exact code under Expression

    actions('HTTP').outputs.headers.Location

    06072020_MfcJA0omm1.png

    ** Initialize Variable should be configured to run on failed

    06072020_ihjmiyMGDo.png

    ** Please do not be confused with the Body (from HTTP1 and HTTP2), make sure the Create File uses Body from HTTP2.

    If these are all correct and the problem still persists, please provide us a screenshot of your full configuration so we can have a look. Please upload the screenshot in your thread here https://www.jotform.com/answers/2387494

    Thanks

  • Profile Image
    Enlighted_INC
    Answered on June 14, 2020 at 12:18 PM

    thank you for testing both CreatE PDF and Create file. I am first trying to get the uploads to work before I get the PDF.


    I have it setup as you show it.

    FYI......I did have it working with the old Jotform account just as my images show below. I had it working with 8 individual "File Upload" widgets, and 8 individual "Form Calculation" widgets


    1592150789error 5.png

    1592150841error 6.png

    1592150904error 7.png


    1592150115error 1.png

    1592150142error 2.png


    1592150179error 3.png


    I could also send you the "File Content" info from below, although it was 49 pages. 

    Let me know

    1592151367error 4.png

    1592151390error 8.png


    BODY of sharepoint "Create File" action shows complete error below.

    {
      "error": {
        "code"502,
        "source""flow-apim-msmanaged-na-westus2-01.azure-apim.net",
        "clientRequestId""89bb29eb-c8fb-4f5b-9c58-11b4bf60b578",
        "message""BadGateway",
        "innerError": {
          "status"500,
          "message""Illegal characters in path.\r\nclientRequestId: 89bb29eb-c8fb-4f5b-9c58-11b4bf60b578\r\nserviceRequestId: 89bb29eb-c8fb-4f5b-9c58-11b4bf60b578"
        }
      }
    }
     

  • Profile Image
    Amin_N
    Answered on June 14, 2020 at 02:05 PM

    Please give it another try by running the flow again since error code 500 is for temporary failures according to Power Automate documentation.

    If the issue still persists, we will be escalating this to our developers to look into.

  • Profile Image
    Enlighted_INC
    Answered on June 14, 2020 at 02:14 PM

    no change. problem still happening

  • Profile Image
    EltonCris
    Answered on June 14, 2020 at 07:49 PM

    Your configuration is indeed correct and the error only occurs during "Create File" based on your screenshot. I checked on Power Automate and this seems to be a common back end issue with SharePoint.

    Example: https://powerusers.microsoft.com/t5/General-Power-Automate/Flows-stop-triggering-unexpectedly-Bad-gateway-502/m-p/126696#M42900


    There's also one user who reported similar when huge file is uploaded, around 20MB.

    https://powerusers.microsoft.com/t5/General-Power-Automate/Get-file-Content-Sharepoint-connector-timed-out-for-files-over/m-p/578600

    You may consider checking this article for a possible solution https://docs.microsoft.com/en-us/sharepoint/troubleshoot/lists-and-libraries/request-timed-out-when-upload-large-file-to-library.

    If the problem still persists, please contact Power Automate support to get further assistance on this issue. I'm sure they'd be able to help.

    Thanks!


  • Profile Image
    Enlighted_INC
    Answered on June 14, 2020 at 10:45 PM

    Per the recommendation of the links you sent me, I cleared cache and history from the browser. I even tried another browser. Problem did not go away.

    I am led to believe this is JotForms problem, as this was working with a free account per your original setup.

    The reason i am led to believe this is JotForms problem, is that the errors keep saying invalid character. So I thought about it and traced the issue to your "Form Calculation" widget.

    I tried a test.

    I bypassed the "Form Calculation" widget, and it worked. But....it is not naming the file as it did per your original instructions, as I bypassed the "Form Calculation" widget. It is naming is naming the file with the "Test.pdf" name I am giving it.

    Could you please look into the issue with the "Form Calculation" widget and let me know next steps?

    AS A TEST, I HAVE DELETED BOTH THE "FILE UPLOAD" WIDGET  AND THE "FORM CALCULATION" WIDGET, AND ADDED THEM BACK. ACTUALLY, I COPIED THEM, AND THEN DELETED THE OLD ONES. STILL DID NOT SOLVE PROBLEM

    And if you need to review the form on my account, it is "NEW PROJECT STARTUP"

    1592188938error 10.png

     

    1592188800error 9.png

     

    1592188966error 11.png

     

  • Profile Image
    roneet
    Answered on June 15, 2020 at 02:05 AM

    I have added a Short text entry field on your form. Could you please try out to insert the File Upload element conditionally as shown below:

    1592201066888888888.gif

    Another thing, I have noticed that you have a broken condition. Please fix the condition.

    Please connect this free text in your workflow.

    Let us know how it goes.

    Thanks.

  • Profile Image
    Enlighted_INC
    Answered on June 15, 2020 at 10:17 AM

    That fixed it. Let hope this continues to work. Thank you.

  • Profile Image
    Enlighted_INC
    Answered on June 15, 2020 at 02:06 PM

    One last thing pertaining to this...... I have 8 of these which currently I have them all connected and are working.

    The last issue around this....

    If I do not upload all 8 files I get a "Failed" within Power Automate. What additional actions could I add to Power automate, that would not cause the action to fail? And to clarify, if I only upload 6 files, I will get all 6 files, but power automate shows an error. I need to add something so the error does not show, as we have to manage the errors when they do happen, and I do not want to receive an error when someone does not upload all 8 files. Especially since, all 8 files are not always required.

    Please advise.


  • Profile Image
    Amin_N
    Answered on June 15, 2020 at 05:06 PM

    To my understanding, you're inquiring what action you can include in your flow to remove the "Failed" error when user has not uploaded all 8 files.

    Since this is entirely a pure Power Automate question, I do recommend that you alternatively reach out to their support, or refer to the guide below:

    Error-handling-when-action-fails

    Your understanding is most appreciated.