Configuring Incoming Sources

This page explains how to configure sources for incoming document processing in the SharePoint Connector.

Source Configuration

Accessing Source Setup

The source list cannot be found with Tell Me search:

Open SharePoint Setup
Choose the Incoming Document Sources link in the Incoming Documents section
The list page shows configured sources

Creating a Source

Click New
Enter source details
Configure settings
Save

Source Fields

Basic Configuration

Field	Type	Description
Source ID	Code[20]	Unique identifier
Type	Enum	SharePoint Folder, Https File List, API Endpoint
Description	Text[100]	Human-readable description

Note: The table caption for this record is "Incoming Document Source".

Location Settings

Field	Type	Description
Folder/URL	Text	For SharePoint Folder sources: the complete server-relative path of the folder to monitor (e.g., `/Shared Documents/Incoming`). For Https File List: the URL. Ignored for API Endpoint sources

Processing Options

Field	Type	Description
Remove after import	Boolean	Delete from source after processing. Only has an effect for SharePoint Folder sources; ignored for Https File List and API Endpoint

Source Types

SharePoint Folder

Monitor a SharePoint folder for new documents:

Field	Value
Type	SharePoint Folder
Folder/URL	Complete server-relative path of the folder to watch

The Folder/URL field must contain the full server-relative path, including the document library. Use the assist-edit (...) on the field to pick the folder.

Example:

Type: SharePoint Folder
Folder/URL: /Shared Documents/Incoming

Https File List

Retrieve files from an Https endpoint:

Field	Value
Type	Https File List
Folder/URL	HTTPS URL

Useful for integration with external systems that expose files via HTTP.

API Endpoint

Receive documents pushed from external systems. Unlike the other types, this source is push-based: the connector does not poll anything -- external systems submit documents through the connector's own API. The Folder/URL field is ignored for this type.

Field	Value
Type	API Endpoint
Folder/URL	(ignored for this type)

For custom integrations where an external system delivers documents to Business Central.

The Upload API

Documents are submitted to the connector's API page (IncomingAPI EFQ, publisher efoqus, group automation, version v2.0, entity uploadDocument):

.../api/efoqus/automation/v2.0/companies({id})/uploadDocument

Create an uploadDocument entity with sourceID (the Source ID of the API Endpoint source), fileName, and base64-encoded documentContent, then call one of the bound actions:

Action	Behavior
Upload	Store the document in the incoming documents queue
UploadAndProcess	Store the document and run matching criteria immediately
UploadAndProcessWithImport	Store, match, and -- if a match is found -- import to SharePoint immediately

Configuration Examples

Simple SharePoint Folder

Monitor main incoming folder:

Field	Value
Source ID	INCOMING
Type	SharePoint Folder
Description	Main incoming folder
Folder/URL	/Shared Documents/Incoming
Remove after import	Yes

Vendor Invoice Folder

Dedicated folder for vendor invoices:

Field	Value
Source ID	VEND-INV
Type	SharePoint Folder
Description	Vendor invoices
Folder/URL	/Shared Documents/Purchasing/Incoming Invoices
Remove after import	Yes

Customer Documents Folder

Folder for customer-submitted documents:

Field	Value
Source ID	CUST-DOCS
Type	SharePoint Folder
Description	Customer documents
Folder/URL	/Shared Documents/Sales/Customer Submissions
Remove after import	No

Multiple Sources

When to Use Multiple

Create multiple sources for:

Different document types
Different departments
Different processing rules
Different retention needs

Source Management

Each source:

Has its own criteria
Processes independently
Can have different settings

Processing Configuration

Remove after import

Setting	Behavior
Yes	File deleted from source after processing (SharePoint Folder sources only)
No	File remains in source

Note: Remove after import only works for SharePoint Folder sources. For Https File List and API Endpoint sources the setting is ignored -- files always stay at the source.

Recommendation:

Yes for one-time processing
No if source is also an archive

Subfolder Routing

Documents can be routed to optional subfolders:

Configure in matching criteria
Different document types to different subfolders

Folder Structure

Source Folder Setup

Create your source folder in SharePoint:

Navigate to SharePoint library
Create the incoming folder
Configure permissions
Note the path for BC configuration

Example Structure

SharePoint Library
├── Shared Documents/
│   ├── Incoming/              ← Source folder
│   │   ├── (documents land here)
│   ├── Customers/             ← Destination
│   │   └── [Customer Folders]
│   └── Vendors/               ← Destination
│       └── [Vendor Folders]

Permissions

Source Folder Permissions

The connector needs:

Permission	For
Read	List and read files
Delete	If Remove after import = Yes

User Permissions

Users processing incoming documents need:

Access to incoming documents list
SharePoint permissions on folders

Processing Incoming Documents

Manual Processing

Go to SharePoint Incoming Documents list
View documents from configured sources
Review matches
Approve/process documents

Automatic Processing

If configured:

Documents scanned automatically
Matching applied
Routing performed
Manual review of exceptions

Troubleshooting Sources

Source Not Finding Files

Check	Resolution
Path correct?	Verify folder path
Files in folder?	Confirm files present
Permissions?	Check SharePoint access
Connection?	Test SharePoint connection

Files Not Processing

Check	Resolution
Criteria exist?	Configure matching criteria
Criteria match?	Test criteria patterns
Destination exists?	Verify table mapping