ue-datatable-migrator

Renaming a column in an Unreal Engine DataTable requires updating struct definitions, code references, Blueprint nodes, and optionally setting up redirectors to maintain compatibility and prevent regressions during schema evolution.

Yes, you can change column types in UE5 DataTables through schema migration. This process includes managing the type changes and generating detailed pre/post-migration validation reports to ensure data integrity.

You can add a new column to a UE5 DataTable by specifying the target table, column name, data type, and a default value. The migration process applies the schema change and validates the updated row data.

Yes, DataTable migration supports bulk operations including importing row data from CSVs and exporting tables for backup. This ensures data integrity when adding or removing rows with uniqueness and foreign key validation.

You need a pre-migration validation report when modifying DataTable schemas or row data during game development refactoring. It identifies potential data integrity issues before applying column additions, renames, or type changes.

Modifying DataTable schemas risks breaking code references and Blueprint nodes if not handled correctly. Limitations include potential regressions from removing rows without foreign key validation or failing to set up redirectors after structural changes.