Developer Guide - Vault Platform for Dynamics 365 Sales

Integration Architecture

The Vault Platform for Dynamics 365 Sales uses a native server-side processing layer within Dataverse. Each Command Bar action routes through a Custom Dataverse API to server-side logic that builds the document payload, uploads it to SharePoint, and calls the Vault Dispatcher.

Dispatcher Contract

The Dispatcher is source-agnostic. It is a pure request-response service with four operations, and it only reads and writes SharePoint.

The Dispatcher never calls back to Dynamics 365. There is no push, no webhook, and no write to Dataverse. All state updates in CRM happen when a CRM user explicitly triggers an action - pull model throughout.

Action Summary

Each Command Bar button routes to a dedicated Custom Dataverse API. The table below describes what each action does and when to use it.

Dataverse Custom Tables

The managed solution installs six custom tables. All table names are prefixed with vault_.

vault_template

Stores template definitions - one row per template.

vault_templatefield

Stores field mappings for each template - one row per mapped field.

vault_templateassignment

Controls which templates appear on which entities and contexts.

vault_templatesigner

Stores e-signature signer configuration per template. Fields reference CRM field logical names resolved at generation time — they are not hardcoded email addresses.

vault_templaterecipient

Stores delivery and workflow recipient configuration per template. Recipients can be either dynamic (resolved from the CRM record) or static (hardcoded email address).

vault_documentlink

The runtime document link table. One row per generated document per record per link type.

Write rules:

Link type policy: A record can hold one standard link and one workflow link simultaneously. A new standard document never deletes a workflow link, and vice versa. The latest document of each type overwrites the previous.

Custom APIs

The solution includes eight Custom Dataverse APIs. The four command actions are invoked by Command Bar buttons. The four admin APIs are intended for one-time or periodic administrative use.

Command Actions

Admin APIs

vault_InitializeDefaults parameters:

vault_ValidateSettings outputs:

Workflow Enforcement

A pre-operation plugin checks whether a pending workflow should block or warn before certain CRM operations complete. It reads the last-known workflow state saved on the record - it never calls the Dispatcher directly. If a user has not recently synced the workflow status, enforcement acts on the most recently saved state.

Enforcement modes (configured per template):

Suggested Enforcement Triggers by Entity

Enforcement mode (Block / Validate / None) is configured per template and stored in vault_documentlink.enforcementMode at the time of document generation.

Batch Dispatch Modes

The Dispatcher detects the operation mode from the payload schema. The plugin code is identical for single and batch operations - both call POST /render and receive a PDF buffer in response.

For batch operations, the Dispatcher accepts the job, immediately generates and returns an Intake Receipt PDF as acknowledgment, then processes the batch asynchronously and writes results to SharePoint. The CRM user receives the Intake Receipt immediately - the same hand-in-hand experience as a single record operation.

Initial release scope:

Batch Safety Thresholds

Thresholds are stored as Dataverse Environment Variables and can be adjusted per customer without a solution update.

Managed Solution Contents

VaultPlatform_D365Sales (Managed Solution)
├── Dataverse Tables (6)
│   ├── vault_template
│   ├── vault_templatefield
│   ├── vault_templateassignment
│   ├── vault_templatesigner
│   ├── vault_templaterecipient
│   └── vault_documentlink
├── Custom Dataverse APIs (8)
│   ├── vault_ProcessDocument         - Command Bar action
│   ├── vault_OpenDocument            - Command Bar action
│   ├── vault_SyncWorkflowStatus      - Command Bar action
│   ├── vault_GetSealedDocument       - Command Bar action
│   ├── vault_BrowseSharePointFolder  - Admin: browse template library
│   ├── vault_ImportTemplate          - Admin: import .vpdf from SharePoint
│   ├── vault_InitializeDefaults      - Admin: seed default templates (8 entities)
│   └── vault_ValidateSettings        - Admin: check environment variable config
├── Web Resources
│   ├── vault_/scripts/vault_actions.js    - Command Bar button handlers
│   ├── vault_/scripts/vault_gallery.js    - Template gallery + progress dialog
│   ├── vault_/scripts/vault_browser.js    - Template browser + import dialog
│   ├── vault_/stylesheets/vault_gallery.css
│   ├── vault_/stylesheets/vault_browser.css
│   ├── vault_/pages/vault_gallery.html
│   └── vault_/pages/vault_browser.html
├── Command Bar Customisations (8 entities)
│   ├── quote, opportunity, account, contact
│   ├── salesorder, invoice, incident, lead
│   └── Buttons: [Process Document] [Open Document] [Sync Workflow Status] [Get Signed Document]
├── Security Roles
│   └── Vault User
└── Environment Variables (12)
    ├── vault_graph_tenantid
    ├── vault_graph_clientid
    ├── vault_graph_clientsecret           (secret)
    ├── vault_graph_driveid                (output document library)
    ├── vault_graph_templatesdriveid       (templates library)
    ├── vault_graph_templatessourcefolder  (folder path within templates library)
    ├── vault_dispatcher_baseurl
    ├── vault_dispatcher_tenantid
    ├── vault_dispatcher_clientid
    ├── vault_dispatcher_clientsecret      (secret)
    ├── vault_batchwarningthreshold        (default: 25)
    └── vault_batchmaxthreshold            (default: 100)

Deployment and ALM