[External File Storage Connector]Local File System Connector (OnPrem)

[IceOnly]

Summary

Implement a new connector that allows access to the local file system of the application server via the external file storage module. It is only intended for OnPrem and not for use in Business Central Online.

Work Item(s)

Fixes #27897

[github-actions]

Issue #27897 is not valid. Please make sure you link an issue that exists, is open and is approved.

[pri-kise]

I would love to have this feature as a W1 first party app, but isn't this against the Universal Code Initiative?
https://www.microsoft.com/en-us/dynamics-365/blog/it-professional/2022/10/28/the-dynamics-365-business-central-universal-code-initiative-is-live/

[IceOnly]

I would love to have this feature as a W1 first party app, but isn't this against the Universal Code Initiative? https://www.microsoft.com/en-us/dynamics-365/blog/it-professional/2022/10/28/the-dynamics-365-business-central-universal-code-initiative-is-live/

Technically yes, the app needs target: ‘OnPrem’.
But Microsoft signed apps are excluded from the licence check.

I believe it promotes the Universal Code Initiative.
Why?
Enough partners build their own local REST web service for file access, an example here is the well-known File Connector from Document Capture. Is an OnPrem customer extension that uses a proprietary File Connector and target: ‘Cloud’ out of the box SaaS ready?

However, if this connector were to be used instead, it can be replaced by another one without any problems. The External File Storage Module only works with relative paths, with a standardised structure. If I create a Local File Account with the base path C:\run, the module turns the file path C:\run\my\HelloWorld.txt into my/HelloWorld.txt.

I can simply upload the content of c:\run\ to e.g. an Azure Blob Storage, perform the cloud migration, replace the connector and that's it!

Isn't that exactly the aim of the Universal Code Initiative?