- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Migration Issue from 1.9 to 2.3.3
Hi,
I have migrated website successfully but attrbute sets are showing prefix "Migration_". How can I replace that?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Migration Issue from 1.9 to 2.3.3
Hello @gkarthick87
You can open the attribute and rename it.
Please check the below screenshot: https://meetanshi.d.pr/yvlEmZ
I hope it helps.
Thank you.
200+ Magento 2 Extensions for Enhanced Shopping Experience.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Migration Issue from 1.9 to 2.3.3
Hi @gkarthick87,
You can change attribute set names in database as well .
Table: eav_attribute_set
Make sure you will take backup before doing any change.
Hope this helps you!
Problem Solved! Click Kudos & Accept as Solution!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Migration Issue from 1.9 to 2.3.3
I'm getting this error:
#1062 - Duplicate entry '1-Default' for key 'EAV_ATTRIBUTE_SET_ENTITY_TYPE_ID_ATTRIBUTE_SET_NAME
Also, I have upgraded magento version to 2.3.5-p1
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Migration Issue from 1.9 to 2.3.3
Hi @gkarthick87 ,
After database changes, seems like you have 2 duplicate entities in the table eav_attribute_set
with same entity_type_id & attribute_set_name (which must be unique).
Please check the table entries and delete one entry.
Hope this helps you!
Problem Solved! Click Kudos & Accept as Solution!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Migration Issue from 1.9 to 2.3.3
Yes but which one i need to delete? I'm not sure about that.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Migration Issue from 1.9 to 2.3.3
Hi,
I hope you have taken the backup of the table before performing the changes.
I am assuming you must have 2 entries example
entity_type_id & attribute_set_name
1 Default
1 Migrated Default (and we make this as Default after migration)
Cross verify which attribute_set_id is being used in the below table leave that.
And delete the other one.
catalog_product_entity
Hope this helps you!
Problem Solved! Click Kudos & Accept as Solution!