Hi @RyanVH,
You have a couple options for document management in Dataverse:
SharePoint Document Management integration
Allows you to associate a document library with a table. A folder gets created for a record when you browse to the related Documents tab for the Dataverse record in a model driven app. You can interact with the SharePoint document library/folders without leaving the Model Driven App. The documents themselves are stored in SharePoint along with the metadata.
Downside is you can't use Dataverse views to run searches against the actual documents or native Dataverse reporting mechanisms.
Upside is you don't use your Dataverse file storage which in comparison to SharePoint storage is more expensive.
Dataverse File Column type
You can create a custom table called Files or whatever you like, add some basic columns for the metadata that would describe your file, and then the File type column to hold the document.
Downside is that it uses Dataverse file storage which will be limited, and can get expensive when you need to purchase add on file storage capacity compared to SharePoint. I'd caution when storing large volumes and recommend setting a reasonable file size limit when cresting the File column.
Upside is that you can easily relate to your Dataverse record and utilize native Dataverse views/search/reporting against your custom File table.
Dataverse Notes with Attachments
This is out of box functionality that allows you to enable Notes on a table, and an attachment can be associated with a note. This is inferior to the above newer capability as it's harder to report on notes with the same downside regarding Dataverse storage capacity.
Last method is to use a Dataverse custom table (E.g Files) to store the metadata for the files, but store the actual file in another place like SharePoint or Azure Blob Storage. You can create a Embedded Canvas App to be connect to the storage system using one of the Connectors. The column in Dataverse can simply hold a reference to the file path.
Downside is its the most effort, embedded Canvas App requires that the Dataverse record must be saved before it can be loaded in the model driven app.
Upside is similar to option 2 where you can have your native relationship and use Dataverse querying/search/reporting on the metadata, and the file is not using up your Dataverse file storage.
Hope this helps.
---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.
