--- title: "Setup and Configuration" slug: "setup-and-configuration-2" description: "Configure Global Master Setup in Business Central with Company Type, Partner ID, External File Account, OAuth2, and Job Queues for data synchronization." tags: ["Job Queue Entries"] updated: 2026-11-04T14:25:17Z published: 2026-11-04T14:25:17Z canonical: "docs.abakion.com/setup-and-configuration-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.abakion.com/llms.txt > Use this file to discover all available pages before exploring further. # Setup and Configuration ## Feature Overview Before Global Master Data Sync can exchange any data between companies, each participating company must be configured to tell the app what role it plays in the synchronization landscape. This is done in the **Global Master Setup** page, which is the single configuration record for the current company. Every company that participates in synchronization — whether it sends data, receives data, or does both — must complete this setup. The setup revolves around three decisions. First, you assign a **Company Type** that determines whether this company acts as a Master (the source of truth that owns and distributes data templates), a Subscriber (a company that receives and applies synchronized data), or both at the same time. Second, you assign a globally unique **Partner ID** that identifies this company to every other participant in the synchronization landscape — this ID is embedded in every file and record exchanged, so it must be unique across all environments. Third, you choose an **Import Method** — the transport mechanism used to move data files between the Master and its Subscribers. New installations should choose **External File Account**, which integrates with Business Central's built-in file account framework and supports a variety of connectors (SharePoint, Azure Blob, SFTP, and others). The **Azure Blob Storage** method is also available for existing installations where direct connection details are managed manually, but new setups should prefer External File Account since Blob Storage is being phased out. The setup page also controls a set of behavioral switches that govern how the Master pipeline produces and distributes files, how the Subscriber pipeline imports and synchronizes them, and how errors are handled. The **Connection Information** group on the same page gives the information a partner needs to configure a Web-service connection back to this company. Job Queue entries that drive the automated pipelines can be created directly from the setup page with a single action. A Subscriber that wants to request specific records from a Master on demand — rather than waiting for the next scheduled sync — registers that Master's connection details in the **Partner Web Service Info** list, also opened from an action on this page. ### Key Facts | Topic | Detail | | --- | --- | | Main page | Global Master Setup | | Additional pages | GM Tenant Connector Codes, Global Master Template Packages, Partner Web Service Info List | | Company Type options | *(blank)*, Master, Subscriber, Master and Subscriber | | Master flags | Master Auto Update Record Set, Master Create IC Files, Master Exchange Record Set | | Subscriber flags | Subscriber Handle IC File, Subscriber Synch. Record Set | | Import Method options | External File Account (recommended), Azure Blob Storage (being phased out) | | Job Queue | Two entries created by the setup action: one for the Master pipeline, one for the Subscriber pipeline | | Authentication (Web-service) | OAuth 2.0 client credentials via GM Tenant Connector Codes | | On-demand record requests | A Subscriber with Partner Web Service Info configured can request and pick specific records from a Master on demand, in addition to the scheduled sync pipeline | --- ## Getting Started The steps below take a consultant from a fresh app installation to a running synchronization between one Master company and one Subscriber company. 1. **Open Global Master Setup in the Master company.** Search for *Global Master Setup* in the Business Central search bar. The page opens automatically on a single record; if none exists it is created on first open. 2. **Set Company Type to Master.** In the **General** group, choose *Master* from the **Company Type** field. The Master Company group of fields becomes active. The system sets reasonable defaults: Master Auto Update Record Set, Master Create IC Files, and Master Exchange Record Set are all enabled. 3. **Enter a Partner ID.** Type a short, unique code in the **Partner ID** field. This code identifies the Master company in every exchanged file. It must not already exist as a Partner record in the same environment, and it must be unique across every company that participates in your synchronization landscape. 4. **Choose an Import Method.** In the **General** group, set **Import Method** to *External File Account*. In the **Subscriber Company** group, locate the **External File Account** sub-group. Click the **Select Account** link (displayed in blue). A lookup of all configured file accounts in Business Central opens. Select the account that will be used to stage synchronization files. The account name and connector type are displayed after selection. If no accounts exist yet, set one up first via the Business Central **File Accounts** page and return here. 5. **Test the storage connection.** From the action bar, use **Storage Connection > Upload test file** to confirm that the selected file account is reachable and writable. Then use **Download test file** and **Delete test file** to verify round-trip connectivity. 6. **Create the Job Queue entries.** From the action bar choose **Create Job Queue Entries**. Confirm the prompt. For a pure Master company, one job is created: *Global Master: Create and send IC File Logs to Subscribers*, scheduled to start at 06:00. Both entries are created in **On Hold** status and must be activated before the automated pipeline starts. 7. **Open Global Master Setup in the Subscriber company.** Switch to the Subscriber company and open Global Master Setup. Set **Company Type** to *Subscriber*. The Subscriber Company group activates and defaults are applied: Subscriber Handle IC File and Subscriber Synch. Record Set are enabled, Only Synch. Net Changes is enabled, and Reset No. Of Synchronization Attempts (Hours) is set to 24. 8. **Enter the Subscriber's Partner ID.** Provide a unique Partner ID for this company — different from the Master's Partner ID. 9. **Choose an Import Method and configure the External File Account on the Subscriber.** Set **Import Method** to *External File Account*, then use the **Select Account** link in the Subscriber Company group to choose a file account. This should point to the same shared storage location used by the Master — both sides must read and write files to the same container or folder. 10. **Set the Subscriber Log Creation Policy.** Choose an appropriate option from **Subscriber Log Creation Policy**: *None* creates no log entries, *Success and Errors* logs everything, *Errors* only logs failures (the default), and *Success* only logs successful synchronizations. 11. **Set Maximum No. of Attempts and reset hours.** Review **Maximum No. of Attempts to Synchronize** (default 5, up to 100) and **Reset No. Of Synchronization Attempts (Hours)** (default 24). These control how the Subscriber handles records that fail to synchronize — the auto-reset means skipped records are retried automatically after the specified number of hours. 12. **Create the Subscriber Job Queue entry.** From the action bar choose **Create Job Queue Entries** on the Subscriber. One job is created: *Global Master: Import, update and synchronize Record Data*, scheduled to start at 06:15. Activate this entry when ready to begin synchronization. > **Note on Master and Subscriber in the same company:** If a single company acts as both Master and Subscriber (Company Type = *Master and Subscriber*), both job queue entries are created together. The Master job is offset to 06:10 and the Subscriber job to 06:05 to avoid collision. --- ## Related Features The Global Master Setup is the gateway to the rest of the app. A company must have a valid Company Type and Partner ID before any Data Templates can be created (Master) or imported (Subscriber) — changing or clearing these fields is blocked if templates already exist. The transport configured in the setup is used by every Partner record on the Master side; each Partner can override the transport type, but the Import Method and External File Account fields on the Global Master Setup serve as the default for the owning company. The Job Queue entries created from the setup page drive both the Master pipeline (which packages and distributes data) and the Subscriber pipeline (which imports and applies it), and both pipelines read their behavioral switches directly from this setup record. Template Packages — pre-built collections of Data Templates distributed by Abakion — can only be imported on a company configured as Master, and the import wizard is accessed from the **Global Master Template Packages** page. The GM Tenant Connector Codes page, also accessible under Administration, holds the OAuth 2.0 credentials that allow a Master to push data to Subscriber companies via web services rather than a shared file account; each Partner record references one connector code when the Web-service transport type is chosen. The same connector codes are reused by **Partner Web Service Info**, which a Subscriber configures to enable on-demand, user-picked record requests from a specific Master — see Data Templates for the **Exchange only Selected Records** template setting this depends on, and Record Data and Synchronization for how requested records are then transferred. --- ## User Stories ****Configure Master company**** **As a** functional consultant setting up a new Global Master Data Sync installation **I want to** designate a Business Central company as the Master and assign it a unique Partner ID **So that** it can own and distribute Data Templates to Subscriber companies **Setup:** 1. Open **Global Master Setup** in the company that will act as the Master. 2. Set **Company Type** to *Master*. 3. Enter a unique value in **Partner ID** (letters and numbers only, no spaces). This ID will identify this company in every file exchanged. 4. Verify that **Master Auto Update Record Set**, **Master Create IC Files**, and **Master Exchange Record Set** are all enabled (they default to on when you select the Master role). 5. Save the record. > **Note:** The Partner ID cannot be changed once Data Templates referencing it have been created. Plan the ID carefully before releasing any templates. ****Configure Subscriber company**** **As a** functional consultant setting up a receiving company **I want to** designate a Business Central company as a Subscriber **So that** it can receive and apply synchronized master data from a Master company **Setup:** 1. Open **Global Master Setup** in the Subscriber company. 2. Set **Company Type** to *Subscriber*. 3. Enter a unique **Partner ID** for this company (different from the Master's Partner ID and from every other participant's ID). 4. Verify that **Subscriber Handle IC File** and **Subscriber Synch. Record Set** are enabled. 5. Set **Subscriber Log Creation Policy** to the desired level (*Errors* is the default). 6. Review **Maximum No. of Attempts to Synchronize** and **Reset No. Of Synchronization Attempts (Hours)**. 7. Configure the Import Method and External File Account (see US-05). 8. Save the record. ****Configure Master and Subscriber in the same company**** **As a** consultant implementing a topology where one company both owns templates and synchronizes from another Master **I want to** configure a single company as both Master and Subscriber **So that** it participates in both roles simultaneously **Setup:** 1. Open **Global Master Setup**. 2. Set **Company Type** to *Master and Subscriber*. 3. Enter a unique **Partner ID**. 4. Both the Master Company group and the Subscriber Company group become active simultaneously. Review and configure all flags in both groups. 5. Configure the Import Method and External File Account for the Subscriber transport. 6. Use **Create Job Queue Entries** — both the Master job (starting at 06:10) and the Subscriber job (starting at 06:05) will be created. > **Note:** Both pipelines share the same Partner ID and storage account in this configuration. ****Set up Job Queue entries**** **As a** system administrator **I want to** create the scheduled background jobs that drive the synchronization pipeline **So that** data is exchanged automatically without manual intervention **Setup:** 1. Open **Global Master Setup** on the company where you want to schedule automation. 2. Ensure **Company Type** and **Partner ID** are already set. 3. In the action bar, choose **Create Job Queue Entries** (also available from the promoted **Process** group). 4. Confirm the prompt. 5. The action creates entries that do not already exist: - On a Master or Master-and-Subscriber company: *Global Master: Create and send IC File Logs to Subscribers* (starts at 06:00 for pure Master, 06:10 for Master-and-Subscriber). - On a Subscriber or Master-and-Subscriber company: *Global Master: Import, update and synchronize Record Data* (starts at 06:15 for pure Subscriber, 06:05 for Master-and-Subscriber). 6. Both entries are created in **On Hold** status under the **GM** Job Queue Category, with a 15-minute recurrence interval, a maximum of 10 run attempts, and a rerun delay of 120 seconds. The ending time is 23:00. 7. Open the **Job Queue Entries** page, locate the new entries, and set them to *Ready* when you are prepared to start the pipeline. > **Note:** If a job queue entry for a given codeunit already exists, the action shows a message instead of creating a duplicate. ****Set up External File Account transport (recommended for new installations)**** **As a** consultant setting up file-based data exchange **I want to** connect Global Master Data Sync to an External File Account **So that** the Master and Subscriber companies can exchange synchronization files via a shared, centrally managed file storage **Setup:** 1. Ensure at least one file account is configured in Business Central (**File Accounts** page) using a supported connector — for example Azure Blob Storage, SharePoint, or SFTP. 2. Open **Global Master Setup**. 3. In the **General** group, set **Import Method** to *External File Account*. 4. In the **Subscriber Company** group, find the **External File Account** sub-group. 5. Click the **Select Account** link (shown in blue as *Select Account*). A lookup of available file accounts opens. 6. Select the shared file account. The **Account Name** and **Connector** fields populate automatically. 7. To verify connectivity, use the **Storage Connection** actions in the action bar: - **Upload test file** — uploads a small test file named after the Partner ID. - **Download test file** — downloads it back to confirm read access. - **Delete test file** — removes the test file to clean up. 8. Ensure the same file account (or a compatible one pointing to the same storage location) is configured on every Subscriber that will receive files from this Master. > **Note:** To detach a connected account, click the blue **Detach Account: [name]** link. The account GUID is cleared and the label reverts to *Select Account*. ****Set up Azure Blob Storage transport (being phased out)**** **As a** consultant maintaining an existing installation that uses direct Azure Blob Storage credentials **I want to** configure the Azure Blob Storage transport **So that** the system continues to work with the original connection setup without migrating to External File Accounts **Setup:** 1. Open **Global Master Setup**. 2. In the **General** group, set **Import Method** to *Azure Blob Storage*. 3. The **Azure BLOB Storage** group in the Subscriber Company section becomes editable, and the BLOB Storage actions in the action bar become available. 4. Enter the **Account Name** (the Azure Storage account name, e.g. `mystorageaccount`). 5. Enter the **SAS token** — a Shared Access Signature that grants read/write/delete permissions on the container. 6. Enter the **Container** name (the container within the storage account used for synchronization files). 7. Use the **Test BLOB Storage Connection** actions to verify: **Upload Test File to BLOB Storage**, **Download Test File from BLOB Storage**, **Delete Test File in BLOB Storage**. 8. Ensure all Partner records on the Master also have their **Data Exchange Type** set to *Azure Blob Storage*. > **Note:** Azure Blob Storage is still supported for existing installations, but Microsoft recommends new installations use the External File Account approach, which leverages the platform's built-in connector framework. Expect this transport to be phased out in a future release. ****Set up Tenant Connector for OAuth2 web service transport**** **As a** consultant implementing a cross-tenant topology where the Master pushes data directly via Business Central's OData API **I want to** configure OAuth2 credentials so the Master can authenticate to the Subscriber's tenant **So that** data can be exchanged without a shared file storage **Setup:** 1. On the **Master company**, open **GM Tenant Connector Codes** (search for it or find it under Administration). 2. Create a new line: - **Code**: A short identifier for this connector (e.g. the name of the Subscriber tenant). - **Description**: A descriptive label. - **Microsoft Entra tenant ID**: The GUID of the Subscriber's Azure Active Directory tenant. (The Subscriber can find this on their own **Global Master Setup** page in the **Connection Information** group under *Microsoft Entra tenant ID*.) - **Client ID**: The application (client) GUID of the app registration created in the Subscriber's Entra ID tenant that has permission to call the Business Central API. - **Client Secret**: The client secret value for that app registration (stored encrypted). 3. On the **Partner record** for the Subscriber company, set **Data Exchange Type** to *Web-service* and reference this connector via the **Tenant Connector Code** field. 4. Use the **Test Setup** action on the Partner record to validate that the connector can authenticate and that the Subscriber returns the expected Partner ID and Company Type. > **Note:** The Token Key and Token Expiration Time fields on the connector are maintained automatically — the system caches the access token and refreshes it when it expires. ****Control subscriber log creation policy**** **As a** system administrator **I want to** control how much logging the Subscriber creates during synchronization **So that** I can balance auditability with storage and performance **Setup:** 1. Open **Global Master Setup** on the Subscriber company. 2. Locate **Subscriber Log Creation Policy** in the Subscriber Company group. 3. Choose the appropriate option: - *None* — no log entries are created. - *Success and Errors* — a log entry is created for every synchronized record, regardless of outcome. - *Errors* — only failed synchronizations are logged (default). - *Success* — only successful synchronizations are logged. 4. Save the record. > **Note:** Setting this to *Success and Errors* on large datasets can generate significant log volume. Review the Subscriber Log Entries periodically to manage growth. ****Configure maximum synchronization attempts and auto-retry**** **As a** functional consultant **I want to** configure how many times the Subscriber retries a failed synchronization record and how long before skipped records are automatically retried **So that** transient errors are handled without manual intervention, and persistent errors are surfaced without consuming resources indefinitely **Setup:** 1. Open **Global Master Setup** on the Subscriber company. 2. Set **Maximum No. of Attempts to Synchronize** to the desired value (minimum 1, maximum 100, default 5). When a record fails synchronization, its attempt counter increments. Once the counter reaches this maximum, the record is skipped until it is reset. 3. Set **Reset No. Of Synchronization Attempts (Hours)** to the number of hours after which skipped records are automatically put back into the synchronization queue (default 24, minimum 0). Setting this to 0 disables the automatic reset. 4. Save the record. > **Note:** When a synchronization run processes a record successfully, its attempt counter is reset to zero automatically. ****View Connection Information for sharing with partners**** **As a** system administrator or consultant **I want to** find this company's Microsoft Entra tenant ID, environment name, company ID, and company name **So that** I can share this information with the Master company's administrator to configure a Web-service Tenant Connector pointing to this environment **Setup:** 1. Open **Global Master Setup** on the company that will be referenced as a Subscriber. 2. Scroll to or expand the **Connection Information** group. 3. Note the following read-only values: - **Microsoft Entra tenant ID** — the GUID of this company's Entra ID directory. - **Environment Name** — the name of the Business Central environment (e.g. *Production*, *Sandbox*). - **Company Id** — the GUID that uniquely identifies this company within the environment. - **Company Name** — the display name of this company. 4. Share these four values with the administrator of the Master company. They will be needed when creating a Tenant Connector record pointing to this environment. ****Import standard template packages from Abakion**** **As a** consultant setting up a new Master company **I want to** download and apply the standard Data Template packages published by Abakion **So that** I have a ready-made starting point for common data synchronization scenarios (items, customers, vendors, G/L accounts, etc.) **Setup:** 1. Open **Global Master Template Packages** (search for it or find it under Administration). The page is only available in Master companies. 2. In the action bar, choose **Get standard packages**. Confirm the prompt. The system downloads all relevant packages from Abakion's central storage. Existing packages are replaced. 3. Review the list. For each package you want to apply, ensure **Apply** is checked. You may use **Set "Apply"** to activate or reset the flag in bulk on a selection. 4. If you want to use a different template code from the original, enter a value in **New Data Template Code** on the relevant line before applying. 5. Choose **Apply selected Packages**. Confirm the prompt. 6. The system creates the Data Templates (headers, lines, filters, and sub-template links) in the current Master company and sets their status to **Pending Approval**. 7. Review and release the imported templates before they can be used in synchronization. > **Note:** A package cannot be applied if a template with the same code already exists. Use the **New Data Template Code** field to rename incoming packages when a conflict exists. ****Pause the Master pipeline**** **As a** system administrator **I want to** temporarily stop the Master from creating and sending IC File Logs to Subscribers **So that** I can perform maintenance on templates or partners without affecting Subscriber environments **Setup:** 1. Open **Global Master Setup** on the Master company. 2. In the **Master Company** group, clear the **Master Exchange Record Set** check box. This prevents the pipeline from sending files to partners, even if IC files are still being created. 3. To also stop IC file creation, clear **Master Create IC Files**. 4. To resume, re-enable the relevant check boxes. > **Note:** Alternatively, place the Job Queue entry for the Master pipeline on hold by setting its status to *On Hold* in the **Job Queue Entries** page. This is more targeted because it pauses the entire job, not just one step in the pipeline. ****Pause the Subscriber pipeline**** **As a** system administrator **I want to** temporarily stop the Subscriber from importing and applying new IC files **So that** I can investigate data discrepancies or perform maintenance without new synchronization data overwriting changes **Setup:** 1. Open **Global Master Setup** on the Subscriber company. 2. Clear **Subscriber Handle IC File** to stop the import of incoming IC files. Files will accumulate in the file account but will not be processed. 3. To also pause the synchronization of record data that is already imported, clear **Subscriber Synch. Record Set**. 4. To resume, re-enable the check boxes. > **Note:** Pausing at the Job Queue level (setting the Subscriber job to *On Hold*) achieves the same result more cleanly. ****Delete all Data Templates and reset setup**** **As a** consultant performing a full reset of the Global Master Data Sync installation on a Master company **I want to** delete all Data Templates and their related records in one operation **So that** I can start the template design from scratch without residual data **Setup:** 1. Open **Global Master Setup** on the Master company. 2. From the action bar, choose **Functions > Delete Data Templates**. A wizard opens. 3. Follow the wizard to select which templates to delete. The wizard runs the **Delete Data Templates** report, which removes selected template headers along with all lines, filters, record IDs, field values, file logs, subscriber assignments, and related data. 4. After deletion, the Company Type and Partner ID remain set. If you also need to reset those, change **Company Type** to blank (note: this is only possible when no templates exist). > **Note:** This operation is irreversible. Take a database backup before proceeding in a production environment. ****Resume and activate the synchronization pipeline after initial setup**** **As a** consultant who has completed the initial configuration on both Master and Subscriber **I want to** activate the Job Queue entries so that automated synchronization begins **So that** Master data starts flowing to the Subscriber without further manual intervention **Setup:** 1. On the **Master company**, open **Job Queue Entries**. 2. Find the entry for *Global Master: Create and send IC File Logs to Subscribers*. Set its status to *Ready*. 3. On the **Subscriber company**, open **Job Queue Entries**. 4. Find the entry for *Global Master: Import, update and synchronize Record Data*. Set its status to *Ready*. 5. Monitor the **Master Activities** and **Subscriber Activities** cue tiles on the Global Master Role Center to confirm that files are being created and synchronized. > **Note:** Before activating the pipeline, ensure at least one Data Template has been released on the Master and at least one Partner is configured and not on hold. ****Show files in the connected storage account**** **As a** system administrator troubleshooting a synchronization issue **I want to** browse the files currently present in the connected file storage **So that** I can confirm that files are being written and identify any that have not been processed **Setup:** 1. Open **Global Master Setup**. 2. From the action bar, choose **Storage Connection > Show files** (for an External File Account) or **Show BLOB Storage Files** (when Import Method is Azure Blob Storage). 3. A list of files in the account opens, filtered to files whose names start with the company's Partner ID. Review the files and their timestamps. ****Export and import template packages manually**** **As a** consultant who wants to copy a custom template design between environments or share it with another customer **I want to** export template packages to a file and import them into another Master company **So that** I can replicate template configurations without rebuilding them from scratch **Setup:** 1. Open **Global Master Template Packages** on the source Master company. 2. Use **Functions > Get Templates** to generate packages for any templates that do not yet have a package record. Select the templates you want to include and confirm. 3. Select the package rows you want to export. 4. Choose **Package > Export Packages**. The packages are exported to an XML file. 5. On the target Master company, open **Global Master Template Packages**. 6. Choose **Package > Import Packages** and select the file. 7. Review the imported packages, set **Apply** for those you want to create, and use **Apply selected Packages** to create the templates. ****Set up a Subscriber to request selected records directly from a Master**** **As a** system administrator on a Subscriber company **I want to** register a Master partner's web-service connection details **So that** users on this Subscriber can request and pick specific records to pull from that Master, instead of waiting for the next scheduled synchronization **Setup:** 1. Open **Global Master Setup** on the Subscriber company. 2. In the action bar, choose **Partner Web Service Info**. 3. Create a new line and enter: - **Partner ID** — must be exactly the same Partner ID the Master company uses in its own Global Master Setup. - **Description** — a free-text label for this connection. - **Company ID** and **Environment Name** — the Master's Business Central company ID and environment name. - **Tenant Connector Code** — the OAuth2 connector to use when calling the Master, referencing a record in **GM Tenant Connector Codes**. 4. Ensure a matching connector record exists in **GM Tenant Connector Codes** with valid Microsoft Entra tenant ID, Client ID, and Client Secret for the Master's tenant (see US-07). 5. Once at least one Partner Web Service Info line and a matching Data Template with **Exchange only Selected Records** enabled exist, a **Request Records** action becomes available on the relevant master-data list pages (for example Customers, Vendors, Items) for users on this Subscriber. > **Note:** Requesting records this way opens a dialog where the user can filter and browse the Master's records page by page, select the ones they want, and send the selection back to the Master — which then queues those specific records for transfer. This is a targeted, on-demand pull, separate from the recurring synchronization pipeline. Full template-side configuration (which fields are shown, which templates support selective pull) belongs in the Data Templates and Record Data and Synchronization articles. ## Field Reference ### Global Master Setup page — General group | Field | Where to find it | What it does | Default | | --- | --- | --- | --- | | Company Type | General group | Defines whether this company is a Master (sends data), Subscriber (receives data), Master and Subscriber (both), or not participating. Changing this type is blocked if Data Templates already exist. | *(blank)* | | Partner ID | General group | A globally unique code that identifies this company in every exchanged file and record. Must not match any existing Partner record. Cannot be changed once Data Templates referencing it have been created. | *(blank)* | | Import Method | General group | Chooses the transport used to move synchronization files: External File Account (recommended) or Azure Blob Storage (being phased out). Only assignable on a Subscriber or Master-and-Subscriber company. | *(blank)* | | Modified By | General group (hidden, Additional) | The user name of the person who last saved the setup record. Read-only. | *(automatic)* | | Modified On | General group (hidden, Additional) | The date and time when the setup record was last saved. Read-only. | *(automatic)* | ### Global Master Setup page — Master Company group | Field | Where to find it | What it does | Default | | --- | --- | --- | --- | | Master Auto Update Record Set | Master Company group | When enabled, the master-side record set is refreshed automatically whenever a tracked record is inserted, modified, or deleted. When disabled, the record set must be refreshed manually before IC files can be created. | On (set when Company Type = Master) | | Master Create IC Files | Master Company group | Enables the creation of IC File Logs (the packages containing record set data) for distribution to Subscribers. Uncheck to pause IC file creation without stopping other master pipeline steps. | On (set when Company Type = Master) | | Master Exchange Record Set | Master Company group | Enables sending of IC File Logs to Partners. Uncheck to pause distribution while still allowing file creation. | On (set when Company Type = Master) | ### Global Master Setup page — Subscriber Company group | Field | Where to find it | What it does | Default | | --- | --- | --- | --- | | Subscriber Handle IC File | Subscriber Company group | Enables the Subscriber to import and unpack incoming IC File Logs. Uncheck to pause import without stopping already-queued synchronization. | On (set when Company Type = Subscriber) | | Subscriber Synch. Record Set | Subscriber Company group | Enables the Subscriber to synchronize the unpacked record data into Business Central tables. Uncheck to pause synchronization without stopping file import. | On (set when Company Type = Subscriber) | | Maximum No. of Attempts to Synchronize | Subscriber Company group | The maximum number of times a failed record synchronization is retried before it is marked as skipped. Range: 1–100. | 5 | | Reset No. Of Synchronization Attempts (Hours) | Subscriber Company group | The number of hours after which records that have been skipped (due to reaching the attempt limit) are automatically put back into the synchronization queue. Set to 0 to disable the automatic reset. | 24 | | Only Synch. Net Changes | Subscriber Company group (hidden, Additional) | When enabled, only field values that have actually changed since the last sync are written to the Subscriber record, rather than all fields in the record set. Reduces write volume on high-frequency syncs. | On (set when Company Type = Subscriber) | | Subscriber Log Creation Policy | Subscriber Company group | Controls which synchronization outcomes create a log entry: *None*, *Success and Errors*, *Success*, or *Errors*. | Errors | | Auto Verify Price Line | Special Handling sub-group (Additional) | When enabled, a changed price line record is automatically verified immediately after it is synchronized. Applies only to price line tables. | Off | | Stop Ownership check | Subscriber Company group (hidden, Additional) | When enabled, the app skips the check that prevents a Subscriber from writing to records that are not in its record set. Use with caution — can lead to imbalanced record sets. | Off | ### Global Master Setup page — External File Account group | Field | Where to find it | What it does | Default | | --- | --- | --- | --- | | Select Account / Detach Account | External File Account group | A drill-down link that opens a lookup of all configured Business Central file accounts. Clicking when an account is attached detaches it; clicking when no account is attached opens the selector. Only usable when Import Method is External File Account. | *(none)* | | Account Name | External File Account group | Displays the name of the currently selected External File Account. Read-only; maintained automatically. | *(automatic)* | | Connector | External File Account group | Displays the connector type of the selected account (for example, Azure Blob Storage, SharePoint, SFTP). Read-only. | *(automatic)* | ### Global Master Setup page — Azure BLOB Storage group (fields editable only when Import Method is Azure Blob Storage) | Field | Where to find it | What it does | Default | | --- | --- | --- | --- | | Account Name | Azure BLOB Storage group | The name of the Azure Storage account (the part before `.blob.core.windows.net`). | *(blank)* | | SAS token | Azure BLOB Storage group | A Shared Access Signature providing authenticated access to the container. Stored masked. | *(blank)* | | Container | Azure BLOB Storage group | The name of the blob container within the storage account used to stage synchronization files. | *(blank)* | ### Global Master Setup page — Connection Information group | Field | Where to find it | What it does | Default | | --- | --- | --- | --- | | Microsoft Entra tenant ID | Connection Information group | The GUID of this company's Microsoft Entra ID (formerly Azure AD) directory. Read-only. Share this with partners who need to configure a Web-service Tenant Connector. | *(automatic)* | | Environment Name | Connection Information group | The name of the Business Central environment (e.g. *Production*). Read-only. | *(automatic)* | | Company Id | Connection Information group | The GUID that uniquely identifies this company within the environment. Read-only. | *(automatic)* | | Company Name | Connection Information group | The display name of the current company. Read-only. | *(automatic)* | ### GM Tenant Connector Codes page | Field | Where to find it | What it does | Default | | --- | --- | --- | --- | | Code | GM Tenant Connector Codes | A unique identifier for this connector record. Referenced by Partner records that use the Web-service transport type. | *(blank)* | | Description | GM Tenant Connector Codes | A free-text description to identify the target tenant or partner. | *(blank)* | | Microsoft Entra tenant ID | GM Tenant Connector Codes | The GUID of the Subscriber company's Entra ID directory. Used to form the OAuth 2.0 token endpoint URL (`login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token`). | *(blank)* | | Client ID | GM Tenant Connector Codes | The application (client) GUID of the Entra ID app registration that has API permissions on the Subscriber's Business Central environment. | *(blank)* | | Client Secret | GM Tenant Connector Codes | The client secret value for the app registration. Stored encrypted in Isolated Storage; displayed as masked. | *(blank)* | ### Partner Web Service Info List page | Field | Where to find it | What it does | Default | | --- | --- | --- | --- | | Partner ID | Partner Web Service Info List | Must match the Master partner's own Partner ID exactly. Identifies which Master this connection line addresses. | *(blank)* | | Description | Partner Web Service Info List | A free-text label to identify this connection. | *(blank)* | | Company ID | Partner Web Service Info List | The Master's Business Central company ID (GUID), as shown on the Master's own Global Master Setup Connection Information group. | *(blank)* | | Environment Name | Partner Web Service Info List | The name of the Master's Business Central environment (e.g. *Production*). | *(blank)* | | Tenant Connector Code | Partner Web Service Info List | References the OAuth2 connector (from GM Tenant Connector Codes) used to authenticate calls to this Master. | *(blank)* | ## Related - [Setup and Configuration](/setup-and-configuration-1.md) - [Setup and Configuration](/setup-and-configuration.md) - [Global Master Data Sync](/global-master-data-sync.md)