Answers.Body: <p>Can you uninstall the extension and re-install?</p>
  <p>i.e Disable &gt;&gt; Uninstall &gt;&gt; Install</p>
  <p>Or you can run below query</p>
  <pre><code>CREATE TABLE `civicrm_afform_submission` (
    `id` int unsigned NOT NULL AUTO_INCREMENT COMMENT 'Unique Submission ID',
    `contact_id` int unsigned,
    `afform_name` varchar(255) COMMENT 'Name of submitted afform',
    `data` text COMMENT 'IDs of saved entities',
    `submission_date` timestamp DEFAULT CURRENT_TIMESTAMP,
    `status_id` int unsigned NOT NULL DEFAULT 1 COMMENT 'fk to Afform Submission Status options in civicrm_option_values',
    PRIMARY KEY (`id`),
    CONSTRAINT FK_civicrm_afform_submission_contact_id FOREIGN KEY (`contact_id`) REFERENCES `civicrm_contact`(`id`) ON DELETE SET NULL
  )
  ENGINE=InnoDB ROW_FORMAT=DYNAMIC;
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-10T12:01:17.397Z
Answers.Text: Thanks! Reinstalling the extension didn't work. I had to create the table manually. But why this extension is required for merge action? And if it's required, why it's not activated by default?
Answers.UserDisplayName: marcelo2605
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-10T12:10:12.887Z
Answers.Text: Ah, the problem only happens when the Form Core ext is activated and the Form Builder not.
Answers.UserDisplayName: marcelo2605
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-01-10T11:53:51.803Z
Answers.LastActivityDate: 2024-01-10T11:53:51.803Z
Answers.UserDisplayName: Pradeep Nayak
Body: <p>Enabling the debug mode, I got more details:</p>
  <blockquote>
  <p>Error Field   Error Value Type    DB_Error Code   -18 Message DB Error: no
  such table Mode   16 UserInfo UPDATE civicrm_afform_submission SET
  contact_id = 123 WHERE contact_id = 456 [nativecode=1146 ** Table
  'wordpress.civicrm_afform_submission' doesn't exist] DebugInfo    UPDATE
  civicrm_afform_submission SET contact_id = 123 WHERE contact_id = 456
  [nativecode=1146 ** Table 'wordpress.civicrm_afform_submission'
  doesn't exist]</p>
  </blockquote>
  <p>It looks like this table is created by the Form Builder extension. I tried to enable it but the table is still not created.</p>
  
Tags: <wordpress><contacts>
Title: Merge Contacts throw an error: DB Error: no such table
ThreadText: # Merge Contacts throw an error: DB Error: no such table
  
  (Asked by: username_0 on 2024-01-10)
  
  Enabling the debug mode, I got more details:
  
  > Error Field Error Value Type DB\_Error Code -18 Message DB Error: no
  > such table Mode 16 UserInfo UPDATE civicrm\_afform\_submission SET
  > contact\_id = 123 WHERE contact\_id = 456 [nativecode=1146 \*\* Table
  > 'wordpress.civicrm\_afform\_submission' doesn't exist] DebugInfo UPDATE
  > civicrm\_afform\_submission SET contact\_id = 123 WHERE contact\_id = 456
  > [nativecode=1146 \*\* Table 'wordpress.civicrm\_afform\_submission'
  > doesn't exist]
  
  It looks like this table is created by the Form Builder extension. I tried to enable it but the table is still not created.
  
  **Tags:** wordpress, contacts
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2024-01-10. Score: 1
  
  Can you uninstall the extension and re-install?
  i.e Disable >> Uninstall >> Install
  Or you can run below query
  CREATE TABLE `civicrm_afform_submission` (
    `id` int unsigned NOT NULL AUTO_INCREMENT COMMENT 'Unique Submission ID',
    `contact_id` int unsigned,
    `afform_name` varchar(255) COMMENT 'Name of submitted afform',
    `data` text COMMENT 'IDs of saved entities',
    `submission_date` timestamp DEFAULT CURRENT_TIMESTAMP,
    `status_id` int unsigned NOT NULL DEFAULT 1 COMMENT 'fk to Afform Submission Status options in civicrm_option_values',
    PRIMARY KEY (`id`),
    CONSTRAINT FK_civicrm_afform_submission_contact_id FOREIGN KEY (`contact_id`) REFERENCES `civicrm_contact`(`id`) ON DELETE SET NULL
  )
  ENGINE=InnoDB ROW_FORMAT=DYNAMIC;
  
  > **Comments:**
  > **username_0**: Thanks! Reinstalling the extension didn't work. I had to create the table manually. But why this extension is required for merge action? And if it's required, why it's not activated by default?  
  > **username_0**: Ah, the problem only happens when the Form Core ext is activated and the Form Builder not.  
  
  ---
  
  