Enum from imported DataTable problem

I am seeing odd behavior when importing a DataTable (from csv) I have defined the DataTable in Blueprint, which contains a couple of enums, also in blueprint.(shown below)

The CSV, imports without error; And when I open the data table, the Enums are always filled with correct values, the display text however is the default text before it was changed.

It is worth noting that i am using Engine 4.5.1; Using an empty Third-Person Blueprint project.(Desktop, Maximum quality, with starter content)

I have tried about everything i can think of, and i still I cant get the display text correctly.

Not sure i am ready to call this a bug… and it is entirely possible that i am doing something wrong…
Any help here would be great.

i tried refreshing the enums, and it invalidated the entries in the DataTable, so i would say that you have hit on the cause.

unfortunately, the by refreshing the nodes, or some related by-product, editing either of the table definition or the data crashes the editor… for that matter trying to delete them crashes in also.

Hi magnetomage,

I haven’t been able to reproduce this on my end, can you provide me some reproduction steps so I can try to cause this to occur? Here is what I have done so far:

  1. Create CSV data table document with the numbers/names you specified above.
  2. Save and close data table, open editor (any project)
  3. Create new enum.
  4. Create the 4 states listed above (save-close)
  5. Create new struct
  6. Create variables for each column and provide the variable types you list above (save/close)
  7. Import data table to enum
  8. Create new actor blueprint
  9. Event On Begin Play>Sequence>Get Datatable Row (one for each row)
  10. Out of the Out Row output, break user struct, create one print string for each variable.
  11. Add static mesh (so it can be seen in level, simply for testing)
  12. Compile, save, close.
  13. Play in Editor

When I did this everything seemed to come in as intended. Are there any steps that I missed that could be causing this? Have you tried using the 4.6 preview to see if it occurs there as well?

I Have been able to reproduce this several times. each time by creating a blueprint project(with sample content) and using the example map included these are the steps:

  1. Create a Datatable in any
    blueprint project,add some fields.
  2. Create the Enum definition, in blueprint
  3. Create a new field in the data-table definition, assign it to the data-table
  4. save.
  5. add data to the example.xslx file provided by epic to match your
    data-table.(enums added as the index
    on the Enum definition).
  6. export the csv(using the embedded button provided)
  7. import via drag-and-drop the data, set it to be a data-table, of the type you defined.
  8. open data-table data and verify the incorrect enum filed names.

that is a good idea; i havent yet, but i will try pulling the 4.6 preview bits down and test against them.

sure, true, i could use an Int, or several other ways to assign the same value… But, this should work… and i like the Type-safeness of Enums.

I am trying to stay in blueprint as much as possible since most of my team have little to no programming experience and non-blueprint classes can confuse them.
they do however have kismet experience in UDK, so using blueprints is not beyond their abilities…

i will try just defining them in C++ and move on.
thank you for you help

after trying the 4.6 preview i am seeing the same issue… however refreshing the nodes does not invalidate the Enum values in the table(as i mentioned below) and i can’t seem to get it to crash… the data is still wrong though…

Hi magnetomage,

I have not been able to reproduce this thus far, have you attempted the 4.6 engine build to see if it is still occurring there for you?

yes, i have tried it on 4.6 using my instructions, and it still shows the incorrect Enum Labels; however, the struct datatable and enums no longer cause crashes when they the blueprint nodes are manually refreshed.

Hi magnetomage,

If you are comfortable with it, can you send me a copy of your project so I can take a look? Thus far I haven’t seen this occur so if I can get access to an enum that is definitely experiencing this error I can try to see what is going on. Thank you!

Hi magnetomage,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.
Thank you.

I have added a copy of a stripped down project, it is on my DropBox folder here

This project contains only the default project content that was added as part of the new project creation.
For size reasons i did not include the StarterContent folder(located in the content folder, as created by the 3rd person blueprint project wizard) it may need to be added back, for thorough testing.

I added a folder named externs that contains the csv file.

The Data folder contains the Datatable(as imported) the struct and enum definitions.

any help here would be great…

I have added a copy of a stripped down project, it is on my DropBox folder here

This project contains only the default project content that was added as part of the new project creation. For size reasons i did not include the StarterContent folder(located in the content folder, as created by the 3rd person blueprint project wizard) it may need to be added back, for thorough testing.

I added a folder named externs that contains the csv file.

The Data folder contains the Datatable(as imported) the struct and enum definitions.

any help here would be great…

Hi magnetomage,

I cannot see in here where the enum is not coming in correctly. I took a screenshot containing the .csv, the enum, and the struct, can you highlight on here where the differences occur? I may simply be overlooking it.

The enum instance in the data table have the default enum item names(e.g. NewEnumeration0, NewEnumeration1, etc) rather than the correct names. It is like the UMetaProperty is not getting set.

Ok so the Type and Initial Status sections? I just saw what you are talking about there and apparently overlooked that yesterday, so thank you for pointing it out! I am entering a bug report, UE-7022 to be assessed by the development staff.

This is still a bug in 4.7.5. I’m running into it all over the place.

Hi jeffvoigt,

This bug report is still under assessment. Unfortunately I do not have a timeframe of when this will be fixed.

Any news if this was fixed in 4.8? I don’t think I saw in the release notes…

Hi ,

There hasn’t been any recent activity on UE-7022 as our resources are currently dedicated elsewhere. I am going to bump the community interest to better reflect the number of developers this is currently affecting. This does not guarantee the bug will receive higher priority, however it may help.