[webfoundryhg]

SOLVED:
was info left in database from previous imports leading up to launch…

select field_id, count(*) c from wp_bp_xprofile_data group by field_id having c > 1;

| field_id | c |
+———-+——-+
| 1 | 7159 |
| 2 | 68 |
| 3 | 23 |
| 4 | 7103 |
| 5 | 7041 |
| 6 | 33 |
| 7 | 7089 |
| 9 | 7119 |
| 13 | 21502 |
| 14 | 7099 |
| 15 | 7108 |
| 16 | 7080 |
| 17 | 7118 |
| 18 | 7118 |
| 19 | 7117 |
| 20 | 7123 |
| 21 | 7123 |
| 22 | 7123 |
+———-+——-+
notice field_id 13
has 21k rows, roughly 7000 x 3
And field_id 13 is for our custom field
So, i’ll bet our custom field is in wp_bp_xprofile_data 3x causing counts to go up x3 roughly
And the proof query …
select value, count(*) c from wp_bp_xprofile_data where field_id=13 group by value having c > 1;
each member is in wp_bp_xprofile_data 3x