Table Relation in Dataverse integraion

(0) Share

Report

Posted on by Anton Gerasimov

Hi Colleagues!
I have to syncronize Sales Header and Sales Line with Dataverse. So, I've created both tables in Dataverse.
Sales Line's Document.No column lookups to Sales Header Id.
Altpgen made me neccessary fields:
field(46;bctmsprt_SL_DocumentNo;GUID)
{
ExternalName = 'bctmsprt_sl_documentno';
ExternalType = 'Lookup';
Description = '';
Caption = 'Document No.';
TableRelation = "CDS bctmsprt_Sales".bctmsprt_SalesId;
}
field(47;bctmsprt_SL_DocumentNoName;Text[100])
{
FieldClass = FlowField;
CalcFormula = lookup("CDS bctmsprt_Sales".bctmsprt_No where(bctmsprt_SalesId=field(bctmsprt_SL_DocumentNo)));
ExternalName = 'bctmsprt_sl_documentnoname';
ExternalType = 'String';
ExternalAccess = Read;
}
It looks like good.

But I'm getting an error during Full Synchronization job:
The data could not be updated because of the following error: Document No. 102205 must be coupled to a record in Dataverse.
I have empty Table Sales Lines in DataVerse. Sales Header table in Dataverse is synchronized and coupled. Could you help me? Or might share the link with related tables synchronizing.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (11)

Answers (1)

Suggested answer

Marco Mels on at

Like (1)

Report

Hello,

We currently do not have dedicated Dev support via the Dynamics 365 Business Central forums, but I wanted to provide you some additional resources to assist. If you need assistance with debugging or coding I would recommend discussing this on one of our communities.

www.yammer.com/dynamicsnavdev

dynamicsuser.net/.../developers

I will open this up to the community in case they have something to add.

Thanks.

Was this reply helpful? Yes No
Hein Kruger 629 on at

Like (1)

Report

Hi,

I used YUN ZHU's article to do the integration.

https://yzhums.com/17065/

You can also follow this Youtube link from Areopa Webinars.

www.youtube.com/watch

Was this reply helpful? Yes No
Anton Gerasimov 20 on at

Like (0)

Report

Hi Marco! Thank you, I'm trying to get aboard.

Was this reply helpful? Yes No
Anton Gerasimov 20 on at

Like (0)

Report

Hi Hein! Thank you for interesting materials,. But I'm already done it. My issue in having deals with related tables. How can we synchronize a couple of related tables such as Sales Header and Sales Line. Furthermore, this couple has Table relation with a pair of field: Document No and Document type. Corresponding table in Dataverse have a relation buy just one field : Document No. So i need an example with synchronizing a couple of related table.

Was this reply helpful? Yes No
Ashuq123 15 on at

Like (1)

Report

You need to delete the coupled record and re-couple the records after any modification in Dataverse Integration table.

Related>Dataverse >Coupling>Delete Couple.

Was this reply helpful? Yes No
Anton Gerasimov 20 on at

Like (0)

Report

Hi Ashug123! Thank you for advice! Could you be more specific where exactly should i click "related"? In Dataverse Connection Setup form? I have no dataverse option in "related" menu there. But I did uncoupling and coupling for both tables in Integration Table Mapping form (menu "uncoupling - Delete Couplings, then menu coupling - Match-Based Coupling). But the result is the same: Document No. 102205 must be coupled to a record in Dataverse...

Was this reply helpful? Yes No
Suggested answer

Greg Enns 1,106 on at

Like (1)

Report

In the Table Mapping, there is a checkbox called "Sync Only Coupled Records". If you want it to create new couplings, then this needs to be unchecked for the table mapping.

Was this reply helpful? Yes No
Anton Gerasimov 20 on at

Like (0)

Report

Hi Greg! Of course, this option is unchecked ...

Was this reply helpful? Yes No
Ashuq123 15 on at

Like (0)

Report

if you don't see Dataverse under related :

Then go to Assisted Setup make sure the Dataverse Integration is setup

Was this reply helpful? Yes No
Suggested answer

Anton Gerasimov 20 on at

Like (0)

Report

I've managed to solve the problem. The root cause is "document no" field in the Sales Lines table contains just document number not corresponding sales header record system id. The decision is creating extension of sales line table with corresponding sales header system ID field. And match this field with dv sales lines table "document no" field. It might be helpful for any related tables synchronizing.

Was this reply helpful? Yes No