The widgets should contain an identifier, perhaps an enumerator which also gets saved. When you load data, you create widgets based on that ID, pipe it in and the widget knows what to do.
In your example you do not create any widgets, though - it seems you’re re-use existing ones? You could associated widgets with enumerators in the map. Or have a dedicated widget manager actor that keep track of whose data belongs to whom.
Hard to advise without knowing the overarching architecture of what we’re making here. Those widgets could belong to actors for example, in which case it would be the actor’s job to re-create / repopulate its own widget data.
There’s too many ways to organise it all.
all the widgets receive the data of the last widget edited.
You’re using a double loop, you assign all widgets data to all widgets. It all gets overwritten over and over again. What’s worse, the GetAll nodes do not guarantee order. So this is totally unsafe and quite chaotic. 