In this case you wouldn’t require the enum to spawn per se, you’d use the enum to determine what dataset to access from the parent blueprint. This isn’t a workaround so much as a feasible way to do the task you are looking for. Another would be to put the datatable information on a custom event and call the custom event for Gandalf when the actor==gandalf, or merlin for merlin etc. I figured the enum is significantly more performant and easier to set up than some other options that are available.