Question
You are configuring Dataverse for a company.
The company has the following requirements for document management, which must be met by using native functionality:
• A single file must be stored and accessed directly from an Account row. No additional metadata should be captured.
• Multiple files must be stored and accessed from a Contact with support for version control.
• Documents must be stored within an on-premises environment.
• Additional rich-text notes must be stored alongside one or multiple file uploads.
You need to recommend a solution for each requirement.
Which solution should you recommend? To answer, move the appropriate solutions to the correct requirements. You may use each solution once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Explanation
Save a file on an Account row: Document column. A file (document) column stores one file directly on the row and captures no extra metadata, which matches a single file on the Account with nothing else recorded.
Store multiple files by using version control: Microsoft SharePoint. SharePoint document management stores many files in a document library folder linked to the Contact, and from the record's Documents grid users can check documents in and out while the library keeps version history. Azure Blob Storage is not a native Dataverse document management option.
Host documents on premises: Microsoft SharePoint. Dataverse document management supports SharePoint on-premises through server-based authentication, so documents can stay in the company's own environment.
Upload documents that have rich-text metadata: Attachments. Notes in the timeline hold rich-text note content together with attached files, so each upload carries its own rich-text description.
