Microsoft is retiring OData page endpoints. This guide shows how to move your SmartConnect maps to the eOne Integration APIs, and where to find every answer along the way.
Why Move to the eOne APIs
The Migration in Five Steps
01
Take inventory
In SmartConnect, review each SmartConnect integration using the Business Central OData Source
02
Install and set up
Install the extension, activate the license and assign permissions. See Overview.
03
Connect SmartConnect
Tick the eOne/core/v1.0 route on your connection. See Working with SmartConnect.
04
Remap each map
Find the endpoint, then match your fields to its columns. See the next section.
05
Test, then switch
Run the new map in a sandbox, compare, then move to production.
Let the Documentation Answer the Questions
Every detail you need for a remap is in the eOne Integration API documentation. Here is where to look:
- Which endpoint replaces my page? Search by the table name, such as “customer” or “sales order”, or browse all endpoints.
- Which column is my field? Every endpoint lists its columns next to the Business Central field behind each one, so your OData field maps across directly.
- How do I skip lookups? Resolver fields take your own keys instead of Business Central numbers.
- What about my custom fields? Extending the endpoints shows how to add them with a companion API.
- Something not working? Start with Troubleshooting.
The same documentation is built into Business Central. Search Tell Me for eOne integration API Documentation.
Moving from the SmartConnect eCommerce Extension
eOne Integration replaces the SmartConnect eCommerce extension and covers everything it did. Your existing keys come with you:
01
Install alongside
Install eOne Integration while the eCommerce extension is still installed.
02
Review the mapping
Open eOne Integration Id Migration. Your eCommerce key fields are already mapped.
03
Run the migration
Choose Run Migration for one company or all of them.
04
Repoint your maps
Move each map to the matching eOne endpoint, matching on Integration Id.
Keep the eCommerce extension installed until every map runs on the new endpoints. Full steps: Integration Id migration.
Use AI to Do the Heavy Lifting
An AI assistant can read both your existing map and our documentation, then draft the remap for you:
01
Export your map
Export the integration from SmartConnect.
02
Point AI at the docs
Give your assistant llms.txt, a map of the documentation written for AI. Every docs page has a Copy site link for AI button.
03
Ask for the remap
Use the prompt below, then review the answer before you change anything.
You are helping me move a SmartConnect integration off Business Central OData pages and onto the eOne Integration for Business Central APIs. 1. Read the documentation index at https://eonesolutions.github.io/eone-bc-integration/llms.txt. 2. Read the migration rules at https://eonesolutions.github.io/eone-bc-integration/odata-migration.md and follow them. 3. For every endpoint you choose, read its topic (the .md link in llms.txt) and use only the columns and actions it documents. Never invent a column. The attached file is my SmartConnect integration export. For each map, answer in the output format the rules page describes: - The replacement endpoint and the topic that documents it. - A table of each OData field, its eOne column, and a note. - Lookups, steps and follow-up maps I can drop, such as number lookups replaced by resolver columns, codeunit calls replaced by bound actions, and separate dimension maps. - Other improvements, such as incremental reads on lastModifiedDateTime or using Document Events instead of comparing records. - Open questions, including anything with no documented match and custom fields that need a companion API. Flag every place the map's behavior would change.
AI gives you a head start and reduces the manual remapping exercise.
Make the Move to the Next Generation of SmartConnect
If you are rebuilding maps anyway, build them once on the new platform. The next generation of SmartConnect is rebuilt for speed and teamwork, with draft mode, role-based security, audit tracking, live monitoring and an MCP server for AI assistants.
Read The Next Generation of SmartConnect, or email sales@eonesolutions.com to get started.
Get Help With Your Migration
Want a hand planning the move? Contact our team or email support@eonesolutions.com.
