Dynamics 365 Finance & Supply Chain Management (F&SCM) - Native Data Exchange

Overview

The Znode Commerce Connector provides native (out-of-the-box) data exchanges for integrating with Microsoft Dynamics 365 Finance & Supply Chain Management (F&SCM). These exchanges are available through the Add From Library option and allow data to be synchronized between F&SCM and Znode without building custom integrations.

Native exchanges include preconfigured source, destination, and YAML mappings, allowing organizations to quickly configure the connection and begin importing data into Znode.


Prerequisites

Before configuring any F&SCM data exchange, ensure the following information is available.

RequirementDescription
EndpointDynamics 365 F&SCM environment URL (for example: yourorg.operations.dynamics.com)
Access Token URLAzure AD OAuth Token Endpoint (https://login.microsoftonline.com/{TenantID}/oauth2/v2.0/token)
Grant Typeclient_credentials
Client IDAzure App Registration Client ID
Client SecretAzure App Registration Client Secret
ScopeDynamics 365 API scope configured in Azure AD
Note: Contact your Dynamics 365 administrator or implementation partner to obtain the required credentials and endpoint information.


Available Data Exchanges

The following native exchanges retrieve data from F&SCM and import it into Znode.

Data ExchangeDescription
Import Simple ProductsImports simple product data from F&SCM into Znode.
Import Configurable ProductsImports configurable product data from F&SCM into Znode.
Import CategoriesImports category data from F&SCM into Znode.
Import InventoryImports inventory on-hand quantities from F&SCM into Znode.
Import PricingImports pricing information from F&SCM into Znode.
Import AccountsImports customer account information from F&SCM into Znode.


Adding an F&SCM Data Exchange

  1. Navigate to Commerce Connector → Manage Commerce Connector.
  2. Click Add From Library.

           

  1. Select the required F&SCM data exchange.

               

  1. Click Add.
  2. Configure the connection using:
    • Endpoint
    • Access Token URL
    • Client ID
    • Client Secret
    • Scope
  3. Save the configuration.
  4. Review the Mapping configuration.
  5. Run the data exchange.
All native F&SCM exchanges include preconfigured YAML mappings that can be modified to meet specific business requirements.


Understanding Data Exchange Components

Each F&SCM data exchange consists of the following sections.

ComponentDescription
Source ConfigurationDefines how the exchange connects to Microsoft Dynamics 365 F&SCM and retrieves data.
Destination ConfigurationDefines how the retrieved data is processed and imported into Znode.
Mapping ConfigurationDefines how fields from F&SCM are mapped to the corresponding fields in Znode.

Proper mappings ensure that data is imported accurately and populated into the correct destination fields.


Data Exchange Use Cases

Product Import (Simple and Configurable Products)

Purpose

Imports product information from F&SCM into Znode, allowing organizations to synchronize their product catalog between the two systems.

Configuration Overview

  • Source Configuration – Retrieves product data from F&SCM.
  • Destination Configuration – Imports product data into Znode.
  • Mapping Configuration – Maps F&SCM product fields to Znode product fields.

Price Import

Purpose

Imports pricing information from F&SCM into Znode to keep pricing synchronized.

  • Source Configuration – Retrieves pricing data.
  • Destination Configuration – Imports pricing into Znode.
  • Mapping Configuration – Maps pricing fields.

Category Import

Purpose

Imports category information from F&SCM into Znode.

  • Source Configuration – Retrieves category data.
  • Destination Configuration – Imports category data.
  • Mapping Configuration – Maps category fields.

Inventory Import

Purpose

Imports inventory information from F&SCM into Znode.

  • Source Configuration – Retrieves inventory data.
  • Destination Configuration – Imports inventory into Znode.
  • Mapping Configuration – Maps inventory fields.

Account Import

Purpose

Imports customer account information from F&SCM into Znode.

  • Source Configuration – Retrieves account data.
  • Destination Configuration – Imports account data into Znode.
  • Mapping Configuration – Maps account fields.


Monitoring Exchange Execution

Data Exchange Logs

Review the Data Exchange Logs after each execution to verify whether the data exchange completed successfully.

StatusDescription
SuccessData was successfully retrieved from the source system and processed by the destination.
FailedAn error occurred during connection, configuration, mapping, or processing.
Note: If a data exchange fails, review the log details, resolve the reported issue, and run the exchange again.


Znode Import Logs

Znode Import Logs are generated only for exchanges that use the Znode Import process.

These logs indicate whether imported records were successfully processed.

StatusDescription
SuccessRecords were successfully imported into Znode.
FailedOne or more records failed validation or import processing.

To view import errors

  1. Open the Import Log.
  2. Click the View Details (Eye) icon.
  3. Review the reported error.
  4. Correct the source data or mapping configuration.
  5. Run the data exchange again.
Note: Znode Import Logs are generated only after the Data Exchange completes successfully.


Mapping Configuration

The Mapping Configuration defines how data retrieved from Microsoft Dynamics 365 Finance & Supply Chain Management is mapped to fields in Znode.

Mapping Structure

SectionDescription
Left ColumnDestination field in Znode.
Right ColumnSource field in Microsoft Dynamics 365 F&SCM.

Purpose

The mapping configuration is used to:

  • Match source fields to destination fields.
  • Transform data between systems.
  • Ensure accurate synchronization.
  • Support data validation during import.

Example

The following example illustrates how F&SCM fields can be mapped to corresponding Znode fields during an Inventory Import.

 



Important Considerations

  • Ensure all required Znode fields are mapped before running the data exchange.
  • Verify that the source and destination field data types are compatible.
  • Review the mapping configuration whenever changes are made to the source or destination data structure.
  • Validate mappings before executing imports in a production environment.


Important Note on Preconfigured Mappings

All native data exchanges include preconfigured YAML mappings designed to support common implementation scenarios.

The connector provides out-of-the-box mappings only for the predefined attributes included in the standard Znode Product Template. Since custom attributes are implementation-specific and vary based on business requirements, they are not included in the default mapping configuration.

To import data for custom attributes, the corresponding field mappings must be configured manually in the Mapping section before running the data exchange.


The out-of-the-box YAML mapping is configured only for fields that receive data from the source API. Fields that are not populated by the API are included in the mapping configuration with empty mappings 


Recommendation: Review all mappings before moving to production to ensure that all business-critical fields are included.


Known Limitations

  • Mapping requirements may vary depending on the Microsoft Dynamics 365 Finance & Supply Chain Management implementation and data model.
  • Additional custom attributes require manual mapping configuration.
  • When using Transmission Mode – Znode Import with the Default Product Template, the connector automatically maps only the predefined product attributes listed below.
Predefined Product AttributesPredefined Product Attributes
ProductNameProductCode
ProductTypeProductSpecification
SKUFeatureDescription
IsActiveCallForPricing
LongDescriptionColor
ShortDescriptionIsFeatured
BrandNewProduct
TagsShippingInformation
ProductImageGalleryImages
FreeShippingHeight
ShippingCostRulesWidth
WeightLength
MaximumQuantityOutOfStockOptions
MinimumQuantity 
Note: Only the predefined attributes available in the standard Znode Product Template are mapped automatically. Any custom attributes created to meet specific business requirements are not included in the default mapping configuration and must be mapped manually.

Troubleshooting

IssueResolution
Authentication FailureVerify the Client ID, Client Secret, Scope, Tenant ID, and Access Token URL configuration.
Empty Import ResultsReview the Data Exchange Logs and verify that data exists in F&SCM for the configured legal entity.
Import FailuresReview the Znode Import Logs and correct any validation or mapping errors.
Missing Fields After ImportVerify that the required fields are mapped correctly in the YAML configuration.
Special Characters in DataReview and remove unsupported characters from the source data before importing.
Mapping ErrorsValidate the source-to-destination mappings and ensure that compatible data types are used.
Best Practice: If additional fields need to be mapped, download a sample YAML file from an existing native data exchange and use it as a reference when configuring custom mappings.


Summary

The native Microsoft Dynamics 365 Finance & Supply Chain Management data exchanges provide an efficient way to synchronize products, pricing, inventory, categories, and customer accounts with Znode. The preconfigured YAML mappings simplify implementation while allowing customization to meet specific business requirements. Before deploying to production, review and validate all mappings to ensure that the required data is imported successfully.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.