# Pagination doesn't appear when detailed is turned on

**URL:** <https://community.forestadmin.com/t/pagination-doesnt-appear-when-detailed-is-turned-on/1816>\
**Category:** Help me!\
**Tags:** howtos, setup\
**Created:** [February 9, 2021, 10:51am UTC](https://community.forestadmin.com/t/pagination-doesnt-appear-when-detailed-is-turned-on/1816 "2021-02-09T10:51:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Talha\_Habib](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/talha_habib/32/1482_2.png) [@Talha\_Habib](https://community.forestadmin.com/u/Talha_Habib)\
**Post date:** [February 9, 2021, 10:51am UTC](https://community.forestadmin.com/t/pagination-doesnt-appear-when-detailed-is-turned-on/1816/1 "2021-02-09T10:51:35Z")

</div>

## Expected behavior

pagination should work regardless of detail setting on/off

## Actual behavior

the table is showing 1 of 0 when detail view is turned off, which by default is off whenever you launch or update an instance, or when you add a new table.

## Context

we are using Postgres, the table with or without association behaves the same way

- Package Version: 1.0
- Express Version: 4.x.x
- Sequelize Version: 6.x.x
- Database Dialect: Sequelize
- Database Version: Postgres 12.x
- Project Name: Lighthouse

Error Reproduced: [Loom | Free Screen & Video Recording Software](https://www.loom.com/share/b0fd01fb3e02437c87ba6ed62bbe53f0)

also another issue as. you can see on video, the brush/customize/setting tool doesn’t work until reload.

---

<div class="post-metadata">

**Author:** ![anon62739609](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@anon62739609](https://community.forestadmin.com/u/anon62739609)\
**Post date:** [February 9, 2021, 11:20am UTC](https://community.forestadmin.com/t/pagination-doesnt-appear-when-detailed-is-turned-on/1816/2 "2021-02-09T11:20:52Z")

</div>

Hey @Talha_Habib and welcome in our community,

It’s a known issue that happens sometimes. It’s due to a conflict between the route `/forest/your-collection-name/count` and `/forest/your-collection-name/:recordId`. To avoid this issue you can replace all

```javascript
router.get('/your-collection-name/:recordId', ...);

```

by

```javascript
router.get('/your-collection-name/:recordId(?!count)', ...);

```