API Controllers that dont use Microsoft.AspNetCor.Datasync TableController

[ideas2appsaustralia]

If the API I am accessing does not use TableController class and has different endpoint URLs but the same HTTP filter which doesnt match with DatasyncClient PullItemsAsync expectation what can I do to find a solution?. The API has a [HttpPost] that I use to get all records but then it has a second HttpPost, [HttpPost("CreateLoad")] that I need to hit if I want to insert a new record. [HttpGet] on its own is not an allowed method

[adrianhall]

We do not support and generally you cannot use a server that does not implement TableController.

[ideas2appsaustralia]

@adrianhall , I have used Postman and taken the MAUI app out of the picture and a record is still created and sent back in the response leaving the other records behind. So its on the server side and either something happening with TableController<> or the API itself or an interaction. The APIs own controllers with only their own base class do not show the problem.

Using the same API with both its builder.Services.AddController {...} and our builder.Services.AddDatasyncControllers could this create any conflict? although I admit I removed builder.Services.AddCOntroller {...} and still problem persisted.

Look anyway I think its getting off topic and into my own specific problem, but just in case you could think of any tips to debug this TableController situation otherwise dont bother replying

[adrianhall]

Without delving into source code, I can't provide suitable suggestions. Something in your code is doing the write to the data store. We are extremely careful to not alter the data store when issuing GETs (in fact, there are explicit tests for this case). I can say with some certainty that it is not the table controller causing your issues.

[ideas2appsaustralia]

@adrianhall , actually I was wrong above. Using Postman Get it works normally. Post creates the rogue record.

When I use the phone app Datasync hits the await offlineTable.PullItemsAsync("", options); and I see the above Get request but then on the EntitTableRepository on the server the CreateAsync task code is hit whereas it should be hitting the AsQueryable.

So it seems the maui app is creating the item.

How do I delete the que? On the offlineTable.PullItemsAsync object there 0 pending operations. I renamed the sqlite databse and Ive put await offlineTable.PurgeItemsAsync("", new PurgeOptions { DiscardPendingOperations = true }); in my code.

I just deleted the emulator and reinstalled a new one which surely must have deleted any que but problem persists

I cant debug inside PullItemsAsync to see where this rogue entity is coming from.

[adrianhall]

You can delete the SQLite database, or you can use the ExecuteSqlAsync() method to delete all records in the __OperationsQueue table. Or you can use PurgeItemsAsync() as you did.

Something tells me that you have a piece of code that is creating a record. We don't do that on PullItemsAsync() nor do we do that on a GET. Add logging to the client to determine if you are doing a POST. If you are, then you can and should trace it back. Don't forget that a PullItemsAsync() automatically does a Push if the table has any pending records to push.

[ideas2appsaustralia]

Yes I was creating something in the end! It was in one of the Delegating Handlers where I was setting request.content.header.contentype in order for localhost to work and I was creating an instance of a content which resulted in maybe a body or even just the content itself was then being handled as if it was a entity