This article focuses on the go-live steps for new SmartConnect integrations when moving from a Business Central Sandbox environment to a Production environment. These steps are crucial for transitioning to the live environment. Before following this article all integrations should undergo thorough testing within the Business Central Sandbox environment.
Prerequisites
- Install the SmartConnect Change Tracking Extension from AppSource into the Production Business Central environment.
- Ensure that the Change Log Activated flag is turned on in the BC Production environment.

- Go to Setup > Tables.
- Enable logging for any tables that will serve as a Change data source, Setup as BC Sandbox Environment.

- Check that all Web Services published in the Business Central Production environment are replicated correctly from the Business Central Sandbox Environment.
Best Practices
- We recommend using Integration Groups to organize integrations in SmartConnect.
- Maintain a structured Name for Data source and integration. For example, Use a prefix of PROD for Production data sources and integrations.
- Example in Sandbox: SAND_ITEMS_CRM_TO_BC
- Example in Production: PROD_ITEMS_CRM_TO_BC
Connection setup
We typically recommend setting up and maintaining two Business Central connectors, but you can update the existing connector with Production details instead. Both methods are outlined here.
- Create a Business Central Production connection in SmartConnect.
- Export the Sandbox version of all integration processes that are tested with the Sandbox and ready to move to the Production connector.
- Import the integration processes using the Production connector.
- Change the integration name to have a prefix of “PROD_”
- Use the Create New Source tab – to create a new data source for the BC Production and add a prefix of “PROD_”
- Open every Business Central destination integration and check the following:
- On the Target tab, make sure the correct connector and company is selected
- If using custom defined companies, modify the JavaScript to reference the new company names.
- On the Options tab, make sure the integration group is the Production group and the logs are enabled.
- On the Tasks tab, make sure all Run Integration tasks reference the production version of the integrations not the sandbox version.
- On the Target tab, make sure the correct connector and company is selected
- Update connector details with Production Business Central tenant ID and select default company.
- Revalidate the Connection.
- Open every Business Central data source and check the following:
- Correct Company is selected
- No errors when clicking Validate or Preview

- Open every Business Central destination integration and check the following:
- Correct Target Company is selected
- If using custom defined companies, modify the JavaScript to reference the new company names.
- No errors when Opening or Saving the integration
- Correct Target Company is selected

Registering triggers
If any of your integrations are using Change or Realtime data sources, they will not be registered to track changes by default.
Change Data Sources
Every Change Data Source integration needs to be registered after changing connectors.
- Open each integration process.
- Switch to the Source tab.
- Check the box to Create, Update, or Delete, and save the integration.

Realtime Data Sources
Every Realtime data source integration will need to be registered after changing connectors.
- Open Data Sources > Realtime Triggers
- Open every production data source and do the following:
- If selected, uncheck the boxes for Trigger on Create and Trigger on Update then click Register
- Reselect the boxes for Trigger on Create and Trigger on Update then click Register

Schedule Setup
New schedules must be added for any change or bulk data source integration.
- Before scheduling integrations, manually run them to ensure there are no errors.
- Create a new integration schedules.
- Make sure the user assigned to the integration schedule is the correct user to be notified of errors.
Conclusion
Before celebrating your successful integration go-live, we recommend using the SmartConnect documentation tool to export definitions of every integration and save them somewhere safe for the future.
For future modifications, for example, if you need to add fields to the integration, we advise manually configuring the test BC integrations before manually updating the Business Central production integrations.
If you have any questions you can reach out to support@eonesolutions.com for assistance.