DB entries removal

Bika.ai discussions
1

Hi, I think the delete entries process should be improved.
Case: i need to remove 14k entries from the DB. The fastest (?) way possible now is to select them by 1000 (maximum on page) and then RMB → Delete entries. But selection doesn’t work well, I need to SCROLL over those 1000 entries and even after that, just about 600-700 entries are selected and can be deleted. After they’re deleted I won’t need to scroll again , but it will be again like 600-700 entries with tendention to lower numbers. This way I spend like 10 minutes to remove 14k entries which is nonsense honestly :smiley: please fix asap.
One good solution would be to allow COPILOT to remove entries directly so one could ask to empty the DB.

P.S. the “create new db” won’t work here because I have dozens of nodes in automation which are connected to this current db

2 Likes
2

Hi @anp, thanks for bringing this up. I’ve already shared it with our product and engineering teams, and it’s on their review list.

The current bulk deletion experience is not ideal, and your suggestion has been passed along for the team to evaluate.

Appreciate you taking the time to report this. I’ll follow up here if there are any updates.

1 Like
3

Hi, something was updated and now it works even worse. Please make it that when user sets the page size to 1000 entries, the frontend will actually LOAD all those 1000 entries without needing to scroll down the page.

4

Hi @anp,

Thanks for the update, and sorry about the trouble.

This seems to be related to a recent frontend change. I’ve passed this along to the team so they can take a closer look and improve the loading behavior. We’ll follow up once there’s more to share.

5

Hi @anp,

Quick update here :wave:

This issue has been optimized on our side. Could you please check if the page now loads all 1000 entries as expected?

Let us know if you’re still seeing anything off.

Thanks for flagging it earlier, that really helped.

6

Hi, thank you very much, this issue is now fully resolved, at least for my workflow :slight_smile: