# Error merging third parties

**URL:** <https://www.dolibarr.org/forum/t/error-merging-third-parties/24998>\
**Category:** CRM/SRM Modules\
**Created:** [February 22, 2024, 7:03am UTC](https://www.dolibarr.org/forum/t/error-merging-third-parties/24998 "2024-02-22T07:03:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![faustobe](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/f/edb3f5/32.png) [@faustobe](https://www.dolibarr.org/forum/u/faustobe)\
**Post date:** [February 22, 2024, 7:03am UTC](https://www.dolibarr.org/forum/t/error-merging-third-parties/24998/1 "2024-02-22T07:03:34Z")

</div>

Hi everyone,

I’m tryin to merge two third parties with the appropriate button in third part section, but I get the following error:  
“Table ‘…\_4.llxgn\_don’ doesn’t exist Failed to merge the two records. Request canceled.”

Has anyone had the same problem and solved it?

---

<div class="post-metadata">

**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\
**Post date:** [February 22, 2024, 4:08pm UTC](https://www.dolibarr.org/forum/t/error-merging-third-parties/24998/2 "2024-02-22T16:08:13Z")

</div>

which dolibarr version and platform?

---

<div class="post-metadata">

**Author:** ![faustobe](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/f/edb3f5/32.png) [@faustobe](https://www.dolibarr.org/forum/u/faustobe)\
**Post date:** [February 22, 2024, 6:41pm UTC](https://www.dolibarr.org/forum/t/error-merging-third-parties/24998/3 "2024-02-22T18:41:22Z")

</div>

17.0.1 on linux, server apache 2.4, db mysql

---

<div class="post-metadata">

**Author:** ![jonbendtsen](https://www.dolibarr.org/forum/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jonbendtsen](https://www.dolibarr.org/forum/u/jonbendtsen)\
**Post date:** [February 22, 2024, 9:49pm UTC](https://www.dolibarr.org/forum/t/error-merging-third-parties/24998/4 "2024-02-22T21:49:19Z")

</div>

19.0 was just released, maybe the issue has been fixed?