# Bug: Weird behaviour with a move using a pattern

**URL:** <https://forum.alumio.com/t/bug-weird-behaviour-with-a-move-using-a-pattern/1594>\
**Category:** Alumio Feedback\
**Created:** [January 24, 2025, 4:17pm UTC](https://forum.alumio.com/t/bug-weird-behaviour-with-a-move-using-a-pattern/1594 "2025-01-24T16:17:31Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![floris](https://forum.alumio.com/letter_avatar_proxy/v4/letter/f/a3d4f5/32.png) [@floris](https://forum.alumio.com/u/floris)\
**Post date:** [January 24, 2025, 4:17pm UTC](https://forum.alumio.com/t/bug-weird-behaviour-with-a-move-using-a-pattern/1594/1 "2025-01-24T16:17:31Z")

</div>

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:

```auto
{
  "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](https://alumio-forum.s3.dualstack.eu-central-1.amazonaws.com/uploads/original/2X/e/e8107949e28c4a7d1008232c37ad881d1a160794.png)

This is the result:

```auto
{
  "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](https://forum.alumio.com/uploads/short-url/wwehRQj94SWS8lKo9BFVEACxvxI.ndjson) (923 Bytes)

---

<div class="post-metadata">

**Author:** ![floris](https://forum.alumio.com/letter_avatar_proxy/v4/letter/f/a3d4f5/32.png) [@floris](https://forum.alumio.com/u/floris)\
**Post date:** [January 24, 2025, 4:23pm UTC](https://forum.alumio.com/t/bug-weird-behaviour-with-a-move-using-a-pattern/1594/2 "2025-01-24T16:23:06Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![m.arief](https://forum.alumio.com/user_avatar/forum.alumio.com/m.arief/32/1568_2.png) [@m.arief](https://forum.alumio.com/u/m.arief)\
**Post date:** [January 27, 2025, 6:22am UTC](https://forum.alumio.com/t/bug-weird-behaviour-with-a-move-using-a-pattern/1594/3 "2025-01-27T06:22:19Z")

</div>

Hi @floris,

You can read this article [Group records Transformer](https://forum.alumio.com/t/group-records-transformer/1425) and use the “Group Records” transformer if you want to group data by a specific “key.” Please refer to the sample provided below.

 ![image](https://alumio-forum.s3.dualstack.eu-central-1.amazonaws.com/uploads/original/2X/9/97a22645cad1606fb01c51c1c6481fd73a33a7c5.png)

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

---

<div class="post-metadata">

**Author:** ![floris](https://forum.alumio.com/letter_avatar_proxy/v4/letter/f/a3d4f5/32.png) [@floris](https://forum.alumio.com/u/floris)\
**Post date:** [January 27, 2025, 9:46am UTC](https://forum.alumio.com/t/bug-weird-behaviour-with-a-move-using-a-pattern/1594/4 "2025-01-27T09:46:43Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![m.arief](https://forum.alumio.com/user_avatar/forum.alumio.com/m.arief/32/1568_2.png) [@m.arief](https://forum.alumio.com/u/m.arief)\
**Post date:** [January 27, 2025, 3:01pm UTC](https://forum.alumio.com/t/bug-weird-behaviour-with-a-move-using-a-pattern/1594/5 "2025-01-27T15:01:23Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![floris](https://forum.alumio.com/letter_avatar_proxy/v4/letter/f/a3d4f5/32.png) [@floris](https://forum.alumio.com/u/floris)\
**Post date:** [January 27, 2025, 3:36pm UTC](https://forum.alumio.com/t/bug-weird-behaviour-with-a-move-using-a-pattern/1594/6 "2025-01-27T15:36:31Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![m.arief](https://forum.alumio.com/user_avatar/forum.alumio.com/m.arief/32/1568_2.png) [@m.arief](https://forum.alumio.com/u/m.arief)\
**Post date:** [January 28, 2025, 6:47am UTC](https://forum.alumio.com/t/bug-weird-behaviour-with-a-move-using-a-pattern/1594/7 "2025-01-28T06:47:15Z")

</div>

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.