Hi NicolasArgente ,
Thanks for your answer, but the file is really a highly standardized one and only the OS servers and the servers of the producing system have access to that path. So there should be no unexpected format change, etc.
in the meantime I also had an incident open with OS and this was the reply:
- Include a workspace step as the first step in a workflow (before import). The workspace has a button which executes a rule, the rule copies the file and automatically executes an import or alternatively copies the file to the incoming folder and then the user manually selects and loads.
- Connector which copies file and reads the file into a DataTable then processes.
- Automated process which copies files to the batch harvest folder and executes the import/load process.
I'm now going with the second option and directly read the file from the UNC path into a data table.
Thanks
Markus