Has anybody tested the Remote File Import using a CSV with a non-comma separator (using pipe)?

[treidfrb]

The Remote File Import does upload the CSV file from the mid server to a Data Source.  Even when pointing the Remote File Import to an existing import set load table with an existing transform map, the uploaded data source configuration does not retain the custom separator value.  It would seem I need to use another file format like XML or JSON to overcome this issue.  We have tested a manual import set configuration, with the delimiter set to pipe, and the import set table load and transform work fine.  We would like to automate the upload and transform from the mid-server file in a schedule, but the nature of the CSV will not retain the custom delimiter when it attempts to load the import table, so it fails to successfully populate the import set table and does not attempt the transform.  Thank you.

[treidfrb · Accepted solution]

Hi Shakti, the way I fixed the issue was to have the file format changed from pipe delimited to tab delimited.  I found that only the default file formats would work when pulling in a file that is located in the mid server file system.  HTH, Tim

[sr82]

thanks Tim. I am not sure what I was doing wrong earlier but I managed to use remote file importer to pull a JSON file from midserver and process that successfully

[treidfrb]

awesome Shakti good job!