Set up product field mapping in Dynamics 365
|
PREREQUISITES Before you can map product fields, you must first install, connect, and assign roles for the Oneflow for Dynamics 365 integration. Make sure you have the Oneflow Admin role assigned to access the Oneflow settings page. |
|
RELATED ARTICLES |
Product field mapping syncs line-item product data from Dynamics 365 into your Oneflow contract templates.
Navigate to product field settings
-
In Dynamics 365, click the current app name (e.g., Sales Hub) to go to the apps page.
-
Select Oneflow Administration.
NOTE
If you use an older version of Dynamics 365:
- If you use an older version of the integration (before 3.8.0.8), then Oneflow Settings appears under the main Settings menu in the Advanced settings page of the legacy UI of Dynamics 365.
- If you use an older version of the integration (before 3.8.0.8) with the new Dynamics 365 UI, then Oneflow Settings appears in the side panel in the Advanced settings page of Dynamics 365.
-
Open the Setup Entities tab. From the list on the left, select the entity you wish to configure (e.g., Opportunity, Quote). To add a new entity, select an entity from the dropdown list and click Configure entity.
-
Click on the Products sub-tab
5. Ensure the Transfer products toggle is enabled to transfer products from Dynamics to your Oneflow contracts, and select a source for product information (i.e. Opportunity product).
|
INFORMATION Product table configuration: |
Configure product fields
Product mapping and sync settings:
There are two product mapping behaviors based on the source of product data:
1. Out-of-the-box Dynamics entities (Opportunity Product, Quote Product)
- These entities have fixed discount and pricing logic that cannot be modified.
- Key fields like Quantity and Price are locked and cannot be remapped.
- Two-way (Bidirectional) sync is disabled for some fields due to the product catalog data structure in Dynamics.
| NOTE You can override how the product list is initially pushed from Dynamics to Oneflow at contract creation, but not the ongoing two-way sync behavior for these entities. |
2. Custom product entities (“Create from Anything”)
- For custom product entities (like "Invoice"), all fields are mappable.
- You can define your own pricing, discount, tax, and freight logic.
- You can select a Sync direction for each field mapping:
- Sync once: The product field will be synced (from Dynamics to Oneflow) only when you create a contract.
- Dynamics to Oneflow: Allows you to push any changes to Dynamics product fields back to product fields in the Oneflow contract using the Push updates to Oneflow button.
- Two-way Sync: In addition to the above, two-way sync will automatically update Dynamics product fields when their corresponding product fields change in Oneflow.
|
NOTE Product sync always starts from Dynamics to Oneflow. Updates from Oneflow to Dynamics are not supported for product data, with some exceptions for two-way sync (see Limitations). |
Additional product sync configuration
-
Product ordering and template overwrite:
- Order products by: Choose the field that defines product sequence in the product table of the Oneflow contract.
- Overwrite template products: Replaces template products with the synced products from Dynamics.
- Discount, Tax, and Freight mapping: These sections show how these values are sourced from Dynamics. For custom entities, these mappings are read-only, and you can set Sync once or Dynamics to Oneflow as the direction. Syncing back from Oneflow to Dynamics is not available.
Push updates to Oneflow
Any time the Push updates button is used, it will refresh the product table in your Oneflow contract.
- Any products that are deleted from the product list will be removed in Oneflow, and any new products will be fetched from Dynamics and created in your contract.
- As for existing products, the integration will respect your selected sync direction for each field. Only product fields set to either Dynamics to Oneflow or Two-way sync will be updated.
- If you add any product to your Oneflow contract manually, these will remain untouched, and will not be removed during the Push updates process.
|
NOTE Pushing updates to Oneflow will only update product fields with a sync direction of Dynamics to Oneflow or Two-way sync. Product fields set to Sync once will not be overwritten. |
Fetch updates from Oneflow
Fetching updates is done automatically through webhook events. However, if the contract is not yet sent, then the Fetch Updates from Oneflow option can be used to pull updates from Oneflow back to your Dynamics instance. This option can also be used if you decide to not set up webhooks for your Oneflow integration.
- Any products deleted from your product table in Oneflow will not be deleted in Dynamics.
- If you create new products in your Oneflow contract, these will not be pulled to your Dynamics instance.
- For any other changes, the Oneflow integration will respect your selected sync direction for each specific field in your product line item. Only product fields set to Two-way sync will be updated.
Limitations
- Sales Module products
- The Two-way sync direction can be selected only for
Price per unitandQuantityfields.- Two-way sync direction can be enabled for price per unit, however, it will work only for write-in products.
- The Two-way sync direction can be selected only for