Business Central & Dataverse Sales Order Line Sync Issues

(7) Share

Report

Posted on by NS-21031733-0

Hi everyone,

I'm facing issues syncing Sales Order Line Items from Dynamics 365 Sales (Dataverse) to Business Central (BC). The Sales Orders themselves sync correctly, but the line items fail with the following error:

Error: "Table CRM Product must be mapped to table Standard Text to transfer value between fields ProductId and No."

Note: I am only looking to sync from one direction in all of my integration table mappings if possible. I want data to flow from Dynamics 365 Sales to Business Central.

I already have CRM Products mapped to Business Central Items, and that sync works fine. So, I’m unsure why it’s asking for a mapping to the Standard Text table.

Other Issues: Unit of Measure (UoM) Coupling

Additionally, I can’t couple Dataverse Units to Business Central’s Units of Measure. When trying to set it up, I get this error:

Error: "There is no Integration Table Mapping within the filter. Filters: Table ID: 5404, Type: Dataverse."

This makes me wonder if the UoM issue is affecting the Sales Order Line sync—perhaps Business Central needs a valid UoM mapping for the products on the sales lines?

What I’ve Tried

Confirmed CRM Product → BC Item Mapping – This syncs without issues.

Checked Table Mappings – No clear reason why Standard Text would be required.

Looked for UoM Table Mapping – BC Table 5404 (Unit of Measure) isn’t mapped to a Dataverse table, and I can’t manually couple UoMs.

Attempted Full Resync – Sales Order Lines still fail.

Questions

Why does CRM Product need a mapping to Standard Text if it's already mapped to Items?

Could the missing UoM coupling be the root cause of the Sales Order Line sync issue?

General Confusion on how the Units of measure, Unit Group, Item UoM is supposed to be handled.

Has anyone successfully synced Sales Order Line Items from Dataverse to BC?

Error Details

Sales Order Line Sync Error:

"Table CRM Product must be mapped to table Standard Text to transfer value between fields ProductId and No."

Unit of Measure Coupling Error:

"There is no Integration Table Mapping within the filter. Filters: Table ID: 5404, Type: Dataverse."

Any insights or workarounds would be greatly appreciated!

Thanks in advance!

Categories:

Dynamics 365 general

