autoSync | auto sync directury to linux server | Data Processing library

Ok, I think I see your problem. Kendo is sending a application/x-www-url-formencoded content type and I'm guessing your endpoint only accepts application/json. Two solutions, either make your endpoint accept x-www-url-formencoded or prefilter the Ajax request before it is sent.

Haven't done any Nodejs work so I can't offer pointers. However, if your endpoint is Java, in Spring it was simply removing the @ResponseBody annotation.

Next option is to prefilter the Ajax request. This example modifies the URL, so this could work in your Delete method. First off is modifying your transport to something like so:

because return { data } is not a valid expression for async functions

just use AsyncStorage, react-native-storage is not needed unless you develop for both mobile and web

Originally, the API method for ADD(CREATE) passed back the entire List (JSON Array) of Maximo entries.

Solution is to pass back only the updated version of the model object initially passed to the ADD(CREATE) method, including the newly assigned "id" value. Newly created entries will have a negative index value which I'll later use at the DB level within a MERGE statement (ie negative values for the primary key shouldn't exist in the DB table) to sync the DB.

If not already clear, I'm using the TempData["MaximoList"] object to maintain the state of the Kendo ListView Control across API controllers. Saving the control state to the DB (leveraging the TempData object) will occur in a more generic controller method which doesn't manage state (adds/deletes/etc.) to the TempData object.

I've also reworked the DESTROY (Delete) components to remove deleted items from the (UI) list only on a successful API call, and have cleaned up the JS by removing a number of unnecessary sets to the control not required to reflect the state of TempData object.

My API Method for ADD method is now:

Ext's rest proxy is designed to use standard REST APIs where paging and filtering options are passed in as query parameters. I.e. something like

https://localhost:44313/api/Rentals?start=1&limit=25

I would recommend to use this approach rather than a non standard REST API. It will enable you to use Ext's related features seamlessly.

If there is no way to change the API and you need to stick with your current server configuration then you need to create a custom proxy overriding some of the related functions. The best bet if you override the buildUrl function and pass your custom generated URL to the request object.

UPDATE

You can start with this code (also created a Fiddle):

The application data folder is a special hidden folder that your app can use to store application-specific data, such as configuration files. The application data folder is automatically created when you attempt to create a file in it. Use this folder to store any files that the user shouldn't directly interact with. This folder is only accessible by your application and its contents are hidden from the user and from other Drive apps.

There's a big difference between user/app content from developer’s app and configuration file.

You will still need to issue a pm2 list command to get the app_name but this may give you a bit of help.

From the steps below you could set up a script to loop through each of the PID's returned from the command pm2 pid. This could be done by storing the output in a file pid.text and looping through.

Why do you put [Route] attributes on your class....? They should be on Controller's Action.

Then you can open Chrome's development tool and look at network tab to check whether the data is sending to the back-end.

You can paste the picture of network to show us when you think you should get the data, then we can check what problem is.

You can try with dataSource batch set to true.

Problem with ComboBox I solved this way. Added a new class for combobox's store. The controller returns a list of this objects.