# Groupby blocks divided into severall parts

**URL:** <https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050>\
**Category:** Technical Help\
**Created:** [April 19, 2024, 7:53am UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050 "2024-04-19T07:53:44Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![asan](https://community.baserow.io/user_avatar/community.baserow.io/asan/32/2108_2.png) [@asan](https://community.baserow.io/u/asan)\
**Post date:** [April 19, 2024, 7:53am UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/1 "2024-04-19T07:53:44Z")

</div>

Hi!

I would like to share a weird behavior occurring with a group by view.

In some cases (I didnt manage to understand exactly when), some groups are separated in two (sometimes more) parts as shown in the following screen in which the group of the items having both `Team` and `EGQ` tags is divided into two parts (one with 5 items and the other one with 2 items). The overall count is fine (7 for both).

 ![Sélection_160](https://community.baserow.io/uploads/default/original/2X/a/ae759b20a485c2449fefd75882982ba592566258.png)

Is this a bug/issue ? Or am I doing something wrong or did I miss something?

Thanks for your help!  
Asan 🦊

---

<div class="post-metadata">

**Author:** ![olgatrykush](https://community.baserow.io/user_avatar/community.baserow.io/olgatrykush/32/219_2.png) [@olgatrykush](https://community.baserow.io/u/olgatrykush)\
**Post date:** [April 22, 2024, 10:14am UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/2 "2024-04-22T10:14:31Z")

</div>

Hey @asan, could you please show or share how the group by is set? Maybe you have some other filters or sorting enabled?

---

<div class="post-metadata">

**Author:** ![asan](https://community.baserow.io/user_avatar/community.baserow.io/asan/32/2108_2.png) [@asan](https://community.baserow.io/u/asan)\
**Post date:** [April 22, 2024, 10:35am UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/3 "2024-04-22T10:35:15Z")

</div>

Hi Olga,

They are two filters, the groupby and no sorting. Here are some screens to show what filter/sorting are activated and how :

![Sélection_164](https://community.baserow.io/uploads/default/original/2X/2/2b9baeaa54d54737b7e2ffb3f1872b204779a7de.png)

 ![Sélection_166](https://community.baserow.io/uploads/default/original/2X/e/e1cf7a0d79dae15c5577d67ea3802d735ce58b3e.png)

Hope this helps 🙂

Thanks!  
Asan 🦊

---

<div class="post-metadata">

**Author:** ![olgatrykush](https://community.baserow.io/user_avatar/community.baserow.io/olgatrykush/32/219_2.png) [@olgatrykush](https://community.baserow.io/u/olgatrykush)\
**Post date:** [April 22, 2024, 10:50am UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/4 "2024-04-22T10:50:41Z")

</div>

Thanks @asan!

I’ll ask the dev team to check your case.

---

<div class="post-metadata">

**Author:** ![bram](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/9d8465/32.png) [@bram](https://community.baserow.io/u/bram)\
**Post date:** [April 23, 2024, 6:35pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/5 "2024-04-23T18:35:49Z")

</div>

Hi @asan, I suspect that this actually a bug. Would you be able to give us more insights into your data? We would need to be able to reproduce the scenario to figure out what’s going wrong specifically?

---

<div class="post-metadata">

**Author:** ![asan](https://community.baserow.io/user_avatar/community.baserow.io/asan/32/2108_2.png) [@asan](https://community.baserow.io/u/asan)\
**Post date:** [April 23, 2024, 7:03pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/6 "2024-04-23T19:03:42Z")

</div>

Hi!  
How can I help? What insight would you need?  
I created a fake table and I can’t reproduce that behavior.  
Howver, exploring what’s happening on my actual table, I realized that it could come from the filter (and not from the group by) because when I filter on my field, I get this result:

 ![Sélection_169](https://community.baserow.io/uploads/default/original/2X/a/ae9e0697eea9ad4fc43b0bf01ea644aed5d2616d.png)  
Any idea?  
Let me know what you need to investigate,  
Thanks,  
Asan 🦊

---

<div class="post-metadata">

**Author:** ![bram](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/9d8465/32.png) [@bram](https://community.baserow.io/u/bram)\
**Post date:** [April 24, 2024, 3:50pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/7 "2024-04-24T15:50:10Z")

</div>

I’m not really sure why this is happening based on the screenshot. Would you be able to share the view in Baserow publicly, and share that with me? It can also be shared privately. Then I can take a look at the raw data. Thanks!

---

<div class="post-metadata">

**Author:** ![asan](https://community.baserow.io/user_avatar/community.baserow.io/asan/32/2108_2.png) [@asan](https://community.baserow.io/u/asan)\
**Post date:** [April 24, 2024, 9:16pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/8 "2024-04-24T21:16:29Z")

</div>

Hi Bram,  
Thanks for your message, I’ve just sent a private message.  
Asan 🦊

---

<div class="post-metadata">

**Author:** ![bram](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/9d8465/32.png) [@bram](https://community.baserow.io/u/bram)\
**Post date:** [April 26, 2024, 9:05am UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/9 "2024-04-26T09:05:47Z")

</div>

Thanks for sharing @asan. We’ll look into it as soon as possible.

---

<div class="post-metadata">

**Author:** ![asan](https://community.baserow.io/user_avatar/community.baserow.io/asan/32/2108_2.png) [@asan](https://community.baserow.io/u/asan)\
**Post date:** [August 8, 2024, 12:06pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/10 "2024-08-08T12:06:49Z")

</div>

Hi Baserow team 🙂  
Do you have news on this bug?  
Thanks,  
asan 🦊

---

<div class="post-metadata">

**Author:** ![bram](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/9d8465/32.png) [@bram](https://community.baserow.io/u/bram)\
**Post date:** [August 9, 2024, 8:26am UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/11 "2024-08-09T08:26:23Z")

</div>

Hey @asan, I remember that we did made some changes for this. Do you still have the same problem?

---

<div class="post-metadata">

**Author:** ![asan](https://community.baserow.io/user_avatar/community.baserow.io/asan/32/2108_2.png) [@asan](https://community.baserow.io/u/asan)\
**Post date:** [August 9, 2024, 2:10pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/12 "2024-08-09T14:10:18Z")

</div>

Hi,  
Yes, we still have this problem on our self-hosted Baserow. We are still in 1.23.2, do you know in which release you have fixed this bug?  
Thanks,  
asan 🦊

---

<div class="post-metadata">

**Author:** ![asan](https://community.baserow.io/user_avatar/community.baserow.io/asan/32/2108_2.png) [@asan](https://community.baserow.io/u/asan)\
**Post date:** [September 24, 2024, 9:10pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/13 "2024-09-24T21:10:15Z")

</div>

Hi,  
We have just upgraded our self-hosted Baserow to version 1.27.2 but still have this problem. The same problem still occurs if I create a new field on which applying the Group By. I also face weird behaviors (rows moving up and down) when I change the value of both the Group By field of others.  
@bram I have shared some data, did you find anything?  
Thanks,  
asan 🦊

---

<div class="post-metadata">

**Author:** ![bram](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/9d8465/32.png) [@bram](https://community.baserow.io/u/bram)\
**Post date:** [September 26, 2024, 8:25am UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/14 "2024-09-26T08:25:37Z")

</div>

Hey @asan, in that case I don’t think it has recently been resolved. I suspect that there is a difference between the backend and web-frontend sort of the multiple select field. Do you have a way of reproducing this problem? Ideally steps like: create a table, create a multiple select field, create 10 rows, set the following data, and apply a sort/group, or something like that. If we can reproduce it, then we should be able to fix it relatively easy.

---

<div class="post-metadata">

**Author:** ![asan](https://community.baserow.io/user_avatar/community.baserow.io/asan/32/2108_2.png) [@asan](https://community.baserow.io/u/asan)\
**Post date:** [September 26, 2024, 9:40am UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/15 "2024-09-26T09:40:15Z")

</div>

I’ve tried to reproduce it but I could not find a way: if I duplicate the table, the Group By works well, if I create a new table from scratch, the Group By works well.

I did export the table as a .csv but there is no weird value…

When I create a new field to apply the Group By with same values, rows are moving when I add the value: for instance, the row 5153 was in the first block `Team` and `EGQ` but when I added the values on the `Test` field the row moved in a new block (the third one) with tag `Team` and `EGQ` whereas I did not change the value of the field on which the Group By is applied. Howerver, when I refresh the page, it gets back to the two initial blocks.

 ![Sélection_155](https://community.baserow.io/uploads/default/original/2X/0/0341711590833a946011c8a024936262a4d2cc78.jpeg)

I tried to find a way to bypass this issue only manipulating the existing table but I could not. The solution of creating a new table would work but it would mean to have a new link which is hard to manage because it is used in many different ways (short links, n8n automations, etc.).

Thanks for your help,  
asan 🦊

---

<div class="post-metadata">

**Author:** ![bram](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/9d8465/32.png) [@bram](https://community.baserow.io/u/bram)\
**Post date:** [September 30, 2024, 8:50am UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/16 "2024-09-30T08:50:31Z")

</div>

I’ve added it to my task list to dive deeper into it @asan. I’ll get back to you on this.

---

<div class="post-metadata">

**Author:** ![asan](https://community.baserow.io/user_avatar/community.baserow.io/asan/32/2108_2.png) [@asan](https://community.baserow.io/u/asan)\
**Post date:** [October 9, 2024, 2:33pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/17 "2024-10-09T14:33:23Z")

</div>

Thanks 🙂  
Just ask me if you need some more information.  
asan 🦊

---

<div class="post-metadata">

**Author:** ![bram](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/9d8465/32.png) [@bram](https://community.baserow.io/u/bram)\
**Post date:** [November 13, 2024, 8:51pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/18 "2024-11-13T20:51:19Z")

</div>

Hey @asan, in the 1.29 release today, we’ve released improved sorting abilities for the single and multiple select field. This can be directly related to the problem you had. Would you mind testing if you still have the problem?

---

<div class="post-metadata">

**Author:** ![asan](https://community.baserow.io/user_avatar/community.baserow.io/asan/32/2108_2.png) [@asan](https://community.baserow.io/u/asan)\
**Post date:** [February 11, 2025, 10:57pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/19 "2025-02-11T22:57:07Z")

</div>

Hi @bram,  
Thanks for your answer. We are in 1.30.1 but I still have the problem…  
I can send you some screenshots.  
Thanks,  
asan 🦊

---

<div class="post-metadata">

**Author:** ![bram](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/9d8465/32.png) [@bram](https://community.baserow.io/u/bram)\
**Post date:** [February 12, 2025, 12:48pm UTC](https://community.baserow.io/t/groupby-blocks-divided-into-severall-parts/5050/20 "2025-02-12T12:48:44Z")

</div>

Hey @asan, I’m sorry to hear that you’re still running into this problem. Would you be able to use the workspace export functionality as documented here ([Export a workspace](https://baserow.io/user-docs/export-workspaces)) to make a full export of your workspace and share that with me privately? That should help us to reproduce and identify the problem you’re encountering.
