Apologies.
BRApi.Utilities.ExecuteFileHarvestBatch works for Direct Load as well. The issue was due to a different piece of code that tried to clear stage data for Direct Load Workflow Profile.
Thanks!
I always try not to use the batch harvester. I've always used the import process API calls to do it. Look at https://community.onestreamsoftware.com/t5/Workflow-and-Data-Integration/Automating-WF-Execution/m-p/10247?search-action-id=7866072495&search-result-uid=10247
Any specific reason to stay away from the batch harvester?
Earlier, the files and folders created by the batch harvester cannot be deleted. I guess there is some utility I saw during Wave that can do it. Then there is an issue with file locks and it will not work when there are file locks.
Oh, and the other one, only someone with old FDM knowledge can understand what the file even means.
