Business Central Addon for RapidStart CRM Setup

High Level Steps

1. Create or use an existing Dataverse enabled environment.
2. Install RapidStart CRM from AppSource on the Dataverse enabled environment.
3. Obtain the Business Central Company System ID.
4. Configure the Integration from within Business Central.
5. Verify the Business Central integration application user role
6. Setup Record Mapping
7. Link Environments (Optional)
8. Install the Business Central Addon for RapidStart CRM from AppSource on the Dataverse enabled environment.
9. Complete in RapidStart Settings app

Before You Begin

Confirm these requirements before starting the Business Central Addon setup:

• Business Central and Dataverse must be in the same Microsoft Entra tenant for Business Central virtual tables.
• Use a human setup administrator with the required Business Central permissions and Dataverse System Administrator access during setup.
• Confirm RapidStart CRM is installed in the Dataverse environment you plan to connect.

Step 3: Obtain Company ID

To obtain your company ID, search Companies in Business Central. Select the target company and press Ctrl+Alt+F1 to open Page Inspection. Copy the ID shown and save it for later.

Step 4: Configure the Integration from within Business Central

Log into the Business Central Environment that you want to connect to.

Take note of the Business Central environment name in the address bar. The URL may also show the company display name, but you already captured the Company System ID GUID in the previous step.

Copy the Business Central environment name to the same notes where you saved the Company System ID GUID.

1. Click on the gear
2. Select “Assisted Setup”

Scroll down to the “Connect with other systems” section and click on “Setup a connection to Dataverse”.

1. Select to Enable data synchronization
2. Select to enable virtual tables and events
3. Click “Next”

Accept the Terms and click “Next”

Accept the connection to Dataverse “Allow Always”, and click OK

Select the target Dataverse enabled environment, and click “Ok”

Confirm the environment is correct, then click the link to Sign in to the Dataverse environment. After signing in click “Next”

