I have a simple grid pointing to ODataV4
When i make an update on the grid, i see 2 requests in a row - one PATCH request ( /fe/odata/providers('63798f07dd296656807c3ebc') ) with an update that completes successfully (though it returns no payload in response) and another GET that returns 404 because it is made to /fe/undefined
i see that GET is triggered by refreshing the row but i dont get why it is sent to "/fe/undefined" URL?
Greetings from Syncfusion support.
Before proceeding with the solution, share the below details so that we will be able to provide a better solution.
The issue you're seeing with the grid making a GET request to an invalid URL ( "/fe/undefined" ) after making an update to the grid is likely related to the grid's data management. The grid is likely configured to refresh the row after the PATCH request is completed, which is causing it to send a GET request to the server.
Regarding the invalid URL ("/fe/undefined"), it could be caused by a few things:
You should check the configuration of the dataSource property, as well as any custom logic or code that might be modifying the grid's behavior. You can also try to check the value of the dataSource when the error happens and compare it with the initial value that you set. Also, check the network tab of the browser's developer tools to see the exact url that is being sent by the grid, this will help you identify the source of the problem.
You can also find help in the official documentation of syncfusion which might be helpful to resolve the issue, https://ej2.syncfusion.com/documentation/grid/data-binding/remote-data/#odata-v4-adaptor---binding-odata-v4-service
Share a simple issue replicating sample so that we will be able to assist you further. Please let me know if you have any questions or if there's anything else I can do to help.
Sorry but i dont follow. Complete grid code is posted in the message above - it does not really have special configuration. Also if i simply click refresh on the tab, the grid refreshes correctly before and afteer, so this issue occurs only on PATCH request refresh.
Steps to reproduce:
We tried to reproduce the issue using the url provided, but we are not able to run the sample as it shows bad gateway. Please refer the below screenshot.
By default, If we use ODataV4Adaptor, the GET method will be triggered for all the grid actions like Paging, Sorting, Filtering, etc., The POST, PATCH, DELETE methods will be triggered for CRUD actions like insert, edit, delete respectively. In these methods, you can perform the CRUD actions in your service.
Screenshot: payload on CRUD actions
public class BooksController : ODataController
private BookStoreContext _db;
public BooksController(BookStoreContext context)
_db = context;
if (context.Books.Count() == 0)
foreach (var b in DataSource.GetBooks())
// GET api/values
public IQueryable<Book> Get()
// POST api/values
public IActionResult Post([FromBody]Book book)
public Book Patch(int key, [FromBody]Delta<Book> patch)
var query = Request.Headers["params"];
var entity = _db.Books.Find(key);
// DELETE api/values/5
public async Task<int> Delete(int key)
var od = await _db.Books.FindAsync(key);
While using ODataV4 Adaptor in the Grid, when performing any data action like filtering, sorting, paging, searching, exporting, etc., the Grid sends the queryString in OData standards to the server. In the server side, you should handle the all the data operations and return the data in required format to the Grid.
ODataV4 sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/odatav41984479243.zip