A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
AI OnAI Off
A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
It is, unfortunately, not supported for Catalog content. Your best bet is to create a property with new name and then migrate the data over the new one.
public class MyMigrationStep : MigrationStep { public override void AddChanges() { ContentType(nameof(MyVariationContent)) .Property("NewName") .UsedToBeNamed("OldName"); } }After running the code, the new property is empty and the old one is there as leftover with its original value. Then I have to do the migration and cleanup manually. Is it supposed to work with Commerce or only for CMS? (for CMS it is working fine) If Commerce is not supported, is there any way to achieve this? Thank you in advance!