# Custom content table with 2K+ rows

**URL:** <https://community.seqera.io/t/custom-content-table-with-2k-rows/961>\
**Category:** Ask for help\
**Tags:** multiqc\
**Created:** [July 12, 2024, 2:06pm UTC](https://community.seqera.io/t/custom-content-table-with-2k-rows/961 "2024-07-12T14:06:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jinfinance](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/jinfinance/32/774_2.png) [@jinfinance](https://community.seqera.io/u/jinfinance)\
**Post date:** [July 12, 2024, 2:06pm UTC](https://community.seqera.io/t/custom-content-table-with-2k-rows/961/1 "2024-07-12T14:06:23Z")

</div>

I’m creating a custom content table with many rows… It works as expected with 400+ rows

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/1X/fa1aff8a0f582cdba916c0ee93eef253645dc588.png)

But on a larger data set of 2K+ rows, it changed to this:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/1X/b9b802f916245be66f957c2bd5723ab537c83b9d.png)

Is there a default threshold value, 1K ? which triggered this behavior ? Can I switch it off ?

Thank you !

---

<div class="post-metadata">

**Author:** ![ewels](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/ewels/32/1_2.png) [@ewels](https://community.seqera.io/u/ewels)\
**Post date:** [July 13, 2024, 6:56am UTC](https://community.seqera.io/t/custom-content-table-with-2k-rows/961/2 "2024-07-13T06:56:37Z")

</div>

Yup, it’s `max_table_rows`. See the docs here:

> **[Configuration - MultiQC](https://multiqc.info/docs/getting_started/config/#tables--violin-plots)**
>
> Settings to tweak how MultiQC works

---

<div class="post-metadata">

**Author:** ![jinfinance](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/jinfinance/32/774_2.png) [@jinfinance](https://community.seqera.io/u/jinfinance)\
**Post date:** [July 13, 2024, 3:37pm UTC](https://community.seqera.io/t/custom-content-table-with-2k-rows/961/3 "2024-07-13T15:37:31Z")

</div>

Great !

I actually tried “no\_violin”: True , and it seemed working.

Does it have the exact same effect as ‘max\_table\_rows’ ?

Thanks again !

---

<div class="post-metadata">

**Author:** ![jinfinance](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/jinfinance/32/774_2.png) [@jinfinance](https://community.seqera.io/u/jinfinance)\
**Post date:** [July 13, 2024, 3:40pm UTC](https://community.seqera.io/t/custom-content-table-with-2k-rows/961/4 "2024-07-13T15:40:05Z")

</div>

btw, while we’re at it… I’m also interested in this link:

[Customising order of modules - MultiQC - Seqera Community](https://community.seqera.io/t/customising-order-of-modules/906)

Do you have any suggestions ?

Thanks !

---

<div class="post-metadata">

**Author:** ![ewels](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/ewels/32/1_2.png) [@ewels](https://community.seqera.io/u/ewels)\
**Post date:** [July 13, 2024, 9:01pm UTC](https://community.seqera.io/t/custom-content-table-with-2k-rows/961/5 "2024-07-13T21:01:49Z")

</div>

> [@jinfinance](#):
>
> I actually tried `no_violin: True` , and it seemed working.
> 
> Does it have the exact same effect as `max_table_rows` ?

Almost - it just disables the violin plots completely rather than adjusting the threshold at which tables are converted into violin plots (so end result should be the same 👍