Select the recommended Team ownership, toggle to Complete without synchronization (we'll do this later) and click “Next”

1. Click Link to Install Business Central Virtual Table app
2. Click “Next” (A new tab will open to AppSource)

Click the “Get it now” button (This addon is free), and the following page will open:

1. Select the target environment (where you have installed RapidStart CRM).
2. Agree to the terms.
3. Click “Install”.

You will see that the solution is “Installing”. This could take several minutes to complete. Occasionally click “refresh” until you see that it is “Installed”, then go back the Business Central Browser tab to continue.

Click “Refresh”

You will see that the Virtual Tables app has successfully installed. Click “Finish”

After a few minutes this page will appear. Select Virtual Tables Tab and then “Available Virtual Tables”

1. Starting by selecting the “item” line
2. Click “Enable” (This will create the virtual table in Dataverse for items)
3. Wait until you see “Visible” box checked. You may need to refresh a few times.

Repeat these steps for: salesInvoice, salesInvoiceLine, salesOrder, salesOrderLine, salesQuote, salesQuoteLine, salesShipment, and salesShipmentLine. This will take several minutes for each one to enable.

Change to sort by Visible/descending, and confirm you see all of these tables. Do not add more Virtual Tables at this time. You can leave the screen as is (we will come back to it) and open a new tab.

Step 5: Verify the Business Central Integration Application User

If Business Central-Dataverse synchronization permissions appear damaged, open Dataverse Connection Setup in Business Central and use Redeploy Integration Solution. This restores Microsoft's integration solution and deploys the Business Central integration security role.

Continue only after the connection test succeeds and the Business Central integration application user has Microsoft's Business Central Dataverse Integration role.

Step 6: Set up Record Mapping and Coupling

Reference mappings to configure before CUSTOMER

• CURRENCY: Business Central Currency → Dataverse Transaction Currency. Direction must be Business Central to Dataverse. Confirm these enabled field mappings: Code → Currency Code, Symbol → Currency Symbol, and Description → Currency Name.
• Confirm the CUSTOMER mapping contains Currency Code → Currency. Synchronize currencies before customers. The Dataverse base currency and Business Central local currency must agree, and required exchange rates must exist.
• Payment Terms: synchronize to Account Payment Terms before customer testing.
• Shipment Method: synchronize to Account Freight Terms before customer testing.
• Shipping Agent: synchronize to Account Shipping Method before customer testing.

Customer creation policy

Set CUSTOMER to Bidirectional if accounts/companies may be created on either side. Then choose the Sync. Only Coupled Records policy as a customer deployment decision:

Option-value validation

Business Central enum value IDs used for Payment Terms, Shipment Method, and Shipping Agent must match the corresponding Dataverse option IDs. The display text or code label alone is not enough. A full synchronization does not repair an ID mismatch when Business Central contains custom enum values that do not exist in Dataverse.

1. Run Synchronize Modified Records for PAYMENT TERMS, SHIPMENT METHOD, and SHIPPING AGENT.
2. Inspect Dataverse Option Mapping and the synchronization error log before testing CUSTOMER.
3. If IDs are not aligned, use the safe default on the CUSTOMER field mappings: Payment Terms Code → Payment Terms = FromIntegrationTable; Shipment Method Code → Address 1: Freight Terms = FromIntegrationTable; Shipping Agent Code → Address 1: Shipping Method = FromIntegrationTable.
4. Change those three fields to Bidirectional only after a developer has added matching option IDs on both sides.
5. Do not invent or renumber option IDs during setup. Custom Dataverse values and Business Central enum extensions must use exactly the same IDs.

Go back to Business Central tab in your browser that we left open.

1. Click the “Integration” tab
2. then “Integration Table Mappings”

Customer decision: keep SALESPEOPLE if the customer wants Microsoft's standard Dataverse-user-to-Business-Central-salesperson synchronization. Delete or disable this mapping only when that standard synchronization is intentionally not used.

1. Select CONTACT
2. Select Coupling
3. Then click “Match-Based Coupling”.
4. Match the above and click OK

1. Select CURRENCY
2. Select Coupling
3. Then click “Match-Based Coupling”.
4. Match the above and click OK

For CUSTOMER Select Mapping/Fields
1. Select “Edit List”
2. and “enable” Account number.

Still for CUSTOMER, select Coupling/Match-Based Coupling. Match using the customer/account identifier fields shown in the screenshot, and confirm the matching fields uniquely identify the same customer on both sides.

For PAYMENT TERMS, select Coupling/Match-Based Coupling. Match Business Central payment term records to the corresponding Dataverse payment term option values by the configured IDs.

For SHIPMENT METHOD, select Coupling/Match-Based Coupling. Match Business Central shipment methods to the corresponding Dataverse freight term option values by the configured IDs.

For SHIPPING AGENT, select Coupling/Match-Based Coupling. Match Business Central shipping agents to the corresponding Dataverse shipping method option values by the configured IDs.

For VENDOR Select Mapping/Fields
1. Select “Edit List”
2. and “enable” Account number.

Still for VENDOR, select Coupling/Match-Based Coupling. Match using the vendor/account identifier fields shown in the screenshot, and confirm the matching fields uniquely identify the same vendor on both sides.

Step 7: Link Environments (Optional)

To prevent someone from accidentally deleting environments, you can link them. Start back in Business Central.

1. Select the Gear icon
2. Then select Admin Center

Select the target environment link

Click on “Link” and select your Dataverse environment

Step 8: Install the Business Central Addon for RapidStart CRM from AppSource

Click this link to open Microsoft's AppSource and confirm you are logged in with your business account.

Select “Get it now” to initiate the installation.

1. Select the environment where you installed the Virtual Tables solution.
2. Agree to terms.
3. Click Install. Note that installation could take several minutes.

You will see that the solution is “Installing”. This could take several minutes to complete. Occasionally click “refresh” until you see that it is “Installed”.

Step 9: Complete in RapidStart Settings app

Go to RapidStart CRM and select the RapidStart Settings App.

You can open the RapidStart Settings app from the App Selector in RapidStart CRM, or from the maker portal:
1. Select Apps in the sidebar.
2. Click the Run icon for the RapidStart Settings app.

1. Confirm you are in RapidStart Settings App.
2. Select “Apps and Addons” in the sidebar.
3. Click “Configure” for Business Central Addon.

Use this wizard to complete any missing items and manage the connector.

Troubleshooting

Missing connection IDs

If a flow reports a missing connection ID, repair the Dataverse and Business Central connection references in the RapidStart Settings app or Power Automate, then turn the flow on again. Recreating a connection alone is not sufficient if the connection reference is still bound to the old connection.

Currency mapping errors

If CUSTOMER synchronization fails on currency, restore or verify the CURRENCY mapping, confirm Code → Currency Code is enabled, synchronize currencies, and confirm the customer currency exists in Dataverse before retrying CUSTOMER.

Option mismatches

If synchronization fails because a Payment Terms, Shipment Method, or Shipping Agent value is outside the valid Dataverse range, the Business Central enum value ID does not match a Dataverse option ID. Use FromIntegrationTable for the affected CUSTOMER field mapping until matching IDs are deployed.

Couplings pointing to deleted records

If a record appears coupled but synchronization points to a deleted or missing record, remove the stale coupling in Business Central and create a fresh coupling to the correct Dataverse account or contact before rerunning synchronization.