Step
Open Business Central search
Use Alt+Q to open Tell Me and search for Extension Marketplace.
Tacto connect User Guide
New
User Guide
Set up and operate Tacto connect with a clean, controlled export process.
Tacto connect lets Business Central administrators generate CSV exports for Tacto from purchasing and supporting master data, adjust the exported structure without code changes, and deliver the result as a ZIP file, to Azure Blob Storage, or to a local server path in on-premises environments.
Good to know
Tacto connect does not require a custom integration service inside Business Central. The export is started manually from the setup page, and the extension ships with a default configuration for tables and fields that can be refined later.
Getting started
Installation
Install the extension directly from Microsoft AppSource within Dynamics 365 Business Central.
Step
Find Tacto connect
Search for the app, open the marketplace entry and choose Get it now.
Step
Complete installation
Follow the standard Dynamics 365 Business Central prompts.
Important: Allow HttpClient Requests
Because this app requires internet access to communicate with external web services, you must allow it to make HTTP requests. Open the Extension Management page, search for Tacto connect, and open the extension settings. Make sure the Allow HttpClient Requests toggle is enabled.
First steps
Getting started
After installation, Tacto connect creates the setup record automatically and inserts a default export configuration when no table setup exists yet.
Screenshot: screenshot of Tacto Setup
Open the setup page
Press Alt+Q to open Tell Me and search for Tacto Setup. This is the central page for export settings, Azure parameters, and export actions.
- TACTO Export starts the configured export.
- Export Table Config opens the list of configured export tables.
- Azure Connection Test, Azure Upload Test, and Azure Storage Inhalt help validate Azure Blob Storage connectivity.
Review the default configuration
The installation routine inserts a starter configuration for 23 tables, including items, vendors, contacts, purchase documents, posted receipts, posted invoices, credit memos, price list lines, payment terms, locations, shipment methods, and item variants.
Azure defaults are also prefilled when the setup record is created:
- Azure Account Name: tactoexchange
- Azure Container: erp-data
- Azure Blob Folder: navision_template
Configuration
Setup fields explained
The Tacto Setup page adapts to the selected export method and the current deployment model.
| Field | What it does |
|---|---|
| Date Filter | Limits item and posted ledger-related data using a CALCDATE formula such as <-12M>, <-2Y>, or <-180D>. Leave it empty to disable date-based filtering. |
| Use Temp Tables | Builds temporary item, vendor, and contact lists from purchase documents and posted purchase receipts so only records relevant to purchasing activity are exported for selected master-data tables. |
| Export Method | Controls whether the export is delivered as ZIP Download, Azure Blob Storage, or Local Storage. In SaaS, only ZIP Download and Azure Blob Storage are available. |
| Export Path | Required only for Local Storage. Defines the full server path where the CSV files are written in on-premises environments. |
| Azure App ID / Client Secret / Tenant ID | OAuth2 client-credential parameters used to obtain an access token for Azure Storage. |
| Azure Account Name / Container / Blob Folder | Defines the exact Azure Storage target for uploaded CSV files. |
Run the first export without a date filter
For the initial export, leave the date filter empty so Tacto receives a complete data set. For all subsequent regular exports you can set a date filter – for example -30D for the last 30 days – to limit the transfer to records that have actually changed.
Azure mode requires outbound HTTP access
If you use Azure Blob Storage, make sure the extension is allowed to perform HttpClient requests in Business Central. Without that permission, token acquisition and uploads cannot succeed.
Delivery options
Export methods
Each export method uses the same CSV generation logic but delivers the result differently.
ZIP Download
Use this in SaaS when a user wants to trigger the export manually and download a ZIP archive immediately. The extension first stores generated CSV files in the internal Tacto Exported File table and then creates a ZIP archive for the current work date.
Azure Blob Storage
Use this when Tacto should consume exported files from Azure Storage. Tacto connect authenticates with OAuth2 client credentials, uploads each generated CSV as a block blob, and offers built-in actions to test the connection, upload a test file, and list existing blobs in the target container.
Local Storage
Use this only in on-premises environments. Each generated CSV is written directly to the configured server path, which makes it suitable for existing file-based integration jobs or local middleware.
Structure control
Manage export tables and fields
Tacto connect is designed so that administrators can adapt the CSV structure without changing the extension code.
Export Table Setup
Open Export Table Config from the setup page to manage the list of exported tables. Each entry stores:
- Table No. The Business Central table to export.
- Table Name. Filled automatically from table metadata.
- Export File Name. The file prefix used when the CSV file is generated.
The Re-initialize Export Tables action deletes all current table and field definitions and recreates the shipped default configuration.
Screenshot: screenshot of Field Selection Page
Field Selection
Use Edit Fields on a table entry to open the field list. The page lets you add fields from the selected table, review the English field name and caption, and control the sequence used in the generated CSV header.
- Move Up and Move Down change the field order.
- Sort order is automatically normalized in steps of 10 after reordering.
- When a field number is selected, the English field name and field caption are filled automatically from metadata.
Execution
Run an export
The export itself is started from the TACTO Export action on the setup page.
Review setup.
Check the date filter, temporary-table option, and selected export method. If you use Local Storage, verify the export path. If you use Azure, verify all Azure credentials and target fields.
Start TACTO Export.
The extension reads the configured table list, builds the CSV header from the selected fields, applies table-specific filters, and exports only the records that pass the configured scope logic.
Receive the result.
Depending on the export method, the files are downloaded as a ZIP, uploaded to Azure Blob Storage, or written to the local server path.
How the data scope is filtered
| Area | Filter logic |
|---|---|
| Items | If a date filter is set, records are filtered on Last Date Modified to export only newer changes. |
| Purchase receipts, invoices, and credit memos | Posted document tables are filtered by Posting Date when a date filter is active. |
| Purchase lines | Only lines with a non-empty type are exported. |
| Price List Line | Only purchase prices with source type Vendor are exported. |
| Master data with temp tables enabled | Items, vendors, contacts, price list lines, item units of measure, contact business relations, and item variants are exported only when they belong to the temporary scope collected from purchase activity. |
Support & Feedback
We are here to help
Whether you have technical questions, need guidance during your rollout, or want to share feature requests, our dedicated Dynamics 365 Business Central team is ready to assist you. Drop us a message, and we will ensure you get the absolute most out of our apps.