Change in behavior of executePutCmd() in custom FTP scripts, from EDI 2.2.0 to EDI 2.5.0+
Article ID: KB0086015
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Resolution:
Behavior in EDI 2.2.0:
The filename parameter that was used in executePutCmd(), was used to name the file on the FTP Server. Users had the flexibility to name the file however they wanted.
Behavior in EDI 2.5.0+:
The filename parameter that is used in executePutCmd(), is actually the internal filename that is stored by EDI. Users cannot name the file on the FTP Server using this method.
Work around: Use executeRenameCmd() to rename the file on the FTP Server to the desired name.
Behavior in EDI 2.2.0:
The filename parameter that was used in executePutCmd(), was used to name the file on the FTP Server. Users had the flexibility to name the file however they wanted.
Behavior in EDI 2.5.0+:
The filename parameter that is used in executePutCmd(), is actually the internal filename that is stored by EDI. Users cannot name the file on the FTP Server using this method.
Work around: Use executeRenameCmd() to rename the file on the FTP Server to the desired name.
Issue/Introduction
Change in behavior of executePutCmd() in custom FTP scripts, from EDI 2.2.0 to EDI 2.5.0+
Feedback
Yes
No
Powered by
