FIXED: replicator table order bug

099 - x64 - win10 - 13080

there is a circumstance where the replicator does not generate it’s replicated items in the same order as the supplied dat.

File attached!
replicatorOrderBug_099_x64_win10_13080.toe (4.26 KB)

Doing some spelunking here, and it looks like display order is alpha numeric. Adding an index value in front of the underscore yields expected results, for example:

1_123 2_564 3_234 4_987

Maybe the expected use case here is that display order is arbitrary - and that ultimately the naming of the replicants is the most important consideration?

Regardless, I think Lucas is right in noticing that it’s not an obvious behavior and certainly feels inconsistent with the behavior of replication by rows - it’s worth noting that this behavior is consistent if Column by Name is the Name by Table parameter.

Maybe a RFE here would be to add a toggle or flag for “Arrange by Row Order” so the user could determine if the arrangement should follow the row indexing, or if it wasn’t important.

It was actually an oversight, as all the replicants were laid-out in alphanumeric order after creation.

The toggle is probably not needed, so the default behavior in the next posted build will be to simply layout by table order.

Thanks for catching this!

Rob.

Yeah it’s certainly a thing that can be worked around but can be a bit hard to to track down when it happens. Thanks for the verification !

I have a very weird use case scenario that is probably not common at all - naming nodes in one area via a random number UUID format like “_3965749127” and that was causing the rows to get reordered.

Lucas