Errors kept this fieldmap from being saved. No error log provided

A few questions for me to try to understand what’s happening:

1. Do you have access to your WordPress database? If so, can you confirm that the plugin has created two tables (wp_object_sync_sf_field_map and wp_object_sync_sf_object_map)?
2. If it does have those tables, is there any data in either one after you try to save the fieldmap (I assume they’re empty, but just in case)?
3. You say it seems to be authorized – I assume when you look at the plugin’s Authorize tab, it says “Salesforce is successfully authenticated.” and shows you some information about the connection to Salesforce?
4. Can you describe what fields you are trying to map, and also the other settings you’ve filled out when you try to create the fieldmap?

If you don’t have wp_object_sync_field_map, this is why you are unable to create a fieldmap.

I’ve seen a few cases where users install this plugin and it is unable to create that table, without which it won’t work, but I’ve yet to determine what about their configuration makes that the case or to reproduce it in a local environment to try to fix it.

Can you tell me what version of PHP, MySQL, and WordPress you are running?

For a possible solution, you might try uninstalling and reinstalling the plugin, though presumably something about your server environment is keeping this table from being created.

Here’s the code you might be able to run:

CREATE TABLE wp_object_sync_sf_field_map (
  id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  label varchar(64) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  name varchar(64) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  wordpress_object varchar(128) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  salesforce_object varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  salesforce_record_types_allowed longblob,
  salesforce_record_type_default varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  fields text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  pull_trigger_field varchar(128) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'LastModifiedDate',
  sync_triggers text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  push_async tinyint(1) NOT NULL DEFAULT '0',
  push_drafts tinyint(1) NOT NULL DEFAULT '0',
  weight tinyint(1) NOT NULL DEFAULT '0',
  version varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  PRIMARY KEY (id),
  UNIQUE KEY name (name),
  KEY name_sf_type_wordpress_type (wordpress_object,salesforce_object(191))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

If MySQL gives you errors creating this table (or if you have access to logs to see why it might have failed on the initial installation) I’d love to see those. Like I said, this is not an unprecedented error but it appears to be rare enough that it is very hard to find out what combination of factors cause it.

• This reply was modified 7 years, 11 months ago by Jonathan Stegall. Reason: fix sql formatting hopefully