Bug: Weird behaviour with a move using a pattern

Alumio Feedback
1

Hi Alumio,

I’ve just found a really weird bug with the Move using a Pattern.

I’ve worked around it for now, but it can cause really strange errors.

So I’ve got this dataset:

{
  "salesBarcodes": [
    {
      "barcodeValue": "87168399454518716839945468"
    },
    {
      "barcodeValue": "87168399454518"
    }
  ]
}

And I’d like to group it on barcodeValue. Then I want to make sure every barcodeValue exists only once, so I use this Move using a Pattern:

image
image937×291 14.6 KB

This is the result:

{
  "salesBarcodes": {
    "87168399454518716839945468": [
      {
        "barcodeValue": "87168399454518716839945468"
      }
    ],
    "87168399454518": {
      "barcodeValue": "87168399454518"
    },
    "9223372036854775807": null
  }
}

It has completely ‘made up’ the last value (doesn’t exist in the dataset) and made the structure really strange.

Attached is a demo-transformer with this particular weirdness. Tested on 3.76.0.

export_20250124171631.ndjson (923 Bytes)

2

Just found out it also does this in Copy using a Pattern.

3

Hi @floris,

You can read this article Group records Transformer and use the “Group Records” transformer if you want to group data by a specific “key.” Please refer to the sample provided below.

image
image1058×285 11.1 KB

The “Move/Copy Using Pattern” transformer is not designed for this purpose (Group the data).

4

Hi @m.arief ,

That’s not what I’m doing. In the configuration I added to the post you can see I do the group records first, then use the move using a pattern.

The Move is used to kind-of ‘reverse’ it, and make sure that every barcodeValue is only once in the result-dataset.

5

Hi @floris

Could you please update your test data to include more items (not just two)? Please also provide the expected results for the test?

6

Hi @m.arief ,

Why? This should be more than clear enough. The issue is probably the specific value of the long ‘barcodeValue’.

The issue is obvious, no matter what my expected result is. The “Move using a Pattern” has completely made up the “9223372036854775807” value.

7

Thank you for your response and for providing further clarification.

Apologize and I understand your concern, and you are correct that the specific value 9223372036854775807 is unexpected and appears to have been generated during the “Move Using a Pattern” process. This value does indeed seem unusual, and I personally agree that it should not be part of the output.

To proceed with the investigation, I will escalate this issue to our development team to determine why this value is being generated. They will analyze the transformer behavior in detail to confirm whether this is a bug or if there’s an underlying configuration issue causing this behavior.

I’ll keep you updated as soon as I receive further insights from the development team. Thank you for your patience and understanding.