This feature is now available as part of the July 2025 SmartConnect Update.

1. Click on the Target tab.
2. Target – select Dynamics 365 Business Central Odata Api.

1. Destination – select a Dynamics 365 Business Central connection.
2. API Route – select an API to be used.
3. Add Service button – Select a BC API Service for mapping.
4. Add Action button – Select from all available actions to add for mapping.
5. Rollback document on failure – If checked, a document header will be deleted if a document line fails.
6. Send to file – If checked, an integration run will generate a file using the source data. No data will be sent to Business Central.
7. Once the required fields have been populated the Integration tab becomes active.
8. Click on the Integration Tab.

Adding a Child Endpoint

Once a service has been selected, the child service option can be used. Child services will be used any time a detail or line endpoint needs to be sent with the header service.

1. Click the Child Endpoints button to select a child endpoint for the selected parent service, this will open the Add Service window and show the related services. Choose a child service.
2. Click the ellipses button on the parent service to add a parent field.  This will link the services together when mapping without having to do a lookup to get the parent document id.
3. Click the Add parent field button to select a field from the parent service that can be used on the child service. This field will be mapped on the child node during the mapping process.
4. Parent Field No Data Options can be set for when no data is returned for the Parent field. Options include:

• Continue – If the header parent field returns no data, the lines will continue to run
• Return default value – If the header parent field returns no data, the lines will use this defined default value
• Return failure for current integration line – If the header parent field returns no data, the lines will return a failure
• Restrict line out if no data exists – If the header parent field returns no data, the lines will not be sent
• Restrict line out if data exists – If the header parent field returns data, the lines will not be sent
• Return null – send a null

5. Parent Actions are like the Add Actions button above but are specific to the Parent Service.  If added, the action will automatically be performed to the document without having to map any fields. Click the Add Action button in the Actions section to select an action.
6. Click OK to save Parent Fields and Actions. The parent field will now be available in the mapping section. Set the Column Type to Parent Source Column to access available parent fields.

Integration Tab

1. Target Lines – from the dropdown list select the lines that will be mapped.
2. For Delete – not used for this destination type.
3. Update Existing – when this checkbox is marked, records that already exist will be updated with any changes.
4. Update Blank Data – not used for this destination type.
5. Source Grouping tab – select which source(s) to group by and the function for the source.
6. Target Integration tab – this is where the Source data is mapped to the Target data.
7. Additional Columns tab – note: there will be a separate section for each type of Additional Column.
8. Once the Target field(s) are mapped to a Source(s), the Save button becomes active allowing the user to save the Integration Process.