Re: Wombat Beta - Feedback
I noticed this in Emporiums release notes
5) Product field SKU added to the primary products database. This is a moderate change but if you plan to use that SKU field, you will need to upgrade 3rd party modules that you want to also use that field. Many stores which needed an SKU have already been using a custom product field for that and will not do the extra work needed to pull the data from the custom field and insert into the native product SKU field.
My question is now that we filled our "Custom Field" named SKU with hundreds of entries, is there a way to move the data over or should we just continue with the "Custom Field" or should we just leave it alone at this point?
"will not do the extra work needed to pull the data from the custom field and insert into the native product SKU field" I'm not clear on "extra work"
I noticed this in Emporiums release notes
5) Product field SKU added to the primary products database. This is a moderate change but if you plan to use that SKU field, you will need to upgrade 3rd party modules that you want to also use that field. Many stores which needed an SKU have already been using a custom product field for that and will not do the extra work needed to pull the data from the custom field and insert into the native product SKU field.
My question is now that we filled our "Custom Field" named SKU with hundreds of entries, is there a way to move the data over or should we just continue with the "Custom Field" or should we just leave it alone at this point?
"will not do the extra work needed to pull the data from the custom field and insert into the native product SKU field" I'm not clear on "extra work"
Comment