Ability to have more than 1 file attachment field so that;
Hi, this is in near future plans.
However, permissions in Fibery are not per-field, so option 2 will not be possible anyway.
To add to this, i have just discovered that I cannot access Files in fibery using Zapier which is a huge limitation. Can you make them available in Zapier so we can automate workflows that need them moving to other places?
Hi @Lee_Denny,
Since Fibery Zap 0.9.11 you should be able to access Files in Zapier. There’s still some limitations as we provide File Object (Zapier Docs). Can you give it a try?
Oh, I’m really looking forward to number 1 and 3! <3
Same here! +1 to 1 and 3.
To add to this for when files are improved. Please make the ability to play video in browser and not have to download it.
Love the idea!
This suggestion is related to this:
Is there an ETA on implementing multiple file fields?
No ETA yet, sorry
So far Q2 2025 is the best guess.
Another +1 for these features here (1 & 3).
I think for now you can get external users to drag individual files into rich text boxes. It looks a bit weird and might have to be explained to them though!
Yes, really need this. Would love to attach specific documents (like contracts, paid invoices etc.) so we can keep track of them and find them easily!
For each file field could we choose to restrict it to certain file types and sizes?
Just a thought, if they are treated like a relations, we could use custom access templates to give access to some files and not others.
Plus one request would be to allow the renaming of files inside of fibery/eith automations. But if it’s too complex, it’s also not so needed.
Hopefully functionality is planned to be extended to also include files as “first class”. While having multiple file fields is ok, one major issue is imho lack of using, aggregating and displaying files as sortable/filterable table or list view while ideally enabling the native “files” drag and drop upload as well.
that way we could at least use some sort of fibery file repo that is not limited to the native, somewhat limited files entity function and it’s preview.
if I understood correctly it might even enable part of the requirements posted by the Op: as long as there’s a way to predefine or automate different preset filters/preset categories when uploading files to different, filtered table/list relation or self-relation views of “files” in an entity.
Something to consider:
One limitation with attached images, is there is no way to take those images and place them into an HTML PDF or embedded in an email (except as an attachment for the email).
It would be really great, if these new file fields could be set up so the images could be referenced. There’s use cases for both the first image and all images. This feature would go a long way in creating documents with dynamic images.
Static images in these documents is already possible. But automations need this to be dynamic. And this is a requirement for Fibery to be the main database for automatically generating these documents.
