I just updated to 5.18.1 to resolve a bug caused when selecting " Exclude contacts with "do not mail" privacy, no street address, or who are deceased." But now I have a new issue:
I set up an export with a saved field mapping. Under Merge Options I select "Merge All Contacts with the Same Address". I then click [Continue], accept my existing saved field mappings, and click [Export]. I then see a fatal error message.
In error logs, I see the following, which I think is failing because of the extra comma after is_deceased VARCHAR(16), :
CREATE TABLE `civicrm_tmp_d_export_e92589f8a1e163117ff1d83e45c03029`(
id INT UNSIGNED NOT NULL AUTO_INCREMENT,
prefix_id VARCHAR(255),
first_name VARCHAR(64),
last_name VARCHAR(64),
suffix_id VARCHAR(255),
street_address VARCHAR(96),
supplemental_address_1 VARCHAR(96),
city VARCHAR(64),
state_province VARCHAR(64),
postal_code VARCHAR(64),
country VARCHAR(64),
preferred_language VARCHAR(5),
organization_name VARCHAR(128),
custom_32 VARCHAR(255),
home_phone_phone VARCHAR(32),
email VARCHAR(254),
custom_31 VARCHAR(255),
groups TEXT,
middle_name VARCHAR(64),
nick_name VARCHAR(128),
display_name VARCHAR(128),
tags TEXT,
deceased_date VARCHAR(32),
do_not_mail VARCHAR(16),
is_opt_out VARCHAR(16),
addressee VARCHAR(255),
postal_greeting VARCHAR(255),
email_greeting VARCHAR(255),
street_name VARCHAR(64),
household_name VARCHAR(128),
civicrm_primary_id VARCHAR(16),
master_id VARCHAR(128),
state_province_id VARCHAR(255),
postal_greeting_id VARCHAR(16),
addressee_id VARCHAR(16),
is_deceased VARCHAR(16),
,
PRIMARY KEY(id),
INDEX index_street_address(street_address),
INDEX index_household_name(household_name),
INDEX index_civicrm_primary_id(civicrm_primary_id) ) ENGINE = InnoDB DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci
Anyone else experiencing this? If not, any ideas why I would?
