Forum Discussion

darshthakkar's avatar
darshthakkar
Valued Contributor
4 years ago
Solved

Using Date.now() while exporting files

Hi Team, While writing files via sftp, I’m unable to ingest Date.now() in the filename itself as seen in the snaps below: (1) Successful execution [passing pipeline parameter and selecting the ‘=...
json
REST
  • SpiroTaleski's avatar
    SpiroTaleski
    2 years ago

    arvindnsn 

    If you have the checkbox "Do not start a new execution if one is already active" checked, then it will prevent the pipeline to run if the previous is still running.  

    And about the concurrency, keep in mind that by default the maximum number of concurrent calls(only for cloudplexes) are 10. 

    BR,

    Spiro Taleski

     

Supratim's avatar
Supratim
Contributor III
4 years ago
Copy LinkReport

@darshthakkar Make expression enabled by clicking on the “=” on filename and can use below expression - “%s/%s%s.csv”.sprintf(“baseSFTPPath”,“constantFileName”,Date.now().toLocaleDateTimeString({“format”:“yyyyMMddHH:mm:ss”}))

darshthakkar's avatar
darshthakkar
Valued Contributor
4 years ago
Copy LinkReport

Thank you @Supratim for providing the string for file writer but this is failing as well.

  • Supratim's avatar
    Supratim
    Contributor III
    4 years ago
    Copy LinkReport

    @darshthakkar Just to make sure you config correctly - 1. use wincsp/other tools to login the sftp server (please use same credential as used in snaplogic). And try to create a file there. If you can then it should work in snap as well.
    2. Make sure you choose cloudplex/groundplex correctly.
    3. And hope you validate this is sftp server not smb.

    • darshthakkar's avatar
      darshthakkar
      Valued Contributor
      4 years ago
      Copy LinkReport

      Done, still not working for me.

      • siwadon's avatar
        siwadon
        Employee
        4 years ago
        Copy LinkReport

        I think it is the problem with colon in the filename which is not a valid character in many file systems generally. You could try removing that from the expression.