You have decided to follow the recommendations above. The first EDI Profile you want to build will send Invoices by FTP to your Customers. Unlike email used in the previous examples, where there are contact records and user records with email addresses, there is no fixed place in the database to store FTP information. How do you build a general EDI Profile to send files to different FTP server for different Customers?
The example below creates and uses four EDI tokens that are not part of the standard set. It uses Customer Characteristics to hold the FTP hosts, user names, passwords, and directories. This approach has some security problems but will serve as an example of the kinds of thing you can do.
