Business Central SharePoint integration for documents people can find
Business Central SharePoint integration links your ERP records to the file libraries you already use. Our consultants set up flows and extensions. They store posted invoices, signed delivery notes, vendor paperwork and project files in SharePoint. We name and tag them the same way. A link on the Business Central record means nobody searches two systems.
Last updated
Why Business Central SharePoint integration helps
Business Central stores attachments on records, and that works for a handful of files. A firm may keep contracts, drawings, certificates and scanned notes against thousands of records. Then a proper document library is the better home. It offers versioning, search and sharing rules. It also keeps large files out of the ERP database.
SharePoint usually comes with Microsoft 365. Its permissions tie to the same accounts people use to sign in to Business Central. Connecting the two lets finance and operations keep working in the ERP. Documents live where the rest of the company works together.
Discuss your document flow →
- ✓Posted sales invoices
- ✓Signed proof of delivery
- ✓Vendor contracts and paperwork
- ✓Project and job files
- ✓Item drawings and specifications
Business Central SharePoint integration routes
There are several routes and they suit different needs. Business Central opens and shares files through OneDrive. OneDrive runs on SharePoint. Power Automate links both products, so Business Central SharePoint integration needs little code. So a flow can react to a posted document and save its PDF into a chosen library.
For tighter control, a developer can use the SharePoint module in the system app. It reads and writes library files directly from AL. There are also AppSource apps that add drag-and-drop document panels to pages. We compare these against your volumes and rules before recommending one.
Compare the options together →- ✓OneDrive file actions
- ✓Power Automate flows
- ✓AL SharePoint module
- ✓Marketplace document add-ons
- ✓Links FactBox on records
How we set up Business Central SharePoint integration
Structure comes first. First, we agree the site and library layout. Then we agree the folder or metadata scheme and the naming pattern. One example is customer number, then type, then document number. A library organized by metadata columns is far easier to search than a deep tree of folders.
Then we build. Flows or extension code create the file, set its metadata from the Business Central record and write the link back. We try everything in a sandbox against a test library. That includes failure cases such as a missing folder, a locked file or an expired connection.
Plan the library structure →- ✓Site and library layout
- ✓Metadata columns versus folders
- ✓File naming pattern
- ✓Who can see what
- ✓Error handling and alerts
What is delivered
When we finish, documents reach SharePoint without anyone saving them by hand. Each carries the customer, vendor or project details you need to filter the library. From a Business Central record a user opens the related files with one click. The files open in the browser.
You receive a description of every flow or extension. You also get the service account and connection it runs under. Finally, we add instructions for what to do when a flow reports a failure. A shared account owns the flows, not an individual. So they keep running when someone leaves.
Ask for a walkthrough →- ✓Automatic document filing
- ✓Record-to-library links
- ✓Flow and connection inventory
- ✓Failure notification routine
- ✓Shared ownership of flows
Pitfalls with document integration
Permissions are the usual surprise. A payroll file in a library the whole company can read is a real problem. SharePoint access is its own set of rules. So we design the two together, library by library. We map each document type to an audience before building anything.
Volume is the next. Large lists and libraries need indexed columns and clear views to stay fast. Flows also have run limits tied to licensing. We size the design for your document counts and keep historic bulk loads separate from the daily flow. We plan for both.
Check your library permissions →- ✓Over-shared libraries
- ✓Flows owned by one person
- ✓Unindexed large libraries
- ✓Inconsistent file names
- ✓Broken links after moves
Business Central SharePoint integration questions
Does Business Central connect to SharePoint out of the box?
Business Central works with OneDrive as standard, letting users open and share files in the browser. Filing into set SharePoint libraries by itself usually needs Power Automate, an add-on or a small extension. It depends on how much control you need.
Can attachments already in Business Central be moved to SharePoint?
Yes. You can export existing attachments and load them into the new library structure. Their record data becomes tags. We treat that as a separate one-time task with its own test run. It stays apart from the flow that handles new documents each day.
Do we need extra licenses for this?
SharePoint is part of most Microsoft 365 business plans. Business Central licenses let you use Power Automate within limits. Whether you need more depends on the connectors and volumes involved. Microsoft publishes the current terms, and we help you read them.
Can Business Central data be shown inside a SharePoint page?
Yes, most simply by embedding a Power BI report built on Business Central data into a SharePoint page. You can also show lists of records through Power Apps or custom web parts that call Business Central APIs. That is a larger piece of work.
What happens if a flow fails to save a document?
The flow logs the failure and sends a note to the mailbox we agree with you. You can then resubmit the document once you fix the cause. We design flows so that a failure never blocks posting in Business Central itself. That keeps the link safe.
Book a discovery call
Let's talk through your move to Business Central.
A focused call with a senior consultant. We learn how your business runs today, give you an honest view on whether Business Central fits, and outline scope and next steps before you commit to anything.
What happens after you send the form