Small and medium business | Business Central, N...

Business Central → Dataverse: Integration Table Mapping no disponible en una compañía

(3) Share

Report

Posted on by Rafael_Malo

Hola comunidad, ¿alguno ha trabajado con integraciones de Business Central → Dataverse/CRM mediante Integration Table Mappings personalizados?

Tengo un caso donde se manejan varias compañías dentro del mismo ambiente.

En la Compañía 1, la sincronización de Dimension Values funciona correctamente. Por ejemplo, se crea un Dimension Value 001 y este llega correctamente a Dataverse/CRM.

En la Compañía 2, se crea otro Dimension Value, por ejemplo 002, y el registro existe correctamente en BC, pero no llega a CRM.

Revisando Integration Table Mappings, encontré algo interesante:

En la Compañía 1 existe el mapping FWTDVDIMVALUE, que relaciona DV Dimension Value → CDS fwt_DimensionValue.
En la Compañía 2, este mapping no aparece.
No tenemos errores en Integration Synchronization Errors.
El Dimension Value sí existe correctamente en BC.

Mi duda es: ¿cómo se generan/inicializan estos Integration Table Mappings por compañía? ¿Existe algún setup o proceso de la integración que deba ejecutarse para una compañía cuando este mapping no está disponible?

Aclaro que los Dimension Values de cada compañía no tienen que ser iguales; los códigos son independientes. El problema es que el registro creado en cada compañía debería sincronizarse con CRM según corresponda.

¿Alguno ha tenido un caso similar o sabe qué configuración/proceso debería revisar para regenerar o inicializar estos mappings en una compañía específica?

¡Gracias!

Categories:

Dynamics 365 Business Central

All responses (4)

Answers (0)

Sort by

Natasha Sabelli 14 on at

Like (0)

Report
Copy link

Link copied!

Hi Rafael, this is a common one. Integration Table Mappings for the standard CRM/Dataverse connector tables get created per company, usually the first time you enable Dynamics 365 Connection Setup and run "Recreate all Integration Table Mappings" (or "Recreate All Job Queue Entries") while that company is active. They don't automatically copy over to every company in the environment. That's almost certainly why FWTDVDIMVALUE exists in Company 1 but not Company 2, even though the underlying data looks fine.

To fix it, switch into Company 2, open the CRM Connection Setup (or Dynamics 365 Connection Setup) page, and run "Recreate Integration Table Mappings" from there. That should generate the missing dimension value mapping using Company 2's context. I'd also double check that Company 2 is actually linked to a company record in Dataverse with integration turned on. If that link isn't there, the recreation has nothing to point to and will just quietly do nothing, which lines up with the "no errors logged" behavior you're seeing.

Hope this helps :)
Suggested answer

YUN ZHU 103,085 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

You can use the following features to ensure data consistency across companies; this should help avoid the issue.
Manage master data synchronization
https://learn.microsoft.com/en-us/dynamics365/business-central/admin-sync-master-data?wt.mc_id=DX-MVP-5004336
https://learn.microsoft.com/en-us/dynamics365/business-central/admin-set-up-data-sync?wt.mc_id=DX-MVP-5004336
Suggested answer

Assisted by AI

OussamaSabbouh 19,350 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hello Rafael,
Yes, the fact that FWTDVDIMVALUE exists in Company 1 but not in Company 2 explains the behavior: without an Integration Table Mapping, there is nothing to synchronize, so you may also see no synchronization error. Custom mappings should be initialized per company through the Dataverse setup; Microsoft recommends creating them through the OnAfterResetConfiguration event in codeunit CDS Setup Defaults (7204), then running Dataverse/CDS Connection Setup → Use Default Synchronization Setup in the affected company. I would first run that in Company 2, then verify that FWTDVDIMVALUE, its field mappings, and the related synchronization job queue entry are created. Since this is a multi-company setup, also review the Company ID / Multi-Company Synchronization handling so each company's Dimension Values stay separated in Dataverse. If the mapping still does not appear after resetting the default synchronization setup, then the issue is likely in the custom extension code that creates FWTDVDIMVALUE, especially its OnAfterResetConfiguration subscriber or any company-specific conditions.
Regards,
Oussama Sabbouh
Suggested answer

Grigorios Mavrogeorgis 3,361 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi, Integration Table Mapping is a per company table. Company 2 has its own set of mappings, and if yours was never created there then nothing runs at all which is also why the error log is clean, there is no job to fail.
Those mappings get built when you run Use Default Synchronization Setup from the Dataverse Connection Setup in that specific company. Base app recreates its own, but a custom one like FWTDVDIMVALUE only appears if your extension subscribes to the reset event in CDS Setup Defaults. Check the extension code for that subscriber first. If it creates the mapping in an install codeunit instead, a company added later may never have got it.
So in Company 2, enable the connection, run the default sync setup, then check your mapping and its job queue entry both exist. Job queue entries are per company as well.
Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis