I’m sorry, I thought I had already addressed this response several days ago.
No, actually, I created a Blueprint Enum called ESkillType. In my case, the Enum values were specifically “None”, “Gun”, “Melee”, and “Spell”. I then created a struct that contained this Enum, among other things, and then a data table based on the struct. When importing values into the data table in 4.8, any non-Enum values are imported properly, but those that are Enums will input only the default, lowest-valued option. Entries of Enums in the data table will additionally only be shown using their would-be default names as well. So, for the value of “Melee”, the actual text displayed in the master list for the Data Table tab is “NewEnumeration2”. After a fresh import, the lower area displaying an individual row will have “None” listed in the Enum’s section of the Struct even as “NewEnumeration0” is imported into the top section. If I select the Enum slot and pick “Melee” in the drop down, the value will switch to Melee in the bottom area and will become “NewEnumeration2” in the top area to reflect the change.
So, there are two distinct bugs:
- Importing the values of a Blueprint Enum into a Data Table from a .csv file causes the value of the enum to become the enum’s default value.
- The text in the top section of the Data Table will display the default name that would have been assigned to the slot in the enum if it hadn’t been renamed. The bottom section will behave as normal.