Data Table not saving

Hello,

My Data table does not save changes when changing an Enum, It will save other entries like bools or ints or text fields, but won;t save the enum changes.

My specific use is a Data Table of Items, each item as a “slot” enum to indicate if it is a head items slot, or legs, etc.

It will save while the engine is loaded but as soon as I close it will lose the Enum changes in the Data Table. I know it will save because then I change a Enum and another value, the other value will save on engine restart but the Enum will not save.

Is this a bug or something else causing the issue? Is there a work around?

The stranger thing is that it used to save but now it doesn’t. So maybe it is a bug that occurs after the data table is a certain size or saved x times?

Thanks.

Hi Trent_WP,

  • Does this occur in a clean, blank project with no additional content or is it limited to one project?
  • Is the data table made in editor or an imported .csv file?
  • What steps can I take to reproduce this error on my end?

Hi Trent_WP,

We have not heard from you in several days. I am marking this as answered for tracking purposes. If you are still experiencing this error, please comment with the requested information.

I’m so sorry, the original notification email from your post go buried in an email folder. My bad.

No it doesn’t happen in a clean project. At least no immediately.

The Data table is made in Unreal, not imported.

Not sure how to reproduce. It seems like it becomes corrupt after some time. It is only related to the Enum data, other parts of the Data table are fine.

Thanks.

Was this project updated from a previous version or was it made in 4.11? Do you have a sample project where this is occurring I can take a look at?

Ok, after taking another stab I believe I have a solution/work around.

  • I created a new and identical ENUM. Not duplicate.
  • Deleted the original ENUM and replaced referenced with the new one.
  • Duplicated the DataTable
  • Deleted the original Data Table and replaced references
  • Change one of the problem enums, save, save all.
  • Restart, check the save held.
  • Fix any compile errors, this seems to break any of the existing ENUM references.

There may be an easier way to do this that is just as effective or less steps but it seems to work this way for me now. Might need further testing to see if it breaks again.

Yes it was updated.

I am happy to hear this is working for you. For now I’ll mark this as answered. If this asset breaks after having done this, please post back and I’ll take another look.

It’s not the first time things have broke like this for me. It would be awesome if it could be looked into and potentially fixed so the same things doesn’t happen again.

I haven’t been able to reproduce it on my end, which is currently standing in the way of any potential fixes. If you have an asset that this is occurring in or if you have steps I can take to reproduce this on my end I’d be happy to work through them and see if I can cause the bug to reproduce.

Here is a link to the offending files. I hope I grabbed enough dependent files that it doesn’t break anything. If it does please let me know and I’ll try again.

If you open the Data Table and try to change the EquipmentSlot Enum on something that has a ‘none’ as it’s value it will not remember the change when you close and re-open the engine. Important that you need to restart the engine.

I would try to change the health potion for example to a QuickSlot Item and it would not save the changes. Works fine until you restart the editor.

Can you provide a sample project with this in it? I’ve attempted to reproduce it however I cannot seem to generate the data table rows to test the bug with the assets provided.

OK, so I created the new project and added those files to it and tested it. My files work, turns out you just need to place them in a ‘Content/Blueprints/Items/’ folder. I can package an empty project with these file in the correct folder for you if you like but things get more interesting…

When setting up this new empty project for you I discovered I no longer have the bug. Using the exact same files that DO cause the bug in my other project. The Data Table saved just fine. So I am really confused as to what could be causing the bug. I have no idea how to re-create it. Maybe there is something else in my project causing the problem?

So what I did next was Instead of creating a new project with those files for you to look at, I decided to strip down my bugged project for you. When I stripped it down the Data Table suddenly began behaving correctly again. It was definitely bugged before stripping it down because I tested it before starting the stripping process.

So something I deleted in the process caused the bug. And I don’t really want to upload my entire project for testing. So what could be the next step in this?

Thanks!

Do you know what files you deleted before the data table began working again? Have you tried running “fix up redirectors” on your contents folder to see if the error is an invalid pointer?

I deleted too many at once to know which file was responsible. Also, fixing up redirectors didn’t work either.

Unfortunately I still haven’t been able to reproduce this on my end. Do you have any other steps I can take? Have you had trouble with the asset after deleting the assets you have already deleted?

For now it is working again after I follow the steps listed above. Is there a way we can take this discussion offline so I can send you a private link to the full bugged project? Then you can see the bug first hand in the exact conditions.

If you like you can send me a private message on our forums here:

I have sent you a private message. I deleted some folders one by one and it seems to be caused my something in my ‘Pawn’ folder. When I deleted this folder the DataTable beings to save again.

Hi Trent_WP,

After looking through your project, I have found that this is a known issue that is in our system as UE-23978. I have updated the bug report to reflect that additional developers are experiencing this error.