Try our conversational search powered by Generative AI!
AI OnAI Off
EPi 10 Migration Issue - CatalogContentProperty n Metafield Default Value
Hello Quan,Let's put this in a simpler scenario. We have a new REQUIRED metafield created under Catalog metaclass. Now I am doing a catalog import/export, the export fails because we have a check for required field is empty and the import does create the entries in the database but no required field metafields are created. This wasnt the case before , EPi was handling it by putting a default value for the columns from MetaDataType table.
We can alter our import/export but we have a risk that might affect something else and wondering if there is a more easier/neat solution for this?
May 12, 2017 21:00
With the new EPi migration, we found that the default values for metafields is not getting updated for all the catalog entries. We have to manually update the default values for each catalog entries.
In other words, before the migration EPi had separate datatable for metafields and each metafield had a default value that gets reflected in all the entries(like catalog) and now since EPi moved it to single table CatalogContentProperty, these default values are missing from the entries and therefore we have entries without any content properties.
Anyone ran into this? Any thoughts? Does EPi have a script to fix this?
Also in future if we create a new metafield with a default value, it looks like we need to manually update the default value for each entries?