SharePoint Connector Documentation
Index

Deployment Checklist

Use this checklist to ensure a successful deployment of the SharePoint Connector.

Pre-Deployment Checklist

Planning

  • Identify SharePoint site and document library
  • Plan folder structure
  • Determine which tables need mapping
  • Decide on authentication method
  • Plan user training
  • Schedule deployment window

SharePoint Preparation

  • SharePoint site exists and is accessible
  • Document library created
  • Permissions reviewed and set
  • Test manual access to SharePoint
  • Folder structure planned

Azure AD Preparation (If Using Your Own App Registration)

Not needed for PKCE with a blank Client Id or Device Code, apart from consent to the connector's app registration.

  • Microsoft Login Method chosen (PKCE, Device Code, Modern App Registration or App Registration)
  • Access to Microsoft Entra ID portal
  • Permission to create app registrations
  • Ability to grant admin consent (or users are allowed to consent to the connector's app registration)
  • Callback URL determined (.../OAuthLanding.htm for PKCE and Modern App Registration, ...?page=70319501 for App Registration)
  • Redirect URI on the right platform (Web, or Mobile and desktop applications for PKCE)

Business Central Preparation

  • Admin access to Business Central
  • Sandbox environment available for testing
  • User list for permission assignment
  • License information available

SaaS Deployment Checklist

Installation

  • Install app in sandbox environment
  • Verify app appears in Extension Management
  • Open SharePoint Setup without errors

Configuration (Sandbox)

  • Enter Base URL
  • Enter Site Name (if applicable)
  • Enter Base Folder
  • Configure authentication settings
  • Choose the Microsoft Login Method (PKCE is preselected)
  • Enter Client ID (App Registration, Modern App Registration, or PKCE with your own app registration)
  • Enter Client Secret (App Registration, Modern App Registration)
  • Enter Entra Tenant Id (PKCE with a single-tenant app registration, Modern App Registration on-premises)
  • Check Callback URL (filled in when the login method is selected)
  • Allow pop-ups for Business Central (all login methods except Device Code)
  • Click Connect and authenticate
  • Verify connection succeeds (no Test button; connection is validated during Connect)

Table Mappings (Sandbox)

  • Create Customer mapping
  • Create Vendor mapping (if needed)
  • Create additional mappings as needed
  • Configure alternative mappings (if needed)
  • Set up auto-create subfolders (if needed)

Testing (Sandbox)

  • Open Customer Card, verify FactBox appears
  • Upload a test file
  • Verify file appears in SharePoint
  • Download/open a file
  • Test additional mapped tables
  • Test auto-upload (if configured)
  • Test document templates (if configured)

Production Deployment

  • Install app in production
  • Enter registration/license code
  • Replicate configuration from sandbox (see Replicating Configuration Between Environments)
  • Re-enter Client Secret (and any e-signing secrets) in the target environment
  • Connect and verify the FactBox loads
  • Assign permission sets to users
  • Verify user access

Replicating Configuration Between Environments

Instead of re-entering the setup by hand, you can move it from one environment to another (for example, sandbox to production) using a standard Business Central Configuration Package (Configuration Packages page). Add the SharePoint Connector tables below to the package, export from the source environment, then import and apply in the target.

Core Setup Tables (always include)

Table No. Table Name Contents
70319500 SharePoint Setup EFQ Main setup card (Base URL, Client ID, site, base folder, options)
70319504 Table Mapping EFQ Table-to-folder mappings
70319490 SharePoint Map. Metadata2 EFQ Column / metadata mappings
70319483 Alternative Mapping EFQ Conditional (alternative) folder mapping rules
70319491 Auto-Create subfolder EFQ Auto-created subfolders
70319492 Auto-Create subfolder 2 EFQ Conditional auto-created subfolders
70319489 SharePoint Category EFQ File categories
70319503 Document Template EFQ Document templates (Custom Report Layout)
70319495 Document Template RL EFQ Document templates (Report Layout)
70319477 SharePoint Print. Settings EFQ Printer / paper settings

Optional Tables (include only if you use the feature)

Table No. Table Name Include When
70319484 Incoming Source EFQ Using Incoming Documents
70319486 Incoming Match Criteria EFQ Using Incoming Documents
70319480 DocuSign Setup EFQ Using DocuSign
70319482 Adobe Setup EFQ Using Adobe Sign

Important: Secrets Do Not Transfer

Sensitive credentials are stored in Isolated Storage, not in the table fields, so a configuration package will not carry them over. After importing into the target environment you must manually re-enter:

  • Client Secret on the SharePoint Setup, then re-run the OAuth consent/Connect for that environment.
  • DocuSign and Adobe Sign integration secrets, if those features are used.

With App Registration, also confirm the Callback URL on the SharePoint Setup points at the target environment and still contains page=70319501. With PKCE and Modern App Registration, the OAuthLanding.htm Callback URL is the same for all Business Central Online environments and needs no change. PKCE with a blank Client Id needs no secret, so only Connect has to be run again.

Tables to Exclude

Do not add runtime, cache, or transactional tables to the package — they are environment-specific or rebuilt automatically. This includes the SharePoint file list/details, doc signers, runtime upload, background report, incoming document/API content, per-record folder mapping, the subsite cache, the obsolete v1 metadata table, and temporary tables.

On-Premises Deployment Checklist

Pre-Installation

  • Correct app package for BC version
  • Access to BC administration shell
  • BC service is running
  • Outbound internet access verified

Installation

  • Publish extension
  • Sync extension
  • Install extension
  • Verify in Extension Management

Configuration

  • Same as SaaS configuration checklist
  • Verify network access to SharePoint
  • Check firewall rules

Feature-Specific Checklists

Auto-Upload Configuration

  • Enable auto-upload in SharePoint Setup
  • Verify table mappings for posted documents
  • Configure Report Selections
  • Set processing mode (Background/Foreground)
  • Test by posting a document
  • Verify PDF appears in SharePoint

E-Signing Configuration

Adobe Sign

  • Adobe Sign account active
  • API access enabled
  • Enter Adobe Setup configuration
  • Connect and authenticate
  • Test sending document for signature

DocuSign

  • DocuSign account active
  • Integration key created
  • Enter DocuSign Setup configuration
  • Connect and authenticate
  • Test sending document for signature

Metadata Configuration

  • Identify fields to map
  • Create metadata mappings
  • Configure field types
  • Upload file to test
  • Verify columns appear in SharePoint
  • Configure print folder
  • Set paper size
  • Test printing a report
  • Verify file appears in SharePoint

User Rollout Checklist

Permission Assignment

  • Identify users needing access
  • Assign SP Conn. User EFQ permission set
  • Verify users have BC base permissions
  • Verify users have SharePoint permissions

Training

  • Prepare training materials
  • Schedule training sessions
  • Demonstrate key features
  • Provide documentation access
  • Establish support process

Go-Live

  • Communicate go-live date
  • Monitor for issues
  • Provide support contact
  • Gather feedback

Post-Deployment Checklist

Verification

  • All configured features working
  • Users can access as expected
  • No error reports
  • Performance acceptable

Documentation

  • Record configuration settings
  • Document customizations
  • Note any issues encountered
  • Update internal documentation

Maintenance Planning

  • Establish update process
  • Plan for periodic review
  • Monitor for publisher updates
  • Schedule periodic permission review

Rollback Plan

If Issues Occur

  • Document the issue
  • Attempt resolution
  • If critical, consider rollback
  • Communicate with users

Rollback Steps

  • Disable auto-upload (if problematic)
  • Revert configuration changes
  • Uninstall app (if necessary)
  • Contact support