Screenshot_2.png

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Daivat Vartak (v-9d... 7,833 Super User 2025 Season 2 on at

Like (1)

Report
Business Central & Dataverse Sales Order Line Sync Issues

Hello NS-21031733-0,

You've encountered a complex issue with the Dynamics 365 Sales (Dataverse) to Business Central (BC) integration, particularly concerning Sales Order Line Items and Unit of Measure (UoM) coupling. Let's break down the errors and explore potential solutions:

Understanding the Errors:

"Table CRM Product must be mapped to table Standard Text to transfer value between fields ProductId and No."

This error suggests that the integration is attempting to use the Standard Text table in BC as an intermediary or fallback when it cannot directly map the ProductId from Dataverse to the No. field in the BC Item table.

This often occurs when the integration encounters a product on the Sales Order Line that it cannot find a corresponding mapped Item in BC for.

"There is no Integration Table Mapping within the filter. Filters: Table ID: 5404, Type: Dataverse."

This error confirms that there is no default or configured integration table mapping between the BC Unit of Measure table (ID 5404) and any Dataverse table.

This indicates that the integration doesn't know how to translate UoM values between the two systems.

Root Causes and Solutions:

Sales Order Line Item Sync Issue (Standard Text Error):

Unmapped Products:

The most likely cause is that some of the products on your Sales Order Lines in Dataverse do not have corresponding Items in BC.

Even if most products are mapped, a single unmapped product can cause the entire Sales Order Line sync to fail.

Solution:

Thoroughly verify that every product on your Sales Order Lines in Dataverse has a corresponding Item in BC.

Ensure that the product IDs match exactly between the two systems.

Check for any inactive or deleted products in either system.

Integration Mapping Issues:

Although you've confirmed the CRM Product to Item mapping, there might be subtle issues with the mapping configuration.

Solution:

Review the integration table mapping for CRM Product to Item carefully.

Ensure that the field mappings are correct and that there are no unexpected filters or transformations.

Data Type Mismatches:

There could be data type mismatches between the ProductId and No. fields.

Solution:

Confirm that the data types of the ProductId and No. fields are compatible.

Unit of Measure (UoM) Coupling Issue:

Missing Table Mapping:

The core problem is the lack of a table mapping between Dataverse Units and BC Unit of Measure.

Solution:

Create a Custom Table Mapping:

You will need to create a custom integration table mapping between Dataverse Units and BC Unit of Measure.

You will need to identify the table in Dataverse that stores the Units information. This can be complex, and might require custom work.

Alternative: Use Standard Text as a Workaround (Not Ideal):

As a less ideal workaround, you might be able to use the Standard Text table to temporarily store and transfer UoM values.

However, this is not a robust or scalable solution and should be avoided if possible.

Address UoM Handling:

Understand how UoM is handled in both systems.

In BC, you have "Units of Measure" and "Item Units of Measure".

In Dataverse, you have "Units" and "Unit Groups".

You will need to make sure you understand how these relate, and if you need to create custom logic to handle the conversion.

Sales Order Line Sync and UoM Correlation:

Potential Dependency:

It's highly likely that the missing UoM coupling is contributing to the Sales Order Line sync issue.

BC might be expecting a valid UoM for each product on the Sales Order Line, and the lack of a mapping is causing the integration to fail.

Solution:

Prioritize resolving the UoM coupling issue.

Once the UoM mapping is in place, retest the Sales Order Line sync.

General Recommendations:

Thorough Data Validation:

Perform thorough data validation in both Dataverse and BC to ensure consistency.

Detailed Logging:

Enable detailed logging in the integration to capture more specific error messages.

Microsoft Support:

If you continue to experience issues, contact Microsoft Support for assistance.

Integration Best Practices:

Follow Microsoft's integration best practices for Dataverse and BC.

Key Takeaways:

The Standard Text error indicates a product mapping issue.

The missing UoM coupling is likely a significant contributing factor.

Prioritize resolving the UoM mapping to address the Sales Order Line sync issue.

I hope this helps!

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Was this reply helpful? Yes No
Verified answer

Mansi Soni 8,874 Super User 2025 Season 2 on at

Like (3)

Report

Business Central & Dataverse Sales Order Line Sync Issues

Hello, It looks like Business Central is expecting a mapping between CRM Product and Standard Text instead of CRM Product and Item, which shouldn't be necessary if your product-to-item sync is already working. This might be due to missing or incorrect field mappings in your integration table setup.

The Unit of Measure (UoM) issue is likely a key factor. Business Central requires valid UoM mappings for items in order to process sales order lines correctly. Since BC’s Table 5404 (Unit of Measure) isn’t mapped to a Dataverse table, the system might not be able to recognize UoMs from Sales and apply them to order lines.

To resolve this:
1. Check Integration Table Mappings – Ensure CRM Product is correctly mapped to BC Items and not Standard Text.
2. Map Units of Measure – If BC’s Table 5404 isn’t linked to Dataverse, create a custom mapping to align UoMs from Sales with BC’s UoMs.
3. Validate Field Mappings in Sales Order Line Sync – Ensure UoM, Product ID, and related fields are correctly linked between Sales and BC.
4. Test Sync After Adjustments – Try syncing again after applying these fixes.

Hope this answer will help you!

Regards,
Mansi Soni

Was this reply helpful? Yes No
Vahid Ghafarpour 11,972 Super User 2025 Season 2 on at

Like (1)

Report

Business Central & Dataverse Sales Order Line Sync Issues

If any of the responses helped resolve your issue, please take a moment to mark the best answer. This helps others in the community quickly find solutions to similar problems.

To do this, simply click the "Does this answer your question?" button on the most helpful response and like the helpful posts. If your issue is still unresolved, feel free to provide more details so the community can assist further!

Thanks for being an active part of the Dynamics 365 Community!

Was this reply helpful? Yes No
JaneP11 2 on at

Like (0)

Report

Business Central & Dataverse Sales Order Line Sync Issues

The Standard Text error I've encountered, not asked AI about, comes from the user assigning a standard text to a comment line. this is not supported by CRM and the sync of the comment will fail. An actual missing product will tell you the product is missing from CRM or BC.

Was this reply helpful? Yes No