Need help in copying XML files from FTP (a) to FTP (b)

Avatar
Raul Bernales
Celigo University Level 2: Seasoned
Engaged
Awesome Follow-up

Good day.  We are trying to create a flow to copy XML files from our clients FTP server to our FTP server and we can't seem to make it work.

Below is the flow that we are working on.

 

Here are the parameters set on source FTP

 

Here are the parameters set on destination FTP

 

And below are the errors that we are getting.  

 

Would appreciate any advice.  Thanks!

0

Comments

5 comments
Date Votes
  • Avatar
    Youssef Zouhairi
    Solutions Consultant
    Engaged
    Celigo University Level 4: Legendary

    Hi Raul, 
    In your import, do you have the blobKey in the advanced section ?


    If not , please try to add the value "blobKey" for Blob path and retry. 

    Youssef

    0
  • Avatar
    Raul Bernales
    Celigo University Level 2: Seasoned
    Engaged
    Awesome Follow-up

    Hi Youssef Zouhairi,  I've tried that one but unfortunately I'm still getting the same error below:

    Message: 
        <!doctype html><html lang="en"><head><title>HTTP Status 500 – Internal Server Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 500 – Internal Server Error</h1><hr class="line" /><p><b>Type</b> Exception Report</p><p><b>...
    Code: 500
    Source: Connection 
    Timestamp: 2023-09-29T13:31:45.064Z
    Error ID: 1828029785
    Trace key : SHIPMENT_498524_20230928102300166780.xml 

     

    0
  • Avatar
    Youssef Zouhairi
    Solutions Consultant
    Engaged
    Celigo University Level 4: Legendary

    Raul Bernales
    It seems that the issue is in the destination server. I tried the same configuration as yours in my account and it works. 
    Try to create a flow with as Export , some csv that you parse, and then as Import, you re-create the csv and deposit the file in the server. That's the way I would troubleshoot it. 
    This is to be sure it's not a blob issue and confirm that the connection to the distant server works correctly. 

    0
  • Avatar
    Raul Bernales
    Celigo University Level 2: Seasoned
    Engaged
    Awesome Follow-up

    Youssef Zouhairi

    We've advanced a bit by changing the File name handlebar expression from {{{record.fileName}}} to SHIPMENT-{{timestamp "YYYY-MM-DD hh:mm:ss" "America/Chicago"}}.XML

    Any chance anyone can help provide the correct handlebar expression to use the exact filename of the source XML file(s).  Below are samples of the source XML filenames.

    • SHIPMENT_498522_20230928102300160837.xml
    • SHIPMENT_498524_20230928102300166780.xml
    • SHIPMENT_497519_20230928102300142041.xml

    Many thanks in advance!

    0
  • Avatar
    Raul Bernales
    Celigo University Level 2: Seasoned
    Engaged
    Awesome Follow-up

    Finally was able to make it work to get the exact filename by reading the article Get the file name and size of FTP exports.  I used the preSavePage function shared by Kathyana Queeman below so the handlebar expression {{record.fileName}} can work.

    function preSavePage (options) {
  // sample code that simply passes on what has been exported
  if(options.data && options.data.length>0){
    for (let i = 0; i < options.data.length; i++) {
      options.data[i].fileName=options.files[i].fileMeta.fileName;
          options.data[i].fileSize=options.files[i].fileMeta.fileSize;
   }
  }
 
  return {
    data: options.data,
    errors: options.errors,
    abort: false,
    newErrorsAndRetryData: []
  }
}
    1

Please sign in to leave a comment.

 

Didn't find what you were looking for?

New post