wouldn't it be a solution to use sharepoint's document library as a export files store?

users can map document library to a local drive/folder and work with it like with local filesystem

Hi Bim Bimi‌,

If I were you, I would use PowerShell (Server) or PnP-PowerShell (Client) (https://github.com/SharePoint/PnP-PowerShell) to process the SAP exported text file and add the information you want to a SharePoint list (which is shown on a page on the intranet). What?? No Nintex??

Cheers,

Rick

in my experience a simple c# app will do the trick to import data to sharepoint and it will be way faster

Hi

as far as I know, the SAP uses an FTP to export that txt file to our shared drive and we tried to make it store the file directly into the sharepoint file directory but does not work as FTP is blocked (cannot be unblocked for sec reasons).

Then what I done so far is, used the Content Editor webpart and pasted an embedded html code that points to the files stored in our shared drive e.g F:SAPexportFirstAider.txt

This at least shows the data as the actual txt file.
Though ideally wanted to show only names and the status but yeh it would take a lot of scripting, which I don't know.

thanks for the suggestions but my scripting and PowerShell is not something I been doing for living
stuff like embedded html code within a content editor webpart pointing to the file in shared folder - seems to be ok

I assume the share is published from some windows host.

then I would say it doesn't matter.

you can map F: drive to a UNC path to SP's doc library as a network share.

or you can even create symlink/junction SAPExport folder to point to UNC path to SP's doc library.

SAP/FTP will not care where file is physically being stored.

Hello Marian

my last solution was to use the extracted .txt file and embed it on Sharepoint.

This work ok at minute .... thanks