Selecting multiple actors with differing DataTableHandles causes data loss

The data table customization (and probably others) tries to aggressively clear out row references that are not valid in the table they point to. This breaks when selecting multiple actors or objects that have different row handle values. It tries to look up the value but fails due to them being different, and then clears out the row because it thinks it is also bad.

No customizations should cause data loss from just viewing them, so this should be fixed to not fix up handles with multiple differing values. It should also be re-evaluated if the fixup code should run at all when the handle is just viewed

1. Create an actor blueprint with a Data Table Handle variable that is set to instance editable
2. Place two instances of that actor in the world, set the handle to point to different tables and rows
3. Select both actors at the same time, the row name switches to None
4. Select an individual actor, note that the row name is STILL none, which means that selecting actors actually causes data loss in this case

What is UAID?

error message when install in U.E 5.3 - IS-IN-FCO2-82

How does TextureRenderTarget2D get TArray<uint8> type data?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

How do I set a material as a post-processing material?

How to delete some elements correctly when deleting an array loop?

How would I go about lerping the rotation instead of it snapping when turning (pls dont sue me epic)

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

UMG RichText not appear image when packaged

Why does the REMOVE method of map container remove elements have memory leaks?