Column Header Mapped to the Wrong Field Name

[BrianJ557]

This happened twice in two recent data uploads. The first time I caught it, the second time I didn't. So now I have a small amount (luckily) of records with the wrong field values.

My first question: How do I delete values from a field ("Job Title", which is a default field). We generally don't map values to this field, so most of them are blank. The problem is that values were mapped to blank fields (which, I suppose, is better than overwriting). The odd thing is that one record did have a job title, the wrong field value did not get mapped to that Job Title field. Or the correct value was mapped, I cannot figure it out.

I've checked the upload file, and there is nothing wrong, except there was a column that should have skipped, and I could have deleted before the upload, and that is the column with the values that got mis-mapped. In the previous upload UI, it displayed each column, and it was marked red if it could not map. Now, you kind of have to look down the rows and see if everything is mapped correctly. I MUCH prefer the previous way.

My Second question: In my 4-5 years using CC, this has never happened before. Did something change with the mapping algorithm? Clearly the UI changed.

[Caitlin_M]

Hi @BrianJ557. To be clear, are you looking to clear out a field for a selection of contacts by uploading a file with blank fields and overwriting the existing field content? 

[BrianJ557]

Yes. I tried uploading with a "space" in the field in question, but that didn't work.

And while maybe not in your purview, I am also wondering about/questioning the mapping logic being used that resulted in two wrong maps in my last few imports.

[BrianJ557]

My data uploads are suddenly showing up as "Lists".

Never seen this before, and is adding confusion for other users, and could potentially cause a campaign to be sent to the wrong targets.

[Caitlin_M]

Hi @BrianJ557. We'd like to look into this more. Please email us at communitysupport(at)constantcontact.com with your username, a reference to this post, and the file you uploaded so we can test the upload on our end to see if we can replicate the issue. Thanks!

[William_A]

Hello @BrianJ557 ,

After reviewing this post and the follow-up emails, the main issue seems to be simply getting used to the updated contacts user interface.

Regarding field mapping, this’ll just come down to reviewing the fields getting matched up. It may look different, but it's effectively the same process where you check the fields and confirm they're correctly mapped before moving on. If you have a default or custom field that matches better than the field the system assigns based on the title, you'd need to manually swap or skip the field, or create a new custom field to assign to.  

We don't have any further insight on what (if anything) might've changed on the backend for assignment logic.

__________________

As for the second part regarding list names, the updated UI allows users to upload contact lists without necessarily assigning them to an existing list. If an existing list isn't selected, or a new one isn't manually created and selected, then the system will default to generating a list with a naming pattern of Import "[file name]" [date][time] where the applicable contacts for that file will be added. 

My personal example:

If you don't want these to exist in your account, your options are to either select a list during the import process, or to delete the default-named new list.