Hi Md Shahidul,
Thanks for your update.
We have analyzed the provided information. By default, we have custom binding support in grid and we suggest to use Grid custom binding concept to achieve this requirement. While using this custom binding concept, this help you to provide your own custom data logic. Grid expects an object as the result of the custom logic and the emitted value should be an object with properties result and count.
At the initial Grid rendering please call your service within the load event of the Grid and please return the result like as “{result: […], count: …}” format to Grid. If you want to perform any Grid actions (like CURD, sorting, filtering, paging, grouping) then we suggest to use Grid dataStateChange and dataSourceChanged events. For grid actions such as paging, grouping, sorting, etc., the dataStateChange event is invoked. You have to query and resolve data using your service in this event based on this event arguments.
The dataSourceChanged event is triggered to update the grid data. You can perform the save operation based on the event arguments and you need to call the endEdit method to indicate the completion of save operation. So we suggest you to use dataStateChange event to handle the crud operations
Please get back to us, if you need further assistance.
Regards,
Thiyagu S