-
Notifications
You must be signed in to change notification settings - Fork 197
Attribute Sets Migration_ #275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @snoroozi Yes, it was done in order to avoid conflicts with names of attribute sets and attribute groups of Magento 1 and Magento 2. You can remove this prefix if you will |
Remove after migration manually or is there a way before? We have about 50
attribute Sets.
…On Thu, Apr 20, 2017, 1:01 AM Victor Rad ***@***.***> wrote:
Hi @snoroozi <https://github.com/snoroozi>
Yes, it was done in order to avoid conflicts with names of attribute sets
and attribute groups of Magento 1 and Magento 2. You can remove this prefix
if you will
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#275 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACQbJdxzlpDwDLdpxG4NIlvHjkWw0Zzqks5rxua8gaJpZM4NCa-c>
.
|
Look into map-eav.xml.dist. \Migration\Handler\AddPrefix handler does it. You can try removing it to test if it works for you. |
Thank you.
…On Thu, Apr 20, 2017, 11:19 AM Victor Rad ***@***.***> wrote:
Look into map-eav.xml.dist. \Migration\Handler\AddPrefix handler does it.
You can try removing it to test if it works for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#275 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACQbJRriYlW04HtwRtFRYKFh251yXoJ6ks5rx3eAgaJpZM4NCa-c>
.
|
@victor-v-rad Will it effect any functionality if we are renaming migrated attribute in magento 2 ? hope for reply soon |
If you have a staging, I suggest leave as is, and then backup your staging
and test there first.
We did have one set back from altering attribute sets directly in the
database and had to roll back to earlier that week a backup we'd made.
…On Mar 14, 2018 8:27 AM, "yogeshsyscraft" ***@***.***> wrote:
@victor-v-rad <https://github.com/victor-v-rad> Will it effect any
functionality if we are renaming migrated attribute in magento 2 ? hope for
reply soon
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#275 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACQbJcGgn_tfdZllkI4VXSjP-bkOq0dcks5teQyigaJpZM4NCa-c>
.
|
When I migrated my data all of my migrated attributes were renamed Migration_someattributeset. All were appended with Migration_
The text was updated successfully, but these errors were encountered: