I think its straight forward, and the “…” is already there in the field header. Aware this might be harder to implement in back end (with zipping?). But would be handy when there are multiple files attached that need downloading. Even better if this action (download attached files) could be exposed in the automation button set up if the entity has the field for files.
2 Likes
We are going to completely redesign files in Q2 and this will be solved as well
9 Likes
Wait what!? That’s… awesome. Files always felt a bit underutilized for our team. Excited to see what you guys have in mind!
( Fingers crossed that they become entities that can be multi-homed and benefit from all the other goodness that comes with entities )
2 Likes
Any chance to get more details if you already have a general direction? I’m building something very file driven and want to try to build it in a way that will utilise the update, but also not force me to build from scratch. Getting an idea also on the migration that will happen to existing file fields would be great. Thanks!!
(My vote is that the file field only has space for 1 file (or at least a setting to turn that on), that way the entity itself becomes the file container. With an action button on the entity itself to download file. (Which is build to work in batch, so we can select multiple files and download together). And have an actual player inside of the entity to view the file thats in there, and allow other types of media as cover in the board view. Then we can make a database called “File” and add a file field, treat each of those entities as a file. But then also the file is not deletable from the entity. You gotta delete the entity in order to delete the file. (A file entity with no file makes no sense.) Then we can link an entity to a “Files” database. And have as many relation fields to files as we’d like. Just like the way we make our own database for Docs. )
In short we are going to make it possible to add as many File fields to a database as needed, change Files UI to make it look good, allow to preview content of the files, download all files, add File unit to all views, create Gallery View.
3 Likes
Will we get support for 3rd party file sharing apps like Google Drive & Dropbox?
1 Like
Not in scope so far. But we will see
That came out of nowhere, great to hear 
I had already plans to try and build an advanced file management system with the following idea (example with Projects DB):
- Have a “File Management” space with a DB which I will call “File Binder”
- Many to many relation File Binder DB ↔ Project DB
- Files extention enabled for both DBs
- Show File Binder Collection in Projects Entity view right below the Files extension
- Auxiliary field in Projects DB: Files count
- Set up an automation with a script which does the following:
If Files count of Project Entity changes (increases), create new “File Binder” entity and link to project, download File from Projects and upload to new File Binder entity, then delete the file from Project Entity.
So basically the idea is that the Files extension of the original DB serves as an upload button and whenever something is uploaded, it is shifted to the collection view below by triggering a new “File Binder” entity creation where file is attached there.
“File Binder” because you could have multiple files within a File Binder Entity.
This would also enable having a centralized space where all files within the workspace can be found.
So as happy as I am that Files will get a rework, I’m also slightly disappointed because I won’t really get to play around with the idea 
2 Likes
This is very exciting. As a workaround for sharing/linking files in multiple places I’ve got a Resources database where one of the entity types is a Eagle link (Design library tool for storing images)
I create an entity in Fibery, add a url field, and then I can link to this entity multiple times.
This gives the effect of being able to link/reference the same images from multiple places and without uploading the files to multiple places.
I’m obviously not asking for Fibery to go this far, but the way that Eagle handles images/files is similar to how entities work in Fibery. Your images/files in Eagle can be tagged and added to multiple folders but you’re not duplicating the file, you’re just looking at the same image in a different view (folder, or a tag view)