Posts: 90
Threads: 19
Joined: May 2014
Reputation:
0
The second video is private and I can't see it.
Anyways, what you are suggesting is that I mass edit the Department field and delete its content followed by a complete reimporte of the database with duplicate handling?
In theory that should work except that in the meantime I have created additional fields and the database already contains some duplicates that I haven't yet merged. The only way I would see this "working" would be by exporting the current database (or at least those contacts with data in the Department Field, around 1500 of them), purging the Department Field, then copying the proper department from my original csv file to the exported one and then finally reimporting the whole thing with duplicate handling. With so many steps involved and contacts on hand here I am kind of relunctant to do this as I am not really confident on the duplicate function.
EDIT: I am going to try that. Just made a backup of Corebos and the database just in case things turn bitter.
Posts: 3,565
Threads: 36
Joined: Apr 2014
Reputation:
49
That sounds complicated, it is much easier than that if you have a way to identify each contact in the CSV in the application.
Let's imagine that each of your contacts has a unique identifier (be it their name, some ID field, ...), you import the CSV again, possibly only with the identifier columns, mandatory fields and department.
On the import step you will find a "Duplicates" section, you open that and select the options to update, in the columns list box you select the columns that uniquely ifentify your contact, then in the field mapping you select the department field so that field gets updated.
In short: import again activating deduplication and update ONLY the department field.
We use this all the time to update product unit price, for example,...
Make a backup of the database first.
Joe
TSolucio
Posts: 90
Threads: 19
Joined: May 2014
Reputation:
0
In principle you are correct but here is the deal:
1 - If I use my original database, that wont work because some contacts name were updated due to spelling errors. If I use that then I will end up with some records not being updated properly.
2 - Let's say I export the current production database so that all the names correspond when I import it back. That should work except that when I export the current database corebos seems to disagree with special characteres in some names and adds garbage instead. I am guessing utf-8 is the reason. Also, since the last name is the only mandatory field I can use I am forced to do some editing on the names.
It's not as easy as you described and one way or another I need to edit manually some contacts so that everything imports/updates properly at the end.
Anyways, seems I am seeing the end of the tunnel here. I've done moreless what you suggested while also having to edit a certain amount of name so that they can be properly identified with the production database.
EDIT: Can I actually use the ID colum as identifier and leave the whole last name colum blank?
Posts: 90
Threads: 19
Joined: May 2014
Reputation:
0
In the import file I've only left the contact ID, last name and department. Haven't clicked the import button yet for the following reason:
Is it normal that corebos does not recognize the contact ID header? By not recognize I mean that states --None-- instead of choosing the corresponding CRM field. That would probably be the single most accurate identifier since there is only one per contact. What's up with that?
By the way, thanks I think we are nearly there!!
--><img src="{SMILIES_PATH}/icon_e_biggrin.gif" alt="