Update exisiting terms data

During the import I am getting:

[10:38:17] Record #32

[10:38:17] ACTION: pmxi_before_post_import ...

[10:38:17] Combine all data for term MU13FLW...

[10:38:17] Find corresponding article among previously imported for post <code>MU13FLW</code>...

[10:38:17] Duplicate post wasn't found with unique key <code>MU13FLW</code>...

[10:38:17] Applying filter <code>pmxi_article_data</code> for <code>MU13FLW</code>

[10:38:17] CREATING <code>MU13FLW</code> <code>Taxonomy Term</code>

[10:38:17] ERROR: A term with the name provided already exists with this parent.

[10:38:17] ACTION: pmxi_after_post_import

Hey @sg88,

Currently, I am facing an issue that if a term already exists, its additional custom field data is not getting updated anymore. How can I get around that?

Based on the log, it looks like this is a “New Items” import (see https://d.pr/5s8uX9) that did not previously create the term, which means it would not be able to detect and update it.

If you set up an import that created the terms initially in a “Taxonomies” import, you can re-run that import to update them: https://www.wpallimport.com/documentation/recurring/update-import. Or, with a separate import, you can use an “Existing Items” import to update them: https://www.wpallimport.com/documentation/recurring/manual-record-matching/ (just be sure to use the “Choose which data to update” option on the last step to choose to update only the data you want changed).

Hm that is strange, actually I thought that the terms all have been created by the import initially.
How do I determine if a term has been imported or created manually?

Hi @sg88,

How do I determine if a term has been imported or created manually?

If you created the term in a “Taxonomies” import with a “New Items” import, then you’d be able to find it in the pmxi_posts database table. If it was created any other way, then there’s really no way to tell if it was imported or manually created without digging through import history logs.

Hey @sg88,

I’m marking this as resolved since it’s been inactive for a month now. Please open up a new topic if you still have questions.