1. Home
  2. Forum
  3. Blazor
  4. ASP.Net Core OData V8 not working with V4 SfDataManager Adpator

ASP.Net Core OData V8 not working with V4 SfDataManager Adpator

Hi, we are using the free license of your software for Blazor. I'm currently implementing a SFDataManager in a SFGrid. The problem I'm having is the current OData implementation in ASP.NetCore expects a string in the request i.e api/Tenants('some-id') but your OdataV4 adaptor creates requests that are api/Tenants(some-id). Is there a way to change this depending on key type?

10 Replies
JP Jeevakanth Palaniappan Syncfusion Team August 20, 2021 12:35 PM UTC

Hi John, 

Greetings from Syncfusion support. 

We have checked your query and we need some more details regarding the problem. So kindly share us the below details. 

  1. When are you facing this problem. During initial rendering or any grid action or performing CRUD operation?
  2. Kindly share us the complete code of Grid and SfDataManager.
  3. Kindly share us the issue reproducing sample.
  4. Kindly share us the video demo showing the reported problem.

The above requested details will be helpful for us to validate your problem and to provide you with a better solution as early as possible. 

Regards, 
Jeevakanth SP. 


JO John August 20, 2021 02:04 PM UTC

Hi,


Thanks for getting back to me.


  1. This issue only occurs during Update and Delete operations from the ODataV4 Adaptor
  2. See attached code sample to reproduce error.
  3. Replace Syncfusion key in Program.cs in the Client
  4. This was created and run using Visual Studio 2019
  5. Run the server and it should open on http://localhost:5000
  6. Go to the fetch data tab
  7. The weather data will load via the DataManager
  8. Try and update or delete one of the entries
  9. A console error shows that there is a 500 internal error.

This is due to the request using the parathesis key (some-id) without quotes. When the call is made manually  with quotes i.e (‘some-id’). The request would be successful.


Thanks

John


Attachment: OdataSyncfusionIssue_c7a6754d.rar

RS Renjith Singh Rajendran Syncfusion Team August 23, 2021 12:33 PM UTC

Hi John, 

We have confirmed it as a bug and logged the defect report “Problem with odata update request when having number typed string values in primarykey” for the same. Thank you for taking the time to report this issue and helping us improve our product. At Syncfusion, we are committed to fixing all validated defects (subject to technological feasibility and Product Development Life Cycle) and including the defect fix in our weekly release which is expected to be rolled out by the end of September, 2021.  
       
You can now track the current status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.       

Regards, 
Renjith R 



RS Renjith Singh Rajendran Syncfusion Team October 5, 2021 03:12 AM UTC

Hi John, 

Sorry for the inconvenience caused. 

Due to some unforeseen circumstances, we have planned to include this in our upcoming bi-weekly release which is expected to be rolled out on or before the mid of October, 2021. 
  
Until then we appreciate your patience.  
  
Regards,  
Renjith R 


MC Mason Channer October 12, 2021 11:34 PM UTC

I also have this issue too.  Please let me know when this update is available.


RS Renjith Singh Rajendran Syncfusion Team October 14, 2021 03:47 AM UTC

Hi Mason, 

Sorry for the inconvenience. 
 
We have planned to include the fix for this issue in our upcoming weekly patch release which is expected to be rolled out on or before October 20, 2021. Until then we appreciate your patience.  

Please follow up on the feedback link for future updates on this bug. 

Regards, 
Renjith R 


RS Renjith Singh Rajendran Syncfusion Team October 20, 2021 10:12 AM UTC

Hi All,   
 
We are glad to announce that our latest release(19.3.0.46) has been successfully rolled out. We have included the fix for this issue “Problem with OData Update request when having number typed string values in primarykey” in our latest version release. So please upgrade to our latest release for latest fixes and features.  
 
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.   
    
Regards,              
Renjith R  


JO John October 21, 2021 01:42 PM UTC

Hi,


There is still an issue with this.  Adding and Updating are working correctly, but when deleting a record the Key is still passed without quotation marks resulting in it not being parsed as a string by the API.


RS Renjith Singh Rajendran Syncfusion Team October 22, 2021 08:39 AM UTC

Hi John, 

Sorry for the inconvenience caused. 
 
We have confirmed this as a bug and logged a defect report “Problem with OData Delete request when having number typed string values in primarykey”. We have planned to include the fix in our upcoming weekly patch release which is expected to be rolled out on or before the first week of November 2021.  
 
You can now track the current status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link. 

Until then we appreciate your patience. 
 
Regards, 
Renjith R 


RS Renjith Singh Rajendran Syncfusion Team November 23, 2021 12:56 PM UTC

Hi John, 
 
We are glad to announce that our weekly patch release (v19.3.0.55) has been rolled out successfully and in this release, we have included the fix for the issue “Problem with OData Delete request when having number typed string values in primarykey”. So kindly update your NuGet (Syncfusion.Blazor) to our latest version to resolve the reported issue. 
 
Please find the NuGet package below 
 
 
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.  
 
Regards, 
Renjith R  


Loader.
Up arrow icon