@Polar bear so paginating the api won't work and doing it through nextjs is the best method? Like I have an idea but that's for worst case scenario type deal.

No no, it works. I just dont have any idea how to send pageIndex and pageSize to the backend. In normal react, i just save them in a state and send it.
Here, i have formData, but also pageIndex(the page user clicks and pageSize(thr total amount of data fetched from the backend)

The paginator i am using does not have any name or id propertiry that i can use to utilize in FormData

So you don't have any way of sending the pageIndex and page size in the form data? Have you tried hidden fields @Polar bear

https://primereact.org/paginator/

I am using this basically. I ahve not heard of hidden fields before1

You can put in the page index and the page size in there and get them as formdata

Will do this tomorrow morning! thanks!

Does not work, by no mean i cannot send Prime React paginator data as formData. How are we suppose to paginate millions of data without fetching them first?

So you can't paginate via the api and need to do it natively right?

Like on nextjs

We have an external api written in .net core. The endpoint accepts parametres such as this, that, pageindex,pagesize.

This and that are form values. pageIndex is the page user clicks on pagination and pageSize is mostly harcoded 10.

i can send this and that form data, but when i handle pagechange i need to send pageSize and pageIndex as well. I am starting to think this is not possible to pull off

Where are you saving the page index @Polar bear

In the url?

nope, i am using Prime React paginator. i am extracting them from the event

not saving it anywhere

but after i extract them, i can send it to the backend and fetch data through a different server action, but this time datatable cannot be updated because i am usinf useFormAction and taking returned state and displaying on the datatable.

This way i end up with two different data states. One from form action, the other from pagination response

This looks to be something you have complicated a lot, why do you need an action, it looks like you are already using client components for handling pagination

"form action"

i am trying to convert a react app to nextjs just to see if it fits our needs. But i am starting to think, the only thing we can use with nextjs is routing.

Do you mean to say, i should just fetch data onside the client component like i would in react? i was following the tutorial and formdata was used there, that is why i used it. So far everything was good but the pagination really made things a bit worse for me