[Error] The contact cannot be synchronized because the company does not exist.

(0) Share

Report

Posted on by Inkey Solutions

2,102

Hi,

We integrate all the contacts from the CRM to the Contact-Dataverse table, and now

we tried to sync all the contacts from the Contact-Dataverse table to the Contact table in the business central, but we face the error that Company Does Not exist.

However, we have some data from the CRM side that does not contain any company [company name].

Can we sync the data without the company into the contact table? Can anyone please provide a solution for this?

I have the same question (0)

All responses (6)

Answers (2)

Verified answer

Marco Mels on at

Like (2)

Report

Hello,

You are seeing the error "The contact cannot be synchronized because the company does not exist." because our synchronization engine, per default, only allows synchronizing Dataverse contacts that have a parent customer (in other words, once they are synchronized, they are linked to the contact of type "company" of the parent customer in Business Central).

To override this default behavior and allow synchronization of such contacts that do not have a parent customer, you need to add this subscriber in an extension and publish it to the environment (tenant):

[EventSubscriber(ObjectType::Codeunit, Codeunit::"CRM Synch. Helper", 'OnGetIsContactBusinessRelationOptional', '', false, false)]

local procedure HandleOnGetIsContactBusinessRelationOptional(var Optional: Boolean)

begin

Optional := true;

end;

Thanks.

Was this reply helpful? Yes No
Inkey Solutions 2,102 on at

Like (0)

Report

Hi,

Thank You Marco Mels, we will try this solution and keep updating you on this but

We have one question, we have the OOTB Table Config template code field in the Integration Table mapping page, please see below screen print,

Could you please elaborate it when we use this functionality? and we tried this but it did not work, Could you tell us why it is not work?

Thank You.

Was this reply helpful? Yes No
Inkey Solutions 2,102 on at

Like (0)

Report

Hi Marco Mels,

Thank You so much for providing the codeunit solution, This Solution is working fine now in our system.

However, we do have questions,

>> Is this supported way? I meant is it like we can modify any system or custom codeunit this way and override the feature or functionalities OR disable the validation? Please confirm.

>> What if Microsoft upgrade BC version, will it get overwritten again and roll back our change?

Kindly share your insights on the same as soon as possible so that we can determine whether we should do change at Sales side or BC side.

Was this reply helpful? Yes No
Suggested answer

Marco Mels on at

Like (1)

Report

Hello,

For contacts this config template is not enabled. You can verify this by creating a new contact and notice that the new contact template doesn't show up like it does when creating a new contact. This may be a bug. You can however apply the template you created to the contacts so the fields do get updated. I wasn't able to do this for the Type field though.

You may want to raise this to our support desk / partner to so that this can be addressed or verified.

Thanks.

Was this reply helpful? Yes No
Verified answer

Marco Mels on at

Like (1)

Report

Hello,

Due to the nature of BC, you are able to adjust the standard functionality via extensions in BC. If there is an issue that cannot be reproduced in standard BC (without any extension) / CRONUS company, we from Microsoft may ask you to verify if the issue does exist in your production environment without that specific extension. If it does not exist, it is an issue with the extension and you, or your partner needs to look into it yourself.

The extensions will not be overwritten by an upgrade. In Sandbox, you may have to reinstall them after we performed an upgrade.

Thank you.

Was this reply helpful? Yes No
Inkey Solutions 2,102 on at

Like (0)

Report

Thank You So Much for the response.

Was this reply helpful? Yes No