Grid paging works on localhost/development but doesn't work when pushed to remote server

[Dylan Kulesza]

Hello:

Is there any reason why paging would work locally on development, but when pushed to a remote server no longer function?

When working locally everything functions as expected.  When I push to a remote server and open up the angular app, my grid shows 0 of 0 pages (0 items) and only displays the first page.  

I'm using an OData adaptor and the service is the same locally and for the remote server.  Looking at the OData response, I have the @odata.count value in both responses. 

Thoughts?

[Manivel Sellamuthu]

Hi Dylan, 

Greetings from Syncfusion support. 

Yes. From the statement “my grid shows 0 of 0 pages (0 items)”, we can understand that the data was not bound to Grid due to some reason. 

To find the exact reason, please check the below and share the details, and share (if you got any). 

1. Share the Grid code
2. Bind the actionFailure event to the Grid,

Documentation: https://ej2.syncfusion.com/angular/documentation/grid/data-binding/#handle-http-error 

3. Please check and share if any console error thrown
4. Bind the beforeDataBound event of the Grid and check you have records for the current view.

Regards, 

Manivel 

[Dylan Kulesza]

ActionFailure wasn't causing any events.

Data was being returned (and bound) by the grid item (first page always loads).

Was in proper OData format.

I was able to resolve the issue by:

Upgrading to the latest Syncfusion

Clear packages.lock

Delete @syncfusion

npm install to latest

Now it works as expected.

[Manivel Sellamuthu]

Hi Dylan, 

Thanks for your update. 

We are happy to glad that your problem has been resolved. 

Please get back to us, if you need further assistance. 

Regards, 

Manivel