Overview
Multiple product table support lets you automatically organize products from Microsoft Dynamics into different product tables within your Oneflow contracts. Instead of transferring all products into a single product table, you can group them based on a selected Dynamics product column, such as Product Category or Product Type.
For example, you can route products categorized as "Services" to one product table, "General Goods" to another, and "Maintenance" to a third. This keeps contracts clean, tailored, and eliminates the need for manual product organization after contract creation.
Prerequisites
|
BEFORE YOU BEGIN Ensure:
|
Configure product table mapping
-
In Dynamics 365, click the current app name (for example, Sales Hub) to go to the apps page. Select Oneflow Administration.
- In Oneflow settings, open the Setup entities tab.
- Select the entity you want to configure (for example, Opportunity).
-
Under Entity configuration, open the Products tab.
-
Expand the Product table configuration section and click Configure new template.
-
Select your Oneflow workspace and the Oneflow template you want to map.
- From the Grouping products by column dropdown, select the Dynamics product column that controls how products are sorted (for example, Product Category).
- Expand each product table under Assign values to product tables and select the column values that should route to that specific table.
- Optional: Enable the Set as default table toggle on one table to catch any products that do not match the mapped values.
- Click Save.
|
RESULT Products from Dynamics will now be automatically assigned to the configured tables whenever a contract is created from this template. |
Routing logic and rules
- Exclusive assignment: Each grouping value can only be assigned to one product table. This prevents the same product from being routed to multiple tables simultaneously.
- Multiple values: You can assign multiple different values to the same product table. For example, a single table can be configured to receive both "Services" and "Support" products.
- Default fallback: If a default table is configured, products with unmapped or missing grouping values are safely caught and added there. If no default table is configured, unassigned products are completely excluded from the contract.
Managing configurations
Configured mappings are listed under Configured templates in the Product table configuration section.
| Column | Description |
|---|---|
| Template name | The Oneflow template with product table mapping configured. |
| Grouping field | The Dynamics product column used to group products. |
| Tables | How many product tables are mapped out of the total available in the template. |
| Default table | The product table designated to catch unmapped products (if configured). |
| Workspace | The Oneflow workspace containing the template. |
| Update | The pencil icon opens the mapping interface for editing. |
Editing or deleting a mapping
To update an existing mapping, click the pencil icon next to the configured template, adjust your grouping column or assigned values, and click Save.
|
NOTE In the update flow, workspace and template values cannot be edited. Changing the grouping column may not immediately reset your current configuration. You can switch back to the previous selection and still see the existing mapping. Unsaved changes are not applied until you click Save. |
To remove a mapping entirely, open it for editing and click Delete mapping at the bottom of the dialog, then click Delete to confirm your action.
Troubleshooting
No product tables are available for the selected template
Make sure the selected Oneflow template actually contains product table sections. If the template was built without product tables in Oneflow, there will be no tables available to configure in Dynamics.
No grouping fields are available
If the Grouping products by column dropdown is empty, verify that product mapping is fully configured for the entity and that the selected product source contains supported fields with selectable values.
The selected grouping column shows no column values
If the grouping column displays no assignable values, the selected field may not contain supported categorical data. Select another Dynamics product column or check the field values directly in Dynamics.
Products are not appearing in the expected product table
Verify that the product has a populated value in the selected grouping column in Dynamics, and that this exact value is assigned to a product table in your configuration. Also ensure the contract was created using the template that holds this mapping.
Some products are completely missing
This happens if a product's grouping value is not mapped to any table and no default table is configured. To fix this, map all expected values or designate one product table as the default fallback.
Common use cases
- Product segmentation: Group products by category, type, product family, or business line so each distinct group appears in its own highly visible section.
- Service and goods separation: Separate recurring service items from physical hardware or goods to make quotes easier for customers to review and sign.
- Subscription management: Route support, maintenance, recurring licenses, and one-time onboarding fees into different tables based on billing frequency.
- Cleaner presentation: Tame complex quotes. When a Dynamics opportunity contains dozens of different line items, categorized tables drastically improve the readability of the final contract.