Azure Logic App - FTP status 400 An invalid request was made - Uploading file on the FTP server

Jean-Charles Mouniapin 1

Hello,

I am trying to upload a file on a FTP server using Logic App and I have got the status code 400 "An invalid request was made. Inspect the passed parameters and actions".

The file is generated from Business Central SaaS to a container. I am using Logic App to upload this file on the FTP and delete it from the container.

Does anyone know how to solve this issue, please? On the FTP API connection, I have enable/disable "Binary Transport", it does not work.

MayankBargali-MSFT 68,471 Reputation points

2022-11-16T10:14:59.227+00:00
@Jean-Charles Mouniapin Thanks for reaching out. Can you share the output of your Create File 2 action by clicking on Show raw outputs of the failed run? It looks like the file content is not passed correctly. Can you try to leverage the base64 file content of your blob file rather than passing the File Content directly.

base64(body('Get_blob_content_(V2)'))

Let me know if the above helps you to resolve the issue. If not, please share the raw output data of your failed action.
Jean-Charles Mouniapin 1 Reputation point

2022-11-17T06:39:34.437+00:00

Hello @MayankBargali-MSFT , thank you for helping. I tried what you mentioned but the result is still the same.
I also tried to convert the content in binary and change the API connection to allow “Binary transport”, but still not working.

Action “Create file” FTP (not secure):

Raw input data:

Raw output data:
MayankBargali-MSFT 68,471 Reputation points

2022-11-17T11:27:44.263+00:00

@Jean-Charles Mouniapin Sorry to hear that. Can you please refer to my private comment so I can connect and assist you further. I couldn't observe the same behavior at my end.
Jean-Charles Mouniapin 1 Reputation point

2022-11-17T14:07:50.75+00:00

Hello @MayankBargali-MSFT , I replied to you as requested, please let me know if you have received my message.

Gordon, George 0

Hello: I am having a similar problem, can anyone help ?

{
    "statusCode": 400,
    "headers": {
        "Cache-Control": "no-store, no-cache",
        "Pragma": "no-cache",
        "x-ms-request-id": "7fb1e9c0-dd50-43a4-b487-bce6f17bee1f",
        "Strict-Transport-Security": "max-age=31536000; includeSubDomains",
        "X-Content-Type-Options": "nosniff",
        "X-Frame-Options": "DENY",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "true",
        "x-ms-apihub-obo": "false",
        "Date": "Tue, 05 Sep 2023 14:57:21 GMT",
        "Content-Length": "1098",
        "Content-Type": "application/json",
        "Expires": "-1"
    },
    "body": {
        "status": 400,
        "message": "An error has occurred.  Field validation failed on table of type 'PTCCustomerPaymentJournalLineSettledInvoiceEntity' for the following fields: JournalLineCompany, JournalBatchNumber. Infolog: Warning: The value '1000' in field 'Journal company' is not found in the related table 'Customer payment journal header'.; Warning: The value '1000-009410' in field 'Journal batch number' is not found in the related table 'Customer payment journal header'..\r\nclientRequestId: 7fb1e9c0-dd50-43a4-b487-bce6f17bee1f",
        "error": {
            "message": "An error has occurred.  Field validation failed on table of type 'PTCCustomerPaymentJournalLineSettledInvoiceEntity' for the following fields: JournalLineCompany, JournalBatchNumber. Infolog: Warning: The value '1000' in field 'Journal company' is not found in the related table 'Customer payment journal header'.; Warning: The value '1000-009410' in field 'Journal batch number' is not found in the related table 'Customer payment journal header'.."
        },
        "source": "csmprod.operations.dynamics.com",
        "errors": []
    }