Hi Roy,

Do I understand it correctly you want the use the File upload control without actually uploading the file? If so you can try out the File link control. That should only record link to the file without actually uploading it.

Hi Mark,

I tried setting a domain on File link, but the domain then still required a Storage location to in_database. For me this was an indication that it would still require for a column to have a storage column.

So is this in_database Storage location obsolete, or does it still store in the database?

Confirmed with a colleague, the File link only works in the Windows GUI like a true file link. In the other GUI's the file still gets uploaded; hence the storage location.

So as long as you are using the Windows GUI, the storage location is ignored when using the File link control.

Good to know that this is an option for the Windows GUI.

Unfortunately, this particular client is using the Web GUI. Do you consider this a bug of the Web GUI, and is this currently being fixed?

This does work as intended and is not considered a bug

It is good to note that when using the File link control, you should use a database storage location that uses Disk; not Database

Could this storage location also be sent to a location that can be reached by the sql server? So be used to move it from one location (from where it's been uploaded), to another location from where the sql server can access it?

I suppose you could do that. When using a Disk storage location, you can find the file at the file location that is now present in your application. When adding/editing a record and uploading/linking to a file, you can then start a Process flow to move the file to a location where the database can reach it.