Question
A company is using Dataverse with a custom table named Prospects. The Prospects table has a lookup to the Account table.
SharePoint document management is configured in the environment but is not configured for the Prospects table. All documents saved as part of the integration must be accessed by using an Account row linked to the Prospects table.
Based on new requirements from end users, the Prospects table must be reconfigured for use with the document management feature.
You need to configure the integration.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Explanation
Server-based SharePoint integration and document management are already configured in the environment, so they do not need to be enabled again; only the Prospects table needs to join. First, edit the Prospects table and turn on its SharePoint document management option, which lets the table participate in the integration. Next, navigate to Document Management settings and run the wizard, selecting the Prospects table so that document locations are created for its rows. Because documents must be reached through the Account row linked to each prospect, select the Based on entity checkbox with Account: the folder structure is then built under the related account's folder, which works because Prospects has a single lookup (N:1) to Account. Clearing Based on entity would store prospect documents in their own flat library, and adding a File column would store files in Dataverse rather than SharePoint.
